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.

Thursday, July 24, 2008

[oopic] Re: OOPIC C1+ Firmware

No, I am using a Futaba Transmitter/Receiver. The output is a servo
timed pulse though so it should work. I need to hook both channels
up to a scope to see if there is seperation between them but either
way, a single channel should have worked with oRCIn (It works with
oPulseTimeH). I only needed two channels so I used three transistors
to build a quick and dirty multiplexer (1 Select, 1 Output, 2 Inputs)
and the PIC picks which one it wants to read, resets the pulsetimer,
waits for a new pulse, and continues.

--- In oopic@yahoogroups.com, "calpolyjdk" <calpolyjdk@...> wrote:
>
> Well, in a way that's a relief to hear that someone else has given a
> shot at it and had troubles as well. That's exactly why I was
hoping
> to get it to work: virtual circuits to pass through servo commands
> until I wanted to do something different with them. Are you using a
> Vex transmitter/receiver? If so, might oRCIN not be perfectly mated
> signal-wise with the Vex as previously mentioned in this forum? I'm
> shooting from the hip here in hopes that these discussions will lead
> to the solutions with oRCIN...
>
> Jonathan
>
> --- In oopic@yahoogroups.com, "tinslwc" <tinslwc@> wrote:
> >
> > I tried to use this object a few weeks ago and could not make it
> > work. I ended up using a multiplexer, having the OOPic select
the
> > channel with a select line and read the pulse width. After it
> > receives it, it selects the next channel and uses the pulse timer
> > object. I could not get it to work with only one channel (using
the
> > servo output from the receiver) or multiple channels. The
> > multiplexer circuit / program reads the channels about 20 times
per
> > second. I would love the RCIn object to work so I could do
> > everything with virtual circuits...Oh well.
> >
> > --- In oopic@yahoogroups.com, "rtstofer" <rstofer@> wrote:
> > >
> > > --- In oopic@yahoogroups.com, "calpolyjdk" <calpolyjdk@> wrote:
> > > >
> > > > Counting the lines, isnt'e RC1 Line 17? In any event, I also
> > tried
> > > > placing the signal onto Line 16 and it still doesn't seem to
be
> > > > working. I'm trying to follow as best as I can the Object
> > description
> > > > of oRCIN(1-6), but again, no dice...
> > > >
> > > > Jonathan
> > >
> > > I must have gotten cross-eyed. RC1 is correct. Still a
capture
> > input.
> > >
> > > Try it with a single channel pulse. In fact, loop an oServo
output
> > > back to the oRCIN1 input and see what happens.
> > >
> > > Post your code. It should be pretty short.
> > >
> > > And describe how you have the system grounds tied together...
> > >
> > > Richard
> > >
> >
>

------------------------------------

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: