NRF24L01 - eagle la...
 
Notifications
Clear all

NRF24L01 - eagle layout?

60 Posts
11 Users
0 Reactions
36.7 K Views
LabRat
Posts: 2981
Topic starter
(@labrat)
Famed Member
Joined: 17 years ago

The antenna is 7" long. (I just remembered that I was supposed to measure it)


Reply
Posts: 2541
(@lightup)
Famed Member
Joined: 17 years ago
LabRat wrote:The antenna is 7" long. (I just remembered that I was supposed to measure it)

Thanks, then I also have one like that.
I bought 4 NRF24L01+ modules to experiment with. One module has the SMA connector and my other 3 have the zig-zag antenna.


Reply
LabRat
Posts: 2981
Topic starter
(@labrat)
Famed Member
Joined: 17 years ago

My plan was to use external antenna on the transmitters (2 units), and zig-zag on the two types of receivers (easier to hide in props etc).

Type 1 : Three channel RGB LED string driver.
Type 2 : NRF2DMX (regenerate DMX at the "far end" of the linkage).


Reply
dmcole
Posts: 2196
(@dmcole)
Noble Member
Joined: 19 years ago

Andrew:

Will you use the same radio-transmission protocol as the Komby products (i.e.: could a hobbyist mix and match Komby devices and you devices)?

\dmc


Reply
LabRat
Posts: 2981
Topic starter
(@labrat)
Famed Member
Joined: 17 years ago

An interesting question as I reviewed the Komby protocol which as I recall was ,

. This just seems backwards, as you have to receive and store the entire payload (31 bytes) before seeing if the address was correct. My intent was to code up

,. This way the state machine parsing the incoming data can identify where in the DMX buffer to write the incoming bytes. Hence saving us 31 bytes of additional storage, as well as the cycles to copy the data around a second time.

That being said, there is nothing stopping us from making a "compatible" packet load firmware image. In fact for the transmitter it should just be a compile flag, as it would be a minor tweak of the write routine from "output address, output 31 bytes of payload, rinse & repeat" to "output 31 bytes of payload, output address, rinse & repeat". For the receivers, it would differ due to the extra step of "validate address before copying", versus "validate address before receiving".

Based on online reading, most of the NRF work seem to be arduinii based... so I don't know if there is much (any?) interest beyond myself, for a PIC based solution.


Reply
Page 11 / 12
Share: