 | | 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)
|
| |
| | Useful Track and Electrical Data
|
|
Regular browsers of Brickshelf might have noticed that I added a new track plans section to my gallery: (URL) the 9V folder (URL) there are useful modules such as Curves (URL) and Double Bends (URL) , conforming to various minimum radii depending on (...) (20 years ago, 25-Jan-06, to lugnet.trains, lugnet.loc.uk, lugnet.cad, lugnet.robotics.rcx)
|
| |
| | Re: Using NXT in a name - legal?
|
|
(...) Would you like to join our project? :) We're still in planning/design mode, so additional input is always good. (20 years ago, 27-Jan-06, to lugnet.robotics, FTX)
|
| |
| | Re: Using NXT in a name - legal?
|
|
(...) ... (...) As it turns out, I just started on a project like that. I intentionally went out of my way to avoid using the letters N, X, & T right NeXT to each other. My totally unofficial opinion would be something like this. There's not much (...) (20 years ago, 27-Jan-06, to lugnet.robotics, FTX)
|
| |
| | Re: Using NXT in a name - legal?
|
|
(...) Is the RCX.NET project's name technically a trademark violation? I just started working with José David Parra on a redesign of his original namespace, so now maybe he'll have to rename it, too. :) What's LEGO's position on code namespaces, (...) (20 years ago, 27-Jan-06, to lugnet.robotics, FTX)
|
| |
| | Re: Using NXT in a name - legal?
|
|
(...) Thanks, Steve. At least Lego made it easy for us to play around with the letters to come up with a new name, as Philo mentioned in this thread. :) - Brian (20 years ago, 27-Jan-06, to lugnet.robotics)
|
| |
| | Re: What I would do (2)
|
|
(...) power) and has 64k of memory. How much runtime state can you really process with 64k after the kernel and sensor/motor processes are loaded? Maybe more than I think... Btw, thanks for the document! The current paradigm in RTOS design seems to (...) (20 years ago, 27-Jan-06, to lugnet.robotics)
|
| |
| | Re: remote control and rcx
|
|
(...) hey thanks dave hopefully i can run some tests as soon as my new rcx arrives. but i'll give it a shot. i'll be posting any progress so u'll know how it goes LeE (20 years ago, 27-Jan-06, to lugnet.robotics)
|
| |
| | Re: What I would do (2)
|
|
(...) I'll add it to my tool belt if it'll run on Linux ;) I certainly don't mean to slight the NXT software (I haven't even played with it yet). I assume it will be quite capable. (...) Indeed. Programming languages are simply tools. They should be (...) (20 years ago, 27-Jan-06, to lugnet.robotics)
|
| |
| | Re: What I would do (2)
|
|
(...) Very good point! So one design goal/guiding principle would be try not to break brickOS programs for NXT and provide if nessecary a easy software upgrade path. (...) I would really like to point out (to the general audience) what I see as a (...) (20 years ago, 27-Jan-06, to lugnet.robotics)
|
| |
| | Re: What I would do (2)
|
|
(...) I would be in favor of having a port of BrickOS for NXT (instead of having another thing to learn). I'm not gonna throw away my RCXs and I would prefer having similar languages for both bricks. Yes programmers would need to know the nuances (...) (20 years ago, 26-Jan-06, to lugnet.robotics)
|
