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