 | | Re: Roboarm.nqh
|
|
I was using the RcxCC program. I put the nqh file in the RcxCC directory and everything worked fine. Thanks for the information. By the way, I am really enjoying your book. I hope everyone gets a chance to read and use it. -- Bob Fay (...) (25 years ago, 22-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Roboarm.nqh
|
|
(...) The idea behind including files is that it allows a common set of definitions and/or functions to be shared by multiple programs. NQC by default searches the current directory for any include files. It is also possible to specify a search path (...) (25 years ago, 22-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Roboarm.nqh
|
|
I am working my way through Dave Baums' Mindstorm book and I have lost my way regarding the #include command. The roboarm1.nqc program calls for roboarm.nqh to be included. The program will not compile because it "cannot open roboarm.nqh". Some (...) (25 years ago, 22-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Can't compile test.nqc
|
|
(...) There is very little difference in the compiler itself between 1.0 mode and normal mode. Most of the changes are due to a new API file that is included (rcx_nqh.h). If something went wrong with building this file, that may cause a crash. To (...) (25 years ago, 20-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Can't compile test.nqc
|
|
Hi, I have been trying to compile NQC (2.0.2) with the watcom compiler under QNX and succeded partialy. I can now compile the test.nqc from version 1.3 in backward compatibility mode (bin/nqc -1 testv1.nqc). But I can't compile the new test.nqc (...) (25 years ago, 20-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: How did you made nqc?
|
|
I second that. Thanks for the explanation. It made a good after word for your book! (...) Joel Shafer joel@connect.net (25 years ago, 16-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: How did you made nqc?
|
|
(...) Yes, a lot of work...which is why the "iteration" part was so important. Individually, none of the steps were too time consuming, and each had a lot of positive feedback associated with it...which served to motivate me for the next step. The (...) (25 years ago, 16-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: How did you made nqc?
|
|
(...) Thanks for your reply, this exactly what I (and probably others) wanted to know. It seems that it took a lot of work, time and knowledge... Thanks again ! Philippe (25 years ago, 15-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: How did you made nqc?
|
|
(...) I started to compose a reply, but it wandered a bit off-topic and was getting quite long. I posted the resulting text here: (URL) this the sort of thing you were looking for, or perhaps more in-depth explanation of some of the algorithms used, (...) (25 years ago, 14-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | How did you made nqc?
|
|
Hello ! Being a fervent user of NQC, (thanks mr Baum!) I'm asking myself how nqc has been made. I know it's a very complex topic, but some explication for non programming-specialists could be very interesting. And because the rcx has quite limited (...) (25 years ago, 13-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | RIS 1.0 Sightings
|
|
If anyone is wanting them, I'm still seeing RIS 1.0 systems with the 'upgrade to 1.5' sticker on them at most the local Best Buys in NE Kansas (IE Topeka and Overland Park Areas) Tom (25 years ago, 13-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: RIS 1.0 vs 1.5: which more "desirable"?
|
|
(...) Sorry, should have said the command console, which does use the VB stuff, and also (of course), sending anything yourself from VB... (25 years ago, 12-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: RIS 1.0 vs 1.5: which more "desirable"?
|
|
(...) That's not true. Neither NQC nor LegOS require any vbx files. (25 years ago, 12-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Implementing Finite State Machines
|
|
Dave, I like the idea of teaching how to solve certain problems both with multiple threads and with a Finite State Machine. Adding "switch" would be great! Personally I think that a plain 'C' FSM using switch can be made to look very clear if (...) (25 years ago, 12-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: RIS 1.0 vs 1.5: which more "desirable"?
|
|
(...) The problem is that 1.5, does not have the vbx file to allow these to work. You have to get this from a version 1 system. (...) 1.5, adds quite a few useful pieces, but loses a few others. Having '1' upgraded, gives you the best of both (...) (25 years ago, 11-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Implementing Finite State Machines
|
|
(...) [snip] (...) FSMs are a boon in our behavioural robotics projects. If you have read the Rod Brooks papers, he uses them to implement subsumptive architectures in his "radical" robots. I have used them a LOT in my Stamp II robots as the only (...) (25 years ago, 11-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Implementing Finite State Machines
|
|
(...) Adding a switch statement to NQC would certainly help make implementation easier...I'll see if I can work it into the next release. Actually, I've been somewhat surprised by the general lack of needing FSMs in my own Mindstorms programming. I (...) (25 years ago, 11-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Implementing Finite State Machines
|
|
Vlad, The Finite State Machine is a good subject for people to consider in robotics, especially in coding the typical 'looping forever' Rcx applications. Lots of regular 'C' FSM's are implemented with a State variable and "switch" statements, or (...) (25 years ago, 11-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: "No reply from RCX" with nqc...
|
|
(...) thank you (and bob fay) for your two responses. i have a sneaking suspicion that bob was right on with the curious battery problem. i opened my tower battery case and "re-seated" the battery. (and i confirmed it *was* in the proper (...) (25 years ago, 9-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: "No reply from RCX" with nqc...
|
|
(...) Try this: nqc -v -raw 10 and then also this (substituting the right filename) nqc -v -firmware <filename> and post the results. The "-v" option turns on some logging that may help us figure out what is wrong. (...) The firmware file is (...) (25 years ago, 9-Dec-99, to lugnet.robotics.rcx.nqc)
|
