Wen trying to read the program out of some USC modules errors such as

• "xtValue" cannot be zero length and
• divide by zero occur.

In many versions of USC Config the import process would also stop when the first error of this type occurred preventing the user from reading the program.

USC Config 105 and 106 have both been modified to report the address of the error and continue importing the program. If originally programmed by "USC Config 105" or "USC Config 106" then in 99.9% of cases the imported program will contain 100% of the original function.

Why Do These Errors Occur

Most USC programs use about 20% of the available user memory, therefore when programming much of USC memory is not written to.

When reading programs out of the USC most of the memory is read by "USC Config 105/106" onto the PC hard drive and then decoded into the data type for that address.

It is during this data conversion process that the errors are reported. After the data is converted the original USC module definition is reconstructed. The reconstruction process will follow a flow chart of sorts and only rebuild data that is actually used.

What Is APCS Doing About This Problem

Both "USC Config 105" and "USC Config 106" have been modified to report the address of errors and continue reading the USC.
The user can inspect the USC module definition to ensure it is correct or program a second module and test function.
The user can fax the address of the error message to APCS, we can determine the function of that memory and advise the user who will confirm that that function was never used in the original program.
Obviously this problem is rare however to prevent it occurring on future production APCS will dump a dummy map of correct data types in all user memory before programming with the standard or user program.