Error Event Code List

Error Event Codes

This page lists all error event codes with more in-depth descriptions than can be found in the Phidget22 API.

These codes are passed to an error event handler. See the Phidget22 API documentation for your device to see which error event codes are supported. The error event codes are generic, and the error description passed to the error event handler may contain more detailed information about the actual cause of the error event.

BADVERSION

Version Mismatch Error. Usually means client and server library versions are out of sync. Update to the latest version of the Phidget software.

BUSY

The Phidget device channel has already been locally attached. Only one channel may attach locally to a device channel.

NETWORK

An error occurred with the network communications. See the error description for more details.

DISPATCH

An error occurred when trying to dispatch an event. It's possible that the data rate is too fast for the computer (or network) and the event queue has filled up.

OK

An error state has ended. You can use the getDescription method of the error event to get more information.

OVERRUN

Sampling overrun. Some samples were lost in firmware because the queue filled up. This error is exclusive to Phidget InterfaceKits.

PACKETLOST

Packet(s) were lost. This error is often an indication that your event handlers are not executing fast enough. Try to remove slow processes like GUI updates or user input from your handlers.

WRAP

A variable has wrapped. For example, the encoder position can wrap from 2,147,483,647 to -2,147,483,648 because of an integer overflow.

OVERTEMP

Over-Temperature condition detected. See error description for more details.

OVERCURRENT

Over-Current condition detected. See error description for more details.

OUTOFRANGE

Out of range condition detected. Usually an input on the board is reporting a value that is outside of the allowed range.

BADPOWER

Power supply problem detected. Either the power supply is being overloaded, or it is under-powered (possibly not plugged in).

SATURATION

A sensor's value has reached the maximum or minimum of its sensing range. For example, a 1000 lux light sensor will throw this error event when a value greater than 1000 lux is detected. The sensor will still be reporting 1000 lux, but this error tells you that you don't know for certain how much higher than 1000 the real reading is.

OVERVOLTAGE

Over-Voltage condition detected. Occurs in power-providing Phidgets when the output voltage exceeds the set value.

VOLTAGEERROR

A voltage error occurs when a Phidget that provides a voltage output has the value drop below what what specified. This can happen if the device being powered draws too much current, which causes a voltage drop. Stay within output current specifications to avoid voltage errors.

ENERGYDUMP

An energy dump occurs when a power-providing Phidget needs to dissipate its extra energy. See the User Guide for your device for more information.