Welcome to the setup guide for the GP-Probe DIN L1, a sophisticated GNSS interference and anomaly detector. The GP-Probe DIN L1 offers two primary options for data processing: using the cloud-based capabilities of GP-Cloud or the onboard signal processing feature, OSP (Onboard Signal Processing).


Using GP-Cloud not only provides access to extensive data analysis and storage, but it also enables users to monitor multiple connected devices simultaneously, making it ideal for users needing advanced analytics, historical data comparison, and remote monitoring across several locations. Alternatively, the OSP option processes data directly on the device, making it ideal for environments with limited or no internet access


Running the GP-Probe DIN L1 is straightforward. Follow these essential steps:

            OR



We recommend watching this introductory video to get started: https://youtu.be/o2Z103R0v-c




 


For a printable version of this manual, please visit:

https://gpspatron.com/gp-probe-din-l1-user-manual/



Before proceeding, review the technical specifications provided in the datasheet:

https://gpspatron.com/gp-probe-din-l1-datasheet/



1. First power-on


The GP-Probe DIN L1 does not have a power button. Simply connect the power cable, and the device will activate. If a GNSS antenna is not connected, an error message will display:

Connecting the antenna resolves this issue, and the probe will show "Connecting" followed by "Offline":


All management of GP-Probe is conducted via an integrated web-based configuration panel.
Learn how to access it here.



It is necessary to install a GNSS antenna and establish a connection to GP-Cloud or activate the Onboard Signal Processing option.




2. GNSS Antenna Installation


Installing the GNSS antenna correctly is crucial for maximizing the performance of your GP-Probe DIN L1. Here are the steps and best practices to ensure optimal antenna setup:

  • Antenna Type: For budget-conscious setups, a simple magnetic GNSS antenna placed on an office windowsill is sufficient. However, for enhanced system efficiency and reliability, investing in a higher-quality antenna and installation is recommended.

  • Minimum Signal-to-Noise Ratio (SNR): Aim to achieve an average SNR greater than 30 dB. This level of signal quality is required for accurate operation of GNSS signal anomaly detection algorithms.

  • Antenna Placement: Install the antenna in a position that provides an unobstructed view of the entire sky.

  • Avoid Industrial Interference: Do not install the antenna near industrial equipment. Machinery and electronic devices can emit interference that might disrupt GNSS signal reception, leading to inaccurate data or false anomalies.

  • Minimize Signal Reflections: Place the antenna away from surfaces that can reflect GNSS signals, such as large metal objects or reflective coatings on buildings. Reflections can cause multipath effects, where the signal bounces off a surface before reaching the antenna, thus distorting the original signal.

  • Avoid Tree Coverage: Be cautious about installing the antenna under tree branches. During windy conditions, the movement of branches can lead to fluctuating satellite signal strengths, potentially triggering false detections by the anomaly detector.

By adhering to these guidelines, you can ensure that your GP-Probe DIN L1 has the best possible conditions for capturing accurate GNSS data, thus enhancing its performance in detecting and analyzing GNSS interference.






3. Connect GP-Probe to GP-Cloud and Configure

Connecting and calibrating your GP-Probe DIN L1 to GP-Cloud involves several key steps:



3.1 GP-Probe Registration in GP-Cloud


Find the GP-Probe ID: Locate the unique identifier for your GP-Probe, which can be found on the instrument's screen or within the Web Configuration Panel:




Log into GP-Cloud using an administrator account:

  • Navigate to the "Probes" menu and click on "Add New Probe".
  • In the popup, choose the probe's model, make up a password (remember it for the next step), and type in the probe's ID:



Detailed registration instructions are available here: https://support.gpspatron.com/en/support/solutions/articles/101000492697-gp-probe-registration-in-gp-cloud





3.2 GP-Probe Connection Configuration


Configure the network settings to connect your GP-Probe to GP-Cloud:

  • Access Configuration Panel: Using a web browser, access the GP-Probe DIN L1 Web Configuration Panel at http://192.168.0.120. Log in with the default credentials: username ‘admin’ and password ‘admin’.
    For more information on how to access the configuration panel, visit this page: https://support.gpspatron.com/en/support/solutions/articles/101000466602-how-to-get-access-to-configuration-panel
  • Network Setup: In the "Connection Config" menu, enter the URL or IP address of your GP-Cloud server instance. If you are using the standard GP-Cloud service, this will typically be gp-cloud.io.
  • API Password: Enter the API password that you created during the probe registration process to authenticate the device with GP-Cloud.
  • Apply: Ensure all settings are correctly entered and save the configuration.

That's it! Your GP-Probe should now be connected and ready to stream data.


You can learn more here How to Сonfigure the GP-Probe's Сonnection to GP-Cloud




3.3 Enabling Data Processing in GP-Cloud


Configure GP-Probe to process data in GP-Cloud:

  • Navigate to the Measurement Config menu.
  • Activate GP-Cloud Processing: Select ‘GP-Cloud’ under the ‘Data Processing’ options to enable cloud-based data processing.
  • Apply Changes.


  • Check Cloud Connectivity: Verify that the device is communicating with GP-Cloud by checking the status on the GP-Cloud dashboard.

 



3.4 Check Data Reception in GP-Cloud


Ensuring that your GP-Probe DIN L1 is transmitting data correctly to GP-Cloud is a crucial step.


  • Log into GP-Cloud: Access your GP-Cloud account to manage and monitor your device's settings.
  • Ensure Device Data Visibility: Navigate to the "Charts" menu, find your probe in the list, and verify that it is not in the 'Offline' status. Check that data on the graphs is updating in real-time.




3.5 GP-Cloud Algorithm Calibration


Note: Only an Administrator has the permissions to change probe settings and calibrate algorithms in the cloud.


When you first activate the GP-Probe in a new location, the status indicators may display "Anomaly" or "Low Position Accuracy." This is typical as the device adjusts to its new environment. To ensure accurate and reliable operation, follow these steps to calibrate the probe:


  • Open the Probe Config Popup: Access the GP-Probe configuration window in the "Charts" section by selecting your probe from the list and clicking the settings icon in the top right corner:


  • Define Traceable GNSS: Specify which GNSS systems (e.g., GPS, Galileo, Beidou, GLONASS) the device should track. It's important to note that BeiDou and GLONASS cannot operate simultaneously.


  • Update Reference Position: You have the option to manually set the Reference Position or use the automatic calculation feature. To do this, click the "RECALCULATE POSITION" button followed by "COPY" to apply the newly calculated coordinates:


  • Select Detection Optimization: Choose between two options based on your setup and needs:
  • False Positive Optimization: Recommended if you are experiencing frequent false alarms due to poor GNSS signal reception conditions.
  • Latency Optimization: Ideal if your antenna is positioned well, away from industrial equipment and with clear sky views. This setting prioritizes quick response times to interference.
  • Reset Calibration: Whenever you relocate the probe, replace the GNSS antenna, or change RF cables, it's necessary to recalibrate the anomaly detection algorithms.
Complete recalibration takes one day. However, improved performance can typically be expected within an hour after recalibration starts.





3.6 Adjust GP-Cloud Detection Thresholds


Adjust the detection thresholds through the Probe Config Popup in the GP-Cloud interface. Proper configuration of these thresholds is crucial for ensuring the GP-Probe DIN L1 operates efficiently under various environmental conditions.


Anomaly Detection Threshold:

  • Set the anomaly detection threshold at 30% for environments with clear sky visibility.  If the antenna is placed on windowsills or in locations where sky visibility is limited, increase the threshold to around 80%. If uncertain about the best setting, start at 50% and adjust based on the anomalies observed in the anomaly graph.


'Low Position Accuracy' Detection Threshold:

  • The 'Low Position Accuracy' event is triggered when the value on the 'Horizontal Position Accuracy' graph exceeds a set limit. A threshold of 15 meters is recommended for antennas installed in locations with unobstructed sky views, as this helps in accurately identifying significant deviations from normal position accuracy.


PPS Offset Detection Threshold:

  • When an external PPS signal source is connected and measurements appear on the 'PPS Offset' chart, set a threshold that matches your specific operational needs. Adjust this threshold based on the typical discrepancies observed to ensure that only significant PPS offset events are flagged.


Interference Detection Threshold:

  • An 'Interference' event is detected when the value on the 'Peak Power' graph surpasses a set limit. To effectively distinguish between normal fluctuations and potential interference, it is advisable to set this threshold approximately 6 dB above the average Peak Power measured over several minutes.




4. Activate Onboard Signal Processing


Activating the onboard signal processing enables the built-in interference and anomaly detection algorithms on the GP-Probe DIN L1, allowing for independent operation without external cloud processing. Follow these detailed steps to configure the onboard signal processing effectively:


4.1 Access the Web Configuration Panel


4.2 Define Traceable GNSS: 

  • Go to the 'Measurement Config > Traceable GNSS'. 
  • Choose the GNSS systems you wish to track, such as GPS, Galileo, BeiDou, or GLONASS. 
  • Click 'Apply' to save these settings.
Please, keep in mind that BeiDou and GLONASS cannot function simultaneously.




4.3 Set Data Processing to Onboard:

  • Still, within the Measurement Config section, scroll down to Data Processing.
  • Select Onboard Signal Processing (OSP) from the options.
  • Click Apply to confirm the change.




4.4 Spectrum Normalisation:

  • Navigate to Status > Measurements in the web configuration panel.
  • Locate the Power Spectrum graph and click on the Spectrum Normalization button. This action will align the spectrum flatness, accounting for any distortions caused by the GNSS antenna and its preamplifier:



4.5 Anomaly Detection Algorithm Calibration:

  • Allow the device to collect data for a minimum of 5 minutes. This duration is crucial to gather enough data for effective calibration.
  • Click on the Calibrate Anomaly button next to the Anomaly graph to initiate the calibration process.



4.6 Setting Reference Position:

  • For calibrating the probe reference position, click on the 'Calculate Reference Position' button next to the Horizontal Position Accuracy (m) graph. 
  • Click Apply to confirm the change:


Alternatively, you can manually set the Reference Position by navigating to Measurement Config > Reference Position section.



4.7 Adjusting Interference Detection Threshold:

  • Next to the Peak Power graph, find a small red arrow. Use this control to adjust the interference detection threshold.
  • We recommend setting this threshold approximately 6 dB above the average Peak Power observed over the last five minutes:



4.8 Adjusting Anomaly Detection Threshold:

  • Use the red slider next to the Anomaly graph to set the anomaly detection threshold.
  • If the GNSS antenna is in a location with clear sky visibility, a threshold of 30% is suggested.
  • For antennas placed on windowsills or where sky visibility is limited, consider setting the threshold higher, around 80%. 
  • If uncertain, start at 50% and adjust based on the number of detected anomalies over a day, or continuously monitor of the anomaly graph for several hours via a connected browser.



4.9 Setting 'Low Position Accuracy' Detection Threshold:

  • For the 'Horizontal Position Accuracy' graph, set the detection threshold for 'Low Position Accuracy' events in meters. We recommend a threshold of 15 meters for antennas with open-sky antenna installation.



4.10 Adjusting 'PPS Offset' Detection Threshold:

  • If an external PPS signal source is connected and these measurements are enabled in Measurement Config, you can observe phase difference measurements in the PPS Offset graph.
  • Set the appropriate threshold for your application to detect PPS Offset events:



After configuring these settings, the GP-Probe should display a 'Normal' status on its screen. If the status indicates otherwise, further adjustments of the detection thresholds may be necessary.




4.11 Monitoring Detected Incidents:


All detected incidents will be listed under 'Status > Detected Events'. Each incident record will include:    

  • Classification (Interference, Anomaly, Low Position Accuracy, PPS Offset)
  • Event time and duration
  • Maximum values during the incident (Central Frequency, Peak Power, Spectral Width, Anomaly Probability, Position Accuracy, PPS Offset)




5. Device Response Configuration upon Event Detection


Configuring how your GP-Probe DIN L1 responds to various events is crucial for effective GNSS interference management and integration with other systems. This section provides an overview of integration methods and specific settings available on the "Output Ports Config" page.


5.1 Integration Methods Overview:

  • GP-Cloud REST API: This API allows external systems to interact with the GP-Cloud, enabling real-time and historical data retrieval.
    Learn more: GP-Cloud REST API Documentation
  • Output Ports: Any of the output ports (GNSS, PPS, or relay) can be configured to respond to specific events. For example, you can set ports to disable upon detecting interference or anomalies, ensuring the integrity and reliability of your GNSS data.
  • Embedded Lua Scripting: This powerful feature allows for custom scripting within the GP-Probe DIN L1. Users can write Lua scripts to automate tasks, handle complex event responses, and integrate with other systems. This provides significant flexibility and customization for advanced users.
  • SNMP Agent: The Simple Network Management Protocol (SNMP) agent enables the GP-Probe DIN L1 to be monitored and managed using standard network management systems. This integration allows for real-time status updates and alerts, ensuring that network administrators can respond promptly to any issues.
  • NO/NC Relay: The Normally Open (NO) and Normally Closed (NC) relay outputs can be configured to switch states in response to specific events. This functionality is useful for triggering external alarms, activating backup systems, or other control tasks based on the detection of interference, anomalies, or hardware errors.


For a comprehensive overview of integration methods, please refer to the full guide at https://support.gpspatron.com/a/solutions/articles/101000495766.


5.2 GNSS Output Port Config:

The GNSS output port can be configured to always remain open, close when the server is unavailable. It is also possible to activate the built-in jammer, which will turn on if the port is closed. This ensures that counterfeit GNSS signals can be reliably blocked:


5.3 GNSS Output Port Disable Rules:

You can configure the GNSS output port to disable upon detecting specific events such as interference, anomaly, low position accuracy, PPS offset, or hardware errors. If the checkboxes are enabled, the GNSS port will be closed when any event is detected. If the 'Jammer is enabled if port is closed' checkbox is active, the built-in GNSS jammer will be enabled to reliably block powerful fake signals. 


5.4 PPS Output Port Disable Rules:

Similar to the GNSS output port, the PPS output port can be set to disable upon detecting any events. This ensures that the PPS output signal is always valid and goes off if any interference, anomaly, or signal quality degradation is detected.


5.5 Relay Port Switching Rules: 

The relay port can be configured to switch states when specific events are detected. This includes reacting to interference, anomalies, low position accuracy, PPS offset, and hardware errors. By setting these rules, you ensure that the relay port responds in a manner that helps mitigate the impact of detected events.


By configuring these settings, you can customize how your GP-Probe DIN L1 responds to various GNSS-related events, enhancing the system's ability to manage and mitigate interference.





Enjoy!