Is it possible to run the UVTron Flame Detector on IOLine 11?



(You need to be a member of oopic -- send a blank email to oopic-subscribe@yahoogroups.com )

--- In o...@yahoogroups.com, "jon_mark_go" wrote:
>
> Is it possible to run the UVTron Flame Detector on IOLine 11?
>

Sure, why not? However, I would use the sample code EXACTLY as given
before I branched out on my own.

Richard



(You need to be a member of oopic -- send a blank email to oopic-subscribe@yahoogroups.com )

Also, this may be somewhat naive. But what is the point of outputting
the UVTron's detected value onto iolines 8-15?



(You need to be a member of oopic -- send a blank email to oopic-subscribe@yahoogroups.com )

Okay. On a separate note, has anyone made any sort of sample code that
would provide some insight as to how to control the movement of a
robot through virtual circuits using inputs from range sensors? IE if
one range sensor spikes in distance, you want to turn that way since
its a hallway, etc.



(You need to be a member of oopic -- send a blank email to oopic-subscribe@yahoogroups.com )

--- In o...@yahoogroups.com, "jon_mark_go" wrote:
>
> Also, this may be somewhat naive. But what is the point of outputting
> the UVTron's detected value onto iolines 8-15?
>

Who's code are you looking at? I am over at Acroname:
http://www.acroname.com/examples/10021/10021.html

In any event, it might be useful to see the accumulated count on LEDs
and a lot of examples do just that.

Richard



(You need to be a member of oopic -- send a blank email to oopic-subscribe@yahoogroups.com )

I assumed it was an analog input so it might have to be on 1-4.



(You need to be a member of oopic -- send a blank email to oopic-subscribe@yahoogroups.com )

--- In o...@yahoogroups.com, "jon_mark_go" wrote:
>
> I assumed it was an analog input so it might have to be on 1-4.
>

No, it is a digital pulse about 10 mS wide that triggers an event. The
sample code counts the events in a one second interval and, if it
exceeds a threshold, it turns on an LED.

Kind of like a Geiger-Mueller radiation counter, I suppose.

The sample code is a very nice example of using events with the OOPic.

Richard



(You need to be a member of oopic -- send a blank email to oopic-subscribe@yahoogroups.com )

I'm just looking at the sample code for oUVTronHM at oopic.com



(You need to be a member of oopic -- send a blank email to oopic-subscribe@yahoogroups.com )

--- In o...@yahoogroups.com, "jon_mark_go" wrote:
>
> I'm just looking at the sample code for oUVTronHM at oopic.com
>

The OOPic code uses IOLine1 as a digital input, not analog, although
you sure can't tell that from the sample code. However, there is a
note that says the input can go to any of the OOPic's 31 IO lines,
hence a digital signal as analog can only go to the first 7.

Given the built-in object, it seems like a good way to go. Just use a
comparator on the .Level property if necessary to supplement the
.Detected property. The documentation doesn't say at what count the
.Detected property is set true.

Richard



(You need to be a member of oopic -- send a blank email to oopic-subscribe@yahoogroups.com )

So any I/O 1-7 would be good to be safe? Or can I really use any 1-31?



(You need to be a member of oopic -- send a blank email to oopic-subscribe@yahoogroups.com )

--- In o...@yahoogroups.com, "jon_mark_go" wrote:
>
> So any I/O 1-7 would be good to be safe? Or can I really use any 1-31?
>

Just what it says: any of the 31 IOLines.

As a practical matter, leave lines 1..7 for A/D, use 8..15 for inputs
because you can turn on internal pull-up resistors (OOPic.PullUp =
cvTrue) and do outputs with 16..31 leaving IOLines 22 & 23 for the
serial port.

To protect the sensor and the OOPic, you can put a 330 ohm resistor in
series with the input connection. This may help prevent a disaster if
you happen to set the selected IOLine as output accidentally.

Richard



(You need to be a member of oopic -- send a blank email to oopic-subscribe@yahoogroups.com )