 | | Re: signals / legOS internals
|
|
(...) When you define a bunch of local variables (more than fit in available registers), where are they? Unless you happen to know the answer, I may have to do some more experimenting. Admittedly, it has been awhile, but the last time I was heavy (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: signals / legOS internals
|
|
(...) Reading this again, I should mention that pushing things on the stack asynchronously is fine, as long as the stack pointer is always in the right place, which is why it must always always always point to the location I mentioned (and seemingly (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: signals / legOS internals
|
|
(...) The stack pointer must always always always point at the bottom of the stack data area, i.e. to the last valid data item on the stack. As a consequence, push val (or mov.w val,@-r7) never overwrites data. When an interrupt occurs, the first (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | signals / legOS internals
|
|
Peek-a-boo! I've been banging my head against this a bit and thought I'd see if any of you can shove me in the right direction. I am trying to implement signals in legOS. The problem is that a signal can happen at any time. I know how to make that (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: IR questions
|
|
(...) Only transmitting keeps the tower alive, at least according to my tests. If absolutely necessary, an occasional 0xff sent by the PC will keep the tower alive; this will result in only a start bit being sent, which ought to occupy very little (...) (25 years ago, 22-Jun-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | IR questions
|
|
This is a whole bunch of IR questions, which come from my first serious fooling around with the IR. Since some of these are legOS or Linux specific, I've cross-posted- I hope no one is too offended. 1) Despite putting the bot in an infinite while (...) (25 years ago, 22-Jun-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: legOS make newbe question
|
|
(...) I'm sorry it took so long to reply, Phil, but as a non-windows user, well, I didn't see much in the initial messages that led me to think I could help. From what I've seen, this is the cause of the error- the two Makefiles (Makefile and (...) (25 years ago, 22-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: www.legOS.net, maybe?
|
|
(...) Markus, It might be a good idea to carefully review the LEGO Group's policies on domain names, possibly even retaining an attornery if you are serious, or contacting TLG attorneys with specific questions. Note that TLG's "Fair Play" page (URL) (...) (25 years ago, 21-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blocking IR
|
|
Hi Kekoa, Could you post your working IR .srec code or email me if possible? I have tried the examples with the LegOS read sensor routines and I still get the same results. i.e. it works at about 2mm from the unit but fails after more than 5mm. I (...) (25 years ago, 21-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: www.legOS.net, maybe?
|
|
Well, for at least one year (possibly two) I can keep binaries and other large items on arthurdent (which is where the HOWTO and my Debian binaries are kept.) Let me know if you want space... -Luis (...) ###...### Profanity is the one language that (...) (25 years ago, 21-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: www.legOS.net, maybe?
|
|
(...) ??? Are you sure: I just looked, and they appear to redirect to some other site ((URL) who give you 20 MB and register you at InterNIC - but here's the catch: InterNIC will bill you! There's also a 1.2 MB file size limit (which may or may not (...) (25 years ago, 21-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | www.legOS.net, maybe?
|
|
Hello, sorry for being out of touch. I just stumbled across a service called www.registernic.net. Apparently, they are handing out .com, .org and .net domains and 6MB of webspace free for two years. They register in your name, and they don't even (...) (25 years ago, 21-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blocking IR
|
|
I'll have to wait now till I get home from work to try the examples :( Phil (...) (25 years ago, 21-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS make newbe question
|
|
Thanks for all of your help. I am surprised also, I thought alot of others were successfully using legOS and thought there would be someone who had gone through this. I checked as you said, and c, c++ and mint are in the legOS.0.1.7 lib directory, (...) (25 years ago, 21-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blocking IR
|
|
In addition to what I mentioned in the previous message, I also set the sensor input port to active. Setting it to passive also works, in which case the ambient light level seems to be around 480-495, and the sensor aimed directly at the IR port (...) (25 years ago, 21-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blocking IR
|
|
(...) So I just tried this, and it took more than a few minutes to get it to work. But it does work. Apparently, the modulation of the IR signal is needed for the light sensor to give a reading. The standard modulation used during regular IR (...) (25 years ago, 20-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blocking IR
|
|
(...) I doubt you have a broken RCX. If you did, firmdl.c would not download firmware correctly. (...) That is a good thing to try; I suppose it did not help things? (...) I don't see why you couldn't post the .srec file. I don't know if you also (...) (25 years ago, 20-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS make newbe question
|
|
(...) Too bad nobody who actually uses LegOS is speaking up. I was under the impression you weren't supposed to move any makefiles around, and that you were just supposed to edit the appropriate makefile (probably Makefile.common) and type make at (...) (25 years ago, 20-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS make newbe question
|
|
I've got it making the first-c++.o file now, but it chokes because it can't find the first-c++.coff file. Probably because it's not being made for some reason. Here is the current make message: snip-- C:\legOS.0.1.7>make h8300-hms-ld -T h8300.rcx (...) (25 years ago, 20-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blocking IR
|
|
Thanks for your help but I think I might have a broken RCX. The code I've been testing and the examples you have help me with all work if I place the light sensor about 2 mm from the IR transmitter. At about 2cm it no longer works at all. I have (...) (25 years ago, 20-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS make newbe question
|
|
Thanks for helping me through this, but nope, That was a mistake when I typed it into the message. The makefile.common has the slashes placed as you show them.. I put Makefile.common and makefile into the LegOS demo directory, Is this the correct (...) (25 years ago, 19-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS make newbe question
|
|
(...) What if you change the \ to a /, and add a trailing /, as in: LEGOS_ROOT=/cygnus/c...gOS.0.1.7/ -Kekoa (25 years ago, 19-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS make newbe question
|
|
Thanks, make -v GNU Make version 3.75, by Richard Stallman and Roland McGrath. Copyright..... Report bugs to..... C: -Phil (...) (25 years ago, 18-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS make newbe question
|
|
(...) For starters, how about the output of "make -v"... -Kekoa (25 years ago, 18-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | legOS make newbe question
|
|
I've tried so many times to get LegOS running, but sure I have problems with the Makefile.common Any help from you experts would be greatly appreciated. BTW, I have some experience with gcc and makefiles, and was able to get the paths correct for (...) (25 years ago, 18-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blocking IR
|
|
Regarding your program. Try sending 0s, not xs, i.e.: char *buffer = "\0\0\0\0\0"; Zeros are coded with the IR on 91% of the time, while xs are coded with the IR on only 45% of the time, neglecting the modulation, which cuts that all down by half. (...) (25 years ago, 16-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blocking IR
|
|
Here is some code for IR detection, with the help from Kekoa. However it doesn't work. I know the hardware is all working because if I run minicom and then run this programme and point the RCX at the lego tower junk appears on the screen. If I take (...) (25 years ago, 15-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Announcement: OnScreen Programming for Legos RCX
|
|
(URL) readme.txt (ASCII version of web page, note some of the content reads especially better on the web, or using a fixed spaced font): OnScreen Programming version 1.0 for Lego Mindstorms Once installing this system, the Lego Mindstorms RCX can be (...) (25 years ago, 15-Jun-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | emulegOs ported to Linux/Unix platforms
|
|
Mark Falco completed the first port of emulegOS to the Linux/Unix platforms. He did the gui with Tcl/Tk, a popular scripting tools available for many platforms including Win and Mac. This version will probably become the *standard* version of (...) (25 years ago, 14-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Lego Network Protocol questions
|
|
Ralph Hempel wrote in message <000001beb0e4$f9d0df...pro150>... (...) I'll back you up on this as well. I did some experiments using two towers connected to two different PCs, and found that I could send raw bytes from one PC to the other without (...) (25 years ago, 14-Jun-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: Blocking IR
|
|
Great, I'll try this out tonight. Many Thanks, Phil. (...) (25 years ago, 14-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Are there any limitations/restrictions on releasing legOS compiled programs (.srec files)?
|
|
I am not a lawyer, but I have been interested in license issues for some time. Because LegOS is basically a library and not really an OS, and because it is compiled in with the rest of your code, technically speaking you must release code to anyone (...) (25 years ago, 14-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Are there any limitations/restrictions on releasing legOS compiled programs (.srec files)?
|
|
Are there any limitations/restrictions on releasing legOS compiled programs (.srec files)? I'm aware that legOS itself is MPL (Mozilla Public License), but are the programs that are compiled with it, and contain a portion of it, subject to open (...) (25 years ago, 13-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blocking IR
|
|
(...) I forgot to mention. At the top of dir_write, you probably want to add: if (dir_tx_state == TX_ACTIVE) return -1; Or something to that effect, so you don't transmit a second message while a first is still transmitting, and so you have a way of (...) (25 years ago, 10-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blocking IR
|
|
(...) Do you mean dir_write? This is a problem with LegOS only. If you want non-blocking writes, comment out (in version 0.1.7 at least): while(dir_tx_state==TX_ACTIVE) ; // FIXME: scheduler integration if(dir_tx_state==TX_OK) return len; // (...) (25 years ago, 10-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Blocking IR
|
|
Before I start trying to do this, does anyone know why the LegOS function write_ir is a blocking function? I'm trying to write an IR detection system but am unable to do so in LegOS because every time I write a byte to the IR port the RCX locks up. (...) (25 years ago, 10-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: arbitrary motor allocation
|
|
(...) Why does the code need a case statement? What interface are you looking for? void motor_dir(motor, dir) and motor_speed(motor, speed)? I missed the previous discussion. This is easy to implement, with no major changes to the code, just an (...) (25 years ago, 9-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | arbitrary motor allocation
|
|
If I recall correctly, there was some discussion of a rewrite of the OS's motor code so that arbitrary motors could be assigned by the code without the need for a large case statement in user code. Has that happened? Is it happening? Can I help? (...) (25 years ago, 8-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: Lego Network Protocol questions
|
|
(...) I'll back you up on this. My pbFORTH sends a simple character stream and it seems to work fine. No complements are necessary. I sure would like to be able to keep the RCX tower alive, though. I wonder if it's the character going through that (...) (25 years ago, 7-Jun-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | tm-and-ir (again)
|
|
Hi all, I've been using Legos without any major problems but never got the tm-and-ir demo to work properly. I can receive characters on the RCX fine but when the 'view' button is pressed (within 3 seconds) the results are normally junk on the screen (...) (25 years ago, 7-Jun-99, to lugnet.robotics.rcx.legos)
|
