- #WONDERWARE INTOUCH 10 ALARM DB LOGGER MANAGER SOFTWARE TO OPERATE#
- #WONDERWARE INTOUCH 10 ALARM DB LOGGER MANAGER MANUAL REV 1#
Hello.Wonderware InTouch HMI 2014 R2 (Version 11.1) Readme Last revision: About This Readme This Readme provides information about InTouch HMI 2014 R2 (Version 11.1). August 6th, 2014, 10:22 AM. There's a test button to test your connection. Press the create button to create the WWALMDB database.
Wonderware Intouch 10 Alarm Db Logger Manager Manual Rev 1
After starting InTouch WindowViewer (alarm provider) on the Windows Vista, Windows 7, and Windows Server 2008 R2 node, open the SMC Logger and look for the most recent string generated by AlarmMgr. The source alarms will not appear unless the AlarmViewer control's alarm query is configured.This type of query only works for InTouch HMI as an alarm provider running in a Terminal Services session, not for InTouch HMI running in a console session.To configure the AlarmViewer's alarm query The process to configure remote alarm retrieval queries has changed for interactive applications such as InTouch HMI when running on Windows Vista, Windows 7, and Windows Server 2008 R2.10 Alarm DB Logger Object User Manual Rev 1.0 P186m10 c) if alarms are checked and alarms are displayed in any Wonderware alarm display from Platform directly, check Alarm DB Logger consumer settings in ObjectWhen InTouch WindowViewer is started and generates alarms from an interactive Windows Vista, Windows 7, or Windows Server 2008 R2 desktop session, an AlarmViewer control (running within InTouch HMI) on a remote node must be specially configured to query the alarms. Awareness Library symbols for alarms, trends, and valves: Alarms SAAlarmSeverity: Shows an alarm summary that includes Alarm Border.
However, there is a limitation in that the combination of Alarm DB Logger configured as a service and InTouch HMI running locally as a console application is still not supported. The Alarm DB Logger now runs as a Service in Windows Vista and later operating systems primarily to support Galaxy Alarms and InTouch HMI Alarms from Terminal sessions. Test to validate that the alarms generated from the alarm-providing node are shown accurately in the AlarmViewer control.Wonderware InTouch HMI and Alarm DB LoggerIn earlier releases that supported Windows Vista, Windows 7, or Windows Server 2008, the Alarm DB Logger could not be enabled to run as a service. In the Alarm Query tab of the AlarmViewer control on the remote computer, configure the alarm query as follows, substituting your nodename of the alarm providing InTouch HMI for "nodeabc" below and substituting your IP address noted in the previous step:Where nodename is the name of the node that is providing the InTouch alarm and ip_address is the IP address that you determined in step 1. The indicated IP address will be unique to your alarm-providing node.
One impact to Wonderware Application Server is to carry forward the restriction introduced with the Windows Vista operating system which permits only one alarm provider. You must install the "Terminal Server" role for Windows 2008 SP2 or the "Remote Desktop Host" role for Windows 2008 R2 in order for TSEGetClientId() and other related functions to work properly.The impact to Wonderware Application Server is minimal as most Wonderware Application Server processes run as services. The cause of this behavior is that the relevant roles are not installed on the Terminal Server. Refer to the Wonderware InTouch HMI 2012 R2 (v10.6) Readme for further information about InTouch HMI applications running in the Terminal Server Console.In another aspect of Terminal Services behavior, InTouch HMI functions such as TSEGetClientID() can return a null value when running on Windows 2008 SP2 and Windows 2008 R2 operating systems with InTouch running in a remote desktop (RDP) client session. Windows Server 2008 and later operating systems treat all remote connections as remote RDP sessions regardless of /console, /admin, or any other switches used to make the connection.This impacts InTouch HMI functionality such as Alarm Manager that depends on the Terminal Server Console session. In Windows Server 2008 and later operating systems, Session 0 is no longer an interactive session, and is reserved only for Windows services.
Wonderware Intouch 10 Alarm Db Logger Manager Software To Operate
The Run dialog box appears. Click Start and then Run. Windows Server 2008 and later operating systems treat all remote connections as a remote RDP session regardless of / consoleor /admin switches in the mstsc connection.To disable fast user switching through the Group Policy interface However, this behavior requires that you disable Fast User Switching in both Windows 7 and Windows Server 2008 and later operating systems.When running Windows Server 2008 and later operating systems, you must modify the terminal services behavior for the Wonderware software to operate properly.Wonderware software detects when an application is running in the console. In Windows Server 2008 R2 it implies that the application was started by a user physically at the machine.
Enabling this policy hides the Switch User option in the Logon interface, the Start menu, and the Task Manager. Set Hide Entry Points for Fast User Switching to Enabled. Go to the following location: Local Computer Policy > Administrative Templates > System > Logon. The Group Policy dialog box appears.
Right-click and select DWORD (32-bit) Value. Go to the following location: HKEY_LOCAL_MACHINE > SOFTWARE > Policies > Microsoft > Windows > CurrentVersion > Policies > System. The Registry Editor dialog box appears. Enter regedit.exe and click OK. So, alternatively, you can configure the Switch User settings through the registry.To disable fast user switching through the Registry Editor
The computer running Windows Vista can be either an InTouch HMI or an ArchestrA alarm provider, but not both simultaneously. If a computer runs Windows Vista as part of an InTouch HMI system, it cannot be configured to be both an InTouch HMI and ArchestrA alarm provider. Windows Vista does not support a dedicated single-node server configuration that runs one or more databases for an InTouch HMI system. On the File menu, click Exit to close the Registry Editor.In a Terminal Server environment that has a managed application deployed to it, the following behavior applies to references in the InTouch HMI application to the InTouchViewApp object:ArchestrA Symbols referencing InTouchViewApp_001.Tag1:Running on the Console - Refers to the tag value of the application running on the console.Running in a Session - Refers to the tag value of the application running on the console.Restarting the Window Viewer application running on the console causes references from the terminal session to disconnect and then reconnect.Running in a Session - Refers to the tag value of the application running in the session.ArchestrA Graphic referencing InTouch:Tag1:InTouch Graphic referencing Galaxy:InTouchViewApp_001.Tag1:Wonderware InTouch HMI 2012 R2 (v10.6) with Windows Vista, Windows 7, and Windows Server 2008 R2 Set the HideFastUserSwitching data value to 1.
The connection will work when User Account Control is disabled. The DDESuiteLink Client connection to the local DAServer using DDE does not work with User Account Control enabled. Hovering to select from the Windows keyboard does not work in the Windows 7 Professional and Windows Server 2008 R2 Standard operating systems.Using Wonderware Application Server with Windows 7 and Windows Server 2008 R2This section describes specific behaviors and restrictions when using the Windows 7 and Windows Server 2008 R2 operating systems with Wonderware Application Server. The onscreen keyboard options have changed for the Windows 7 and Windows Server 2008 R2 operating systems. The InTouch Extensibility Toolkit might need to be started by right-clicking and selecting Run As Administrator on Windows Vista or later operating systems to function properly. If Recipe Manager is started using the path Start\ Program\ Wonderware\ InTouch\Recipe, then select Run as Administrator on Windows Vista or later operating systems.
0 kommentar(er)
