Here’s what more than 2,500 business decision-makers around the world say.Download the report
...with the Facility Hero app in hand! Discover how you can optimize your maintenance efforts today.Learn more
Access tailored services, 24/7 self-service and expert help. Anywhere, anytime, any project.Discover now
Everything you need to know about our IoT technology backbone.Learn more
Explore our global offerings or select your country from one of our five regions.Global
Découvrez nos offres globales ou sélectionnez votre pays dans l’une de nos cinq régions.
Because the Momentum is a single CPU device and cannot off-load tasks to a backplane, the CPU must singularly read inputs, solve logic, write outputs, check logic CRC and service communications.
There is a difference if the communications requests are sourced at the Momentum (as a ModbusTCP client), or serviced as a response to a client (as a ModbusTCP server). Factor 3 Momentum CPU scans for client requests such as MSTR or IO Scanner requests.
This is because it will take 1 CPU scan to open a TCP connection to the destination server, another CPU scan to send the request, and a third CPU scan to process the response. This does not factor in the CPU servicing of the destination module should it have similar logic tasks to perform with modules serviced at the end of User Logic CPU scan.
Sign up for all the latest solutions, offers and best practices straight to your inbox.
We are excited that you have joined the group. You will receive your welcome email soon describing the program and what to expect in the upcoming weeks. Enjoy!