Hi, Saragani.
Thank you very much for the link. This document is much better about the header information.
Anyhow, I must be a dumb stone... experimenting the updated "format" with my small Ruby script did not do the trick.
Here is the array I produced to send usung Ruby:
> Send CMD[size:20]: [210, 4, 101, 0, 14, 0, 47, 49, 48, 82, 69, 48, 48, 50, 48, 48, 53, 49, 70, 13]
This refers to the command string '/10RE0020051F\r', which returns CRC = 1F (49, 70 byte values at the end of message, just before CR, byte 13). The header was added at the begining with values [210, 4, 101, 0, 14, 0] as you can see above.
So, my questions are:
1> The docs says the header is "binary"; here I understand it is BYTE coded numbers - makes sense?
2> The command string is "char", or may I say, ASCII BYTE coded chars, so '/' becomes 47, <CR> becomes 13 and so on - right?
So if I get an byte array with the above values sent to the PLC (which is TCP socket connected for sure), how come it is not responding the request?
If you could shed some guru light over this issues... =]
Best regards,
AD