I assume that the historized point was working before the error, so I
discount the typo scenario.â I think at this point you don't have much
choice other than deleting the current CALC.RI04 from the AIM historian and
re-adding it. You'll lose historized data but you may solve your problem.
Duc
On Tue, Mar 22, 2016 at 3:30 PM, Joseph M. Riccardi <Joe@xxxxxxxxxxxxx>
wrote:
It falls into that freshman category but I couldn't think of anything
else...
Joseph M. Riccardi
386-451-7607 Cell
Joe@xxxxxxxxxxxxx
"To give real service you must add something that cannot be bought or
measured with money; and that is sincerity and integrity." - Donald A.
Adams
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On
Behalf Of Vandewater, Tom (HI Contractor)
Sent: Tuesday, March 22, 2016 3:25 PM
To: 'foxboro@xxxxxxxxxxxxx' <foxboro@xxxxxxxxxxxxx>
Subject: Re: [foxboro] AIM* Collection fails after divide by 0
That was my immediate thought also Joe;<)
-----Original Message-----
From: foxboro-bounce_freelists.org [mailto:foxboro-bounce_freelists.org]
On
Behalf Of Joseph M. Riccardi
Sent: Tuesday, March 22, 2016 9:01 AM
To: foxboro_freelists.org
Subject: Re: [foxboro] AIM* Collection fails after divide by 0
CALC block .RI004 should be RI04... Hope it is just a typo.
Joseph M. Riccardi
386-451-7607 Cell
Joe_eRiccardi.com
"To give real service you must add something that cannot be bought or
measured with money; and that is sincerity and integrity." - Donald A.
Adams
-----Original Message-----
From: foxboro-bounce_freelists.org [mailto:foxboro-bounce_freelists.org]
On
Behalf Of Johnson, David (Redacted sender "David.Johnson" for DMARC)
Sent: Tuesday, March 22, 2016 2:57 PM
To: Foxboro_freelists.org
Subject: [foxboro] AIM* Collection fails after divide by 0
All knowing list,
HELP!
If we could do this without the freshman lecture on bounds checking, error
checking, and knowing that a divide by zero error was a possibility, that
would be great.
I did it, I divided by 0, the result was NaN and now the data that was
being
collected by the AIM* historian has a 1.#QNB showing on the trend, and it
is
NOT collecting historical data.
The value is a IND .RO0001, the number goes to a lead/lag LLAG block, the
resulting .OUT of the LLAG goes to a CALC block .RI004 and that is the item
that is trended. (Don't ask...)
The number being calculated by the IND block is now acceptable, all the
numbers are ok, but the AIM* historian will not collect the data.
We have transitioned the LLAG block from Auto to Man and back. We have
DELETE/UNDELETE the CALC block. We did an upload/done on the IND block. We
have stopped and restarted the historian instance that contains the point.
I'm at a loss.
Any help would be appreciated.
Thanks,
David
________________________________
Confidentiality Notice:
The information contained in this message is private and confidential. This
information is intended only for the individual or entity named above. If
the reader of this message is not the intended recipient, you are hereby
notified that any use, review, dissemination, distribution, copying or
action taken based on this message or its attachments, if any, is strictly
prohibited. If you are not the intended recipient, please contact the
sender
by reply email and delete or destroy all copies of this message and any
attachments. Thank you.
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request_freelists.org?subject=join
to unsubscribe: mailto:foxboro-request_freelists.org?subject=leave
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request_freelists.org?subject=join
to unsubscribe: mailto:foxboro-request_freelists.org?subject=leave
----------- Please note that my email address has changed. Please update my
contact information to reflect my address as forwarding for the old address
will end on January 1st 2016. The only change is modifying the domain name
of the email address from @ppetrol.com to @parpacific.com.
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
