 | | 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)
|
