Bugs v4.3.10

Alan.Webb · 23 May 2020 08:11

Where is the updated version actually located? Is it just source code? The release doesn’t mention it’s been updated and when I tried to install it I got a message saying the version already installed is newer

I’m obviously getting it wrong somewhere.

Larsvest · 23 May 2020 08:32

sourcecode updated yesterday and some new lines for the Mega 14 hours ago

I don´t use ver 4 yet so don´t know message about already installed.

BrianTee_Admin · 24 May 2020 14:39

I don;t know what the heck happened, it was there for a few days, now is the old one again. sometimes i really don’t like github. Try again…

https://github.com/farmerbriantee/AgOpenGPS/releases/tag/4.3.10

Francois · 24 May 2020 20:39

Hello,
I’m perhaps wrong but I wonder the following thing :
has anyone used the UDP communication with v3.4.10 ?
With USB it works perfectly. With UDP, in the Aog to Autosteer direction
it work but I’ve sometimes Crc errors in the other direction nothing ?
The message Steer Module Not Connected is always there.
What are the conditions for this message to disappear ?
It seems that the Crc is always the Crc of the Module Configuration
even if his is Steer Settings ?
Best regards,
francois

Apm · 24 May 2020 22:44

Ya. I think we need a session to teach Git.
Github ok for actually storage & distribution of the project, but Git better for rest.
Maybe a new thread for it if enough interest, as its really needed to make this project truely collaborative.

Alan.Webb · 25 May 2020 22:03

It confuses the hell out of me and sometimes my suse PC’s get really annoyed with it!

deistho · 26 May 2020 07:59

The roll source is not stored with the vehicle.
Compass is not visible
(overlapp missing )

darrenjlobb · 26 May 2020 15:51

Not sure if this is specifically a 4.3.10 bug, or maybe something thats been around a while, but I have only started majorly using it since 4.3.10, so that is my experience…

I am noticing upon loosing NTRIP connection (under a tree / loose 4g cell etc) when AOG goes into the waiting / trying to reconnect state with its built in NTRIP client, I am finding AOG keeps locking up, everything stops, steering stops, numbers on display stop moving for second or two, sometimes this can be 3-5 seconds, if on level ground with no side draft, you barely notice as once on the line, the tractor hardly moves off track during that time, but if on the side of a hill, or mid U turn etc, its fairly chronic!

Once the connection is successful and it returns to “listening” it all starts working again / everything is perfect…

Have been mainly on the good side of the valley with it, where signal is great / never once had a blip in days, but the other side it drops out quite often, normally for 15-30 seconds max, which should be fine as the F9P stays on its last fix for that long anyway, but due to this issue, it creates chaos as AOG is just constantly locking up / causing problem.

Has anyone else seen this at all? Or could it be something specific to my situation?

I use UDP to connect everything (ethernet on 192.168.1.255 subnet), but the ntrip corrections come in via wifi (mobile hotspot), on a different subnet…don’t know if having these two connection in any way upsets AOG? Like i said, when its connected / working, it works 100% spot on, but soon as it drops, it causes me the problem.

Any ideas?

Richardklasens_admin · 26 May 2020 21:27

I never had this problem with any version…

GTx · 16 June 2020 23:57

I don’t now if someone is mentioned this, because my English not so good to understand everything completely, but in the latest version it still is.

Sooo… In right menu bar you can change skips from 1 to 10.
You can also do in in U turn settings, but only from 1 to 6

And if you change skips in menu bar greater than 6 (for example my tramlines is every 7 row for my seed drill) and open U turn settings you got a error.

uturn

BrianTee_Admin · 18 June 2020 02:14

Nice catch - probably a real pain, i will look at this! Thx

BrianTee_Admin · 18 June 2020 02:18

Fixed, will be in next update
Screenshot_1

m_elias · 18 June 2020 19:59

I’ve been playing around with 4.3.10 using the simulator only so far. Here are a few things. Note, I just installed this version. It’s the first time AoG has been installed on this computer since installing W10 from scratch.

Minor feature requests:

Allow keyboard/numpad entry in Enter a value keypad popup for numerical values
Define a default action button (save/okay/exit/close/return) for popup windows and allow enter key on keyboard to activate that button.
In Uturn settings window, use preferred units and if using m/ft, then allow a decimal point.

Minor bugs

Stop Record Pause Boundary window shows boundary offset in unlabeled meters instead of preferred units.
Click 2 Points on the boundary then Choose… window shows tool width in unlabeled cm instead of preferred units.
In the following screenshot, sections 1-4 should be in auto/green and section 5 is in manual due to proximity to the boundary. The bug is that sec3 is is painting correctly but it’s showing red/off on the imp.

Major bug

After opening an existing field with boundary (created in AoG by driving the perimeter) and deleting the applied area, when I try to open the Headlands windows, AoG crashes.

This is using the default tractor and a 121.67’ 3pt imp with 20" overlap. I can easity recreate it multiple times. Once I load the default tool, it works without crashing. Go back to my wide 3pt imp and it again crashes. I’m not sure where the 111.3 value comes from.

If I can help with more info or testing please let me know.

edit
I forgot to attached the details from the unhandled exception error. Maybe there are some clues in the error message. Note, at one point c:\users\griz is mentioned but that’s not a path on my computer.

Error details

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: Value of ‘111.3’ is not valid for ‘Value’. ‘Value’ should be between ‘Minimum’ and ‘Maximum’.

Parameter name: Value

at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)

at AgOpenGPS.FormHeadland.FormHeadland_Load(Object sender, EventArgs e) in C:\Users\Grizs\Desktop\Git\AgOpenGPS\SourceCode\GPS\Forms\FormHeadland.cs:line 51

at System.Windows.Forms.Form.OnLoad(EventArgs e)

at System.Windows.Forms.Form.OnCreateControl()

at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)

at System.Windows.Forms.Control.CreateControl()

at System.Windows.Forms.Control.WmShowWindow(Message& m)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

at System.Windows.Forms.Form.WmShowWindow(Message& m)

at System.Windows.Forms.Form.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.4180.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

AgOpenGPS
Assembly Version: 4.3.10.0
Win32 Version: 4.3.10
CodeBase: [file:///C:/Program%20Files%20(x86)/AgOpenGPS/AgOpenGPS.exe](file:///C:/Program%20Files%20%28x86%29/AgOpenGPS/AgOpenGPS.exe)

System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4001.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.4150.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.3752.0 built by: NET48REL1
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.4180.0 built by: NET48REL1LAST_B
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:/Program%20Files%20(x86)/AgOpenGPS/OpenTK.GLControl.DLL](file:///C:/Program%20Files%20%28x86%29/AgOpenGPS/OpenTK.GLControl.DLL)

OpenTK
Assembly Version: 1.2.0.0
Win32 Version: 1.2.2336.6514-pre
CodeBase: [file:///C:/Program%20Files%20(x86)/AgOpenGPS/OpenTK.DLL](file:///C:/Program%20Files%20%28x86%29/AgOpenGPS/OpenTK.DLL)

Control.Draggable
Assembly Version: 1.0.7235.3768
Win32 Version: 1.0.7235.37687
CodeBase: [file:///C:/Program%20Files%20(x86)/AgOpenGPS/Control.Draggable.DLL](file:///C:/Program%20Files%20%28x86%29/AgOpenGPS/Control.Draggable.DLL)

RepeatButtonControl
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: [file:///C:/Program%20Files%20(x86)/AgOpenGPS/RepeatButtonControl.DLL](file:///C:/Program%20Files%20%28x86%29/AgOpenGPS/RepeatButtonControl.DLL)

Tinkerforge
Assembly Version: 2.1.16.0
Win32 Version: 2.1.16.0
CodeBase: [file:///C:/Program%20Files%20(x86)/AgOpenGPS/Tinkerforge.DLL](file:///C:/Program%20Files%20%28x86%29/AgOpenGPS/Tinkerforge.DLL)

Keypad
Assembly Version: 4.3.10.0
Win32 Version: 4.3.10.0
CodeBase: [file:///C:/Program%20Files%20(x86)/AgOpenGPS/Keypad.DLL](file:///C:/Program%20Files%20%28x86%29/AgOpenGPS/Keypad.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.

BrianTee_Admin · 22 June 2020 03:52

Can you post your tool.txt on telegram?

m_elias · 22 June 2020 18:59

Here’s my tool.txt for the Major Bug.
120ft 3pt sprayer.txt (1.0 KB)

Regarding Minor Bug #3, I briefly tried to reproduce it but could not.

BrianTee_Admin · 23 June 2020 19:26

Found the headland problem, max for distance from boundary was 99.9 meters, in your case, that is too narrow for the calculation so upped it to 199 meters. Hopefully no one needs a headland bigger then that (650 feet). Screenshot_3

minorplanets · 16 March 2021 04:04

Something that looks like it has popped up in one of the latest updates of 4.3.10. This is a field kml imported into Google Earth. Boundaries seem to have come out distorted. Applied area is correct.

Probably associated with the projection as it was working fine prior to that change. These boundaries I believe were driven then bought into Google Earth, cleaned up a bit, then bought back into AgOpenGPS. I was planning on tweaking one of the internal boundaries a touch more. All fine in use on the tractor. There is an obvious offset in the Google Earth photo (unrelated).

Anyone else noticed? Could be a Southern Hemisphere thing?

Tooki57 · 1 April 2021 06:27

trying to download v4.3.10.msi on aog release , windows defender stop me cause of trojan "ludicrouz " …

BrianTee_Admin · 4 April 2021 14:05

well that is ludicrous lol.

Hubs · 4 May 2021 20:10

Hello.

I’m using the Version 4.3.10 and I’ve got a proleme with the U-Turn
It can be activated, but starts to count at about 14 000m and counts down only one meter per second.
The problem is pretty new.
Probably it started when we created the fields from KLM file out.

The fields were measured external with a Leica receiver and the Zeno Connect app.
Subsequently, the individual fields were extracted and stored using Google Earth.
Does anyone know the problem ?
Thank you in advance