The problem can be restated:
360 / 20 = 18 deg / sec = 1 deg / .056 sec
One degree is the smallest increment provided by the rotation sensors.
NXT-G has a timer sensor with 1/100th second resolution.
Set a motorPower variable to 10
Start a timer
Loop until rotationDegrees >= 360
If timeElapsed * 18 > rotationSensorDegrees
The NXT actually uses IEEE 794 32-bit floating point number format in little endian byte order. I like using this site for conversions.
So, to decode your messages:
TX: 00 09 00 05 60 EA 00 00 00
Byte 0: 0x00 - response required
Byte 1: 0x09 - write message command
Byte 2: 0x00 - Mailbox 1
Byte 3: 0x05 - Message size of 5 bytes
Bytes 4-7: 0x60 0xEA ...
Sadly that's a limitation of Windows RT - there's no way you can install the EV3 software on there.
Windows RT can only run apps from the Windows Store (and some specially compiled apps that MS supply such as Office RT - however I don't think the typical user can install a correctly compiled non-Store app on the Surface - as a developer you can side load ...
Unfortunately there are no shortcuts. EV3-G can not open programs written in NXT-G.
To quote Lego:
9.5 I have a LEGO MINDSTORMS NXT2.0 (8547) set; will there be an upgrade/conversion kit from NXT to LEGO MINDSTORMS EV3 (31313)?
No, but LEGO MINDSTORMS EV3 offers backward compatibility to NXT. You can therefore use your NXT Intelligent Brick ...
No, it appears that you need to use the EV3 software to program the EV3 kit, as per the FAQ on the LEGO site: http://mindstorms.lego.com/en-us/News/ReadMore/Default.aspx?id=476781
The EV3 sensors also won't work with the NXT brick either.
Though, I'd imagine if you're getting an EV3 kit, it should come with the EV3 software.
No, there is no automated way to convert source files from other programming languages into un-compiled NXT-G code. The .rbt format is very complex, so writing a program to interpret programs written in other languages and generate a proper .rbt file with properly placed and configured blocks would be an incredibly time-consuming and tedious task that wouldn'...
I found the resolution of the EV3 motors by attaching a 90° connection to the motor, and a long axle with a pointer at the end so I could see changes in small angles. By running a loop a large number of times with settings of 360°, then with 360.5°, then 360.75°, and watching for when the changes trigger actual accumulation of ending point, I found that ...
You just need to make the blocks match your pseudo code. The missing part is "Stop Motor B". Adding blocks to stop motor B will help.
Also, stop motor B needs to be before starting motor A, otherwise motor A will run while motor B is running.
If Touch1 == Bumped Then
Rotate MotorA by 15 degrees
Else If Touch2 == Bumped Then
In the middle "thead" all of your motor blocks are "unlimited" or "stop". These blocks change the motor state and immediately continue to the next block. These are inside a loop that loops forever, so these blocks are running continuously in the loop. The motor blocks in the top thread may have an effect for a split second until the middle thread loops again ...
The move steer and move tank blocks take 5kb each while the large motor block takes 4kb. If you have a long string of move blocks in your program, it will take up big chunks of memory. We've gotten around that in the past with using myblocks. Myblocks are only copied to the NXT once and called each time it is needed in the program. A pivot myblock might take ...