[Imported] Scadapack 357, Telepace Studio, OMNI flow, as Slave


[Imported] Scadapack 357, Telepace Studio, OMNI flow, as Slave

>>Message imported from previous forum - Category:SCADAPack RTU<<
User: mchartrand, originally posted: 2018-10-25 14:45:46 Id:215
This is a re-posting from the obsoleted (October 2018) "Schneider Electric Telemetry & SCADA" forum.


I have a 357, using Telepace Studio, being a slave and an OMNI Flow computer as Master.
I am seeing the send/receive lights flicker, bit to seeing any data into my mapped registers.
Here's what I see with Modsim:


Seems pretty straight forward.
The modbus registers you're using aren't valid for the slave device...
Not surprising when you're trying to access holding register address 44410.. I.e. HR 444411
6digit Modbus addressing is not very common

You should read up more on Modbus 🙂


Now I am confused. The ScadaPack is the slave, using registers 44410 as a start. The OMNI is the Master trying to send the ScadaPack, as slave, the registers.
No idea about the "6 digit modbus" comment.
OMNI is sending 44410 to me at 44411. I have 44400 to 44450 open to receive the writes from the OMNI.
Part of the issue is that the OMNI is not ours and I can't tinker on that side._**


Read some more about Modbus
[http://www.simplymodbus.ca/FAQ.htm](http://www.simplymodbus.ca/FAQ.htm "http://www.simplymodbus.ca/FAQ.htm")

Look at the addresses you sent in your 'Master' frame.

It appears the OMNI is misconfigured.


The beloved OMNI flow computer, when posed with the 16 function code to write multiple variable, implies the 40000, thus all the OMNI as the master only has to designate the last four digits._**

Attached file: (editor/xy/l39jylr5rh7u.pdf), Master.pdf File size: 20340

Attached file: (editor/vm/tpobxg2ipvt8.pdf), Slave.pdf File size: 14291