 | | Re: NXT to RCX Communications
|
|
----- Original Message ----- From: "Brian Davis" <brdavis@iusb.edu> To: <lugnet.robotics.nxt...ugnet.com> Sent: Wednesday, October 04, 2006 10:23 PM Subject: Re: NXT to RCX Communications (...) Thanks Brian. I might as well use the time to try and (...) (18 years ago, 5-Oct-06, to lugnet.robotics.nxt)
|
| |
| | Re: NXT to RCX Communications
|
|
(...) No. The light sensor can have the red LED either on or off - you can't set it to "20%" or something like that, and there's no way to toggle the LED fast enough to mimic or RCX-style IR message. But... You could cetainly have a program (...) (18 years ago, 5-Oct-06, to lugnet.robotics.nxt)
|
| |
| | NXT to RCX Communications
|
|
Hello everyone: Is it possible for the NXT to send Run Program commands from the NXT to RCX via a light sensor? Here is an example: 1- The NXT Ultrasound sensor detects an object close by, triggers the NXT light sensor to light up at 20 percent (...) (18 years ago, 5-Oct-06, to lugnet.robotics.nxt)
|
| |
| | Studless building techniques
|
|
I am working with a couple FLL teams, building with the NXT. I am having a little trouble coaching them on studless building techniques, as it is still a bit of a new concept to me as well. I'm sure I've seen presentations or how-to's on the subject (...) (18 years ago, 3-Oct-06, to lugnet.technic, lugnet.robotics.nxt, lugnet.robotics.edu)
|
| |
| | 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)
|
| |
| | 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: (...) (18 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. (...) (18 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 (...) (18 years ago, 2-Oct-06, to lugnet.robotics.nxt)
|
| |
| | Help with NXT-G programming.
|
|
Hello, I got my Mindstorm NXT set a few weeks ago. Have built and programmed all the modells that was in the program that came with the set. And now started to make my own robots with the NXT. The NXT-G program looks great and is easy to understand (...) (18 years ago, 2-Oct-06, to lugnet.robotics.nxt)
|
| |
| | 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)
|
