Ok, thanks. I thought so but I wasn't sure. I understand the logic of having only movement panel, but I think it all hinges on the assumption 1 project = 1 robot. Which is the concept behind the mobile interface, and that's fine.

Thing is, a PC project is a very different animal, but it too can only have one movement panel. A PC project can access multiple robots. Each can be controlled individually. In this regard it would seem multiple movement panels would be appropriate. Like the non-movement AutoPosition panels, each Movement Panel could address a different board. Would this be a possibility?

That exists - add the non movement Auto Position panel. You can find out more by visiting the Add Control button of ARC. In that menu, you will find new controls to add to a project.

If you wish to add a non Movement Panel version of the auto position, you may do so in the add control menu.

For example, in my Ted talk last week - you would have seen me control 5 robots (3 six, 2 roli) with a single wiimote in a single ARC.project. I'll post the project for you...

Here's the project that i used to control 5 robots (3 Six, 2 Roli) with a single WiiMote for my Ted talk on June 17th 2016: TEDX.EZB

Whoops. I didn't give enough information. I'll study everyone's replies but for now here is a little clarification.

My bot is not mobile (around 200 pounds) and around 6 feet tall. The motors control:

Waist rotation Head rotation Arm actuators (2) Head lifter Mechanism with two motors

All are 12 volt. My goal is to simply turn them on, stop, and then reverse. At this point I just need "puppet" control. I plan to get more imaginative later.

@RoboHappy ... What you want to do is so simple to do using just the custom Movement Panel and variable(s) to represent speed.... Slow indoor, fast outdoor... as an example using PWM

$speed_set = 50 #half speed

PWM(D0,$speed_set)

$speed_set = 100 #full speed

PWM(D0,$speed_set)

Variables are global so you can change $speed_set on the fly in other scripts and the custom Movement Panel will immediately change the speed of your motors... if your photo cell detects a lot of light... set $speed_set = 100 else $speed_set = 50.... very simple...

Mulberry, sounds exciting!

Use the hbridge Movement Panel with pwm for the actual physicals direction movement of the robot. That means the wheels that move the robot, i.e. Forward, left, right, reverse, stop. Those are directions and that means the direction the robot moves. So use the hbridge Movement Panel with pwm for the wheels that move the robot.

Now add a mobile interface using the example video that I presented earlier. Add buttons for controlling the waist, head, arm, etc.

With the mobile interface you can easily add a nice background image as well. This makes the program look nicer and be easier to use.

Voila!

@DJ, and everyone else Thanks for the info. I figured as much, but was glad to get a better explanation and insight! Been awhile since Ive done any coding for CY, kinda forgotten alot, been too busy with my new toy (3d printer). later!

Yeah those 3D printers are sure attention hogs!