 | | is IR considered broken?
|
|
The precompiled tm-and-ir, kinda works for me. It is pretty good at receiving data, but the transmitted message often has garbage. When I compile it myself using the latest legOS snapshot, it always transmits garbage, others seem to have seen the (...) (25 years ago, 12-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: is IR considered broken?
|
|
Sorry it took so long to reply, Mark... I somehow seem to have deleted your mail and only noticed it on the newsgroup by accident. Here are my thoughts. (...) Uhuh. This is (apparently) not a unique experience. (...) I have not had that experience, (...) (25 years ago, 14-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: is IR considered broken?
|
|
(...) I have working IR code, but it does not work with LegOS. It works with that "custom, as-yet-unreleased version of Librcx" I mention every so often. It probably wouldn't take much to port it to LegOS. Changes would be: - modify hook to get a (...) (25 years ago, 16-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: is IR considered broken?
|
|
Yes I would be interested in seeing the libRcx implementation of the IR functions. thanks, Mark (...) (25 years ago, 16-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: is IR considered broken?
|
|
(...) For all who are interested, I copied the source to: (URL) porting hints, e-mail me directly. -Kekoa (25 years ago, 16-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | The IR FIX -- was: Re: Is IR considered broken?
|
|
(...) I had the same problem. (...) Here's the fix: enclode the old handler code in #ifdef TRASH, use the new #else part. I'll say a few things about the motivation below. (If you prefer to patch, download (URL) it's based on LegOS 0.1.7 but should (...) (25 years ago, 26-Jul-99, to lugnet.robotics.rcx.legos)
|
