PDF Versions

Errata for viewLinc 3.5.2.277
Issued October 28, 2010

Errata for viewLinc 3.5.1.266
Issued July 26, 2010

Errata for viewLinc
3.5.1.266

Issued July 14, 2010

Errata for viewLinc 3.4

viewLinc Errata


Errata for Vaisala Veriteq viewLinc 3.5.2.277

Issued October 30, 2010

General:

- To ensure data timestamp accuracy, verify that the viewLinc server time is set accurately before installing the viewLinc software. The viewLinc server and logger host should also be set to have their time synchronized with an accurate source at least once a day.

- When entering text in various fields of the forms, it is necessary to tab out of the field or select another field for the new values to be saved.

UI:

- Channel updates in the browser may stop refreshing on low-activity systems and the server has disconnected message may appear. The workaround is to refresh the browser.

Alarms:

- Threshold Alarms generated during a backfill, and deactivated during the backfill, will not send activation notifications. The deactivation notification will be sent. The workaround is to add the template macros [AlarmTimestamp] and [AlarmValue] in the Threshold Restored email template.

System:

- Ensure that only one viewLinc administrator is activating, deactivating, or swapping loggers at a time.

Reporting:

- When a manual report is started during a time when scheduled reports are running or other users are generating reports, the status of the manually generated report is listed as “Queued”. The status will remain “Queued” until the queue gets to this report. This could be a significant period of time depending on the size and quantity of reports already in the queue.

- Due to the time required to generate reports, it is recommended that scheduled reports be set up to start during non-peak times and have at least 15 minutes between each report. This will reduce the chance of a scheduled report delaying a manually requested report. It is also best not to schedule reports with large data sets to start at the same time.

- “Monthly” reports are actually 31 days, not calendar months.

Logger Swapping:

- When swapping loggers it is important to allow the new Logger to come to equilibrium before placing it on the COM port. This will ensure that data recorded from outside of the environment is not included on reports.

- If a Logger that is to be swapped in is linked to a vLog Audit Trail then the swap will succeed, however, the descriptions will revert to what they were before swap on the next update. The workaround is to ensure that loggers are not linked to a vLog audit trail before attempting to swap.

For more information and updates on viewLinc, contact Veriteq technical support.