|
North East Kansas | I am getting much closer on the 20/20 issue. Who's fault is it? There is blame to go around, but its looking like the 372 is causing the issue in the first place, although the NAV controller may also be getting confused with a receiver setting. Precision planting used to filter this bad data, and make the planter work good, but they stopped filtering the data sometime around or before the release of the version 2022 software. All the other manufacturers are still filtering this data which is why they aren't having these issues. It would have been nice if Precision just told me this in the first place. One thing I've heard over the years is that it's a digifarm issue, and that is not true. The only reason you will notice it with digifarm or any other port C device is simply because they are using port C.
I have tested so many different receiver configurations. It does seem like only the RTK unlocked receivers are having this problem, and only when using port C. Is port C locked when the receiver has no unlocks or just an omni unlock? If I change the default settings on port C, I have the speed blips. even in WAAS of the RTK unlocked receivers. I'm hoping to get my receiver and possibly NAV firmware updated on Monday and then I can see if that works.
So far I have had 2 non unlocked 372, and 1 omni unlocked 372 receivers work fine. One had WAAS, one had centerpoint RTX, and the other had rangepoint RTX on it. The Rangepoint receiver has no unlocks and it worked fine even when Port C was configured. A newer 372 with an omnistar unlock, and it was running rtx centerpoint also worked fine even when port C was setup to be used. I couldn't try digifarm since none of those receivers have full unlocks. A fully unlocked 372 that originally ran digifarm didn't work on WAAS, XFILL, or RTK. When I set the receiver back to default, and then changed the WAAAS antenna back to 135, it worked fine on WAAS. I then changed the configuration of the port C. I just changed the second line only where the default setting is TSIP on both Lines and shows a 38.4 frequency. I changed TSIP on the top to RTCM, and then changed tsip on the bottom to NMEA, just like when you are setting a device up like digifarm. I didn't hook any device to port C, but only changed those port C settings. That alone caused some issues for the 20/20. Instead of speed blips higher, they made the blips lower. So with nothing hooked to port C, just changing a setting alone messed everything up even running in just WAAS. So to recap, only the RTK unlocked receivers (372,262) had these glitches, and only when port C was configured. It is extremely weird. I hope it can be solved by firmware, and it's not a hardware lottery issue. There is a chance that keeping a default port C would allow me to run centerpoint RTX on the fully unlocked receivers, but I already have digifarm so it would be nice to keep running it.
I'll report back when I'm totally fixed, since that might help a lot of people. I've seen so many people fight this over the years. | |
|
Getting closer on the 20/20 speed blips
