Using Qosium Probe

Qosium Probe is not directly operated as such since Qosium measurements are controlled fully by a measurement controller. However, there are certain operative functionalities, like license activation and launching, that are discussed in this section.

1. License and Activation #

Qosium Probe needs a license to run. The license information is locally stored in a license file located in Probe’s installation folder. The license can be pre-activated, like, for example, in the academic license. In this case, Qosium usage can be started right after the installation.

In installation-limited licenses, each Qosium Probe needs to be activated online. The activation is carried out simply by using Kaitotek’s License server as follows:

  • Launch the Probe if not already running
  • Verify that the device where Qosium Probe is installed has Internet access
  • Open a measurement controller, like Qosium Scope, and connect Qosium Probe
  • Qosium Probe will now activate itself at Kaitotek’s License server.

A successful activation is typically fast. There appears some information of the successful activation while the controller just connects the Probe as usual. If something goes wrong, error information is delivered via the controller. An activated Qosium Probe will be fixed to the device. However, the installation can also be moved to another device.

If your license requires online activation, but it is impossible to organize an Internet connection to the device, contact Kaitotek’s support. There are also other alternatives for the activation.

2. Launching Probe #

Once Qosium Probe has been parameterized, it is time to launch it. Typically, Qosium Probe is set to run as a system service. In this way, it always starts with the platform, being ready for measurements. This also has the advantage that running Qosium measurements does not require administrative rights in the platform.

Qosium Probe can also be run as a normal application. This can be useful in some special cases since Probe’s log window will be visible. Administrative rights, however, are needed when launching the Qosium Probe application.

The way of launching Qosium Probe is dependent on the platform. These are discussed in the following subsections:

Only a single Probe is required per measurement point.
Did you try to launch Qosium Probe as an application, but it failed because of a reserved port? If so, check that is Qosium Probe already running as a system service.

3. Installation Transfer #

If you have an installation-limited license, it is possible to transfer an activated Qosium Probe to another device. In practice, Qosium Probes can always be installed without limits, but in installation-limited license models, only a certain number of them can be in use. Thus, transferring Qosium Probe from one device to another is, in practice, transferring the license.

License transfer is carried out as follows:

  • Verify that both of the devices have an Internet connection
  • Go to the device from where the Qosium Probe is to be removed
  • Open command line (with administrative rights in Windows)
  • Start Qosium Probe with a special argument:
    • Windows: QosiumProbe licunreg
    • Linux: sudo <path>/QosiumProbe licunreg
  • The given command will try to release the activated license. Check the printed log that did it succeed. If so, the license has been disactivated and the installation-right returned to the Kaitotek’s License server.
  • Now go the device where the installation will be transferred to
  • Install Qosium Probe there, if not already installed.
  • Activate the Qosium Probe installation as explained earlier

4. Log #

Qosium Probe writes a high-level log to standard output when it is running. Typically, there is no need to observe this log. In some rare cases, e.g., when troubleshooting license issues, you may need to check the log. When you launch Qosium Probe directly as an application from the command line, the log will be printed there to be observed directly. If Qosium Probe runs as a system service, you need to access the system log.

For example, if you are running Qosium Probe as a system service in Ubuntu, and you wish to see the last 50 lines of Qosium Probe’s log, it is done in terminal as follows:

sudo systemctl status -n 50 QosiumProbe

Further Reading