Don’t know what is going on but I doubt you have done anything wrong.
Have you checked if the Euref stream has the same GPS L2 code as your private base (was it F9P?)? I don’t know how it changes things and I don’t understand why e.g. RTCM 1004 needs to state which L1/L2 code is used. I thought 1004 “just” informs the carrier phase and the modulation data could be anything, the receiver just needs to “remove the data modulation” before correlating with the carrier.
Someone here seemed to know the GPS code stuff quite well and might be able to explain why e.g. SNIP RTCM decoder says F9P refers to L2X for L2 code while for my commercial base SNIP reports L2W for the L2 code?
Even if the AGI-3 did not understand the L2 information, it should be able to find a fix with the L1 data only since your private base is so close. No idea if it takes more time, never used a single frequency receiver.
Off topic but I tried our Fendt VarioGuide RTK receiver (the Fendt variant of the Topcon AGI-4) and it did not find any fix from 1075 (and/or 1085) messages. Looks like AGCO has no purchased the update to support MSM messages. Neither do they have updates for Galileo support. The first brochures of AGI-4 refer to coming Galileo support but I asked at the TFF forum and looks like AGI-4 with Topcon cloths neither has Galileo implemented as of today. What a shame.
With STRSVR I converted F9P data to RTCM 1004, 1006, 1012 and 1033 and I got an RTK fix from my F9P base. It took time, needed good satellite visibility and was quite unstable. A bit odd when F9P as a rover seems to keep RTK fix much better than the AGI-4 when receiving corrections from my commercial base.
Did you manage to get anything working in the end @Alan.Webb ?
I had a problem today trying to set up a Topcon AGI-3/X30 with an F9P base.
Entered all the ntrip details, unit starts receiving data, but no RTK.
Reboot
Instant RTK fix. Works great.
5 minutes later the unit stops applying the corrections and falls out of RTK. It’s still receiving messages though.
Reboot doesn’t fix the issue.
No I didn’t unfortunately. We got it working with another base on rtk2go with a staggering 150Km baseline!! Way better than it was on SBAS. I see STRSVR has been updated so I might have another go when I’ve got the 724 up and running on CAN BUS.
I just managed to obtain RTK fix with my AGCO branded Topcon X30 + AGI-4 using a correction stream from my F9P-based base station.
Had the same problem initially that RTK messages were coming through, but no RTK fix. Boot and instant RTK fix.
Will need to check next time whether it drops out of RTK in 5 min or not. I’m using STRSVR to convert the F9P data + add the following RTCM 3.0 messages: 1004(1),1006(31),1008(31),1012(1),1033(31). Some of them are empty and for some reason STRSVR loses most of the Glonass satellites from the initial MSM message data If I forward unconverted and converted entries to SNIP, I can see that the converted data has less of both: GPS and Glonass satellites. But RTK fix works and is obtained within a couple of minutes.
Edit: It is possible STRSVR does this reduction in satellite numbers for a reason - some older receivers refuse to obtain RTK fix if the L1 correction data has more than 12 satellites.
I didn’t do anything about TADJ, but did set ADVNULLANTENNA. What do you think should be done with TADJ?
I have been able to connect to a Finnish reference network DGPS (NTRIP) stream that broadcasts just messages 1006, 1071 and 1081, so for DGPS via NTRIP the message 1008 is not needed.
I also tried with my older Fieldbee L1 base (with older SkytraQ chip), relaying that stream to RTK2go and with that STRSVR does not lose any of the GPS or Glonass satellites. However, with even 20 satellites in view and close to the base, the receiver fails to move from RTK Float to RTK Fix and the Topcon/AGCO (Valtra) system complains about position accuracy and refuses to autosteer.
In the end I decided to keep the correction stream that originates from a F9P, but convert it into two separate mountpoints: L1 only and L1/L2. This way the L1 stream provides correction with max 12 satellites, but IT WORKS.
Could be different with “genuine” Topcon AGI-4 that has better software updates and might accept more satellites.
The TADJ=1 or 1.5 seems to be popular, Stefal’s rtkbase is using that, also here:
Don’t know if it is needed and if I remember right, RTKLIB was supposed to take care of the related issue on the current release.
I have the Fendt variant of the TOPCON AGI-4 receiver and it does not work without RTCM 1008 (I’m not using the F9P base). I could not run it with MSM messages either, perhaps different AGI-4 software?
Which AGI-4 SW did you have on the AGCO (I guess Valtra/MF/Challenger variant) AGI-4? I have that too but couldn’t get the latest SW last summer because it is not loaded to the official diagnosis tool. Did not help telling the SW release info to the local service and their support guys (got it from the release info from the thefarmingforum.co.uk).
I’m not familiar with MSM messages, does 1071 enable RTK accuracy? I thought 1074 and 1077 were more popular (but don’t know the difference).
Okay, so I made some corrections to my above messages to remove misinformation.
So now I have a fully functional AGCO (Valtra) AG3000 receiver (AGI-4 hardware) + AGCO version of Topcon X30 screen. With fast RTK Fix from F9P, even with just 6 satellites. AND the autosteer actually engages!
The F9P base is providing full set of RTCM messages to one mountpoint on an NTRIP server. Then - on a totally remote PC - I relay that mountpoint to STRSVR and use it to convert the original RTCM messages to just 1004,1006,1008,1012 and 1033. Message 1008 has ADVNULLANTENNA. In 1006 I have the base location that set in STRSVR in the same “options” menu as ADVNULLANTENNA. This overrides any previous base location info. Message 1033 is empty and I’m still not sure if it needed. Does no harm.
This in my view is very convenient. I do not need complicated and limited message injection systems at the base location, but can adjust the messages with STRSVR anywhere with a Windows tablet - including in the cab. It just has to be on 24/7 or at least when working.
I just tried this F9P again as a base for the Topcon AGI-4 (the MF/Valtra variant and the Fendt variant).
I had the same messages as Juurikko above plus 1019 and 1020. I was using the Stefal Raspberry Pi base, it also runs RTKLIB on the Raspberry (not sure about the RTKLIB version). Had the ADVNULLANTENNA and the TADJ=1 setting (just because Stefal has it on the default settings).
Our Valtra was doing fine, much better than at my previous test about a year ago. The Fendt was mostly fine too first but later on struggled a bit more than expected when close to buildings (where RTK is often lost even with my commercial base).
I wonder why it worked better this time. Had a look at the RTCM1004 message content (from the SNIP decoder). All GPS satellites had L2X now for L2. Previously some 30% did not use L2. I tried to google about GPS modernization status but did only find ancient documents. Would anyone know if they now all have the new L2 signal that F9P supports?
I also observed some odd behaviour. The RTCM1012 message included G32, good SNR and pseudo range values. RTCM1004 on the other hand reported 0 SNR for G2 (which actually was good from my other base). I wonder if this is an RTKLIB issue, SNIP issue or something else?
If I forward unconverted and converted entries to SNIP, I can see that the converted data has less of both: GPS and Glonass satellites. But RTK fix works and is obtained within a couple of minutes.