PDF Versions

Errata for viewLinc 3.4.101.672Issued December 3, 2010

Errata for viewLinc 3.4.100.533
Issued April 26, 2010

Errata for viewLinc 3.4.6.2968
Issued January 27, 2010

Errata for viewLinc 3.4.6.2963
Issued January 20, 2009

Errata for viewLinc 3.4.5.2911
Issued November 27, 2009

Errata for viewLinc 3.4.4.2869
Issued October 8, 2009

Errata for viewLinc 3.4.3.1823
Issued August 20, 2009

Errata for viewLinc 3.4.3.1804
Issued July 14, 2009

Errata for viewLinc 3.4.1.1703
Issued June 12, 2009

viewLinc Errata


Errata for Vaisala Veriteq viewLinc 3.4.101.672

Issued December 3, 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.

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:
- Deactivating, reactivating, or swapping loggers from multiple client sessions simultaneously is not supported and can lead to errors. Please make sure that when you are deactivating, reactivating, or swapping loggers, other users are not performing one of these operations at the same time.

If this happens the symptoms that may be seen are: abnormal system behavior caused by concurrent logger deactivations/reactivations/swaps (for example, logger updates are not happening, portions of UI fail to load, unexpected errors in the log, etc). The workaround is to restart viewLinc Service then perform the actions again by one user.

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.

- “Daily” reports are every 24 hours, not 1 day. This can cause a shift by 1 hour when Daylight Savings time is turned on or off. The workaround is to reset the start date after each DST/STD change.

- When a scheduled report fails to run, the event log will display the complete error message instead of a friendly failure message.

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.

Real-Time Display:
- In Channel View, vertical axis sometimes shows values formatted incorrectly (e.g. 10.10 instead of 11.0). There is currently no workaround for this.

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