To use the ToolScope Net as a service, some steps are required. The following prerequisites exist for this action:

  • A “Windows 2000” or later operating system
  • A current version of Java JRE or JDK (minimum version 8)
  • A admin account with access
  • The "ToolScope_Net-V11-*-Setup.exe" file (link)

Step one: Install the ToolScope Net

To install the ToolScope Net software on a windows operating system, execute the "SoftScope-V11-Setup.exe" with admin rights. Then follow instruction of the setup assistant. If the setup detects no Java on the system, press yes in the next dialogue to install it. Be careful the Java installation dialogue can be in the background.  At the end of the copying process, the installer will ask you if you want to set up a normal application. You need to answer with "no".

Step two: first start

The Visualization of the ToolScope Net is started automatically at the installation. Otherwise there will be a shortcut in the start menu named "ToolScopeNet_Visualization".
It will take the service a little bit time to start up depending on the computer. After a while there should appear the ToolScope Net GUI, instead of the white service screen.


Figure 1: The GUI of the ToolScope  Net displayed with ToolScope Connector


Press the Settings tab and click on "Other" in the lower left corner. The menu should then look similar to Figure 2.


Figure 2: View of the ToolScope with the ToolScope Connector



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


Figure 3: 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 4. 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 4: 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.


Now you can configure the ToolScope Net and follow others manuals.


Additional step:  start up fails

If step two fails because the ToolScope Connector is never showing a visualization like Figure 1, then there can be a problem with the service. First open the services menu in windows with administration rights. You can just enter "service" into the window start menu for newer version. Older versions of windows will offer the service menu over the system controls.

Inside the service menu search the entry "ToolScope_Net" and click it. There should be column named "status" which show if the ToolScope Net is running. If it is not running, then there is a text named "start the service" on the left site. Click the text part "start" to start the service. If its now running check if the start-up type is set to automatic. Most of the time there can be two different errors coming while trying to start the service.

The first one says that the system can't find the target file. This means that the "nssm.exe" got deleted form the ToolScope Net folder. This problem can be solved with little time. Just call our technical support and we can send you the necessary file and help you solving the error. You can also repair the error itself, if you have a backup of the system. The file "nssm.exe" should be in the subfolder "NSSM" inside the ToolScope Net installation path. Inside the subfolder "NSSM" the file is inside the two subfolders "win32" and "win64". Mostly one of the folders is completely missing after that error.

The second error says that the ToolScope Net could not start for some reason and often brings some hart to understand reason with it. This error can mostly be solved by changing the account which executes the service. Per default the local system account is doing that. In the properties of the service there is the tab "Log on". There you can set the account which should execute the service. If this does not solve the problem, please call our technical hotline.