If you manage to get the sabretooth Movement Panel to work then when you add the speech recognition control, it will already be configured to work. You won't need any additional set up... Forward() is all you need, no extra parameters... if the sabertooth Movement Panel works, then so will the speech control panel

Hopefully last question for a while.............. regarding scripting.. If I write script does it have to be associated with the graphical user interface. This is a hard question for me to explain. I program PLC's for a living and this is quite a bit different. So when I script/program my robot to move to a location most likely using timed commands will it always need the graphical Movement Panel present on the desktop or running? Same with speech, do I need to have the graphical speech recognition block open on the desktop.? I would like the onboard atx computer to boot, open up ARC and run based on verbal command. Literally I want to say " I need assistance with a beverage" and have the bot move from a fixed always known location (manual placement) to move forward for a specified time, make a left turn 90 degrees, and then continue forward for another predetermined time. This is the simplistic version. It will be impressive enough to see that happen before adding in other sensors. The atx computer will not have a monitor and I will just rdp into it for adjustments and additional programming. Thanks Richard R. You will definitely get the reolved NOD from me hopefully tonight when I get back to this. Thanks again

I haven't read any of this topic yet but wanted to just point out that the RoboClaw is a clone of the Sabertooth from what I read in the past.

Now I'll give the topic a proper read (and see that someone else has probably said this).

If it's basically a clone of the sabretooth, check out the sabretooth tutorial on here.... get the dips on the roboclaw set for 38400... You only need 2 wire... ground to the ground pin on the ezb and the s1 connected to the data pin on the same port of the ezb... Just try D0 pin for now... once you get the sabretooth control panel working, we can go from there... Speech control has to remain open as it is linked to the particular motor control panel that you have open as well...

No dip switches. But I have that part taken care of. Will be back at it again tonight. Thanks again

      Chris

Jumpers perhaps?

It is all set thru menus... so in other words push set button and status 1 light blinks. Depending how many times it blinks is the current mode setting. I set it last night for mode 5 which is simple serial command, however I could not set the baud rate. After reviewing the manual again this morning I know how to accomplish this. So I will definitely get that done before next post. Im not so sure on the clone thing. This controller is a bit more advanced from my research. This controller will take encoder inputs directly to it. If operated in packet serial mode it can use these encoder inputs and send to EZB4. In other words I don't need a kangaroo board as I have been reading about. So to recap.... for the lower drive train I am using the robo claw 2x60 and will be using it in simple serial mode to start. Now to add complexity to the mix I will be using a robo claw 2x 30 for the wheel chair shoulder motors as well. This will be controlled by ezb4 board number 2. Again to add more I see that I can only have one Movement Panel open in ARC hence the question on do I need to have graphical reference open. Thank you everyone for looking at this post, I cant wait to get this thing rolling.

                                             Chris

And one other thing maybe worth mentioning is the robo claw manual specifically calls out using a UART port from the microcontroller. I'm not sure how this differs from serial commands sent from D0 but if D0 doesn't work I will move to D5 and change port setting in EZB4 to accommodate. I would think serial is serial and at this point I would only be using one way comm anyways. So.... let the fun begin!