The new CPE305 has a new way to connect to via Ethernet straight out of the box. Instead of using a utility and pushing an address into it, you can simply use the factory address of 192.168.0.100. Once online with the CPU you can change the target address as needed.
There are two alternative methods to get online with a new CPE305 as well:
Use a configured Ethernet module (IC695ETM001) in that same rack and download an address into the CPE305 via the ETM.
Use a serial cable (IC693CBL316) to download into the CPE305.
The CPE310 has the same Ethernet setup as the CPE305. The main connectivity difference is the number of serial ports. Similar to the classic CPU310, it has one 9 pin port as well as one 15 pin port.
Keep in mind the CPE310 can be loaded with a CPU310 configuration which makes migration much easier. This allows you to use your Machine Edition with versions back to 5.5 SP1.
Useful information from your partners in automation.
Tuesday, January 31, 2012
Using Excel to View Data from a DAServer
There are two methods you can use to view data from a DAServer in Excel. The first is explained in Wonderware’s Tech Note 686 – Using FSGateway and SuiteLink to Replace NETDDE. Use Tech Note 686 if you wish to connect to a DAServer on a remote node. Tech Note 686 can be used to connect to a DAServer on the local node as well. When connecting to a local DAServer, you can also use the method explained below.
In the example below, the DAServer used is the DASABCIP and the operating system is Windows 7 64-bit. The procedure below is required when using Excel to connect to a local DAServer on Windows Vista, Windows 7, or Windows Server 2008.
1. Open the System Management Console and ensure the DAServer is deactivated. Right-click the DAServer and select Configure As Service > Not a Service. This is a very important step. You will not be able to establish communications to any DAServer via local DDE if it is set to run as a service.
3. Name your shortcut and click Finish.
4. Double-click the shortcut to start the DAServer.
5. Verify the DAServer is activated in the System Management Console. The icon next to your DAServer should have a green box with a white checkmark.
6. Open Excel and enter the DDE formula =ApplicationNameTopic!Tagname. In the example below, my ApplicationName is DASABCIP, my Topic is TankFarm, and my Tagname is Tank106_Level. If everything is configured correctly, you will see the value of the Tagname when you hit Enter.
In the example below, the DAServer used is the DASABCIP and the operating system is Windows 7 64-bit. The procedure below is required when using Excel to connect to a local DAServer on Windows Vista, Windows 7, or Windows Server 2008.
1. Open the System Management Console and ensure the DAServer is deactivated. Right-click the DAServer and select Configure As Service > Not a Service. This is a very important step. You will not be able to establish communications to any DAServer via local DDE if it is set to run as a service.
2. In addition to configuring the DAServer as “Not a Service”, you must start the DAServer outside the System Management Console in order to access it via local DDE. Therefore, you must browse to the executable to start the DAServer, or simply create a shortcut. To create a shortcut, right-click on your desktop and select New > Shortcut, click Browse and find the executable for your DAServer. The default location in Windows 7 for the DASABCIP is:C:\Program Files (x86)\Wonderware\DAServer\DASABCIP\Bin\DASABCIP.exe.
3. Name your shortcut and click Finish.
4. Double-click the shortcut to start the DAServer.
5. Verify the DAServer is activated in the System Management Console. The icon next to your DAServer should have a green box with a white checkmark.
6. Open Excel and enter the DDE formula =ApplicationNameTopic!Tagname. In the example below, my ApplicationName is DASABCIP, my Topic is TankFarm, and my Tagname is Tank106_Level. If everything is configured correctly, you will see the value of the Tagname when you hit Enter.
Wednesday, January 4, 2012
Upgrading InTouch Runtime nodes to InTouch 2012
Classic InTouch is often installed with both Development and Runtime features enabled. We've typically installed both features, even if it really is an InTouch runtime node only, and let the license determine how it's used. This causes a problematic upgrade with InTouch 2012. If you've installed both features, the installer program cannot tell whether the node is being used as a Runtime or Development, so it will upgrade both features.
Why does this matter? Because with InTouch 2012, a Development workstation includes not just InTouch, but also Wonderware Application Server and Microsoft SQL Server (for ArchestrA graphics development).
So when you upgrade an InTouch node, it will likely install InTouch, Application Server, and MS SQL Server Express.
This does not create a huge problem, but it does use additional hard drive space and runs some additional services. And it certainly is unnerving if you didn't expect it.
To avoid having the installer migrate your InTouch Runtime to a Development platform, you should first modify your existing InTouch installation and remove Development from the feature list.
In Control Panel / Add or Remove Programs, select Wonderware InTouch. Click 'Change'. In the subsequent Setup dialog box, select Modify, and then click Next.
Click InTouch Development, then select Entire feature will be unavailable. Then click Next and complete the install wizard.
You can now upgrade to Version 2012 and it will properly detect that this node is just an InTouch Runtime.
Why does this matter? Because with InTouch 2012, a Development workstation includes not just InTouch, but also Wonderware Application Server and Microsoft SQL Server (for ArchestrA graphics development).
So when you upgrade an InTouch node, it will likely install InTouch, Application Server, and MS SQL Server Express.
This does not create a huge problem, but it does use additional hard drive space and runs some additional services. And it certainly is unnerving if you didn't expect it.
To avoid having the installer migrate your InTouch Runtime to a Development platform, you should first modify your existing InTouch installation and remove Development from the feature list.
In Control Panel / Add or Remove Programs, select Wonderware InTouch. Click 'Change'. In the subsequent Setup dialog box, select Modify, and then click Next.
Click InTouch Development, then select Entire feature will be unavailable. Then click Next and complete the install wizard.
You can now upgrade to Version 2012 and it will properly detect that this node is just an InTouch Runtime.
Subscribe to:
Posts (Atom)