|
SEQ, Australia | It's always going to try and spray the missed patches between passes, as it is a "gap" in the coverage logging, Depending on the nozzle spacings, height and fan angle, you are usually covering around 61ft or better by actual sprayed ground. You can adjust the Application Width (not the swath width) out to 61ft and it will then always show a slight amount of overlap on the outer sections (0.5ft each side) that will do a better job of hiding the skip that is showing when you are running at 60ft. It will still do 60ft passes for the autosteer. Just be aware that it will also log area based on the 61ft now, which will slightly affect your actual rate and area to empty values.
As for the skips on the turns, make sure you have the Minimum override speed set so that as the sprayer slows down, it doesn't lose too much pressure/flow and make the boom sections unable to keep up a spray pattern once you drop under a certain speed. A nozzle chart is reasonably important for setting that number up, but it can be manually altered until you are happy. Also set the Valve Behaviour on Sections Closed to "Lock in Last Position" if you have a Servo Valve, and "Lock at Minimum' if it is a PWM controlled pump. There will also be issues if the outer boom sections are very short and the inner boom widths are wide. It will close down the valve to try and stay roughly on rate as you enter point rows, which means the last section on is a short boom width, requiring not much flow, so when you turn and re-enter the field it will only be open a small amount to run the opposing short section and then have to open quickly to accommodate the larger sections as they hit the unsprayed areas, and it may not be physically able to get everything pressurised quickly enough to guarantee a nozzle pattern. Also check that you have a decent Start Overlap distance, the Coverage Overlap % should be at 99%, and the Boundary Overlap % should be at least up to about 30-50% so that the boom sections don't turn fully off if the end of one boom just crosses over the boundary line. If you are running on WAAS or RangePoint RTX accuracy, these boundaries will shift slightly over time, which will change how much boom thinks it is over the line from one Event to the next
Edited by Trimbleguy 9/3/2025 06:14
| |
|
Field IQ—what setting do I change to fix this?
