none of my delays will be very long... I was only testing it with long delays to see if the math was working right. I will probably never have any more than 200mS delay.. in fact most of them would me much less, like around 60mS... so I'm wondering.. could I perhaps use set_yield as suggested? I can't really tell what the min/max values are for this.. but could I set it for say 400000 instructions or push the time out to 200mS?
also is there any way to know how long until the next yield, or if just came back from one? that way I could start my entire procedure at just the right time and be done before any yielding happens..
these questions could be irrelevant however... because my intention is to use the motion detector, then light some leds in sequence with specific delays after motion is detected, and I suspect the motion detector will be depending on things happening during the yield such as reading the sensor.
I'm wondering if there is something I can do besides motion detection for my water drop detector... perhaps I could aim a red laser pointer at my camera, but instead of just hitting the lens with it, put a diffuser over the lens.. then just monitor the red intensity of just the relevant part of the sensor, and the instant it falls below some threshold because the water drop got in the way, make it exit immediately and continue the script. seems like that would react pretty fast, although I have no clue on how to implement that.. Anyone have any input on this idea?
Started by fudgey
« 1 2 3 4 »
Started by ghorian
Started by mattkime
« 1 2 »
Started by MotCan10
« 1 2 3 »
General Help and Assistance on using CHDK stable releases
Started by ericcire
« 1 2 »