| ModuleAPI C# Version Developer's Guide |
|
MODULELIBRARY
The reader may have an abnormal situation during the working process, and the physical communication link between the reader and the external system where the problem occurs most. No matter what happens, the system needs to be detected in time. Tag operations such as read, write, lock, and destroy may also fail. These situations are thrown by an instance of the exception class, prompting the upper system.
ModuleException Class
The base class of other exception classes
| Member | Description |
|---|---|
| ErrCode | Error code |
OpFaidedException Class
Non-fatal error, this means operation fails.
HardwareAlertException Class
When reader detects any condition that may cause damage to hardware this exception would be threw. The actions that possibly cause damage to hardware are as following.
- Transmit power through a port without antenna connection.
- High temperature of environment.
- Antennas stay too close to metal plate when the reader is reading tags, if the transmit power is very great it would be highly possible that lots of power is reflected into reader through antennas and cause damage.
Therefore, when detecting these error users should let the reader stop working and check whether there is any kind of maloperation above.