QC-Gage Errors by Description (F-Z)
Print Friendly View
written: 02/01/2006
last modified: 03/15/2024

File already exists

Save using a different name or delete the old one


File already open

Close the program (or the QC-Gage Run Screen) that has the file open. You may need to reboot the computer, this error also occurs when the operating system loses track of a file's status.


File not found

Check QC-Gage settings for bad Spec Plan names, output files, etc. You may need to reinstall QC-Gage is a critical system file is missing or damaged


Following baud rate is unsupported on the following device. (Baud rate, Device):

Pick a different Baud rate


Gage not on

Usually from a multiplexor - Turn the gage on, make sure it is connected to the multiplexor, make sure the multiplexor is set to look on the correct channel.


Gage not zeroes

Zero the gage


Hardware detected a break condition.

Consult the manual for the inspection equipment. You can also try rebooting the computer and if the problem persists try a different cable.


Hardware detected a framing error.

The baud rate of the inspection machine may not match the PC, the number of data bits or stop bits may not match, or you may have parity set on one but not the other.


Hardware detected a parity error.

Try using shielded cable or a surge suppresser / noise filter. Make sure the gages and QC-Gage are both set to the same parity settings


I/O error occurred during an attempt to communicate with a parallel device.

Make sure the printer is on and connected properly


Input past end of file

Usually from a corrupt file, if the error persists you may need to reload QC-Gage


Invalid picture

The picture file is an invalid format or has been damaged


Invalid picture type

The picture file is an invalid format or has been damaged


Out of Data

For some gages this may signal the end of collected data, more a warning than an error.


Out of memory

Close one or more programs. You may also need to reboot the computer.


Out of string space

Contact Prolink with the exact circumstances this error occurred under


Parallel device signaled that it is out of paper.

Put paper in the printer, check for loose or damaged cables.


Parallel device was not selected.

Make sure printers are configured correctly


Path not found

You may have deleted a path that QC-Gage needs, or a network drive may not be mounted.


Path/File access error

The file may be open, you may not have sufficient network permissions, or you


Permission denied

The file is already open, close the program (or the QC-Gage Run Screen) that has the file open. You may need to reboot the computer, this error also occurs when the operating system loses track of a file's status. Insufficient network permissions can also cause this error.


Receiving queue overflowed.

The inspection equipment might not obey XOff, the cable's hardware flow control lines (if enabled) might be broken, you might be running at too high a baud rate, or your buffer may be too small for the inspection program you are running.


Requested mode is not supported, or the idComDev parameter is invalid.

Very rare, usually indicates a hardware problem - try a different port.


RLSD (receive-line-signal-detect) time-out.

Make sure hardware flow control is enabled on both machines or disabled on both machines. Check for loose or damaged cables. Make sure the cables are of the correct type


Subscript out of range

Contact Prolink with the exact circumstances this error occurred under


Syntax Error

This error is from the Gage Script Parser - it usually means the Gage script is damaged. Try reloading the gage definition.


Time-out occurred during an attempt to communicate with a parallel device.

Make sure the printer is on and connected properly


Too many files

Close some programs or set your "Buffers" and "Files" settings in your Config.sys to higher numbers


Transmission queue was full when a function attempted to queue a character.

Make sure hardware flow control is enabled on both machines or disabled on both machines. Check for loose or damaged cables. Don't enable both software and hardware flow control. The inspection machine may be ignoring XOffs.


Unrecognized Variable

This error is from the Gage Script Parser - it usually means the Gage script is damaged. Try reloading the gage definition.


Unspecified

Used for gages that do not say what the problem is, the gage manual may list possible problems


User defined

Written by the Gage Script author, look for details in the Connection Notes section of the QC-Gage manual if Prolink wrote the Gage Script and look in your company's procedures if your company wrote the script.


Wrong Channel The expected channel doesn't match the received one

Make sure you select the correct channel on the gage. You may need to ask your Gage Administrator to include instructions about gage channels in the notes for each dimension in your spec plan.


Wrong Units The expected units don't match the received ones

The gage may be set wrong (it may have a inch / mm switch, etc.) or your Gage Administrator may have misspelled the unit abbreviation in the Spec plan.

Applies To

QC-Gage v.4.10
QC-Gage v.3.00
QC-Gage v.1.96
QC-Gage v.1.91

Category

Data Collection
See more articles in this category