Go Down

Topic: Data over XBee works for a few seconds then stops... (Read 14395 times) previous topic - next topic


Did more testing today. I ran my parsing at 150ms (up from 10ms) and it still drops out. There's no way I'm overrunning a buffer sending 20bytes every 150ms...particularly using call-response.

Have you tried going slower than 150ms on the PC side? Like a more human noticeable rate (1 s maybe)?
And then scale downwards.


150ms is already well beyond an acceptable latency (any sudden movements perceivably lag). I can try higher, but 1second is beyond useless for the type of application it's intended for (gesture sensing of a performers movements).

I'll give it a spin with 500ms maybe for testing purposes.


I'm looking at it from a testing perspective. So, at least you can confirm that this is not creating a bottleneck for the communication. :)

Go Up

Please enter a valid email to subscribe

Confirm your email address

We need to confirm your email address.
To complete the subscription, please click the link in the email we just sent you.

Thank you for subscribing!

via Egeo 16
Torino, 10131