I think it’s just a block of 4 bytes and each bit in that block represents a section. So for 8 sections you could just send bits in byte 5 and leave the others as 0x00
Could be wrong though!!
1 Like
Thanks for writing this bridge CQuick! I have just setup a new Bogballe M35W with the Totz box successfully. The only snag I ran into was the bridge software did not pick up the section data from AOG properly. It just showed the error “Invalid section data! Please re-load the vehicle file in AgOpenGPS”. In the end I got around this by manually editing the config.ini file and it seems to be working. Will test tomorrow.
Any ideas what might have gone wrong? This is on a mixed UDP/USB system (nano for canbus steering over USB) on a slightly older AgOpenGPS version (5.2.2 I think). I tried reloading various vehicles, restarting AgopenGPS/AgIO etc but no luck.
By the way I would be interested in variable rate control if/when you get around to implementing it.
How did you go about getting your hands on the serial protocol CQuick? I want to do a similar thing for a Hardi Sprayer but I am not having much luck getting my hands on the “Hardi VRA protocol.”
Bogballe publishing the documention for the serial protocol. See link it github repo
AgOpenGps should be included in this leaflet:
https://www.google.com/url?q=https://www.krm-ltd.co.uk/Bogballe/Bogballe%2520Leaflets/GPS_Controlled_Spreading.pdf&sa=U&ved=2ahUKEwi0lurSp_f8AhUJuIsKHem0CjoQFnoECAEQAg&usg=AOvVaw1fErbdIT58Lw5vn5sloh1t
That’ll be because the section width PGN was only added in v5.6.something
The section data forwarding should still work, but you’ll need to use the latest AOG for the autoconfig.
I’ve updated the script on Github now, which should be more verbose about whether it’s connected to AgIO, incase there are any network issues, and also displays a warning if you’re using an unsupported version
That would explain it! I will try the new version.
Couple of bugs squashed today.
There’s a new setting in the config.ini, if you want the spreader to continue spreading after losing connection to AOG then set it to 1. By default when losing network it will stop spreading, but this can be annoying going over hills and losing cell connection, which causes AgIO to briefly lock up.
So this means you can carry on your run until it re-connects
Anyone tested this in the 2023 season. How is it working?
Wondering if I sell my old L1 spreader and buy a used M35W with Zurf Control unit.
Is variable rate on roadmap? Maybe AgopenGPS needs Shapefile support first?
I’ve been using it all last spring, no changes planned for this year unless anyone reports any bugs.
Should work on a Zurf but I haven’t tested it personally. I will help you if you have any issues though!
In terms of variable rate, I’m waiting for the VR function in AOG to mature and stabilise before I put any effort in. I agree, shapefile support is important.
Hello , it seem you work on ASD Quantron , I do also , did you have some results ?