Asked
— Edited

Hey guys I have a question/ am curious about something.
I have 3 V4 boards and 2 of them work great. One of them has a serious delay while running ARC scripts. the script will start but nothing will happen for 4-5 seconds.
they have all been updated and run on the same windows 10 computer. All are powered with 12 volts DC.
Has anyone else run into this and knows why I am experiencing one board with a large delay?
Thank you again!
Aaron
Are they in AP or client mode? If in AP mode, check the WiFi channel on the EZ-B web page. It could be set to a channel that is saturated in your location.
If in client mode, the channel is set by the router, but they can be set to 802.11g or n. N is faster, but has shorter ranger and more likely to have issues penetrating walls. There is a checkbox to enable or disable N mode.
Alan
Also check your project - it may not be optimized. Post it here and someone can look at it.
Also, if the project is not optimized, the communication channel may be flooded. There is a flood protection option in the connection control config menu. Be sure to read the question marks and help to understand it.
thank you DJ playing with the flood protection really helped out the response time, I think it was the project and it not being perfectly optimized..
Aaron
Aaron, that video is awesome. I have so many questions! How is the robot following you?
i see an Easter bunny inside the box !
he wrote:
it's a cool idea ...
maybe an ultrasound transmitter ? similar to the video below :
https://www.youtube.com/watch?v=tAyWrJoVUbs
Very similar but uses IR and ADC rather than ultrasonic
I really like their design but started me thinking of trying their method with an ezb. However could an ultrasonic sensor be tricked into reading another ping signal without the use of an xbee like in their video?
My understanding is that the sensor sends a ping and waits for the ping back. That time interval and the speed of sound result in a distance. Without the returning ping actually coming from the same sensor wouldn't they be out of sink with one another and when the ping is initiated? Is there anyway to compensate for this or set a delay to start once the initial ping is registered?
That way you wouldn't need the xbee to manually send the ping the same time it starts waiting for the return?
Aaron
You could use it without an xBee - but you would lose one feature:
The reason for the xBee is to have the micro initiate the ping, so a distance could be determined. The distance allows the robot to adjust speed.
If you had a handheld simply send a ping every second, you would lose the ability to determine distance, but you would know the direction. So long as you don't care about distance, you don't need the xBee.
A more cost effective, more compact and less complicated alternative to xBee are these RX modules. I've used them in past projects with great results: http://www.romanblack.com/RF/cheapRFmodules.htm
You can get them for around $2 for a pair on eBay - if you decide to go the route of the ez-b initiating the ping.
Personally, i would not use it at all. I would just have a ping sent every second. The speed could be adjusted by an IR distance sensor and camera - since the robot would require obstacle avoidance anyway.