Hello Brian, my config is normally a dual Antenna so PAOGI would be the correct Sentence. But i wanted to find out how a Single Antenna System works with the New Sensor CMPS14! Thats why i have changed Sentence. When i activated PAOGI, AOG not recognizing the CMPS14.
Anyway it worked out lauter yesterday. I really have to say, both concepts works really well. I have compared it with same settings and same AB curves. PP works really well for both concepts, also tested up to 20 kmh.
Load the new ino’s from the support.zip, and do the settings in AOG. There is the machine ino there are well, but just make sure your relays are connected to what the pin designation is in the arduino code. Much like version 4, not much has changed.
If you used the mma or brick or bno055, that has been replaced with the bno080, 085 or the CMPS14. Lots of discussion on those here.
That was just to fix the ABLine so you could see it. I’ll build it for the recorded path and post it outside of this discussion, as it is not part of V5.
Trouble with Google Earth, is that it is not real, nor is it accurate. If you scroll through the years of photographs you can watch them shift. In 2004, my house is sitting nearly 100 meters to the west.
Now if you are wanting to import and export in and out of google earth, you need to have a reference point. That reference point will have an east and west component. Based on your picture and the assumption that north is 45 degrees, then the south component is equal to the west component and is cos(45)(146). But again, that is assuming 45 degrees.
Finally got a notice from RobotShop that my CMPS14 shipped. Hopefully I’ll get a chance to work with it again. I’d like to update from my version 3.x setup that has served quite well to do all the steering on the planter tractor for the last 3 years.
What would also be useful is to have the start date and the end date of work in the kml file.
A request has also just been made to have this information for the traceability of the work.
Possible feature or change that would be useful is to have Autosteer disengage once RTK signal is lost. I run into issues where I lose RTK and the tractor decides to jump 50cm one direction with no notice.
Currently there is not a start and end date saved to the section. Sections start and stop often and save every so often. So, it processes it in chucks. Each chunk would only be seconds apart. And even at that the Sections are not in order in the kml. You would need a recorded path running. That could have a start and stop.
Id agree with this. Perhaps if RTK alarm is set then disengage steering if triggered?
Possible feature or change that would be useful is to have Autosteer disengage once RTK signal is lost. I run into issues where I lose RTK and the tractor decides to jump 50cm one direction with no notice.
I’ve been over about 700 acres now with v5, mostly spreading fertilizer. It’s been working great! I really appreciate the “delete applied area” function. It makes starting a new process in the field much easier than v4.3. I don’t have to remember to save under a different name all the time, just wipe the painted area clean and start again! Thanks.
Abcurve isn’t shifting depending on the tool offset. (Tool offset is here 50 cm.) Though this works fine with abline. Is it hard to correct it in abcurve?
