Login or create an accountClose
I am a returning customer
Login or create an accountClose
Your Account Has Been Created!
Thank you for registering with TechMaze!
You will be notified by e-mail once your account has been activated by the store owner.
If you have ANY questions about the operation of this online shop, please contact the store owner.
You have been logged off your account. It is now safe to leave the computer.
Your shopping cart has been saved, the items inside it will be restored whenever you log back into your account.
NRF24 SE8R01 Wireless 2.4Ghz modules
- This is a wireless transceiver module that is fully compatible with NRF24L01+. Need be used in pairs, it is easy very convenient to use. It can be applied to the smart car, smart home, wireless remote control. Small size, lightweight, it is especially suitable for industrial applications.
- 126 Channels to support multi-point communications and support frequency hopping to meet the communication needs.
- The maximum transmission rate is 2Mbps, as air transmission time is very short, greatly reducing collision phenomena in wireless transmission (Transfer rate can be set of 500Kbps, 1Mbps or 2Mbps.)
NRF24 the same as the modules with the 8-pin connector except Vcc and Gnd is swapped:
- Vcc (1.8-3.6V)
The next problem was coming up with a way to hook them up to a breadboard. The castellated pads use a half-pitch (1.27mm) spacing, so you can't solder on standard pin headers and plug the module into a breadboard. My solution was to solder 24AWG wire from an ethernet cable to the castellations, and in turn plug those wires into a breadboard.
My initial testing of these modules indicated they did not use Nordic nRF24l01+ chips, or chips that are compatible such as the Beken BK2423 or the SiLabs Si24R1. The most obvious indication that these are not nRF modules ISS that the default pipe0 address (register 0A) is 46 20 88 41 70 instead of E7 E7 E7 E7 E7. They also respond to the bank switch command (0x50, 0x53), which is not supported by the Nordic chip. I sent a message to the vendor asking for a data sheet, and while I waited I tried to figure out what chip the modules use.
Besides Beken and SiLabs, Hoperf makes a compatible module called the RFM70. The RFM70 modules have a pinout that starts with GND, and they have the same default pipe0 address as the nRF. The only other chip I could find that is similar to the nRF24l01 was the NST LT8900 or LT8901. The datasheets for the NST chips didn't match with the register values from my modules.
Surprisingly, less than 24 hours after messaging the seller, I received an attachment containing a datasheet for the Semitek SE8R01. My initial thought that these would inter-operate with nRF modules simply by changing the pipe0 address was disrupted by the discovery that these modules use a slightly different packet format. Section 7.3 of the datasheet shows a 2-byte guard after the address field, just like Bluetooth EDR uses where it switches from GFSK to DPSK.
If these modules use DPSK after the guard byte, then there is no way they will communicate with genuine nRF modules. Another less significant source of incompatibility is that these modules don't have a 250kbps mode; instead, it has a 500kbps mode along with the 1 and 2-Mbps modes. The 250kbps mode on the nRF24l01+ modules is good for extended range since it has 9 dBm better sensitivity than 1mbps (-94 vs -85 dBm). The SE8R01 datasheet indicates -86 dBm sensitivity at both 1mbps and 500kbps, so there would seem to be little reason to use the 500kbps mode.
One benefit to these modules is that they have a received power report in register 09, something the nRF modules don't have. Although the datasheet documents the bank switch command, and how the currently active bank is reported in the status register 0E, there is no documentation of the bank 1 registers.
I also tested the modules to see if they will support packet sizes over 32 bytes. The chip seems to accept a payload length of up to 255 bytes, but the read Rx payload command only gives 32 bytes before looping back and repeating the first byte in the payload.