1. If the modem is in the receiver. Most GNSS systems use the 2G mobile data connection. Connection problems are inherent to any mobile network, since 2G technology is old and 3G, 4G and voice connections have priority when the network is overworked. The solution would be to contact the mobile provider to reset the SIM or relay in the area while your GNSS equipment is on. This problem does not manifest when the SIM is in the controller.
2. Connection problems, the base is not loaded and the rover remains in standalone mode. The first step is to reset the receiver (Stonex, South, Trimble) by holding down the power button until activation of the restart sequence on/off/beep, and all LEDS fluctuate/LEDS remain lit.
The second step is to create a new profile (existing profiles are deleted) to connect to ROMPOS via ntrip. At ntrip server/DNS enter rtk.rompos.ro or 93.113.10.123, the port is 2101 and the user and password are retrieved from the app.rompos.ro/rover interface.
After connection the solutions offered in the ROMPOS corrections table should be the following *.
RO_MAX_3.1 recommended solution
RO_VRS_3.1
RO_iMAX_3.1
Nearest_3.1 direct connection to a reference station (< 30km recommended)
Nearest_2.3 recommended for equipment using RTCM 2.3
RO_FKP_3.1
RO_i_MAX_2.3 recommended for equipment using RTCM 2.3
RO_FKP_2.3 recommended for equipment using RTCM 2.3
*Mandatory, the receiver will have to transmit the coordinates of the station point (by NMEA-GGA type message)
NOTE: If you try to activate in a crowded area with 4G/3G signal, try activating in a less crowded area (township, surrounding area, etc.)