SynqNet Performance Compatibility

For 16 kHz drives (the majority of SynqNet nodes), the new scheduling algorithm (introduced in the 03.04.00 software release) results in control latency times identical to previous MPI releases. For drive update rates other than 16 kHz, and for non-periodic nodes (RMBs), control latency may change.

Since a change in control latency may affect performance, special attention is recommended for the following node types when upgrading from previous MPI releases.


Drive Update Rates other than 16 kHz

For systems upgrading from MPI releases prior to the 03.04.00, certain drives deserve special attention due to possible changes to control latency. These are all drives with driveFrequency other than 16 kHz:


For these drives, it may be best to review drive tuning and performance using the new control latency. In some cases, the MPISqNodeConfigControlLatency.minimum setting may allow the new system to match (or at least approach) the previous control latency.


Improved Control Latency

RMB-10V2, Trust Automation, Soonhan nodes and other nodes without a drivePeriod requirement will have control latency reduced from MPI releases prior to the 03.04.00. Previously, these nodes used a default 62.5 uS period when scheduling control latency. As of 03.04.00, these nodes no longer round up control latency and schedule the minimum possible time, based on controller and network delays. This change in latency may affect tuning and performance. If necessary, use the MinControlLatency setting to match previous control latency, thus avoiding the need to review tuning and performance.


See Also:

Node Control Latency | Cable Length Discovery Uncertainty Factor | Confirming SynqNet Control Latency


       Legal Notice  |  Tech Email  |  Feedback
Copyright ©
2001-2010 Motion Engineering