 | | Re: makelx issues
|
|
According to Luis Villa: (...) I'll post the new version this weekend, then ;-) (...) It will be for convenience only with the new release - all front- and backends are integrated, so it's only Make that needs to know about program locations. (...) (25 years ago, 5-Nov-99, to lugnet.robotics.rcx.legos)
|
| |
| | RCX motor voltage
|
|
I've completed a syncro drive model to be RCX controlled and have encountered an unexpected barrier. The model's drivetrain was tested using a battery box (6 AAs) and works fine. But when I try to drive it with the RCX it doesn't have enough power (...) (25 years ago, 5-Nov-99, to lugnet.robotics.rcx)
|
| |
| | Networking
|
|
I saw mention of adding UDP support to the legOS Network and was curious if anyone had started work on it. I'd like to start a project where multiple RCXs communicated with each other and could communicate learned information to each other. The (...) (25 years ago, 5-Nov-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: makelx issues
|
|
(...) Hmm. Well, I'll put off testing on windows then- I don't have permission (I don't think) to put perl on those boxes. (...) It turns out that just putting the legOS/util in the path did the trick. I had asssumed that was just for convenience, (...) (25 years ago, 5-Nov-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: New pbForth 1.1.0
|
|
(...) It's not that hard, and it's not really a secret....I'll email the source as a zip to you in the next few days, OK. I just realized that the only place RCX_ECHO RCX_EMIT, and LCD_4TH are documented are on this list! (...) The RCX has 32 of (...) (25 years ago, 5-Nov-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: makelx issues
|
|
Hi Luis, (...) I rewrote makelx-back - it's called makelx now, and it doesn't require perl anymore. I just didn't post it yet, as it didn't merit a 0.2.2 release just yet. At least in my eyes. For now, try and insert a line into makelx that prints (...) (25 years ago, 5-Nov-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: New pbForth 1.1.0
|
|
(...) It works fine. It even worked with my own "no-echo" terminal. Best part, of course, it's that nice splash "4th" ;) (...) Well, I'm really would like to see sources, if it not a secret. I would not mind about "cleanest", perfection is very (...) (25 years ago, 5-Nov-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Communication with PC using NQC
|
|
Hi all! Having a touch of flu, I might be asking a FAQ here... if so, sorry. How can the RCX communicate with the PC, except by SendMessage? The Spirit.ocx has the Poll functionality to ask for RCX state - is there any similar stuff in NQC? And are (...) (25 years ago, 5-Nov-99, to lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
| |
| | Updating the Web based compilers?
|
|
Would it be possible for any of the very kind people who maintain the LegOS Web Based Compilers be able to update their compilers to the latest 0.2.1 version of LegOS? Dying to try out the new programming features... Dave Chen (25 years ago, 5-Nov-99, to lugnet.robotics.rcx.legos)
|
| |
| | makelx issues
|
|
I'm trying to use 0.2.1 and having problems- no executables are appearing in the demo/ directory. Stepping through the make, I can see that the .dc1, .dc2, etc. files are being made (whether or not correctly I have no idea.) Running make-lx (...) (25 years ago, 4-Nov-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: 0.2.1 API
|
|
Never mind- did it myself. Thanks anyway... -Luis (...) ###...### Profanity is the one language that all programmers understand. -Anonymous ###...### (25 years ago, 4-Nov-99, to lugnet.robotics.rcx.legos)
|
| |
| | 0.2.1 API
|
|
I seem to remember that someone here installed doxygen and generated a new set of API docs for 0.2.0. Am I correct in that? Or am I smoking something? If that is the case, I'd love to hear from you- a copy would be real nice to re-link from the (...) (25 years ago, 4-Nov-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: New pbForth 1.1.0
|
|
(...) Thanks! How does it work for you? I'll put in some release notes on the website in a few days. (...) I took the sources out for now until I can really clean them up. If you REALLY need them, I can email them to you. Next on the block is (...) (25 years ago, 4-Nov-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Connecting two RCX's
|
|
|>I have two RCX bricks and would like them to co-operate without using the |>IR-Port. Is it possible to communicate by attaching a motor port of the |>first RCX to a sensor port of the second? As far as I know the motors work |>on 9V and the (...) (25 years ago, 4-Nov-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: New pbForth 1.1.0
|
|
Hi Ralph, Nice to see a new release! Only question, why did you remove sources from the package? Would be really nice if you can publish the sources too. Sergey Udovenko (25 years ago, 4-Nov-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | rcx tools setup
|
|
I have following problem with setting up the rcx tools (the old ones, distributed with legOS-0.1.7): I set up the Makefile.common to properly point to my paths: TOOLPREFIX=/home/eri...tachi-hms- LEGOS_ROOT=/home/eri...gOS-0.1.7/ when I run make I (...) (25 years ago, 4-Nov-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: RCX-enhanced egcs
|
|
I just downloaded the new rcx tools, unfotunately the gcc dies (segmentation fault, even if I run the gcc only (with no parameters). any ideas what's going on? does it require glibc2.1? any settings? TIA erik (...) (25 years ago, 4-Nov-99, to lugnet.robotics.rcx.legos)
|
| |
| | New pbForth 1.1.0
|
|
Finally, the pesky stack bug and the goofy double echo byte problem has been fixed. Thanks to Sergey Udovenko I have also integrated a little "splash screen" on the LCD that lets you know pbForth is up and running. (URL) Will get you there. Please (...) (25 years ago, 4-Nov-99, to lugnet.robotics.rcx.pbforth, lugnet.robotics)
|
| |
| | Re: Connecting two RCX's
|
|
(...) Another case would be where you also want to use IR for doing radar. If you had IR messages bouncing around for both radar and communication, it might confuse the radar algorithm or generate incorrect readings. (You'd also have to reserve a (...) (25 years ago, 3-Nov-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Connecting two RCX's
|
|
(...) For example if your RCXs are facing opposite direction or if there is a door between them, etc. etc. In such case a wire would be better than IR. Ciao. Marco. (25 years ago, 3-Nov-99, to lugnet.robotics.rcx.nqc)
|
