The mobile ARC app internally only has code for wifi connectivity. It has no code to understand USB connectivity because it's non-standard or not compliant on most devices. It would be nearly impossible to write a single application that supports all usb dongles

There are a few things you can do

1. add a safety switch to the robot to monitor wifi connectivity with a relay connected to the EZ-B. The EZ-B has a setting in the configuration interface which uses port D24 to determine the status of the connection. So the robot can have a shutoff relay when the signal drops. Look in the ez-b configuration to set the option.

2. use a wifi scanner to get optimal wifi channel. I know on ez-robot's website they have a link in the FAQ about that here under WIFI SATURATION: https://synthiam.com/Tutorials/Trouble-Shooting.aspx#9

4) use a $25 raspberry pi in the robot running ARC instead of a mobile device

Or here's a latest update - which i think is a great price! Seriously super cool. The atomic Pi is a $35 windows computer: https://dlidirect.com/products/atomic-pi

Hi DJ,

Thank you for the response.  Understood that the mobile interface will not connect via USB.

I did not know that D24 was able to monitor the connection in this manner! I will setup my robot with this feature regardless of the operating system. [the robot weighs around 100lbs]

What would perform better in your opinion: -a standard pi[b+] utilizing ARC -a mobile app using a phone with 4gb of ram Are these two components comparing apples to apples?

Thank you, Aaron

the Pi version will give you more potential because plugins don't work on mobile. Also, with the Pi you can have more programs and different versions of programs. It's like having a little PC

Although, i do recommend Atomic Pi instead because it's $35 and runs windows. So it's just like having a laptop on your robot!

Atomic Pi is already sold out!!!

Thanks for the info!! Awesome find!!!

Hi DJ,

Thank you for the link and info on the Atomic Pi.  I am going to wait until the Atomic Pi comes back in stock.  I think this is the best solution for my requirements.

In the meantime, can you recommend a suitable relay for a 12V source? All of my robots will be getting this update.

EDIT Would this relay be acceptable? Relay Link:

Thank you, Aaron

this is a good question for Jeremie. I’ll tell him to check the thread

@robot56

12V automotive relays are definitely a robust option for switching 12V but personally I tend to stay away from relays. Relays are mechanical and do have a limited life. Automotive relays are definitely better as I have yet to have an automotive relay fail in any of my vehicles but I like to use MOSFETs instead. MOSFETs also don't have the electrical "ringing" effect of switch contacts and are audibly silent. There are a few caveats to using MOSFETs but there's tons of information online to sow you how to use them effectively. You can also purchase boards with the supporting circuitry already added.

Here's an example from Amazon

Due note that MOSFETs do generate a lot of heat with high current loads so sometimes extra heat sinking is required.

Hi guys,

I finally received my mosfet switches for my connection failsafe.

I am having a hard time finding the setting for using D24 to monitor the connection.

Can anyone help me locate this in the ezb configuration?

Thanks, Aaron

The setting enabling the D23 connection monitoring is in the ezb web server.... Make sure you update your ezb4 x/2 to the latest firmware first...

Richard is absolutely correct, with up-to-date firmware on the EZ-Bv4.1/2, that option is in the Webserver settings under "Advanced Settings" in the "Network services" section. It's called port D23 connection status.

Hi guys,

Quick update, the problem was firmware.  I got the board updated and everything worked accordingly.  Great feature to have

Thank you, Aaron