Technical FAQs

Ask a Question

What is the ModbusTCP response time from a Momentum?

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.

Was this helpful?
What can we do to improve the information ?