 | | Re: BrickOS Threading... —Steve Hassenplug
|
| | | (...) ... (...) This change seem to improve things. Can I change it back to the way it was before? Thanks Steve (22 years ago, 13-Dec-02, to lugnet.robotics.rcx.legos)
|
| | | |
| | | | | Re: BrickOS Threading... —Joseph Woolley
|
| | | | (...) <snip> (...) Steve, Yes, infact I had tested a couple different applications with the motor controller being called every 1 ms and the same ones with a 2 ms interval. I didn't see a difference with those applications, but did recognize the (...) (22 years ago, 13-Dec-02, to lugnet.robotics.rcx.legos)
|
| | | | |
| | | | | | Re: BrickOS Threading... —Steve Hassenplug
|
| | | | (...) In trying to balance an RCX on two wheels, every little bit makes a difference. I didn't think it would matter quite that much, but my robot really shakes more with the new version. Thanks for the work, Steve (22 years ago, 13-Dec-02, to lugnet.robotics.rcx.legos)
|
| | | | |
| | | | | | Re: BrickOS Threading... —Joseph Woolley
|
| | | | 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 (...) (22 years ago, 13-Dec-02, to lugnet.robotics.rcx.legos)
|
| | | | |
| | | | | | Re: BrickOS Threading... —Mark Riley
|
| | | | 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 (...) (22 years ago, 13-Dec-02, to lugnet.robotics.rcx.legos)
|
| | | | |
