This TechNote gives you important instructions to be performed on each platform at which you want to deploy the DIObjects to avoid having licensing issue in runtime when running new versions from DIObject , which use the new Archestra License not suitelink.lic for example DIMBTCP 3.0 sp1 and DIABCIP 5.0, inside Wonderware Application Server 3.1 SP3 Patch 1 .
Sentinel Agent and Manager Sentinel is a new feature included in System Platform 2017 Update 3. Sentinel constantly monitors the License Server to ensure that it is accessible. In the event that the connection to the License Server is lost, Sentinel can be configured to send a warning message so you can quickly fix any issues and ensure. License: Failed to retrieve information from the FS A2 Development license. Either the FS A2 Development license is not available or it has expired. I checked Invensys Licence Manager and the dev licence is definitely there and its expiry date is June 2017. On the other VM, the licensing setup is identical and ArchestrA IDE opens up with no. To use the new computer name as the license server, navigate to Start Programs ArcGIS Desktop Administrator on a computer where ArcGIS Desktop is installed. Click License Manager on the left and the Change button on the right. Type in the license server's new name and click OK. Move the ArcGIS License Manager from one machine to another.
Application Versions
- Application Server 3.1 SP3 P01
- DI MBTCP 3.0 SP1
- DI ABCIP 5.0
OPERATING SYSTEM
Windows Server 2008 R2
SITUATION
When running newer DASSERVER it stops periodically , getting Information message in your logger says that <DASERVER name > Please install a valid license for this DAServer product as shown in fig.1 below. trying with external demo license and getting same issue.
Figure 1: License invalid info message
SYMPTOMS
DAServer now uses the ArchestrA License Manager and the common ArchestrA license file.
If you are still using software versions that use the wwsuite.lic license file, and you do not have an ArchestrA.lic license file with the correct feature line you need to add it, you need to run InitLicense.wsf file included with the CD image to initialize the new ArchestrA Licensing sub-system.
ACTION
If you are running Wonderware Application Server 3.1 SP3 Patch 1 or older, you must perform the following functions on each platform where you want to deploy the MBTCP DIObjects to it, Please follow below steps.
- Undeploy DIObjects. and close IDE.
- Install two Microsoft components manually.NET 4.0 Framework and Visual C++ 10.0 SP1 run-time redistributable components.
- Run the InitLicense.wsf file included with the CD image, fig.2, to initialize the new ArchestrA Licensing sub-system.
Figure 2: InitLicense.wsf file in DIObject CDWe will see license subsystem Initialization success message as shown in Figure 3 (below).
Figure 3: License subsystem initialization success message - Launch ArchestrA IDE and deploy DIObjects again.
Script in InitLicense.wsf
<job>
<script language=”VBScript”>
Set oShell = CreateObject(“WScript.Shell”)
If CInt(oShell.RegRead(“HKLMSOFTWAREMicrosoftWindows NTCurrentVersionCurrentBuildNumber”)) > 3790 Then
If WScript.Arguments.Named.Exists(“elevated”) = False Then
‘Launch the script again as administrator
CreateObject(“Shell.Application”).ShellExecute “wscript.exe”, “””” & WScript.ScriptFullName & “”” /elevated”, “”, “runas”, 1
WScript.Quit
Else
‘Change the working directory from the system32 folder back to the script抯 folder.
Set oShell = CreateObject(“WScript.Shell”)
oShell.CurrentDirectory = CreateObject(“Scripting.FileSystemObject”).GetParentFolderName(WScript.ScriptFullName)
End If
End If
Dim WSHShell, RegKey, OsType, FolderPath, ProgramFilesPath
Set WshShell = CreateObject(“WScript.Shell”)
OsType = WshShell.RegRead(“HKLMSYSTEMCurrentControlSetControlSession ManagerEnvironmentPROCESSOR_ARCHITECTURE”)
FolderPath = “Common FilesArchestrALicense”
If OsType = “x86” Then
RegKey = “HKLMSOFTWAREWonderwareLicense”
ProgramFilesPath = wshShell.ExpandEnvironmentStrings(“%PROGRAMFILES%”)
FolderPath = ProgramFilesPath + FolderPath
‘wscript.echo “Windows 32bit system detected”
Else
If OsType = “AMD64” Then
RegKey = “HKLMSOFTWAREWow6432NodeWonderwareLicense”
ProgramFilesPath = wshShell.ExpandEnvironmentStrings(“%PROGRAMFILES(x86)%”)
FolderPath = ProgramFilesPath + FolderPath
‘wscript.echo “Windows 64bit system detected”
End If
End If
WSHShell.RegWrite RegKey & “FlexLicFileDir”, FolderPath, “REG_SZ”
wscript.echo “ArchestrA Licensing sub-system initialization succeeded.”
</script>
</job>
This article offers those who master the classic InTouch R14, a step-by-step instruction on setting up communication with devices using the Modbus TCP protocol. I’ll try to explain those features of the settings that can put a novice developer in a difficult situation.
1. Licensing
The company Klinkmann supports developers of their products, issuing full, but temporary licenses, each of which operates a little less than a month. After the expiration of this period both the development system and runtime stop working. It is required to repeatedly request and update license files.
Usually three files are issued. All of these must be installed in the ArchestrA License Manager. It looks like this:
The absence of a license or an incorrectly installed license may be the cause of the lack of communication. After installing the license, it is desirable to reboot.
2. Download and install the integration package Server DA (DASMBTCP)
Detailed configuration instructions in the video:
3. As an emulator of the MODBUS TCP operation, I usually use the product from Modbus Tools (Modbus Pool & Modbus Slave)
Immediately configure the data exchange to make sure that everything we have is working with the Modbus TCP protocol and data is being exchanged.
Attention!!!
ID is set to 255. Otherwise it will not work. Where to change this value in driver properties – yet did not find. If your Slave device has a different ID, then the working connection will not be achieved.
We disable the Modbus Pool, we do not need the port to be busy at the beginning of the connection.
4. Configure the Server DA driver (DASMBTCP)
Pay attention to the port number (for example, indicated 503)!
Here we form a common list of tags that will exchange data with the PLC
Help describes the signs that we can specify for correct data retrieval
5. Indication of parameters on video frame
We go in WindowMaker
Create an Access Name that will be associated with our topic and server
Archestra License Manager 2014 Crack
Next, create the required number of tags associated with the Access Name
Archestra License Manager 2014 Torrent
Next on the video frame create a dynamic text
Linking (linking) it with the tag we need
6. Run the system Online (Runtime)
If there is no error anywhere, values similar to those in the Modbus Slave
I experimented a bit with disabling the drivers manually. I found out that when communication is lost, the values remain on the screen without changing, without giving out any indication of an error. This is certainly not suitable for the work of the industry. I will look for how to implement otherwise, for example, the replacement of values by the signs of the lattice. I will supplement this article later, when I find a solution
Wonderware License Manager
#InTouch, #stepbystep, #instructions, #settings, #drivers, #Modbus, #Stepbystepinstruction, #Stepbystep