|
SEQ, Australia | No, not specific to an AFS Connect machine. I have it happening on 2 x machines that this customer has - one is an AG Ready Steiger 500, and the other is an 8970 New Holland. All machines have NavII/III controllers in them already, but the NH 8970 was upgraded from Ag170/NavI/Ag252/SiteNet900 to GFX-1260/NavIII/Nav-900/Ag820. The Steiger had a GFX-1260/NAV-900/Ag820/NavIII in it as well, but was just being used as a haulout/field-bin tractor to start with, so wasn't noticeable. The NH 8970 is a frontline planting tractor that was the latest one installed, so it was noticeable straight away that there was a problem. We have proven that the data/PIQ conversion is the problem buy just putting an FMX display back into both machines, keeping the NAV-900/NavIII and Ag820's and then the dataset works properly, but if we wipe the FMX of all field data and re-import it from scratch, we see the same sequence of the FMX loading it up wrong, recognising it and then fixing it each time. Any other machine that has had the A-B lines set up with an FMX and then transferred to a GFX has worked perfectly.
Trimble reckoned they saw a similar issue with legacy field data loaded into a PIQ display on versions prior to V13.6, but we tried importing a fresh copy of the data into Ver14.4 & Ver14.6 with no change to the problem. I have to try the same again on Ver15.XX shortly to see if the problem remains the same. I have been concentrating on one particular line which is a NE to SW line so far, but then I want to also try a SE to NW line to out if the dataset can be "moved" as a group to get everything re-aligned. I believe there is a projection issue/update causing it, because even the original A-B line is off by the same amount.
Edited by Trimbleguy 5/26/2025 20:03
| |
|
Trimble FMX to a Trimble GFX1260
