 | | NXT direct commands
|
|
Hi, i'm programing a Python library for remote controlling the NXT, now i'm working with the "set output state" message and i would like to know what means the diferent values of each parameter: #MOTOR MODES MOTORON = 0x01 BRAKE = 0x02 REGULATED = (...) (20 years ago, 3-Oct-06, to lugnet.robotics)
|
| |
| | RE: Tacho Limit and Braking
|
|
(...) You can do just about anything with one line of code if you count user subroutine and user macro calls as "one line". The "Rotate" macro in your example expands to four lines of code that sets up and calls a user program subroutine that is (...) (20 years ago, 2-Oct-06, to lugnet.robotics.nxt)
|
| |
| | Re: Tacho Limit and Braking
|
|
(...) This made sense, until I read this... In lugnet.robotics.nxt, John Hansen wrote: (...) I had to go back and re-read this to understand one is talking about the NXT firmware, and the other is talking about NBC. If I read it correctly, it means: (...) (20 years ago, 2-Oct-06, to lugnet.robotics.nxt)
|
| |
| | Re: Help with NXT-G programming.
|
|
(...) That's just... weird. I've never managed to get something like that. The sequence beam seems to be pinned to the lower edge of the Loop structure, so that even if I make the loop wider, I still can't get to the blind end of the sequence beam. (...) (20 years ago, 2-Oct-06, to lugnet.robotics.nxt)
|
| |
| | Re: Tacho Limit and Braking
|
|
(...) This is incorrect. There is no "setout" opcode in RobotC. RobotC uses a proprietary commercial alternate firmware with a completely different set of opcodes and virtual machine functionality than the standard NXT firmware. Unfortunately, the (...) (20 years ago, 2-Oct-06, to lugnet.robotics.nxt)
|
