Release Note
xxx_A102.fpg

Description:
The rxOnOutPort bit may not be valid in the Receive Control Block status word. This does not affect basic operation, but may cause problems with idle cable detection after fault recovery (only if the system has more than 16 nodes). This problem depends on internal FPGA routing delays, and potentially exists in all builds prior version 224. Currently, the problem has only been observed in 223_A301.fpg.

Description:
XMP and eXMP controllers using FPGA versions 221 and 222 always discover cable lengths of 0. The MPI schedule will allow for actual cable lengths between 0 and 10 meters, but longer cables may not work reliably. ZMP controllers are not affected by this bug.

Description:
When fault recovery occurs on a network with 9 or more nodes, excessive upstream packet error counts may be seen for all nodes, or some nodes may fail to recover. The errors occured if a CHANGE packet arrived while the receive FIFO was reset at the begining of the next controller cycle. This problem exists in all FPGAs prior to version 222.

Description:
A debounce filter has been added to all 6 opto inputs of the XMP and ZMP controller designs. The filter delays input changes 140 uS +/– 20 µS, with the delay restarting if the input bounces back to the previous value.

Description:
ZMP controllers may fail network initialization. Typically, the application (Motion Console, reset, etc.) will never complete initialization. For MPI releases prior to 03.01.00, the application halts and never reports an error. The program can be aborted successfully in some cases, while others require a reboot to fully recover. Occasionally, the host computer may hang. For MPI releases 03.01.00 and later, the application will report an error. This problem exits on all ZMP controllers prior to FPGA version 221. XMP controllers are not affected.