3 ms·
Was that using brickOS (previously legOS)? I always stuck to NQC since it was powerful enough for my (likewise) early-teen self but worked with the stock firmwa
by dschep 14y ago
Was that using brickOS (previously legOS)? I always stuck to NQC since it was powerful enough for my (likewise) early-teen self but worked with the stock firmware.
- mikeash 14y agoI did a lot of stuff with brickOS when it was still legOS. I started out in NQC, but it just wasn't fast enough. I had a two-wheeled robot that did dead reckoning by counting wheel revolutions to figure out where it was in the room. NQC took about one second per navigation update. My robot was kind of hilarious running NQC, because it would jump forward and then stop for a second while it calculated the navigation update, then jump forward and stop again, etc. Using native C, I got the navigation update cost down to 10ms, allowing for smooth driving without having to stop and wait for calculations.