802_15_4

[Orange]

If I send 0x33 through the project example in the directory “nRF5_SDK_17.1.0_ddde560\examples\802_15_4\wireless_uart”.I can see the data 0b  61 88 01 34 12 0b 00 0a 00 00 33.

The format of our customer product is different from that of this command. They are not standard. Is there any way to close all the data before 0x33 above? The length information of the first byte can be retained

[ovrebekk]

Hi

Can you give me a bit more information about what the product is going to do? 

It is very uncommon to use the 802.15.4 MAC directly for an end product. If you need mesh capabilities it makes more sense to use one of the higher level protocols (such as Thread or Zigbee), and if you don't need mesh then possibly a Bluetooth or a proprietary 2.4GHz connection could make more sense. 

I assume there is some packet overhead in the wireless_uart example, but I need to dig a bit more into the code to understand exactly what these bytes are doing. 

Best regards
Torbjørn

[Orange]

Hi Torbjørn, thank you for your reply.

The customer's product has been mass-produced before, a 2.4G remote control. Now let's redesign.

Our boss wants to use 52840. We only use the RF function of 52840, instead of running higher level protocols. So I want to ask how the routine "wireless_uart" receives/sends its own RF data without ID, addr, index and other information.

Best regards

Orange

[ovrebekk]

Hi Orange

Is using 802.15.4 a requirement? 

If not I would suggest using the ESB protocol instead. This is a simple proprietary 2.4GHz based protocol that adds very little overhead to the packet. 

What you receive on one side is identical to what you send on the other side, all the header information is automatically removed by the library. 

You can find these examples in the following SDK folder:
\nRF5_SDK_17.1.0_ddde560\examples\proprietary_rf

Best regards
Torbjørn

[Orange]

Hi Torbjørn, 

I ran the project esb_prx&esb_ptx in the directory "propertary_rf" with two boards, and the two boards can be used for receiving and sending. But I saw 250Kbit is not defined in the nrf_ esb. h file (see below)

#if defined(RADIO_MODE_MODE_Nrf_250Kbit)
NRF_ESB_BITRATE_250KBPS = RADIO_MODE_MODE_Nrf_250Kbit, /**< 250 Kb radio mode. */
#endif //!( defined(NRF52840_XXAA) || defined(NRF52810_XXAA) || defined(NRF52811_XXAA) )

See from the notes ! (Defined (NRF52840_XXAA), does this project not support 250Kbit?

I added the definition of 250Kbit at the top of the header file (as shown below) and set the sending and receiving rate to 250Kbit. The two boards cannot communicate. Change back to Nrf_ 1Mbit or Nrf_ 2Mbit can communicate normally

#define RADIO_MODE_MODE_Nrf_250Kbit RADIO_MODE_MODE_Ieee802154_250Kbit

Best regards

Orange

[Orange]

Hi Torbjørn,

I saw you recommend this project in other people's questions(github.com/.../nRF-Radio-802.15.4-Projects).I tested that the data sent by this project can be modified as I want. However, the project cannot be sent after several times. Is there any update to make the project more stable?

 The radio project example can not modify param to run IEEE802.15.4-2006? 

Best regards
Orange