Welcome to Synthiam!

The easiest way to program the most powerful robots. Use technologies by leading industry experts. ARC is a free-to-use robot programming software that makes servo automation, computer vision, autonomous navigation, and artificial intelligence easy.

Get Started
Canada
Asked — Edited

Ssc32 In Mobile Interface

Hi,

I have been using an ezb-v4 with a ssc32 to control servos without issue for a while now. However, trying to use the Mobile interface (v2017.02.16.00) the ezb/ssc32 link (uart @115200) is freezing (red light on both ezb and ssc32) as soon as I try to send a command via the uart. (It will still control the servos plugged directly into the ezb)

I tried clicking the Ssc32 control on the desktop of the mobile and it says: "This control does not have an interface".

Has anyone else experienced weird connection issues when using uart?

P.S. this also happens when I swap the battery in the robot on the Win10 desktop version of ez-builder. In order to reconnect, I have to shut down the application and restart.

Any assistance would be greatly appreciated.


ARC Pro

Upgrade to ARC Pro

Get access to the latest features and updates before they're released. You'll have everything that's needed to unleash your robot's potential!

AI Support Bot
Related Content
Synthiam
Based on your post activity, we found some content that may be interesting to you. Explore these other tutorials and community conversations.
#1  
You need to initialize the port first.... I do it in an init script. Also make sure you add the SSC-32 control to your project as well... I have not tried using the ssc-32 with a mobile device however, just on a PC...

Code:


UartInit(0,0,115200)
#2  

Quote:


P.S. this also happens when I swap the battery in the robot on the Win10 desktop version of ARC. In order to reconnect, I have to shut down the application and restart.


In general, losing power on the bot should not cause EZ-B to lock up, it should just disconnect, but it is best practice to hit the disconnect button before powering down the bot (to change battery, or any other reason), to make sure that any ongoing communications are shut down, and to re-run your initialization when you power back up and connect.

Alan
Canada
#3  
Thank's for that. I've added the script to the "connection established cmd" (as well as added an init control) and that seems to have solved the PC connection issue. Hasn't resolved the Mobile interface. I even tried adding a button with said script and no dice...
#4  
@srobert It's possible the ssc-32 control does not work with the mobile interface....
Login to post a comment