Chat freely about anything...

User avatar
By eriksl
#81958 @holopaul, the code path for sending data from the network to the UART and receiving from the UART and sending it to the netwerk is completely different. Can you please explain which path you're using (most) and which is having the latency?

When I am testing with the terminal emulator, it looks like network->UART is quite good and responsive, the path from UART->network looks like having some latency, but it can also be just the keyboard key repeat that's slow.
User avatar
By holopaul
#81963
eriksl wrote:@holopaul, the code path for sending data from the network to the UART and receiving from the UART and sending it to the netwerk is completely different. Can you please explain which path you're using (most) and which is having the latency?

When I am testing with the terminal emulator, it looks like network->UART is quite good and responsive, the path from UART->network looks like having some latency, but it can also be just the keyboard key repeat that's slow.


I feed both esp the same sensor data. The data flow is this: sensor>uart bridge>network(ip)>processing ide viz on the computer.
You can take a look at this slowmotion (240fps) clip. v22 on the left, v11 on the right side.
https://imgur.com/a/7CuRMKZ
User avatar
By eriksl
#81965 In this direction an improvement was possible, can you please test? Sending to network is now started immediately and not left waiting for a "slow interrupt" (which isn't that slow, it fires 10 times a second). The drawback is that less data is accumulated, you'll now probably get one byte per packet ;)