Hello,

ok, no problem. Can you provide order number of that Keypad? Or link to manual? Without to know close infos about that keypad functionality we can't go further in my opinion. That test is really required.

Update: sry to not check SW, I have limited options now with Siemens SW... I still expect PLC as RTU Slave so you need configure MB_SLAVE block inside S7-1200 and with same comm properties as Schneider has on picture (speed, data bits, parity, ...). That can be way for tests in case that Keypad looks to me like Modbus Master here.

Hello,

very sry. With this info is help not possible. You can do what I recommended already to you, check all messages comming from jeypad to PLC or PC SW and then build your PLC code due that messages. Try prepare that Modbus RTU Slave block on S7-1200 then and make tests. If you don't provide more clear infos, we can't help better, sry.

Hello,

try that simple test with Hercules and PC connected to that Keypad, if you put some key some message need apear on Hercules box. That message can be copied here and can investigate next if you can. No other help now really, sry. I see this way as only one here to go further. 

Simply i expect these steps (if I need make this prj):

1. hack that keypad messages depended to each key pressed on keypad.

2. due that message format can say for sure if it's Modbus protocol or other maybe internal, who know.

3. due this important hack of keypad I can prepare PLC S7-1200 project, all depends to that point 1,2. If I know that messages structure I can simply then prepare PLC code to that keypad keys required action, simple.

Finito.

Update: maybe better explanation of point 3 to be in, this means 2 possibilities. You need due used protocol prepare serial communication on S7-1200. With Modbus RTU it can be maybe better because library is available and due hack of keypad can expect maybe some problems with correct answers with Slave PLC. In case of user defined protocol you need completelly program that serial by yourself with some blocks and in this case that hack of messages from keypad must be very precise. I see that hack most important. I don't know what way you'll select, we can help here to you as much as we can, without doing your job of course.

Hello,

hmmmm looks like something is there but better will be see it as HEX format. Sry, I don't use Hercules (use my own SW). Try find so where it can be set to HEX representation or better see that mesages. Just one thing - success  messages are there but pls try monitor. Messages are comming cyclically or only after key pressed? If HEX format isn't available try find other suitable serial SW and check.

Update: maybe also SW used by some users here with Modbus (ModScan or similar, also not used by me) can be better in this case, try find it, set it as MB RTU Slave (that original Schneider has RTU address 1) with that comm settings and we hope will see it better.

Update2: hmmm but from that screenshot it looks to me ok, I expect you pressed keys on keypad and some messages looking differently  that chars are not ok so try find HEX so it can look like FF 01 30 3A ...     This will be better because your windows char set is Unicode here and hard to understand then ASCII code.

Hello,

eeeeeeeh that Hercules isn't good, now I did test and with hex you can only send (bottom option). received messages it interpret only as chars what is unusable definitelly (for programmers and debug). Ok, try find other serial SW and in last case that Modbus SW.