Tech Support | BPM Microsystems
BPM Microsystems go login
Products Software Support About BPM Micro
Technical Support
Header Downloads
none

Empty Socket Test - Explanation

Summary
A detailed explanation of the Empty Socket Test Option. (NOTE: This option was removed from BPWin beginning with V5.5)

Details
During an automated programming system job run, there can be the occasional mis-pick or mis-placement of a device during handling. The error message for a mis-placement is ALWAYS to correct the device placement. The error message for a mis-pick is ALWAYS to manually remove the device and discard. And here is where a problem can occur. Due to factors such as poor operator training, or inattention, the operator can neglect to remove a mis-pick from a programming socket. If this occurs, and the devices are reprogrammable, then a double stack can occur in the socket, where the bottom device is reprogrammed, and top, blank device gets moved to the output.

The Empty Socket Test was created just for this purpose - when the operator fails to do what is required.

The value for this option will determine how often each programming site will perform a continuity test. We recommend a minimum value of 5. This means that after 5 programming cycles on each site, that site will perform a continuity test. The programming cycles can be passes or failures, and when every fifth device is removed, the site will perform a continuity test. If a device is detected in any socket, anytime throughout the job, the job will be terminated with an error message, stating that a device was detected in a socket that was supposed to be empty.

The logical urge is to set this value to 1 so that if a device is accidentally left in a socket, it will be detected quickly. Although this is true, there are some negative consequences with using a value of 1.
First, you will loose throughput. Devices per hour will decrease due to the added time is takes to perform the continuity test. This decrease can be substantial.
Second, the site stepper motors will be worked twice as often, which will wear the motors out twice as fast. Replacing the motors require removing the sites, and site removal requires re-teaching.

The reason that we recommend a value of 5 (or 10) is to reduce the drop in devices per hour, and to save wear and tear on the site stepper motors.
Should a failure ever occur, simply rerun the programmed devices in Verify mode to find the blanks.

Again, this option was created to compensate for operator error.

This option works for all socket modules, including FX4.


For further information, please click here


Last Modified: 03/01/2011