NRF24L01 - eagle la...
 
Notifications
Clear all

NRF24L01 - eagle layout?

60 Posts
11 Users
0 Reactions
36.7 K Views
Posts: 6728
(@p-short)
Illustrious Member
Joined: 19 years ago

Me, me, me!

I've been working on some PIC-based NRF projects, although I've become distracted by another more interesting project. The largest board is a PIC18F23K22-based 'host' with a 64x128 graphics LCD. The other two boards are AC dimmers for low-amperage light strings (one is two-channel, the other is four-channel) using PIC16LF1503 microcontrollers. The original intent was to use these for controlling lawn sprinklers, although they can also switch or dim 110VAC loads.

100 0747

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

Interesting. Was there a thread with more details that I missed? (I haven't been completely focused of late)


Reply
Posts: 6728
(@p-short)
Illustrious Member
Joined: 19 years ago

Just one brief post in this thread (post #37). Otherwise I've been keeping quiet.


Reply
timon
Posts: 2149
(@timon)
Noble Member
Joined: 16 years ago
P. Short wrote:Me, me, me!

I've been working on some PIC-based NRF projects, although I've become distracted by another more interesting project. The largest board is a PIC18F23K22-based 'host' with a 64x128 graphics LCD. The other two boards are AC dimmers for low-amperage light strings (one is two-channel, the other is four-channel) using PIC16LF1503 microcontrollers. The original intent was to use these for controlling lawn sprinklers, although they can also switch or dim 110VAC loads.

This is inline with what I have on the drawing board for some landscape lighting both 12V and Line voltage. While I'm trying to resurrect the Pixel Flower I'm moving on toward other landscape lights some of which will be nRF based using PICs.

LabRat wrote: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.

As far as the address at the start rather than the end I agree but for even more reasons. I believe the protocol could be made more flexible if the control byte was at the start. At one point I thought that change was going to be made but I guess it got abandon but I need to explore that. Having a "compile" flag works but having the option for a run time switch would be nice then devices could be change without having to reload the image.

I'd like to see a complete nRF "C" library made available for PIC processors so more wireless can be used with them.

The FPD version 2 that dpits and I have been working on has provisions for a nRF module. The board is entirely PIC based so there will be more PICs using the wireless modules The plan is to support all three wireless speeds and pixel counts 4096 pixels when running at 2Mbps. The supporting code has not yet been written but initial plans are to support the Komby protocol but other protocols are alway possible.


Reply
Posts: 6728
(@p-short)
Illustrious Member
Joined: 19 years ago

How's this coming along?


Reply
Page 12 / 12
Share: