Understanding Modbus adressing in e!COCKPIT

2020-02-27T14:33:16.853000Z

Yeah, seems to work fine when I'm not using the offset field. Checking array-box enables me to define length after defined address.

But how do you do it when writing to control words with function code 16? I mean do you have to reset the bits manually?

Understanding Modbus adressing in e!COCKPIT

2020-02-27T14:33:15.467000Z

Hello,

I have never worked with Wagos e!COCKPIT, but usually when we define a Modbus communication we define the address of the first variable (in your exemple 500) to read and the number of variables to read.

Generally, the address of the first variable can be:
- the number of the variable, for example for% MW100, the address will be 100. This is the case with some PLC.
- User-defined in slave configuration (example with Raspberry Pi).

Hoping this helps you

Best regard.

Understanding Modbus adressing in e!COCKPIT

2020-02-27T14:33:14.978000Z

Hello

Going to set up some generic modbus registers in Wagos e!COCKPIT. The device I'm connecting to has a table that specifies data with "function code 4h" and a table with addresses from 500, 501, 502 and onwards.

In e!COCKPIT when I create a new generic modbus variable I can set function code "ReadInputRegisters (FC 4)", and also a number in "Register" and "Offset".
What do I put in Register and Offset in this case?

I dont have the equipment so I can't do any testing yet.

Recent posts to Understanding Modbus adressing in e!COCKPIT

Understanding Modbus adressing in e!COCKPIT

Understanding Modbus adressing in e!COCKPIT

Understanding Modbus adressing in e!COCKPIT