Now about the environment. The area where this will all take place will be on a wide open, flat space. There should be basically no physical obstacles for the signals to collide with. But even so, the nRF24L01 has good checking for repeated packets. So if the signal bounced off of something and arrived again at the receiver, it would know and just throw it out.
Haha, well not exactly, but same idea. This is really as simple as I'm just trying an experiment. I will probably just make some sort of small robot and do this on my driveway, giving it a certain path to follow based on position.Oznog said:So you're thinking of an autonomous mower... we know.
No, it doesn't have to be RF, I would just prefer it that way. Again, this is mostly just an experiment for me, so I'm not so much looking for practicality at the moment. Instead I really want to see if I can make this work with RF. That said, though, ultrasonic is probably going to be the only thing I'm going to be able to use anyway, due to the mentioned complications RF would give me.Sceadwian said:Does this have to be RF? 1-40 feet isn't that great a distance, if you have line of sight you could use time of flight of a single pulse of an ultrasonic transducer to measure distance, but that's nearly as plagued with details as the RF method.
The problem with the repeating cycle is that you have to capture the reception time at A in each cycle so that you can get an aggregate time to divide by the number of cycles. You might be able to get round this by, instead of capturing the reception time, merely detect the reception by A and use it to automatically trigger the next transmission by A.Because if I just did one complete cycle, the total time (after subtracting the time for code execution, delays, etc.) of the time 'on air' would be too small to measure with a timer with a 100ns resolution. So by repeating the cycle 295 times (590 half-cycles) and measuring the whole process in one chunk, I make it so I can pretty accurately measure the 'on air' time.
The problem with the repeating cycle is that you have to capture the reception time at A in each cycle so that you can get an aggregate time to divide by the number of cycles. You might be able to get round this by, instead of capturing the reception time, merely detect the reception by A and use it to automatically trigger the next transmission by A.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?