The thing that I really REALLY like about MyRobotLab, is that GroG has taken really difficult things like speech recognition and vision processing and made it "monkey pushes the button" easy.
Pioneers are the guys with the arrows in their backs. GroG can probably tell you all about that.
Here I'll go over several issues I have found with the Arduino service & WIndows 7 (64 bit)
FTDI Driver strangeness & Jumpy Oscope
After updating my driver at some point (or unknowingly being updated by Windows) I noticed the Arduino Oscope behaving very strangly. When I selected a trace on the Arduino to display, the trace line would freeze, then flash quick, then pause, then flash - nothing like the smooth behavior it had previosly.
I have x64 bit OS running on one of the builds you have on the bleeding edge.
I am not sure if my setup is fully functional.... but I get it to work most often and sometimes have to kill the java process manually to get it to release the serial port....
I'm having fun with this and learning a little more each day.
My question is how can I talk to the Arduino with a direct serial connection via realterm or equivalent terminal when running the arduinoserialbare.pde on the microcontroller.
MRL runs on a JVM and can communication to the Arduino micro-controller through a serial port. MRL controls the Arduino through a serial protocol.
MRL to Arduino uses a 3 byte command set
msg = METHOD
msg = PARAM1
msg = PARAM2
The Motor service gui is being updated. It has been designed to support multiple motor controllers. This is nice, since there can be a little complexity in attaching a motor to a motor controller.
For example an Arduino can directly drive a simple 2 bit H-bridge connected to a DC motor. Or a motor shield can be used, which has its own motor port configuration. Other shields and bridges might have different configuration.