 | | Re: light sensor problem?
|
|
(...) Let me think about how to uncouple this from sys_time, so the code can get higher resolutions. (...) Yes, but even if all active sensors are turned of we are running with a lot of CPU power due to the high sampling speed. If you lower the (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation Sensor Values
|
|
(...) That's a good question. Is this the latest tarball? If so, there have been some modifications to the refresh loop, and this may indicate a bug in them. In other words, it could be the double sets of lcd_refresh() and not the actual reading (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation Sensor Values
|
|
I added back in the display code, and left out the lcd_refreshes. Then I got a proper counter. I wonder why the refresh was throwing the reading off. Thanks for all your help, Andy (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | RE: light sensor problem?
|
|
(...) I've used the OC1B interrupt for my servo driver code in pbForth. You could use the OC1B to set the settle time for each reading, and then actually read the results when the interrupt expires. Having a structure to tell you which A/D to read (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: light sensor problem?
|
|
(...) :-) It is not the best implementation I've seen... :-) (...) Yes. I hate the delay loop but we I can't imagine how to do it better if we still need maximum speed in reading values from sensors. The routine also change his sampling speed if we (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: light sensor problem?
|
|
(...) That's good. Now I wonder about some other questions: - Will it get the same value as the original firmware? - Will be influenced by offset (eg. from battery voltage)? In other words, do you think that the settle time is enough? I've tested (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation Sensor Values
|
|
Well, I do not know if I have to have code to display the values. I do not get anything on screen when I run this code. If I put a loop, and with every loop, the sensor value is being displayed, then I get the values mentioned before. I run the (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation Sensor Values
|
|
(...) Andy- Have you set up the rotation sensors correctly? You need to do a few things before you get reasonable values for the rotation sensor. 1) use ds_active(&SENSOR_1) to turn on the sensor. 2) use ds_rotation_on(&SENSOR_1) to turn on the (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Rotation Sensor Values
|
|
I was reading about rotation sensors for legOS for a new robot, and thought I'd try it out. So, I made a simple program that would show rotation sensor values on the display. What I got was not what I expected. I have never used the rotation sensors (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | dsound
|
|
Hi Luis, (...) I wonder if it would be interesting to include a small utility I wrote assisted by a friend of mine (Paolo Masetti) to convert MIDI files into LegOs C code: since then all of our robots are equipped with a subroutine generated by this (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Grey Archs Needed, 1x1
|
|
Jason- I don't know the references offhand, but there are a number of lugnet lists dedicated specifically to trading and/or buying of Lego parts. I'm not flaming you for being OT or anything- just that you are much, much more likely to have success (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Grey Archs Needed, 1x1
|
|
Hi Guys, I really need a couple of 1x1 light grey archs. Find the pic at: (URL) or Trade. Thanks. Jason (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: light sensor problem?
|
|
(...) Right. I made the connection between Kekoa saying "I need to test" and you saying "I will test" right /after/ sending the message, of course :) (...) True. (...) I figured this would be the case. gcc is a wonderful tool, but it does tend to (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: light sensor problem?
|
|
(...) This is why I want to measure things in our lab at work ;) (...) And keeps lower prio tasks from running, which they could do if we slept... (...) Oh well, there are some optimizations missing. I just looked at the code generated by (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: light sensor problem?
|
|
(...) proof that this occurs (even though his logic does seem pretty dead on.) (...) Well, we do... time_t current_time = sys_time; while (sys_time < current_time + the amount of time I want to wait) { do nothing; } It's not pretty, but it is (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Ideas for 0.2.5 (was: Re: Possible bug with bss allocation)
|
|
This will be my last post for a few hours- I have real work to do :) (...) Generally, user programs have it pretty simple for this already (which is why I had thought of this some time ago, and then dismissed it.) I had never considered the (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: light sensor problem?
|
|
(...) (URL) > I doubt we need this very fast reading of sensors. This makes implementing (...) Yes, when we have user space timers... (...) This is correct, but there are many good reasons for keeping assembly low bandwidth, like pitfalls in (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Ideas for 0.2.5 (was: Re: Possible bug with bss allocation)
|
|
(...) Shure, no problem. (...) While we are at it, I have two other major changes in mind: - Implement timers. A timer would install a callback function with a private to the caller void * argument. This callback function is called at the timers (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: light sensor problem?
|
|
(...) :) Bad is, of course, all relative... (...) Yes, though IMHO fast = good. It allows us to do things with legOS that might not be doable with other firmwares. (...) I'm not sure which comments you are referring to- do you have a URL for the (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: light sensor problem?
|
|
(...) It doesn't surprise me that someone has already worked this out. (...) It really, really doesn't surprise me that Michael was the one who worked it out. If no one thinks it is too big an overhead, I can put it in in an hour or so when I do a (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
