REXYGEN Community Forum / Modbus Master/ Slave TCP comminication

Re: Modbus Master/ Slave TCP comminication

2016-10-19T13:43:04Z

Hi Hendrik,
in REX (and also in Modbus specification), all the areas are numbered separately. Therefore "register 30001" in 3rd party software or device is equal to "InReg, address 0" in REX. Similarly, "register 40001" equals to "Register (16bit), address 0".

Hope this helps.

Jaroslav

Re: Modbus Master/ Slave TCP comminication

2016-10-19T12:04:10Z

Hi Jaroslav,

I was wondering if you had time to look at the files I sent?

Thanks,

Re: Modbus Master/ Slave TCP comminication

2016-10-18T09:51:10Z

Hi,

I did a basic setup to test, see attached.
test_master_task.mdl test_master_exec.mdl test_master_cfg.rio

Thanks,

Re: Modbus Master/ Slave TCP comminication

2016-10-17T13:06:49Z

Hi Hendrik,
can you please upload the source .mdl and .rio files?

Jaroslav

Re: Modbus Master/ Slave TCP comminication

2016-10-17T10:46:56Z

apologies, I forgot to mention that I have used the correct register (inReg) but still have no connection (MODBUS MASTER TCP main: item "" timeout)

Thanks,

Re: Modbus Master/ Slave TCP comminication

2016-10-17T04:48:49Z

Hi Hendrik,
in REX the registers are numbered from zero, i.e. 40001 is equal to register 0, type Register 16-bit, 30001 equals to register 0, type InReg 16-bit.

Hope this helps, have a nice day!

Jaroslav

Modbus Master/ Slave TCP comminication

2016-10-16T12:13:11Z

Hi,

I am having trouble sending data from slave to master (Master= REX/Unipi) but I have no issue sending data from Master to slave. The slave device has no "built in" Modbus TCP communications, but is flexible which means I can sent messages using ASCII, HEX or decimal over Modbus (UDP or TCP). I am using holding registers (holding registers = 40001, etc) to write to the slave device and it works fine.

The problem is that I cannot seem to establish a connection when sending data from slave to the master. See attached.

I am not sure what the problem could be?