The command that you are looking for is setMotorTarget as shown in the documentation here.
Essentially, you need to set the target rotation for the motor in degrees and then wait for the movement to take place:
//Sets motorA target to 50 degrees at a speed of 100
setMotorTarget(motorA, 50, 100);
// Waits for movement to complete
According to the online documentation, Bluetooth commands are supported for NXT but not for EV3.
On the other hand RobotC is supporting Bluetooth upload/debugging. This means that it is accessible. My first instinct would be to look at how RobotC did it (if the code is available). My second instinct would be to find if somebody already hacked the EV3 ...
Debugging tip: Inside of the wait loop, print the gyro angle on the screen so that you can see what the actual value is.
In your code, I see...
...which presumably causes the robot to rotate clockwise. And also...
...which presumably rotates the robot counter ...
It's been quite a while since I've programmed a robot, but using only the sonic sensor does make it a bit more challenging. Also, not knowing anything else about the robot you've built (it's size, other sensors & their location, the ball grabbing mechanism, etc.) it further complicates any possible advice.
That being said, the only solution I could ...
As you already have a working program for the continuous line, you just need to add provisions for the cases when
(the robot is moving on a straight part) AND (the color sensor finds a gap in the track)
Depending on your existing solution you might need to code dedicated methods to identify the two sub-cases and then call them repeatedly to see if the ...
This model uses gears to do 2 things:
Change the direction of motion:
The motor turns an axle, on which a gear is attached (partially hidden black disk in the picture).
The first two gears shift the rotation out in front of the motor.
The next two knob wheel "gears" turn the rotation 90 degrees, resulting in the golf club motion you see in the ...
Have you updated the firmware? That may be a problem but it also may be that there is an error connecting using Bluetooth. “Destination host was down” means that the coding platform could not connect to the NXT.
I have the same problem. I don't know why, but if I use only the plug adapter (without batteries inside) it works, communicates in/out with the tower. With batteries, no. In my case I only use this RCX with energy from plug adapter. (windows vista, robolab 2.9.4 , rcx 1.0 - usb tower).
Try to use this (Windows XP x86):
RIS v2.0 software -> http://www.mediafire.com/download/vrg2iajcv4uxkf3
Updated USB Tower drivers -> http://www.philohome.com/sdk25/tower164.zip
Also maybe you have a faulty RCX or IR tower. Try to change the battery of the IR tower.
I recommend the use of the Windows XP x86 (32 bits) for install the RIS v2.0 software. ...