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.

Monday, October 22, 2007

Re: [oopic] Does oMathC work?

I'll have to check the manual when I get back to the desk. There
have been lots of changes with the V.6 compiler and I don't have them
all internalized yet.
I'm assuming that you want to use this with a PID or PD loop or you
wouldn't care about setting the update intervals with any particular
precision.
I'll post again when I know more.

DLC

Shaggy wrote:
> I don't fully understand what you are saying here, could you expand on it a
> bit? My goal is to have the math operation occur once per second. I was
> under the impression that for the oMathC object, having a 1Hz signal on the
> process clock would do that. The exact name of the property for the process
> clock is not quite clear. I would have expected that the property name is
> ProcessClock due to the documentation, but that is not recognized. Process
> does appear to be recognized, but perhaps that is not the property name.
>
> As for Input1 and Input2, using cvLatch, the documentation states that it
> replaces the output with Input1, which is all I want to do. Input2 is not
> used in this case.
>
>
> ooPIC Tech Support wrote:
>
>>Hz1 is a flag property, which you would use with the clock or Operate
>>inputs. The input1 and input2 are data inputs (note that there is no
>>input) and you would need to use oBus to link that to something.
>>
>>DLC
>>
>>Shaggy wrote:
>>
>>>In putting together some odometer code, I wanted to move the value from
>>>the
>>>oQuadencode count to a oWord object all in a virtual circuit. To move a
>>>word, I figured that the way to go would be the oMath object in cvLatch
>>>mode. However, I wanted to do that once every second, so I used the
>>>oMathC
>>>object and tried to link the ooPIC.Hz1 to the timer. I used several
>>>variations of this line:
>>>
>>>(assuming that lMath is declared as New oMathC)
>>>
>>>lMath.Process.Input.Link(ooPIC.Hz1)
>>>
>>>I get an error saying that Input is not a member of oMath. I note that
>>>the
>>>compiler is not saying that it is not an error of oMathC. To test this, I
>>>changed oMathC to oMathO, and got other errors that specifically referred
>>>to
>>>the oMathO object. Since the error I am getting refers to the oMath
>>>object,
>>>rather than the oMathC object, it leads me to believe that the oMathC is
>>>not
>>>actually implemented, despite using B2.2+ (which appears to include the
>>>oMathC object).
>>>
>>>Any suggestions?
>>
>>--
>>------------------------------------------------------
>>Dennis Clark ooPIC Tech Support
>>www.oopic.com
>>------------------------------------------------------
>>
>>
>
>

--
------------------------------------------------------
Dennis Clark ooPIC Tech Support
www.oopic.com
------------------------------------------------------



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: