There is a flag for u turn in the nano, not sure really if it flags but its there. Need to find a better way to interact with the nano during operation.
But the set point has to scale with the output to keep set point hovering over current current output. With the code above you have to noticeably pull or hold it to disengage. Keep in mind I only weigh 165lbs, If perfect was 20% force over normal steering, its at 35% right now in all modes.
I froze a bit tonight but got it all ironed out. The reason for the random disengage was my original snippet allowed the set point value to go negative. I am extremely happy with the results now using the ACS712 straight or in a uturn.
// Use current PWM value as percentage to add some extra amps while U turning.
// To get more setpoint resolution between amps 10.5 amps would be entered as "105" on the settings page
if ( abs(analogValue - 512) >= (steerConfig.PulseCountMax * ( 1.2 + (abs(pwmDisplay) / (steerSettings.highPWM - steerSettings.lowPWM))* 1.1))) //amp current limit switch off
{
steerSwitch = 1; // reset values like it turned off
currentState = 1;
previous = 0;
}
}
Also tonight I learned the difference between my Chinese brt10 tablet, and Getac f110 G2. Though the brt10 runs AOG well especially going straight, I was still having some odd U turn and Contour guidance overshoot issues. The Getac runs U turns much more precise and extremely smooth. I thought AOG was great before, but I cant get over how smooth, slow and methodically it moves the steering now.
Do you think a pc with more “horse power” can make autosteering better?
I think what is going on is comparable to PC’s and video game frame rate.
The higher power tablet is able to crunch the numbers faster so it keeps up with each scan required and the result is smoother without any dropped “frames”. The wheel turns slower during u turn but more accurately.
The BRT10 gets its processor loaded up during Uturn and ends up over compensating, because its not able to keep up with the higher demand. The wheel whips to keep up between “dropped frames” and overshoots more.
All AOG tuning settings are the same. Only difference is the tablet used.
The test that will for sure prove this is seeing if there is still a long pause between contour segments during boundary guidance on headlands.
Now you scared me. I was thinking about getting an ASUS TH101A, BRT10. I think I’ll pay more and get a GETAC. Or some tablet or 2-in-1 notebook with i5>i7 processor with 4GB<=8GB ram
You don´t need an i7. I am running AOG v5 very well on a Dell Venue 11 (dell venue 11 pro 7140 m-5y71)
It is fan-less, so no dust inside!
It has almost 400 nits of brightness (I still need to buy an antiglare protection sheet for it) I think it is all right in daylight but not direct sun.
Ive had a good time with the getac G2, I am pretty sure a Panasonic would be no different.
Sold the getac G2 and dock already to the friend I farm with, after seeing that my lawnmower was outperforming his fleet of Trimbles.
Found a used G3 f110 and dock, so already upgraded. But now its too cold to play with, bench testing only.
But as for boundary guidance with the f110, it worked smoother overall, but still does some mad line hopping. I think this feature requires a bit more development. It either works, or loop de loops nothing in between.
Sorry I know this is not the subject of this topic. But to clear up some doubts:
1/ HP ElitePad 1000 G2 10.1" 64GB Silver Tablet with 4GB RAM Memory
2/ Hp Pro Tablet 608 G1
3/ Tablet Windows 10 W11 Pipo 11.6 8gb +128
4/ ASUS TH101A,
5/ BRT10.
What is the best way to run AGOPENGPS?
Biggest consideration of all is screen brightness, the brt10 was only 400nits. Found this insufficient under canopy, especially at sunrise and sunset. Full sun completely unreadable. Also found its very jumpy in uturn in back to back test.
Got a used F110 because they have 800nits brightness. Can see it very well under all conditions under a canopy or in cab. Only have moderate washout reading in open station direct full sunlight but still very usable. Added bonuses were being rugged, more responsive and larger touch screen and great cab mounting options.
Buy for the max Nits. Being able to see the screen under all conditions really is the most important.
i7 with 8gb of ram runs this program without compromise.
Ask google about speed: UserBenchmark: Intel Celeron N2930 vs Core M-5Y71
The speed of the one I use versus BRT10 processor, and I see why potatofarmer say it is too slow.
Meaning Celeron -N2930 is too slow to consider!
In a tractor with cabin, direct sunlight is not a problem I have noticed with only 400 nits.
In windows joblist AOG and AGIO both takes about 10% (5 to 15) of CPU usage, when driving in field with U-turn active. (Correct I did not check % CPU when doing the U-turn, but did not notice jumps in frames)
So you must compare nits, speed and price to find what suits you.
I searched and found something about disengagement.
Ag Open has this pricing beat, lol
I read cover to cover, disengagement is only mentioned as a needed item twice, but no mention of how to pull it off. They reused a trimble Ez steer motor for the tests, and did spend a disproportionate amount of time back calculating why it works. Very good report hopefully they got a good mark on it at school, AOG is light years ahead of this project, other than the camera guidance portion.
Has the latest version of AOG 5.4.4 been updated to include code for use of the ACS712?
Yes, I tested it with an older version as well and it worked.
Yes functionality for ACS from arduino .ino 5.0
All you have to do select current disengagement from the arduino setup page on tablet.
thanks for the quick response. Would thess ACS712 work? not sure of amps as there are 20’s and 30 amp choices thought I would go with 30.
Yes it would work. Just connect the OUT pin to A0 pin on the PCB.
Cant remember if i am using 20 or 30, all it should affect is the final setpoint value scaling. Having to enter 14 vs 10 as a setpoint.
This setpoint is that found in the Arduino .ino code? if so where?
You can set it in settings in AOG
