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