@nut would really like to know were you got your switches and and enclosure. Do you have a schematic for wiring switches to PCB.
Thanks
Hi
Sorry for late reply, been away for a while. Switches from local spare parts store, box standard electric enclosure from hardware store. Scheme coming later today, hereās a wiring pic.
Ino should work from post 164!
So the wiring goes like this:
Thereās one on-off rocker switch that is connected to ground and outmost switch port.
Then thereās a second on-off-on switch thatās wired to ground and the other two ports for up/down respectively. I just ran one ground wire from PCB as they are all connected on the board anyhow.
The tilt sensor and a/d converter are not needed. So you need the power supply parts, optocouplers and all the resistors, capacitors etc needed for those circuits. You can leave the 5v supply out and it still works, but you need to power the arduino always via USB. With the 5 volt supply it worls also standalone without PC connected with manual up/down
Right, so if i want my manual switch to run. I need to have nano powered from board
Hi
I modified my .ino to work with this sparkfun joystick, it works great (on bench). Connected to pin A0
Here is the file: ValveControlPropLever.ino (9,1 Ko)
So it has an auto/man switch an the prop lever.
In manual mode the prop lever gives an output according to the min/max valves values from opengrade (when connected, else inoās default values).
In auto mode, the prop lever turn off the auto mode as soon the blade is lifted. Then you can lift/lover the blade the same way than when the auto/man switch is on man, but when you fully push the lever in lower position it reactivate the auto mode. Once auto mode reactivated lowering the lever have no effect.
I think this should give a very good control of the blade for grading, having all the control on one finger!
I donāt use a pcb, I have all connected directly to the nano (so far). Iām planning to make a 3D printed case for the lever, adapted to a suitable place in the tractor. Maybe changing for an IP67 lever later, but itās a big price step from IP65 resistive lever to IP67 hall!
Here is some photos of D5H valve project.
@nut should i be able to see if my on off switch for auto is working when watching āfrom blade control window.ā
Hi
depending the ino you are using, in the āFrom Blade Control Portā window, the first number will be 0 or 1 depending the blade is going up or down. The second will be the PWM value sent to the valve.
A quick way to see it work is to use the LaserMode.
You can also see these values in the āGPS Dataā window.
Remember that you maybe have to go in the vehicle configuration tab and resend the values to the arduino when connecting it (just to be sure it use the opengrade valve values instead his defaut values). Sometimes it donāt send the values at the start, a little bug.
So ive been using āpat open grade v2.1ā all day. And i think thier is a problem in cut window when drawing cut line. The āslope readoutā seems to be wrong, i think. It looks like its dividing the rise in meters by the run in feet.
slope should read 1.0 at the rise and run shown in picture?
Also tried my valve for the first time. Its a bucher 16 gpm load sense closed center 24 volt coils. The whole system runs which is exciting. But its to eratic to be usable goin down it drops about six inches below. and then goes about 2 inches above. then drops to 6 below up down up down continuously. Im including link to video. I would like to go with proportional valve but havnt been able to find one yet with load sense.maybe putting some orifices in circuit would help? Any help or advice would be appreciated.
For the valve setting you can try with a higher āovershot red,ā value, with my prop valve it is between 15 and 25. With a higher value it should stop the valve a greater distance before it goes back to the line, to avoid going back and forth. On/off valve may need a value of maybe 40 or even 90.
More deadband can help, the value is the distance from 0 in millimetres.
Witch ino are you using?
For the slope value, it seam to make the same error in metric and feet. This will need some investigation!
Im using the INO from @nut post 164. Would yours work with PCB v2 ?. I was using a overshoot reduction of 100 when i quite. It didnt seem to change it regardless of were i had it
This ino seam to have the PID correction, but it will probably need some improvements!
I learned a lot about these variables in the code and their limitations when I was playing with my prop lever.
You will probably need some flow control on the cylinder line to reduce the speed.
Did you tried with the blade on the ground? Mine vas dropping pretty fast when in the air.
@Pat And i have ordered an hydraforce sp10 57C but is out 10 weeks so will be awhile before i can test it.
I will give a look.
It use the side view to calculate the slope. Maybe I messed up while adding the views under and above.
I made a test and the error was the same in metric and imperial. the displayed slope x 4.02 = real slope.
Note: for horizontal distance you have to use the counter a bottom left. the first one on bottom right is the survey point count.
Edit: it seam that the slope value is calculated from the height in metre and the distance in survey pts number! Was this bug in the original app? I will have to take a look.
So the number i have circled in photo is not distance from start point of survey? All along i have been using that as distance. It must match fairly close for the speed i drive with the dozer. That would be really nice if that would read disance. I will check brians version to see how it runs.
So with brians current version i ran in simulation at different speeds.
i show the speed / ft in distance counter bottom left / distance in survey window (circled numver in previous photo. In this version all numbers in survey window stay meters it looks like the circled number is distance across window in meters it stays consistant across different speeds.
2.7 mph 150 46
5.8 mph 150 45
11.9 mph 150 44