In AGIO, IP address of machine, can it be changed? For some reason AGIO gets my virtual-network address as default, and is grey, can’t change?
Well… Too hurry, found solution same time as wrote that… In ip v4 (tcp/ip) settings has advanced options. There is “Automatic metric value” or something.
Going trough all networks adapters and making sure primary card has smallest metric number, windows or network-stack or something decides where to go first.
Thought to put this out, tried search at forum but no go, here it is for somebody else to find.
Restarted agopengps and agio and there it is, my primary network-address.
Okay, think we’ve isolated this bug a bit further.
I think our GPS setup/settings is good. RTK F9P running at 10 Hz. Fix to fix is 1 and min speed is 1, but sometimes we need to mow at 1.
Check out the video below. What we’re finding is that as you turn towards a new AB curve, the pure pursuit yellow dot doesn’t always pick the right direction, even when you reset the direction by tapping the tractor. As you can see, the yellow dot stays behind the tractor even when driving forwards, so when you engage autosteer, it tries to turn 180 degrees. The work around is to turn ab curve on and off again.
I realized, that not very many people have a situation like this, but I thought I would put a video on here as an idea of something that could possibly be improved on in the future. We have so many new lines in one field, that it hardly works to use AB curves, because we would have at least 15 or 20 lines per field! Using contour mode works great, until you come alongside a previous pass that is different than your current line, and then AOG gets completely confused. Our Raven system that we are using works just like aog, but our deere system does not jump lines.(not sure how they fix this problem?) I’m guessing this would be a major upgrade @BrianTee_Admin ? ContourLineSwitching - Google Drive (our fields look like this everywhere…)
This happens if you can stay on the line within half a tool width and not leave to make a new one in curve. Otherwise it would be constantly picking new curves to drive on. What i can do is make sure the line isn’t “backwards” to the current direction and redraw it.
Ok new version on github 5004.zip that now parses the nmea in AGIO. This is a huge thing, when it was done in AOG, the nmea had to be timed with the frame redraw etc, so it had to poll if new data is coming in etc. Now, whether udp or serial, AgIO immediately parses it, sends a complete pgn (and very much smaller byte form with only the needed information instead of hundreds of characters) to AOG which immediately triggers a frame redraw/update.
AgIO has a GPS data form, tap the double arrows at top of AgIO. Numbers on the left side of the icon mean data going in, right side of icon, data rate going out.
This version may have some errors - or not. There was much debate to do this huge mod - but it works extremely well, we had to do it. Give it a try.
I got mtz8302’s dual gps working, via usb everything works.
UDP i get no gps data?
AGIO set UDP ON, tested ntrip via UDP, it works, but no data…
AOG_GPS_ESP32 's debug messages shows got ntrip data, so data flowing in, but no out?
Confused.
Am I right, if I assume when just in same subnet (ip’s etc “right”), agio just gets what is available?
No need to (havent FOUND any place to give nothing but com-ports) set up nothing, UDP on and thats it?
But anyway, funny to see 80cm of sheetmetal with two antennas attached to give so accurate roll and heading without moving.
And, I haven’t said anywhere yet the obvious, great work you all. I’ll try contribute something else than just questions sometime…
Maybe begin to write “beginners guide to agopengs, what to do and what to avoid”…
Just read so much problems with gyros roll-sensors etc, decided not to go there first…
Probably not a good place to post this but I made a sticky abline. We were running a small tractor and a small tool with no auto steer. When turning the u-turn it was difficult to find what line you were supposed to drive to as it kept jumping. So, only the selected line would show up. When you got to the end of the row, you manually advanced the line right or left before making the turn. Perhaps a sticky curve may work in your situation. Just a thought.
Was just messing around with the app when this came out, posted in case it is usefull, if not please ignore
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ComponentModel.Win32Exception (0x80004005): No application is associated with the specified file for this operation
at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start(String fileName)
at AgOpenGPS.FormBoundary.btnOpenGoogleEarth_Click(Object sender, EventArgs e) in C:\Users\Grizs\Desktop\SourceCode46\GPS\Forms\FormBoundary.cs:line 273
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4300.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
AgOpenGPS
Assembly Version: 5.0.0.4
Win32 Version: 5.0.0.4
CodeBase: file:///C:/AOG_5004/AgOpenGPS_5_Beta/AgOpenGPS.exe
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4300.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4270.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4300.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
OpenTK.GLControl
Assembly Version: 1.2.0.0
Win32 Version: 1.2.2336.6514-pre
CodeBase: file:///C:/AOG_5004/AgOpenGPS_5_Beta/OpenTK.GLControl.DLL
----------------------------------------
OpenTK
Assembly Version: 1.2.0.0
Win32 Version: 1.2.2336.6514-pre
CodeBase: file:///C:/AOG_5004/AgOpenGPS_5_Beta/OpenTK.DLL
----------------------------------------
Control.Draggable
Assembly Version: 1.0.7235.37687
Win32 Version: 1.0.7235.37687
CodeBase: file:///C:/AOG_5004/AgOpenGPS_5_Beta/Control.Draggable.DLL
----------------------------------------
RepeatButtonControl
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/AOG_5004/AgOpenGPS_5_Beta/RepeatButtonControl.DLL
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
A bit annoying feature(or is it just me…) is that autosteer configuration window and autosteer chart window needs to open, resize and reposition every time settings screen has been opened to make adjustments. I like to keep them open and in certain places on the screen when I make fine adjustments.
If there is draft, does AOG keep the pivot on the line or the implement that is a known distance behind? ( because that distance from the pivot is set in tractor hitch and implement settings)
Or does V5 not handle draft with single antenna (I thaugt it could with bno085 or cmps)
And in V5, what does the value “ingegral starts at” do to the integral when driving Stainley?
Just a thought regarding the ino for arduino: now some of the values are architecture dependent (found out playing around with the 32bit Teensy), so the negative setpoints and wasoffsets don’t work if you go to a platform where you have 32 bit int. Could we modify the code in the ino something like this and if someone could check if this still works with arduino, it should as int and short are the same. Now you get the same behavior regardless of the platform.
//Bit 8,9 set point steer angle * 100 is sent
steerAngleSetPoint = ((float)((short)Serial.read()| (short)(Serial.read() << 8 )))*0.01; //high low bytes
Same with the wasOffset, declare it as short and:
steerSettings.wasOffset = (short)Serial.read(); //read was zero offset Hi
steerSettings.wasOffset |= (short)(Serial.read() << 8); //read was zero offset Lo
Those were the two platform dependencies I came across. I guess you could declare all int as short in the arduino code to be on the safe side, but still you get an int that is 16 bit out from Serial.read() in AVR boards and 32 bit from e.g. ARM based boards.
It happens every time I try same thing, but it does not crash, if I click continue it continue working fine (im in demo mode)
It happens every time I enter START OR DELETE A BOUNDARY and then click on blue shaped circle.
Can you tell me how you create those sticky ABlines? I think i could use it for plough control, so when the plough reaches min or max width it doesn’t jump to next ABline and creates a “wave”.
Thanks in advance.
This was in the ABC simple version. I created a bool isSticky and created a button to turn it off and on. Then in the abline.cs there was a line of code that checked how many widths away. Before this I added, and if (!isSticky) and included that width calculation in the brackets. Now it did not update which line to drive. Then I used the offset abline buttons to jump full right or left one full tool width if (isSticky). A hack at best, but worked well for us. I’ve learned a bit more of the AOG since then and would now add a right or left button on the screen to jump over as needed. I would also have it force how many paths away and set my current abline based on this value.
Too hurry, found solution same time as wrote that… In ip v4 (tcp/ip) settings has advanced options. There is “Automatic metric value” or something.
