 | | libm, windows
|
|
has anyone had success with using libm in windows? I have legOS programs written from a solaris machine that compile fine and work when downloaded to the RCX, but I have not been able to compile them on a windows machine due to linking problems. The (...) (23 years ago, 24-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: BricxCC release 3.3.3.4
|
|
hi John, (...) great ! (...) even better ! (...) Well ok, but another way could be to monitor it's output (in the past in generated .....) and to shut it down when no more ... arrive. So the timeout parameter can disappear totally. I don't critize (...) (23 years ago, 23-Jan-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Rail Racers track operation details
|
|
I have finally documented how the current Rail Racers race track is controlled and configured. I hope to had more detailed information on each individual component soon, as well as the source code for the RCXs (developed in NCQ). The basic overview (...) (23 years ago, 23-Jan-02, to lugnet.robotics.rcx, lugnet.trains, lugnet.general) !
|
| |
| | Re: BricxCC release 3.3.3.4
|
|
(...) Hmmm. I'm guessing here. Does your main window fill the entire screen when it starts up? Does the restore/maximize button contain an image that looks like a box with a dark black bar across the top? Or does the restore/maximize button contain (...) (23 years ago, 23-Jan-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: BricxCC release 3.3.3.4
|
|
Hi John, Sorry for the incorrectness: "the upper right restore/maximize button still doesn't work" is the button of the Main Window. The child window is working OK. I made also an mistake on the tree request: It should be variables (and not (...) (23 years ago, 23-Jan-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: BricxCC release 3.3.3.4
|
|
(...) I'm not sure I understand what you mean by "the upper right restore/maximize button still doesn't work". Are you talking about the restore/maximize button on the main BricxCC window or the one on each MDI child editor window? Delphi programs (...) (23 years ago, 23-Jan-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: BricxCC release 3.3.3.4
|
|
Hi John, Wow you are a fast programmer. I just downloaded the new version and will test it. It is really great that this program is adapted to the user wishes/comments. Just one question: I bought a new computer (AMD 1.333 GHz Thunderbird, 512Mb, (...) (23 years ago, 23-Jan-02, to lugnet.robotics.rcx.nqc)
|
| |
| | NQC 2.4 r2 released
|
|
The only major change is the inclusion of USB support for the Macintosh/MPW version of NQC (which requires the driver and libraries from the Mac SDK available at www.legomindstorms.com) (URL) Baum (23 years ago, 23-Jan-02, to lugnet.robotics.rcx.nqc)
|
| |
| | BricxCC release 3.3.3.4
|
|
I've just released a new version of BricxCC. Version 3.3.3.4 implements the following changes: 1. Watching the brick only while the Watch window is active is now an option on the Watch window. 2. It fixes a bug in TFakeSpirit.SetSensorMode which (...) (23 years ago, 22-Jan-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: More RCX's controled by one tower ?
|
|
You cannot program them independantly, but you can make sure your programs respond to different IR messages during normal operation. All RCX's will receive the messages, but as long as only one responds with some action then independant control is (...) (23 years ago, 22-Jan-02, to lugnet.robotics.rcx, lugnet.robotics)
|
| |
| | Re: thread class for legOS
|
|
(...) In the post you replied to saying "static doesn't matter", the proposal was: private: static int runWrapper(...) ; I then replied to your post, etc. Anyway, let's not degenerate into he-said-she-said. We're really just talking past each other (...) (23 years ago, 22-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: NQC 2.4 r1 released
|
|
Its been brought to my attention that Lego has already released the Mac SDK and driver for the USB tower (sorry I didn't see it!): (URL) should be able to post an updated version of NQC with USB support for Mac OS9 tomorrow. Dave (...) (23 years ago, 22-Jan-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: thread class for legOS
|
|
(...) In fact, neither of these suggestions will work with the code as it stands, because the runWrapper() function tries to call the Run() function, which is a non-static member function. You could pass a pointer to the class instance (this) in the (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: thread class for legOS
|
|
(...) Unless you define a function as a member function, there is no this parameter at all. In the example given, it was not a member function at all (nor should it be). I believe you are thinking of a static member function vs. a non-static member (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | RE: firmware
|
|
SDK 2 includes the latest version of firmware and tools to load it to the RCX. It's also included in the new RIS 2.0 CD The new RIS 2.0 is the one with the RCX 2.0 + USB InfraRed Tower + Latest firmware version (you could call it 2.0, yes) You can (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: firmware
|
|
this sdk 2 is the firmware??? -- Paula Berger E-mail: pberger@terra.com.br paula@inf.pucrs.br ICQ#: 71133278 "It's the end of something simple, and the beginning of everything else" -- ----- Original Message ----- From: "Robert Seifert" (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: firmware
|
|
(...) Firmaware is a kind of ?operating system? needed to be downloaded to RCX to allow it process programs. Physically it is file firmxxxx.lgo (where xxxx is a number ) located somewhere in directory tree created by RIS installation process. If you (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.nqc)
|
| |
| | RE: newbie
|
|
If you decide to use LegOS you won't be needing nor will you have the chance to use NQC because a RCX with LegOS loaded won't understand nor respond to any standard firmware commands. Check (if you didn't already) the side links at: (URL) From: (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | RE: newbie
|
|
so if i decide to use LegOS I don't need NQC, right? as I understood, de LegOS itself it's complete to be used alone.... (...) programs on RCX. (...) LEGO (...) could call (...) LEGO (...) standard LEGO (...) for (...) run some (...) don't (...) -- (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
| |
| | RE: newbie
|
|
LegOS is an operation system ( a firmware replacement in itself) It's like a mini UNIX system, that will run true C compiled programs on RCX. NQC on the other hand, all it does is translate a NQC program into LEGO pCode that will be *interpreted* by (...) (23 years ago, 21-Jan-02, to lugnet.robotics.rcx.legos)
|
