|
 | | 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: 0.253)
|
|
| | 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: 0.253)
|
|
| | 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: 0.253)
|
|
| | 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 (...) (26 years ago, 16-Apr-99, to lugnet.robotics.rcx.pbforth)
| |
|
ir
(score: 0.253)
|
|
| | 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 (...) (26 years ago, 15-Apr-99, to lugnet.robotics.rcx.pbforth)
| |
|
ir
(score: 0.253)
|
|
| | 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 (...) (26 years ago, 14-Apr-99, to lugnet.robotics.rcx.pbforth)
| |
|
ir
(score: 0.253)
|
|
| | One Way/No Way wires
|
| Use of diodes to MUX two motors on a single output has been known for a long time. I have not seen a description of just putting the diode in the wire itself to make a One Way wire. If you use two you get a No-Way wire which does not sound useful. (...) (24 years ago, 29-Aug-00, to lugnet.robotics.rcx)
| |
|
long
(score: 0.253)
|
|
| | NQC 2.2 r1 released
|
| NQC 2.2 is finally out of beta test. I appologize for the long alpha/beta cycle...it wasn't that there were tons of problems, but just that I have been quite busy with a lot of other things. There were only a few minor fixes between 2.2 b1 and the (...) (24 years ago, 26-Aug-00, to lugnet.robotics.rcx.nqc) !
| |
|
long
(score: 0.252)
|
|
| | Re: Rotation sensor bug found
|
| Lou, thank you for your reply. (...) This should work. (...) This seems wrong to me because sets all the STATE_n_VALUE to k-RANGE_SIZE. For now I modified ds_rotation_handler() in this way (two occurrences): // if ( IN_RANGE ( STATE_0_VALUE ) ) { // (...) (25 years ago, 18-Apr-99, to lugnet.robotics.rcx.legos)
| |
|
range
(score: 0.252)
|
|
| | 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 (...) (26 years ago, 14-Apr-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 0.252)
|
|
| | 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 (...) (26 years ago, 14-Apr-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 0.252)
|
|
| | Rotation sensor help (some progress)
|
| Again about my problems with legOS and the rotation sensor. First of all I checked the four values returned by both my two rotation sensor. They are different from the ones inside direct-sensor.c but anyway inside the specified range legOS: (...) (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.legos)
| |
|
range
(score: 0.252)
|
|
| | Problems Solved(WAS Re: Problems with datalog)
|
| (...) before (...) I just tried using the Wait() command for up to 5 seconds. Still didn't work. I remember reading that the Vision Command required the new firmware. I assumed that VC d/l'd the new firmware automatically. I didn't remember waiting (...) (24 years ago, 25-Aug-00, to lugnet.robotics.rcx.nqc)
| |
|
long
(score: 0.252)
|
|
| | Re: Rotation sensor bug found
|
| (...) It wouldn't, though. First it gets the maximum of the given value or RANGE_SIZE. That is done to prevent a similar overflow at the low end, even though, with current values, that won't happen. Then, that value is compared against the safe (...) (25 years ago, 19-Apr-99, to lugnet.robotics.rcx.legos)
| |
|
range
(score: 0.252)
|
|
| | Re: Rotation sensor bug found (maybe!)
|
| (...) You've got a point here. What if we hardwire STATE_0_VALUE to the following? #define STATE_0_VALUE (ds_unscale(1023U)-RANGE_SIZE) Or, for a more general approach: #define MIN(a,b) (a<b?a:b) #define MAX(a,b) (a>b?a:b) #define STATE_VALUE(k) ( \ (...) (25 years ago, 17-Apr-99, to lugnet.robotics.rcx.legos)
| |
|
range
(score: 0.252)
|
|
| | 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 (...) (26 years ago, 13-Apr-99, to lugnet.robotics.rcx.pbforth)
| |
|
ir
(score: 0.252)
|
|
| | Rotation sensor bug found (maybe!)
|
| I think I might have found a bug in the ds_rotation_handler (direct-sensor.c). The problem arises when the STATE_0_VALUE is checked using the IN_RANGE macro. As STATE_0_VALUE is 1023U<<6, which is about the max value for an unsigned, adding to it (...) (25 years ago, 17-Apr-99, to lugnet.robotics.rcx.legos)
| |
|
range
(score: 0.252)
|
|
| | 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: 0.252)
|
|
| | 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: 0.251)
|
|
| | Re: Ir transmission
|
| (...) My next project is to port the IR proximity dectector originally posted by Mark R. David (markdavid@mediaone.net) in sort-of-Spirit code which I reposted in NQC whan I had got it working. It is the best performing detector I have found so far. (26 years ago, 4-Apr-99, to lugnet.robotics.rcx.pbforth)
| |
|
ir
(score: 0.251)
|
