Introduction

Network Dashboard is an utility software that may be very useful to manage large number of active machines in one place. It allows you to check working statuses of motion platform in your facility, monitor its temperatures and up times. It also notifies about pending Action Center issues that require your attention. All you need is single master PC and machines with their computers connected to the same local network. The Network Dashboard is always installed together with the ForceSeatPM Platform Manager.

Configuration

At this point we need to assume that your local network is well configured. All machines and its computers are turned on and connected to the local network. Another mandatory that needs to be fulfilled is Platform Manager application running on every computer. Having all set it is time to launch Network Dashboard application. It establishes connection with Platform Managers that are running on the slave computers and continuously monitors connected devices.

First launch

After first launch default configuration.ini file is created. It defines IP addresses of slave computers and expected number of machines connected to each one. The configuration file can be opened directly from the application by clicking Configuration link that is placed at the top left window corner. The content of the configuration file looks like below:

[10.0.0.1]    ; change to the correct ip address of your host computer
Port=35001    ; change to the correct port number that is available on your host pc
DeviceCount=1 ; set number of devices that are connected to the host pc

[10.0.0.2]    ; change to the correct ip address of your host computer
Port=35001    ; change to the correct port number that is available on your host pc
DeviceCount=1 ; set number of devices that are connected to the host pc

Every slave computer entry consists of IP address, connection port and number of connected devices. You need to change default values and enter real data that will allow to establish network connections.

For this example purpose, let’s assume that there are two 2 slave computers in the local network at following IP addresses “192.168.1.101” and “192.168.1.139”.  PC#1 is expected to work with 3 machines, PC#2 with only 1. Configuration file for such setup would be as follows:

[192.168.1.101]
Port=35001
DeviceCount=3

[192.168.1.139]
Port=35001
DeviceCount=1

Machine information

Every single machine listed in the application has a visual representation with set of specific data that can be very useful to monitor, diagnose and resolve potential problems. Usually it will be nothing more than new software update notified by Action Center but having swarm of running machines at one time may be very demanding to deal with.

Available data:

  • machine name
  • serial number
  • host IP address
  • not resolved Action Center issues that require your attention
  • firmware version
  • device components temperatures
  • up time
  • status
    • OK                   – everything is OK
    • No Machine – means that machine is not connected to PC
    • Error              – has to be checked directly on the specific PC
    • No Host PC  – computer specified in configuration file is not available
    • N/A