 | | Avoiding objects
|
| Hello All, I'm new to the world of Mindstorms and to this list, and I have a question. Upgrading the Roverbot, which backs up when the bumpers feel something, is there a way of avoiding walls and objects on the floor. What is the best way to do (...) (23 years ago, 11-Dec-03, to lugnet.robotics)
| | |  | | Re: BricxCC release 3.3.7.6
|
| (...) Unfortunately I haven't documented my pbForth support very well. Perhaps the following explanation will be useful to all BricxCC users who want to try pbForth. BricxCC figures out some things based on the extension of the file open in the (...) (23 years ago, 11-Dec-03, to lugnet.robotics.rcx.pbforth, FTX)
| | |  | | Re: Memory, Motors and Odd Things
|
| (...) no. Ok, that's my first problem. (...) hmm. yep. malloc()... (...) no, using the firmdl3. (...) Yes, it's recursive. And, I'm sure your hunch is right. (...) It sounds like it's the malloc() bug. I'm using 0.2.6.09 (?) I'm not going to switch (...) (23 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos, FTX)
| | |  | | Re: BricxCC release 3.3.7.6
|
| (...) Wow! I've just discovered Bricxcc! Thank you very much for providing such a useful tool. I'm using PbForth and I was impressed by what you've included in BricxCC. Just to share with you, here's what I did so far. I've renamed the Help file so (...) (23 years ago, 11-Dec-03, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.legos, lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics, FTX)
| | |  | | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
| (...) <snip> (...) <snip> (...) <snip> I didn't have time to mention this in my earlier post, but this memory dump points out a potential problem with the way BrickOS allocates memory for programs. In the above memory dump, the 0x6B words at 0xB648 (...) (23 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos)
| |