Error Code List

Error Codes

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

These codes are thrown as Phidget Exceptions or returned as error codes from C functions. See the Phidget22 API documentation for your device to see which error codes are supported. The error codes are generic, and the error description may contain more detailed information about the actual cause of the error.

Value Legend
Hex: Hexadecimal	Dec: Decimal	LV: LabVIEW

Name	Value	Description	Details
OK	Hex: 0x00 Dec: 0 LV: 0	Success
PERM	Hex: 0x01 Dec: 1 LV: 7001	Not Permitted
NOENT	Hex: 0x02 Dec: 2 LV: 7002	No Such Entity
TIMEOUT	Hex: 0x03 Dec: 3 LV: 7003	Timed Out	This can happen for a number of common reasons: Check that the Phidget you are trying to open is plugged in, and that the addressing parameters have been specified correctly. Check that the Phidget is not already open in another program, such as the Phidget Control Panel, or another program you are developing. If your Phidget has a plug or terminal block for external power, ensure it is plugged in and powered. If you are using remote Phidgets, ensure that your computer can access the remote Phidgets using the Phidget Control Panel. If you are using remote Phidgets, ensure you have enabled Server Discovery or added the server corresponding to the Phidget you are trying to open. If you are using Network Server Discovery, try extending the timeout to allow more time for the server to be discovered.
KEEPALIVE	Hex: 0x3A Dec: 58 LV: 7058	Keep Alive Failure
INTERRUPTED	0Hex: 0x04 Dec: 4 LV: 7004	Op Interrupted
IO	Hex: 0x05 Dec: 5 LV: 7005	IO Issue
NOMEMORY	Hex: 0x06 Dec: 6 LV: 7006	Memory Issue
ACCESS	Hex: 0x07 Dec: 7 LV: 7007	Access (Permission) Issue
FAULT	Hex: 0x08 Dec: 8 LV: 7008	Address Issue
BUSY	Hex: 0x09 Dec: 9 LV: 7009	Resource Busy	The Phidget you are trying to open is already open elsewhere. Check that the Phidget is not already open in another program, such as the Phidget Control Panel, or another program you are developing. Check that the addressing parameters have been specified correctly.
EXIST	Hex: 0x0a Dec: 10 LV: 7010	Object Exists
NOTDIR	Hex: 0x0b Dec: 11 LV: 7011	Object is not a directory
ISDIR	Hex: 0x0c Dec: 12 LV: 7012	Object is a directory
INVALID	Hex: 0x0d Dec: 13 LV: 7013	Invalid
NFILE	Hex: 0x0e Dec: 14 LV: 7014	Too many open files in system
MFILE	Hex: 0x0f Dec: 15 LV: 7015	Too many open files
NOSPC	Hex: 0x10 Dec: 16 LV: 7016	Not enough space
FBIG	Hex: 0x11 Dec: 17 LV: 7017	File too Big
ROFS	Hex: 0x12 Dec: 18 LV: 7018	Read Only Filesystem
RO	Hex: 0x13 Dec: 19 LV: 7019	Read Only Object
UNSUPPORTED	Hex: 0x14 Dec: 20 LV: 7020	Operation Not Supported	This error is thrown when a method is called that is not supported by the Phidget hardware. For example, calling setFanMode on the 1065, which has no fan. Or calling setEnabled on an encoder channel that is always enabled, like the one built in to the DCC1002.
INVALIDARG	Hex: 0x15 Dec: 21 LV: 7021	Invalid Argument	One or more of the parameters passed to the function is not accepted by the channel in its current configuration. This may also be an indication that a NULL pointer was passed where a valid pointer is required.
AGAIN	Hex: 0x16 Dec: 22 LV: 7022	Try again
NOTEMPTY	Hex: 0x1a Dec: 26 LV: 7026	Not Empty
UNEXPECTED	Hex: 0x1c Dec: 28 LV: 7028	Unexpected Error
DUPLICATE	Hex: 0x1b Dec: 27 LV: 7027	Duplicate
BADPASSWORD	Hex: 0x25 Dec: 37 LV: 7037	Bad Credential
NETUNAVAIL	Hex: 0x2d Dec: 45 LV: 7045	Network Unavailable
CONNREF	Hex: 0x23 Dec: 35 LV: 7035	Connection Refused
CONNRESET	Hex: 0x2e Dec: 46 LV: 7046	Connection Reset
HOSTUNREACH	Hex: 0x30 Dec: 48 LV: 7048	No route to host
NODEV	Hex: 0x28 Dec: 40 LV: 7040	No Such Device
WRONGDEVICE	Hex: 0x32 Dec: 50 LV: 7050	Wrong Device
PIPE	Hex: 0x29 Dec: 41 LV: 7041	Broken Pipe
RESOLV	Hex: 0x2c Dec: 44 LV: 7044	Name Resolution Failure
UNKNOWNVAL	Hex: 0x33 Dec: 51 LV: 7051	Unknown or Invalid Value
NOTATTACHED	Hex: 0x34 Dec: 52 LV: 7052	Device not Attached	This can happen for a number of common reasons: Be sure you are opening the channel before trying to use it. If you are opening the channel, the program may not be waiting for the channel to be attached. If possible use openWaitForAttachment. Otherwise, be sure to check the Attached property of the channel before trying to use it.
INVALIDPACKET	Hex: 0x35 Dec: 53 LV: 7053	Invalid or Unexpected Packet
2BIG	Hex: 0x36 Dec: 54 LV: 7054	Argument List Too Long
BADVERSION	Hex: 0x37 Dec: 55 LV: 7055	Bad Version	This error occurs when the version of the Phidget libraries is different than the one being used on the network server. Update both to the latest version to solve the error. If you're using Javascript, ensure that the same version of phidget22.min.js is being used in your working directory as the one being pointed to by the webserver in the Phidget Control Panel.
CLOSED	Hex: 0x38 Dec: 56 LV: 7056	Closed
NOTCONFIGURED	Hex: 0x39 Dec: 57 LV: 7057	Not Configured
EOF	Hex: 0x1f Dec: 31 LV: 7031	End of File
FAILSAFE	Hex: 0x3b Dec: 59 LV: 7059	Failsafe Triggered	Failsafe Triggered on this channel. Close and Re-open the channel to resume operation.