Specifies the result of invoking method.
Namespace: com.gigatms.parameters
Assembly: GIGATMS.UHF (in GIGATMS.UHF.dll) Version: 2.6.0.0 (2.6.0.0)
Syntax
Members
Member name | Value | Description | |
---|---|---|---|
ERR_SUCCESS | 0 | Request command completed successfully | |
ERR_UNKNOWN | 255 | Unknown error | |
ERR_OUT_OF_MEMORY | 254 | No available memory to process request command | |
ERR_BUSY | 253 | Command was rejected by the device, this could be caused by the device is busy in processing the previous command. | |
ERR_IO | 252 | The inputs/outpus of device occurs an unexcepted error that cannot be handled by device. | |
ERR_TIMEOUT | 251 | Cannot get reply command for a specified period of seconds. | |
ERR_REQUEST | 250 | The request command is not supported by device. | |
ERR_NO_MESSAGE | 249 | Cannot get message data from device. | |
ERR_PARAMETER | 248 | The reply data is invalid or cannot parse correctly. | |
ERR_PROTOCOL | 247 | The command format is invalid. | |
ERR_PROTOCOL_CRC | 246 | The CRC caculation error is detected. | |
ERR_CHIP_NORESP | 240 | RF Chip doesn't respond to MCU (Timeout). | |
ERR_CHIP_HEADER | 239 | Header Bit=1. | |
ERR_CHIP_PREAMBLE | 238 | Signals to MCU that there was an error during preamble detection or FIFO overflow happened during reception or transmission. | |
ERR_CHIP_RXCOUNT | 237 | Signals the MCU that the reception was shorter than expected or an error caused by a disabled command or protocol violation was observed during reception. | |
ERR_CHIP_CRC | 236 | Tag reply CRC error. | |
ERR_CHIP_FIFO | 235 | A fifo underflow IRQ is not produced. | |
ERR_CHIP_REFLECTED_POWER | 234 | Chip reflected power error. | |
ERR_CHIP_BUS_PINS | 233 | Data bus interface pins not working. | |
ERR_CHIP_ENABLE_PIN | 232 | The enable pin is not working. | |
ERR_CHIP_CRYSTAL | 231 | Crystal is not stable. | |
ERR_CHIP_LOCK_PLL | 230 | PLL is not locked. | |
ERR_CHIP_RF_POWER_OFF | 229 | RF Power is Off. | |
ERR_GEN2_SELECT | 223 | Error when selecting tag. | |
ERR_GEN2_ACCESS | 222 | Error on sending access password. | |
ERR_GEN2_REQRN | 221 | Error on sending ReqRN. | |
ERR_GEN2_CHANNEL_TIMEOUT | 220 | Error on RF channel timed out. | |
ERR_GEN2_PC_LENGTH_ERROR | 219 | Error on EPC Length. | |
ERR_GEN2_WRITE_CHECK_ERROR | 218 | Error on writing tag data. | |
ERR_GEN2_HANDLE_ERROR | 217 | Error on getting tag handle. | |
ERR_GEN2_ACK_NO_EPC | 216 | After ACK command the tag no reply EPC. | |
ERR_GEN2_NOT_COVERED | 128 | Catch-all for errors not covered by other codes. | |
ERR_GEN2_NO_SUPPORTED | 129 | The Tag does not support the specified parameters or feature. | |
ERR_GEN2_PRIVILEGES | 130 | The Interrogator did not authenticate itself with sufficient privileg-es for the Tag to perform the operation. | |
ERR_GEN2_MEMORY_OVERRUN | 131 | The Tag memory location does not exist, is too small, or the Tag does not support the specified EPC length. | |
ERR_GEN2_MEMORY_LOCK | 132 | The Tag memory location is locked or permalocked and is either not writeable or not readable. | |
ERR_GEN2_CRYPTO | 133 | Catch-all for errors specified by the cryptographic suite. | |
ERR_GEN2_NOT_ENCAPSULATED | 134 | Command not encapsulated The Interrogator did not encapsulate the command in an AuthComm or SecureComm as required. | |
ERR_GEN2_BUFFER_OVERFLOW | 135 | The operation failed because the ResponseBuffer overflowed. | |
ERR_GEN2_SECUREITY_TIMEOUT | 136 | The command failed because the Tag is in a security timeout. | |
ERR_GEN2_ERROR_NO_POWER | 139 | The Tag has insufficient power to perform the operation. | |
ERR_GEN2_ERROR_UNKNOWN | 143 | The Tag does not support error-specific codes. | |
ERR_TAG_INVALID_PASSWORD | 144 | The password is incorrect – tag is not open. The IDS custom password protection is active. | |
ERR_TAG_BATTERY | 146 | The battery measurement can not be started. The tag is fully passive and there is no battery attached. | |
ERR_TAG_INVALID_COMMAND | 147 | Command is not allowed in active state. Custom commands that can modify logging and calibration parameters are not allowed | |
ERR_TAG_EEPROM_BUSY | 150 | The memory can not be accessed as the measurement unit or SPI is accessing the EEPROM. This error is reported when the EEPROM. |
See Also
Reference
com.gigatms.parametersErrorCode