 | | 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)
|
| |
| | Re: Direct Link (was Global Objects was Strange RCX startup issues)
|
|
(...) perfect! Step by step directions. Thanks. (...) So, now I can use the 'run' button to do other stuff, right? Or, for that matter, I could do other stuff with the On/Off button. After I turn it off (using the code listed), then, I can just turn (...) (21 years ago, 15-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Direct Link (was Global Objects was Strange RCX startup issues)
|
|
(...) Ok, I'll take a shot at it: 1) Make a new directory in the root BrickOS directory called pgm. 2) Copy the files config.h and Makefile from the boot directory to the pgm directory. 3) Copy your C files to the pgm directory. 4) Edit config.h (in (...) (21 years ago, 13-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Vision command + linux
|
|
someone ask me to diffuse my code .... then it's here : (URL) can use it to make your own project. Please read the README and if you have any question mail me nanobapt (21 years ago, 12-Dec-03, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: Vision command + linux
|
|
(...) LOL, thanks (...) I wil try some method to fixe it nanobapt (21 years ago, 12-Dec-03, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: Vision command + linux
|
|
(...) This is a pretty cool technique! I really like the middle picture (movehead2.jpg) just as a work of art. (...) You could overcome this by subtracting out the minimum pixel change from all pixels. So if the entire picture gets brighter or (...) (21 years ago, 12-Dec-03, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Vision command + linux
|
|
I've test a new filter for the camera .... In my first study I applied a filter only in one image .... Now I take the "time" parameter ! I make a difference between two image and here is the result When nothing move : (URL) I move my head : (URL) (...) (21 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Direct Link (was Global Objects was Strange RCX startup issues)
|
|
In lugnet.robotics.rcx.legos, Mark Riley wrote: ... (...) All right, this brings up an interesting question. I can use BrickOS well enough to make it do cool stuff, but I really don't know all the cool stuff BrickOS can do... If I read this (...) (21 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
Mark Riley wrote: [snip] (...) This is easy enough to implement (1 or 2 lines), but raises the question: Should these memory strategies be included with BrickOS (with a config.h flag to control it)? I am sure the educators would rather leave that (...) (21 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Global Objects was Strange RCX startup issues
|
|
Understood. In this case, I am thinking that the option should be ON by default; such that a new, less experienced user would not encounter a problem; but an experienced user could turn the option off. // Joe (...) (21 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Global Objects was Strange RCX startup issues
|
|
(...) But, it perhaps should default to being enabled as this deficiency has caused some confusion in the past. Great work, Joe! Mark (21 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Global Objects was Strange RCX startup issues
|
|
(...) I opt for option. Not much may be to much in some cases. And I don't want to program in c++ anyway. Regards, Michael (21 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Global Objects was Strange RCX startup issues
|
|
(...) [snipped] (...) I simply added ctor_size and dtor_size to the *image*, *lx* and *program* structures. This allows the program manager to calc the start and end of these segments. (...) It wasn't as hard as I had thought. I have the fix (...) (21 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | 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 (...) (21 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 (...) (21 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 (...) (21 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | 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)
|
| |
| | Re: Logging sensor data
|
|
(...) That's why I use brickOS nanobapt (21 years ago, 10-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | 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)
|
| |
| | Re: Logging sensor data
|
|
(...) No, I regret to say, you must buy it. Jerry (21 years ago, 10-Dec-03, to lugnet.robotics.rcx.legos)
|
