|
|
 | | Re: BrickOS Threading...
|
| Joe, (...) Maybe a special kernel build for testing purposes that increments the lower sys_time word by 0x4000 instead of 1. This will greatly increase the opportunity for this glitch to occur (from once every 65 seconds to once every 4ms.) You (...) (23 years ago, 13-Dec-02, to lugnet.robotics.rcx.legos)
| | | | | Re: Hammer Help
|
| Thanks for the response. I've decided to stay away from string on the robot as string can get easily entangled, especially if battling another robot. I took a break from trying a design using gears and differentials - I was getting really (...) (23 years ago, 13-Dec-02, to lugnet.technic, lugnet.robotics)
| | | | | Re: Hammer Help
|
| In the prototype I used string and winch to set the hammer. I've decided not to use it on the robot - string can too easily get caught and entangled in stuff, especially if it goes up agianst another robot. On the prototype it works surprisingly (...) (23 years ago, 13-Dec-02, to lugnet.robotics)
| | | | | Re: Firmware download troubles
|
| (...) The problem he's describing, if it's the same one I have, is independant of the position, direction, and power level of the tower. It seems to have something to do with BrixCC itself. The only thing I find puzzling is that Matt (the other Matt (...) (23 years ago, 13-Dec-02, to lugnet.robotics.rcx)
| | | | | Re: BrickOS Threading...
|
| Steve, I checked in some changes this morning (into cvs) to put the motor controller back at the 1 ms interval. However, I want to complete the get_sys_time() updates that Mark Riley has proposed; so that can be tested as well. I am not sure when (...) (23 years ago, 13-Dec-02, to lugnet.robotics.rcx.legos)
|
|
