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