|
 | | Re: Ir transmission
|
| (...) Perhaps EMIT? would do (...) I'm nearly done with my NQC to pbFORTH port of the IR proximity detector, but I'm stuck where I have at present got a 30ms delay (Sleep(3) in NQC). I expect it isn't critical but the current detector works so well (...) (25 years ago, 14-Apr-99, to lugnet.robotics.rcx.pbforth)
| |
|  
ir
(score: 1.640)
|
|
| | RE: Ir transmission
|
| (...) Alas, I only used the firmware timers available as core RCX firmware calls. I can look through Kekoa's disassembly to see if there are higher resolution timers available ( I think the motor timers might be useful ) In general, NQC hooks in (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.pbforth)
| |
|
ir
(score: 1.639)
|
|
| | Re: legOS ...
|
| Hi Mark, you might consider joining the legOS mailing list www.lugnet.com. We're currently working on network protocols for the IR device. POSIX compliance is very worthwile. I'm considering to make all devices files. Yes, even sensors. That way, we (...) (26 years ago, 30-Mar-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.639)
|
|
| | Re: gcc build instructions for linux
|
| OK, I have some more information now. When I build 0.1.6 in my new environment it works fine. 0.1.7 and the snap exhibit the problem. The problem is that when using tm-and-ir, the 'view' button (which is supposed to send the message "Hello World") (...) (26 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.639)
|
|
| | RE: Ir transmission
|
| (...) I think its around 16 Mhz for the crystal and 4 MHz for the cycle time. I think there is a msec timer buried in the OC1A handler (see Kekoa's disassembly) I agree that we want something to trigger a run flag instead of having to check the (...) (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.pbforth)
| |
|
ir
(score: 1.639)
|
|
| | Re: Ir transmission
|
| (...) The bytecode interpreter does it, which is what NQC maps to (opcode 43). I'd prefer a timer (or access to a clock) with millisecond resolution rather than a delay because things will get interesting whan multitasking. What is the CPU clock (...) (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.pbforth)
| |
|
ir
(score: 1.639)
|
|
| | Re: Ir transmission
|
| (...) Well, in the spirit of FORTH there should be no finite number, just create and destroy them on the fly as and whan you need them. I have been wandering around the internet looking and found that hForth has one already: \ hForth multitasker \ \ (...) (25 years ago, 17-Apr-99, to lugnet.robotics.rcx.pbforth)
| |
|
ir
(score: 1.639)
|
|
| | loading s/w
|
| After successfully downloading and running tm-and-ir.srec (Linux host), I cannot download to it any longer. Upon power up, the LCD displays LEGO!5 and I can select any other program slots. I could just re-load firmware in '95 but I don't want to (...) (26 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.639)
|
|
| | Re: Making Light Sensor Passive
|
| I'm not sure what you mean by "making light sensor passive". The light sensor, by design, requires power to work. You can tell the RCX that the light sensor is a passive sensor, but you don't get much range in readings - the phototransistor in the (...) (26 years ago, 25-Feb-99, to lugnet.robotics.rcx.nqc)
| |
|
range
(score: 1.638)
|
|
| | Re: gcc build instructions for linux
|
| I got everything to build using egcs 1.1.2, but I am having problems with the tm-and-ir demo (after modifying it for the new execi syntax) which make me think maybe egcs is not generating correct code. I used the build instructions at (URL) did use (...) (26 years ago, 7-Apr-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.638)
|
|
| | Re: loading s/w
|
| (...) I belive LegOS breaks firmware deletion, in the sense that the "delete firmware" opcode is not supported by the IR routines, but I could be wrong about that. If you are using an AC adapter and no batteries, the easiest thing to do is to turn (...) (26 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.638)
|
|
| | Re: loading s/w
|
| (...) I skipped something here. The assumption I made is that you want to load new custom firmware. If you want to load the Lego firmware, find the Firm0309.lgo file in your Mindstorms directory, and load that into the RCX exactly as you would (...) (26 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.637)
|
|
| | Re: legOS Network Protocol
|
| (...) I too may be interested in this, although probably only the higher level stuff ie I'm not too sure how good I'd be at interfacing with the IR. Anyway, I had a look around and I found some references on a protocol layered on top of IP called (...) (25 years ago, 14-Apr-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.637)
|
|
| | Re: SENSOR_READ doesn't return 0
|
| More information: (...) CONSTANT is working - easy to check by doing RawLight . which prints 1 (...) This last line is the problem, if I use a SENSOR_MODE of 80 as in TRACKER.TXT then I get a SENSOR_READ of 0, if I use SENSOR_MODE 0 then I never get (...) (25 years ago, 13-Apr-99, to lugnet.robotics.rcx.pbforth)
| |
|
ir
(score: 1.636)
|
|
| | Re: legOS Network Protocol
|
| (...) Sounds good. Does it provide a stream interface or datagrams only? My faulty memory suggests that it might be the latter. If the network implementation supports packet reassembly (packets larger than MTU), there may not be a need for a stream (...) (25 years ago, 14-Apr-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.636)
|
|
| | 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)
| |
|
ir
(score: 1.635)
|
|
| | 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)
| |
|
ir
(score: 1.635)
|
|
| | FW: IR mode
|
| -----Original Message----- From: John Cooper [mailto:robots@jpsc.co.uk] Sent: Thursday, May 06, 1999 6:07 AM To: Ralph Hempel Subject: IR mode (...) I wonder if these will work? ;---...--- ; IRMODE_HI ( -- ) M_CODE(9,``"IRMODE_H...HI,_SLINK) MOV.W (...) (25 years ago, 11-May-99, to lugnet.robotics.rcx.pbforth)
| |
|
ir
(score: 1.635)
|
|
| | Re: Ir transmission
|
| (...) I can't get EMIT to work, in NQC I do this: SendMessage(255); // Flash Sleep(3); ThisRaw = RAW_LIGHT; and the raw light sensor reading has big spikes for IR reflections. but: [ HEX ] FF EMIT 30 msWait RawLight LIGHT? does not, I think that (...) (25 years ago, 10-May-99, to lugnet.robotics.rcx.pbforth)
| |
|
ir
(score: 1.635)
|
|
| | FW: Ir transmission
|
| -----Original Message----- From: John Cooper [mailto:robots@jpsc.co.uk] Sent: Monday, April 19, 1999 2:31 AM To: Ralph Hempel Subject: Re: Ir transmission (...) Well, I don't do realtime stuff (until now), in fact what I do (simulation) is almost (...) (25 years ago, 11-May-99, to lugnet.robotics.rcx.pbforth)
| |
|
ir
(score: 1.635)
|
