Also got playing around in AOG tonight and I must have mist the section thing all together. It could be just a small error in code but idk.
I can set the individual sections as wide as I want but if you use the sections button to apply to all sections you are limited to 394 inches.
It’s just the limit set too low for the “section width” box, it’s 1000 cm. limits for individual section are set to 5000 cm(164 ft).
@BrianTee_Admin should just set it to 5000. Or is it a reason to not be set at 5000?
Are you satisfied using the radar? There are ways to convert the speed to pulses. Brian has included this in a recent post and may actually be in the ino. But if the GPS speed is not accurate enough with the trees, I wonder how the ABLine is accurate.
Two other questions (forgive my ignorance:)
What is VRA?
Is product pan testing something you do and then set, or is it machine/product specific.
Currently on 60foot with lime I am ok being within 1-2 foot pass to pass. As I have mentioned in other posts RTK is not necessary in my work. But without speed input I can do nothing since the system is based off speed. That is why I went back to good old radar it just works and is accurate.
VRA = Variable Rate Application
Changing rate based off a predefined field prescription from soil tests and in season tissue tests.
As for pan testing
Easier to show than explain
But essentially yes product and spreader specific.
That’s what I figured and 5000 is probably a good round number to use.
VRA, we worked on a kml reader that gave the prescribed application rate for the field. I suspected this is what VRA was, but wasn’t sure if this was the prescription or the dose. For spraying, dose mapping is pretty easy. Wildly my mind went to dose mapping spreading in these half circles. I think that is out of my reach and ability. Probably doable, but seems complicated.
Back to the radar. I assume the raven system controls the spreader based on user inputs and monitoring the radar speed. Is the radar machine specific or a raven product?
Here is where we were working with the VR stuff.
@SK21 may can give some insight on the rate app and speed monitoring.
@SK21 @KentStuff do you guys have any ideas on how I could enter in two different rates but be able to switch between the 2 rates on the fly while going through the field without a prescription map made. Kinda variable rate but I would need to push a button or switch? I have the variable rate controller with @SK21 design and INO. RAVEN 440 controller and similar have this function and just wondering if it’s possible to do here?!
It shouldn’t be too hard to do. I think Brian had that in his original AgRate software. I will see what I can come up with.
Sounds awesome, then a person could possibly wire or put that into a future design of toggle switch adjustable rate for two or even three pre-determined rates. I was reading through the VR posts for a 3rd time today and trying to gather if you guys have a came up with the software for VR. I was working on a KML file now to make contour maps with 2 different rates. Is there such software for it yet? Maybe I should move this over to the @SK21 variable rate thread?
Should the pre-determined rates be as a % of the main rate or separate altogether? The VR software isn’t completed yet.
I would say it should match whatever the VR software is going to use for values across the field. Of course gallon or liters is easy, but I believe a percentage is going to be the easiest for software side of things. This would allow people to figure the percentage of whatever product they’re applying. My thought was similar to what you guys were working on before, 100% of base/main rate and allow 200% of that or down to 1% of base/main.
The switch box would be ideal as it’s easier bouncing in the field to hit a toggle switch. It could get confusing to have to cycle through rates versus flipping a toggle in direction of actual set rate.
When i built my VR box, I integrated the 16 relays, cytron, VR pcb, section pcb and all switches into the front clear cover of the water proof box. 32 pin connector to connect sprayer, planter, etc. easily to the wired box. It left lots of room for more switches, 12 vdc plug, etc too. I highly recommend to people to use a bigger box then needed and clear cover to see led lights for verification and functionality of relays and cytron. The rate controller has not skipped a beat all spring spraying. Keeps up gpm with speed perfect! Rate controller worked flawlessly with my 12 row shutoffs on the corn/soybean planter as well.
A switchbox would be best. Something in software would be quicker to make. Maybe only two rates and a separate push button. Open to ideas.
Good to hear it worked for you. Which version of the software?
2.2.0, it’s the “works” that you sent me back in march-april. Having the select able relays is a great feature. I’m really looking forward to variable rate coming. What you, @KentStuff, @PotatoFarmer and @BrianTee_Admin were working on looks amazing.
I would agree that would be the quickest. In the future for pcb changes, a physical switch would integrate more into what i’m familiar with Raven spray controllers. A push button isn’t a bad idea just much easier to forget the set rate versus seeing a switch flipped up or down. This will be nice for overriding a prescription map amount or in this case not having a prescription and wanting to manually bump up the base rate in sections of fields!
I don’t work much yet, Just lots of building whats already been created, testing and testing and testing.
Trying to learn the magic of programming the windows side of things.
Debug.zip (6.8 MB)
Here is the latest version with a rate change button. Click on “Target Rate” to switch. Use the settings page to change the amount. It will work in the simulator but it won’t work with the ver 2.2 nano ino.
That works awesome in simulator. Very easy to switch back and forth. Can each rate be tied with different paint colors? Even then, how easy is it to implement it on a nano file?
RCnano.zip (11.4 KB)
Here is an ino file that will work.
Painting different colors would be good. This has to be done in AOG. I don’t think a pgn exists to allow this from an external program. AOG ver 6 feature request!
