 | | Re: NXT to NXT communication?
|
|
(...) The motors offer little resistance when used this way. However, there's something else which I think is kind of cool. If you look close, when I let go of the controller, the paddles return to the middle, and the car stops. Using just one block (...) (20 years ago, 3-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) Yep (at least that's one way to do it). I tried making a X-Y joystick, but the mechnical slop was more than I liked, so I've got one with two paddles and a thumbwheel (slightly different from Steve's) (...) Not too bad. The NXT motors are not (...) (20 years ago, 3-May-06, to lugnet.robotics)
|
| |
| | Re: NXT to NXT communication?
|
|
(...) they when you do that? Also, I noticed at one point you scooted the controller closer to the car. Was that because it had lost the signal? What is the effective range, anyway? I also wonder what happens when you have more than two NXT bricks (...) (20 years ago, 3-May-06, to lugnet.robotics)
|
| |
| | Re: NXT Programming with Next Byte Codes
|
|
(...) The NQC compiler in some form or other is headed for NXT support but for a number of reasons I needed to produce a functional assembler first. Now that it is mostly complete I will be trying to shift gears and work on NQC. I will post several (...) (20 years ago, 3-May-06, to lugnet.robotics)
|
| |
| | Re: NXT Programming with Next Byte Codes
|
|
(...) Great news! I look forward to seeing more. Can you post some complete example programs? Also, is there a C syntax commandline alternative in the works? (20 years ago, 3-May-06, to lugnet.robotics)
|
