Go Down

Topic: Can somebody guide me with nrf24l01 command transmission? (Read 523 times) previous topic - next topic

JeromeAriola

So before we close, let me just clarify some things:

1. The nrf24l01 only sends messages which are at maximum 32 bytes (meaning I can only send at max a message like "HelloMyNameIsJeromeAriolaAndIRun", which is a 32 letter message.)

2. My Arduino can take a message, process it to where if I was to send a "U" message it would tell the motors "Hey I received a message U, meaning I turn on all the motors until he says D or something else"

Lastly, can you show me how you connected your nrf24l01 to the Arduino?

Thanks for all the help

Robin2

Lastly, can you show me how you connected your nrf24l01 to the Arduino?
This is ridiculous. I put all those details in the link I gave you in Reply #1. Have you even read it once?

And, yes, a single nRF24 message has a max of 32 bytes. I suspect that will be at least twice as much as you need, but if you need more you can send 2 or 3 messages.

Quote
2. My Arduino can take a message, process it to where if I was to send a "U" message it would tell the motors "Hey I received a message U, meaning I turn on all the motors until he says D or something else"
I don't know whether this means you know what you are doing or you haven't a clue.

...R
Two or three hours spent thinking and reading documentation solves most programming problems.

JeromeAriola

Gosh I keep missing critical details...

I just want to ask: What is a pipe to be exact? It's been confusing me, because to me I think it's a link or something with slave and master.

And you also said that the address is 5 bytes. Does this mean I can only send at max a 27 byte message? I mean, it's not like I'm gonna need that much, but it's nice to know.

Whandall

I just want to ask: What is a pipe to be exact? It's been confusing me, because to me I think it's a link or something with slave and master.

And you also said that the address is 5 bytes. Does this mean I can only send at max a 27 byte message? I mean, it's not like I'm gonna need that much, but it's nice to know.
Do yourself a favour and read the NRF24L01+ datasheet.
Ah, this is obviously some strange usage of the word 'safe' that I wasn't previously aware of. (D.Adams)

Robin2

IMHO the datasheet does not explain the concept of pipes very well - it just tells you how to use them - and even that is sparse enough as @Whandall's experience in another Thread has shown :)

The idea of pipes can be a bit confusing. Think of them as 6 shelves onto which the mail for different residents in an apartment block can be placed. All the letters come through the same mail slot (the radio receiver listening on Channel N) and when they fall on the floor someone picks them up, looks at the name of the recipient (the address the message was sent to) and puts them on the correct shelf (the pipe that has been assigned the same address as the message) or shreds them if they are for a recipient who lives in another block (i.e. if they are for an address that is not assigned to any of the pipes on this nRF24)

...R
Two or three hours spent thinking and reading documentation solves most programming problems.

Whandall

The packet format that is used on air is described very detailed.
(And so the non existent influence of the address size on the payload size).

All information about the addressing/pipes is in the datasheet,
admittedly a little bit scattered over the document.
Ah, this is obviously some strange usage of the word 'safe' that I wasn't previously aware of. (D.Adams)

Robin2

All information about the addressing/pipes is in the datasheet,
admittedly a little bit scattered over the document.
It is so nice to meet someone with such a sunny disposition :)

...R
(PS, I am not disagreeing with your statement - just your assumption that the datasheet will make sense to newbies)
Two or three hours spent thinking and reading documentation solves most programming problems.

Whandall

I had to read it a couple of time before I really understood the mechanisms.  ;)

Since the library basically only interfaces to the chips functions, there is no way around the datasheet
to understand the inner workings and limitations of the communication.

But that is only my humble opinion.
Ah, this is obviously some strange usage of the word 'safe' that I wasn't previously aware of. (D.Adams)

JeromeAriola

I think I get the whole pipe concept. I really do this time.

Okay, thanks guys. You guys have been great a great help, even when I was very stupid. (thanks especially to Robin2)

I think we're done here, although I'll be coming back for extra help. My nrf24l01s just came in, and i want to try some of the stuff you have taught/showed me.

Thanks a million!

Robin2

there is no way around the datasheet to understand the inner workings and limitations of the communication.
I agree completely - but that does not make it easy for a beginner.

...R
Two or three hours spent thinking and reading documentation solves most programming problems.

JeromeAriola

#25
Mar 23, 2017, 02:40 am Last Edit: Mar 24, 2017, 02:29 am by JeromeAriola
Hey, Robin, I found something that I think might help me with my project, but just needs some expert interpretation.

http://www.blog.aeste.my/?p=3690
 Like what are all the "0x99" etc for and how do I know how and when to use them?

Robin2

Hey, Robin, I found something that I think might help me with my project, but just needs some expert interpretation.

http://www.blog.aeste.my/?p=3690
That link does not work.

However you should know in advance that I put all my efforts at interpretation into the link in Reply #1 and I have no plans to reinvent my wheel.

...R
Two or three hours spent thinking and reading documentation solves most programming problems.

Whandall

The correct link is probably https://blog.aeste.my/?p=3690

As far as I understand that's the reverse-engineering of a quadcopter communication that uses a NRF.
Ah, this is obviously some strange usage of the word 'safe' that I wasn't previously aware of. (D.Adams)

Robin2

The correct link is probably https://blog.aeste.my/?p=3690
Thanks for that.

It seems to use a fairly obvious system - the sort of thing (in simplified form) I have been trying to get the OP to focus on.

...R
Two or three hours spent thinking and reading documentation solves most programming problems.

Go Up
 


Please enter a valid email to subscribe

Confirm your email address

We need to confirm your email address.
To complete the subscription, please click the link in the email we just sent you.

Thank you for subscribing!

Arduino
via Egeo 16
Torino, 10131
Italy