Question regarding 16385 register

 Hello,

bkomar

Hello.
Did you resolve your problem with Legrand's module? I've exactly the same hardware configuration as u mentioned and I faced the same problem with access to 16385 register.

 you can try use extended range addressing what is f.ex. for Holding register range of 400001-465535 what can be used for register value 16385. In case you need read Holding register , your Destination value for master block is 400001+16385 => 416386.

 Hello,

bkomar

Thanks for quick answer Ivan.
As far as I understood you mention a solution for access for holding registers.That 16385 register is from discrete inputs so the function code will be 02, not 04. 
Should it work also with 02 register group?   

I added an attachment with register map to better illustrate that problem.

 this can depends to your TIA version used so I recommend download your TIA version system manual and check MB_MASTER or Modbus_Master blocks help where table is desxcribed with ranges about specific <register>. In case you don't have this option, you need only create own driver, no other way. Pls come here with your findings...

Hello,

if you look at my attachment (here for TIA v16) you can see definitelly results - you can. Range is to also from 10001 to 19999 if I see correctly, sry for previous answer.

Hello,

ok, I probbaly now think that some missunderstanding is here - from my side. If your mentioned address is right value of register (is higher that standard range 9999 max) then answer is no, you can't read with FC02 in case of register 16385. Apologize for my missunderstanding if this is the right idea. In this case as I said previously only own driver is one correct way.

Update: what is inside world, companies with HW development add ranges for their data and SW need to be updated to this requirements as soon as possible. Sometimes complete change of driver is required or own build. Now Siemens addressing system can put some confuson and mistake therefore I started think that maybe your mentioned address is real address not that as is inside Siemens table. Simply we need pay attention to this difference what can do really mistakes and missunderstandings often...

Hello,

thnx for confirm that problematic address. Solution can be also use of some Gateway that translate Modbus TCP to RTU (your S7-1200 can be simply Client over Modbus TCP and at other side of gateway Modbus RTU 485) and maybe with other FC in this case but problem can be if your Slave device can support specific FC, sometimes this isn't possible. Look for sure to your TIA version again but to MB_CLIENT if some higher FC (MODE) is supported with higher address for DI. Hope you'll be lucky with some info or solution, no problem with next questions.