My simpleRTK2B (latest firmware 1.12) is connected via USB to an Android smartphone running the SW Maps app. Communication works. However, although I can connect to an NTRIP server (connection is not refused) with exactly the same parameters as successfully used in u-blox u-center, there is 0B/s transferred data. Changing the smartphone language to English – as recommended by another user – did not work.
1. Do you mark the checkbox, “send NMEA GGA to NTRIP Caster” ? if no, select the checkbox.
2. Do you have enabled High Precision NMEA? UBX-CFG-NMEA? If yes try to disable.
1. checkbox is marked.
2. High precision NMEA is disabled.
Maybe I would give a try to another NTRIP client in android to confirm that if the problem is coming from SWMaps or from the configuration of the board. You can try Lebefure: https://play.google.com/store/apps/details?id=com.lefebure.ntripclient&hl=de_CH
With the Lefebure NTRIP Client app and using my credentials I can successfully connect to my NTRIP service provider, receive the list of mount points, choose one, and get pseudo-corrections (if I set a pseudo lat/lon within the app). However, the Lefebure app apparently cannot connect via USB to my simpleRTK2B device.
Hi cosinus, then it seems it has to do with sw maps, did you try open a ticket with them?
@Cosinus Did you sort out the problem with SWMaps.
If not, it might help to know that Lefebure CAN connect via USB to simpleRTK2B.indirectly,
I use the app “USB Serial Port to TCP/IP Socket, UDP” by T2 TECHHUB from the Play Store on my Android phone to bridge the USB to a local port on my phone then set Lefebure to use that port with “External via TCP/IP (Beta)” in the receiver settings.
NB There are probably other apps which do the same thing, but make sure you choose one which is happy with binary not just ASCII.
@AndrewRL: thanks for the info about connecting Lefebure to simpleRTK2B!
I have to apologize: user Mauro Bettella had already posted the answer and SW Maps indeed works with simpleRTK2B including caster corrections. It is mandatory to set the phone language to ‘English’. Stupid thing, I thought I had done so but the setting was ‘English (German)’, I have no idea what that strange setting means? If I ‘really’ set ‘English’ the SW Maps works as expected.
The point is number format e.g., the number between latitude 51 and 52 is spelt as ‘51.5’ in English and as ‘51,5’ in many other European languages. SW Maps knows this and displays numbers correctly for the chosen language. However, the caster communication ONLY works if the language is set to ‘English’. I have contacted the software developers from SW Maps and asked them to eventually modify their code to make it more convenient for ‘non-English’ users.
@Cosinus OK thanks. Glad you already sorted it.