Wi.232FHSS-25-R Radiotronix, Wi.232FHSS-25-R Datasheet - Page 18
![RF Modules & Development Tools 900MHz FHSS Low Power Transceiver](/photos/15/97/159757/landingpageradiotronixwifreestar232dtsstandup_sml.jpg)
Wi.232FHSS-25-R
Manufacturer Part Number
Wi.232FHSS-25-R
Description
RF Modules & Development Tools 900MHz FHSS Low Power Transceiver
Manufacturer
Radiotronix
Datasheet
1.WI.232FHSS-25-FCC-RA-R.pdf
(67 pages)
Specifications of Wi.232FHSS-25-R
Lead Free Status / RoHS Status
Lead free / RoHS Compliant
Other names
WI232FHSS-25-R
WI.232FHSS-25-R/ WI.232FHSS-250-R DATASHEET
2.5. Exception Engine
Wi.232FHSS modules are equipped with an internal exception engine. When errors occur during module
operation, an exception is raised. Exception codes are stored in the
occur, and cleared once they are read. If an exception code is already present in
following an error, the new exception code will overwrite the old value.
network, impeding valid communications. Assured delivery is enabled by setting bit 4 of
regNETWORKMODE.
Should the address information match exactly, the receiving module will immediately send an RF ACK
packet. This packet lets the sending module know that the message has been received. An RF ACK packet
is made up of 7 bytes of overhead, and is sent immediately following reception; CSMA delay is not applied to
RF ACK packets. When the sending module receives the RF ACK packet, it will mark the current block of
data as completed and update its buffer pointers. If this is the last message in the queue, the sending
module will assert the BE pin to indicate the state of the incoming buffer.
Troubleshooting Hint: Communications Problems. If you are unable to communicate with another module,
it is most likely caused by one of the following. First, check to make sure that you are using the same data
rate. Modules programmed with different data rates will not communicate nor share the RF channel with one
another. Second, ensure that your network mode and addressing is configured to properly access the
module of interest. Also, ensure that you are addressing a specific module when using acknowledgment.
Failure to do so will cause large delays and loss of data.
2.5.1. Exception Codes
Exception codes are organized by type for ease of masking (see Exception Masking). The following table
lists the exception codes and their meanings. All other values are reserved.
Table 5, Exception Codes
2.5.2. Exception Masking
Wi.232FHSS modules have an external pin, EX, that can be asserted to indicate to the host that an error has
occurred. The exception mask provides a simple method of discriminating which errors cause the EX pin to
toggle. If the exception code, once ANDed with the exception mask (regEXCEPTIONMASK), is non-zero,
the EX pin is asserted. Once the EX pin is asserted, the
low. The following table lists some example exception masks.
It is important to note that the exception mask has no effect on the exceptions stored in the exception
register. The exception mask only controls which exceptions affect the EX pin.
Exception Code
0x08
0x09
0x13
0x20
0x40
0x42
0x43
0x44
Exception Name
EX_BUFOVFL
EX_RFOVFL
EX_WRITEREGFAILED
EX_NORFACK
EX_BADCRC
EX_BADHEADER
EX_BADSEQID
EX_BADFRAMETYPE
17
Description
Internal UART buffers overflowed
Internal RF packet buffer overflowed
Attempted write to register failed
Acknowledgement packet not received after maximum
number of retries
Bad CRC detected on incoming packet
Bad CRC detected in packet header
Sequence ID was incorrect in ACK packet
Unsupported frame type specified
regEXCEPTION
regEXCEPTION
register must be read to return it to
regEXCEPTION
register when they
Revision 1.1.0