|
|
 | | Re: Rotation sensor bug found
|
| (...) OK. I was wrong. I should have better analyzed your code... This definitively prove how long still is my way to get my hands on C :) BTW, I wrote an e-mail to Markus but got it bounced back. Mario (25 years ago, 19-Apr-99, to lugnet.robotics.rcx.legos)
| | | | | HOWTO v 0.1
|
| Hey everyone. I'd like to announce that I've posted to the web a basic version of a HOWTO for LegOS. If everyone has a chance, please take a look at it and let me know what you think. In particular, take a look at the about the HOWTO section, as it (...) (25 years ago, 19-Apr-99, to lugnet.robotics.rcx.legos)
| | | | | 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)
| | | | | RE: Linux Newbie
|
| Linux is a full blown Operating System, available with full source code. A good place to start is (URL) legOS is built using the same tools that are used to build Linux (GNU compiler and tools, etc.), I don't believe that you need to use Linux to (...) (25 years ago, 18-Apr-99, to lugnet.robotics.rcx.legos)
| | | | | 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)
|
|
