 | | 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)
|
| |
| | Re: Lego Network Protocol questions
|
|
(...) So of course I was curious about getting rid of the complements. Apparently, they are not necessary, or so my testing so far seems to indicate. Under the several lighting conditions I tried, and for distances of up to 27' (the farthest I could (...) (25 years ago, 6-Jun-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: Lego Network Protocol questions
|
|
(...) I forgot to mention that one possible deficiency is the complements. They can be eliminated, for the most part, with careful counting of zeros. I haven't done any testing regarding this, so I don't know how many zeros in a row will break (...) (25 years ago, 6-Jun-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: Lego Network Protocol questions
|
|
Regarding the IR protocol, I have elsewhere suggested the following simple low-level format: 1 start, 1 stop, 2400 baud, odd parity 55 f0 f0 L ~L D1 ~D1 .. Dn ~Dn C ~C L is number of data bytes, valid range 1..255, less depending on buffer sizes Dx (...) (25 years ago, 6-Jun-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | RE: Lego Network Protocol questions
|
|
Sorry, I have been out of the loop for quite some time now on the protocol. Next time will someone smack me when I voluntarily take a compiler theory course on top of 3 other computer sciences courses. I had no life for over a month. I am currently (...) (25 years ago, 5-Jun-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: I'm having problems getting legos to compile
|
|
(...) you can specify where the .h files are using the -I switch... maybe you just need to check the Makefile (or Makefile.common) and change some paths there... or: check the configuration of compiler, sorry, I can't help with that... erik (25 years ago, 5-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | I'm having problems getting legos to compile
|
|
on cygwin.. I'm sure it's something I forgot to setup. Can anyone help?? it's complaining that it can't find the .h files.. (25 years ago, 5-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | compilation errors w/ legOS 0.1.7+patches
|
|
Hello all! I just downloaded and installed legOS 0.1.7 and applied all of the available patches. I created a quick program, one which one turns on a motor, sleeps, the returns, and attempted to compile it. This is the error that I get: (...) (25 years ago, 3-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Download at www.multimania.com
|
|
I have all the LegOS files (including reasonably recent egcs and binutils .tar files) here: (URL) As usual, I recommend the LegOS howto for new users- (URL) it helps... (...) ###...### God was my co-pilot, but we crashed in the mountains and I had (...) (25 years ago, 1-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Download at www.multimania.com
|
|
I got exactly the same problem - I cannot get the legos nor other files from the legos site. I always get random sized files (shorter than actual size of files I try to dowanload). somebody help please. I just got the mindstorm and would love to (...) (25 years ago, 31-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | emulegOS: a legOS (and RCX) emulator
|
|
Marco Beri and I just released the first version of emulegOS, a software emulator of legOS and the RCX itself. We like a lot legOS and the way it opens a broad range of possibilities to the RCX, but felt the need of a more comfortable environment (...) (25 years ago, 29-May-99, to lugnet.announce, lugnet.robotics, lugnet.robotics.rcx.legos)
|
| |
| | Re: light values?
|
|
Ah... that makes sense- I didn't realize that power was completely cut. Should have (I'm not *that* incompetent in reading electronics diagrams). Oh well. Thanks for the feedback, John... Luis (...) ###...### God was my co-pilot, but we crashed in (...) (25 years ago, 28-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: light values?
|
|
(...) The light sensor is an active sensor, which means that it requires power to operate. When you call ds_passive, you are no longer supplying power to the sensor between readings. Some people have reported being able to use the light sensor for (...) (25 years ago, 28-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: light values?
|
|
Some months ago, I posted this question, but got no response. I've finally played with it some more this morning and have some observations: 1) After setting ds_active, my light sensor returns values of 0-100, as I should. 2) After calling (...) (25 years ago, 28-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Lego Network Protocol questions
|
|
In lugnet.robotics.rcx.legos, Kekoa Proudfoot writes: [ ... ] (...) To this end, i've started work on a Discrete Event Simulator. The idea is to use this to see the effects of some of the things you mention above. Note that this is not an (...) (25 years ago, 21-May-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Download at www.multimania.com
|
|
Hi, I'm not sure exactly why this is, but for some reason I can't get a binary download to work from .. (URL) .. Whenever I try and download any of the files from this server ( using both a PPP line at home, and the connection at Uni.) I get (...) (25 years ago, 16-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: firmdl question
|
|
(...) I believe the units are tens of firmware bytes downloaded already. Oh, to point out the obvious, this is a ROM thing, not a firmdl thing. -Kekoa (25 years ago, 13-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rom sensor read routine
|
|
(...) The current LegOS model really hammers the sensors, almost to the point of oversampling them. It only takes a short while (less than 0.1 ms, I think) to sample all four sensors; I think LegOS samples the next sensor immediately after finishing (...) (25 years ago, 13-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | firmdl question
|
|
When using firmdl to download a program to the RCX, what exactly do the numbers on the LCD indicate? Are there units I should be attaching to them, or are they just there to indicate progress without specific units? Just curious- Luis ###...### God (...) (25 years ago, 13-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rom sensor read routine
|
|
Hi Kekoa, (...) I am fixing this right now. (...) The current legOS sensor read cycle is this (i=illuminate, c=A/D conversion) S1: iii iii iii ccc S2: ccc iii iii iii S3: iii ccc iii iii S4: iii iii ccc iii If you find your sensor 2 readings to be (...) (25 years ago, 2-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Lego Network Protocol questions
|
|
(...) I believe transmission and reception are independent, i.e. the emitter circuit is decoupled from the receiver circuit. The hardware on the H8 is full duplex. Once you finish sending a byte, I think you get two interrupts: one saying a byte has (...) (25 years ago, 5-May-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Floating point emulation
|
|
I succeeded in using (emulated) floats in a legOS program. Here are some instructions in case some of you want/need to try 32 bit FP emulation. First of all I must point out that I have no merit at all in having got this result, a part from having (...) (25 years ago, 5-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Lego Network Protocol questions
|
|
(...) Just to state my interests: I'm mainly interested in the protocol, eg what level of service it would provide etc. In particular, I'm interested in layering a higher level gauranteed delivery protocol atop whatever simple one is provided. (...) (...) (25 years ago, 5-May-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: I'm being stupid. But how?
|
|
Here's the fair play policy: (URL) right. The Lego Group is exceedingly protective of their trademarks and intellectual property. If they haven't pursued action against legOS, it's very likely a deliberate policy rather than an oversight. Jonathan (...) (25 years ago, 5-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Lego Network Protocol questions
|
|
In lugnet.robotics.rcx.legos, Ralph Hempel writes: [ ... ] (...) This is actually the book from which the thoughts I posted about arose. It is, indeed, a great book ;-) (25 years ago, 5-May-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: I'm being stupid. But how?
|
|
(...) Considering the past history of TLG, I'd say the fact that they haven't said anything about the name LegOS says a lot. TLG is paranoid about their trademark. Use Lego like a noun (as in, "I liked Legos a lot when I was a kid," or "I play with (...) (25 years ago, 4-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: I'm being stupid. But how?
|
|
(...) Lego's always been a bit of a hobbyist's thing[1] so probably even TLG thinks there isn't much point in siccing lawyers on us, even if they disapproved. Big companies[2] lawyering hobbyists is really bad PR :) [1] not in any way derogatory, (...) (25 years ago, 4-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: HOWTO v 0.1
|
|
(...) Not ATM. (If I get gdb actually *working* with the LegOS I'll do a little HOWTO for that and stick it on the web, though... has anyone got it working right yet? I'm not stuck or anything, I just haven't finished getting it running.) (25 years ago, 4-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | tm-and-ir.c
|
|
Is anyone else having problems with this? The receive and display part works fine but it won't send "Hello World" when I press the View button. The srec from the LegOS home page works fine but if I build it myself it doesn't. I've tried both the web (...) (25 years ago, 1-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: I'm being stupid. But how?
|
|
(...) Hahaha, regarding that LegOS is more of a library than an OS, my opinion too. But you have to admit the name has some appeal, even if it is something of a misnomer... :) Clearly it says something about TLG's attitude toward LegOS that they (...) (25 years ago, 3-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: HOWTO v 0.1
|
|
(...) Thanks (I think...) (...) Because I've found that it is significantly faster, and nearly canonical (as, technically speaking, it is part of the same domain, despite being hosted elsewhere(Stanford, IIRC.)) The only reason I found it in the (...) (25 years ago, 3-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | I'm being stupid. But how?
|
|
I've written a test program using the 19990330 LegOS snapshot[1], and it's misbehaving oddly. The program looks like this: (the headers are the result of my frobbing the LegOS headers to refer to <mindstorms/{legOS header}>...) #include (...) (25 years ago, 29-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: HOWTO v 0.1
|
|
(...) Not half bad IMHO. But why point egcs searchers at ftp://go.cygnus.com/...gcs-1.1.2/ ? The canonical site is ftp://egcs.cygnus.co...cs-1.1.2/. egcs-1.2 will be out fairly soon. There have been changes to the h8300 support, but the changes are (...) (25 years ago, 29-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Read me first! Re: case statement doesn't work- any clue?
|
|
Nevermind. Dangit. Forgot break statements like a moron. -Luis (...) ###...### God was my co-pilot, but we crashed in the mountains and I had to eat him. -bumper sticker ###...### (25 years ago, 3-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: case statement doesn't work- any clue?
|
|
(...) Doh! You haven't put any breaks between the cases. BTW, if LegOS can change the semantics of C its cleverer than I thought ... :-) Cheers, Ben. -- (URL) grandfather once told me that there are two kinds of people: those who work and those who (...) (25 years ago, 3-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | case statement doesn't work- any clue?
|
|
I'm trying to program some very rudimentary debugging stuff- just outputting variables to the screen. Basically, I want to use a switch/case statement to read an integer variable (in this case ID_number) which is then linked (by the case statement) (...) (25 years ago, 3-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Lego Network Protocol questions
|
|
(...) Oops, I must've just caught the tail end of the conversation. I assumed the standard [lame] lego protocol was being discussed, not a custom protocol. Sorry. Dave (25 years ago, 2-May-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | RE: Lego Network Protocol questions
|
|
With all of the talk about networking and IP embedding and such, and since I'm working on a proprietary '485 master/slave protocol for a client, I had to dust off a GREAT university text on networks. It devotes an entire chapter to ALOHA and slotted (...) (25 years ago, 1-May-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: Lego Network Protocol questions
|
|
(...) Dave, did you catch the crosspost from lugnet.robotics.rcx.legos? I think there were details discussed there that may or may not have amounted to a fairly specific proposal for a protocol for LegOS. Anybody care to summarize whatever was (...) (25 years ago, 1-May-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: Lego Network Protocol questions
|
|
(...) Transmit whenever you feel like it and hope you didn't obliterate data coming from the other direction. Rudimentary, but still quite effective given the typical use pattern with is host driven command/response. With RCX to RCX communication (...) (25 years ago, 30-Apr-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Lego Network Protocol questions
|
|
Hi all. I came to the discussions on the LNP a bit late and was wondering if the following questions had been discussed (I flipped through an old Communications course book and noted some thoughts): - Can we do Carrier Sense *whilst* we are (...) (25 years ago, 30-Apr-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: IS free()'s operation atomic?
|
|
(...) I agree, free() is not ISR safe. One thread can get preempted after the check but before the store, and a second thread can adjust mm_first_free, making the first thread's check invalid. -Kekoa (25 years ago, 29-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | IS free()'s operation atomic?
|
|
Hi all I think that free() operation in mm.c is not ISR safe in multitasking mode. This operation is not keep coherence about value of mm_first_free,is it? ---...--- in mm.c ---...--- // for task safe operations, free needs to be // atomic and (...) (25 years ago, 29-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Rom sensor read routine
|
|
In writing some sensor code yesterday/today (it's 6 am), I passed over the ROM sensor code at 14c0. The documentation has been put in the usual place. The rotation code is pretty simple: the expected state machine, with split points between the four (...) (25 years ago, 25-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) given (...) lego (...) [ stuff about lego/native collisions ] (...) of a (...) on (...) I was wondering, since people are considering using tags in the LNP frame to signify local to local messages, could we not also use this to "label" non (...) (25 years ago, 23-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) In my brief experimentation with rom_reset(), it does not actually clear the rom- rather it only starts the program over again (in main()). Is this intentional? I get this behavior when calling it from main- when calling it from within another (...) (25 years ago, 21-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation sensor bug found
|
|
(...) This seems the best approach to me too. My problem is I don't know if I am able to do such a thing :-) (...) I know your site and know you've done a LOT of hard work to understand and explain both RCX hardware and original firmware code. Mario (25 years ago, 21-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) That's what I am doing. Markus. (25 years ago, 21-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) Hmm.. with a little hacking you could certainly detect logic errors. The main problem I think would be writing alternative C-Functions for the H8 assembler, which makes up legOS itself. You'd also need to create a simulator engine for legOS to (...) (25 years ago, 21-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) The first instruction (at 03ae) places the stack in on-chip memory, assuming RAME bit of SYSCR is at its initial value of 1. Why not make rom_reset() disable interrupts, then do its thing? That would be the safest thing to do. -Kekoa (25 years ago, 21-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) Well, if rom_reset() gets invoked near the end of your time slice, ROM has no time to reset the OCIA IRQ vector before the next timer tick. I'm not certain about the order in which ROM sets up data areas and IRQ vectors. legOS freely allocates (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) Assuming packets without large internal gaps, we could employ a timeout to wait for a packet transmission of unknown protocol type to end. At 2400 bps with 8E1 (LEGO, isn't it?), one data byte has 11 bits, so a space of 1.5*11/2400 s should be (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation sensor bug found
|
|
(...) Excellent idea. This would yield the default settings dead-on. (...) Scaling isn't about the final output. The final output is already in the standard format. Scaling is about shifting the raw sensor values displayed by the firmware six digits (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) Yes this will be a datagram only protocol for the time being. The LNP will allow us to do things like debugging and remote control. I have also invisioned something like a "shell" running on the legOS that you could either "telnet" in to or (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation sensor bug found
|
|
(...) Why doesn't somebody finish up the decoding of the ROM, specifically the routine at 14c0. This routine takes the raw sensor samples and converts them to usable values, including handling the temperature and rotation sensors. The standard (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) From what little I remember about the Lego protocol, here are some thoughts. *) On reception, some Lego packets may contain data which look like the beginning of a legOS native protocol frame. Most likely, the checksum would fail (once enough (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) What sort of safety are you referring to? Motors left running? My initial thought was of lost memory or data structures in an indeterminate state, but that would seem to be moot since you are restarting from the ROM, which will have forgotten (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) The interface is specifically datagram only. Dunno about packet reassembly; I doubt it as the philosophy is minimalism. The main advantage I see in it is the ability to change the degree of checking it does on your behalf to ensure packets (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation sensor bug found
|
|
(...) I suppose we could ask for help also to non-legos owners of RCX and rotation sensors. What if any of us posts a message in the robotics newsgroup asking for some reads of rotation sensors? Raw values can be read with the sandard firmware too (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation sensor bug found (maybe!)
|
|
(...) Exactly. I don't have rotation sensors, either. I think these values were originally gathered from Michael Nielsen's sensors. What's the current status? Is there a patch working for everybody, or do we need some calibration work? It would be (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) rom_reset() does the trick, you'll need to #include "rom/system.h". I'm not sure wheter this is safe when multitasking. (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
