 | | Re: IR Proximity Detection Problem
|
|
(...) A friend of mine attempted this setup a while back and came to the conclusion that he basically needed to be nearly perfectly perpendicular to the object he was trying to detect. So he decided this was way to precise/finicky for his general (...) (22 years ago, 17-Jan-03, to lugnet.robotics.rcx)
|
| |
| | Re: BricxCC 3.3.7.1
|
|
(...) Sure. I've made that change now but I will wait for a few more updates before I put out a new release. Thanks, John Hansen (22 years ago, 17-Jan-03, to lugnet.robotics.rcx)
|
| |
| | Re: IR Proximity Detection Problem
|
|
Dean, Philo, Thank you both very much: Including the sensor monitoring in a "repeat"-loop brouhgt the solution. Works quite perfect. I guess "SendMessage" is somewhat slow, i. e. the IR-emission/reflection. Now I am going to even improve the (...) (22 years ago, 17-Jan-03, to lugnet.robotics.rcx)
|
| |
| | Re: BricxCC 3.3.7.1
|
|
(...) grab this update, but just in case it's not in this one, can you add to your list to add to the next release the file suffix .nqh to NQC files? Thanks again! (22 years ago, 17-Jan-03, to lugnet.robotics.rcx)
|
| |
| | spyutils.nqh
|
|
I have attached to the end of this message the spyutils.nqh file I've been compiling. It's not got a lot in there yet, just the routines defined as "utility" in the Lego Spybotics ROM SDK plus the SendRCXMessage. I'm aiming toward this file being (...) (22 years ago, 17-Jan-03, to lugnet.robotics.spybotics, lugnet.robotics.rcx.nqc, lugnet.robotics)
|
| |
| | BricxCC 3.3.7.1
|
|
I've uploaded release 3.3.7.1 of BricxCC to my website. This adds a couple new features and fixes a few minor bugs. 1. Built-in MIDI conversion to NQC, MindScript, LASM, C, or Pascal. See Tools/MIDI Conversion. You can save directly to a file or to (...) (22 years ago, 17-Jan-03, to lugnet.robotics.rcx)
|
| |
| | Re: DISTRIBUTED/PARALLEL CLUSTER for legOS through n*RCX
|
|
(...) An interesting idea. Presumably a light sensor alone would suffice, as it could be switched between active/passive mode to turn the LED on/off. You couldn't get high bandwidth, but there wouldn't be interference. Also, this would take multiple (...) (22 years ago, 17-Jan-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: brickOS with BricxCC
|
|
(...) Well, I guess I am one of the two :) Its nice to know I am on the cutting edge of things. Actually I am probably one of the few BrickOS users that is too dumb or impatient to deal with cygwin or unix. (...) Seems fine to me. I think all we (...) (22 years ago, 17-Jan-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: IR Proximity Detection Problem
|
|
(...) Dirk, I had a similar problem when I first tried, eventually determining that I wasn't measuring the light sensor value while the message was being sent. You have to wait a little bit after sending the message before reading the peak light (...) (22 years ago, 16-Jan-03, to lugnet.robotics.rcx)
|
| |
| | Re: IR Proximity Detection Problem
|
|
Maybe the ambient light is too high ? in that case you can decrease visible light sensitivity as well as shielding detector from red LED light using this method : (URL) (only hope that this doesn't offend your "Lego purity" sense ;o) Philo (...) (22 years ago, 16-Jan-03, to lugnet.robotics.rcx)
|
| |
| | IR Proximity Detection Problem
|
|
I have tried to get proximity dectection via RCX emitting IR (SendMessage/NQC) and Light Sensor (mounted on top of the RCX's IR unit). But the raw values seemed to be the same with/without emitting IR. Average value was 725. Went up to 800 (black (...) (22 years ago, 16-Jan-03, to lugnet.robotics.rcx)
|
| |
| | MIDI conversion
|
|
I have added a feature to BricxCC to convert MIDI files to NQC, MindScript, LASM, brickOS C, and brickOS Pascal code. It seems to work quite well with the first three languages (i.e., the sound generated by the RCX closely resembles the MIDI file (...) (22 years ago, 16-Jan-03, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx.nqc)
|
| |
| | Re: Interesting BrickOS Timing Results
|
|
(...) I forgot to mention... This is *almost* the same as moving some of the subsystem code into a seperate high priority task. For example, LCD refresh code is executed in the 1ms timer ISR. It really doesn't need to be in the ISR. It can do it's (...) (22 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Interesting BrickOS Timing Results
|
|
(...) 250msec? Not blocked entirely, but delayed. That's what I meant by "stutter". I've measured the general interrupt handler to take anywhere from 70-150us. So, the higher the sample rate the more significant the disruption. Anything faster than (...) (22 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
|
| |
| | RE: Interesting BrickOS Timing Results
|
|
(...) I have been following this thread in my peripheral vision for a while now. All of the talk is very interesting and appears to be leading to a general question about how and why the drivers are the way they are.... As a point of interest, some (...) (22 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx.pbforth)
|
| |
| | Re: DISTRIBUTED/PARALLEL CLUSTER for legOS through n*RCX
|
|
Hi there, did some worh with rcx/legos/DSM in my thesis which can be found at www.cs.uit.no/~kenne.../Thesis.ps Although i didnt share the memory of each rcx, i installed a dsm server(created at the local university) on a notebook which each rcx (...) (22 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Interesting BrickOS Timing Results
|
|
Mark Riley wrote: > Actually, if we move the sys_time > handler back to OCRA (instead of the watchdog NMI), > then we could just check if bit 0 of sys_time is zero to > determine if the subsystem handler should be called (plus > this will get (...) (22 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: DISTRIBUTED/PARALLEL CLUSTER for legOS through n*RCX
|
|
Yes Kekoa it's a bottle neck, as I wrote on the original message, the main idea is to distribute the load, with the MINIMUM amount of network traffic. I think that all the RCX should be connected through fibre optics, in order to implement the (...) (22 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Interesting BrickOS Timing Results
|
|
Hi Marc, (...) Nice idea, but wouldn't that result in at least one of four cycles beeing blocked by OCRA? or is our system interrupt finished within less than 250msec? (...) Right, that was what I did for my Lepomux patch - works fine. Gunther (22 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Interesting BrickOS Timing Results
|
|
(...) My thought was that the OCRA interrupt could be used as the general 1ms interrupt and the subsystem handler (which is currently using OCRB) could be called every other time from the OCRA handler by using a flag (toggled every 1ms). Actually, (...) (22 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
|
