Please answer the following questions as completely as you can. We've discovered that the majority of problems require this information to effectively solve your problem. Sometimes problems require additional information. We will contact you if we require additional information.
Please click the button below to request calibration, service & repair:
*Required
PS family: Please export the job file, the programmer event log file, and the TLDebugLog.txt file (i.e. C:\Dataio\TLDebugLog.txt).
RoadRunner/FlashPAK family: Please zip the FDRROOT directory from the job card.
FLX500: Please zip the FDRROOT and also the FLXLog.zip created from the save logs button on the version screen
This information is displayed on the banner screen when the programmer is powered up. It can also be found in the eventlog.txt file of all FlashCORE products.
Please give the date, time and description of what you were doing when you first noticed the problem.
Does the problem occur in a certain pattern?
Please describe the problem you are experiencing.
Here are some examples of what we're looking for: adapter, programmer, display, keypad, host PC (FLX or PS), gantry, probe, etc.
For example, does the problem occur randomly, only when programming, when the machine is idle, or when the user is performing a particular operation
If yes, please give as many details as possible. This will help us reproduce the problem you're experiencing.
Below is a description of where to find your Data I/O serial number for each product family:
PS family: on back below the power/air panel
RoadRunner family: with robotics cover removed, on the casting above the Reject Bin the PNP Head(Pick and Place) may be covering it when placing devices on the belt.
FlashPAK family: on the back of the unit
FLX500: on the communication wall visible when the left tray module is removed
3980xpi: on the back of the unit
TLWin.exe version for all FlashCORE products plus the AH500 version.exp program version for the PS system or the FLX.exe version for the FLX500
If you have made any recent changes, can you please describe them.
If yes, please describe how you are working around the error.
Does the problem occure more often when the user is doing a certain operation or when the machine is idle?
Data I/O Support - Device Programmer Support, Data I/O Flash Programmer Contactt