 | | FW: pbFORTH
|
|
-----Original Message----- From: John Cooper [mailto:robots@jpsc.co.uk] Sent: Wednesday, April 21, 1999 2:31 AM To: Ralph Hempel Subject: Re: pbFORTH (...) Thanks for that, I can't try it until tomorrow because the machine wth the IR tower on is in (...) (25 years ago, 11-May-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | FW: Ir transmission
|
|
-----Original Message----- From: John Cooper [mailto:robots@jpsc.co.uk] Sent: Monday, April 19, 1999 6:07 AM To: Ralph Hempel Subject: Re: Ir transmission (...) To answer the question, I would say do it as core (quicker download). I think we agree (...) (25 years ago, 11-May-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | FW: multitasker
|
|
-----Original Message----- From: John Cooper [mailto:robots@jpsc.co.uk] Sent: Monday, April 19, 1999 2:31 AM To: Ralph Hempel Subject: Re: multitasker (...) Excellent news. (...) You can have our SpeedBot as a demo program (as soon as I get it to (...) (25 years ago, 11-May-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | 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)
|
| |
| | FW: pbFORTH and MARKER
|
|
-----Original Message----- From: Ralph Hempel [mailto:rhempel@bmts.com] Sent: Thursday, April 22, 1999 12:55 PM To: John Cooper Subject: pbFORTH and MARKER John, I have discovered yet another bug in the CREATE DOES> of pbFORTH and fixed it. Now (...) (25 years ago, 11-May-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Forward of pbFORTH debug sessions
|
|
John Cooper and I have exchanged numerous emails on the progression of pbFORTH and he has agreed to share them with the group. I guess we should have always discussed on the group, but once I just hit Reply instead of ReplyToAll and that was the end (...) (25 years ago, 11-May-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | 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)
|
| |
| | 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)
|
| |
| | 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)
|
| |
| | 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)
|
