|
| | random problems...
|
| I'm having a problem with the random() function in BrickOS. I keep getting a return value of zero. Is there something that needs to be set-up before using the function? What kind of value does it return? I've seen documentation that says it returns (...) (21 years ago, 29-Dec-03, to lugnet.robotics.rcx.legos)
| |
| brickos (score: 0.510) |
|
| | Re: Memory, Motors and Odd Things
|
| (...) Hi Steve, Are you using BrickOS 0.2.6.10? In earlier versions, it was possible for malloc() to return pointers to RAM in the range [F010,FB7F], which was shared with the motor port controller. Writing to this memory adversely affected the (...) (21 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos, FTX)
| |
| brickos (score: 0.508) |
|
|
| brickos (score: 0.507) |
|
| | Re: Strange BrickOS Timing
|
| Hi Gunther, (...) have (...) I'm NOT really an expert in brickOS, but these are the sources of delay and msleep: void delay(unsigned ms) { unsigned i; while (ms-- > 0) for (i = 0; i < 600; i++) // not well calibrated. ; } //! delay execution (...) (21 years ago, 3-Dec-03, to lugnet.robotics.rcx.legos)
| |
| brickos (score: 0.507) |
|
|
| brickos (score: 0.507) |
|
|
| brickos (score: 0.507) |
|
|
| brickos (score: 0.507) |
|
| | Strange BrickOS Timing
|
| Hello out there, maybe someone can explain to me why the current brickOS release seems to have msleep()-amnesia ;-) We've been testing the data transfer to our Lepomux device. For some strange reason we were still using kernel 0.2.6.07nmChg with a (...) (21 years ago, 2-Dec-03, to lugnet.robotics.rcx.legos)
| |
| brickos (score: 0.507) |
|
| | Strange RCX startup issues
|
| Hello, using brickOS v0.2.6.10... When I declare an object of type Motor and assign it a port outside of main() the RCX does not run the program at all, I have to remove batteries and reload firmware to get it back to normal. Is this related to the (...) (21 years ago, 9-Dec-03, to lugnet.robotics.rcx.legos)
| |
| brickos (score: 0.507) |
|
|
| brickos (score: 0.507) |
|
| | Re: Logging sensor data
|
| (...) If you had not already decided to use LegOS/BrickOS you might have used Robolab, which has nice sensor data-logging utilities built-in. I show a sensor log in my project 'The LEGO Level' at (URL) It's very easy to set up. Jerry (21 years ago, 10-Dec-03, to lugnet.robotics.rcx.legos)
| |
| brickos (score: 0.507) |
|
|
| brickos (score: 0.507) |
|
| | Re: Strange BrickOS Timing
|
| Hi Guido, (...) That patch referes to an older transfer-protocol. The one we are using now, does not need SUCH a stable timing. But the Output from BrickOS is a lot worse than it was in older versions. I thing Gunther can explain this better, but I (...) (21 years ago, 3-Dec-03, to lugnet.robotics.rcx.legos)
| |
| brickos (score: 0.507) |
|
| | Memory, Motors and Odd Things
|
| I ran into something odd, and I'm wondering if someone can explain it. I have a pretty large BrickOS program, (the .lx is about 9k) and it uses around 2k for variables. (I think) I've noticed when the program is running, it's not doing anything with (...) (21 years ago, 10-Dec-03, to lugnet.robotics.rcx.legos)
| |
| brickos (score: 0.507) |
|
| | Re: Strange BrickOS Timing
|
| Hi Gunther, (...) have (...) After some investigation I found this page on YOUR site: (URL) YOU state: Using Lepomux requires a stable timing on the motor port because it is used as a serial data port. Since brickOS does a lot of stuff (...) (21 years ago, 3-Dec-03, to lugnet.robotics.rcx.legos)
| |
| brickos (score: 0.507) |
|
|
| brickos (score: 0.507) |
|
| | Logging sensor data
|
| Hi there, I'm quite new to the Mindstorms and LegOS/BrickOS scene but have recently begun using the kits for robotics purposes in University. They have been a revelation to me and speed up prototyping projects to no end. My question though concerns (...) (21 years ago, 9-Dec-03, to lugnet.robotics.rcx.legos)
| |
| brickos (score: 0.507) |
|
|
| brickos (score: 0.507) |
|
|
| brickos (score: 0.507) |
|
| | Re: Remote Message Buttons
|
| (...) I just use the standard IR message stuff from BrickOS. They are normal messages, so this works just fine. Here are some lines of code: (I think it's in lnp.h) #include <sys/lnp.h> ... clear_msg(); ... if (msg_received != 0) my_message_value = (...) (21 years ago, 8-Dec-03, to lugnet.robotics.rcx.legos)
| |
| brickos (score: 0.506) |