RTKlib/постпроцессинг

I’m new here and found some very helpful messages here, thank you !
Unfortunately the “medicine” is not working on my Navilock NL-8002U USB with M8030-KT - it’s strange because it has 3.01 (107888) too, here are the details

17:59:30  $GNTXT,01,01,02,u-blox AG - www.u-blox.com*4E
17:59:30  $GNTXT,01,01,02,HW UBX-M8030 00080000*60
17:59:30  $GNTXT,01,01,02,ROM CORE 3.01 (107888)*2B
17:59:30  $GNTXT,01,01,02,FWVER=SPG 3.01*46
17:59:30  $GNTXT,01,01,02,PROTVER=18.00*11
17:59:30  $GNTXT,01,01,02,GPS;GLO;GAL;BDS*77
17:59:30  $GNTXT,01,01,02,SBAS;IMES;QZSS*49
17:59:30  $GNTXT,01,01,02,GNSS OTP=GPS;GLO*37
17:59:30  $GNTXT,01,01,02,LLC=FFFFFFFF-FFFFFFED-FFFFFFFF-FFFFFFFF-FFFFFFE9*50
17:59:30  $GNTXT,01,01,02,ANTSUPERV=AC SD PDoS SR*3E
17:59:30  $GNTXT,01,01,02,ANTSTATUS=OK*25
17:59:30  $GNTXT,01,01,02,PF=3FF*4B

And when I send B5 62 06 41 00 00 47 DB in Messages/Custom in uCenter I get

B5 62 06 41 80 00 52 5B 4E 9E AD FF FF FF FF FF
EF EB FF 76 FE FF FF FF FF FF FF FF FF FF FF FF

And it doesn’t change withe “medicine”

I think I’m doing it right because B5 62 06 01 03 00 02 14 01 21 6E properly activates MEASX

Hopefully some bright mind can figure out a new medicine. Thank you !

EDIT - after flashing a new firmware just in case (it doesn’t help) I have this now, no other change

Navilock after flash :
18:14:17 $GNTXT,01,01,02,u-blox AG - www.u-blox.com4E
18:14:17 $GNTXT,01,01,02,HW UBX-M8030 00080000
60
18:14:17 $GNTXT,01,01,02,EXT CORE 3.01 (107900)33
18:14:17 $GNTXT,01,01,02,ROM BASE 3.01 (107888)25
18:14:17 $GNTXT,01,01,02,FWVER=SPG 3.01
46
18:14:17 $GNTXT,01,01,02,PROTVER=18.00
11
18:14:17 $GNTXT,01,01,02,FIS=0xEF4014 (200058)56
18:14:17 $GNTXT,01,01,02,GPS;GLO;GAL;BDS
77
18:14:17 $GNTXT,01,01,02,SBAS;IMES;QZSS49
18:14:17 $GNTXT,01,01,02,GNSS OTP=GPS;GLO
37
18:14:17 $GNTXT,01,01,02,LLC=FFFFFFFF-FFFFFFED-FFFFFFFF-FFFFFFFF-FFFFFFE950
18:14:17 $GNTXT,01,01,02,ANTSUPERV=AC SD PDoS SR
3E
18:14:17 $GNTXT,01,01,02,ANTSTATUS=OK25
18:14:17 $GNTXT,01,01,02,PF=3FF
4B

Your PF value prevents the raw data output. Here is the full PF bit matrix:


PF=    0             00.0000.0000 old
PF=  300             11.0000.0000
PF=  379             11.0111.1001 M8P
PF=  3BF             11.1011.1111 M8U
PF=  3F7             11.1111.0111
PF=  3FA             11.1111.1010 M8T
PF=  3FF             11.1111.1111 nodata
PF=FFFFF 1111.1111.1111.1111.1111 M9N
PF=?????                          F9K?
PF=FF9F3 1111.1111.1001.1111.0011 F9R
PF=FDBFF 1111.1101.1011.1111.1111 F9H
PF=FFF7A 1111.1111.1111.0111.1010 F9T
PF=FFF79 1111.1111.1111.0111.1001 F9P
                        ||   |||| tim
                        ||   |||  ppp
                        ||   ||   raw
                        ||   |    adr
                        ||        udr
                        |         rtk

Thank you for the reply. That makes sense and I wasn’t expecting the 8030 to be able to output RAW out of the box but that’s something that the “medicine” for M8N based receivers has been able to fix I think ?

If no “medicine” can be found I saw here https://rtklibexplorer.wordpress.com/2017/06/07/newest-u-blox-m8n-receivers-not-usable-with-rtklib/ about the M8N that “there are now several modified versions of u-blox firmware and RTKLIB floating around that have been hacked to unscramble the messages” but I have not been able to find them :frowning:

**используйте эту команду в ОДНУ СТРОКУ
**
use this command in ONE LINE

B5 62 09 21 AC 00 9F C0 97 F4 89 DC DE 41 85 2A F2 57 D0 A6 B6 74 72 7A 3D 91 37 06 F1 81 A0 9C D3 BA 13 C9 7C BB 00 00 20 00 00 00 00 00 4C B4 57 5D D2 FF FF FF 07 F8 EF FB FF 76 EF FF 92 EE FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF C0 5A 97 0B DE 7A

THANK YOU VERY KINDLY ! The additional “FF FF” towards the end did the magic !

Sorry for the silly question but what is a good way of running 301_rom_m8n_eFuse.cmd with one click ? There I sent everything via uCenter so it takes a bit of time. I tried loading it in ScriptCommunicator but it only seems to take .js scripts ?

Also I have an old Antaris 4 USB receiver with a patch antenna that’s very sensitive and I saw here https://wiki.openstreetmap.org/wiki/UbloxRAW#ANTARIS4 that there was also a way to enable RXM-RAW and RXM-SFRB on it with command : b5 62 09 01 09 00 14 6c 00 00 00 00 00 00 ff 92 f7 but it doesn’t work. Is there any “medicine” available for it too ?

Modifying firmware is too much effort without any substantial gain, because
the stock rtklib u-blox driver does not support this input data format.
The only feasible long-term solution is to maintain a GPLv3 fork of the rtklib/rtkgps+ combo,
keeping the ‘permutation’ and ‘xor’ 128bit keys outside the source code tree.
If somebody will volunteer to maintain such repository at github, i will happily contribute the source code
dealing with the user-oriented missing features.

Вопросы по поводу “Quadrifilar backfire helix antenna” антенны (http://lea.hamradio.si/~s53mv/navsats/analog.html):

В описании сказано, что данная конструкция антенны очень чувствительна к длине продов т.к. используется эффект резонанса и в общем-то антенна узкополосная, т.е. именно та, что на приведена рисунке предназаначенна для частоты 1572.42MHz, а для например Глонасс (GLONASS L1) размеры должны быть на 3% меньше. При диаметре 30 мм - 3% = 0,9 мм - на сколько реально выдержать такие размеры (изменения) ?

Так же делается допущение:

Обычно один из продников заменяется на полутвердый коаксиальный кабель того же диаметра, что и остальные продники. Но применение конструкции показанной картинке (fig. 16) не ухудшает значтельно качетсво приема, поэтому она использется.
Может быть можно рассмотреть “идельную” конструкцию “балун” - без центральной трубки(каоксиала) ?

Ищу, где приобрести semi-rigid coaxial 141 50Ом, пока нашел только в Казани, минимум 2 метра. Может, кто подскажет какие еще есть вариенты.

Можно ли использовать LNA от какой-ть готовой патч антенны ?

Спасибо.

как уже говорил, **делать эту антенну без прибора нет особого смысла **
если имеете прибор то подключите к нему стандартный квадратный керамический патч и посмотрите что такое узкополосность и какую именно частоту показывает прибор на резонансе кер. патч, должно быть 1575 МГц и ксв ~ 1.2
“Quadrifilar backfire helix antenna” по отношению к патч довольно широкополосная и без проблем перекрывает GPS и GLONASS

для изготовления я использовал медь диаметром 1.2 мм и серебренный фторопластовый МЯГКИЙ коаксиал диаметром толи 4 … 5 мм по оплетке то ли больше … лень идти измерять
те размеры условные но начинать надо с них, предварительно изготовив оправку для гнутья, на глаз не прокатит
после 4-х итераций мне удалось попасть в размер когда GPS и GLONASS были в полосе пропускания
модуль LNA можно использовать от любой патч антенны, но лично я не стал этого делать,
ибо и так все чудесно.
для симметрирования (вместо балуна) одевал снизу (возле медных проводов впритык) феррит. цилиндр с внутренним как внешний у коаксиала

Планирую сделать модель для 3Д принтера и распечатать, чтобы соблюсти размеры.

я тоже так планировал :smiley:

Is anyone here still using SiRF II or III receivers ? I found an old Globalsat BT-338 and have downgraded the firmware to 3.02 using http://gps.0xdc.ru/wiki/doku.php?id=sirfstar#globalsat_bt-338 and normally this should output phase data but when I use the Kinematic2_MobileApp app by Cnav on geodesist.ru to produce a Rinex the phase data is empty and there are no readings in RTKPost. When I log with SiRFDemo there does seem to be info though. There is also an app called GNSS Monitor by sklimkim but I can’t download the latest v4 version. Anyway I’m confused and would appreciate if anyone can help, thanks !

Did you enable the sirf messages with the raw data content ?
The same should apply also to the antraris4 receivers.

Thanks for your suggestion.
For Antaris 4 I can use RTKNavi directly with the uBlox format so I can see quickly if the messages are enabled.
For SiRF receivers there is a SiRF format input for the Android version of RTKLibe but not for the computer version and I’m not getting any satellite info in the Android version so I’m not sure if it’s expecting a different SiRF format (SiRF 4?) or if messages haven’t been enabled properly…
It seems that with SiRFII or SiRFIII you can’t do realtime and have to log data ?
When I look at the sirfstar.gps log from SiRFDemo the CarrierPhase data is there but not in Rinex log produced by theKinematic2_MobileApp app. I haven’t found an app to convert the sirfstar.gps to Rinex.

sirf2, sirf3 and sirf4 use exactly the same raw binary data packet format (GPS, 12 channels).

Which messages did you enable with the SiRFDemo program ?

I have enabled several including the one with Carrier Phase data apparently : 028 (0x1C - Nav Lib Measurement Data) enabled and when I look at “Receiver Output View” in SiRFDemo I can see the data coming through. With the BT338 running 3.00 the carrier phase field in sirfstar.gps is 0.00000 but in 3.02 (got it here http://gps.0xdc.ru/wiki/doku.php?id=sirfstar#globalsat_bt-338)) there are non 0 values.

I haven’t been able to determine if there are real time solutions (RTKNavi for instance) for SiRF receivers or if it’s logging only and then post-processing with a Rinex file. So far I have only found the Kinematic2_MobileApp app that is supposed to create a Rinex but that’s not working for me for some reason, are there others ? Thanks !

What version of Kinematic2_MobileApp and what platform (Win32 or Windows Mobile) do you use ?
I haven’t looked in sources for many years but if remember correctly the logging of carrier phase was not implemented in early versions (2011) due to phase measurements was not present in sirf binary data.

Thank you for your help. I’m using version 0.11 on Win32 from https://geodesist.ru/threads/programma-raboty-s-bytovymi-navigatorami-v-praktike-geodezista.5101/page-7#post-74909 - I haven’t found more recent versions ?

The BT-338 log (test1131.11o) posted by sklimkim here https://geodesist.ru/threads/programma-raboty-s-bytovymi-navigatorami-v-praktike-geodezista.5101/page-7#post-74904 has phase data in it using FW 3.1.1 with the same reference as the one found here http://gps.0xdc.ru/wiki/doku.php?id=sirfstar#globalsat_bt-338 - I will flash mine to that version from 3.0.2 that it’s using right now.

kinematic-release-0.13

Program changes baudrate, protocol and messages automatically so no need to do it in SirfDemo. It is logging both RINEX and raw binary data which can be replayed in SirfDemo or converted in 3rd party tools.

One message is not enough for the generation of proper RINEX output, please enable MID7, MID8 and MID28.

I am not aware of any ready-to-use compiled rtklib version with the sirf raw data support,
but you can compile it yourself. It will be a tough exercise on windows :expressionless:

What is strange is that RTKGPS+ for Android supports SiRF input and it is built from RTKLIB so I’m not sure why SiRF is not there. Unfortunately the support for SiRF in Alpha 26 (latest version on the Playstore) of RTKGPS+ for Android is broken, it is working in Alpha 23 but in that version I can’t get data from Ntrip feeds…I wasn’t able to find apks of Alpha 24 or Alpha 25 to see if one of them has both SiRF and Ntrip working properly. Does anyone here have them maybe ?

Thank you very much ! I now get Carrier Phase data in the Rinex. I will try to post-process it with RTKPost to see if I get usable results.