on 06-07-2010 3:43 PM
Hi,
I attempt to understand the EWM-MFS telegram creation..
One can define Actions and ActionFunctions, TelegramStructures, ... within the MFS customizing. But where is the conversion, creation of telegrams to communicate with PLC? I have problems to understand the concrete interplay of the various elements of EWM-MFS..
Can somebody give me some aid?
Regards!
Bahit A.
Hi Juergen, We are in EWM9.5 we are trying to use latest ABAP push channel concept. That is without PCo to connect to our robot control unit(PLC). Now the question is this Robot vendor can work only with REST or SOAP message. Where can we do the conversion from Telegram message to REST/SOAP message? Could you pl. clarify this.
Thanks & Br
Mathi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
the conversion is done via an RFC adapter. The EWM system sends a RFC to this adapter (which for exmple can be the Pco (Plant Connectivity), but also another adapter), which makes the TCP/IP communication with the PLC.
Best regards
Juergen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Of course it is quite a long time ago, but did you - or others - solve the problem? I'm struggling with the same issue.
When exactly and by which functions is the telegram creation done? When I generate and save a warehouse task (relocation) no telegram is created by the EWM, even though I have customized the PLC.
Kind Regards
Phil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
99 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.