.

The Server Utility allows MPI and MPX applications running on remote computers to control local motion controller cards by connecting via a TCP/IP connection.

Usage

At the command line, type one of the following options:
         ex: C:\mei\XMP\bin\>server -control 1

server [-control #] [-listen # (3300)]

 

Where

-control n Specifies that controller n in the machine is to be used.
NOTE: Controller 0 is the first controller in a machine.
-listen portId Listens for connections on TCP/IP port portId.

 

Examples

C:Mei\Xmp\Bin\>server
C:Mei\Xmp\Bin\>server -control 1
C:Mei\Xmp\Bin\>server -listen 3000
C:Mei\Xmp\Bin\>server -control 1 -listen 3000

 

Client/Server Connections Limitation

Server.exe launches two threads for each client connection. Each thread requires 2 MB of memory. For the eXMP-Series controller with 128 MB RAM, server.exe allows for 8 client connections. If server.exe cannot launch a thread, it will display a "Fatal Error" and cause the client to fail with a "Connection Closed" error. The other connections will continue to operate until server.exe is exited.

Troubleshooting

If the server.exe fails, it will display error messages. When using headless controllers (ex: eXMP-SynqNet), pipe the server.exe output to a file, which will allow you to retrieve the error messages at a later time.

 

 

       Legal Notice  |  Tech Email  |  Feedback
      
Copyright ©
2001-2008 Motion Engineering