1. Two additional Item User Fields were added.
2. Two User Fields were added to each coil record. Elclipse Uart Commands were added to allow the user fields to be set.
3. A print macro was added to allow the coil user field to be printed on Bundle tags or the part.
4. The Coil User Fields can be viewed by pressing the F6 key in the Production Coil screen. The user fields for the selected coil will be didplayed.
5. The Title Headers for the new Coil User Fields can be programmed via Eclipse Uart Commands.

XL200H, XL202H, XL206H and XL212H OPEN LOOP controllers are now capable of operating in Feed to Stop mode.

The DSP exception reporting was modified due to recent DSP communication errors related to Ethernet Communications.

Before any data is attempted to be read or written to or from the DSP, the DSP interface port is tested to see if it is reporting an Exception.

The DSP documentation recomends against allowing the compiler to generate Nested Hardware Do loops. This feature was disabled in the project compiler settings.

The following example could be used to duplicate the issue on a private network.

PC has DHCP enabled with an alternate static configuration PC Ip address: 192.168.1.2 PC Subnet Mask: 255.255.0.0 PC Gateway 0.0.0.0 XL IP: 192.168.2.1 XL Subnet Mask: 255.255.255.0 XL Gateway 0.0.0.0

Due to the PC's subnet mask the PC believed the XL was on its alternate address subnet. The XL believed traffic from the PC was from outside of its subnet and so it used its invalid Gateway IP to route traffic back. Eventually the DSP, which contains the ethernet stack, stopped responding to the 80386 and the controller reset with a task error 0x8F0000E.

If the XL subnet was edited so that the invalid gateway was no longer used, the task errors could no longer be duplicated.

The DSP ethernet stack was modified to test the validity of the gataway before responding to traffic not on its subnet. The XL will no longer respond or attempt to resolve routes to IP addresses not in its subnet unless it has a gateway address that is also on its subnet.

Based on internal request, the default value for the Eclipse Source setup has been changed to Ethernet.

Based on internal request the MODBUS communication defaults were changed to 38400 Baud, No Parity, 1 stop bit, config address 0

Mueller asked for an option that allways deletes the coil from inventory on a tailout. They have issues with operators selecting old coils from the controller inventoy, just to get running. The operators are not answering the Completed or Return to Inventory question correctly.

They asked that we don't even ask the question about Completed or Returned but this is 1) not generic and 2) seemed unsafe for their system. We are not sure that their system could handle a controller using a coil that had been reported as completed.

We decided that the real problem is the coils that are being left in the coil inventory. We added the Remote option to the Yes and No options. Remote works the same as Yes except that the controller will only have the currently loaded coil in its inventory. In addition, the operators are forced to answer the Completed or Return to Inventory question. This is required because the coil is going to be deleted and we need them tell us how to report the coil to Eclipse.