MBLogic
for an open world in automation
Help - Installation - Starting the Application
Overview:
Starting the Application:
When all software has been installed, you can start the application.
Starting from Linux:
Do one of the following"
- If you are using Gnome, double click on the "mblogic.sh" file.
- Or from the command line, type "./mblogic.sh".
Starting from MS Windows:
Do one of the following"
- If you are using the MS-Windows GUI, double click on the "mblogic.bat" file.
- Or from the command line, type "mblogic.bat".
The batch file ("mblogic.bat") assumes that you have installed Python version 2.5 or 2.6, and that you have installed it in the default location ("C:\Python25" or "C:\Python26"). If you have a different version of Python installed, or have installed Python in a different location, you will have to edit the batch file accordingly. To edit the batch file, open it with a text editor (e.g. MS Notepad), and change it to match the version and location of your Python installation.
Start-up Messages:
You should see something like the following appear:
Starting MBLogic. Starting system status web server... Starting ModbusTCP server... Starting REST web service... Starting help system web server... Starting HMI web service... Starting ModbusTCP clients... Started to connect outgoing client PumpPressure Started to connect outgoing client FanCommand Started to connect outgoing client Robot1 Started to connect outgoing client Beacon Started to connect outgoing client SlidePosition Started to connect outgoing client Conveyors Started to connect outgoing client FanSpeed Started to connect outgoing client Horn Soft logic system started. Server Loopback Server running at 9:39:30, Mon 05 of Jan, 2009 ... Incoming client connected to Modbus TCP server from 127.0.0.1. Incoming client connected to Modbus TCP server from 127.0.0.1. Incoming client connected to Modbus TCP server from 127.0.0.1. Incoming client connected to Modbus TCP server from 127.0.0.1. Incoming client connected to Modbus TCP server from 127.0.0.1. Incoming client connected to Modbus TCP server from 127.0.0.1. Incoming client connected to Modbus TCP server from 127.0.0.1. Incoming client connected to Modbus TCP server from 127.0.0.1. Connected outgoing client FanCommand. Connected outgoing client FanSpeed. Connected outgoing client Horn. Connected outgoing client Robot1. Connected outgoing client PumpPressure. Connected outgoing client Beacon. Connected outgoing client SlidePosition. Connected outgoing client Conveyors.
Some of the above lines may appear in a different order depending on when the connections are made. The above assumes you are using the example configuration file included with the release. If you are not using the example configuration, you will see a different series of messages relating to which servers and clients are starting up and connecting.
Port usage is determined by the configuration file.