Thanks, hadn’t spotted that. Will have a fiddle in an hour and see how things go.
One other thing @BrianTee_Admin. No biggie and maybe a Windows 10 “feature”, but when adding manual sim coordinates (edit: from Notepad) and also when importing a KML from GE, AOG stays in focus meaning there’s a fair bit of moving / resizing windows so that you can flip between the two.
As I say, not a big problem, just thought I’d mention it.
Ok, will keep uturn on.
And a Mario version would be amazing, if ever you have the time and inclination.
And a massive “THANKS” for giving the world AOG, best thing I’ve seen in years.
And you’re spot on.
Reset back to defaults and it’s working pretty flawlessly. My problem now is that I am using a small tool on a small field, it’s a toy by your standards: 100CM in length, 85CM wheelbase and 50CM wide.
I will keep testing and see what I can make it do.
The code is built around for roughly 3 meter minimum. It works the best at the 12 meter range. Set up the vehicle as the defaults and see if it will run the “big” pattern. Remember that the computer has no idea how big it really is. Start with what works and creep down. There’s a lot of programing to get it to run the small vehicles. I’ve done it a few times. Boundaries must be cut small, u-turns must be modified, and radiuses must be adjusted.
Ok, I see what you’re saying.
Tried resetting to defaults and it ran fine on the sim. Left it at the defaults and took it out for a test on a football field; just wanted it to follow an AB line, perform a single uturn and return, but it was all over the place going left / right and then driving in circles. Possibly GPS accuracy, possibly AOG settings. I’ll give it another couple of field tests and see if I can get it working reliably. If not, then perhaps full strength AOG just won’t work for such a small vehicle.
Fingers crossed!!
But defaults can´t drive a vehicle, settings must be done according to your steering setup.
Did you do the settings as in Brians video, mentioned to you 24 days ago in the other thread: Getting started with PCB hardware for beginners ?
@Larsvest is correct. Default only works in the simulator. But when you get into the field on a small tool and running slow, NTRIP is very important. The GPS will be all over the place.
I did calibrate the WAS, but didn’t do much more.
Ok, my bad, I’ll bone-up again, adjust and retest.
Ya, depending on the machine and setup, it can be a bit of struggle, but change things one at a time, see the effect, learn what the settings do, adjust etc.
Right, so one variable at a time. I’ll do some tests this weekend and post how it goes.
As always, thanks for your time guys.
Evening (relatively speaking), Gents
After a lot of fiddling, I can see what the main problem is: section / tool width. The minimum values that I can get reliable performance from seems to be one section with 300cm width; if I drop down to (say) 200cm, then u-turns start to act strangely.
I’ve dropped the wheelbase down to 85cm, turn radius to 200cm, tow length to 50cm and tailing hitch length to 20cm, and it runs pretty sweet in the sim with a single 300cm section, but my problem now is that no tool I use with be that large. Will keep fiddling to see if I can find a workaround, but I might also slap an Emlid Reach 2 on the vehicle and see if that helps.
As discussed here it turns better to left. ( at the end of keyhole it is also right when the whole turn is started with left arrow).
It can do 0,85 m section/implement when you choose 1 skip, keyhole turn and your trator settings but also max steer angle at 70 degree(or it cant follow keyhole).Of course you would have to do the field twice then to get it all done.
That’s really interesting and useful, thanks Lars. I will test this all out later this evening and see if it helps.
Did find one problem with this setup: tractor stops U-turn in sim if angle between AB line and boarder is not close to 90 degree. It shows the u-turn but stops when close to the keyhole pattern.
@bluerabbit, we found that the uturn steps can be shorter and it works really well. You can crash it but it works much better. Read through that post, It will tell you what to change.
That is where I where I got stuck. Have never programmed anything before arduino a year ago, so what program xxx to open and which file yyy to change?
Exactly, last May I thought C# was a music note. I’ve learned some since then. I’ll isolate what I did and post it here. Maybe tonight or so.
Am I going in the right direction with downloading Visual studio community, and then choosing NET desktop development?
Yes, I’ve found that to work for what I do. I un-check live share, just in time debugger, and a couple more on the options.
I have been testing for about 4 hours with the vehicle set up to match my own (85cm wheelbase, 270cm U-turn (i’m going to have to work on that), 45 degree max steering angle, etc and everything works well until I drop the tool width to under ~180cm, then it just stops being reliable.
3m runs sweet, 2m drifts a little after the apex of the turn, 150cm runs out of the field.
As was said in the “Possible sharp turn fix” thread, AOG isn’t designed for small vehicles so none of this surprises me, but… gah! So near and yet…
I’ll re-read the short term fix thread a couple of times as some parts of that discussion threw me.