Unfortunately I am 3000 miles away from my hardware lab and when I was packing up I left my oscope in Arizona, but if we need one I can make one pretty quickly. As for everything else we should be alright on hardware testing.
The RFM69HCW does not have meshing in its bag of tricks though that would've been nice. Hindsight is such a pain sometimes lol.
In any event you could think of the mesh as an application level development I suppose. The radios themselves more or less communicate with any radio that is in range and from there when they get a signal, if it is for them then they do something with it, if not they either forward, or discard it. That is the basic principle of the Radiohead RH_RF69 Library.
Today I wrote a much simpler communications method for them since at any given point in time only one node is communicating with master unit and vice versa. So I hit on the idea of just have the nodes forward the message without the use of a route.
Any node that received it but wasn't the destination, waited a small random time, and then would rebroadcast the message. I gave each transmission a unique ID so that it would only be processed and/or forwarded once per node that got it.
With end to end acknowledgement this works perfectly with one sensor. Pretty good with 2 sensors, and gets exponentially worse as more sensors get added. So I have spent a significant portion of the day trying to find good ways to prevent collisions and broadcast storms.
I tried checking the rssi of the radio but ran into the same problem as the developer of the RH_RF69 library did with an major freeze when triggering the radio to take a new reading. I tried bastardizing the rf69.available() to make sure no one else was transmitting but that only worked so so.
Now I am back to the drawing board to figure out the best way to stop these collisions while still mass forwarding the payload, which with this new approach is 54 bytes.
Time frame is...how to say this...I wanted to go home a month ago, so faster would be better than slower.
is it "just" intended to build somthing like like rangeextender with multiple hops?
Yes exactly that...that is all it actually needs to do. That would precisely solve the problem. Just wish it had of occurred to me as quickly as it did to you. I only thought it up last night after a month of trying and failing.