Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel

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

Remote Operations Forum

Collaborate and share knowledge on the extensive range of remote systems and devices, including SCADA radios and RTUs, on the Schneider Electric Exchange Remote Operations (formerly SCADA & Telemetry) forum. From commissioning SCADA integration devices and software, to enhancing existing installations or troubleshooting, connect with a global community of experts and users. Subscribe today.

Janeway Janeway

[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