 | | 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)
|