 | | Re: strange motor behaviour
|
| (...) The problem is that the upper memory area (0xf000-0xf800) is connected to both RAM and motor output. Every byte written here is also interpreted as motor command. The latest CVS version of BrickOS has fixed this (this memory is written only (...) (21 years ago, 2-Apr-03, to lugnet.robotics.rcx.legos)
| | | | | Re: strange motor behaviour
|
| Marko, Here's a thread that might give a little more background on the BrickOS bug Jochen mentions: (URL) Hoenicke" <Jochen.Hoenicke@Inf...enburg.DE> wrote in message news:200304021124.11...burg.de... (...) (21 years ago, 2-Apr-03, to lugnet.robotics.rcx.legos)
| |
