Each Quality Audit table entry is now able to be configured with instructions that can be displayed in the Quality Audit window, once triggered.

If the Instructions are populated on a Parent Record that contains the trigger, these instructions are assumed to pertain to all of the child entries. These are labeled "General Window Instructions". Each Child record of the trigger can contain their own instructions. They are displayed seperately when the child is displayed. These are labeled "Specific Request Instructions".

If a Quality Audit is triggered directly (has no children) and has instructions, its instructions will be displayed as "Specific Request Instructions"

During record test, if enabled, the record address and header of each record will be dumped to the Debug Output.

Enabling the debug output is enabled by typing "Display Records" and pressing enter while using FlashWizard. A shortcut, "D RE" can be used as well.

There was a race condition between deleteing records from Eclipse and Quality Audit trigger conditions.

When records were deleted from Eclipse, they were just marked as deleted but the Quality Audit triggers were not deleted until the marked Custom List records were deleted. If a trigger condition would occur, the Marked Custom List records would be displayed.

This was resolved by modifying the Marked Records function to call a new method that can be overriden in each record type. If a records gets Marked, it will call this new method and the record can then do other operations at the same time that are specific to itself.

The Custom List records where modified to Mark their QA Trigger recrods as deleted when they themselves get marked.

A new record chain of Custom List records has been created for Eclipse to use in a dynamic interactive way.

Expected operation is that Eclipse will delete the prior list, just in case a prior interaction never got triggered and fully completed. The controller will actually do this for Eclipse if there are no communication errors and the triggered list is fully completed by the operator before power is cycled.

Eclipse will create the list and create the trigger, type 13, that this new list requires. When the chain is unlocked, the new list will be triggered and displayed.

The new trigger has all of the same features for halting the line, allowing overrides etc as the existing Custom List Quality Audit triggers.

Trigger type 13 is not compatible with the Original Custom List chain and the existing trigger types are not compatible with the new Dynamic Custom List chain. Any attempt to use incompattible trigger types will result in a non-response from the XL.

The Hole queue for Inputs 23 or 24 can now be dumped to the Dubug window in the PC simulation or to FlashWizard on the hardware.

The debug instructions are displayed as such: Dump <"Hole> <23 or 24> Dump Hole Queue for input 23 or 24

To dump the hole queue for input 24 the command is: Dump Hole 24

Make sure to press enter.

The asterisc show where the commands can be shortened. Whire space is ignored. The command can be shortened to: duh 24

The command will print the number of holes in the queue and, for each hole, the position from the leading edge of the material.

The Specific example this was found for was an XL206CLFP with switch 80-0. Press five had a Press Reaction time and no other presses did. If the P option was not present, the parameter would not be present.

This was tracked down to some code that was trying to ensure the Printer Press would have a reaction time. However, it was implemented incorrectly.

The logic was corrected and simplified, which rectified the issue.

The Initialize data had encroached into the Heap memory start location so a remap was required.