These Release Notes are established to support and introduce new releases of WebAccess HMI & SCADA software.  They provide a list of new features, known-issues and bug information.

 

Definitions:

==========

 

Official Release - This is a version that is frozen.  It will not change during the release period (typically a business quarter or 3 months).  However, the "Release Notes" for this official version will be changed during the release period to document any new problems as we discover them. The source code will not be frozen.  The Official Release will be in WebAccess Website http://webaccess.advantech.com/, labeled "Official Release" containing the NodeSetup.exe, ClientSetup.exe in different language.  The only thing we update in the Official Release folder is the Release Notes as new problems are identified.

 

Candidate Release - This is updated when there is a new Build. This adds new features for a future release and resolves know issues or problems in the Official release.  Customers can install this at their own risk. The Candidate may solve a known problem.  If it introduces new problems, customers have the option to re-install the Official Release. We maintain the source code to match this Candidate Release.  The Candidate Release will be in WebAccess Website http://webaccess.advantech.com/.  The Candidate Release will be updated through the quarter.  The release notes for the Candidate will be updated describing new features or known Issues.

 

Candidate Release GDI+ - This is the “Graphical Device Interface Plus” version of WebAccess.  It has enhanced graphical features to give lighting and 3-D effects using “Gradient Fill”, Transparency, Unlimited color palette and other enhancements.  Old graphics will be compatible with new GDI+ clients and GDI+ Draw.  However, GDI+ graphics will not be viewable in older clients or previous versions of DRAW. 

 

Candidate Release 8.2_20170817 Version

Software Build          Feature or Fix Description

Feature Enhancement: Added four webservice APIs.

Ÿ GetDataLogExt/{ProjName}

Ÿ GetDataLogExt/{ProjName}/{NodeName}

Ÿ Json/GetDataLogExt/{ProjName}

Ÿ Json/GetDataLogExt/{ProjName}/{NodeName}

Feature Enhancement: Added new device, Mitsubishi FX5U PLC Ethernet driver.

Feature Enhancement: Added new device, Mitsubishi A1S PLC programming COM port driver.

Feature Enhancement: Added new device, Mitsubishi A2S PLC programming COM port driver.

Feature Enhancement: Added new device, Siemens LOGO PLC driver.

Feature Enhancement: Added new device, ICP DAS SMS machine (GTM-204M-4GE) driver.

Feature Enhancement: Added new system tag “New Alarm”. When a new alarm occurs, the value of “New Alarm” changes to 1.

Feature Enhancement: Improved the point transfer function by adding a confirm mechanism to ensure that when multiple tags are transferred rapidly, the value is correctly updated.

Feature Enhancement: Improved the Modicon driver to support 64-bit double data type and Modbus RTU over TCP.

Feature Enhancement: Improved the MQTT driver to support the Baidu MQTT broker.

Feature Enhancement: Improved web service to support access tag fields and array tags.

Feature Enhancement: Name of the PwrMeter driver changed to “DLT645-97”.

Feature Enhancement: Periodic Excel reports can be generated manually.

Feature Enhancement: Modified the report generation process by accelerating the speed of report generation.

Feature Enhancement: Modified the parameter definition mode of culculation tag, user can set the reference point is whether to use an initial value or a final value when the communication fails.

Feature Enhancement: Modified SNMP driver, add write function (UDP), only supports DO, AO and char (-128~127).

Problem Resolved: When multiple holiday groups exist, only the first group could be selected.

Problem Resolved: When the MQTT driver was set to redundant mode, the primary/backup SCADA node switch would fail.

Problem Resolved: SCADA_agent_keeper could not boot start in Windows 7 and caused plug-and-play functionality to fail.

Problem Resolved: Error when downloading a group of 250 alarms.

Problem Resolved: PWMeter driver could not read data if the device ID contained “ox16”.

Problem Resolved: MQTT broker auto-filled IP field information was not displayed correctly in the table.

Problem Resolved: Fixed the import ADAM 3600 ASP error.

Problem Resolved: Modified the WASCADA driver to show the error screen (ASP) during remote uploads of the SCADA node.

Problem Resolved: Modified the ODBC database to show the error screen (ASP) when SCADA does not create an event log.

Problem Resolved: MQTT broker did not start automatically when powered on.

Problem Resolved: Modified the SCADA agent plug-and-play connection mechanism.

Problem Resolved: Fixed the data log issue where “datacore.exe” failed to run.

Problem Resolved: When the Alarm Group system tags were configured to log only, the alarm information still appeared in the Alarm Summary.

Problem Resolved: Increased the SPMS ODBC data processing speed.

Problem Resolved: Addressed the ICS-VU-714103 vulnerabilities of Advantech WebAccess.

Problem Resolved: Addressed the ICS-VU-010269 vulnerabilities of Advantech WebAccess.

Problem Resolved: Addressed the ICS-VU-525331 vulnerabilities of Advantech WebAccess.

Problem Resolved: Addressed the ICS-VU-346732 vulnerabilities of Advantech WebAccess.

Problem Resolved: Fixed the OPCUA communication failure related to a lack of credentials and having only a user name and password.

Problem Resolved: MQTT broker settings could not be changed.

Problem Resolved: SignalR Alarm Summary not sending push notifications.

Problem Resolved: When the array tags are configured to ODBC log, the datacore crashes.

Problem Resolved: An RTDB file error (IDX and WDB do not match) causes numerous tables to open, preventing the reading of historical data.

Problem Resolved: Webvrpcs.exe will now be recovered within three days when the task scheduler is executed.

Problem Resolved: Fixed the %AALMGLOBALN quantity error.

Problem Resolved: Fixed the vulnerabilities that occurred when LoadLibrary used an absolute path.

Problem Resolved: Modified the OPCUA driver parameter.

Problem Resolved: When the calculation point communication is abnormal, the signal point can now retain the last value or the preset value.

Problem Resolved: ASP updates implemented

Ÿ Added an auto-fill IP field to the MQTT broker.

Ÿ Added the AXVLC video device (rtsp).

Problem Resolved: Fixed the system log date format write error.

Problem Resolved: Fixed the display error for alarm messages sent to the Socket2Air device phone number.

Problem Resolved: Fixed the Excel Out function. When tag information is exported to Excel, the system will verify that the output file is in XLS format to prevent hackers from using the file name to hide important files.

Problem Resolved: Fixed the measurement point selection error where the measurement point that indicates the array size is greater than zero is also recorded.

Problem Resolved: Modified the method for activating the HJ660 option.

Problem Resolved: When multiple browsers or tabs for different projects are open, read and write errors occur during project configuration.

Problem Resolved: The device list failed to update after the device name and unit number were modified.

Problem Resolved: Fixed Eventlog could not be recorded.

Problem Resolved: Fixed the BACNet driver issue where WebAccess could not obtain the correct .Qcode value even with first polling.

Problem Resolved: Fixed the Siemens S7 driver issue where one byte is lost when reading the last tag.

Problem Resolved: Fixed the issue where the Modbus server would not allow the text tag to write or add text swap conversion code.

Problem Resolved: Fixed the issue where high-volume action logging would cause a view crash.

Problem Resolved: Fixed the vulnerabilities caused by buffer overflow.

Problem Resolved: The datacore status will be checked regularly and errors will be logged.

Problem Resolved: Fixed a minor bug in BITMAP related to the SESRUN hidden command.

Problem Resolved: Following a Windows update, a SNMP driver communication failure would occur.

Problem Resolved: For the Mewtocol driver, “<” and “%” can be used in the header.

Problem Resolved: Unable to send SMS via the Socket2air driver.

Problem Resolved: When a tag name comprises only numbers, commas are added automatically in the log page.

Problem Resolved: Logs could not be organized according to date and time on a webpage.

Problem Resolved: To modify the Alarm Management configuration settings, the entire SCADA node needed to be downloaded.

Problem Resolved: A username and password required to log into the Excel report page.

Problem Resolved: Excel report UI display errors in the French language version.

Problem Resolved: The tag list and report list could not be displayed correctly because they contained special characters.

Problem Resolved: Modified unable to ACK when reply alarm email to ACK.

Problem Resolved: Modified MYSQL driver will crash sometimes.

Problem Resolved: Modified Event Log function, when datacore is start, event log has no record about # of log samples after event.

Problem Resolved: Moified when install Project Node only, WARTCommunication.exe will cause memory leak.

Problem Resolved: Add ATZ Command in SenSMS.

Problem Resolved: Modified Mitsubishi FX5U driver reading error when read X and Y register.

Problem Resolved: Modified in French version, Google map cannot be displayed normally.

WebAccess Dashboard 1.0

Problem Resolved: Removed looping through all tags in the tag list.

Problem Resolved: Widget builder updated

1) Fixed the issue where dragging, copying, or pasting objects caused changes to their width and height.

2) The default refresh time has been changed from 1 minute to 5 seconds.

Problem Resolved: Modified the login process.

Problem Resolved: Removed the debugger message.

Problem Resolved: The phone board has been modified to support sliding, and the widget phone layout has been adjusted.

Problem Resolved: Fixed the issue where spline2 appeared on the phone.

Problem Resolved: Fixed the integer-to-string conversion error.

Problem Resolved: The missing OnOffHov.png and Switch_1Hov.png are now provided.

Problem Resolved: The tag list button goes missing after the builder widget is updated or refreshed.

Problem Resolved: Fixed the issue of the widget builder ID having two guides.

Problem Resolved: Fixed the issue where a line becomes a rectangle (configured properties should be saved immediately).

Problem Resolved: Fixed the bug where only the first page could be read when the test list is open.

Problem Resolved: Fixed the bug where the default meter and text phone widgets could not present values.

Problem Resolved: Custom widgets could not be displayed.

Problem Resolved: Fixed the issue where the dashboard could not connect to Node-RED when in debug mode.

Problem Resolved: Corrected the functionality of the <almacks> and <almack> buttons.

Problem Resolved: When inserting text, the <shift> button does not function, preventing users from typing “+”, “_”, etc.

Problem Resolved: In animation “fill” mode, the “fill On” property remained causing the animation to behave unexpectedly.

Problem Resolved: Unable to animate color in the animation.

 

Candidate Release 8.2_20161121 version

Software Build          Feature or Fix Description

Feature Enhanced: Provide MQTT Broker to receive data from Advantech IoT Gateway and devices, such as WISE-4000 series wireless modules, ADAM-3600, ECU-1152 ,etc.

Feature Enhanced: As MQTT Client, connect to WebAccess/Cloud through MQTT driver over WebSocket, has whitelist to choose tags to publish data.

Feature Enhanced: Add Java Script analysis with JSHint.

Feature Enhanced: New device, EtherNet/IP for AB ControlLogix and CompactLogix Series PLC with tag name access driver.

Feature Enhanced: New device, Advantech B+B Wzzard MQTT driver, follow B+B Wzzard data transmission format.

Feature Enhanced: New device, CODESYS API Driver for Advantech PAC.

Feature Enhanced: Add EKI-1322 SMS driver.

Feature Enhanced: Add ‘==’ option and string comparison function for Event Log.

Feature Enhanced: Add a system tag to show alarm number in alarm group.

Feature Enhanced: Add inspection mechanism for BACNet Server, once check the set, will start BACNet Server service automatically.

Feature Enhanced: Add display tag list by page for WebService.

Feature Enhanced: Check user permission according to different project for WebService.

Feature Enhanced: Enhance some functions in Excel Report

Ÿ Tag type : analog, discrete, text, analog change.

Ÿ Record type : Data Log, ODBC, alarm log, action log, event log.

Ÿ Database type : Access, MySQL, SQL Server, Orcale.

Ÿ Tag value filter(alarm value == 0).

Ÿ Add Tag description.

Feature Enhanced: Add import and export function for user list and the marks of Baidu map.

Feature Enhanced: Show the “Running” status of each SCADA Node.

Feature Enhanced: Add “Enable OPCUA Server” option in SCADA Node property, start OPCUA Server automatically.

Problem Resolved:  Add same user in Project Node and SCADA Node, when login to Dashboard Viewer, will show error message “Account Limited Authorization”.

Problem Resolved:  Cannot send mail directly in Excel Report view mode and "Send Email" button disappear.

Problem Resolved:  Modify login verification for WebService and Dashboard.

Problem Resolved:  DSP popup has some issues after open a new tab in IE browser.

Problem Resolved:  IVSEvent reporter application crash.

Problem Resolved:  Sometimes can’t get the data from RTDB.

Problem Resolved:  Modify Siemens drivers.

Ÿ SiemS7#.DLL --> Add Serial interface (MPI)

Ÿ SiemS72#.DLL --> Add TCPIP interface

Ÿ SiemS7DR.DLL

                             -->Fix TSAP handling bug,  the first 2 number shoud be HEX, old one treat it as decimal was wrong.

                             -->Add error error quality code B080 for no data returned in communication.

Problem Resolved:  Modify Omron drivers.

Ÿ OmronCP#.DLL to support OMRON CP series PLC directly.

Ÿ OMRONDrv.DLL to support CP series.

Ÿ OMRONDrv.DLL, fix the text tag cannot record to database.

Problem Resolved:  When exporting too much tags with Event Log, Modbus Server tags and BACNet Server tags through the Excel Out tool, unable to complete export all the information.

Problem Resolved:  Different projects, if the Event Log name is the same, will cause query error.

Problem Resolved:  Use video display to show log list, but doesn’t display properly.

Problem Resolved:  In redundant mode, when the primary node recovery, the backup node did not sync the data to the primary node.

Problem Resolved:  In redundant mode, when the primary node and backup node starts at the same time, will cause datacore crash.

Problem Resolved:  In redundant mode, device switching between primary and backup, but only switch from the primary to the backup, cannot return from the backup to the ptimary.

Problem Resolved:  Unable to get the constant (Discrete) tag value in ViewDAQ.

Problem Resolved:  Modify WASCADA driver, when the frequency of tag record into ODBC is less than 1 minute, will cause datacore crash.

Problem Resolved:  Increase the length of device name, expand to 31 characters by 16 characters.

Problem Resolved:  Unable to check the data from Datalog, when open a historical trend in Dashboard, the trend will be locked.

Problem Resolved:  The minute data of RTDB can’t be backup and delete during the data maintenance.

Problem Resolved:  Webvrpcs.exe will be crash once open DrawDAQ or download graph only.

Problem Resolved:  Unable to send email normally when alarm occurs.

Problem Resolved:  Due to RTDB Share memory issue, when open multi views to show datalog trend, viewDAQ will crash.

Problem Resolved:  When the kernel is simulation mode, the time stamp of the Alarm Log seems strange. The Alarm Summary does not display it.

Problem Resolved:  When the alarm lines in one trend are more than 10, bwview.exe will crash.

Problem Resolved:  When query data from datalog without start time, the number of records is more than 25, will cause error.

Problem Resolved:  Fixed Vulnerability: Advantech WebAccess 8.1 ActiveX buffer overflow.

Problem Resolved:  When the project node and SCADA node is installed in different computer, cannot check Dashboard.

Problem Resolved:  If a tag set alarm, it will show 0 in Excel Report (ODBC).

Problem Resolved:  The date in WebAccess software version is not same with the data show on the homepage.

WebAccess Dashboard 1.0

Problem Resolved:  "change size of multi objects" , after copy and paste multi objects will result grouping error therefor add a check if the action is in paste mode change size shouldn't modify AllIdOfPasteObj.

Problem Resolved:  Increase the length of device name, expand to 31 characters by 16 characters.

Problem Resolved:  Widget Builder smallicon not up-to-date issue

Problem Resolved:  When open a new dashboard, builder widget sometimes will change size (open twice) issue

Problem Resolved:  Modify the menu list to show the correct Dashboard list based on the login permissions.

Problem Resolved:  Widgets can't be uploaded.

Problem Resolved:  Widget builder gradient effect change color in animation

Problem Resolved:  Can’t modify the color gauge.

Problem Resolved:  Widget Builder Update:

1) Fixed gif file display overlap issue

2) Fixed copy / past object ID not change issue

3) Fixed multiple buttons cannot bind tags issue

4) Change tag selection to filter pop-up window

5) Fixed prevent drawPanelGroup get undefined issue

6) Set the correct property, prevent H/V expand issue

7) Remove old construct tag list, droped, replaced by tag selection to filter pop-up window

 

Candidate Release 8.1_20160519 version

Software Build          Feature or Fix Description

Feature Enhanced: Integration with WebAccess/IVS is done to provide real-time video monitoring and IVS-event video playback.

Feature Enhanced: Connection to the web server on project node now supports HTTPS.

Feature Enhanced: SCADA node now can act as an OPC UA Server.

Feature Enhanced: A new device type, DNP3TCP, is added to act as a DNP 3.0 L1/L2 client.

Feature Enhanced: Some drivers are enhanced to support EKI-1321L. They are ACEFAM3, ADAM5KASC, MitsuA, MitsuAnA, MitsuFx, MitsuFx2, MitsuFx3, MitsuQl, Modiconl, OmronCl, OmronCJ, OmronCS, OmronCV, SiemS72, WISEM501, WISEM502, and WebOP.

Feature Enhanced: The bad values in Event Log now can be displayed as either “-1” or “*”.

Feature Enhanced: Mail servers with SSL now are supported.

Feature Enhanced: A restricted user privilege is added for project users.

 

Problem Resolved: Alarm emails failed to send when multiple alarms occurred at the same time.

 

Problem Resolved: Alarms failed to be acknowledged in dashboard.

 

Problem Resolved: Kernel cannot be stopped when BwUPS driver was used.

 

Problem Resolved: Multiple buffer-overrun vulnerabilities in BwAspObj.dll were patched.

 

Problem Resolved: A buffer-overrun vulnerability in cellvision.ocx was removed by deleting and unregistering the ocx.

 

Problem Resolved: The vulnerability to reveal password in Project User web page was patched.

 

Problem Resolved: Multiple errors occurred when updating project and node property pages.

 

Problem Resolved: SignalR failed to be connected when HTTPS connection to web server on project node was used on Windows8 and Windows Server 2012 or later.

Problem Resolved: Primary keys “Proj” and “Node” in BwPData.mdb was added to fix data recording error in certain circumstances.

Problem Resolved: Alarm information for calculation tags failed to be shown in Alarm Summary.

Problem Resolved: Simulation mode may fail to be turned on.

Problem Resolved: Miscellaneous errors were fixed in OPC DA Driver.

Problem Resolved: Text tags in OPC UA Driver failed to be recorded in ODBC log.

Problem Resolved: Bugs fixed for three dashboard widgets: actionlog, textValue1 and textValue2.

Problem Resolved: Dashboard failed to display vertical and horizontal line width.

Problem Resolved: ViewDAQ and View client may crash when displaying IVS event log.

Problem Resolved: Web Service failed to work when multiple http ports in IIS were configured.

Problem Resolved: Dashboard failed to work when project and/or node names were changed.

Problem Resolved: Bugs fixed for Hardkey related errors.

Problem Resolved: Mitsubishi FX2N D8/M8/Y/S driver failed to write to the device correctly.

Problem Resolved: Intel IEEE floating conversion for Modicon driver was added.

Problem Resolved: Data may fail to be synchronized between the primary node and the backup node.

 

Candidate Release 8.1_20151230 version

Software Build          Feature or Fix Description

Feature Enhanced: A new drawing tool, Widget Builder, is added for users to create user defined widgets for Dashboard.

Feature Enhanced: Dashboard now supports import and export functions for widget, dashboard and dashboard project.

Feature Enhanced: Web Service now supports SignalR.

Feature Enhanced: Use <SENDPTZ>v1=dashboard#dname to switch dashboard that is embedded in graph.

Problem Resolved: WASCADA driver failed to work correctly when there are too few tags configured.

Problem Resolved: Fixed the issue that the declaration of BwDeviceA and BwMdb table in bwcfg.mdb is not consistent.

Problem Resolved: A new alarm email mechanism was implemented to avoid blocking global script execution.

Problem Resolved: Add reference line in Datalog trend display in ViewDAQ and View Client.

Problem Resolved: ODBC data now can be saved optionally with a time stamp at either the start or the end of the recording interval.

Problem Resolved: Enhanced Backup and Restore function.

Candidate Release 8.0_20150816 version

Software Build          Feature or Fix Description

Feature Enhanced: Enhance OpcTool.

Feature Enhanced: Add “Update” and “Delete” function in Excel Report.

Feature Enhanced: Add “New Report” function in Excel Report.

Feature Enhanced: MP4 format is now supported by the video widget.

Feature Enhanced: Auto-start IIS to reduce boot time for Windows Embedded.

Feature Enhanced: Excel Report now supports xlsm format.

Feature Enhanced: The user name of Web Service is case-sensitive.

Feature Enhanced: Keep the last value in Data Log Trend.

Feature Enhanced: APAX-5580 driver is added.

Feature Enhanced: Video Widget is added for dashboard.

Problem Resolved: The transmission will not resume after disabling and then enabling the COM port for WASCADA driver.

Problem Resolved: The Simplified Chinese characters could not be displayed properly in WebAccess Express for Win 7 Embedded version.

Problem Resolved: Bwswfcfg.exe was misrecognized as a virus by various antivirus programs. The file was removed after installation to prevent the warning.

Problem Resolved: Fixed the URL error when clicking new query for log displays inside ViewDAQ and View Client.

Problem Resolved: Add comport number option for Upload Remote Node.

Problem Resolved: Fixed Google Map display issue after renaming project.

Problem Resolved: The offset function in ABPLC driver failed to work properly.

Problem Resolved: Retry count in Datacore didn’t work for the first packet.

Problem Resolved: SNMP Driver failed to parse packets correctly.

Problem Resolved: Due to the security issue of Microsoft speech component in IE5, IE6, IE7, we upgrade related DLLs to prevent the vulnerability. Strongly recommend our user to patch Security Update for IE (933566).
See more information:
National Security database link: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-2222
Microsoft Security update report link: https://technet.microsoft.com/library/security/ms07-033

Problem Resolved: Data Log Trend widget caused dashboard to stop responding when invalid tags existed.

Problem Resolved: The Config UI displayed error while switching away from Data Log Trend widget.

Problem Resolved: Miscellaneous performance improvements for dashboard widgets.

Problem Resolved: Undo function failed to work properly when removing dashboard widgets.

 

Candidate Release 8.0_20150412 version

Software Build          Feature or Fix Description

 

Feature Enhanced: A new calendar dialog box was added to handle date selecting for Report.

 

Feature Enhanced: A new parameter was added to allow users to set either desktop mode or mobile mode for Dashboard page that was embedded in ViewDaq/View client.

 

Feature Enhanced: OPC Server now utilizes share memory mechanism to enhance performance in data communication with datacore.exe for WebAccess 8.0.

 

Feature Enhanced: Google Maps projects can now be exported and imported using Excel file format.

 

Feature Enhanced: Excel Report now can be used with data logged to ODBC.

 

Feature Enhanced: A new mechanism is added now for easy SRP integration.

 

Feature Enhanced: WebAccess Express is upgraded to version 3.4.8.

 

Feature EnhancedThe new BACnet Server declares it does not support segmentation. So, the other program does not request very large data. Update FileBwBacDrvJ.dll_20141223

   Feature Enhanced: The BACnet Server can now handle a larger response packet up to 280 points. Update FileBwBacDrvJ.dll_20141223

Feature Enhanced: Maximum number of datalog tags for the WaGetDataLog and VdBroadWinGetLocalDataLog function is now increased to 100. Update file: WebSvcObj.dll and Viewdll1.dll

Feature Enhanced: The VdBroadWinGetLocalDataLog function now returns minute, hourly and daily data aligned on the minute, hour and day, respectively. Update file: Viewdll1.dll

Feature Enhanced: WebAccess Express v3.4.6 release.

Feature Enhanced: Web service function enhanced Added tag list filter in Data log. Support internal tags and block tag list.

Feature Enhanced: Add SMS support for UNO-2272 SMS Modem.

Feature Enhanced: Remove the data limitation for retransmission (Store and forward) when RTDB is used.

 

Feature Enhanced: Dashboard Widget supports Digital I/O, except for the Gauge and Meter Widget.

Feature Enhanced: Save All feature in dashboard Editor is added now. User can now save all dashboard pages at once.

Feature Enhanced: User can now right click folder icon in tree list to create a new dashboard page.

Feature Enhanced: Undo function in Dashboard Editor is added.

   Feature Enhanced: Internal tag information is now supported in the Point Information Widget.

Feature Enhanced: Tag list now only lists datalog tags for various historical trend widgets like Historical Bar Group Comparison, Historical Bar, Historical Area Trend, Historical Bar Trend, Historical Bar Line, and Historical Line.

Feature Enhanced: Support Left clicking on the markers in Google Map to link to the Dashboard page.

 

Feature Enhanced: Dashboard Widget updates.

 

Feature Enhanced: 30-second refresh time limitation is removed.

 

Problem Resolved: When project name was changed in Configuration, Google Maps project name failed to change accordingly.

 

Problem Resolved: Asp page may encounter error when New Query in Text Tag Log was clicked.

 

Problem Resolved: Upload Remote Node failed to work when there were more than 20 WAScada nodes.

 

Problem Resolved: When data field is NULL, BWDBDrv failed to return the empty string.

 

Problem Resolved: WAScada datacore crashed when there were multiple ports configured.

 

Problem Resolved: AB PLC driver failed to write when point type was string and failed to read when point type was long.

 

Problem Resolved: Get value function is now performing as designed by updating every second when scan rate is set below 1 second and updating accordingly when scan rate is set to more than 1 second.

 

Problem Resolved: Alarm Log failed to synchronize to backup node when recovering from disconnected cable.

 

Problem Resolved: Associated analog value in Alarm Summary disappeared on backup node when there were multiple alarms generated simultaneously.

 

Problem Resolved: Webvrpcs.exe crashed when there were too many disabled alarms.

 

Problem Resolved: Internal buffer was increased twice in BwTcpip to avoid WAScada crashed.

 

Problem Resolved: GetTagValueText failed to support hex value in Web Service.

 

Problem Resolved: Log to ODBC failed to insert correct text values when they contained ‘-‘.

 

Problem Resolved: The message - “All SCADA Nodes are offline” - may appear when entering Dashboard Viewer.

 

Problem Resolved:  Tag values failed to update correctly after switching Dashboard pages.

 

Problem Resolved: The device ID for BACnet driver should be only 1 byte, but the device ID in the old driver contains 2 bytes. Update File:BwBacDrvJ.dll_20141223

Problem Resolved: Some programs failed to recognize and communicate with the BACnet driver. Update FileBwBacDrvJ.dll_20141223

Problem Resolved: The VdBroadWinGetLocalDataLog function occasionally failed to retrieve hourly and daily data in RTDB. Update file:WaDBs.dll

Problem Resolved: Duplicated data records may appear in RTDB. Update file:WaDBs.dll

   Problem Resolved: Memory leak occurred in RTDB. Update file:WaDBs.dll and Viewdll1.dll

   Problem Resolved: Memory allocated for WaDbRead was not enough in RTDB. Update file: WaDBs.dll

Problem Resolved: Data failed to be correctly retrieved from RTDB for time interval greater than or equal to 4 hours. Update file: WaDBs.dll

Problem Resolved: Instead of being promptly recorded as value change or quality change, data was postponed to be recorded to RTDB on the hour. Update file: Datacore.exe.

   Problem Resolved: Date failed to be displayed correctly in Excel Report.

Problem Resolved: Report date failed to show correctly in Excel Report.

   Problem Resolved: WhenAllwas selected as the maximum line per page option, log display pages may fail. Now when All is selected, maximum line per page will be set to 1440.

Problem Resolved: EXCEL Report failed to be displayed inside the web page.

Problem Resolved: The Demand Control function could not start in Backup SCADA when primary SCADA goes offline.

Problem Resolved: The first data record in Event log was incorrect. Update file:BwEvntUp

Problem Resolved: The return value of the GetValueText function for Analog & Discrete Tag is empty.

Problem Resolved: When IIS port was not set as 80, SignalR failed to work correctly. As a result, data failed to be displayed correctly in dashboard.

 

   Problem Resolved: Tag Value cannot display in Vertical Text Value Widget Tag if Tag name contains- symbol.

Problem Resolved: Failed to detect illegal characters when Widget Preference was saved.

   Problem Resolved: Widget Title background failed to be uploaded.

   Problem ResolvedSingle Line Text Widget failed to upload the right and left icon consecutively.

Problem Resolved: Lucida Sans font is now not supported for Google Chrome Browser.

 

Problem Resolved: Widget name changed incorrectly as undo applied.

 

Problem Resolved: Hyperlink failed to work correctly in Google Map widget.

 

 

8.0-2014.10.31

Feature Enhanced: New generation of WebAccess HMI – Business Intelligence Dashboard which provides users with cross-platform, cross-browser data analysis and user interface based on HTML5 technology. Dashboard functions include Editor, Viewer, and built-in widgets such as trends, bars, alarm summary, maps, et cetera.

 

Feature Enhanced: The new Excel Report function allows users to define Excel templates which automatically generate daily, weekly, monthly, yearly, or on-demand report in the EXCEL format. The Excel Report function is also web-based that can be generated and viewed in web browser anytime and anywhere.

 

Feature Enhanced: Provide Web Services interface for partners to integrate WebAccess data into APPs or application system.

 

Feature Enhanced: Support Modbus server with multi-port/Multi-device access and text point read function defined in moddefs.ini.

 

Problem Resolved: WebAccess trend synchronization feature in WASCADA driver now works correctly when the server-side Scada node uses RTDB to store data log. RTDB handling procedure in Datacore.exe was revised to fix the issue.

 

Problem Resolved: The ODBC timestamp is offset by one time interval when Wascada driver synchronizes trend and ODBC data

 

Problem Resolved: WaDbTable.dll may stop responding if a user program continuously calls WaGetLocalDataLog() for a long period of time while WebAccess kernel is running. Internal memory handling mechanism for second data in Datacore.exe was revised to fix the issue.

 

Problem Resolved: Fix the issue that DrawDAQ/Draw Client may crash when adding an icon file in Toolbar configuration dialog box.

 

Problem Resolved: Fix the issue that Panasonic PLC driver fails to return correct values for block tags with negative values. Driver is non-supported ASCII code.

 

Problem Resolved: Resolve the issue that Datacore.exe may crash when there are no tags configured for the SCADA node.

 

Problem Resolved: Resolve the issue that marker dialog box in the Google Maps function fails to popup due to version upgrade by Google Maps server.

 

Problem Resolved: Resolve the issue that SIEMENS PLC driver fails to read Text point if users configure the text point with WORD or DWORD type address.

 

Problem Resolved: Resolve the issue that warptagent.exe crashes when connection to BwCfg.mdb fails.

 

Problem Resolved: Resolve that issue that reply Alarm Email to Acknowledge the Alarm in Alarm Management System function fails to work.

 

Problem Resolved: BACnet Driver (BwBacDrvJ.DLL) sends Vender ID (150) with only one byte instead of two bytes to comply with BACnet standard.

 

Candidate Release 7.2_20140730 version

Software Build          Feature or Fix Description

7.2-2014.07.30

Problem Resolved: Datacore may stop responding when scanning multiple devices in parallel.

 

Problem Resolved: Classroom scheduler cannot be downloaded to backup node.

 

Problem Resolved: Text values containing 2-byte characters cannot be set correctly to WebOP devices.

 

Problem Resolved: The HIKVision Video type was updated to support the latest HIKVision network cameras and video servers.

 

Problem Resolved: Fix the typing rule of password in Administrator/Project Users function. User cant type more than eight characters. The limitation for password is eight characters.

 

Problem Resolved: The area of video display in ViewDAQ/View Client failed to be included as part of hardcopy printout on Windows 8.1 with IE 11 installed.

 

Problem Resolved: I/O tagnames containing - character cannot be deleted from tag list.

 

Problem Resolved: Constant tags created under API/BwConst cannot be logged to ODBC.

 

Problem Resolved: The ODBC time stamp is offset one interval time when Wascada driver synchronizes trend and ODBC data. Modify BwWriteOdbcLog to fix the bug issue.

 

Problem Resolved: WaTable.dll may stop response if user program continuously calls WaGetLocalDataLog() for a long period while WebAccess kernel is running. Modify internal memory handling for second data to fix the problem.

 

Problem Resolved: Webvact.ocx has been updated to allow thirty-party integration to navigate graph pages by changing CotoCmd property without reloading the OCX.

 

Problem Resolved: Buffer overrun issue regarding string-type properties in webdact.ocx and webvact.ocx has also been fixed.

 

Candidate Release 7.2_20140606 version

Software Build          Feature or Fix Description

7.2-2014.06.06

Feature Enhanced: The Samsung SNP-6200RH Camera video type was added to support Samsung network cameras.        

 

Feature Enhanced: New Event Log allows recording data continuously while the event condition met.

 

Feature Enhanced: Add Associated Analog Tag in Discrete Tag ALARM Properties.  Associated Analog Tag value can be displayed in Alarm Summary page for discrete tag.

 

Feature Enhanced: Enhanced the WebAccess soft keyboard operation. Use the setting in bwclient.ini under WebAccess\Node to define the size of soft keyboard for Text Change Dialog Box and Login Dialog Box, respectively.     

 

Feature Enhanced: The WebAccess Express support SUSIAccess devices and all computers. WebAccess Express Version 3.4.3

 

Problem Resolved: The Vivotek FD8134V and Vivotek FD8335H video type was updated to support the latest Vivotek network cameras and video servers.

 

Problem Resolved: The Pixord ND637E video type was updated to support the latest Pixord network cameras and video servers.

 

Problem Resolved: Bug fixes for the IE 11 incompatible issue regarding flash support. Update fileswfalsh HTML file

 

Problem Resolved: Bug fixed typing Chinese error in WebAccess DrawDAQ when editing the graphic page in Windows 7 Traditional Chinese operation system. 

 

Problem Resolved: Bug fixed double clicking on Create Marker in Google Maps shows ironic message.       

 

Problem Resolved: WebAccess communicates with APAX problem in discrete tag. File affected:Mod_dev.dll    

 

Problem Resolved: Alarm Management system cant send the SMS/E-mail from WebAccess versions between 2013/11 and 2014/04. File affected:Datacore.exe         

 

Problem Resolved: BACnet server may cause error if there is no AI tag configured. File affected:BwBacdrvj.dll 

 

Problem Resolved: WAScada driver miss data in trend data synchronization. File affected:SCADADrv.dll

 

Problem Resolved: Bug fix. Scheduler does not run on backup node, when backup node is active..

 

Problem Resolved: Bug fix. There is no data display in the shift report receiving from email while it shows correctly in IE.

 

Candidate Release 7.2_20140303 version

Software Build          Feature or Fix Description

 

7.2-2014.03.03

Feature Enhanced: Enhanced Google Maps Alarm status display configuration.

 

Feature Enhanced: Enhanced the WebAccess keyboard configuration. Use the script setting in bwclient.ini under WebAccess\Node to initially turn on CAPS LOCK for Text Change Dialog Box and Login Dialog Box, respectively.

 

7.2-2014.01.20

Problem Resolved: "Keep last value" for discrete point does not work as expected in WebAccess View programs. File updated: Bwkrlapi.dll

 

7.2-2014.01.10

Feature Enhanced: Add IPV6 support for UDP. File updated: BwTcpip.dll

 

7.2-2014.02.10

Feature Enhanced: Enhanced WAScada feature to allow center node to use connection initiated by remote node. File updated: Datacore.exe, scadadrv.dll, BWTcpip.dll.

 

Feature Enhanced: Change ADAM5K device name to ADAM5KA, to distinguish ADAM 5000 using ASCII protocol from Modbus protocol. File updated: add ADAM5KA.dll. There is no impact on existing ADAM5K user. Newly installed WebAccess show ADAM5A only.

 

Problem Resolved: " Incorrect Language Version. System running in simulation mode." Is incorrectly prompted when datacore is failed to load control file. File updated: Datacore.exe

 

Problem Resolved: WebAccess default enable 8dot3name option during installation on all volumes.

 

7.2-2014.01.24

Problem Resolved: Datacore may stop response when the alarms change quickly while the system load is heavy. File updated: Datacore.exe.

 

Problem Resolved: "Keep last value" for discrete point does not work as expected in WebAccess View programs. File updated: Bwkrlapi.dll

 

7.2-2014.01.10

Feature Enhanced: Add IPV6 support for UDP. File updated: BwTcpip.dll

 

7.2-2013.12.15

Feature Enhanced: Supports tag ODBC data synchronization in WASCADA driver. File updated: BwODBCP.DLL, SCADADrv.dll and datacore.exe.

 

Feature Enhanced: Supports ADAM-4069. File updated: ADAM4k.DLL.

 

Feature Enhanced: Supports Mitsubishi device in format 4 without CR-LF. File updated: MITSUAX.DLL.

 

Feature Enhanced: Compatibility update for WebView client connects to old kernel to prevent unnecessary login dialog box pop up. File updated: BWKRLAPI.DLL.

 

Problem Resolved: All TCP device drivers connected to the scada node itself if the backup device IP is blank when the primary device failed. File updated: BwTcpip.dll

 

Problem Resolved: Download faceplate from faceplate configuration page caused incorrect data in faceplate page. File updated: BwDatimg.dll

 

7.2-2013.11.14

Feature Enhanced: Add a tag field SCANFG to act as a flag to reflect the scan status of a tag. Setting value of the tag field to 0 while waiting for its value becoming 1 can be used to determine whether the tag bas been scanned at least once. File updated: datacode.exe, bwkrlapi.dll, bwview.exe, bwwebv.exe, bescrp.exe, viewtag.dat.

 

Feature Enhanced: Streamline the creation process for virtual directories needed for WebAccess. File updated: AppPoolAssign.exe, bwwfaa.exe.

 

Problem Resolved: Stack Buffer Overflow Remote Code Execution vulnerabilities discovered in webdact.ocx and webvact.ocx have been patched. File updated: webdact.ocx, webvact.ocx.

 

Problem Resolved: SQL Injection Remote Code Execution vulnerability discovered in DBVisitor.dll has been patched. File updated: DBVisitor.dll.

 

Feature Enhanced: Miscellaneous translation updates for ASP. File updated: aspvcobj.dll.

 

Problem Resolved: Miscellaneous bug fixes for ASP code used in Configuration.

 

7.2-2013.11.01

Feature Enhanced: .Net Framework 4.0 installation packages are now included in WebAccess. The correct version of .Net Framework 4.0 will be installed if needed. File updated: dotnetsetup.exe.

 

Feature Enhanced: Miscellaneous translation updates for ASP. File updated: aspvcobj.dll.

 

Problem Resolved: Bug fixes for datalog retrieval functions in viewdll1.dll. File updated: viewdll1.dll.

 

Feature Enhanced: Analog and discrete point ODBC data from WAScada driver’s tag with /T option will be restored from remote node after lost connection. File updated: datacore.exe, SCADADrv.dll.

 

Problem resolved: SMS message sent only to 1st phone number configured. 2nd and more numbers were ignored in old version. File updated: datacore.exe.

 

Problem resolved: Datacore.exe may crash if a point alarm to normal delay time is configured without any alarm setting. File updated: datacore.exe.

 

7.2-2013.10.30

Feature Enhanced: WebAccess Express 3.2.

 

Feature Enhanced: The messoa video type was added to work with MESSOA network Cameras and video servers. PTZ controls for this video type is also supported. File updated: bwview.exe, bwwebv.exe, messoa.htm, messoa.cab and bwnode.mdb.

 

Feature Enhanced: The compro video type was added to work with COMPRO network cameras. File updated: compro.htm, compro.cab and bwnode.mdb.

 

Problem Resolved: The ACTi video type was updated to work with the latest ACTi network cameras and video servers. File updated: acti.htm, acti.cab and bwnode.mdb.

 

7.2-2013.10.28

Problem Resolved: Datacore may cause application error in primary node in redundant system configuration mostly when primary node is busy. This issue was introduced when remote access code is implemented in intra-node communication around mid-2013. File updated: Datacore.exe.

 

Feature Enhanced: Google Map tracking, allows user put marker on Google map with position information in a text point in real-time.

 

7.2-2013.10.24

Feature Enhanced: 2 System tag parameters, DEVTPON and DevTpOff are added to support total number of all Online and Offline devices for specified device type. File updated: Datacore.exe and bwnode.mdb.

 

Feature Enhanced: In BACnet server, "UNITS" property index 117 is supported for the following objects : AI, AO, AV, Demand-Limit and Load-Limit.

Properties of "Notification Class" object, except "Profile Name", are also supported. File updated: Datacore.exe.

 

Feature Enhanced: 75-tag free version is no longer supported. File updated: DATACORE.EXE.

 

Problem Resolved: In some cases, text point with length 0 may cause run-time application error on datacore.exe. File updated: BwDatimg.DLL.

 

7.2-2013.10.22

Feature Enhanced: SNMP driver allows user to select maximum number OID per request. User may select maximum to 1 OID per request to avoid some SNMP devices report all requested object fail when one of the data not available. File updated: BWSNMP#.DLL, BWSNMP.DLL.

 

7.2-2013.10.17     

Problem Resolved: Remove 10000-tag limitation when converting old datalog data to RTDB. File updated: ConvToRTDB.EXE.

 

Feature Enhanced: Auto-assign AppPool .NET framework settings for virtual directories used by WebAccess. File updated: AppPoolAssign.exe.

 

7.2-2013.10.02

Feature Enhanced: Support TCP connection to Mitsubishi FX series PLCs. File updated: MitsuFX#.DLL, MitsuFX2#.DLL, MitsuFX3#.DLL and MitsuAX.DLL.

 

Feature Enhanced: TPC-1x71H Driver is added to support I/O on TPC-1x71. Type: TCPIP. File updated: BwNode.mdb, TPC1X71H#.DLL and TPC1X71H.DLL.

 

Feature Enhanced: Create 3 more virtual directories for WebAccess Express and other future feature enhancements. File updated: bwwfaa.exe.

 

Feature Enhanced: Add the following tag fields for tag manipulation: EXTNA0, EXTNA1, EXTNA2, EXTNA3, EXTNA4, EXTNA5, EXTNA6, EXTNA7, EXTNA8, EXTNA9, EXTNT0, EXTNT1, EXTNT2, EXTNT3, EXTNT4, EXTNT5, EXTNT6, EXTNT7, EXTNT8, and EXTNT9. File updated: bwview.exe, bwwebv.exe, bwscrp,exe, viewdll.dll, bwdraw.exe, bwwebd.exe, datacore.exe, bwdataup.exe, bwkrlapi.dll, BwSyncDb.exe, scadadrv.dll.

 

Feature Enhanced: Add the following Daq tags for alarm summary and alarm group display customization: %TALMSUMC(,%TALMSUMD(,%TALMGRPB(, %TALMGRPC(. File updated: bwview.exe, bwwebv.exe, bwdraw.exe, bwwebd.exe.

 

Feature Enhanced: EKI Driver is added to support all EKI devices using SNMP protocol. Type: TCPIP. File updated: BwNode.mdb, EKI#.DLL and BWSNMP.DLL

 

7.2-2013.09.27

Feature Enhanced: Mewtocol Driver is added to support Panasonic FP series PLC and controller. Type: Serial and TCPIP. File updated: BwNode.mdb, Mewtocol#.DLL and Mewtocol.DLL.

 

7.2-2013.09.24

Feature Enhanced: APAX KW WebAccess Integration, WebAccess APAX driver can import Variables from a CSV file, which exports from APAX KW software.

File updated: APAX#.DLL, MOD_DEV.DLL bwnode.mdb.

 

Feature Enhanced: Added 64-bit IEEE double precision Real number conversion support for APAX and Modicon devices. IEEE-Double Big Endian and IEEE-Double Little Endian types are added to the devices. File updated:APAX#.DLL, MODICON#.DLL and MOD_DEV.DLL.

 

7.2-2013.09.12

Feature Enhanced: Get Datalog data now support backup node. File updated: viewdll1.dll, viewdll1.h, viewdll1.lib.

 

7.2-2013.08.25

Feature Enhanced: Support FINS protocol to all OMRON PLCs on serial connection. File updated: OmronC#.DLL, OmronCJ#.DLL, OmronCS#.DLL, OmronCV#.DLL and OMRONDRV.DLL.

 

Problem Resolved: OPCTOOL failed if OPC node configured with remote access code. This error was introduced when we patched ASP security vulnerabilities in the 7.0-2012.03.18 release. File updated: OPCTOOL.EXE.

 

7.2-2013.08.18

Feature Enhanced: IPv6 support. File updated: webdact.ocx, webvact.ocx, datacore.exe, bwtcpip.dll, bwtcpipv6.dll, Scadadrv.dll. Note: For all the previous WebAccess versions to patch new datacore.exe or Scadadrv.dll, BWTcpipV6.dll and Bwtcpip.dll are also need to be updated.

 

7.2-2013.08.05

Feature Enhanced: GPS Driver is added to support NMEA0183 complied GPS devices with RS-232 interface. Type: Serial. File updated: BwNode.mdb, GPS#.DLL and GPS.DLL.

 

Feature Enhanced: Multi-touch support. File updated: BwMultiTouch.dll, bwview.exe, bwwebv.exe, bwdraw.exe, bwwebd.exe, viewdlg.dll, webvdlg.dll, webvdlgu.dll drawdlg.dll, webddlg.dll, bwdatimg.dll.

 

7.2-2013.07.26

Problem Resolved: Increase email engine stability. File updated: bwblcmd.exe, bwblat.dll.

 

7.2-2013.07.01

Problem Resolved: The IE windows popped up ViewDAQ/View Client may fail to operate under certain conditions. File updated: bwrunmie.exe.

 

Candidate Release 7.1

Software Build          Feature or Fix Description

 

7.1-2013.04.01

Feature Enhanced: The pen width in GDI+ version of DrawDAQ/Draw Client has been enhanced to be compatible with GDI version of DrawDAQ/Draw Client. Since the rendering engine for GDI+ is different from the one for GDI version, the lines (straight or curve) with small pen width (for example, between 0 and 1) may disappear or become segmented when displaying in ViewDAQ/View Client if the pen color is not solid (alpha value of the color is not 255).

 

Feature Enhanced: The IP address in IPv6 format is now supported by Project node and SCADA node. For WASCADA node and TCP/IP communication drivers, IPv6 IP address is not yet supported.

 

Problem Resolved: Google Map Integration now works with the latest version of Google Map after rewriting JAVA Script to work around the incompatible issue introduced by the new Google Map server.

 

Problem Resolved: Miscellaneous ASP errors introduced in recent months have been fixed.

 

Feature Enhanced: WebAccess Express now supports devices compatible with Advantech DiagAnywhere.

 

 

Candidate Release 7.0

Software Build          Feature or Fix Description

 

7.0-2013.01.21

Feature Enhanced: WebAccess RTDB engine is introduced as an optional feature which requires a special licensed control file. With RTDB feature turned on, 200,000 tag records of sequential write per second and 300,000 tag records of sequential read per second can be achieved on a medium performance computer. Multiple data compression algorithms are utilized in RTDB to further reduce data storage size requirement. A straightforward API interface for RTDB is also provided for easy third-party integration. To test on this new feature, please backup and remove your control file (bwkserv.exe) from WebAccess\Node directory and install the latest packing of WebAccess Node. After installation and rebooting, turn on “Use RTDB For Data Log” option at Node Property page. Finally, download database and start node to start logging your data log using WebAccess RTDB. Please note that the control file installed with WebAccess Node installation is for demo purpose and only good for 2-hour continuous running.

 

7.0-2013.01.17

Feature Enhanced: IE 10 is now officially supported. All IE 10 incompatible issues known to us have been resolved.

 

Feature Enhanced: Add an option to ignore client CRC set for Modbus Serial Server. To enable this option, add ignore_CRC=1 under serial section of Moddef.ini.

 

Problem Resolved: Hardkey failure on SCADA node due to remote desktop access to the SCADA node.

 

Problem Resolved: Action log and alarm log to backup SCADA node many fail when there are many log requests in a short period of time.

 

Problem Resolved: Miscellaneous issues regarding ADAM devices for WebAccess Express.

 

7.0-2013.01.08

Feature Enhanced: Add a new driver – AdvDAinfo – to integrate devices compatible with Advantech DiagAnywhere.

 

Feature Enhanced: WebAccess Configuration now allows users to conveniently delete multiple tags at one time.

 

Feature Enhanced: Add “Swap Byte Text” data conversion code.

 

Feature Enhanced: Add “Scan Devices in Parallel” in TCPIP port configuration page. With this option set to “Yes”, communication code for TCPIP ports runs in separate threads for each device so a device won’t be blocked by other devices.

 

Problem Resolved: WebAccess Express captures mouse focus when auto-generating graph files.

 

Problem Resolved: WebAccess Express crashes when scanning ADAM2000 devices.

 

7.0-2013.01.02

Feature Enhanced: Add an optional setting in DrawDAQ/Draw Client for enhanced curve smoothness. The option is under Setting in DrawDAQ/Draw Client. Graph rendering speed will be reduced when the option is turned on. Therefore, it is advised to turn on the option only if you can see the desired improvement after turning it on.

 

Problem Resolved: Faceplate button on the toolbar of DrawDAQ/Draw Client failed to reflect the new faceplate insert feature enhanced in the release 7.0-2012.10.31.

 

Feature Enhanced: Improve the end point precision for Polyline, Bezier and Spline in DrawDAQ/Draw Client. The improvement didn’t apply to Arc due to the compatible issue. That means the end points of Arc may still have the one-pixel rounding error.

 

Problem Resolved: Download failed to work for Alarm Management System.

 

7.0-2012.12.10

Problem Resolved: Google Map Integration failed to work with the latest version of Google Map.

 

Problem Resolved: Modbus Server Configuration failed to use the correct code page to display 2-byte characters.

 

Problem Resolved: Miscellaneous updates for WebAccess Express.

 

7.0-2012.12.05

Problem Resolved: R-Text, L-Text and C-Text animations failed to work properly. The error was introduced in the release 7.0-2012.11.29.

 

Problem Resolved: The 16th period of Classroom Scheduler failed to work.

 

Problem Resolved: Required database tables failed to be created when data source is ORACLE.

 

Problem Resolved: Eventlog failed to work when data source is ORACLE.

 

7.0-2012.11.29

Feature Enhanced: Blinking animation objects in the same graph will now be blinking in synchronization.

 

Feature Enhanced: Allow users to define specific strings in graph display for BAD and NA tag points. This can be done by adding the following section into bwclient.ini as shown below.

 

[display]

bad=*

na=#

 

Feature Enhanced: Add DESELECT command for DrawDAQ/Draw Client. This will allow users to perform certain operations when creating CMD files for SESRUN. SESRUN is an unofficially supported feature which is suitable for advanced users only.

 

Feature Enhanced: WebAccess Configuration will now display optional features in dark cyan.

 

Feature Enhanced: Modbus Server Configuration is now added in WebAccess Configuration. The previously defined moddef.ini will be imported automatically.

 

Problem Resolved: DrawDAQ window may appear when using WebAccess Express to generate graph files automatically.

 

Problem Resolved: Large ICON used in Google Map Integration will now be scaled down proportionally.

 

Problem Resolved: Datacore may crash when SMS messages are generated from alarm management system.

 

7.0-2012.10.31

Feature Enhanced: Add an option at Node Property Page to specify whether to allow the same user to login simultaneously to a SCADA node from ViewDAQ/View Client on different computers. If disallowing the same user to login simultaneously to a SCADA node from different computers, it may take up to 2 minutes after logout for the same user to be able to login from a different computer again.

 

Feature Enhanced: Faceplate insert in DrawDAQ/Draw Client will now show block name list dialog box first. After selecting a block name, its associated faceplates will be listed in the faceplate list dialog box. For example, if “abc” is the associated block type for the selected block name, the faceplates like “abc.dfp”, “abc@1.dfp”, “abc@123.dfp”, “abc@anything.dfp”, etc. will be listed in the faceplate list dialog box.

 

Feature Enhanced: Allow certain tag fields to be used in calculation formula for Calculation Point. The tag fields supported are advdbv, advhi, advlo, almdbv, almhh, almhi, almll, almlo, almst, almva, aprdig, aprhdv, aprhh, aprhi, aprldv, aprll, aprlo, aprroc, outphi, outplo, qcode, spanhi, and spanlo.

 

Feature Enhanced: Allow users to specific “0” or “*” for Modbus server when communication is bad by defining an entry in moddef.ini as illustrated below.

 

1)    “0” when communication is bad. This is the default.

 

[mod_def]

enable_exception=0

 

2)   “*” when communication is bad.

 

[mod_def]

enable_exception=1

 

Feature Enhanced: Enhance Bacnet server to allow field changes to be updated to database.

 

Feature Enhanced: Enhance Bacnet server to support read/write for "UNITs" property 117, write for "Time_Delay" property 22, write for "Polarity" property 84 as signal reverse, write for "Inactive_Text" property 46 as discrete descriptor state 0, and write for "Active_Text" property 4 as discrete descriptor state 1.

 

Problem Resolved: Omron driver failed to handle the leading 0s in the PLC response packet.

 

Problem Resolved: Datacore crashed when array tag configured as data log point.

 

Problem Resolved: Datacore crashed when more than 5000 outstanding alarms in a project.

 

Problem Resolved: Miscellaneous errors in Google Map Integration.

 

Problem Resolved: Miscellaneous errors in ASP code for Configuration.

 

7.0-2012.09.13

Feature Enhanced: For GDI+ version of WebAccess only. In addition to 4:3 screen aspect ratio support, DrawDAQ and Draw Client now allow users to save graph files for 16:10 and 16:9 screen aspect ratios. The menu items for selecting different screen aspect ratios are under Setting menu item in DrawDAQ and Draw Client. A drawing area will be reduced accordingly to reflect the aspect ratio selected. When saving graph files using Entire Drawing option, only the content inside the reduced drawing area will be saved. This will ensure that the saved graph files will have a correct aspect ratio when displayed in full screen.

 

7.0-2012.09.12

Feature Enhanced: Google Map Integration. Please note that the internet access to the Google Map server should be available for this feature to work properly.

 

WebAccess now allows users to create map files that contain markers on Google Map. A marker contains Icons which can be displayed according to the value of a tag. A marker also contains title and up to three label/value combinations to be displayed as the marker information. And a left-click Marco can also be associated with a marker.

 

The map list dialog box can be accessed via Map menu item under Tools for map files already created and downloaded to be displayed in ViewDAQ or View Client.

 

Map List dialog box and map files can also be accessed using the following methods.

 

1)   <DIALOG>MAP -> bring up Map List dialog box.

2)   <GOTO>TOOL=your_map.map -> go to your_map.map directly.

3)   uti:gmap/gmap.asp?hwnd=%HWND&map=your_map& in video display -> display your_map.map inside a video display window in graph.

 

7.0-2012.06.29

Problem Resolved: Installation error may occur during WebAccess Express installation which is part of WebAccess Node installation process.

 

Problem Resolved: Web service for WebAccess mobile applications has been revised to fix various bugs.

 

Problem Resolved: Text value containing character ‘&’ cannot be displayed in Point Info dialog box for ViewDAQ/View Client.

 

Problem Resolved: The unknown time zone information on SCADA nodes may cause WebAccess to lose data in trend data synchronization.

 

Problem Resolved: The unknown time zone information on SCADA nodes may result in emails sent out by WebAccess with incorrect time stamps.

 

Problem Resolved: View Client failed to close a synchronization object properly. This will lead to a memory leak in View Client.

 

Feature Enhanced: User configurable send delay is supported for Watanabe RiAlLink driver.

 

Feature Enhanced: Disable array insert feature for ODBC data log to SQL server by default. To enable array insert feature, please add the following entry in bwodbcix.ini located in WebAccess\Node directory.

 

[bw_odbc_data]

array_insert=1

 

7.0-2012.06.02

Problem Resolved: Tooltip display may cause View Client to crash. This error was introduced in the 7.0-2012.05.21 release.

 

Problem Resolved: Slow update occurs after sending a write command in ADAM 4K driver with Modbus protocol.

 

Feature Enhanced: OPCUA driver is implemented for WebAccess to connect to thirty-party OPCUA servers.

 

Feature Enhanced: Two new functions are added in viewdll.dll for alarm summary tag list.

 

 

int VD_API VdGetAlarmTagNo();

 

int VD_API VdGetAlarmTaglist(char *tagbuf, int tagsize, int start, int num);

 

 

Two new corresponding methods are also added in COM object "Bwdllobj.DllObj". The following VB code segment demonstrates how to use these two methods.

 

 

Public Function VdGetAlarmTagNo()

 

Dim dllobj As Object

 

Set dllobj = CreateObject("Bwdllobj.DllObj")

 

VdGetAlarmTagNo = dllobj.GetAlarmTagNumber()

 

Set dllobj = Nothing

 

End Function

 

 

Public Function VdGetAlarmTaglist(start, num)

 

Dim dllobj As Object

 

Set dllobj = CreateObject("Bwdllobj.DllObj")

 

VdGetAlarmTaglist = dllobj.GetAlarmTagList(start, num)

 

Set dllobj = Nothing

 

End Function

 

7.0-2012.05.21

Problem Resolved: Tooltip display may cause Draw Client to refresh the entire drawing content resulting in an unpleasant visual experience. We only experienced this issue on Microsoft Windows XP.

 

Problem Resolved: Web services on the project node used by WebAccess Mobile failed to work. This error was introduced recently after we implemented Remote Access Code validation on RPC calls.

 

Feature Enhanced: A new video type, hikvision, is added to support video display and PTZ feature for Hikvision network camera/video server.

 

Problem Resolved: Database download cannot be completed in certain rare cases.

 

Problem Resolved: If system time is moved ahead by 200ms, “Time Event” in EVENT LOG may miss one record.

 

Problem Resolved: If two or more OPC client text points are configured, the tags after the second tag may not get correct value.

 

Problem Resolved: A LNS device that fails after the system runs over 49.7 days may cause the device never to recover.

 

Feature Enhanced: Add Protocol_Services_Supported and Object_List supports for BACnet server Device Object.

 

Feature Enhanced: Allow user to define minimum time gap and minimum cycle for all devices of GetState() issued for Lonworks Device in LON_MAP.INI. The syntax is as follows:

 

[DeviceStatusCheck]      

Min_Gap=500

Min_cycle_interval=300

 

If this is not defined, BwLNSApp.exe works as it did before.

 

Min_Gap (in milli-second) defines the minimum time between any two GetState() function calls, regardless how many devices and the sequence of the devices. This setting ensures only 1 GetState() can happen in defined time to prevent too many Lonworks traffic.

 

Min_cycle_interval (in second) defines the minimum time to complete check device state for ALL devices. Please make sure Min_Gap * total_devices < Min_Cycle_interval. Otherwise, only Min_Gap will be valid.

 

7.0-2012.03.29

Problem Resolved: Certain RPC calls between multiple SCADA nodes or redundant SCADA nodes failed to work when remote access code is set. We overlooked this issue in the 7.0-2012.03.18 release.

 

Problem Resolved: Scheduler and Classroom Scheduler cannot be accessed from within ViewDAQ and View Client. This error was introduced recently when we patched ASP security vulnerabilities.

 

Problem Resolved: The algorithm for Scheduler and Classroom Scheduler has been revised to handle large-scale scheduled tasks effectively.

 

Problem Resolved: WebAccess CE version has been updated to support Remote Access Code validation on RPC calls to WebAccess RPC servers. The updated WebAccess CE version is required to work with project node or SCADA nodes with remote access code.

 

7.0-2012.03.18

Problem Resolved:  We discovered that RPC calls to a built-in WebAccess RPC server using default port number 14592 have not been authenticated properly. With this security vulnerability, running SCADA nodes can be exploited by using reversely engineered exploit code. In the latest packing of WebAccess, we patch the vulnerability by implementing Remote Access Code validation on the built-in RPC server.

 

It is strongly recommended that our users upgrade their systems using the latest packing of WebAccess Node especially if the SCADA nodes are exposed to the Internet. If Remote Access Code has already been used previously, the reinstallation of WebAccess Node on SCADA nodes will patch the vulnerability automatically. If Remote Access Code has not been used, please enter Remote Access Code during the reinstallation of WebAccess Node on SCADA nodes.

 

Please note that the latest packing of WebAccess Client is needed if Remote Access Code is used. An incompatible WebAccess Client will be redirected to a web page on the project node to download and install the compatible WebAccess Client.

 

7.0-2012.03.08

Problem Resolved:  WebAccess has a feature that allows its View Client to connect to the SCADA Node directly without having to be redirected from the Project Node. To reflect the recent update for Remote Access Code validation on RPC calls, the URL link for this feature should be revised as follows:

 

http://your_scada_node_ip/broadweb/bwview.htm#proj=project_name&node=node_name&. . . .

&code=remote_access_code&codetype=1

&node2=backup_node_name&code2=backup_remote_access_code&codetype2=1

 

Note 1: The parameter code and codetype can be omitted if no remote access code is configured for node_name.

Note 2: The parameter code and codetype can be omitted if the remote access code for node_name has not been changed since the last successful connection to node_name.

Note 3: The parameter node2, code2 and codetype2 can be omitted if no backup node is configured or no remote access code is configured for backup_node_name.

Note 4: The parameter node2, code2 and codetype2 can be omitted if the remote access code for backup_node_name has not been changed since the last successful connection to backup_node_name.

 

7.0-2012.03.02

Problem Resolved:  A backdoor left open unintentionally to WebAccess RPC server using default port number 4592 has been discovered by our engineers and outside hackers. With this backdoor open, WebAccess Project and SCADA nodes can be easily exploited by using existing API functions shipped with WebAccess package or by using reversely engineered exploit code. Two separate reports claiming to have successfully exploited WebAccess RPC server have been evaluated and validated by our engineers. In the latest packing of WebAccess, we seal the backdoor by implementing Remote Access Code validation on WebAccess RPC server.

 

It is strongly recommended that our users upgrade their systems using the latest packing of WebAccess especially if their Project and SCADA nodes are exposed to the Internet. If Remote Access Code has already been used previously, the reinstallation of WebAccess Node on Project and SCADA nodes will seal the backdoor automatically. If Remote Access Code has not been used, please enter your own Remote Access Code during the reinstallation of WebAccess Node on Project and SCADA nodes.

 

Please note that the latest packing of WebAccess Client is needed if Remote Access Code is used. An incompatible WebAccess Client will be redirected to a web page to let you install the compatible WebAccess Client from the Project node.

 

Please also note that a new login page will appear before entering View client if Remote Access Code is used. Please enter operator’s username and password to proceed to View client.

 

7.0-2011.12.20

Feature Enhanced:  A beta version of WebAccess Express is packed as part of WebAccess Node installation package. The official release notes will be sent out separately when an official version of WebAccess Express is ready.

 

Feature Enhanced:  Log more error messages with time stamps into recover.log for debugging RPC communication issues.

 

Feature Enhanced:  A Mac address as the key to the control file is now supported on computers with multiple network cards.

 

Feature Enhanced:  Improve the performance of LOG to ODBC by sending compressed data via RPC and using array insert when the database is MSSQL or MySQL.

 

Feature Enhanced:  Array element access for configuration property is now supported for LNS driver.

 

Feature Enhanced:  Double word access is now supported for Festo driver.

 

Feature Enhanced:  BAS3000 device type is added to support Advantech BAS 3000 series.

 

Feature Enhanced:  Excel Out option is added for Shift Report, Daily Report and Monthly Report. If the option is turned on, the corresponding reports in the Excel file format will be generated automatically under project node’s WebAccess\Node\YourProject_YourNode\Report directory.

 

Problem Resolved:  Patch all known SQL injection and XSS issues.

 

Problem Resolved:  Resolve the issue that WebAccess Client may hang when connecting to SCADA node. This was introduced when we released 7.0-2011.08.27.

 

Problem Resolved:  Resolve the issue that Point Info dialog box in ViewDAQ/View Client may fail to display or the content of it may display incorrectly when there are user programs and/or Scripts running.

 

Problem Resolved:  Resolve the issue that View in Graph may fail to display when multiple instances of them appear in one graph.

 

Problem Resolved:  Resolve the issue that Video Display may display incorrectly when IE 9 is used.

 

Problem Resolved:  Resolve the issue that WebAccess Client may fail and IE window may close automatically when IE 9 is uses and especially when network connection is slow.

 

Problem Resolved:  Resolve the issue that RPC calls from WebAccess Client to SCADA node may fail in redundant SCADA systems.

 

Problem Resolved:  Resolve the issue that WebAccess Client stops responding for a long period of time when the network cable is disconnected in redundant SCADA systems.

 

Problem Resolved:  Resolve the issue that Datacore sometimes crashes when the network cable is disconnected and/or connected in redundant SCADA systems. The issue is worked around by catching the error and recovering datacore.

 

Problem Resolved:  Resolve the issue that user programs cease to function properly in various scenarios. As a result of this, from now on, VdBroadWinKrlFree() or dllobj.KrlFree must be always called regardless of the return value of VdBroadWinKrlInit() or dllobj.KrlInit().

 

Problem Resolved:  Fix Omron driver API interface issue.

 

Problem Resolved:  Fix SNMP driver data conversion issue.

 

Problem Resolved:  Fix ADAM4000 ASCII driver issue.

 

7.0-2011.08.27

Feature Enhanced:  Implement Reservation feature for Scheduler.

 

Feature Enhanced:  Add new SMS and email features for “SMS When Return To Normal”, “Email When ACK Alarm” and “SMS When ACK Alarm”.

 

Feature Enhanced:  Allow users to define maximum number of client computers that can connect to the SCADA simultaneously.

 

Feature Enhanced:  Improve GUI for tagname filter list for Action Log, Alarm Log, Analog Tag Log, Analog Change Log, Discrete Tag Log and Text Tag Log.

 

Feature Enhanced:  Enhance WebService on project node to support the latest version of WebAccess Mobile for iPhones and Android phones. For project node to support WebAccess Mobile, web service for IIS muse be enabled before installing WebAccess. To enable web service for IIS, please refer to release notes 7.0-2011.01.26.

 

Feature Enhanced:  Implement data compression in WAScada driver to improve performance.

 

Feature Enhanced:  Add WebOP device driver.

 

Feature Enhanced:  Add PwrMeter driver.

 

Problem Resolved:  Revise SCADA node and project node TIME synchronization procedure.

 

Problem Resolved:  Patch known buffer-overrun issues for webdobj.dll COM object and bwscript.dll COM object.

 

Problem Resolved:  Patch known security holes for bwocxrun.ocx.

 

Problem Resolved:  Resolve the issue that RPC call to RPC server in Datacore returns too early before actually finishing the call.

 

Problem Resolved:  Resolve device information display error in configuration.

 

Problem Resolved:  Resolve double-byte data processing error in WebAccess OPC server.

 

Problem Resolved:  Resolve Oracle and MySQL support issue.

 

Problem Resolved:  Resolve the issue that Webvrpcs.exe failed to be recovered when “Add Client” failed during connection to Webvrpcs.exe.

 

Problem Resolved:  Resolve the issue that “Add Client” failed during connection to Webvrpcs.exe. The error was introduced by the release 7.0-2011.05.23.

 

Problem Resolved:  Resolve the issue that User Management fails to work. The error was introduced by the release 7.0-2011.05.23.

 

Problem Resolved:  Resolve SETVAL and GETVAL error in Global Script. The error was introduced by the release 7.0-2011.05.23.

 

Problem Resolved:  Resolve hardkey reading error for SCADA-only installation. The error was introduced recently.

 

7.0-2011.05.23

Feature Enhanced:  WebAccess Mobile V1.2 has been released. It can be found on App Store. All iDevices with iOS3.2 or newer are supported.

 

To support WebAccess Mobile, please enable web services for IIS on the project node and then install the latest packing of WebAccess GDI+ version on the project node.

 

To enable web service for IIS, please refer to the following instructions outlined in the release note 7.0-2011.01.26.

 

7.0-2011.05.23

Feature Enhanced:  Setting value to a different tag for I/O tags is supported. For example, by appending /W=TagNameB to the end of point address field of TagnameA in configuration, any values set to TagnameA will be actually set to TagNameB.

 

Feature Enhanced:  Two new system tag parameters - SchdlrST and SchoolST - are added to define tags to enable/disable regular scheduler and school scheduler.

 

Feature Enhanced:  <ALMACKS>%FILTERED is implemented to acknowledge all alarm tags under the filtered criteria.

 

Feature Enhanced:  Alarm Summary display can be filtered by the criteria that user-level >= tag-level. This option can be turn on/off in node property page.

 

Feature Enhanced:  SMS when alarm return to normal is optional. This option can be turn on/off in node property page.

 

Feature Enhanced:  A new Reservation feature has been implemented for Classroom Scheduler.

 

Problem Resolved:  Resolve the issue that calling GetValueFromNode and SetValueToNode interfaces in webdobj object when Kernel is not running will cause these two interfaces to cease functioning even after Kernel is running again.

 

Problem Resolved:  Patch security holes regarding certain RPC calls and some asp files.

 

Problem Resolved:  Resolve the issue that Jscript and VBScript fail to run on Windows 7.

 

Problem Resolved:  Fix the bug that redundant comports may not work properly.

 

Problem Resolved:  The hard-key for project node and the hard-key for SCADA node can now work properly on the same computer.

 

Problem Resolved:  Resolve the issue that redundant comports may not work properly.

 

7.0-2011.01.26

Feature Enhanced:  WebAccess GDI+ to support our newly released native iPhone application for WebAccess Thin Client - WebAccess Mobile V1.0. WebAccess Mobile can be found on App Store. All iDevices with iOS3.2 or newer are supported.

 

To support WebAccess Mobile, please enable web services for IIS on the project node and then install the latest packing of WebAccess GDI+ version on the project node.

 

To enable web service for IIS, please refer to the following instructions:

 

1) For Windows XP or Windows Server 2003, make sure .NET 3.5 is installed. .NET 3.5 can be installed via Windows Update.

 

2) For Windows Vista, please modify IIS setting as follows and execute “Windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe –i" after modifying IIS.

 

Internet Information Services – ON

 

Web Management Tools – ON

IIS 6 Management Compatibility - ON

IIS 6 Management Console – OFF

IIS 6 Scripting Tools – OFF

IIS 6 WMI Compatibility – OFF

IIS Meta base and IIS 6 configuration compatibility – ON

IIS Management Console – ON

IIS Management Scripts and Tools – OFF

IIS Management Service - OFF

 

World Wide Web Services - ON

Application Development Features – ON

.NET Extensibility – ON

ASP – ON

ASP.NET – ON

CGI – ON

IASPI Extensions – ON

IASPI Filters – ON

Server Side Includes - ON

 

Common Http Features – ON

Default Document – ON

Directory Browsing – ON

Http Errors – ON

Http Redirection - ON

Static Content - ON

 

Health and Diagnostics – ON

Custom Logging – OFF

HTTP Logging – ON

Logging Tools – OFF

ODBC Logging – OFF

Request Monitoring – ON

Tracing - OFF

 

Performance Features – ON

Http Compression Dynamic – ON

Static Content Compression - On

 

Security - ON

Basic Authentication - OFF

Client Certificate Mapping Authentication - OFF

Digest Authentication - OFF

IIS Client Certificate Mapping Authentication - OFF

IP Security - OFF

Request Filtering - ON

URL Authorization - OFF

Windows Authentication (optional ON, usually OFF)

 

3) For Windows 7, please modify IIS setting as follows.

 

Internet Information Services – ON

 

Web Management Tools – ON

IIS 6 Management Compatibility - ON

IIS 6 Management Console – OFF

IIS 6 Scripting Tools – OFF

IIS 6 WMI Compatibility – OFF

IIS Meta base and IIS 6 configuration compatibility – ON

IIS Management Console – ON

IIS Management Scripts and Tools – OFF

IIS Management Service - OFF

 

World Wide Web Services - ON

Application Development Features – ON

.NET Extensibility – ON

ASP – ON

ASP.NET – ON

CGI – ON

IASPI Extensions – ON

IASPI Filters – ON

Server Side Includes - ON

 

Common Http Features – ON

Default Document – ON

Directory Browsing – ON

Http Errors – ON

Http Redirection - ON

Static Content - ON

 

Health and Diagnostics – ON

Custom Logging – OFF

HTTP Logging – ON

Logging Tools – OFF

ODBC Logging – OFF

Request Monitoring – ON

Tracing - OFF

 

Performance Features – ON

Http Compression Dynamic – ON

Static Content Compression - On

 

Security - ON

Basic Authentication - OFF

Client Certificate Mapping Authentication - OFF

Digest Authentication - OFF

IIS Client Certificate Mapping Authentication - OFF

IP Security - OFF

Request Filtering - ON

URL Authorization - OFF

Windows Authentication (optional ON, usually OFF)

 

Windows .NET Framework 3.5.1 - ON

Windows Communication Foundation HTTP Activation – ON

Windows Communication Foundation Non-HTTP Activation - ON

 

4) For Windows Server 2008, please modify IIS setting as follows.

 

Web Server –

 

Common http Features - ON

Static Content - ON

Default Document - ON

Directory Browsing - ON

Http Errors  - ON

Http Redirection - ON

 

Application Development Features

ASP.NET - ON                 

.NET Extensibility - ON

ASP - ON

CGI - ON

IASPI Extensions - ON

IASPI Filters - ON

Server Side Includes - ON

 

Health and Diagnostics

HTTP Logging - ON 

Logging Tools - OFF

Request Monitoring - ON

Tracing - OFF

Custom Logging - OFF

ODBC Logging - OFF

                 

Security - ON

Basic Authentication - OFF

Client Certificate Mapping Authentication - OFF

Digest Authentication - OFF

IIS Client Certificate Mapping Authentication - OFF

IP Security - OFF

Request Filtering - ON

URL Authorization - OFF

Windows Authentication (optional ON, usually OFF)

 

Performance Features – ON

Static Content Compression – ON

Dynamic Content Compression (optional ON, usually OFF)

 

Web Management Tools – ON

IIS Management Console – ON

IIS Management Scripts and Tools – OFF

IIS Management Service – OFF

 

IIS 6 Management Compatibility - ON

IIS Meta base compatibility – ON

IIS 6 WMI Compatibility – OFF

IIS 6 Scripting Tools – OFF

IIS 6 Management Console – ON

 

7.0-2011.01.11

Feature Enhanced:  Improve the performance of data transfer for WASCADA nodes.

 

Feature Enhanced:  Trending tooltip to display tag description is now optional in Node property page.

 

Feature Enhanced:  Security Area has been increased from 32 to 64.

 

Feature Enhanced:  A dropdown list will appear for digital tag change value interface in Thin Client.

 

Feature Enhanced:  Alarm Management System is implemented as an optional feature to allow users to define worker groups that will receive text messages and/or emails when specific tags in alarm groups in alarm.

 

Problem Resolved: 15-second limit was set unintentionally for all RPC calls when trying to fix network cable disconnected issue. This will cause download operation and some other slower RPC calls to return before actually finishing the call.

 

Problem Resolved: the inconsistent content for block tags appearing in tag list for various log display pages like Action Log, Alarm Log, Analog Tag Log, Analog Change Log, Discrete Tag Log and Text Tag Log.

 

7.0-2010.11.10

Feature Enhanced:  BEMS version1.1 (Building Energy Monitoring System) uses Microsoft Silverlight and .NET 3.5 installed on the Project Node.

 

Problem Resolved: SCADA node not restarting after download and restart command.  This happened with large tag counts; a timing issue, the command to restart occurred before the node had completely stopped.

 

7.0-2010.09.30

Problem Resolved:  After release 7.0-2010.08.17, the View Client may take up to extra 3 seconds to close. This seemed too long for most users. The code has been reviewed and modified to reduce the delay to a more acceptable level of 0.75 second.

 

Problem Resolved: The issue that the View Client stops responding when physical connection to SCADA Node is broken down as a result of network cable unplugged should have been resolved.

 

Feature Enhanced: As an ongoing integration process for our new Silverlight version of BEMS, WebAccess Node installation will automatically create a virtual directory named BEMS in IIS.

 

Feature Enhanced: Two methods are added in webdobj.webdraw object for users to get tag values from and set tag values to SCADA Node. Webdobj.webdraw is designed to work on the Project Node especially with IIS.

 

The prototypes for the two methods are:

 

STDMETHODIMP GetValueFromNode(BSTR ProjName, BSTR NodeName, BSTR TagList, long No, VARIANT *ret);

 

STDMETHODIMP SetValueToNode(BSTR ProjName, BSTR NodeName, BSTR TagList, long No, BSTR ValueList, long *ret);

 

A sample asp code segment is shown below to illustrate on how to use these two methods.

 

Dim tObj

set tObj = Server.CreateObject("webdobj.webdraw")

Dim  retval

' To Get Values From Node

retval = tObj.GetValueFromNode(“Your_Project_Name”, “Your_Node_Name”, “Tag1” + vbCrLf + “Tag2” + vbCrLf + “Tag3” + vbCrLf, 3)

if retval(0)> 0 then

  ' The values returned are in retval(1), retval(2), . . . for Tag1, Tag2, . . .

else

  ' Tag list has syntax error, Connection to SCADA node failed or Kernel is not running.

end if

' To Set Values To Node

retval = tObj.SetValueToNode(“Your_Project_Name”, “Your_Node_Name”, “Tag1” + vbCrLf + “Tag2” + vbCrLf + “Tag3” + vbCrLf, 3, “Vaule1” + vbCrLf + “Value2” + vbCrLf + “Value3” + vbCrLf)

if retval> 0 then

  ' The values have been set.

else

  ' TagList has syntax error, ValueList has syntax error, Connection to SCADA node failed or Kernel is not running.

end if

set tObj = nothing

 

7.0-2010.09.02

Feature Enhanced: BACnet MS/TP device driver via serial (RS485). Named BwBACnetM, this device driver supports communication via a serial connection (RS485) directly to the SCADA node PC allowing a direct connection to the BACnet MSTP serial network. This provides a second method of communications to BACnet MS/TP serial devices. Note that the BACnetJ driver also supports MS/TP communications via a BACnet TCPIP or Ethernet gateway to MSTP.

 

Problem resolved: Registry entries created by WebAccess were sometimes removed by some anti-virus applications.

 

Problem resolved:  False alarm information sometimes appeared in alarm summary.

 

Problem resolved:  The span high of COM x scan time, %ACOMSCANTM(x), has been increased from 60,000 msec to 600,000 msec to represent the correct scan time for slower devices.

 

7.0-2010.08.17

Feature Enhanced: Scheduled Reports. Although its period is still limited to a maximum of 24 hours, the Shift Report can now extend beyond midnight (for example, from 8 am today to 8 am the next day).

 

Problem Resolved: Modbus server has been updated to fix an error that occurred when reading tags with certain conversion type.

 

Feature Enhanced: A new video type, advantechnvs, is added to support Advantech NVS video server.

 

Problem Resolved: The issue regarding instances of IE 8, which are invoked usually by View in Graph, failing to be freed after use is resolved.

                             

7.0-2010.08.10

Problem Resolved: Blank data in Scheduled Reports in French Language version.

 

7.0-2010.07.16

Problem identified: Datacore will not stop. This prevents download from restarting. This occurs infrequently. Current solution is to return to previous version.

 

Problem identified: Simulation Mode (SIMU) does not enter simulation mode. Tags still attempt communication and are marked as bad *[fffff] or *[9000] or *[8000].  Fix will be in next build.

 

Problem Resolved: View may cause IE 8 to crash after viewing a graph file that contains View in Graph.

 

Feature Enhanced: Thin Client.  In addition to iPhone 2G, iPhone 3G, iPhone 3GS and iPhone 4, iPad and Android phones in general should work well now with our Thin Client. Please use the built-in browser on the supported mobile devices to connect to http://your_project_node, the page should be redirected automatically to the Thin Client on your project node.

 

Feature Enhanced: A Key Macro command can be sent from within View in Graph to its parent - a ViewDAQ/View containing the View in Graph. The syntax is:

Macro:      <SENDPTZ>=parent#your_macro_command

 

TCL:        SENDPTZ “=parent#your_macro_command”

 

VBScript:   SENDPTZ “=parent#your_macro_command”

 

JScript:    SENDPTZ(“=parent#your_macro_command”);

  

Feature Enhanced: SQL Commands in Scripts. In addition to FETCH NEXT which is previously supported, FETCH PREVIOUS, FETCH FIRST, FETCH LAST, FETCH ABSOLUTE n (starting from 1) and FETCH RELATIVE m (can be a negative number) are now supported for databases that support scrollable cursors. As a result of our internal testing, we can conclude that these fetch commands work fine on Microsoft SQL Server while failing on Microsoft Access.

 

A JScript sample is shown below to illustrate on how these commands can be used:

 

SQLDIRECT("CONNECT SESSION 2 TO bems,sa,zzcnjky");

SQLDIRECT("USE SESSION 2");

SQLDIRECT("DECLARE C1 CURSOR FOR Select [F_Value] from [T_EC_EnergyItemResult] where [F_EnergyItemCode]='01000' and [F_EndTime]<'2010-3-18 12:00:00' order by [F_EndTime]");

SQLDIRECT("OPEN C1");

SQLDIRECT("FETCH NEXT C1 INTO tag1");

SQLDIRECT("FETCH PREVIOUS C1 INTO tag2");

SQLDIRECT("FETCH FIRST C1 INTO tag3");

SQLDIRECT("FETCH LAST C1 INTO tag4");

SQLDIRECT("FETCH ABSOLUTE 5 C1 INTO tag5");

SQLDIRECT("FETCH RELATIVE -3 C1 INTO tag6");

SQLDIRECT("CLOSE C1");

SQLDIRECT("DISCONNECT SESSION 2");

 

7.0-2010.07.02

Problem Resolved: Datacore crashes immediately on start if Display Scan Tags are marked to DataLog or Log to ODBC. Starting with May 10 2010 build, if Display Scan Tags were marked to DataLog or Log to ODBC, they where forced to Constant Scan; however, not enough memory was allocated for the larger number of Constant Scan tags.  A change to BwDatImg.dll solved the problem.

 

Problem Resolved: Slow downloads occurring for a database with a large number of ODBC log tags.

 

Feature enhanced: Added a text-type system tag, DevActIP(comport, unit number). It shows the current active IP for a device. For a dynamically addressed remote SCADA node (i.e. WASCADA), a user can use this information to access the remote SCADA node. This is read-only tag

 

Feature Enhanced: Added a text system tag "SMS_Numb". This allows a user to change the SMS phone number (initially defined in SCADA Node Properties).

 

Problem Resolved: In a super SCADA node connecting to multiple remote SCADA nodes (WASCADA), in different time zones, with trend synchronization tags configured, a problem would occur the 1st day of each month, with  log data not recorded correctly.

 

7.0-2010.06.08

Problem Resolved: On certain computers with IE 8 installed, the entire content of Draw Client or View Client will flash itself about every one second. We are almost 100% sure this is caused by a bug in a COM interface provided by IE 8; we decided to work around the issue in case Microsoft never fixes it. To implement this update, please install the latest packing of WebAccess Client.

 

7.0-2010.05.10

Feature Enhanced:  For all device driver communications, a 20 ms delay is added after the first connection and before the first send to make sure the device is ready to receive data after the initial connection.

 

Feature Enhanced:  Event data uploading performance has been improved.

 

Feature Enhanced:  An accumulation point with a negative accumulated frequency ranged from -1 to -3600 seconds is now allowed to mimic a differential tag. The differential tag value will be evaluated every "-Accumulate frequency" seconds as the difference of the current source tag value and the last reset time source tag value). To use the following picture as an example, Meter Reading is the source tag with 1440 as Reset Minutes. The differential tag, Daily Usage, will be evaluated every 60 seconds as the current daily usage. To avoid the tag values being reset after restarting kernel, it is recommended to set "Keep Previous Value" to 1.

 

New tag fields:  .EXTAA0, .EXTAA1, .EXTAA2, .EXTAA3 and .EXTAA4, are added and defined as the analog type to represent Extra Value 0,  Extra Value 1, Extra Value 2, Extra Value 3 and Extra Value 4 of a tag. These tag fields are used to hold any user defined data. If “Online Change Tag Field to Database” is set to yes in SCADA Node properties, these values will be saved and reinitialized after a SCADA node restart or download.

 

Feature Enhanced:  %TDTRDSTM, which is read-only previously, can now be set to define datalog trend start time for each individual datalog trend group (defined by %TDTRDCGN).

 

7.0-2010.02.24

Problem Resolved: CPU utilization increased abnormally after View client exits.

 

Feature Enhanced:  New Allen-Bradley MicroLogix driver is added with device name ABMLGX.

 

Feature Enhanced: Siemens S7 TCPIP driver now supports two new parameters, T (Timer current value) and C (Counter current value). Two new conversion codes, Timer Value and Counter Value, are also added. Timer value converts the encoded value (10x, 1x, 0.1x, and 0.01 based) into the second base value and vice versa.

 

Feature Enhanced: Text array point value in WAScada driver is limited to first 100 elements to be transferred while analog and discrete array elements will be limited to 1000.

 

Feature Enhanced: The “Save and Download to SCADA Node” operation in Scheduler and Classroom Scheduler will be verified after data downloading. The status of download operation will be displayed accordingly.

 

Feature Enhanced: The changes for Log Data Maintenance will be taken into effect immediately after pressing the Submit button. Previously, database download, which causes datacore to restart, was required.

                            

Feature Enhanced: BEMS (Building Energy Management) data can be part of Log Data Maintenance tasks if the BEMS option is purchased. 

 

Problem Resolved: Tag Tooltip failed to display in Trend/XY Plot in the GDI+ version.

 

Feature Enhanced: Upload Remote Node feature, used with the WASCADA device is enhanced to include new upload options: All Tags or Only Tags with Alarms configured, Include Alarm Groups, Real Time Trends, Data Log Trends, Synchronize Alarms, Synchronize Alarm Groups, Synchronize Tag properties.

 

7.0-2009.11.16

Feature Enhanced: Toggle state (2) added to Scheduler for use with Block Writes and the system tag DEVBWT. Some device drivers, like Modbus, Mitsubishi, LNS and iLon support a block write. To enable a block write a system tag must be created for each device using the DEVBWT system parameter.  Normally the DEVBWT tag is set to 0 (zero) meaning no block writes.  When the DEVBWT is set to 1, writes to the device are suspended and the values written to the tags are queued in a buffer.  When the DEVBWT is reset to 0, the buffer is used to write a Block of data. The scheduler can support this by placing the DEVBWT tag at the start of an Equipment List, with it’s state picked as 2 (Toggle) and again as the last tag in the Equipment List and it’s state set as toggle.  This allows all the tags in the equipment list to be written using a blocks write.   Block writes are especially useful to structures, as found in LNS and iLON.

 

Feature Enhanced: New Gradient Fill feature for our GDI+ version by allowing users to choose two extra Custom Blend options and to define a center path for path gradient fill:

 

1)    Triangular-Shaped Blend – The blend follows a triangular shape with the extremes of the triangle's base at the gradient's boundaries. The default-blend starting color appears at the starting and ending boundaries of the gradient brush when a triangular-shaped blend is applied. The position of the ending color is somewhere between the boundaries and is determined by the value of Focus. In other words, the focus specifies the position of the peak of the triangle. As shown in the following picture, a focus value of 0.50 places the peak half way between the starting and ending boundaries. The ending color appears at this peak with a percentage of the gamut between the gradient's default-blend starting color and default-blend ending color defined by the value of Factor.

 

2)    Bell-Shaped Blend - The blend follows a bell-shaped curve with the extremes of the bell's base at the gradient's boundaries. The default-blend starting color appears at the starting and ending boundaries of the gradient brush when a bell-shaped blend is applied. The position of the ending color is somewhere between the boundaries and is determined by the value of the Focus. In other words, the focus specifies the position of the peak of the bell. As shown in the following picture, a focus value of 0.70 places the peak at 70 percent of the distance between the starting and ending boundaries. The ending color appears at this peak with a percentage of the gamut between the gradient's default-blend starting color and default-blend ending color defined by the value of Factor.

 

3)    Center Path for Path Gradient - By default, the center color of a path gradient is at the center point. The center color can appear along a path that surrounds the center point. That path is the boundary path scaled in the x direction by a factor defined by the value of X and in the y direction by a factor defined by the value of Y. The area inside the scaled path is filled with the center color. As shown in the following picture, a center path is defined by scaling the boundary path 0.20 in the x direction and 0.20 in the y direction.

 

Problem Resolved: Alarm email - if a '{' or '}' in the subject or content may stop email sending.

 

Problem Resolved: Data Log Trends:  A gap would appear at the last hour of the month to the first hour of next month in minute or hourly datalog trend if the value stayed unchanged for a while.

 

7-2009.10.13

Feature Enhanced: GDI+ (pronounced Gee Dee Eye Plus) is an enhanced Graphical Device Interface allowing transparency, unlimited color palette, 1 million objects can be grouped into a single object and other enhancements.  Old graphics will be compatible with new GDI+ clients and GDI+ Draw.  However, GDI+ graphics will not be viewable in older clients or previous versions of DRAW. GDI+ is a separate installation.  It is very much still a “Candidate Release” and not officially released.  There are now two Candidate Releases, one labeled GDI+.  This is stage 1 of the GDI+, more enhancements are expected over the coming month.

 

Feature Enhanced:  A Batch Write feature is added to the LNS, iLon100 and iLONSS drivers. For multiple writes to the same NV in different part of a structured data, WebAccess issues only one write command with all the changes to avoid timing problem.

 

Feature Enhanced: A TCP/IP interface is added to the Mitsubishi FX3 PLC driver.

 

Problem Resolved: BEMS licensing in Windows Vista.

 

Problem Resolved: Alarm summary may lose a few seconds after set a new value to a tag field if "Online Change Tag Field To Database" enabled.

 

7.0-2009.08.14

Problem Resolved: Data Log Trend errors have been fixed.

 

7.0-2009.08.13

Feature Enhanced:  Trend synchronization between WASCADA nodes and the Super SCADA. The Local time stamps of the WAScada nodes will be used to plot Trend data on the Super SCADA.

 

Feature Enhanced: Alarm Log synchronization between WASCADA nodes and the Super SCADA. Contents in the local languages of WAScada nodes will be converted to the language used on the Super SCADA.

 

Problem Resolved:  BwPData.mdb will disappear if the compacting procedure (to reduce the file size of BwPData.mdb) fails for an unknown reason during Log Data Maintenance.

 

Problem Resolved: Certain operations in System Log, Action Log, Alarm Log, Analog Tag Log, Analog Change Log, Discrete Tag Log, Text Tag Log and Event Log may fail due to our previous attempt at preventing SQL Injection attacks.

 

Problem Resolved:  Import SCADA Node feature will fail and the asp page will stop responding when importing SCADA node from other project nodes with older versions of the BwCfg.mdb. This error was introduced after release 6.0-2009.05.27 when we introduced the Classroom Scheduler.

 

Problem Resolved: a memory leak in OPC client has been fixed.

 

7.0-2009.08.03

Problem resolved: Memory Leak in webvrpcs.exe (The WebAccess Network Service). The problem was caused by adding hardkey checking for BEMS option in late June 2009. All the versions between 6/29 and 7/31 may have this problem. A new file named BwPAlarm.dll can be replaced with the latest version to fix this problem in earlier versions. Or, reinstall using this or later version.

 

7.0-2009.07.21

Feature Enhanced: User-defined DLL compatible with VIEW/ViewDAQ.  It was first released in version 6.0-2009.1.06 and 6.0-2009.2.3. To further enhance this feature, there are two new function calls for users to efficiently get and set multiple tag values. They are:

 

void VC_API VcViewMultipleGetValue(char *taglist, int size_tag, char *valuelist, int size_value, int no);

 

void VC_API VcViewMultipleSetValue(char *taglist, int size_tag, char *valuelist, int size_value, int no);

  

To have this enhancement, please install the latest packing of WebAccess Node on SCADA nodes and WebAccess Client on client computers. The updated version of viewcall.h and viewcall.lib for these functions are located in WebAccess\Node directory.

 

The following sample codes demonstrate how these two function calls can be used.

  

 

// Get values of Tag1 and Tag2 ----------------------------------------------------------------------------------------------------

    char * pt_tag = (char *)calloc(32, 2);

    char * pt_val = (char *)calloc(80, 2);

 

    strcpy(pt_tag, "Tag1");

    strcpy(pt_tag+32, "Tag2");

 

    VcViewMultipleGetValue(pt_tag, 32, pt_val, 80, 2); // The values of Tag1 and Tag2 are in pt_val and pt_val+80, respectively.

 

    free(pt_tag);

    free(pt_val);

 

 

// Set values of Tag1 and Tag2 ----------------------------------------------------------------------------------------------------

    char * pt_tag = (char *)calloc(32, 2);

    char * pt_val = (char *)calloc(80, 2);

 

    strcpy(pt_tag, "Tag1");

    strcpy(pt_tag+32, "Tag2");

 

    strcpy(pt_val, "123.00");

    strcpy(pt_val+80, "456.00");

 

    VcViewMultipleSetValue(pt_tag, 32, pt_val, 80, 2);

 

    free(pt_tag);

    free(pt_val);

 

 

7.0-2009.06.29

Problem Resolved: Redundant SCADA Nodes, the Backup Node ViewDAQ did not consistently show the value of Tags from the Primary SCADA Node.

 

 

Candidate Release 6.0

Software Build          Feature or Fix Description

 

6.0-2009.06.09

Feature Enhanced: A Tag field named .NODEVA – to complete the enhancement as described in the earlier email. By using .NODEVA, users can set temporary value for a tag that can be shared among different ViewDAQs on a SCADA node or different View clients on a Client node. For example, users now can use this feature to easily pass parameters to another ViewDAQ/View Client that is called up by DSPPOPUP/DSPPOPUPDEP/DSPPOPUPTOP.

 

6.0-2009.06.08

Feature Enhanced: A Tag field named .VIEWVA.  It allows users to set a temporary value to a tag which is valid as long as the current ViewDAQ/View client stays running.

 

An existing tag field, .TEMPVA, can be used for the similar purpose. The difference between .TEMPVA and .VIEWVA is the scope of the temporary value. The temporary value set using .TEMPVA is only valid inside a graphic. Leaving the graphic, the temporary value will be reset to the corresponding tag value when first referred in another graphic page. Please note that when leaving and then reentering the graphic, the temporary value will still be reset as the corresponding tag value.

 

In contrast to .TEMPVA, the temporary value set using .VIEWVA is valid across all graphic pages in the same ViewDAQ/View client. The use of .VIEWVA can allow users to pass some parameters between different graph pages in the same ViewDAQ/View client without interfering with other ViewDAQ/View client.

 

6.0-2009.06.03

Problem Resolved: A COM object, updated recently in the release version of 2009.05.27, may cause the IIS Worker Process to stop working when users are using WebAccess Configuration. We have resolved the issue.

 

6.0-2009.05.27

Feature Enhanced: Classroom Scheduler.  Similar to the Scheduler, but the time periods mimic class periods in a School or University.  Up to 16 class periods per day, repeating up to 7 days a week. The user interface is really all that changes.

 

Problem Resolved: Users with Level 15 assigned to any Area cannot log in to VIEW, and the Tags with their security level assigned as 15 will not behave as expected in terms of Area/Level security. Level 14 is okay, Level 16 is okay. A database download has to be performed after installation completes and the computer reboots.

 

Feature Enhanced: WebAccess OPC server (BwOPCServer.exe) now will be connected on request any time regardless whether Datacore.exe is running or not. If Datacore.exe is not running, WebAccess OPC server will be still connected but all the values for the valid tags will be returned as bad values.

 

Problem Resolved: Display high/low of trend displays may not be downloaded to SCADA nodes or display high/low of trend displays may not be able to be saved back to configuration database. The error was introduced recently due to the inconsistence between our database migration programs. Please install the latest packing of WebAccess Node on Project/SCADA nodes and WebAccess Client on Client computers.

 

Feature Enhanced:< SAVEGROUP>REALTRD and <SAVEGROUP>DLOGTRD are added as MACRO commands for users to save Realtime Trend group settings and Datalog Trend group settings inside and outside of Trend Displays, respectively. Previously, < shift_F4> can be used for this purpose but only inside Trend Displays.

 

6.0-2009.05.14

Problem Resolved: Action Log to Printer from View client now works as designed if Action Log to Printer is enabled in Node property page of WebAccess Configuration. We implemented this feature from day one of WebAccess, but it never worked as designed.

 

Feature Enhanced:  ActionScript 3.0 in Flash is now supported. There are many incompatible issues between ActionScript 2.0 and 3.0. When setting values to variables of AcrionScript 3.0 in Flash with flashvars=your_flash_variable... from within ViewDAQ/View client or fscommand(“GETVAL”, “your_flash_variable=your_webaccess_tag”);, root.loaderInfo.parameters. your_flash_variable must be used to retrieve the values in ActionScript 3.0. The following sample script written in ActionScript 3.0 illustrates how this can be done.


function WaitGetValue():void {

fscommand("GETVAL","pv=%ANUMRAND");
pv=root.loaderInfo.parameters.pv; // This statement is not required and not allowed when using ActionScript 2.0;
if (pv != pv_old) {
pv_old = pv;
tbox.text=pv;
}
}
var sid;
var pv;
var pv_old;
pv = "";
pv_old = pv;
tbox.text=pv;
sid  = setInterval(WaitGetValue, 500);

 

6.0-2009.04.27

Feature Enhanced: Alarm Email Notification of Return to Normal. A new option is added to the SCADA Nodes properties: “Email When Return to Normal”.  It is optional to enable sending email when the alarm tag has been acknowledged and its value has returned to normal. The default is No.  SMTP Server, Email Account, Password, Email Address, and Email From must be enabled in SCADA node properties. Alarm Email must be enabled for the Tag.

 

Feature Enhanced: New Daq Tag: %TALMTRIGGER. In the release of 6.0-2009.04.02, we implemented a new feature for users to define alarm triggered scripts. We now further enhance the feature by adding a DaqTag named %TALMTRIGGER. This allows users retrieve the tag name that triggered the alarm script. %TALMTRIGGER is valid only in the script that is triggered by alarm. Otherwise, it will return an empty string.

 

6.0-2009.04.12

Feature Enhanced: Scheduler and PLC Scheduler Keymacros in VIEW and ViewDAQ.

Previously, users can only go to various pages in scheduler or plc scheduler page for current SCADA node via UTI interfaces. That is only p=xxx is available for previous versions of WebAccess. Now we provide more options for their corresponding UTI interfaces:

 

1)  For scheduler:

 

<GOTO>TOOL=BWSCH.UTI^p=xxx^sort=s1^sort2=s2^GpNo=no^node=NodeName

uti:scheduler/schedulerView.asp?p=xxx&sort=s1&sort2=s2&GpNo=no&node=NodeName&

 

xxx = 1 -> Holiday, sort2 parameter is ignored, GpNo is hgNo (Holiday Group Number).

xxx = 2 -> Time, GpNo is tgNo (Time Group Number).

xxx = 3 -> Equipment, GpNo is egNo (Equipment Group Number).

xxx = 4 -> Circuit Group, GpNo is ecgNo (Circuit Group Number).

 

If p=xxx is not specified, Time is the default page.

 

s1 is the first sorting option, 0 -> sorted by group number, 1 -> sorted by group name.

s2 is the second sorting option, 0 -> sorted by group number, 1 -> sorted by group name.

 

If sort=s1 or sort2=s2 is not specified, group number will be the sorting criterion.

 

no is group number.

 

If GpNo=no is not specified, the first available group number will be displayed.

 

NodeName is the node name that the UTI page is associated with. The node must belong to the current project.

 

If node=NodeName is not specified, the current node is used.

 

2)  For plc scheduler:

 

<GOTO>TOOL=BWSCHPLC.UTI^p=xxx^sort=s1^sort2=s2^GpNo=no^node=NodeName

uti:ba/baView.asp?p=xxx&sort=s1&sort2=s2&GpNo=no&node=NodeName&

 

xxx = 1 -> Holiday, sort2 parameter is ignored, GpNo is hgNo (Holiday Group Number).

xxx = 2 -> Time, GpNo is tgNo (Time Group Number).

xxx = 3 -> Equipment, GpNo is egNo (Equipment Group Number).

xxx = 4 -> Circuit Group, GpNo is ecgNo (Circuit Group Number).

xxx = 5 -> CPU Number, sort, sort2 and GpNo are ignored.

 

If p=xxx is not specified, Time is the default page.

 

s1 is the first sorting option, 0 -> sorted by group number, 1 -> sorted by group name.

s2 is the second sorting option, 0 -> sorted by group number, 1 -> sorted by group name.

 

If sort=s1 or sort2=s2 is not specified, group number will be the sorting criterion.

 

no is group number.

 

If GpNo=no is not specified, the first available group number will be displayed.

 

NodeName is the node name that the UTI page is associated with. The node must belong to the current project.

 

If node=NodeName is not specified, the current node is used.

 

6.0-2009.04.09

Feature Enhanced: Alarm Filter Command for Scripts and Keymacros. A new command, ALMFILTER, is added to serve as an alternative way for users to set various filters for Alarm Summary Display in a single command line format. This command can be used inside or outside of Alarm Summary Display.
Keymacro: <ALMFILTER>lock^normal^p^bfffffffffffffffffffffffe
TCL Script: ALMFILTER lock^normal^p^bfffffffffffffffffffffffe
VBScript: ALMFILTER “lock^normal^p^bfffffffffffffffffffffffe”
Jscript: ALMFILTER(“lock^normal^p^bfffffffffffffffffffffffe”);
These commands will set filters that are equivalent to those in the Alarm Summary Disable Options dialog box.

 

Feature Enhanced: <DIALOG>ALMSUMONOFF can now be safely used outside of Alarm Summary Display for users to set various filters for Alarm Summary Display interactively. Previously, this command could only be used inside of Alarm Summary Display and sometimes caused ViewDAQ/View to behave erratically if used outside of Alarm Summary Display.

 

6.0-2009.04.02

Feature Enhanced: Alarm triggered Scripts.  To define script files to be run once when tags in alarm state, the script file name is added to Media File field of in the Alarm section of the Tag property page. Please use the pipe symbol “|” (Shift-\) to separate media files and/or script files.  If there is no media file or a single script, then just enter the script file name (include the file extension, .scr, .js, .vbs, .jse, .vbe). Script files in TCL, JScript, VBScript, JScript encoded, and VBScript encoded formats are all supported.

 

To run a script as a local screen script, pre-append the file name with local!.  For example, local! mediascript.vbs

The local script file, mediascript.vbs, will also be run once as a local script inside the first available ViewDAQ, if any, on the SCADA node and inside the first available View client on each computer connecting to the SCADA node. If the local! option is not specified , the script file will be run once as a global script inside the global script engine on the SCADA node when tag is in the alarm state the script is associated with.

 

Please note that the script will block execution flow of ViewDAQ/View client or global script engine. Therefore, please make sure the scripts exit as soon as possible.

 

Feature Enhanced: View Client to connect to a SCADA node that is running on a different language version of WebAccess Node. Fonts available are usually different on the SCADA node and the client computer when they are running on different versions of Windows. Therefore, the font display is out of our control and may not be perfect. Moreover, we are not sure all of character sets available on the SCADA node can be used as file paths or file names. This may cause an issue when we have to use the native character sets of the SCADA node to create paths or files on the client computer. Finally, scripts are run locally and may present some potential issues especially they are designed to run on the language environment available for the SCADA node.

 

Although we spent more than two months to make this feature available, we are not sure the feature will work for all scenarios. Therefore, this will be an unofficially supported feature.

 

6.0-2009.4.01

Feature Enhanced: Alarm Lock for Alarm Summary.  A special status can be assigned to a Tag in Alarm that will mark the Tag for filtering in the Alarm Summary page (to view all Locked Alarms Only or Hide All Locked Alarms).  Tags can also be sorted to show Locked Alarms at the top of the Alarm Summary List. There will be a white rectangle prefixed to every locked alarming tag in the new default Alarm Summary display. The lock status of an alarming tag will be automatically cleared when the tag is not in alarm (Return to Normal) or in a new alarm status (i.e. change from High Alarm to a High-High Alarm). A button labeled Lock is added to the alarm summary that allows user to select an alarm and then lock it.  A checkbox labeled Lock is also added to the Alarm Summary to allow alarms to be arranged by Locked Alarms first.  Two checkboxes labeled Locked and Unlocked are added to the Alarm Filter Dialog Box to hide Locked or to hide Unlocked alarms from the Alarm summary.

 

Feature Enhanced: Alarm Range Filter for Alarm Summary. Another special status will be assigned to a tag in alarm when its value has returned to normal that is Unacknowledged (without an ACK) and if “Ack Alarm by Return to Normal” is set to NO in SCADA Node property page. The alarming tags can be sorted or filtered based on the Range status in Alarm Summary display. The green color will be used to display this type of alarming tags in the new default Alarm Summary display. (Return-to-Normal Unacknowledged alarms show in a Green Color in the new default Alarm Summary Page). A checkbox labeled Range is also added to the Alarm Summary to allow alarms to be arranged by Return-to-Normal Alarms first. Two checkboxes labeled Value in Normal Range and Value in Alarm Range are added to the Alarm Filter Dialog Box to hide Return-to-Normal Alarms or to hide Active Alarms from the Alarm summary.

 

Feature Enhanced: The lock and range features are also implemented in the new default Alarm Group display. There will be a white rectangle prefixed to every locked alarming tag. Return-to-Normal Unacknowledged alarms show in a Green Color.

 

Feature Enhanced: A new tag field “.ALMLK” is added to be used with the lock status of a tag. The Change Value dialog box can be used to lock or unlock the tag.

 

Feature Enhanced: A new tag field “.ALMEST” is also added to be used to show a new combined alarm/lock status of a tag. The field value will be 0 if no alarm, 1 if unack alarm, 2 if ack alarm, 3 if back to normal without ack, 5 if unack alarm and locked, 6 if ack alarm and locked, 7 if back to normal without ack and locked. The following figure shows that the tag, 25_AHU1_FANS_S, is locked and its value has returned to normal without ACK.

 

Please note that the new default almsum.dxx/bxx and almgrp.dxx/bxx will be in config\system\drw and bgr directories. In order to use these new features for existing projects, users have to use these new files to manually replace existing almsum.dxx/bxx an almgrp.dxx/bxx in your project_node directories or modify them accordingly.  The old Alarm Summary Display is compatible with the new, it just will not show the Lock and Range buttons, colors or markers.

 

6.0-2009.3.29

Problem Resolved: Very Long Tagnames in Dynamic Animation of Block Detail Displays. WebAccess allows users to use both parameters and regular tags as tag names in block detail graphic. However, when very long tag names (including tag fields) are used as an Animation Tag or an Attribute Tag inside block detail pages, ViewDAQ/View Client may crash.

 

Feature Enhanced: Print Log in Alarm Log and Action Log will now output in HTML format and use IE web browser to display the output. We use the similar format for trending data export in Realtime Trend and Datalog Trend. Previously, the output was in text to Notepad.

 

6.0-2009.3.24

Feature Enhanced: Support for Internet Explorer 8 (IE8).  It requires users to reinstall Project Node, SCADA node and View Client plug-ins.  Old IE7 plug-in is compatible with new Project Node software.

 

Due to compatibility issues between IE 8 and IE 7, we have modified components of WebAccess in order to work with new IE 8 while keeping WebAccess compatible with IE 7 and earlier. The notable issue is that previous versions Draw/View Clients and BEMS chart displays will not work with IE 8 (typically they display as almost completely black). Besides modifying our asp and C++ codes, we automatically add "X-UA-Compatible: IE=EmulateIE7" as a custom HTTP header of Default Web Site on project node. (Found in Default Web Site properties of IIS Manager).  This may not be necessary for our asp code to run properly. Therefore, we may remove this customer header from Default Web Site on project node in later packing of WebAccess after we feel comfortable with IE 8.

 

Feature Enhanced:  GOTO LOGINPAGE.  This allows users to log out to a login page of View client by using the following macro and script commands. The syntax is:

 

Macro:      < GOTO>LOGINPAGE

 

Tcl Script:  GOTODAQ LOGINPAGE

 

VB Script:    GOTODAQ “LOGINPAGE”

 

JScript:    GOTODAQ(“LOGINPAGE”);

 

When the commands are carried out, all View clients, on the same computer, will log out, reconnect to the SCADA node and then display the login page. When logging in again, all View clients will return to their previously displayed graphic before logging out. However, if the new user does not have access to the previous display, the welcome page will be displayed.

These commands are ignored by ViewDAQ.

 

Feature Enhanced: Download User defined files to VIEW clients.   Users can predefine files to be downloaded to client computers from a SCADA node when View clients connect to the SCADA node by adding a "download" section into bwserver.ini on the SCADA node. This feature may be useful when users implement their own flash objects or user-defined DLL with VIEW/ViewDAQ and extra data files are needed by the flash or DLL on Client computers.  The location of these files should be a subdirectory of WebAccess\Node.

 

Using the "download" section listed below as an example, all files in WebAccess\Node\test directory on the SCADA node will be downloaded to WebAccess\Client\testc directory on the client computer and all files with extension ".dat" in WebAccess\Node\YourProject_YourNode\test1 directory will be downloaded to WebAccess\Client\YourProject_YourNode\testc2 directory. The directories specified for Client computers will be created automatically if they do not exist.

 

[download]

 

no=2

source_1=..\test

destination_1=..\testc

fileext_1=*.*

 

source_2=test1

destination_2=testc2

fileext_2=*.dat

 

6.0-2009.3.10

Problem Resolved: Alarm Email. If the tagname contains a dash or minus sign, the alarm email subject may include only part of the tag name.

 

6.0-2009.2.18

Problem Resolved: The bwNode.mdb file in the 2009.02.10 build could not be opened in some versions of Windows (usually Windows XP Pro and Server 2003).  The result was an error when trying to add or edit a tag or comport.

 

6.0-2009.2.10

Feature Enhanced: Email of Alarms subject now includes Tag Name, Tag Description, Alarm Type, and Value.
For example: ResLvl1 Reservoir 1 Level High Alarm (4.3)

 

Problems Resolved: The WAScada driver, if users changed the .INITVA tag field with the synchronized option chosen (write Online Change Tag Field To Database, bwCFG.mdb), it sometimes caused a driver error.

 

6.0-2009.2.3

Feature Enhanced: User-defined DLL compatible with VIEW/ViewDAQ. We implemented an enhancement for users to create their own user-defined DLL compatible with VIEW/ViewDAQ in the release version 6.0-2009.1.06. To further enhance this feature, we added four new functions for users to create their URL displays inside dialog boxes in the user-defined DLL. They are:

 

void VC_API VcCreateWebBrowser(HWND hWndParent, RECT Rect, const char *UrlString);

void VC_API VcUpdateWebBrowser(const char *UrlString);

void VC_API VcResizeWebBrowser(RECT Rect);

void VC_API VcDeleteWebBrowser();

 

where UrlString can be any ordinary URLs or in the format of UTI:/DAQ:/VDO: syntax. Please note that only one URL display is allowed in a dialog box. Please also make sure that the dialog box has the WS_CLIPCHILDREN attribute to avoid redrawing issues.

 

A sample MyDLL project exists to demonstrate how to use these APIs is available from Broadwin’s Milpitas office. To test MyDLL.dll, please copy MyDLL.dll to WebAccess\Node directory and use MyDLL.bgr the call up the sample dialog box.

 

6.0-2009.1.14

Feature Enhanced: Multiple state alarm handling is implemented for discrete tags. Each state of a tag can be assigned as an alarm with each state having a unique alarm priority, delay time, wav file, media file.  Each state can be assigned individually the ability to send email notification and text-to-speech alarm annunciation (although the same message is sent or read).

 

Feature Enhanced: Tag fields added for discrete tags’ multiple delay times. Tag fields for each state’s alarm delay time are added. They are DELAY0, DELAY1, …, DELAY7. The maximum value for each alarm delay time is 6,000,000 milliseconds.

 

Feature Enhanced: Analog Tag alarms “To Normal Delay Time” has been separated from Alarm Delay Time field. The maximum value for analog alarm delay time (DELAYA) is also increased from 600,000 milliseconds to 6,000,000 milliseconds.

 

Feature Enhanced: Five additional tag fields to store double values and five additional tag fields to store text values for tags have been added. Users can use these of any purpose. They are EXTVA0, EXTVA1, EXTVA2, … EXTVA4 and EXTVT0, EXTVT1, EXTVT2, … EXTVT4 respectively. Text fields are 70 characters max.

 

Feature Enhanced: Database table and ASP code have been redesigned to handle Alarm Group data up to 250 tags for each group regardless of the length of each tag in the group.

 

Feature Enhanced: Remote Copy. View clients now allow users to copy files form SCADA nodes to client computers. Only can files in the directory of WebAccess\Node or its subdir4ectories be copied from SCADA nodes to the directory of WebAccess\Client or  under on client computers. The syntax is as follows:

 

For Macro:              < REMOTECOPY>YourFileName

For TCL script:         REMOTECOPY YourFileName

For VBScript:           REMOTECOPY "YourFileName"

For JScript:            REMOTECOPY("YourFileName");

 

 

For example, to copy file ABC.DAT form WebAccess\Node of SCADA node to WebAccess\Client of client computer, please use <REMOTECOPY>..\ABC.DAT,

 

to copy file ABC.DAT form WebAccess\Node\CurrentProjectNode of SCADA node to WebAccess\Client\CurrentProjectNode of client computer, please use < REMOTECOPY>ABC.DAT.

 

Please note that BwCfg.mdb requires a new schema to implement these changes. The BwCfg.mdb will be automatically converted after installation completes and the project node computer reboots. If an unconverted BwCfg.mdb is copied into WebAccess\Node\config directory later, the conversion process will not be carried out.  To force the conversion, please restart webvrpcs.exe or reboot the project node computer.

 

6.0-2009.1.06

Feature Enhanced: User-defined DLL compatible with VIEW/ViewDAQ. We implemented an enhancement for users to call  a user-defined function located inside a DLL from within ViewDAQ/View Client. The user-defined function can be a customized dialog box. The syntax is:

<DLLEXEC>MyFunction^data@MyDLL.dll.

 

MyFunction residing in MyDLL.dll must have the prototype as follows:

 

 

#ifdef MYDLL_EXPORTS

#define MY_API __declspec(dllexport)

#else

#define MY_API __declspec(dllimport)

#endif

#ifdef __cplusplus

extern "C" {

#endif  /* __cplusplus */

void MY_API MyFunction(HWND hWnd_main, const char *data);

#ifdef __cplusplus

}

#endif

 

Please note that the execution flow of ViewDAQ/View Client will be blocked. Therefore, we also provide a function -- VcViewTimerCallback()-- to be used with MyFunction to prevent from blocking the execution flow.  Users must implement a 25 msec timer to call this function and take actions according the return value. The following is an example of how this can be done.

 

void CMyFunction::OnTimer(UINT nIdEvent)

{

    If (nIdEvent == FG_UPDATE_TIMER) {

          LRESULT dlgState = VcViewTimerCallback();

          if (dlgState == DAQDLG_QUIT)

                OnCancel();

          else if (dlgState == DAQDLG_HIDE) {

                ShowWindow(SW_HIDE);

           }                      

          else if (dlgState == DAQDLG_SHOW) {

                ShowWindow(SW_SHOWNA);

           }

    }

}

  

We also provide three more functions for users to GetValue from, SetValue to, and SendCmd to ViewDAQ/View client that invokes MyFunction: They are:

 

char VC_API * VcViewGetValue(LPCTSTR Tag);

void VC_API VcViewSetValue(LPCTSTR Tag, LPCTSTR Value);

void VC_API VcViewSendCmd(LPCTSTR Cmd);

 

 

The required header file and library file for these functions are located in WebAccess/node directory. Please note that MyDLL.dll must be put in WebAccess/node directory. When calling up MyFunction from with View client, MyDLL.dll will be automatically downloaded from the SCADA node to client computers.

 

6.0-2008.12.30

Feature Enhanced: Draw animation objects: The maximum number of animation objects has been increased from 2000 to 4000.

 

Feature Enhanced:  BwOpcServer.ini. is no longer needed when the SCADA node acts as an OPC server.

 

Problem Resolved: OPC driver failed to connect to OPC 2.0 and 3.0 servers. The error was introduced when we increased the com port number from 12 to 60.

 

Problem Resolved:  Some minor errors related to WebAccess Configuration have been fixed.

  

Feature Enhanced: Dynamic IP Addresses for polled devices. Now WebAccess can poll devices, including WebAccess SCADA nodes, with dynamic IP address. As long as the devices can send "Where I am" message according to the following format. WebAccess SCADA node will search the device name in the message against the device name in WebAccess device configuration, if the names match, WebAccess uses the new IP from the message to poll the device. In order to support this feature, users need to configure WebAccess SCADA node Modbus listening port to take "Where I am" message. This Modbus listening port is the same port if the SCADA node also servers as a device polled by another SCADA node. For WebAccess with dynamic IP acting as a device to be polled by another SCADA node, a user needs to configure the IP, port and frequency to send "Where I Am" Message. If NAT or port mapping is used in the router, users need to set it correctly to make this feature works.

  

The device sends its ID using Modbus TCP format, with command code 0x7E.

 

The format is defined as :

 

Byte 0 : Transaction Identifier H

Byte 1 : Transaction Identifier L

Byte 2 :  Modbus protocol identifier, should be 0

Byte 3 :  Modbus protocol identifier, should be 0

Byte 4 :  Data Length H, 0

Byte 5 :  Data Length L, 64

Byte 6 :  Unit Address, 0

Byte 7 : Command code 0x7E

Byte 8-39 : Device Name

Byte 40-69 : reserved

 

6.0-2008.11.14

Problem resolved: the Comport property for OPC interface may fail to be updated or modified when multiple ports are defined in WebAccess Configuration. To resolve the issue, please install the latest packing of WebAccess Node on Project nodes.

 

6.0-2008.11.12

Feature changed: A 2-hour demo control file including BEMS (building Energy Management System) and Demand Control options is included with all versions of WebAccess. Please note that the control file will not be overwritten during installation. Therefore, to have the new 2-hour demo control file, please delete previous demo control file (bwkserv.exe in WebAccess\Node directory) before installing the latest packing of WebAccess Node on SCADA nodes.

 

Problem resolved: In Primary-Backup nodes setup, “download graph only” to Backup node will copy some incorrect data from Primary node to Backup node and cause datacore to behave erratically. Specifically, after a Download graphic to backup node followed by a download trend or faceplate, recipe, etc. when restart backup node, datacore shows error: "Database Error! Please re-download database."

 

Problem resolved: WebAccess OPC client fails to operate when port number greater than 12 is assigned to it.

 

6.0-2008.11.07

Problem resolved: The November 06 version failed to start properly.

 

6.0-2008.11.06

Problem resolved: Do not use this version and please use the 11.07 or later packing. Due to packing errors, WebAccess bwview.exe, bwwebv.exe, bwscrp.exe and bwmail.exe will fail to start in the 11.06 version. Please reinstall the latest packing of WebAccess Node, dated November 7 2008 or later, on project/SCADA nodes to resolve the issue.

 

Feature Enhanced: Data Logging. Users can now disable deadband checking for one-minute data in Data Logging.  This feature is enabled or disabled in SCADA node properties in the Project Manager.

 

6.0-2008.11.03

Problem Resolved: some ASP pages for WebAccess Configuration may generate VBScript errors after recent Windows Updates for XP and Vista from Microsoft are installed. We rewrote our asp code to avoid these errors. To resolve this issue, please install the latest packing of WebAccess Node on the project node.

 

6.0-2008.09.30

Feature Enhanced: The display format of tags is increased to 16 digits total.  The max number of digits for the integer portion is 15 digits, and the maximum number of digits for the decimal portion is 15. The tag field .DSPFMT range is increased to 15.1 also to be consistent with configuration.

 

6.0-2008.09.29

Feature Enhanced: Analog Change Dialog Box. The Hex output type in the Analog Change dialog box will be chosen as default when the display format for a tag is hexadecimal.

 

Problem Resolved: Node property page in configuration occasionally failed to display when an old bwCfg.mdb was used. This error was introduced when modified ASP codes introduced to support WebAccess for CE in certain markets.

 

6.0-2008.09.23

Feature Enhanced: The display format of tags is increased to 16 digits total.  The max number of digits for the integer portion is 15 digits, and the maximum number of digits for the decimal portion is 15. The tag field .DSPFMT range is increased to 15.1 also.

 

6.0-2008.09.12

Feature Enhanced: BEMS, Building Energy Management System. A separately licensed data logging and analysis package for monitoring and analyzing Electric Power, HVAC, water, and gas usage.  This is a very advanced package, too broad to describe in these release notes. Please see the BEMS user manual for a description.

 

A BEMS link was added to WebAccess Project Manager (bwproj.asp or the Home hyperlink) to configure the BEMS.

                            

A BEMS popup menu item will appear under Tools menu bar or right-click menu for ViewDAQ and the View Client when the BEMS option is purchased. These will display pre-formatted displays specifically designed for energy monitoring and analysis, HVAC, water and gas usage. Please see the BEMS user manual for a description.

 

Feature Enhanced: Calculation Tag.  A pull-down list of formulas is added next to the Formula field in Calculation Point properties page (i.e. Add Calculation Tag and Update Calculation Tag).

 

Feature Enhanced: Alarm Properties for all Tag types.  A pull-down list of graphic display names (graph names) is added next to the Alarm Graph field in Alarm properties page for Analog and Discrete tags (Add Tag and Update Tag).

 

Feature Enhanced: Event Log configuration (Add Event Log and Update Event Log). A pull-down list if Script files is added for Event Log Tags Setup page (the second page of the configuration) next to the tags to log (this will instead cause the named script to run).

 

6.0-2008.08.26

Problem Resolved: Starting March 2007, WebAccess tried to reduce the startup and primary/backup synchronization, using data written to the TRD folder. But in primary only case, WebAccess also wrote one unnecessary record every time it started to each trend file folder in the TRD folder. This is now eliminated. All the unnecessary files in the TRD folder can be deleted manually.

 

Feature Enhanced: Data Log Trends now can access trend data globally from any SCADA node in the project.  For example tag1 data logged on SCADANode1 can be viewed on a Data Log Trend display on SCADA Node 2 and mixed with tags from SCADA node 2 on the same trend display.

 

Feature Enhanced: Constant Points and Tags from different devices in a single Block. Use the BWCONST device. 

1. Create parameters and block Types for the BWCOSNT

2. Create an API type Comport

3. Create a BWCONST device.

4. Add Blocks.  Leave the address blank to create a Constant Point.

5. If the address is another Tagname in the SCADA Node, it is used to create blocks that span multiple devices (i.e. a Cascade PID block from two separate PID controllers).

 

6.0-2008.08.03

Feature Enhanced: Data Log Trends and Real-time Trends.  Users can create use multiple trend templates (e.g. different colors and layouts) in the same project. For example some trend groups can have black backgrounds to facilitate viewing while others have white to facilitate printing on paper. Users can create and assign up to 100 extra customized trend graph templates for Realtime/Datalog Trend groups. The customized trend graph templates must have “b??” as the file extension:

for Realtime Trend,  the file must be in the form of realtrd.b00, realtrd.b01, ..., or realtrd.b99.

for Realtime Xyplot, the file must be in the form of realxyp.b00, realxyp.b01, ..., or realxyp.b99.

for Datalog Trend,  the file must be in the form of dlogtrd.b00, dlogtrd.b01, ..., or dlogtrd.b99.

for Datalog Xyplot, the file must be in the form of dlogxyp.b00, dlogxyp.b01, ..., or dlogxyp.b99.

 

Please note that the customized trend graph data in WebAccess Configuration (BwCfg.mdb) will be erased when “Saving Trend Setting” is performed from within the previous versions of ViewDAQs or View Clients. Therefore, please make sure that WebAccess software is up-to-date on Project nodes, SCADA nodes, and Client computers

 

6.0-2008.07.29

Problem Resolved: System Point Tags monitorig Comports and Devices. PortSTS, PortCTag, PortDTag, DevSTS, DevCTag, DevDTag, DevBWT and DevComm are all updated to monitor up to comport number  60.

 

6.0-2008.07.18

Feature Enhanced: OPC Server. The SCADA Node can act as an OPC server. By creating a BwOpcServer.ini file in the drive:WebAccess\node\Project_SCADANode folder, the SCADA node will respond to OPC client requests.  The user must define tags in the BwOpcServer.ini.

An example BwOpcServer.ini is as follows:

 

[OPC_DEF]

TOTAL_TAG=3

TAG1=AnalogTagname,0

TAG2=DigitalTagname,1

TAG3=TextTagname,2

 

 

Where 0, 1, and 2 define the tag as analog point, digital point, and text point, respectively.

 

Feature Enhanced: Log Data Maintenance. After archiving ODBC data, WebAccess now compact the Bwpdata.mdb and BwEvent.mdb databases no matter what the data source is. If users do not configure archive ODBC database, then WebAccess does not perform this function.

 

Feature Enhanced: System Point Tags. Two new system tags (parameter names: PDATA and PEvent) are added to show the file size of BwPdata.mdb and BwEvent.mdb on the project node. Users can use these tags to generate alarms if necessary.

 

6.0-2008.07.01

Problem Resolved: A negative integer number or a floating number entered in View Auto Logout Time Out, Restore Alarm Status Time Out, Restore Tag Scan Status Time Out fields in Create New SCADA Node or Update SCADA Node pages, in the WebAccess Project Manager, resulted in the corresponding fields displaying as 0 in the SCADA Node Property page. This caused confusion. Now the WebAccess Project Manager will display consistent values between Create New SCADA Node / Update SCADA Node page and the SCADA Node Property page for these fields so users can easily identify the errors and make any necessary corrections to these fields. Please note that we still do not check if values entered into these fields are valid or not for compatibility reason.

 

6.0-2008.06.25

Feature Enhanced: Event Logs now support logging on Text-type tags into EventLog_? Tables

 

6.0-2008.06.23

Problem Resolved: LNS driver support multiple databases, up to 64. The previous version may report wrong device status if multiple database are involved.

 

Problem Resolved: BacnetJ driver handles display scan type tags.

 

Problem Resolved: Database driver (BWDB) supports text array up to array size 256 .

 

Problem Resolved: WebAccess kernel support Modbus serial RTU server function. The Modbus definition file (named moddef.ini locates at drive:\WebAccess\Node) should look like:

 

[MOD_DEF]

 

LISTEN_PORT= 502

TOTAL_TAG = 7

 

TAG1=40001,TM_65,0

TAG2=40002,SIN_65,4

TAG3=40004,F65_CA01,4

TAG4=40014,F65_CA06,1

TAG5=30001,MD30001,0

TAG6=00001,F65_CD01,0

TAG7=10003,F65_CD_02_ALARM,0

 

[serial]

com=3

baud_rate=19200

data_bit=8

stop_bit=1

MainParity=N

device_unit_no=1

 

 

[Format Description]

LISTEN_PORT = port number for TCP/IP, must match WebAccess device configuration, Default:504

TOATL_TAG = Total tags to be read

TAGn=ModBus_Address,WebAccess_TagName,Type

n= 1 to total_tag

ModBus_Address = 0xxxx, 1xxxx, 3xxxx, 4xxxx

WebAccess_TagName = Point(Tag) Name in Local SCADA node

Type 0 = Unsigned 16-bit integer

Type 1 = Signed 16-bit integer

Type 2 = Unsigned 32-bit integer

Type 3 = Signed 32-bit integer

Type 4 = 32-bit Floating point

 

6.0-2008.06.06

Problem Resolved: Project Manager login.  Resolved five ways to bypass the login process to access the project node’s database configuration pages.

 

6.0-2008.06.03

Problem Resolved: ODBC Logs.  Previously, the sorting in ascending order worked for the last page of the ODBC Log Displays for System Log, Action Log, Alarm Log, Analog Tag Log, Analog Change Log, Discrete Tag Log, Text Tag Log, and Event Log. Previously, using the Start or Prev hyperlink would result in scrambled sort order

 

6.0-2008.05.29

Feature Enhanced: Real-time and Data-Log Trend settings saved to project from VIEW client and ViewDAQ. The current settings for Realtime Trend and Data-log Trends can be saved to SCADA node and uploaded back to project node from within ViewDAQ and View Client.  In VIEW, this is accessible from the mouse. Right Click -> Edit -> Save Trend Setting or using Shift+F4 keys.  In ViewDAQ, this is accessible from the top menu bar Edit -> Save Trend Setting or using Shift+F4 keys. 

 

Feature Enhanced: Extended the scan time for %ACOMSCANTM() from 12 to 60.

 

Feature Enhanced:  Extended port support from 12 to 60 Siemens for Fire Alarm Panel, Omron PLC, Keyence PLC, SMTP, GPIB, Lanstar, LNS and BTrack drives.

 

Problem Resolved: Corrected BCD support for Mitsubishi PLC for Serial interface.

 

Feature Enhanced: Added support for Bacnet schedule and calendar object interface via API defined by Sumitomo.

 

6.0-2008.05.21

Problem Resolved: Deviation Alarming. the display format of .advdbv (Alarm Deviation Deadband Value) and .almdbv (Alarm Deadband Value) was not implemented correctly. Now, the display format of underlying tag is used for .advdbv and .almdbv.

 

6.0-2008.05.15

Driver Enhanced: BACnet IP device driver (BACnetJ) now supports BACnet trend log uploading and synchronization with the WebAccess Data Log Trends and ODBC Database. If Log Data is checked in tag properties, the BACnet trend log of device will be read and inserted into WebAccess DataLog trend files. If the ODBC analog change log is checked in tag properties, data will be added to ODBC database too. To enable this feature, the BACnet trend object instance number is appended to the address of the tag. The syntax to read/sync device trend log data, add /T=nnn, where nnn is the BACnet trend object instance number. For example, AI-5 is logged in trend object 10, the address field will be 0,5,85/T=10.

 

6.0-2008.05.14

Feature Enhanced: Integrity Checking. Previously, tags in table tAcc, tCalcAnalog, tCalcDiscrete, tAnalog, tDiscrete, and tText were checked against TagName field in table pTag. Now, they are also checked against TagType field in table pTag.

 

6.0-2008.05.12

Problem Resolved: 2-byte character display.  2-byte text in R-Text, L-Text, and C-Text animation objects may display incorrectly in View/ViewDAQ if a 2-byte character in the text is truncated by half to fit in the space provided for the animations.

 

6.0-2008.04.29

Problem Resolved: Existing Event Log data would fail to download to the runtime database yet newly added Event Log data downloaded without errors. To resolve the issue, install the latest packing on the project node.

 

Feature Enhanced: Mitsubishi Device Drivers.  BCD conversion has been added to all Mitsubishi PLCs.

 

Feature Enhanced: iLon100 Device Driver.  For iLon100 device, bit write error for a bit within an integer using AUTO-Conversion is corrected.

 

6.0-2008.04.28

Problem Resolved: The System Log could record or display an incorrect Project Name and SCADA node name with multiple use of the Web browser’s Back button to call up pages in the Project Manager. This problem occurred rarely since most users have a single project.

 

6.0-2008.04.08

Problem Resolved: WebAccess View client may disappear mysteriously inside IE. Although very rare, the latest version has a mechanism to recover the View client if it disappears by itself. To implement this update, please install the latest packing of WebAccess Client on client computers.

 

6.0-2008.03.06

Feature Enhanced: iPhone support.  The WebAccess Thin Client now supports Apple iPhone. A new set of  asp codes allows the Thin Client to be displayed correctly on Apple iPhones. When users use an Apple iPhone’s Safari browser to connect to http://your_project_node_ip, they will be redirected to http://your_project_node_ip/broadweb/hd2/m.asp. 

 

Feature Enhanced: Modbus Server. WebAccess adds support for reverse word order for 32-bit data in Modbus server. To use the new feature, a user needs to define type 6,7,8 for reversed word order unsigned, singed and float in the modef.ini file (see section 14.5 of the Engineering manual).

 

Sample definition:

 

[MOD_DEF]

 

LISTEN_PORT= 505

TOTAL_TAG = 7

 

TAG1=40001,TM_65,0

TAG2=40002,SIN_65,4

TAG3=40004,F65_CA01,4

TAG4=40014,F65_CA06,1

TAG5=30001,MD30001,0

TAG6=00001,F65_CD01,0

TAG7=10003,F65_CD_02_ALARM,0

 

[Format Description]

LISTEN_PORT = port number for TCP/IP, must match WebAccess

 

device configuration, Default:504

TOTAL_TAG = Total tags to be read

TAGn=ModBus_Address,WebAccess_TagName,Type

n= 1 to total_tag

ModBus_Address = 0xxxx, 1xxxx, 3xxxx, 4xxxx

WebAccess_TagName = Point(Tag) Name in Local SCADA node

Type 0 = Unsigned 16-bit integer

Type 1 = Signed 16-bit integer

Type 2 = Unsigned 32-bit integer

Type 3 = Signed 32-bit integer

Type 4 = 32-bit Floating point

Type 5 = Double Precision (Low word*10000+ low word)

Type 6 = Unsigned 32-bit integer, Low reg *65536 + high reg

Type 7 = Signed 32-bit integer, Low reg *65536 + high reg

Type 8 = 32-bit Floating point, reverse word order

 

Problem Resolved: Alarm Graphic.  Previously the Alarm Graphic feature truncated file name length for graphic displays to 31 characters (not including the .bgr).  The database will accept 32 characters, but those will be truncated to 31. If there was a file with those 31 characters, it called that file, otherwise no display was called from the Alarm Graph. The Alarm Graphic feature in the WebAccess Alarm Summary, Graphic File names is limited to 32 characters. A download is required after updating the Node software to implement this change.

 

Feature Enhanced: A new DaqTag, %TALMSUMB(, for Alarm Summary Display. %TALMSUM7( is used to display the alarm limit value in Alarm Summary Display and was incorrectly displayed as blank when an alarming tag was a digital tag. We fixed this issue in version 6.0-2008.03.05. However, a minority of our users may be used to this error and would like to continue to display the alarm limit value as blank for a digital tag. For those users, please replace %TALMSUM7( with %TALMSUMB(

 

6.0-2008.03.05

Problem Resolved: Thin Client for Japanese and Chinese. Some web pages of the Thin Client failed to set the correct code pages for JPN, CHN, and TWN versions of WebAccess. This resulted in failing to display 2-byte characters correctly.

 

Problem Resolved: Alarm Summary. The alarm value of a digital tag in the Alarm Summary displayed as the alarm limit while the alarm limit was displayed as blank. Clients will need to download and install the client plug-in from the “Download Plug-in Here” link on bwroot.asp to see the change.  Clients will not be prompted or forced to reinstall the plug-in.

 

6.0-2008.03.04

Feature Enhanced: Filename length for graphics in the Thin Client. WebAccess previously allowed 28 characters for the graphic display file name (32 if counting the .bgr file extension) to be used in Thin Client. The file name limit has been increased from 28 to 60 characters (64 counting .bgr).  The Thin Client will truncate any longer names to 64 characters, if there is a file with those 64 characters, it will call that file, otherwise will give an Error.  To work reliably, with the Thin Client, please limit Graphic File names to 60 characters (reserving 4 characters for the .bgr). After installing Node software on the Project node, download graph to regenerate the Thin Client list.

 

 

6.0-2008.02.14

Problem resolved: Graphic displays fail to open if they contain JPEG, GIF and Bitmaps.  An enhancement to support JPG and GIF files in graphic displays without conversion to BMP files in version 6.0-2007.06.18 introduced a problem. We discovered that the algorithm in ViewDAQ/View used to handle JPG/GIF/BMP data in graph may fail to operate correctly under rare circumstances. This caused image objects in graph to display incorrectly or cause ViewDAQ/View to crash. To resolve the issue, please install the latest version of WebAccess Node on SCADA nodes and WebAccess Client on clients.

 

6.0-2008.01.21

Problem resolved: WebAccess allows a remote web browser client to connect to the SCADA node directly if IIS (Internet Information Server) is installed on the SCADA Node. Please refer to Section 4.5-2005.09.21 of Release Notes or Section 16.1.3.2 of Engineering Manual for further details. We discovered that some error messages did not display correctly if this approach was used to connect to a SCADA node. To resolve the issue, please install the latest packing of WebAccess Node on the SCADA nodes and WebAccess Client on client computers. Please note that after installing and rebooting the SCADA nodes, “download database” or “download graph only” is required at least once.

 

6.0-2008.01.17

Problem resolved: WebAccess Configuration installed on Windows Vista logs out users prematurely. A session timeout is the maximum number of minutes of inactivity allowed by IIS without canceling a session and releasing resources associated with it. Asp code on the project node set the session timeout to 1440. That means WebAccess Configuration will logout automatically after 1440 minutes of inactivity. We discovered for a project node running on Windows Vista, WebAccess Configuration will actually logout automatically after 20 minutes of idle time. To avoid WebAccess Configuration installed on Windows Vista logging out on users prematurely, please install the latest packing of WebAccess Node on the project node.

 

6.0-2008.01.14

Problem resolved: View Client was mistaken as a View in Graph (calling VIEW inside an existing VIEW client graphic) when its style is not “overlapped window with title” and it is included in a dependant display group popped up from within a View in Graph. As a result of this error, the values for %TDAQDSPNAME, %TDAQNAME, and %TDAQTITLE which are associated with the View Client will be incorrect. Macros and scripts which take a parameter in the form of dspname:daqname that identifies the View Client will also fail to operate. To resolve the issue, please install the latest packing of WebAccess Node on SCADA nodes, Project Node and WebAccess Client on client computers. Clients must force a download (e.g. from the “Download Plug-in here” link on bwRoot.asp) and re-install the Client plug-in.

 

6.0-2007.12.10

Feature Enhanced: Read Dynamic AnimationTag Name and Attribute Tag from a local script assigned to an animation. In DRAW and DrawDAQ in the Dynamic -> Animation box, there is the little used “Advanced” button next to tag name.  This assigns a local script to the animation.  To enhance the usability of local scripts when they are associated with animation objects, there are two new tags: %TTAGLS( and %TTAGLSA( found in the DaqTag list.  These tags allow a script to get the Tag name and Attribute Tag name of the animation object the local script is associated with from the “Advanced” button in Dynamic -> Animation.

The format [GETVAL @%TTAGLS(0)] and [GETVAL @%TTAGLSA(0)] to get the values of tagname and attribute tag, respectively. The zero level is the current level and most commonly used. To access Tag name and Attribute Tag name of an animation object nth-level up (assuming that we all understand multi-attributes animation in WebAccess), please use %TTAGLS(n) and %TTAGLSA(n), where n is 1, 2, …..

 

6.0-2007.12.06

Problem Resolved: Previously, graphics using both a trend object and an animation object based on local tags (i.e. a local tag file) might behave erratically in VIEW and ViewDAQ: the graphic might freeze or values may change erroneously.

 

6.0-2007.11.29

Feature Enhanced: URLEncode , a Script Action Command.   To allow scripts in View/ViewDAQ to pass parameters containing 2-byte characters (typically used in Chinese and Japanese) to our asp code on Project Nodes or to other web pages at other web sites, there is a new Action Command, URLENCODE, for WebAccess script engines. The following example illustrates how to URLEncode the string ”中文”.

 

For TclScript:

     [URLENCODE 中文]

 

For VBScript:

URLENCODE(“中文”)

 

For Jscript:

URLENCODE(“中文”)

 

6.0-2007.11.27

Problem Resolved: ASP code for 2-byte languages (Japanese and Chinese).  Previously the ASP code for web pages on the project node using JPN, CHN and TWN versions of Windows Vista might not handle 2-byte characters correctly. We have modified many asp files, ViewDAQ for SCADA nodes and View for client computers to resolve this issue.  The latest packing of WebAccess Node must be reinstalled on Project/SCADA nodes and the latest packing of WebAccess Client is also required for client computers.

 

6.0-2007.11.12

Driver Updated: iLON100 device driver updated to support e3 version of iLON100.

 

6.0-2007.11.08

Problem Resolved: WebAccess OCX used in View/Draw client could not handle project names containing 2-byte characters when used inside JPN, CHN and TWN versions of IE 7. That meant View/Draw client was not be able to connect to SCADA/Project node when IE 7 for JPN, CHN and TWN versions of Windows was used. To resolve this issue, please install the latest candidate version of the WebAccess Client on client computers.

 

6.0-2007.11.05

Feature Enhanced: Variable SCAN time for tags on same com port.  The  /N option appended to the address of a tag allows user to specify a scan time as a multiple of the scan time specified in Comport Properties. The tag will be scanned at the rate of N * scan time.

 

Problem Resolved: Modicon Serial Driver. Beginning with 10/18 build, the WebAccess Modbus serial port driver did not work correctly.

 

6.0-2007.10.30

Feature Enhanced: Export to EXCEL for Scheduled Reports.

1)   In the WebAccess Configuration / Project Manager, while viewing a Scheduled Report Display, use the “Right-click Menu”, then select the “Export to Microsoft Excel” menu item from the popup menu. A version of Microsoft Excel, which supports “Export to Microsoft Excel”, (e.g. Excel 2002 or later), must be installed on the client computer where Internet Explorer is run.

2)   In ViewDAQ, while viewing a Scheduled Report, select “Edit” from the menu bar at top, then select the “Export to Microsoft Excel” menu item from the Edit submenu to export data. A version of Microsoft Excel, which supports “Export to Microsoft Excel”, (e.g. EXCEL 2000 or later), must be installed on the SCADA node where ViewDAQ is run.

3)   In the WebAccess VIEW client, while viewing a Scheduled Report, use the “Right-click Menu”, then select the “Export to Microsoft Excel” menu item from the popup menu. A version of Microsoft Excel, which supports “Export to Microsoft Excel”, (e.g. Excel 2002 or later), must be installed on the client computer where the VIEW client is run.

 

6.0-2007.10.18

Problem Resolved: Log to ODBC for Analog Tag Log, Analog Change Log, Discrete Tag Log and Text Tag Log stopped logging in the build dated 6.0-2007.10.16 and 6.0-2007.10.18. 

 

6.0-2007.10.16

Feature Enhanced: The maximum number of comports is increased from 12 to 60. ) Customers who ever developed their own WebAccess drivers should contact the Milpitas office).  A download of the database is required after update to ensure standard device drivers accommodate the changes.  The Point Info dialog box in View/ViewDAQ is modified by adding two columns of Port Numbers to handle up to 60 comports.  The Station Status Display in View/ViewDAQ scrolls to 60. The Comport Properties page in WebAccess configuration will allow up to 60 entered as comport number.

 

6.0-2007.10.05

New Cameras supported: Two new video types, vivotekmpeg4 and powerview, are added to WebAccess to support the Vivotek MPEG-4 camera series and the Advantech PowerView 6000.

 

6.0-2007.09.26

Problem Resolved: 32-character length description in Faceplate, Realtime Trend, Datalog Trend and Alarm Groups added for VIEW and ViewDAQ. Previously configuration allowed up to 32 characters for the description in Faceplate, Realtime Trend, Datalog Trend and Alarm Groups but VIEW and ViewDAQ displayed only 25 characters of the description.

 

6.0-2007.09.16

Problem Unresolved: We did not expect that our users actually had used the Pushbutton feature with Top Bevel Color, Button Color, and Right-Bottom Bevel Color all setting to Page Color, Bevel Size setting to 0, and Transparent and Animation all checked.  So, when we tried to fix the issue regarding the invisible pushbutton feature (described below for 6.0-2007.09.10), we did not consider the compatibility issue causing drw with pushbuttons to fail to load.  With some major customers actually using this feature, although not correctly, we have to reverse the fix for 6.0-2007.09.10 to maintain the backward compatibility. We will evaluate the possibilities of fixing the issue without causing any compatible issues in the future. For now, please do not use the packing of 6.0-2007.09.10.

 

Clarification: The enhancement for Datalog display for version 6.0-2007.09.05. In the release email and note, we failed to mention that the s/m/h/d value in< SHIFTDTRD>LEFT^s^m^h^d and <SHIFTDTRD>RIGHT^s^m^h^d can be negative. For example, <SHIFTDTRD>LEFT^-1^-1^-1^-1 will shift display window for second/minute/hour/day interval type x second/minute/hour/day to the left, where x is interval for the trend display. For 20 seconds interval trend, shifting will be 20 seconds to the left.

 

6.0-2007.09.10

Problem Resolved: Invisible Pushbutton. WebAccess allows users to create a pushbutton without showing the button itself in View/ViewDAQ if Left-Top Bevel Color, Button Color, Right-Bottom Bevel Color are all set to Page Color, Bevel Size is set to 0, and Transparent is checked as shown in the following picture. Previously, if Animation was also checked, instead of staying invisible the button was shown as a rectangle box in View/ViewDAQ.

                             

6.0-2007.09.06

SIGNIFICANT CHANGE: Data Log Trend One-Minute Data.  The DataLog Deadband is now applied to one-minute trend data. Previously, the dead band was ignored and a value recorded at the end of each minute.  Now, the deadband (multiplied by the difference in high and low span) is used to determine if the new value should be recorded.  The result is that many trends that oscillated within the deadband will now appear flat. However, less data will be recorded, and the SCADA node will start faster and show faster response for users with large amounts of trend data.

 

Feature changed: Data Log Trend. Previously, the first record of one-minute and one-hour data in each month showed the last record of the previous month data. One-minute data and One-hour data only contains data for current month.

 

Modbus Driver: Batch writes for multiple 16-bit registers are optimized.

 

6.0-2007.09.05

Feature Enhanced: Datalog Trends and XYplot display in View/ViewDAQ have the following additional features:

 

1) Start time for Trend/XYplot display will be aligned at second/minute/hour/day boundary for second/minute/hour/day interval type.

 

2) < SHIFTDTRD>LEFT^s^m^h^d and <SHIFTDTRD>RIGHT^s^m^h^d can be used to specify how Trend/XYplot display window shifts. For example, < SHIFTDTRD>LEFT^S^S^S^S will shift display window for second/minute/hour/ day interval type a full span to the left, <SHIFTDTRD>LEFT^Q^Q^Q^Q will shift display window for second/minute/hour/day interval type 1/4 span to the left, and <SHIFTDTRD>LEFT^1^1^1^1 will shift display window for second/minute/hour/day interval type 1 interval to the left.

 

The s/m/h/d value in <SHIFTDTRD>LEFT^s^m^h^d and <SHIFTDTRD>RIGHT^s^m^h^d can be negative. For example, <SHIFTDTRD>LEFT^-1^-1^-1^-1 will shift display window for second/minute/hour/day interval type x second/minute/hour/day to the left, where x is interval for the trend display. For 20 seconds interval trend, shifting will be 20 seconds to the left.

 

3)   New dlogtrd.dxx, dlogxyp.dxx, dlogtrd.bxx, and dlogxyp.bxx with updated< SHIFTDTRD>LEFT and <SHIFTDTRD>RIGHT are included and will be used as the default Datalog Trend/XYplot display for new projects. For existing projects, please copy these files from config/system/drw and config/system/bgr directories or modify your customized Datalog Trend/XYplot display accordingly.

 

Please note that some shift options may not be precise. For example, a trend display with 1 day interval which is aligned at the day boundary, the span will be 365 days or 366 days. Thus, it should be expected that a left-shift ¼ span following by a right-shift ¼ span will not be back to the same display before shifting.

 

To have these enhancements, please install both the WebAccess Node on project and SCADA nodes and the WebAccess Client on client computers. Clients will not be prompted to re-install the client. It is suggested to use the “Download Plug-in Here” hyperlink on the bwroot.asp (the first page in a standard  installation).

 

6.0-2007.08.09

Problem Resolved: Previously, WebAccess Draw client may crash when clicking the OK button after a wildcard filename was input in the name field of various File List dialog boxes. These dialog boxes are DRW File List, DXF File List, and File List for BMP, DSM File List, DFP File List, and DWT File List.

 

6.0-2007.08.01

Feature Enhanced: To avoid accidentally downloading the database or graphics to the SCADA node and accidentally starting or stopping the SCADA node, a web page now pops up for users to confirm the Download, Download Graph only, Start Node or Stop Node operations. Previously this appeared only if a Backup SCADA Node was configured.

 

Feature Enhanced: When submit=1 is specified in the address string accessing an ODBC Log Page, for example: uti:SysLog/LogPg.asp? …………..&submit=1&, the page will display log entries directly without showing the query page first. For more details regarding uti:SysLog, please refer to Chapter 11.1.54 of WebAccess Engineering Manual

 

Feature Enhanced: Advantech DAQ device driver (named ADVDAQ) is added to WebAccess device list.

 

6.0-2007.07.27

Problem Resolved: When changing the Page Count or Node Access for a Restricted User accessed via User Management formerly caused an error that forced an exit out of Project Manager to bwRoot page. The problem was in the UserNodepg.asp.

 

6.0-2007.07.24

Feature Enhanced: Printing to Local Printer of Client. The Print hyperlink in web pages that access  the System Logs (for example the Analog Tag Log) and Scheduled Reports now have an option to select the Local Default Printer on client computers. This applies to Scheduled Reports and System logs accessed via the VIEW client and the Project Manager.

 

6.0-2007.07.12

Problem Resolved:  OPC driver (bwOPC). Formerly, the WebAccess OPC client used the IDataObject interface to handle asynchronous data communications with OPC servers. Recently, it was discovered that this interface is optional for OPC 2.0 servers and is not supported for OPC 3.0 servers. Previous versions of the OPC client driver may fail to communicate asynchronously with OPC 2.0 servers if the IDataObject interface is not implemented on the 2.0 server. The older OPC client driver will fail to communicate with all OPC 3.0 servers. The resolve this issue, the new OPC client now uses the IOPCAsynIO2 interface, which is required by OPC 2.0 and 3.0 servers, to communicate asynchronously with OPC 2.0 and 3.0 servers. To implement this update, please install the latest version of WebAccess Node on the SCADA nodes and download the database after installation.

 

Known Issue: The System Log may record an incorrect Project Name and SCADA node name with multiple use of the Web browser’s Back button to call up pages in the Project Manager.  Essentially the user enters a project, then uses the back button to jump to a cached page for another project, essentially confusing the System Log as to which project the user’s action is applied to. This is similar to the problem described in the 6.0-2007.07.09 build.  This problem occurs extremely rarely since most users only have a single project.

  

6.0-2007.07.09

New Video Type:  Added a new video type named vivotekh263 to support Vivotek Network cameras that encode using the H263 codec.

 

Problem Resolved:  Resolve the issue that WebAccess Configuration may log an incorrect project name to System Log when a new project is created if using the Back key in IE7 to access Create Project.

 

Correction: previous versions of the Release Notes incorrectly described the switching between Primary and Backup field devices (e.g. PLCs) using the system tag DEVCOMM as switching SCADA nodes.

 

6.0-2007.06.25

Problem Resolved:  Exclude Analog Tag Log data from Scheduled Reports when there is no data during the period of data collection (WebAccess records  -2147483648 (Decimal) or 0x80000000 (HEX) to the Alarm field of Analog Tag Log when there is no data during the period of data collection).  Previously WebAccess Scheduled Report modules failed to exclude this type of data and treating blank data as the value zero and thus produced incorrect results.

 

6.0-2007.06.18

Feature Enhanced: To improve the performance of image handling in WebAccess, JPG and GIF files can be used directly in graphic displays without conversion to bmp files. The advantage of using JPEGs and GIFs in graphic displays are: 1) a much smaller file size and 2) better rendering speed. The benefit is further noticed when viewing the graphic display using WebAccess view clients in a web browser. The enhancement can be outlined as follows:
1) JPG files can be used directly as the background image file in graph (File->Set Graph Parameter).
2) JPG file can be used as the image objects directly (Draw->Bitmap).
3) GIF file will be converted to the same GIF format with .bmp as the file extension (Draw->GIF).
4) Removed Draw->JPG menu item since it is no longer needed.

 

6.0-2007.06.12

Feature Enhanced: Speed up the performance when clicking Add Device, especially when there are no existing devices under the com port.

 

Feature Enhanced: Added an option for users to enable tooltips for toolbar buttons in ViewDAQ and View client. The tooltip can be enabled using Toolbar Tooltip option in the SCADA Node properties page. The setting will affect all ViewDAQs on the SCADA node and all View clients connecting to it. To override the setting, please add toolbar=x (0 to disable, 1 to enable) in [tooltip] section of the corresponding bwclient.ini on the SCADA node or client computers.

 

Feature Enhanced: "%PLUS ", "%MINUS ", "%LOOPPLUS ", "%LOOPMINUS ", "%ROTATEPLUS ", and "%ROTATEMINUS " now can be used in Macro/Script (<SETVAL> and SETVAL) to set values of digital/discrete tags.

 

Problem Resolved: Solved the issue when using Windows Vista, a ViewDAQ displaying a graphic with a Video display, may stop responding when it detects the graphic file being changed.

 

Problem Resolved: Solved the issue when using Windows Vista, a ViewDAQ/View displaying a graph with Video Display and indirect tags, may stop responding when it detects the indirect tags being changed.

 

6.0-2007.06.05

Feature Enhanced: WebAccess version number is changed from 5.0 to 6.0.

 

Feature Enhanced: Update Flash object to version 9.0.45.0.

 

Feature Enhanced: Update hardkey Sentinel System Driver to version 7.4.0.

 

Feature Enhanced: Restore Tcl DLL back to version 8.4.0.2.

 

What’s new in WebAccess version 6.0

 

 

Advantech WebAccess HMI & SCADA software

Features

Web Browser based engineering 
Unique to WebAccess all engineering, database configuration, graphics building (DRAW) and software administration (download, start and restart remote nodes) is performed using a standard Web browser.  

Redundant SCADA Nodes & Comports
If the Primary fails, the Backup SCADA Node will begin communications to the automation devices and Web Browser clients will be redirected to the Backup. Redundant Comports enable redundant communications path to Devices.

Data Logging, Historical and Real-Time Trending 
Each tag is logged to a separate file on the SCADA node hard drive; this allows "new tags" to be added to a Historical Trend display without losing history of other tags. A "Real-Time Only" trend reduces disk space requirements.

Alarm Handling Package 
WebAccess provides a notification system to inform operators of process and equipment status including summaries, logs, sorting by priority, alarm response graphic, text messaging to pagers and cell phones, email notification of alarms and Text-to-Speech Alarm Annunciation.

Display Groups 
Local SCADA nodes support a non-web browser version intended for standalone architectures and control room users.

Recipe Function 
Recipes provide an easy method for operators and users to change the value of hundreds of settings.

Scheduler 
The Scheduler provides control and setpoint changes based on time and date.  Lights, Fans, and HVAC equipment are turned on and off based on the time, day of week and date. The Scheduler is also used in process control and manufacturing applications.

DDE, OPC and ODBC interfaces 
DDE, NetDDE, ODBC and OPC are Microsoft communications standards to exchange data with your automation equipment, spreadsheets, databases or 3 Party software packages.

Scripts using Tcl
Scripts in WebAccess are based on the open source programming language Tcl and allow users to develop customized displays, calculations and reports.

Database Import / Export
The database export and import to EXCEL allow users to create and modify Tags and Blocks in a spreadsheet using copy, paste, edit and other EXCEL tools. Databases can be imported from other HMI packages. Tags and Nodes can be imported from other WebAccess Projects to allow aggregation of multiple facilities into a larger Project or to scale down and make a node independent.

Email custom reports, logs and messages WebAccess will email reports and logs generated with Scripts and Pushbutton Keymacros.

Customize Toolbars with Icons and animated buttons 
Use Microsoft Icon files (*.ico) to build tool bars. These can be imported from any application. Animate Toolbars buttons built in DRAW to provide flashing, color change, text changes or any animation.

System Log 
Monitor who connects to the project and SCADA nodes with web browser. 

Centralized Logs 
Log real-time data, alarms, and operator actions from all SCADA nodes to a central ODBC compliant database including: Analog Data Log, Discrete Data Log, System Log, Alarm Log and Operator Action Log.

HTML Reports 
Generate HTML Reports using menu-based queries of Centralized ODBC Logs based on Date, Time, Tag, Node including: Analog Data Log, Discrete Data Log, System Log, Alarm Log and Operator Action Log.  Copy and paste these html reports to EXCEL, Word, etc.

Engineering Tool independent of software version installed at customers’ site. 
An ordinary web browser is the engineering tool! Engineers & technicians always have the right version of software needed.

Distributed Architecture
SCADA nodes run independent of any other node. Each SCADA node communicates to automation equipment using communication drivers supplied with WebAccess.

Centralized Database Server
The Project Node is a centralized database server of configuration data. A copy of the database and graphics of all SCADA nodes is kept on the Project Node.

Enhanced Security 
Users can be assigned various privileges to restrict display and data access. WebAccess uses the Area of Responsibility concept to restrict changes to data.

Vector-based Graphics
Vector-based graphics provide smaller file sizes and faster downloads. Import AutoCAD DXF, Bitmaps, JPEGs and GIFs. AutoCAD DXF files can be imported, edited, filled and animated.

ZOOM graphics in Run time 
Vector Graphics allow users to zoom in to magnify any display up to a power of 8x.

Video and Audio
Web-enabled Video cameras allow operators and users to monitor equipment and facilities using the WebAccess client. Live full-motion Video, audio and Windows Media are viewed in same Graphic display as Trends, Alarms. Pushbuttons and Live Data.

ActiveX
WebAccess uses an ActiveX control running inside Internet Explorer to provide real-time, dynamic data and graphics with full animation.

Thin Client 
WebAccess provides a "true" Thin Client interface for PDA, Pocket PCs and others not wishing to install our ActiveX Client plug-in. The Thin Client interface is an alternate to the full animation Client. No special software or operating system is required.

Global database
The "tags" and real-time data from all SCADA nodes in a project are viewable on all nodes.

Email notification of Alarms 
Email notification of Alarms is a standard feature in WebAccess. No third party software is required. Tags can be individually selected to generate an email, assigned recipient email address or use global email recipients. Alarms can be "acknowledged" via a reply email.

Pager, Wireless PCS and Cell Phone text messaging for Alarms and Events
Pagers, wireless PCS and Cell Phones that can receive text messages can also be used for notification of Alarms and events. No third party software is required. Tags can be individually selected to generate an message to a specific recipient address or use global recipients. 

Schedule Alarm Email and Page recipients by Shift, Day of Week, and Holidays 
Schedule who receives Alarm email and text message pages based on Time of day, Shift, Day of week, and Holiday schedules.

Scheduled Reports 
Scheduled Reports include Shift, Daily and Monthly reports that are automatically generated from the Real-time data. Users & Operators can View the current and previous reports using a web browser. Reports are optionally emailed and printed automatically by the WebAccess SCADA node. The output of the Scheduled Reports can be copied and pasted into EXCEL, WORD, and other general-purpose office applications as a formatted table or spreadsheet.

 

Project Node - System Requirements

Operating System: Windows 2000 (Professional and Server), Windows Server 2003, Windows XP Professional, Windows Server 2008, Windows Vista Business or Vista Ultimate with IIS (Internet Information Server) installed. (See notes 1 and 2 below.)

IIS (Internet Information Server) installed.  The WWW Service (web Server) must be installed and running. ASP (Active Server Pages) enabled.

SMTP Server (optional, not recommended). The SMTP service is not needed on the Project Node if using Email Alarm Notification, Email of Scheduled Reports or MAIL commands. WebAccess normally uses an external SMTP Server (for example the corporate email server or and ISP) to forward email. Optionally, you can allow the Project node to forward email directly.

NTFS File System - NTFS provides Security and it is faster. FAT provides no security and is not appropriate for the Web Server (Project Node).

Microsoft Licensing will limit the number of clients connecting to IIS.  The Limit is 10 simultaneous connections in Windows 2000 and XP Professional. In Windows 2000 and XP Server versions, the limit is dependant on your license (it can be unlimited). Vista Business is unlimited

Hardware: Pentium III, Pentium IV, Celeron or Athlon processors are recommended for the Project Node and SCADA nodes.  SCSI Hard Drive, SAN or other large cache storage recommended if Data Logging.

Network Addressing: Fixed IP Address or network address.   See section 2.3.1 About Addresses of Engineering Manual for more information.

Web Browser: Optional. Needed for configuration tool. Microsoft Internet Explorer 6.0, 7.0, 8.0 or later. (ASP enabled) Medium Security Zone setting for safe browsing.

Display Resolution:  (Optional although a Display is recommended). 1024 x 768 or higher (recommended).  Lower resolutions also supported.

Communications Service: Microsoft TCP/IP Protocol.

Communications Speed: T1 or DSL is recommended. 
(33 Kb/sec, 56 Kb/sec, 128 Kb/sec and ADSL supported)

User Security Privileges:
For Windows 2000, 2003, XP and Vista, Standard Users (i.e. a member of the Power Users) can install and run the client. Restricted Users (i.e. a member of Users) cannot install and cannot run the Client.

Web Security: WebAccess supports Anonymous Access, Authenticated Access (Integrated Windows authentication) and Secure Communications including Certificates, Secure Sockets and Virtual Private Networks (VPN).

Firewall Security (optional): If using a connection through a Firewall, two additional TCP Ports assigned by your system administrator are required. These are in addition to Port 80, the HTTP port, which must also be opened (or a third port assigned for HTTP).

Note 1 - Windows 2000 and Windows XP, Windows XP requires service pack 2 (SP2) or later, 2003 Server requires service pack 1 (SP1) or later, Windows 2000 requires service pack 4 (SP4) or later.

Note 2 - Windows Vista Home, Windows XP Home, Windows 98, and Windows ME are not supported as a Project node or SCADA node.  They do not provide Web Server software. They can be Clients.

SCADA Nodes - System Requirements

Operating System: Windows 2000 (Professional and Server), Windows Server 2003, Windows XP Professional, Windows Server 2008, Windows Vista Business or Vista Ultimate with IIS (Internet Information Server) installed. (See notes 1 and 2 below.)

NTFS File System - NTFS provides Security and it is faster. FAT provides no security and is not appropriate for the SCADA node.

Hardware: Pentium III, Pentium IV, Celeron or Athlon processors are recommended for the Project Node and SCADA nodes. SCSI Hard Drive recommended if Data Logging to SCADA Node. The hard drive disk controller will be the limiting factor on most systems depending on the number of tags data logged.  

Network Addressing: Fixed IP Address or network address.   See section 2.3.1 About Addresses for more information.

Web Browser: Optional.  Needed for configuration Tool. Microsoft Internet Explorer 6.0, 7.0, 8.0 or later. (ASP enabled). Medium Security Zone setting to allow ActiveX control.

Display Resolution:  1024 x 768 or higher (recommended).  Lower resolutions also supported.

USB or Parallel Port: D25 pin parallel port (LPT1 - ECP mode required) or USB port required for License Hardkey.

Serial Port: If using RS-232 or RS-422 it is recommended to have an actual serial port.  Using a Serial to USB converter is not recommended because errors on the serial device are often masked by the USB driver interface.

Communications Service: Microsoft TCP/IP Protocol.

Communications Speed: T1 or DSL is recommended. 
(33 Kb/sec, 56 Kb/sec, 128 Kb/sec and ADSL supported)

User Security Privileges:
For Windows 2000 and XP, Standard Users (i.e. a member of the Power Users) can install and run the SCADA node. Restricted Users (i.e. a member of Users) cannot install, but can run the SCADA node.

WebAccess supports Virtual Private Networks (VPN).

Firewall Security (recommended): If using a connection through a Firewall, two additional TCP Ports assigned by your system administrator are required. These are in addition to Port 80, the HTTP port, which must also be opened (or a third port assigned for HTTP).

IIS -  Internet Information Server (optional, not recommended).  The WWW Service (web server) is not needed on the SCADA Node. Normally users connect via the Project Node and are redirected to the SCADA node. Optionally users can connect directly to the SCADA node using a local file and manually entering the SCADA Node information as described in section 16.1.3 bwView.htm. Optionally install IIS on the SCADA node to allow an alternate method of allowing users to connect (a type of redundancy) if the Project Node or main web server is not available.

SMTP Server (optional, not recommended). The SMTP service is not needed on the SCADA Node if using Email Alarm Notification, Email of Scheduled Reports or MAIL commands. WebAccess  normally uses and external SMTP Server (for example the corporate email server or ISP) to forward email from SCADA Nodes. Optionally, you can allow the SCADA node to forward email directly.

Note 1 - Windows 2000 and Windows XP, Windows XP requires service pack 2 (SP2) or later, 2003 Server requires service pack 1 (SP1) or later, Windows 2000 requires service pack 4 (SP4) or later.

Note 2 - Windows Vista Home, Windows XP Home, Windows 98 and Windows ME are not supported as a SCADA node.

 

Client - System Requirements

Operating System: Windows 2000 Professional and Windows XP Professional are highly recommended as clients. Windows Server 2008, Windows 2000 Server and Server 2003 are also supported.

Windows Vista Home Basic, Vista Home Premium, Vista Business and Vista Business Ultimate are also supported as clients on many, but not all, hardware platforms (See note 3.)

Microsoft Windows 98 and Windows XP Home support most, but not all, features in the WebAccess client. (See note 2.)

Hardware: Pentium, Celeron, Athlon or better required by clients.

Network Addressing: Dynamic IP (DHCP) and fixed IP supported. Host names (e.g. computer network name), if recognized by client, SCADA Node and Project node, are also supported.

Web Browser: Microsoft Internet Explorer 6.0, 7.0. 8.0 or later supports all features. ASP enabled and ActiveX enabled. A Medium Security Zone setting for safe browsing using either the Internet Zone, Intranet Zone or Trusted Site.  Video Requires IE 6.0, 7.0, or later (ASP enabled).

Display Resolution:  1024 x 768 or higher (recommended).  Lower resolutions also supported.

Communications Service: Microsoft TCP/IP Protocol.

Communications Speed: T1 or DSL is recommended. 
(33 Kb/sec, 56 Kb/sec, 128 Kb/sec and ADSL supported)

User Security Privileges: For Windows 98 / ME, all Users can install and run the Client.

For Windows Vista, 2000, 2003 and XP, Standard Users (i.e. a member of the Power Users) can install and run the client. Restricted Users (i.e. a member of Users) cannot install and cannot run the Client.

Web Security: WebAccess supports Anonymous Access, Authenticated Access (Integrated Windows authentication) and Secure Communications including Certificates, Secure Sockets and Virtual Private Networks (VPN).

Firewall Security (optional): If using a connection through a Firewall, two additional TCP Ports assigned by your system administrator are required (4592 and 14592 are the default TCP ports). These are in addition to Port 80, the HTTP port, which must also be opened. For more Information see The Engineering Manual Section 1.6.1.1 TCP Ports and Firewalls.

Note 1 - Windows 2000, XP and 2003. WebAccess can be run under Windows 32 bit operating systems for Intel compatible systems only. It will not run under other types of Windows such as Windows for DEC Alpha or Windows for PowerPC®.
Windows XP requires service pack 2 (SP2) or later. 2003 Server requires service pack 1 (SP1) or later. Windows 2000 requires service pack 4 (SP4) or later.

Note 2- Windows XP Home, Windows 98, and Windows ME do not support all advanced animation features in WebAccess including bitmap rotate and text rotate.

Note 3- Windows Vista running on some hardware platforms (for example single core INTEL and AMD) do not support Video, Tools, Reports and web browser controls inside a graphic display.  

            It appears most Dual Core INTEL and AMD PCs produced after 2006 do support all features in the WebAccess Client using Vista.  

          It is recommended to test an Vista based PC before using it as a WebAccess Client if you plan to use Video, Tools, Reports, Logs or any Web control inside a graphic.

 

Thin Client Requirements

Operating System: Apple iPhone with Safari browser, Microsoft Windows Mobile 5.0 for Pocket PC, Windows CE version 3.0 or later. Also, Windows 95, 98, ME, NT 4, 2000, XP, 2003 and Vista can be used. Palm OS has limited functionality (text only interface for Palm OS).

Web Browser: Microsoft Pocket Internet Explorer and Internet Explorer 5.0 or later. Internet Explorer 6.0 or 7.0 also supported.

Display Resolution:  200 x 200 minimum. 

Communications Service: Microsoft TCP/IP Protocol

Communications Speed: Wireless Ethernet, T1, DSL, ISDN, serial
(33 Kb/sec, 56 Kb/sec, 128 Kb/sec) and ADSL supported

User Security Privileges:
No installation of software is required.

Web Security: WebAccess supports Anonymous Access, Authenticated Access (Integrated Windows authentication) and Secure Communications including Certificates, Secure Sockets and Virtual Private Networks (VPN).

Note - The Thin Client interface supports static snapshots of graphics (GIFs and JPEGs). Each time the refresh button is pushed, a "snapshot" of the animation is made. Thin Client Displays do not automatically. It does not support animation, pushbuttons, or drag regions (slider bars). Thin Clients require a continuous connection with the Project Node and may increase the licensing requirements of the Windows 2003, 2000 or XP software to support an increased number of connections.

 

Disk Space and CPU speed

These apply to the SCADA Node (for Data Log Trend Files) and Project Node (for ODBC Log Files). 

SCSI Hard Drives are recommended if you a Data Logging to the Project Node or SCADA Node.

Data Log Trend recording

The hard drive disk controller will be the limiting factor on most systems depending on the number of tags data logged.

The actual number of tags that can be Data Logged by a SCADA node is dependent on:

·         Processor Speed (CPU Speed)

·         Hard Disk Access Time

·         Processor Load (due to other tasks like scripts, schedules, communications, calculation tags).

·         Scan Rate of the Communication Port

A guideline is 500 tags/second for a 1.8 GHz Pentium IV processor. If your Scan rate is every 3 seconds, then you could data log about 1500 tags. Increasing the deadband to reduce the number of changes/second could increase this number of tags data logged. These assume the worse case scenario that there is no deadband or that the tags exceed the deadband every scan cycle.

500 tags/second scan rate

1000 tags / 2 second rate

2000 tags / 4 seconds rate

The use of a deadband will result in recording only significant changes, effectively reducing the number of value changes recorded per scan (and increasing the number of Tags that can be data logged).

If you are Data Logging more than 1500 tags  on a SCADA node, you should consider using multiple SCADA nodes or using SAN, NAIS or other Disk Cache to speed up Disk Controller Access times by the SCADA node PC.

Data Log Trend Disk Space

Real time trends never store data on the hard drive.

Data Log Trends record Data to the Hard Drive of the SCADA Node.

Log to ODBC (Analog Tag Log, Discrete Tag Log, System Log, Action Log and Alarm Log) record data to an ODBC Database on the hard drive of the Project Node (an Access Database by default, named BwPData.mdb via the DSN named bwPData_Access).

Data Log Trend records 10 bytes per sample on the SCADA node.  If you are sampling 1000 tags every 1-second and you are using NO deadband, then it will be:

500 tags * 10 bytes/sample * 1 scan/ sec * 3600 samples/hour * 24 hours/day * 30 days/month  * 1/1024 *1/1024 *1/1024  = 12 Gigabytes in a month.

500 tags * 10 bytes/sample * 1 scan/ sec * 3600 samples/hour * 24 hours/day * 365 days/year  * 1/1024 *1/1024 *1/1024  = 146.9 Gigabytes in a year.

500 tags * 10 bytes/sample * 1 scan/ sec * 3600 samples/hour * 24 hours/day * 1/1024 *1/1024 = 412 Megabytes in a day.

If a deadband is used, it will be less. If you assume the tags exceed deadband only 50 percent of the time (every 2 seconds), it will be

12 * .5 = 6 Gigabytes / month / 500 tags

146.9 * 0. 5 = 73.5 Gigabytes / year / 500 tags

412 * 0. 5 = 206 Megabytes / day / 500 tags

If a 5 second scan time is used:

500 tags * 10 bytes/sample * 1 scan/ 5 sec * 3600 samples/hour * 24 hours/day * 365 days/year  * 1/1024 *1/1024 *1/1024  = 29.4 Gigabytes in a year.

The Maximum file size of an Access Database is 2 Gigabytes.

The Log Data Maintenance feature in WebAccess will archive Data Log Trend files to a network folder or mass storage device AND will ERASE files that are older than a user-defined period on the local hard drive of the SCADA Node. Log Data Maintenance will also archive and delete the expired (old) records from the ODBC Log databases on the Project Node.  (See Log Data Maintenance for a description of Automatic Archiving and Maintenance of Data Log Trend Files).  The Log Data Maintenance will prevent your disk drive from filling up if used properly.  In the above examples, if Log Data Maintenance were set for 30 Days would require only 9 Gigabytes of Disk space for data log trend files for 500 tags.

Note - if both Archive and Delete Expired Files are selected, but the Archive device is off-line, then the expired records and files will not be deleted.

Archive / Mass Storage Disk Space

Data Log Maintenance will copy expired Data Log Trend files daily to the archive media. No file compression is used in version 3.0.  In the above 500 tag examples:

412 Mega Bytes /day / 500 tags / sec assuming every tag changes every second with no deadband for Data Log Trend files.

Data Log Maintenance will also create Access Database files daily for expired records from the ODBC Logs; up to 6 files daily: System Log, Action Log, Alarm Log, Analog Tag Log, Discrete Tag Log and Text Tag Log, as selected by user. If the SCADA node is off line, then a data file will be created the next day the SCADA node is running at the record time, containing data from the previous day(s).

The minimum size is 64 Kbytes per daily ODBC file. (6 x 64Kbytes = 384 Kbytes / day minimum). The maximum is hard to calculate for System, Alarm and Action Log.

Action Log (bwActionTable - bwPData.mdb) 220 Kbytes / 500 Operator Actions

Alarm Log (bwAlarmTable - bwPData.mdb) 4200 Kbytes / 20,000 Alarms

Analog Tag Log (bwAnalogTable - bwPData.mdb) 29,900 Kbytes / 370,000 Value changes

Discrete Tag Log (bwDiscreteTable - bwPData.mdb) 14,200 Kbytes / 250,000 State changes.

Text Tag Log (bwTextTable - bwPData.mdb) 4200 Kbytes / 20,000 changes.

There is no Archive restore or Playback feature in version 4.0.  An Archive restore and playback is scheduled for a future release. Users can manually copy Data Log trend files (second X, minute M and hour H files) back to the SCADA node to view archived data.  Archived ODBC files are easily opened using Access.

Program Files

Typical size of the WebAccess Node subdirectory (WebAccess Program files) for a combined Project/SCADA node is 29 Megabytes. 

Typical Size for a WebAccess Client Subdirectory (Program files only) is 6 megabytes.

Typical Size for the InetPub\wwwroot\broadweb subdirectory on the Project Node is 7 megabytes.

Graphics

You have to make an estimate of the number of graphics on the SCADA Node, Project Node and Clients. Assume 200 Kbytes/graphic, 20 tags per graphic and 300 graphics

300 graphics * 200 Kbytes/graphic  * 1/1024 * 2 = 5 Megabytes in /bgr and 5 Megabytes in DRW = 10 Megabytes

Around 32 Megabytes is required for all the default symbol libraries, widgets and system drawing files on the Project Node and SCADA node(s). 

The entire Symbols and widgets are not downloaded to the Clients.  Only the individual symbol or widget is downloaded to a client if it is requested while using DRAW. Similarly, only the individual Graphic File(s) requested by a Client is downloaded and cached on the Client PC.

The Log Data Maintenance feature in WebAccess will archive Data Log Trend files to a network folder or mass storage device AND will ERASE files that are older than a user-defined period on the local hard drive of the SCADA Node. Log Data Maintenance will also archive and delete the expired (old) records from the ODBC Log databases on the Project Node.  (See Log Data Maintenance for a description of Automatic Archiving and Maintenance of Data Log Trend Files).  The Log Data Maintenance will prevent your disk drive from filling up if used properly.  In the above examples, if Log Data Maintenance were set for 30 Days would require only 9 Gigabytes of Disk space for data log trend files for 500 tags.

Note - if both Archive and Delete Expired Files are selected, but the Archive device is off-line, then the expired records and files will not be deleted.