Yes the list called MapList is only for all the visual, built with the resolution specified in the vehicle/display tab.
All the blade calculation are made with the ContourList witch are the same points than the agd file to not lose precision. When the blade is near a point it use this one, else it looks for the closest pt on all 4 side and make a average.
All the stuff for the blade control is working. Right now I am just improving the visual aspect and the .agd file importing. I will use it it about 2 weeks in field and I am planning to rebuild a new version this winter.
I will check your library.
Edit:
Now importing .agd file should work pretty well. It import the MB code(have to be just one), discard all other beginning by 0, import 2SUBZONE1 to 9, 2PER, and 3GRD
Iāve uploaded a new branch, āUnder Constructionā. It has the pickable points in the ABDraw screen. Click the select text and click lower left to upper right. Right click on any of them to select. Unclick select and draw point to point and click profile it will draw the profile. Get near the profile line and you can see where you are along that line with survey and cut values bottom right. The numbers at the top of the page are the survey points. If you right click on any of them you can change both survey and cut values. Pressing the green enter button makes the change. The x button goes back to ab screen. That part gets confusing.
Give it a try. Might crash might work, might kill the family cat.
Iāll start with the one thatās pre installed on the blade, itās a Cetop on/off valve from duplomatic. Same valve as the manufacturer uses in their gps/laser setup.
I have added an important feature to the survey mode! I just thought yesterday that a survey point is useless or even a bad thing if the fix is not RTK!
With my first android bluetooth app I had some drops and didnāt always seen immediately
So now it only record point when is RTK, you can also select float RTK if you want.
I also changed the simulator to enter lat long on the main screen. @nut You are in the longitude East? You can look if this work near to you.
The simulator was writhed only for lat of more than 10 north and long more than 100 west.
There are some label that always display N and W no matter the real position? Itās only visual?
Iāve tried a bit to draw the contour lines, with little to no success. If the field is nice and sloping one direction fairly easy to find the lines across the field. If there is a hill or raven in the field, it does not want to draw the circle. Correction it may draw one of the circles, but if thereās two, not so much. If there is a flat area, with many points at a given contour point, it has no idea what to do. So my thoughts were, find all the points at say 100, 101, 102, etc. and connect the dots. Hind sight thatās great for a single sloped field. But that doesnāt work for not so flat areas. Hand calculation of contours is find the highest point, find his neighbors, interpolate the whole numbers between each and draw the complete circles. If the circle is not complete move to the next point down in elevation and do it again. Proceed down in elevation and work your way to boundaries, ditches, walls, or other. Easy said, fairly simple to draw, but I have not been able to code that. Any thoughts?
I rewrote the elevation calculation stuff, the four pts stuff was not good enough. Now it search for the closest pt NW, NE , SW and SE then check for the closest point from blade on each line (north, south, east, west), calculate this point height, and make a weighed average of these points.
Good stuff! Just finished harvest on Monday so hoping to get back to testing the leveling this week, control box is almost finished, will post some pictures when thatās done and the bench testing works.
Those none elevation points made a mess of the averages. I had to get rid of them also. I chose to ignore anything less than 1 in the reading.
So you are taking a weighted average of eight points? Are you averaging the cut elevation, the survey elevation, or last pass? Does your blade height change either of these or does it create a new set of points and eliminate all the ones that have been cut?
@KentStuff For the 3GRD pt, I have not figured out reading the words when there is nothing between comas, it return null or skip it?
For the blade control it use only the design point cut elevation(pasted to the ptList), averaging when not close enough from a point. it make the same with the existing elevation but itās only for the elevation view. The ptList values are never changed.
All the visual is made with the mapList, so the blade accuracy is never affected what ever happen in the visual part.
I have been working a little on last pass recording but in the mapPt List so only for visual but itās not great this will be removed and re-writhed. So right now there is nothing to control the blade dept it goes the cut altitude.
I will continue to improve the blade calculation, I had some ideas, so there will be an other update I a few days.
I canāt take to much credit for all this work (especially the math part)! I am only taking @BrianTee_Admin 's work and putting it together. This last code come from AOG from dist calculation from AB line.
All these calculations begin is OpenGL.Designer.cs Line 472
Yes, I give @BrianTee_Admin all the credit, I just feed new numbers in his formulas and modify or copy others. My latest thought was to read the survey data and then leave that alone, build a new file each time with a date stamp. Points edited during the session would be written to this file. Upon opening a field you select which survey you want to open. And start building a new file with new cuts. Possibly convert/export the last cut data to the new survey file.
Some hardware updates, box for control soon ready for testing. Should work without opengrade connected with the manual buttons as the arduino gets now power from PCB
One rocker for man-auto selection and one for up-down.
In my opengrade3D you can load an agd file only once per field(erase all the files below to reopen an agd). It will not make any modification to the agd file.
It will create:
contour.txt, this is the list with the 3GRD pts, this are the pts used for blade control
BoundaryList.txt, the list for all boundary and zone pts
DesignList.txt, for debug only, a list of all the pts loaded from agd file with the code used in opengrade
MapPt.txt, list for all the visual stuff, the only one that will be modified during use.
To use an agd file:
1- Go near to the field to avoid big easting or northing number (in real or in the simulator)
2- Open a field that never loaded an agd file (like the one that created the survey) or create a new one.
3- Go in the vehicle tab and select the desired map resolution
4- Open the agd file and wait for the map to be created (can take several minutes)
After that simply open and close the field.
Last release, v1.0.2:
I think it now have a very good blade elevation calculation but I am now thinking if it should have a look ahead feature to compensate the delay in the program. But even at 8km/h 0.2 sec would give only 0.5m so I think it should not be a big deal.
I should have my optisurface software tomorrow, so I will see if the survey work well.
It works with same code. Its electrically identical, just smaller. I try to make the arduino code this week and test the buttons, will post here when its working.
My program has 2 modes, survey and grade, you switch by click on the bottom task bar.
In survey mode you can only survey, it will build an .ags file when done. It have to be done in one shot, you cannot exit the program and resume the survey later, it will overwrite the older one (probably need to add time/date stamp to the file)
This .ags file cannot be used in opengrade3D, you have to pass trough optisurface to make the design and create an .agd file.
In grade mode opengrade3D can only work with an .agd file, all others functions (except laser mode) have been removed. You cannot modify the cutaltitude once in opendrage3D you can only adjust the overall height (like commercial systems)
All the big calculations are made the first time the .agd file is openned, after that you can close and open the field or opengrade3D and all the data will be there.
@KentStuff I didnāt take time to look at your AOG survey yet. I think you should export an .ags file for your survey only (only existing altitudes) and if you add cutaltitude values to your point you should build an .agd file (only with the points that have an altitude and a cutaltitude).
This could be used in opengrade3D.
Opengrade3D can handle survey pts 30m apart right now and is optimized for point equally spaced (like a grid) but I will add more setting to handle random spaced pts and greater distances.
Iāll give it a shot now that thereās a break in harvesting.
