XGRIDS Lixel K1, K2 & L2 Pro RTK Setup: LixelGO NTRIP
Connect XGRIDS Lixel K1, K2 and L2 Pro to RTKdata in LixelGO: Custom NTRIP, AUTO mountpoint, mobile data in Quick Connect and datum settings in LixelStudio.
This page covers the XGRIDS Lixel RTK setup with RTKdata NTRIP corrections for three handheld SLAM scanners: the Lixel K1 (LixelKity K1), the Lixel K2 and the Lixel L2 Pro. The K2 has the RTK module built in, the K1 uses the K1 RTK module on an RTK bracket, and the L2 Pro takes either the Standard RTK or the Survey RTK module. All three are set up in the LixelGO app on iOS or Android, and the scans are georeferenced in LixelStudio on Windows.
For RTKdata you create one NTRIP profile in LixelGO with Type set to Custom. The scanners have no cellular modem, so the corrections come through your phone's mobile data or a Wi-Fi network with internet access. The Lixel L3 has a separate guide: XGRIDS Lixel L3.
Enter these values in LixelGO under RTK Settings > Account Settings. Select the tab for your region and use the server closest to your work area. All three servers share the same base station network; the difference is routing latency. See NTRIP Server Settings.
Host (domain):
rtk.rtkdata.comin Host (preferred)Host (IP fallback):
13.56.117.10in Host, if LixelGO rejects the host name or the host name does not connectPort:
2101in PortUsername / Password: From RTK Credentials in your account dashboard in Username and Password, not your website login
Mountpoint (ALL CAPS):
AUTO(recommended) in Mountpoint, orAUTO_WGS84,AUTO_ITRF2020,AUTO_ITRF2014
Host (domain):
eu.rtkdata.comin Host (preferred)Host (IP fallback):
3.73.41.96in Host, if LixelGO rejects the host name or the host name does not connectPort:
2101in PortUsername / Password: From RTK Credentials in your account dashboard in Username and Password, not your website login
Mountpoint (ALL CAPS):
AUTO(recommended) in Mountpoint, orAUTO_WGS84,AUTO_ITRF2020,AUTO_ITRF2014
Host (domain):
aus.rtkdata.comin Host (preferred)Host (IP fallback):
54.206.56.130in Host, if LixelGO rejects the host name or the host name does not connectPort:
2101in PortUsername / Password: From RTK Credentials in your account dashboard in Username and Password, not your website login
Mountpoint (ALL CAPS):
AUTO(recommended) in Mountpoint, orAUTO_WGS84,AUTO_ITRF2020,AUTO_ITRF2014
All LixelGO values at a glance:
Type
Custom
Ellipsoid
WGS84 (in China: CGCS2000)
Host, North America
rtk.rtkdata.com, IP fallback 13.56.117.10
Host, Europe
eu.rtkdata.com, IP fallback 3.73.41.96
Host, Australia
aus.rtkdata.com, IP fallback 54.206.56.130
Port
2101
Username
From RTK Credentials in your account dashboard. It starts with rtk and is not your website login.
Password
From RTK Credentials, not your website password
No password required
Leave unticked
Mountpoint
AUTO in capital letters. Alternatives: AUTO_ITRF2020, AUTO_ITRF2014, AUTO_WGS84
Host is a text field and takes the host name, so enter the host name first. Use the IP fallback of the same region if LixelGO rejects the host name, for example with Invalid host or port or Invalid IP service address, or if NTRIP stays red and the mountpoint list does not load with the host name. LixelGO has no GGA switch: give the scanner a position outdoors before you connect, as described in the steps below.
What do you need before connecting a Lixel K1, K2 or L2 Pro?
To connect a Lixel K1, K2 or L2 Pro to RTKdata you need the scanner with its RTK hardware, a current LixelGO app on a phone with internet access, scanner firmware that supports RTK in your connection mode, active RTKdata NTRIP credentials and RTKdata coverage at your site.
Scanner with RTK hardware. Lixel K2: nothing to mount, RTK is built in. Lixel K1: the RTK module on the RTK bracket, mounted on the scanner (the tilted bracket needs firmware 1.2.3 or later). Lixel L2 Pro: the Standard RTK or Survey RTK module with its bracket.
LixelGO from the App Store (iOS) or Google Play (Android, publisher XGRIDS LIMITED), version 2.1.2 in September 2026. The K2 needs LixelGO 2.0.1 or later. Do not install the Android APK from the XGRIDS download page: in September 2026 it was still LixelGO 1.2.5.
Phone with Android 12 or later, or an iPhone 12 or later. XGRIDS does not support phones with 4 GB of RAM or less and recommends at least 8 GB for the K2.
Internet on the phone. Mobile data for the default Quick Connect Mode, see the next section.
RTKdata account with active RTK credentials (username starts with
rtk).Coverage at your site. Check the RTKdata coverage map before the job.
LixelStudio 4.x on a Windows 10 or 11 PC with an NVIDIA RTX 20 series or newer graphics card, for georeferencing.
App and firmware versions
RTK in Quick Connect Mode needs scanner firmware 3.1.1 or later. XGRIDS states "Firmware 3.1.1+: RTK and activation supported", so update to 3.1.1 or later first or use Hotspot Mode. Update through Settings > Firmware Upgrade in LixelGO, one step at a time: XGRIDS does not support skipping versions.
Lixel K1
3.2.1
Update path: below 1.2.4 → 1.2.4 → 2.4.1 → 3.0.2 → 3.1.1 → 3.2.1
Lixel K2
3.3.2
Needs LixelGO 2.0.1 or later
Lixel L2 Pro
3.2.1
Update path: below 2.4.1 → 2.4.1 → 3.0.2 → 3.1.1 → 3.2.1
The labels on this page come from the English LixelGO interface. LixelGO switches its language automatically, so on a phone set to another language the labels differ.
Current app version when this page was written: LixelGO 2.1.2 (September 2026).
Where does the Lixel get internet for RTK corrections?
A Lixel K1, K2 or L2 Pro gets its RTKdata corrections through your phone or through a Wi-Fi network with internet access, because the scanners have no cellular modem. For the L2 Pro, XGRIDS states that the scanner "does not have a built-in 4G module".
Quick Connect Mode (default since LixelGO 1.3.0)
The phone joins the scanner's Wi-Fi, and LixelGO carries the NTRIP connection over the phone's mobile data
Your phone has a SIM with mobile data
Hotspot Mode
The scanner joins your phone's hotspot
RTK in Quick Connect Mode is not available, for example on firmware below 3.1.1
Bridge Mode
Scanner and phone share a Wi-Fi network that has internet access
Your phone or tablet has no mobile data, but a site Wi-Fi or router with internet is available
Quick Connect Mode, the default since LixelGO 1.3.0, needs the phone's mobile data. Turn mobile data on before you connect. A Wi-Fi-only tablet, a phone without a SIM or a phone with mobile data switched off gets no corrections in this mode. Use Bridge Mode with a Wi-Fi network that has internet access instead, or Hotspot Mode if the phone has mobile data but Quick Connect Mode is not available.
Hotspot Mode
In LixelGO tap + (Add New Device), connect to the scanner over Bluetooth, enter the name and password of your phone's hotspot, tap Configure, then Finish (some app versions show Done). On iOS the K2 documentation calls this mode Direct Connect Mode.
XGRIDS' checklist for a hotspot that the scanner accepts:
Location, Hotspot and Bluetooth are on at the phone.
Hide Network is off in the hotspot settings.
No VPN is active.
The hotspot password uses only letters and numbers.
If the connection still fails, switch the hotspot to the 5 GHz band.
iPhone: the iPhone name, which becomes the hotspot name, uses only English letters without spaces or special characters. Turn on Allow Others to Join, set compatibility to maximum, and stay on the Personal Hotspot page until Data Connection Successful! appears.
Bridge Mode
Tap +, select Bridge Mode, connect to the scanner over Bluetooth, then enter the name and password of the Wi-Fi network, not of a phone hotspot. The network must have internet access, otherwise NTRIP cannot connect.
The field IP in Step 3: Confirm device and phone share the same network is the scanner's local IP address. LixelGO fills it in itself. It is not the caster address: RTKdata only goes into RTK Settings > Host.
Keep the corrections running on the phone
In Quick Connect Mode, keep LixelGO open while you scan. XGRIDS notes that the scanner loses the fixed solution when the app is closed.
On Android, LixelGO asks for background permissions. Enable Allow background activity for the battery, allow background data under Data Usage, and turn battery optimisation off for LixelGO. Otherwise Android can stop the correction stream when the screen is off.
How does the XGRIDS Lixel RTK setup work in LixelGO RTK Settings?
In LixelGO you open RTK Settings from the satellite tile on the device page or from Settings > RTK Settings, set GNSS Mode to RTK under Advanced Settings, and enter the RTKdata values under Account Settings with Type set to Custom: Host rtk.rtkdata.com (North America), eu.rtkdata.com (Europe) or aus.rtkdata.com (Australia), Port 2101, Mountpoint AUTO, and the username and password from RTK Credentials in your RTKdata dashboard.
Connect the scanner and open RTK Settings
Hold the power button for about 4 seconds until the LED turns green.
Connect LixelGO to the scanner in the mode you chose above.
On the device page, tap the satellite tile. It shows the satellite count and the status, 0 and None at first. You can also open Settings > RTK Settings.
RTK Settings has two tabs: Account Settings and Advanced Settings.
Older app versions name the path Setting > RTK. If you see that, update LixelGO first.
Set GNSS Mode in Advanced Settings
Check that GNSS Mode is RTK. Leave everything else in Advanced Settings at the defaults: the XGRIDS K1 FAQ says no changes are needed there ("Keep the default disabled state"). Older app versions show RTK Type with XGRIDS RTK and Other Brand: keep XGRIDS RTK.
Set GNSS Mode to RTK. Leave Satellite System on Select all.
Set GNSS Mode to RTK.
Set RTK Type to the module that is mounted and confirm with Set: Standard RTK for the Standard RTK module (small antenna), Survey RTK for the Survey Grade RTK module.
If your LixelGO version also shows Enable Status and a mount type for the Survey Grade module, the XGRIDS FAQ asks you to set Enable Status to On and the mount type to Max RTK, and to set Enable Status back to Close when you change to the Standard RTK module (small antenna). LixelGO keeps this setting for the next use.
On a DJI M300 or M350 the L2 Pro uses GNSS Mode DJI with RTK Type Aerial RTK. RTK then comes from the drone, not from the LixelGO NTRIP profile on this page. For the drone's own RTKdata connection, see DJI Matrice 300 / 350 / M30T.
Restart the scanner after every change of GNSS Mode. LixelGO shows RTK mode: Changes apply after restart. In PPK or DJI mode LixelGO does not log in to NTRIP.
Enter your RTKdata account in Account Settings
Type: Custom. Qianxun SI and China Mobile are services for mainland China.
Ellipsoid: WGS84, in China CGCS2000. Do not choose OTHER. The ellipsoid section below explains why.
Host: the host name for your region,
rtk.rtkdata.com(North America),eu.rtkdata.com(Europe) oraus.rtkdata.com(Australia), withouthttp://and without a port. Use the IP fallback from the region tabs at the top of this page if LixelGO rejects the host name, or if NTRIP stays red and the mountpoint list does not load with the host name.Port:
2101. Keep this port: LixelGO 1.2.5 for Android switches to an encrypted (TLS) connection on port 2102.Username and Password: from RTK Credentials in your account dashboard. Tap the eye icon to show the password and check it.
No password required: leave unticked.
Mountpoint: type
AUTOin capital letters, or tap the button next to the field and pick AUTO from the list. The list can show more entries thanAUTO,AUTO_ITRF2020,AUTO_ITRF2014andAUTO_WGS84: pickAUTOunless your project needs one of the global frames.
Save the profile
Tap the disk icon at the top right. The Save Configuration dialog asks Save ntrip info to configuration?
Pick a slot, for example Configuration 1, and tap Save.
Rename the profile with the pencil icon, for example to "RTKdata Europe".
Saved profiles appear in the drop-down at the top of the page, and LixelGO keeps up to five. After the first setup the scanner logs in with the saved profile automatically. If it logged in before the scanner had a position, for example indoors, tap Disconnect, then tap Connect outdoors once the satellite tile shows Single.
Connect and wait for Fixed
Outdoors under open sky, wait until the satellite tile shows satellites and Single.
Tap Connect.
The indicators RTK and NTRIP turn green, and the status moves from Single to Float (Floating in some app versions) to Fixed.
Connect starts an NTRIP session and Disconnect ends it.
How do you know the scanner has a usable RTK fix?
A Lixel K1, K2 or L2 Pro has a usable RTK fix from RTKdata when LixelGO shows the RTK and NTRIP indicators green, the status reads Fixed, and the satellite tile counts more than 10 satellites.
RTK green means the RTK module is detected. NTRIP green means the NTRIP connection is up.
Green on both is not the same as usable. Check Fixed and the satellite count every time before you start. LixelStudio later filters RTK points by satellite count (preset to 10), HDOP and tilt angle.
Lixel K2: XGRIDS documents the device light for device states, such as "Steady green: Standby mode" and "Slow green flash: Scanning mode". Do not use a light as the fix indicator on the K2: only Fixed in LixelGO counts.
Lixel K1 and L2 Pro: the LED on the RTK module shows red (not connected), blue (connected, no fix) or green (fixed). The LixelGO status stays the reference.
Scanning with RTK
Tap GO on the device page. Ready to scan shows Project Name, Mount type (Handheld) and GNSS Mode (RTK). Start recording only when LixelGO shows Fixed, not None, Single or Float.
Once fixed, walk at least 10 m in the fix before you head into the main route.
Keep sections without a fix short: under 50 m on the K1 and K2, under 100 m on the L2 Pro.
Collect more than 100 valid RTK points. With fewer than 20 the transformation in LixelStudio fails, and between 20 and 100 the accuracy drops.
Tilt: at most 15° for the K2 in RTK mode. The XGRIDS precautions page gives 10°, so hold the K2 as upright as possible. At most 20° for the K1 and L2 Pro.
Do not switch the NTRIP account during a scan. LixelGO warns Switching NTRIP accounts during scan affects accuracy.
After the job, tap Disconnect in RTK Settings.
Which ellipsoid and target CRS should you use with AUTO?
With the RTKdata AUTO mountpoint you set Ellipsoid to WGS84 in LixelGO, and in LixelStudio you keep Source CRS on WGS84 and select the projected system of your regional datum by EPSG code as Target CRS, without a WGS84-to-national datum transformation.
AUTO delivers the corrections in the regional datum for your position, for example NAD83(2011) in the USA, NAD83(CSRS)v7 in Canada, ETRS89 (realization ETRF2000) in Europe and GDA2020 in Australia. For regions without a listed regional datum, AUTO falls back to WGS84(G2139) at the mid-year epoch. The full list per country is in Coordinate Systems & Datums. In LixelGO, WGS84 is the name of the ellipsoid setting: the coordinates still arrive in your regional datum. ETRS89, NAD83 and GDA2020 use the GRS80 ellipsoid, which is nearly identical to WGS84.
WGS84 in LixelGO enables the real-time output in absolute coordinates and, on the L2 Pro, Measure Point. Do not use OTHER.
After changing Ellipsoid, wait about five minutes before you scan. XGRIDS: "Changing the RTK coordinate system takes about 5 minutes to apply".
In China
AUTOdelivers CGCS2000, so select CGCS2000 there.The real-time output of the scanner uses "WGS84: UTM 3-degree zone", not a standard 6-degree UTM zone. For GIS and CAD, use the LixelStudio output in your EPSG system.
Use
AUTO_WGS84(WGS84(G2139) at the mid-year epoch) only when the deliverable must be in a global frame, for example to combine it with data in WGS84.AUTO_ITRF2020andAUTO_ITRF2014deliver ITRF at the current epoch. With these global mountpoints the zero-parameter file below no longer applies, and reaching a national system needs a real datum transformation. Keep one mountpoint per project and per Map Fusion.
The datum and target system choices that apply to every SLAM scanner are collected in Georeference SLAM Point Clouds with RTK.
Georeference the scan in LixelStudio
Steps for LixelStudio 4.0.1.6:
Under Project Processing, leave High-Precision Optimization off. It is mutually exclusive with Coordinate Transformation.
Open Coordinate Transformation and tick GNSS, with the RTK module as the data source.
Open Details next to Source CRS and check that it shows WGS84, as in LixelGO, and not CGCS2000.
Under Target CRS, click Select and pick the projected system of your regional datum by EPSG code, for example 25832 (ETRS89 / UTM zone 32N) or 6346 (NAD83(2011) / UTM zone 17N).
If LixelStudio asks for seven parameters, load a text file that contains
0 0 0 0 0 0 1. XGRIDS uses the same file in its RTK Setting Guide for WGS84 to JGD2011 and KGD2002. Do not enter official WGS84-to-national parameters:AUTOhas already delivered the regional datum, and they would shift the data a second time.Heights are ellipsoidal. For heights above sea level, set a fixed Height anomaly (Elevation Anomaly in the XGRIDS manual) for small sites or a custom coordinate system with a geoid. See Understanding Heights.
Click Start, then check the result at one known control point. A consistent offset of 50 cm to 1 m points to a datum mismatch, not an accuracy problem, see Coordinate Systems & Datums.
If the control point shows a consistent offset, open Details next to Source CRS again and check that it shows WGS84. If seven parameters were requested, check that they come from the
0 0 0 0 0 0 1file and not from WGS84-to-national parameters. Process again, and if the offset stays, send the control point coordinates and the EPSG code of your Target CRS to support@rtkdata.com.
Set the target system before you click Start: the coordinate system is applied during processing, not at export.
Accuracy Check expects a control point file with "Point Name, Easting, Northing, Ellipsoidal Height". Enter ellipsoidal heights, not heights above sea level, in the same coordinate system as the GNSS target.
Map Fusion with RTK needs valid RTK data in every project, each project under 20 minutes, and data from the same device type.
LixelStudio 4.x processes only data recorded with firmware 2.4.1 or later.
Why does NTRIP stay red while the mountpoint list loads?
In LixelGO, RTK green with NTRIP red means the RTK module is detected but the NTRIP connection to RTKdata is not up. Check first whether the phone has internet on the NTRIP path, then the RTKdata credentials, then the mountpoint. The RTKdata mountpoint list loads without a login, so seeing AUTO in LixelGO proves neither your credentials nor a running correction stream.
The RTKdata sourcetable answers without a login (checked on 25 September 2026). XGRIDS' advice for RTK green and NTRIP red is: "Check whether the phone has internet access, or try switching to a different CORS account". Work through it in this order:
Tap Disconnect.
Check the internet path: mobile data on in Quick Connect Mode, internet on the hotspot in Hotspot Mode, internet on the Wi-Fi in Bridge Mode.
Retype Username and Password from RTK Credentials, without spaces and without automatic capitals.
Check that Mountpoint reads
AUTOexactly, in capital letters.If the mountpoint list does not load with the host name, enter the IP fallback of your region as Host (
13.56.117.10North America,3.73.41.96Europe,54.206.56.130Australia), keep Port2101and MountpointAUTO, and restart LixelGO before you tap Connect.Outdoors, wait for satellites and Single, then tap Connect again.
If another device uses the same credentials at the same time, disconnect it or add a data stream.
Troubleshooting
RTK green, NTRIP red
No internet on the NTRIP path, then wrong credentials, then wrong mountpoint
Follow the checklist in the previous section, in that order. If the mountpoint list does not load, use the IP fallback of your region.
RTK red, NTRIP green
RTK module not detected (Quick Connect Mode)
K1 and L2 Pro: power off, reseat the RTK module, restart. K2: power the scanner off and on and reconnect LixelGO. If RTK stays red, contact your XGRIDS dealer, because the module is built in.
RTK and NTRIP both red
RTK module not seated
K1 and L2 Pro: power off, reseat the module, restart. Then check the internet path.
Both green, but 0 satellites
RTK hardware fault
Cross-test with another RTK module (K1, L2 Pro) before you conclude that the scanner is at fault.
NTRIP green, status stays Single or Float
No position from the scanner at the caster yet, then blocked sky, too few satellites or a tilted scanner
Check that the satellite tile shows satellites and Single, then tap Disconnect and Connect: AUTO needs the position to pick a base station. Then move to open sky, hold the scanner upright, and wait for more than 10 satellites.
RTK password incorrect
Wrong username or password
Retype both from RTK Credentials. The username starts with rtk and is not your website login.
LixelGO says the RTK mode does not support NTRIP login
GNSS Mode is PPK or DJI
Set GNSS Mode to RTK and restart the scanner.
Invalid host or port or Invalid IP service address
Host entry not accepted
Check the host name for typos, with no http:// and no port in Host, and Port 2101. If the message stays, enter the IP fallback of your region as Host: 13.56.117.10 (North America), 3.73.41.96 (Europe) or 54.206.56.130 (Australia). Keep Port 2101 and Mountpoint AUTO.
Fix is lost when the phone screen turns off
Android stops LixelGO in the background
Allow background activity and background data, turn battery optimisation off, keep LixelGO open.
Scanner does not join the phone hotspot
Hotspot settings
Apply the hotspot checklist above.
Bridge Mode shows an IP like X.X.1.X
Scanner on the wrong subnet
Restart the phone's hotspot or the phone, then try again.
Connection fails after a network change or a new Host entry
LixelGO for Android can keep the address it looked up for the host until the app restarts
Tap Disconnect and Connect, or restart LixelGO.
Corrections drop when a second device connects
Two devices on one set of credentials
One data stream allows one connection. See Account & Credentials.
For connection problems that are not specific to LixelGO, for example a login that succeeds without corrections, see Fix NTRIP Connection Issues.
Frequently asked questions
Does the XGRIDS Lixel K2 have built-in RTK?
Yes. XGRIDS lists "The RTK module is now built-in" among the K2's upgrades over the K1, so there is no module to mount. The K2 still needs an NTRIP correction service such as RTKdata and an internet connection through your phone or a Wi-Fi network.
Can I use a third-party NTRIP service like RTKdata in LixelGO?
Yes. Choose Type Custom in RTK Settings > Account Settings and enter host, port, username, password and mountpoint. XGRIDS lists "standard-format custom RTK" as supported next to its preset services for mainland China, and RTKdata streams RTCM 3.2 with MSM messages, see Correction format.
Does LixelGO need mobile data on my phone for RTK?
In Quick Connect Mode, the default, yes: the phone sits in the scanner's Wi-Fi and LixelGO carries the RTKdata corrections over the phone's mobile data. Hotspot Mode also runs on the phone's mobile data. Without mobile data, use Bridge Mode with a Wi-Fi network that has internet access, because the scanners have no cellular modem of their own.
Which Ellipsoid should I choose in LixelGO outside China?
Choose WGS84. It enables the real-time output in absolute coordinates, and with the RTKdata AUTO mountpoint the corrections still arrive in your regional datum. Do not choose OTHER, and wait about five minutes after a change.
Why is my Lixel scan not georeferenced in LixelStudio?
The most common causes are High-Precision Optimization switched on (it excludes Coordinate Transformation), too few valid RTK points (fewer than 20 fails, more than 100 are needed for full accuracy), no Target CRS set before processing, and data from firmware older than 2.4.1 in LixelStudio 4.x. Start scans only at Fixed and walk at least 10 m in the fix.
Related Guides
LiDAR Scanners & Mobile Mapping: all scanner guides and the shared RTKdata connection settings
XGRIDS Lixel L3: separate RTK setup guide for the Lixel L3
NTRIP Server Settings: regional hosts, IP fallbacks, port 2101 and the AUTO mountpoints
NTRIP & GGA Essentials: why
AUTOneeds your position and which correction format RTKdata streamsCoordinate Systems & Datums: which regional datum
AUTOdelivers in each countryUnderstanding Heights: ellipsoidal and orthometric heights, and when a geoid model is needed
Account & Credentials: where to find your RTK credentials and how many devices can connect at once
Fix NTRIP Connection Issues: what to check when the login works but no corrections arrive
Coverage Map: check RTKdata coverage at your site before the job
Georeference SLAM Point Clouds with RTK: datum and target system choices for every SLAM scanner
DJI Matrice 300 / 350 / M30T: the drone's own RTKdata setup when the L2 Pro flies on an M300 or M350
Quick reference
LixelGO 2.1.2 from the App Store or Google Play, scanner firmware updated (K1 and L2 Pro 3.2.1, K2 3.3.2), mobile data on for Quick Connect Mode.
Settings > RTK Settings > Advanced Settings: GNSS Mode RTK (L2 Pro: RTK Type matching the module), then restart the scanner.
Account Settings: Type Custom, Ellipsoid WGS84, Host
rtk.rtkdata.com,eu.rtkdata.comoraus.rtkdata.com(IP fallback13.56.117.10,3.73.41.96or54.206.56.130), Port2101, Username and Password from RTK Credentials, MountpointAUTO, then Save Configuration.Outdoors, wait for Single, tap Connect, and scan only with RTK and NTRIP green and Fixed.
LixelStudio: High-Precision Optimization off, Coordinate Transformation > GNSS, Source CRS WGS84, Target CRS EPSG system of your regional datum,
0 0 0 0 0 0 1if seven parameters are requested.
Last updated
Was this helpful?