menu

For the installation of ToolScope Net is the archive "ToolScope_Net-V11-*-Setup.zip" (link) necessary, alongside a server.

Installation

The first step is to set up the server. A Linux operating system should be installed. The most suitable is the operating system "Debian GNU / Linux", but this is not a prerequisite. Then a network adapter is to set up, which must be connected to the machines to be monitored.

Now the files from the archives can be installed. For this, the archive "ToolScopeNetPacket-V11-*.zip" needs to be unpacked. After that, there should be the folder "ToolScopeNetPacket" and the file "InstallationScript.sh" inside the unzipped folder. An example is illustrated in Fig. 1

 

Figure 1: Folder content after unpacking the archives (Windows example)

For the file "InstallationScript.sh" needs to be executed for the installation. Be sure to make it executable first before trying to run it with (chmod 0700 ./InstallationScript.sh). The script will create folders copy files and give a status report of the process. After the script finished, it will automatically start the ToolScope Net software, if there were no errors.

 

First Start

If the ToolScope Net software is not running start the script “/etc/init.d/TSFirmware.sh” with the following command:

nohup /usr/local/bin/TSFirmware.sh &

Use the command "ps aux | grep java" to determine if the ToolScope Net software is running. There should be a process running  with a large argument line, which runs the java class "brinkhaus.launcher.Firmwarelauncher" or/and "brinkhaus.dataProcessing.ProcessingInstance"

 

To get the visualization of the ToolScope Net software, the visualization software ToolScope Connector is necessary. It can be downloaded at the same location as the ToolScope Net software. Or you should be received it if you got the data via E-mail or SFTP server. Unzip the archive "ToolScope_Connector.zip" and copy the folder "... / ToolScope_Connector / Visualization_Windows / 20170619 /" to a Windows computer on the network. After copying, run the file “ToolScope_Connector.exe” on the Windows computer.

 

Figure 3: Service screen of the ToolScope Connector

 

There should be a window as shown in Figure 3. Press “F1” to open a new window as shown in Figure 4. In the Target-IP field, type the IP address of the server. In the Target-Port field should be the number 2200. Then press the "OK" button.

 

Figure 4: connection window of the ToolScope Connector

 

 

The contents of the ToolScope Connector should now look similar to Figure 5. The messages in the diagnosis are likely to differ.

 

Figure 5: Diagnostic view of the ToolScope with the ToolScope Connector

 

 

Now you can press Settings and then click on "Other" in the lower left corner. The menu should then look similar to Figure 6.

 

Figure 6: View of the ToolScope with the ToolScope Connector

 

 

Now write the text "NumberOfTo" in the field with the text "search words". You should see the variable "NumberOfToolScopeInstances (FirmwareLauncher)" as shown in Figure 7.

 

Figure 7: Settings view for other ToolScope settings

 

Select the value with a mouse click and press the "Edit variable" button. Then a window should open as shown in Figure 8. Set a desired value into the text field that corresponds to the number of monitoring instances. Then press "Save" button and press the "complete restart" button. After this, the system must be restarted or the script must be executed again.

 

Figure 8: Window for changing a variable of the ToolScope

 

Now you can set the ToolScope further according to the manual. To get to the other instances, press the key combination "CTRL" and "arrow up" in the ToolScope Connector. Then, press F1 and enter a different port. Port 2200 is the first instance. All other instances are to be found consecutively behind port 2200.