We tried to use the ethernet port on PLC and with CP 1243-1 but we had no success.

     Best regards,

     LoMi

Hello,

hard to say where the problem is. It is clear that via PC it is possible so problem then can be wrong address of register set to CLIENT block. What is also very important is correct device addtress ID set on PLC, this is static TAH MB_Unit_ID so it must be same as set inside your PC app, I see there 1, prior execute CLIENT block. I expect also that check of connection established is important to check. Hope you understand also that in case you want check and test access from PLC, your PC app must be disconnected from Weintek because Port then is occupied by PC app. Really your screenshots are not enough to say something clear about problem.

          Dear Mr. Duris,

     First of all, thanks for answering. 

     Everything you suggested we already tried. All parameters are the same as in ModbusDoctor and MBDoctor is disconnected before trying communication from PLC.

We have experience with Modbus TCP and it always worked out of the box.

     Can you please specify what information should I send here in order to give you a better picture of the system so you and other experts can help?

     If you or anybody have some suggestions about what should we try please feel free to write.

    Regards,

    LoMi

Hello,

All parameters are the same as in ModbusDoctor...

as I said, this is the problem probably because cfg of register address is different on PLC, in this case due type of register. Compared with one specific situation, you need set regsiter address on CLIENT block differenntly, as table on help to block describes In PC app simply addresses are set without any specific offset, what are defined and required on other devices to better recognize and set address due specific type of register. Look, you have there f.ex. address 6000 but with Input register f.ex. but you can't set this same on PLC, look to table inside help where offset 30001 is expected, in case of this register type..