>
> > Maybe you can enlighten me as to why I should be using the V5
> compiler instead of the V6? Since I had no feedback other than Dan
Michaels of Oricomtech saying something like V5 was better
documented and had better examples, I ended up just using the V6
compiler.
>
That comment was a few months ago. Maybe the online manual is all
updated now.
> I haven't heard from Dan lately. I hope all is well!
>
Depends on which bush you look behind.
> V6 spent years in beta. There are two ways to look at that: first,
> the compiler is perfect or, second, it wasn't a priority. Well, we
> know it isn't perfect. I guess I just got put off by the amount of
> time it spent in beta with no apparent effort to move it forward.
>
> OTOH, V5 with all its' warts is a known quantity. It has been
around since Win95 and, while it lacks the newer objects, it is a lot
more stable.
>
> I haven't spent ANY time looking at the new objects because I don't
> plan to upgrade to V6 any time soon. Maybe if I did some reading,
I would get motivated. Or not... It's frustrating when things don't
> work. oEvents comes to mind.
>
> >
> > > But it is good to know that the OOPic can handle the Parallax
PING sensor.
> >
> > Not sure it can. It assumes that there are two I/O lines, one for
> the ping and one for the echo. Not sure if you can use the same
line for both. You would probably have to try it out.
>
I use the Ping with my bot that has a Basic Stamp on it, and it works
fine there. One i/o line is used for triggering and outputting.
However, the Ping requires measuring pulsewidths down to microsecond
resolution, and the oopic isn't great for this.
However, I much prefer the Ping to the SRF0x devices, as I found them
to have bad sidelobe pickup. I haven't tried the Maxsonar that Dennis
mentioned, although I have a couple in the box now.
> I don't have the sonar device and there could be issues with the
two pin approach. Ordinarily, I would solve that by using either one
pin or at least turning the output pin into an input so it would
float when not pinging. But I have no idea how it is actually
> implemented.
>
> Richard
>
It should be possible to connect 2 I/O pins to a device like the Ping
that uses just one line for both I and O, by connecting them together
using a 1K or so series resistor, and connecting the remote device to
the Input line. This is how a lot of SPI devices are interfaced. Most
device output pins should be able to drive a 1K load.
- dan michaels
www.oricomtech.com
--- OOBOT40 Boards ---
========================
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/oopic/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/oopic/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:oopic-digest@yahoogroups.com
mailto:oopic-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
oopic-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
No comments:
Post a Comment