FAQ

Your data will be automatically updated and used by the new version. After the first GUI start, a message is displayed offering a database upgrade. This automatic migration includes the following data:

• Results (including all files, recordings, etc.)

• Missions/Tasks

• Frequencies and frequency lists

• Stored filters

• Scheduler actions

• System position

Other application settings will not be transferred automatically to a new version. Contact our customer support if a transfer to the new version is necessary. Custom modems and decoders are stored separately in a central location and will be automatically reused by the new version.

The Splash screen can be closed by clicking on it. Open the <Resources> view via the <Views> menu and check if any components are in a red/yellow state. If yes, check if there are any error messages shown as items under that component in the tree-view.

For example, the Result storage component will be in the error state if there is less than 1 % free space on the hard disk.

Try closing the software and starting again. Contact our customer support if none of the above helps.

In the case of a network receiver not being recognized, double-check the IP-addresses and ports you’ve entered in the Receiver Configuration Tool. Try deactivating your firewall. Check if Jumbo-Frames are activated on your network card (needed for IZT/narda receivers).

If you have multiple receivers in your configuration, delete them and add them again one-by-one.

There may be filter settings preventing the results from appearing. To solve this, click <Clear filter> on the toolbar and increase the frequency/time range to the maximum. If frequency information was missing in the signal, your results may be stored with frequency = 0 Hz. Also, old results will by default be automatically deleted after one week from the database (this setting can be changed in application settings). If your hard disk is almost full, your oldest data will also be automatically deleted.

To add tasks to the task overview, you must have a mission which is active. The new task is then added to the mission. Switch to the mission view and check the status of the missions or create a new active mission.

Check in the Task Activity view if there are any triggers and/or started/dropped actions for your task. Use the task-based filter in the <Emissions> view to interactively monitor if there are any live emissions which fit your task trigger.

If a mission or task has changed, they won’t be reloaded/updated automatically in a task-based filter. You have to manually update using the <Reload Missions/Tasks> button.

An Automatic Wideband Monitoring mission is probably currently active in your system. You can check this in the Missions view. After you activate the mission, wideband classification switches into continuous mode. Therefore, snapshot classification is not available. After you deactivate your active mission, the <Classify> button will appear automatically.

Since it is an offline mission, the software has to store narrowband recordings in order to perform recognition & decoding. The files are deleted afterwards (because recording action was not selected in a task), but the recording information stays visible in the database.

To do this, it is necessary to open and modify the prolang.cfg file in the installation folder with a text editor. Valid entries are ”de“ for German and “en“ for English. go2MONITOR must be restarted after the change.

The integrated map material is based on OpenStreetMap (OSM). It is possible to use your own maps. You can specify a map source and server in the settings (see section User Interface Settings).

If there are problems in starting go2MONITOR when no LAN is activated, add the Microsoft Loopback Adapter.

• In the Device Manager, select <Add legacy hardware>

• In the Add Hardware wizard, select <Install the hardware that I manually select from alist (Advanced)>

• In the Common hardware types list, click <Network adapters> and then click <Next>

• In the Manufacturer list, click <Microsoft>

• In the Network Adapter list, click <Microsoft Loopback Adapter> and then click <Next>twice.

• If a message about driver signing appears, click <Continue Anyway>.

• In the Completing the Add Hardware Wizard dialog box, click <Finish>, then click <OK>

You will need go2DECODE or AnalysisSuite to create your modems and decoders. From there, you should save your modem as a *.ver file and your decoder as *.pkg file in the common modems directory for all PROCITEC applications (see below for exact location).

go2MONITOR will automatically recognize that there are new files in this directory and add the corresponding modems and decoders to the system. Similarly, if you want to delete or change modems or decoders, just delete or change the corresponding files from the common modems directory. All changes will be applied automatically. Some decoders may need additional files, e.g. custom alphabets. These files have to be copied to the common modems directory, and will be applied automatically, just as decoders.

The location of the common modems directory is:

• WindowsR

%USERPROFILE%\procitec\common\modems

• LinuxR

$HOME/procitec/common/modems

Some modems are not suitable for automatic modem recognition, so they will be deactivated if you are in search mode. Which modems are suitable for automatic search can be seen in the Auto-recognition column in the Modem List Editor Usage.

Also, if a modem list contains more than 200 modems, all modem will be disabled and appropriate message will be displayed indicating that you have to select a shorter modem list.

Click <Perspective> on the toolbar and select the Default perspective.

You will find log files in the <USER_DIR>/log directory. Simply compress all files you find in that directory and send them to support. It would also help if you could report the exact time when the problem occurred

and the steps to reproduce it.

The location of the <USER_DIR> is:

• WindowsR

%USERPROFILE%\procitec\go2monitor x.y

• LinuxR

$HOME/procitec/go2monitor x.y

The integrated map material is based on OpenStreetMap (OSM). It is possible to use your own maps. You can specify a map source and server in the settings (see User Interface Settings). Available map source types are Local Data, OpenStreetMaps (OSM) and ESRI/ArcGIS. The Local Map data is shipped with the product and cannot be modified yet.

For OSM and ArcGIS you need to specifiy a server URL. This can be a remote, on-premise or local host server. If you like to use your own local map data or a custom server, please contact us for further information.

The channel opens und shows the message “Waiting for a free channel. . . ”. When a channel in the system becomes free, the resources will be occupied automatically and the channel starts to work.

This limit can be set independent from the number of channels in the system by license for the operator workplaces.

The administrator has the control over the wideband inputs. This means that he can also “specify frequency ranges for use” or decide what should be processed in the system.

If the administrator turns off a wideband input, the operator couldn’t work with this. He looks in his channels that “frequency or bandwidth is out of range”. The operator gets a hint in the interface if the administrator changes something at the wideband inputs (yellow information box).

Yes, it is possible with the license option Narrowband Receiver Control Option (NRC).

The operator has access to all wideband inputs in his narrowband channels. However, he can only monitor/ see one input in his wideband spectrogram. Even if he switches to a different wideband input, his work on narrowband channels from another wideband input operates further. This was implemented for performance reasons in order to reduce the network load in large systems.

If decoding is not possible as the decoder cannot automatically detect the polarity of the signal, then we recommend changing the primary demodulator from USB (off) to LSB.

Define a new signal source in the menu <Extras><Options> (e.g. go2MONITOR CH1). For a connection to go2MONITOR channel #1, connect to port 36600; for channel #2, connect to port 36601, etc.

Open the “sda.conf” file in the user folder and set the value of ShowToolTips to 0.

Example:

sda.exe –conf C:\Temp\my_sda.conf

As default, SDA looks for its configuration file “sda.conf” first in the user folder and then in the installation folder. On the command line you can parameterize the configuration which will be loaded (in the example C:\Temp\my_sda.conf).

To do this, it is necessary to create the file “prolang.cfg” in the user folder and then modify it with a text editor. Valid entries are “de” for German and “en” for English. go2DECODE must be restarted after the change.

The license file “default.maw” is stored and searched for in the user folder.

(.../<user>/procitec/go2decode <version>)

Alternatively, it can be stored in the installation folder.

Modems and modem lists can be added via drag-and-drop to go2DECODE. This also applies to signal recordings (e.g. WAV files) in DANA. It is possible to select multiple files at the same time.

If go2DECODE is parameterized with a very long modem list and / or fed with a broadband input signal, it takes a long time until the automatic detection is finished. go2DECODE seems to stuck, but it continues to run in the background. It is recommended not to use a broadband input signal, but to use only the necessary narrowband input signal. Furthermore, the modem list should be limited to possible modems.

There are several possible reasons:

• Nominal frequency or search range is not set correctly

• Signal quality is too bad

• The modem is not included in the modem list, not selected or not active

• The mode is set to production: only the selected modem is active. Other modems in the
list are ignored.

The displayed modems in the result display are not all installed or existing modems and doesn’t represent the complete modem database. Modems can be added via <Modem><New Modem>.

Results produced are stored by go2DECODE in the user folder under

“.../<user>/procitec/go2decode <version>/mem_prod”

in addition to the output in the user interface.

Through DANA, both complex and real live audio signals can be used, e.g. to integrate a WebSDR. To do this, the audio output must be redirected to an audio input in the operating system. Under WindowsR, e.g. “Virtual Audio Cable” can be used. In DANA, the source must be switched to sound, selecting either real or complex (IQ). The audio input is selected under <Extras><Sound Configuration>.

“.ver” – Single Modem

“.cmf” – List of modems (complete modem definitions)

“.mlst” – List of modems (only modem references)

“_dec.pkg” – pyDDL decoder package

“_dec.py” – pyDDL Decoder Python source file

“.wav” – signal file, real or complex

“.para” – signal parameters for wav files (like receive frequency)

If signal files have been lossy compressed (e.g. mp3), important signal information (e.g. phase) which are necessary for demodulation are usually lost. This difference is not acoustically audible but prevents decoding for most modems. Only simple modems, e.g. morse, are rather uncritical in this regard. Signal files, even after reconversion of mp3 or similar, are therefore mostly unusable.

A complex signal consists of 2 real channels (I and Q components). The spectrum of a complex signal generally differs at positive and negative frequencies. Real signals are single-channel. Since the spectrum of a real signal is symmetric around 0 Hz, the redundant negative frequencies are usually not displayed in spectrum representations. In DANA, files with 2 channels are played by default as a real signal and only the first channel is used. In order to play the file in as a complex signal, you have to right-click on the path of the corresponding file in the file list and set the mode to IQ. The signal must be selected and played at the same time.

The values of all spinboxes can be changed using the mouse wheel. The digit marked by the cursor changes. Furthermore, the unit can be changed by right-clicking on the spinbox and previously entered values are displayed again.

The font size can be adjusted for high-resolution monitors as follows:

• By setting the parameter “--font-size <XX>” at startup via the command line. The font size is only changed for the current call.

• As a permanent entry in the file “sda.conf” in the user directory. The key <add key="GlobalFontSize" value="XX"/> under the entry <appSettings> has to be updated or created.

Problem:
Why is the modem not found or not decoded?

Solution:

There are several possible reasons:

• Nominal frequency or search range is not set correctly
• Signal quality is too bad
• The modem is not included in the modem list, not selected or not active
• The mode is set to production: only the selected modem is active. Other modems in the list are ignored.

Latest update 2023-07 helpdesk