The “autonomous” part of AOG is seriously behind the field work part which has been the major focus these last few months. Yes, most of the code was commented out just to make sure the normal field operation code was working.
Just added this simple little check in the FormCommSet.cs to see if you could add a trigger to the relayData and you can. I put it on [9] as it was not being used on this version. And sure enough, it will give you the out or in bounds value (15 or 0). Arbitrary values, but it works. If I remember right, on one of the videos, there were extra serial read values in the arduino code. I may be wrong, but it may be worth looking into.
if (mf.mc.isOutOfBounds)
{
mf.mc.relayData[9] = (byte)15;
}
else
{
mf.mc.relayData[9] = (byte)0;
}
Edit: This was the video (6.25 mins is where the extras are). Much has changed very quick, but it is controllable:
1 Like
Thanks for this Kentstuff, this is all a massive learning curve. I have had a look, and edited, the CS files as described, but I’m still a little lost with this. Basically nothing changed after I’d done the edit, I’m unclear as to whether the app needs recompiling.
Sorry for my ignorance!
The geofence OOB feature does work as things stand; if the vehicle breaches the geofence, then it cuts power to the relays. So if I strap a relay to the drive motor and designate this as a tool, then it does stop as required.
The final problem I have though is the overlap feature: if the vehicle hits an area it has already covered, then it cuts power to the tool. If that tool is the main drive motor, then obviously the vehicle just stops… potentially half way across a field.
Is there any way of disabling this overlap feature whilst maintaining the OOB function? If I can do that, then I have everything working through AOG.
I have tried, but unfortunately there is no change. The sections still disable when they hit an overlap area.
Thanks for the idea through 
In original code it should be working. With this manual mode I can overlap and drive to my neighbors field and it will be painting all the time.
Try to change to manual section control while driving.
1 Like
I’ve updated the MicrOpenGPS to limit the number of sections to 7 and use section 8 for the out of bounds relay. Simply connect your equipment master supply to the section 8 relay in the arduino code. It will send a 0 for off or 1 for on. Section 8 is overwritten just prior to the serial transmit. I have reformatted the strings in the picture below to see working. Just remember, there is no out of bounds when there is no boundary. I have not tried with the arduino but it appears to work in the simulator. Edit: Workaround I know, but it is simple. Better solution would be the other switches as mentioned above.
1 Like
Ok, let me try what you’ve each suggested.
Really can’t thank you enough for about 8 months of support!!
Almost there
I’m not sure how you originally got the MicrOpenGPS, but fairly certain you will have to update it and rebuild it on your end in Visual Studio. You will loose whatever changes that you have made.
Ugh, that does sound a bit beyond me right now. I’ll try MylArti‘s suggestion, see if I can make that work.
I have set the manual switch as you suggested and have two sections. If I set them to manual, then they stay on regardless of whether the vehicle is inside, or outside the geofence.
Am I missing something obvious?
I added the program.zip folder to the github. You should be able to download it, unblock it, unzip it, and run it outside of any virus shut outs to see if it works for you. May can just download, unzip and go. Not sure how it with come out on your end.
https://github.com/KentStuff/Micropengps/blob/master/Program.zip
1 Like
It works as it is supposed to work. It paints until you stop it manually i.e. automation is missing. Now overlapping the area covered will not cause work to be interrupted. Hopefully this will solve your final problem.
Rebased the latest version 4.3.10 and made the MicrOpenGPS mods with the limited 7 sections and the 8 section as the geofence relay. Here is the link to it. I’ve ran it in the simulator a bit and it appears to work. You can click the module console and see the 10000111 byte when in bounds and 00000111 when out of bounds. Works in manual or auto.
1 Like
It works perfectly! Pin 12 (in my setup) goes LOW as soon as it’s OOB and HIGH as soon as it’s back in the boundary.
I cannot thank you enough for your time. I will add this circuit to the vehicle and see if it all works. If it does, I will post some vids.
Brilliant, thanks!!
Even better. I tested the latest iteration of V4 last night and it’s a huge advance, runs very smoothly and has some excellent new features.
Thanks again.
Alright where’s the videos? 
Must be the ones fund under play button, at the top of this page.
Edit : didn’t understand the joke from Hobbyfarmer.
Mine is still a work in progress. I just hit a headache that has taken me 20 hours to cure… turned out my ADS1115 had died. Diagnosing that was fun…
I’ll post a vid as soon as I get it working, I do promise
Edit: Just while I’m here, may I clarify something?
I’ve installed the new ADS1115 and it seems to be working fine, but when I monitor the output in Serial Monitor, it’s not holding steading; fluctuating from 0,0 - 10.0.
Can I confirm that the value that needs editing for WAS calibration is
#define SteerPosZero
I’m fairly sure that’s right. I’ve had to put mine up to 2164 to get close to 0,0. Is this normal, or have I done something odd?
Am playing with the micro a bit. I have the turn radius set to 10 but the turn it does on the screen is is maybe 150 to 200. Is there more steering settings to make it turn tighter?
Edit: there must be different settings. The last turn was with 250 turn radius and the previous ones were 10. To bring things into prospective the tool I’m using is 10 wide