 | | Re: RC DrWho K9
|
|
Very nice!!! Russell _so_ has to work this into Series 3 somewhere. ;) (20 years ago, 2-Feb-06, to lugnet.space, lugnet.robotics, lugnet.technic)
|
| |
| | RC DrWho K9
|
|
Hi I've been building some DrWho lego .......I'm still working on all my DrWho MOCs Dalek, Davros, Cyberman and K9 but some friendly AFOLs have said I should RC my Dalek or K9 so I picked up a cheap "Dirt Crusher RC" set as the base of my go at an (...) (20 years ago, 2-Feb-06, to lugnet.space, lugnet.robotics, lugnet.technic)
|
| |
| | Re: What I would do (2)
|
|
(...) Performance should come first. But thinking about API compatability, hopefully we will get a more programmable environment than the RCX's limitation from registers, functions and memory. A slowdown process may also be needed to make the NXT (...) (20 years ago, 1-Feb-06, to lugnet.robotics)
|
| |
| | So when do we know about the MDP?
|
|
It ends Sunday, will participants receive emails on Monday? I would assume so since they want to deliver the kits by the end of February. -aps (20 years ago, 1-Feb-06, to lugnet.robotics)
|
| |
| | Re: studless construction practice
|
|
(...) Wait until you try to take the dang things apart ;-). For studless disassembly, I find a thin sheet of textured rubber invaluable for gripping the pins to pull them out (commonly used for opening stubborn jar lids). This does point out one (...) (20 years ago, 1-Feb-06, to lugnet.robotics)
|
| |
| | Re: studless construction practice
|
|
I've recently got back into technics.. and got a few of the 2004/05 kits... my first impression was: "This is Peg-o... not Lego!" after my first 4 hour session of building the 8436 truck.. my fingers were really sore from inserting so many little (...) (20 years ago, 20-Jan-06, to lugnet.robotics)
|
| |
| | Re: What I would do (2)
|
|
(...) Absolutely. I think the design of the NXT NQC should be dependent on the standard firmware just as NQC was based on the RCX firmware. David nailed exactly what I'm interested in. Even when using NQC it still **feels** like I'm writing in C. It (...) (20 years ago, 1-Feb-06, to lugnet.robotics)
|
| |
| | Re: What I would do (2)
|
|
(...) Definitely performance! Trying to porting an old RCX program to the NXT would be near impossible -- everything is so different there. Just as you'd have to totally rebuild your robot, you have to do a total rewrite of your code anyway. So (...) (20 years ago, 1-Feb-06, to lugnet.robotics)
|
| |
| | Re: How many people signed up for the NXT Developer's Program?
|
|
(...) Following Bert van Dam: (URL) would investigate a self-learning robot with NXT via a wireless connection to my computer as a father-son project. (20 years ago, 1-Feb-06, to lugnet.robotics)
|
| |
| | Re: What I would do (2)
|
|
(...) Oh, performance! NXT NQC should match the NXT brick's capabilities. How many people have such sophisticated programs that they need to port from the RCX to the NXT to realisically demand compatibility? I mean this a robot hobby tool. Half the (...) (20 years ago, 31-Jan-06, to lugnet.robotics)
|
| |
| | Re: What I would do (2)
|
|
(...) The optimum solution would be both - provide a new API that gets the most out of the new firmware, but an optional "compatability layer" that adds what is necessary to provide an API compatable with the RCX. Note that I'd vote to get the new (...) (20 years ago, 31-Jan-06, to lugnet.robotics)
|
| |
| | Re: What I would do (2)
|
|
(...) As the brick, sensor, motors... are quite different, direct portability is not of paramount importance for me. So I vote for performance. Philo (20 years ago, 31-Jan-06, to lugnet.robotics)
|
| |
| | Re: What I would do (2)
|
|
(...) I like this concept, but what if in the case of NQC the new firmware turns out to be such a radically different design that it makes it extremely difficult, if not impossible, to carry over very much of the rather large API built into NQC to (...) (20 years ago, 31-Jan-06, to lugnet.robotics)
|
| |
| | Re: What I would do (2)
|
|
(...) <snippage> (...) Ed, can you point me to the sort of things you have read which make you believe the NXT software and its underlying firmware will provide the sort of control and flexibility which such things as NQC and alternate firmwares (...) (20 years ago, 31-Jan-06, to lugnet.robotics)
|
| |
| | Re: Feb. Wired is out
|
|
(...) Great article, with some good pictures. Also online at: (URL) a sidebar on Lego Factory, Paul Sinasohn LUGNET #115 BAYLUG (20 years ago, 30-Jan-06, to lugnet.robotics, lugnet.mediawatch)
|
| |
| | Re: Using NXT in a name - legal?
|
|
(...) NeXT Software was the company, NeXTcube and NeXTstation were the two machines, and NeXTSTEP was the OS. After Apple acquired NeXT (it's more the other way around, actually), a lot of the NeXTSTEP features carried over into Mac OS X, such as (...) (20 years ago, 30-Jan-06, to lugnet.robotics, FTX)
|
| |
| | Re: Using NXT in a name - legal?
|
|
(...) Steve, do you think TLG would object to leJOS NeXT? Legally I it should be okay, since I don't think people can trademark a common word like 'Next'. I'm not sure if capitalization of letters matters with regards to trademarks though. Someone (...) (20 years ago, 30-Jan-06, to lugnet.robotics, FTX)
|
| |
| | Re: NXT and FLL
|
|
(...) I've also been involved as a coach/mentor since FLL was introduced to our small country. And as a matter of fact I even won the Adult Coach/Mentor Award last year (URL) soon as I can get hold of one of the Mindstorms NXT, I would ask the kids (...) (20 years ago, 28-Jan-06, to lugnet.robotics)
|
| |
| | Re: What I would do (2)
|
|
(...) Didn't say it was! :-)! (...) Bingo! (...) I'm running it now and its quite a nice little OS. Like we both said, the real work is just asking tasks to manage the specific resources of the NXT. (...) Again, totally agree (as I stated in my last (...) (20 years ago, 27-Jan-06, to lugnet.robotics)
|
| |
| | Re: What I would do (2)
|
|
(...) The processor speed (even underclocked) will not be an issue. There real issue which I see many people have talked about is the amount of memory will be in the NXT. On the website for uCOS-II there is a RAM calculation (for the Intel 80x86 (...) (20 years ago, 27-Jan-06, to lugnet.robotics)
|
