RF24mesh terminology for networking

Projects Networking, Protocols, and Devices
1

Hi all, I'm starting to get into using the RF24mesh library (beginning to use it), and attempting to understand some terminology associated with the mesh networking. I'm using arduino MEGA 2560's with nrf24L01+ transceivers, with RF24mesh sketch codes (for a slave arduino and one master arduino). The communications is working, but now working toward understanding some terminology, to understand some basics of operation.

[This post will involve questions about terminology, but there is another post involving a communications issue, at ...click here.....]

I came across this site here ... https://tmrh20.github.io/RF24Mesh/General-Usage.html

...and it says that "RF24Network addresses can be viewed as MAC addresses".

It also says "When joining or re-attaching to the network, nodes will request a RF24Network address, and are identified via nodeID".

Normally, MAC addresses are permanent, unique, and fixed, right? So, if a slave device already has a permanent/fixed/unique MAC address, then how is it possible for the slave to request a MAC address? And where would the slave request this MAC address from? Request it from the master device?

Is it true that these "RF24Network addresses" refer to the 5 byte (40 bit) address to be assigned to an nrf24L01 transceiver device?

Maybe there are other users of the RF24mesh library here that can start me off on the road to understanding some basics. I haven't found a beginner's tutorial explaining the terminology yet. So if anyone has a good beginner's tutorial that gives a rundown on these terminology and address assignments.... then definitely paste the link here. Will definitely read it.

Thanks in advance!

2

You seem to be DOUBLE POSTING and you have been around long enough to know not to. Please click Report to Moderator and have the Threads merged.

...R

3

Robin2:
You seem to be DOUBLE POSTING and you have been around long enough to know not to. Please click Report to Moderator and have the Threads merged.

...R

One post is associated with terminology. The other is about system functionality. It's definitely not double-posting, as the two topics are totally unrelated, right?

On the other hand, if the two posts are allowed to be merged (even though the topics are unrelated), I definitely don't mind. That would be good too. I did think about it before having two posts on RF24mesh..... but decided against having the terminology question (this thread) in the technical thread about the occasional 'SendFail' messages.

4

Southpark:
as the two topics are totally unrelated, right?

I may be wrong but it seems to me they both refer to the same project and I suspect that the info in one will be relevant for the other.

I will leave it to you to decide whether you ask the Moderator to merge them.

If you decide to keep them separate I reckon it would be a good idea to have cross-links from one to the other.

...R

5

I think you have some good points there Robin. I'll add a cross-link to the first post of each post. I agree that if somebody else goes down the same path, they may be interested in both things. Thanks Robin! Good recommendations.