I have scoured the community for latency related issues but could not find my scenario. Basically, I have 2 Xenons in a time-critical application. When an incident occurs, the first Xenon does a mesh.publish to the second (48-byte message). When the second Xenon receives the message, it records t…

Are both devices using an EtherWing? If so (or the possibility exists) why not use UDP via Ethernet? If not, you have two UARTs on the other Xenon free to use and send the result to the gateway which doesn’t take part on the measurement. Have you considered BT to communicate between the two devic…

and if that end’s up not working as well, and the distance is not important, only the object passing through both sensors, you can also consider a simple sensor like this one

Lateral and outside-of-the-box thinking often help to come up with better solutions than clinging to an idea an forcefully making it (somewhat) work Yes indeed :slight_smile: Only one device is using an Ethernet wing and there is no Gateway. There is a lot of processing that is needed simultane…

Distance needs to be over 30 feet and is outdoors …

I would think the Bluetooth latency would be similar but you could use a XBee radio in pass through mode where the PIN on one XBee radio is mirrored on the 2nd XBee radio. Or the RFM95 radios to do the same thing. I’m not sure what the latency difference is between those 2 options but they are opti…

@Jimmie , perhaps the question should be, what latency do you need? As I see it, the serial laser sensor has a communications latency and the Xenon to Xenon introduces latency for any wireless or ethernet protocol used. Add to that the missing Xenon/Xenon time synchronization and “a lot of process…

Thank you @peekay123 . Yes, sure. Without losses, we expect the time difference to be about 75 ms. Since we need speed to be within 10%, that leaves only 7 ms for latency. I am hoping that using a hard wire and an interrupt will work but agree that it may be too tight …

[image] Jimmie: Without losses, we expect the time difference to be about 75 ms. Since we need speed to be within 10%, that leaves only 7 ms for latency. That's a velocity of 400 feet per second (30 feet in 75 ms), or ~275 MPH. I'd agree that a wired solution for (1) Controller/MCU is your b…

The 30 feet is the distance from the sensor to the object not the distance between the two sensors :slight_smile: The distance between the two sensors is about 150 cm.

Why not use the TX/RX of one and hook it up to the RX/TX of the second and just use Serial1 for the communication? I use this to have Feathers and Particles talk, and it works fine. I even wrote a rudimentary class that allows for asynchronous communication between the two.

Mesh Latency - Revisited

Firmware

Jimmie July 24, 2019, 3:44am 32

Topic		Replies	Views
Network Latency Firmware	13	1364	January 25, 2019
Boron + 5-Xenon Setup Questions General	85	5222	December 22, 2018
Slow response times on first attempt BLE // NFC	3	581	January 10, 2019
Xenon based Mesh network only BLE // NFC	24	4827	February 3, 2020
Large Mesh Networks Thread Project Share xenon	35	2805	November 23, 2019

Mesh Latency - Revisited

Related topics