 | | Annelus
|
|
Hello everyone, I have finally finished a rather large project that has occupied my time for some months now. I started building Annelus when I discovered (URL) Rotundus> and decided to emulate the creation. What I came up with was a month long (...) (20 years ago, 4-Oct-06, to lugnet.robotics, FTX)
|
| |
| | Re: Studless building techniques
|
|
In lugnet.robotics.edu, Merredith Portsmore wrote: <snip> (...) Meredith, Thanks for posting this. It is wonderful first shot at some of these building topics. I am concerned, however, about the Pythagorean triangles on the Stability link. The (...) (20 years ago, 4-Oct-06, to lugnet.robotics.edu)
|
| |
| | Re: Studless building techniques
|
|
(...) There are some good basics at the LEGO Technic Design School. They've been slowly adding more (URL) Beams & Connectors How LEGO TECHNIC elements work together. Lesson 1: TECHNIC 101 Lesson 2: Stability with LEGO TECHNIC Course: Gears TECHNIC (...) (20 years ago, 4-Oct-06, to lugnet.robotics.edu)
|
| |
| | 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 (...) (20 years ago, 3-Oct-06, to lugnet.technic, lugnet.robotics.nxt, lugnet.robotics.edu)
|
| |
| | Re: NXT direct commands
|
|
For better documentation of the various parameters, look in the Executable File Specification.pdf around page 81. Here's the notes I made in ruby-nxt ((URL) # output mode COAST = 0x00 # motor will rotate freely? MOTORON = 0x01 # enables PWM power (...) (20 years ago, 3-Oct-06, to lugnet.robotics)
|
| |
| | 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)
|
