The nRF905 is a wireless transceiver IC similar to the nRF24L01, but with a working frequency of 433/898/915MHz, offering a longer range and more IO pins. Although the data rate of nRF905 is only 50Kbps, lower than the 2Mbps of nRF24L01, this library provides considerable flexibility.
The library supports the use of interrupts and allows for the option of connecting two modules, as their status can also be accessed through the IC’s status registers. Additionally, the library supports basic collision avoidance mechanisms.
NOTE: v3.0.0 of the library was released on 12th September 2017, the default CD pin has changed and the AM pin is now used by the library.
Download
Arduino: [HERE] and [Documentation] (or use the Arduino library manager and search for “nrf905”)
AVR (non-Arduino): [HERE] and [Documentation]
| nRF905 | ATmega48/88/168/328 | Arduino Uno | Description |
|---|---|---|---|
| VCC | 3.3V | 3.3V | Power (3.3V) |
| CE | D7 (13) | 7 | Standby – High = TX/RX mode, Low = standby |
| TXE | B1 (15) | 9 | TX or RX mode – High = TX, Low = RX |
| PWR | B0 (14) | 8 | Power-up – High = on, Low = off |
| CD | D4 (6) | 4 | Carrier detect – High when a signal is detected, for collision avoidance |
| AM | D2 (4) | 2 | Address Match – High when receiving a packet that has the same address as the one set for this device, optional since state is stored in register, if interrupts are used (default) then this pin must be connected. |
| DR | D3 (5) | 3 | Data Ready – High when finished transmitting/High when new data received, optional since state is stored in register, if interrupts are used (default) then this pin must be connected. |
| SO | B4 (18) | 12 | SPI MISO (Mega pin 50) |
| SI | B3 (17) | 11 | SPI MOSI (Mega pin 51) |
| SCK | B5 (19) | 13 | SPI SCK (Mega pin 52) |
| CSN | B2 (16) | 10 | SPI SS |
| GND | GND | GND | Ground |
Some of the module pin names differ from the IC pin names in the datasheet:
| Module | IC |
|---|---|
| CE | TRX_EN |
| TXE | TX_EN |
The nRF905 is not 5V compatible, so some level conversions will need to be done with the Arduino outputs. A simple voltage divider or resistor and zener diode will do the trick. Only TXE, CE, PWR, SI, SCK and CSN pins need level conversion (not CD, AM, DR and SO).
| Divider | Zener |
|---|
The nRF905 has 511 channels ranging 422.4MHz – 473.5MHz in 100KHz steps on the 433MHz band and 844.8MHz – 947MHz in 200KHz steps on the 868/915MHz band (remember to check which frequencies are legal in your country!), but each channel overlaps adjacent channels so there are only a total of 170 usable channels at once.
Searching for nRF905, PTR8000 and PTR8000+ should yield some results for modules on AliExpress, Ebay and DealExtreme. You should be able to get 2 for around £10.
Callbacks
Since v3.0.0 this library uses callbacks which are ran when events occur. If the option to use interrupts is enabled then the callbacks will run from the interrupt routine so be sure that any global variables you use in them are declared ‘volatile’, just as you would when dealing with normal ISRs. These events will wake the microcontroller if it is sleeping.
| Event | Callback | Notes |
|---|---|---|
| New packet incoming | NRF905_CB_ADDRMATCH | |
| Valid packet received | NRF905_CB_RXCOMPLETE | |
| Invalid packet received | NRF905_CB_RXINVALID | |
| Packet transmission complete | NRF905_CB_TXCOMPLETE | This only works if the nextMode is NRF905_NEXTMODE_STANDBY when calling nRF905_TX() |
Nitty-gritty radio stuff
The actual air data-rate of nRF905 is 100Kbps, but the data is Manchester encoded which halves the throughput to 50Kbps. The modulation is GFSK with ±50KHz deviation. The radio also adds a few extra bits of data to the address and payload; a preamble and CRC.
Transmitted packet
| Preamble 10 bits | Address 1 or 4 bytes | Payload 1 – 32 bytes | CRC 0 – 2 bytes |
The address is also used as the syncword and should have as many level shifts as possible. 10100110 01100101 00011010 11011010 (2791643866) would be a good address to use, but 00000000 00000000 00000000 0010000 (32) would not be.
The CRC is used to detect errors in the received data. Having a CRC doesn’t eliminate all bad packets, there is always a small chance of a bad packet passing the CRC. Using larger CRCs helps to reduce that chance.
When the CRC is set to 16 bit the radio uses the CRC16-CCITT-FALSE (0xFFFF) algorithm. I’m not sure what it uses for 8 bit CRCs.
Transmission time
The sizes of the address, payload and CRC can be adjusted for a balance between throughput and latency.
Example configurations
| Address size | Payload size | CRC size | = | Throughput (bps) | Latency (ms) |
|---|---|---|---|---|---|
| 4 | 32 | 2 | = | 36940 | 6.93 |
| 1 | 4 | 1 | = | 17680 | 1.81 |
| 1 | 1 | 0 | = | 6838 | 1.17 |
Throughput is how much useful data can be sent (the payload part), assuming no delays for writing and reading the payload.
Latency is how long it takes for the transmission to complete.
Switching from standby mode to receive or transmit mode takes a maximum of 650us and switching between receive and transmit modes takes a maximum of 550us.
Transmission time can be worked out with:
t = tstartup + tpreamble + ((Naddress + Npayload + NCRC) / BR)
tstartup is the time to switch mode as stated above (650us / 550us).
tpreamble is 200us for the 10 bit preamble.
Naddress, Npayload and NCRC are the address, payload and CRC sizes in bits.
BR is the bit rate which is 50,000.
For config 1, switching from standby to transmit:
t = 0.00065 + 0.0002 + ((32 + 256 + 16) / 50000)
t = 0.00693 seconds (6.93ms)
A note to developers: Before v3.0.0 this library would load the address bytes in reverse order, keep that in mind if you’re using an old version of the library to interface with other radio systems!
