This Forum is Dedicated For all The Object Oriented PIC Lovers .......... The concept behind OOPic is straight forward. Use preprogrammed multitasking Objects from a library of highly optimized Objects to do all the work of interacting with the hardware. Then write small scripts in Basic, C, or Java syntax styles to control the Objects. During operation, the Objects run continuously and simultaneously in the background while the scripts run in the foreground telling the objects what to do.

Wednesday, November 21, 2007

[oopic] Re: I/O problem

--- In oopic@yahoogroups.com, J M <drjack199@...> wrote:
>


As I underatand it, the original s-board was designed before the
later crop of oopic chips that dedicate I/O lines 22+23 for RS232
UART.

So, when you plug a version II or III chip into the board, you should
not try using those pins for anything else besides RS232. Use some
other pins.

Also, it's best to reserve I/O lines 1-7 for A/D channels, and not
use them for digital I/O, as there are some allocation problems when
trying to use some of those lines for A/D and others for digital I/O.

> Thanks, I do realize that the pins and I/O's are not
> the same. I did not have a schematic with the pin #'s
> in front of me. Those pins are 35, 37 and 39
> respectively.
>
> So what you are trying to say second then, is that
> this is normal operation for the oopic? Then what
> about I/O 21, is it independent or is it also tied
> into the internal RS232?
>
> Do you know of better a schematic that shows this for
> the oopic-s board?
>
> --- dan michaels <oric_dan@...> wrote:
>
> > --- In oopic@yahoogroups.com, "drjack199"
> > <drjack199@> wrote:
> > >
> >
> >
> > First, distinquish between cpu pin #'s 21, 22, 23
> > and oopic-assigned
> > I/O lines 21, 22, 23. They're not the same, in case
> > you didn't
> > realize it.
> >
> > Secondly, do not try to use oopic I/O lines 22+23
> > for regular I/O,
> > because they are connected to the internal RS232
> > UART.
> >
> >
> >
> >
> >
> >
> > > I am using the oopic III+ and am experiencing a
> > problem with I/O's
> > 21,
> > > 22, 23. I test each I/O using the LED program,
> > the program is the
> > one
> > > from the oopic webpage (Chapter 2 - Your first
> > ooic application).
> > I
> > > like to do this to make sure the oopic is working
> > properly, saves
> > me
> > > the headache down the line. I did this test I
> > found that I/O 23
> > never
> > > has an output, when 21 is powered 21 and 22 have
> > an output, but
> > when
> > > just 22 is tested only 22 outputs a signal. Not
> > sure what the
> > problem
> > > is but these are the only 3 ports with a problem.
> > Is there a
> > hardware
> > > issue, a firmware issue or is this a normal
> > operation for the
> > oopic.
> > > I don't believe that the last one is proper but
> > just have to
> > check.
> > > It was suggested that ths maybe how it operates,
> > but I don't
> > believe
> > > that.
> > >
> >
> >
> >
>
>
>
>
______________________________________________________________________
______________
> Get easy, one-click access to your favorites.
> Make Yahoo! your homepage.
> http://www.yahoo.com/r/hs
>



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:

http://docs.yahoo.com/info/terms/

No comments: