IWS Installation on Windows CE-Based Devices
Although this example references the Beckhoff CX5020 controller as the CE device on which the embedded runtime-only product installation will be performed, it is intended as a general tutorial on such installations to a Windows CE-based device. If your device employs a CE Processor Type other than X86, you will use the CE processor-type subfolder of \Redist that matches that of your device when selecting the correctly compiled CEServer.exe file from the path on your development machine, as specified below. For example, if your CE device employs an ARM processor, then you will substitute ARMv4i for X86 in the path.
It is preferred that the runtime system files installation goes through the link between the Remote Management dialog and the Remote Agent program, because it not only copies files, but it also registers specific files on the operating system of the CE device. You would have to manually register these files if you simply copied the system files from the development system to the CE device without going through this link. Likewise, you should use this link to copy the project, as well, as this process automatically creates/updates the file called CEAPP.ini on the CE device, which contains the pointers used by CEView.exe to locate and identify the project that it will execute at runtime startup.
This information assumes that you are running Indusoft version 7.0, 7.1.or 8.0.
On the CF card (or other suitable storage memory), create a folder
just for the Indusoft files, and call it Studio, for example. You need to copy
one file to this Studio folder from the IWS development machine to begin the
process. Since the CX5020 has an x86 CE Processor Type, you need to copy the
file c:\Program Files\Indusoft Web Studio vX.x\Redist\WinCE 5.0\X86\Bin\CEServer.exe
from the development machine to the Studio folder on the CE device.
At this point, you should open the Indusoft development environment and load the project that will run in the CX5020 if you want to install it, as well, after installing the runtime system files. Run the CEServer.exe program from the Studio folder on the CX5020. This will bring up the Remote Agent dialog, which should display the current IP address of the CX5020 at the bottom of the dialog.
On the Indusoft development machine, select Home, then select the Connect icon in the Remote Management group on the ribbon. This will open the Remote Management dialog with the Target tab displayed. Enter the IP address of the 5020 for the Target Station and select the Connect button to establish the link between the Remote Mgmt dialog and the Remote Agent program on the CX.
The Status field will show that you are connected to CEView v1.0
(because you haven’t yet installed the runtime system files), and the Platform
line will show the Win CE version and the processor type. If the connection is
not established, there may be something blocking communications via TCP Port
4322, on which the Remote Agent is listening, and you may need IT help to
correct it.
When the connection is established, ensure that the “Only Newer
Files” box is not checked. Select the Install System Files button to send the runtime
system files to the device, which also registers Issymbol.ocx on the CE
operating system. This is the Active X control which is required to interpret
and display our graphic screens. The correctly compiled set of runtime system
files for your platform and processor type will be sent to the CE device, based
on the specific CEServer.exe file you selected in the first step.
Once the runtime system files have been downloaded, select the Project tab on the Remote Management dialog, and ensure that the Target line shows the correct path to the Studio folder on the CX5020, ending with the name of the project folder that will be created. Ensure that the box labeled “Only Newer Files” is not checked, and select the Download button to create the project folder on the CX5020 and send the project’s subfolders and files to that folder.
If you receive an error that the folder doesn’t exist, use the browse button at the end of the Target line to open a browse window, navigate to the Studio folder on the CX5020, use the Create Directory icon to create the folder, open it, then click OK to close the Browser. Always ensure that the Target line displays the correct path to the project folder before sending any files to the remote device, whether it is the first installation, or simply an update to existing project files.
Note that the runtime system files located on the CE device consists of a Bin folder and a Drv folder. This Bin folder is a copy of the Bin folder on the development system from which you originally copied the CEServer.exe file to place in the Studio folder, which means that it contains its own copy of CEServer.exe. You should never run this program from inside the Bin folder. Always execute the copy of CEServer.exe that is outside the Bin folder. If you ever update the service pack or version of the Indusoft product installation on your development machine, and then connect to the Remote Agent and re-send the system files to update them on the CE device, you should then stop the Remote Agent, and overwrite the CEServer.exe that is located outside of the Bin folder with a copy of the newer version that is now inside the Bin folder. If you have configured Windows CE’s Startup group (or the Init key in the Windows CE Registry) to automatically launch CEServer.exe at startup, this may prevent you from overwriting CEServer.exe as just described, because CEServer.exe launches a sub-process called Codemeter.exe, and Windows will not allow you to delete CEServer.exe as long as Codemeter.exe is running. You will need to start the CE device, stop the IWS project runtime, then remove the auto-launch configuration and restart the device again. This will prevent CEServer.exe from launching, thus preventing Codemeter.exe from launching, enabling you to overwrite the old CEServer.exe with the new one. You can then restore the auto-launch configuration, shutdown and restart the device to launch your project runtime on the newly updated system files.