PAC Display Runtime: Historical Logs may miss data if another trigger event occurs too quickly

Applies To:

PAC Display Basic
PAC Display Professional

Versions Affected:

Versions affected: R9.4a through B9.4h (prior to February 23, 2016)
Problem is fixed in version: R9.5a

Resolved In Version:

Problem is fixed in version: R9.5a

Symptoms:

If the trigger for a trigger-based historic log occurs too quickly, PAC Display Runtime may miss subsequent activations of the trigger, resulting in no data being logged.

Workaround:

Try using a different value to set the trigger each time.
One way you could do this is:

Configure the start trigger to be < > 0 (meaning "not zero").
In your PAC Control strategy, add a new 32-bit integer variable that gets incremented each time you want to set the trigger again.
Next, add a step that checks the new variable's value. If the value is 0 (zero), set its value to 1 (one).
This step makes sure that the new variable never equals zero (which is the non-triggered state).
Finally, move the value of the variable to the variable used by the start trigger.
Now, each time the trigger is set, it will be a unique value so that Runtime will know it's a new trigger event.

And here is an example of this logic in OptoScript, where nStartTrigger is the start trigger 32-bit integer variable and nTriggerCount is the secondary 32-bit integer variable used to increment the value that gets moved to the start trigger.

    IncrementVariable(nTriggerCount);
    if (nTriggerCount == 0) then
      nTriggerCount = 1;
    endif
    nStartTrigger = nTriggerCount;

Resolution:

Opto 22 has resolved this issue.

Questions?

Contact: Opto 22 Product Support.
Phone: 800-835-6786 or 951-695-3080
Email: support@opto22.com

DISCLAIMER

This Opto 22 Knowledge Base ('OptoKB') article is intended to provide general technical information on a particular subject or subjects and is not an exhaustive treatment of such subjects. Accordingly, the information in this OptoKB article is not intended to constitute application, design, software, or other professional engineering advice or services. Opto 22 may modify the OptoKB articles at any time. Before making any decision or taking any action which might affect your equipment, you should consult a qualified professional.

OPTO 22 DOES NOT WARRANT THE COMPLETENESS, TIMELINESS, OR ACCURACY OF THE DATA CONTAINED IN THIS OPTOKB ARTICLE AND MAY MAKE CHANGES THERETO AT ANY TIME AT ITS SOLE DISCRETION WITHOUT NOTICE. FURTHER, ALL INFORMATION CONVEYED HEREBY IS PROVIDED TO USERS 'AS IS.' IN NO EVENT SHALL OPTO 22 BE LIABLE FOR ANY DAMAGES OF ANY KIND INCLUDING DIRECT, INDIRECT INCIDENTAL, CONSEQUENTIAL, LOSS PROFIT, OR DAMAGE, EVEN IF OPTO 22 HAS BEEN ADVISED ON THE POSSIBILITY OF SUCH DAMAGES.

OPTO 22 DISCLAIMS ALL WARRANTIES WHETHER EXPRESSED OR IMPLIED WITH RESPECT TO THE INFORMATION (INCLUDING HARDWARE, SOFTWARE, AND/OR FIRMWARE) PROVIDED HEREBY, INCLUDING THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTIBILITY, AND NON-INFRINGEMENT. Note that certain jurisdictions do not sanction the exclusion of implied warranties: thus, this disclaimer may not apply to you.