Recommended SAP Sequence for Targets with Trim
This tip concerns PEmicro's Cyclone automated programmers. We've noticed that on rare occasions some users have observed that although a "PT" (program trim) command has been specified in the SAP programming sequence, the trim value is not programmed. By working closely with Cyclone users, we've discovered that the issue is not that the Cyclone receives the command and fails to program the trim value to the target, but rather the PT operation was accidentally pre-empted by the user. How could this happen if the operation is configured in the Cyclone and all a user needs to do is wait for the operations to finish? The problem lies in the "wait for the operations to finish" portion of the sequence. A stand-alone operation typically uses the following sequence: with PT being the last command in the sequence. In a labor-intensive manual production environment, it is possible that a user may mistakenly terminate the sequence when he sees the "verification" LED or LCD display, thus ending the operation prematurely, when in fact there is one more "PT" command yet to be executed. To remedy this potential issue we recommend a slightly modified SAP sequence, which will not affect anything under normal conditions, but will help prevent human error. The sequence is as follows: As you can see, the "PT" command now occurs before the verifications begins. By putting the "PT" command ahead of the "PM" command, it also becomes an extra check for the trim value... if a valid trim value is not calculated, the Cyclone will not program the target.CM algorithm_file
SS user_srecord
EM
BM
PM
VM
VC
PT
CM algorithm_file
SS user_srecord
EM
BM
PT
PM
VM
VC