otech
07-15-2008, 12:02 AM
mControl version 2.1 has been confirmed to run on Beckhoff CX10xx systems running Windows XP Embedded. As previously mentioned, we had accomplished this using mControl version 1.x.
The Beckhoff embedded controller we tested was the CX1001-x21 with 128 MB of RAM. Here, it is connected to a CM11A X10 adapter and an X10 lamp module.
http://www.embeddedautomation.com/images/appnotes/Beckhoff-CX1001.jpg
Although we were able to get mServer running on the CX1001-x21, due to its low memory, we strongly recommend using the CX1020-x21 or the CX1030-x21 with at least 512 MB of RAM and 2GB of Flash drive space.
Since we have not yet developed mControl functionality with Windows CE, the Beckhoff CX9000 series is currently not supported. For now, you will need an embedded controller running Windows XP Embedded.
This guide will contain:
1) Installing mControl on a Beckhoff embedded controller
2) Connecting to your embedded controller’s mControl server with a PC
1) Installing mControl on a Beckhoff embedded controller
The first step is to ensure your Beckhoff embedded controller is running .NET Framework 2.0 or higher. If not, download it to your controller. Here is the link for .NET 2.0: http://www.microsoft.com/downloads/details.aspx?familyid=c4837dad-5719-4b63-8752-cb0a65802329&displaylang=en#AffinityDownloads
After you have the .NET framework, installing mControl on your controller should be the same as on any other Windows XP system. Download the latest build of mControl, unzip the folder, and run the installer located in the Win2K_XP_Vista folder. Detailed installation instructions can be found on page 42 of the mControl v2 User Manual located at:
http://www.embeddedautomation.com/mControl%20v2%20(Home%20Edition)%20User%20Manual.p df
Once you have completed the install, try running mServer.exe on the controller. If you want to see live logging output, run mServer through command prompt with the following command:
C:\>”Program Files\Embedded Automation\mControl\server\mServer.exe” /d
Keep mServer running on your embedded controller for the next step.
2) Connecting to your embedded controller’s mControl server with a PC
First, we will want to have mControl installed on the PC that will be connected to the server hosted on the Beckhoff.
When you install mControl on your PC, there are two options:
You can:
i) Do a client install
ii) Do a full install
Due to possible resource conflicts, we recommend you only do one type of install on your PC. You will also need to configure your firewall on each system to allow exceptions for ports 29990 to 29995.
i) Client Install
The advantage of the client install is that you do not have to manually configure the connection each time you want to connect to a different mControl server. You can select from a list of discovered servers.
For instructions on the client install, refer to the following link:
http://www.embeddedautomation.com/forum/showthread.php?p=4303#post4303
ii) Full install
For installation instructions, refer to the mControl user manual, as previously mentioned.
After install, you will want to connect to the server hosted on the Beckhoff embedded controller. To do this, you will need to edit the RemotingClient.config file on your PC, located in the \Embedded Automation\mControl folder.
Open the file, and where you see the following lines, replace “localhost” with the IP address of your Beckhoff.
<add key="mControl.WebServiceUrl" value="http://localhost:29990/mServer.asmx" />
<wellknown type="EmbeddedAutomation.mHome.Api.IAuServer, mHomeApi_tcp" url="tcp://localhost:29992/mAuServerURI" />
<wellknown type="EmbeddedAutomation.mHome.Api.IAuServer, mHomeApi_http" url="http://localhost:29991/mAuServerURI" />
Do the same for the matching entries in the web.config file located in the same directory. This way, you will be able to connect via mControl for IE as well as through mControl Editor.
Regardless of the method you chose to install mControl on your PC, you should now be able to connect to the server running on your Beckhoff. Open mControl Editor and press the connect button. You should now be connected to the server.
Changes to the service, such as which adapters will be loaded, need to be made on the Beckhoff.
Happy Automation!
The Beckhoff embedded controller we tested was the CX1001-x21 with 128 MB of RAM. Here, it is connected to a CM11A X10 adapter and an X10 lamp module.
http://www.embeddedautomation.com/images/appnotes/Beckhoff-CX1001.jpg
Although we were able to get mServer running on the CX1001-x21, due to its low memory, we strongly recommend using the CX1020-x21 or the CX1030-x21 with at least 512 MB of RAM and 2GB of Flash drive space.
Since we have not yet developed mControl functionality with Windows CE, the Beckhoff CX9000 series is currently not supported. For now, you will need an embedded controller running Windows XP Embedded.
This guide will contain:
1) Installing mControl on a Beckhoff embedded controller
2) Connecting to your embedded controller’s mControl server with a PC
1) Installing mControl on a Beckhoff embedded controller
The first step is to ensure your Beckhoff embedded controller is running .NET Framework 2.0 or higher. If not, download it to your controller. Here is the link for .NET 2.0: http://www.microsoft.com/downloads/details.aspx?familyid=c4837dad-5719-4b63-8752-cb0a65802329&displaylang=en#AffinityDownloads
After you have the .NET framework, installing mControl on your controller should be the same as on any other Windows XP system. Download the latest build of mControl, unzip the folder, and run the installer located in the Win2K_XP_Vista folder. Detailed installation instructions can be found on page 42 of the mControl v2 User Manual located at:
http://www.embeddedautomation.com/mControl%20v2%20(Home%20Edition)%20User%20Manual.p df
Once you have completed the install, try running mServer.exe on the controller. If you want to see live logging output, run mServer through command prompt with the following command:
C:\>”Program Files\Embedded Automation\mControl\server\mServer.exe” /d
Keep mServer running on your embedded controller for the next step.
2) Connecting to your embedded controller’s mControl server with a PC
First, we will want to have mControl installed on the PC that will be connected to the server hosted on the Beckhoff.
When you install mControl on your PC, there are two options:
You can:
i) Do a client install
ii) Do a full install
Due to possible resource conflicts, we recommend you only do one type of install on your PC. You will also need to configure your firewall on each system to allow exceptions for ports 29990 to 29995.
i) Client Install
The advantage of the client install is that you do not have to manually configure the connection each time you want to connect to a different mControl server. You can select from a list of discovered servers.
For instructions on the client install, refer to the following link:
http://www.embeddedautomation.com/forum/showthread.php?p=4303#post4303
ii) Full install
For installation instructions, refer to the mControl user manual, as previously mentioned.
After install, you will want to connect to the server hosted on the Beckhoff embedded controller. To do this, you will need to edit the RemotingClient.config file on your PC, located in the \Embedded Automation\mControl folder.
Open the file, and where you see the following lines, replace “localhost” with the IP address of your Beckhoff.
<add key="mControl.WebServiceUrl" value="http://localhost:29990/mServer.asmx" />
<wellknown type="EmbeddedAutomation.mHome.Api.IAuServer, mHomeApi_tcp" url="tcp://localhost:29992/mAuServerURI" />
<wellknown type="EmbeddedAutomation.mHome.Api.IAuServer, mHomeApi_http" url="http://localhost:29991/mAuServerURI" />
Do the same for the matching entries in the web.config file located in the same directory. This way, you will be able to connect via mControl for IE as well as through mControl Editor.
Regardless of the method you chose to install mControl on your PC, you should now be able to connect to the server running on your Beckhoff. Open mControl Editor and press the connect button. You should now be connected to the server.
Changes to the service, such as which adapters will be loaded, need to be made on the Beckhoff.
Happy Automation!