AgTalk Home
AgTalk Home
Search Forums | Classifieds (163) | Skins | Language
You are logged in as a guest. ( logon | register )

Getting closer on the 20/20 speed blips
View previous thread :: View next thread
   Forums List -> Precision TalkMessage format
 
steve1616
Posted 11/19/2025 18:57 (#11440351 - in reply to #11439990)
Subject: RE: Getting closer on the 20/20 speed blips


North East Kansas
I can try that, and see how it reacts on port D. I have now updated the receiver, NAV, and pro 700 software. The receiver update helped quite a bit, but the NAV and the pro 700 update didn't help. It may have actually hurt it a little.

I can see that the main thing is the RTCM setting on Port C. I have officially completely fixed the 262 with the 20/20. The big thing seems to be the fact that you set to CRM on port C for the 262, compared to setting it on RTCM for the 372. In fact, Setting it to CRM for the 372 actually helps also, but the 372 just seems to not be as consistent. Port C and RTCM is the main thing messing things up. It sometimes helps to set NMEA out to ASAP also. I can say that I have made the 372 very functional, but I can tell that it's just not as perfect as other setups. The 372 will now operate within .35 mph consistency, although the occasional blip still happens. The 372 will operate at .25 mph consistency with no blips that I have seen when set to CRM on port C. This would probably be more than great for most people. What I can also tell you is that every single receiver that is not fully unlocked exhibits no issues at all no matter how port C is set up. The fully unlocked receivers also exhibit no issues either when using waas or centerpoint RTX as long as port C isn't setup for RTK. In all of these scenarios, whether these receivers are running WAAS, range point, or centerpoint, these scenarios have a .07 mph consistency. I have been able to get our 262 running Digifarm to be perfect also since it's set on CRM instead of RTCM for port C. I am not sure there is any way to get our 372 to be perfect when Port C is configured on RTCM. I would consider this issue as mostly fixed though. I am positive that no one would ever notice any issues where I have things set right now even on the unlocked 372. One thing to add is that it seems like Trimble wanted all other forms of RTK to fail on the 372 that have to be configured on port C. Maybe to make their own centerpoint stand out. Im not sure but it seems very weird.

Edited by steve1616 11/19/2025 19:08
Top of the page Bottom of the page


Jump to forum :
Search this forum
Printer friendly version
E-mail a link to this thread

(Delete cookies)