 | | RE: Tacho Limit and Braking —
|
| | | If you want to try something a little different, use RobotC to do this. There are several advantages to this: * It can be done with one "setout" opcode. * The RobotC PID algorithm for this type of movement is different than the NXT-G (...) (18 years ago, 2-Oct-06, to lugnet.robotics.nxt)
|
| | | |
| | | | | Re: Tacho Limit and Braking —John Hansen
|
| | | | (...) 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 (...) (18 years ago, 2-Oct-06, to lugnet.robotics.nxt)
|
| | | | |
| | | | | | 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 (...) (18 years ago, 2-Oct-06, to lugnet.robotics.nxt)
|
| | | | |
