Unlikely you have a RC1_PWM output issue. Can you attach a tlog or bin (dataflash) log file and I’ll have a look.
Check your RC1_ parameter settings to ensure you have a min max set to sensible values.
Hi Kevin. Are you running the latest 3.0.1 version of ArduPilot?
Secondly you should always have the arming checks on. At the very least have ARMING_CHECK enabled as this will perform system checks and tell you if there is a problem but won’t prevent you from arming. If you also have ARMING_REQUIRE on then that will prevent you from arming but this is a GOOD thing as there is obviously a problem with the vehicle that needs solving.
The issue is with RC_MAP. Looks like you have changed it so
RCMAP_YAW = 1
RCMAP_ROLL = 4
This means you have told the pixhawk that instead of outputting the value on channel 1 its now being output on channel 4. With skid steering the output channels are RCMAP_THROTTLE and RCMAP_ROLL. You can either move your channel 1 connection to channel 4 or change back to defaults RCMAP
Let us know how you go.
Wow thanks Grant for clearing that up, I got up and running for a bit today.
Yes, I’m using 3.0.1. I have a Spektrum DX8 for my radio and a Sony Xperia Z4 Tablet for running Tower. I’m running a 3DR PPM encoder for the RX.
I had a bunch of problems with the arming checks and I am not quite sure how to arm in MP, so that’s why I took them all off and I’m fine arming with just the hardware safety switch. I plan to go back and revisit as I understand the settings better.
You were totally right about the RC_MAP. I changed them back and the throttle and skid steer worked fine, albeit on odd radio sticks. I tried to change them in MP, but they didn’t seem to change after a few restarts.
I manually reversed the throttle setting on my radio. It now works as it should on the left stick.
The rudder was a bit trickier as it was on the right stick for up/down. I had to manually switch the plugs on the PPM encoder for 2 and 3, then it worked fine. Right stick-left/right.
I had the USV out again yesterday trying it on AUTO mode, but had a bunch of problems…
I noticed a “stuttering” on my port thruster in MANUAL mode. I didn’t have this issue when I was testing it on the bench. This may be a BlueESC hardware issue so I’m not really sure where to go here.
When I tried turning to port, the vehicle comes to a stop and then turns slowly to port. Skid steer works fine when I am going straight or turning straboard.
I used Tower on my Sony Xperia Z4 tablet for my GCS because for whatever reason I was having connection issues with QGC. I wrote a simple waypoint path in Tower, uploaded the mission and changed the mode to AUTO…than the USV put it’s bow to the point, but started moving in reverse away from the point.
Solution: I have the throttle reversed on my radio. I can swap the propellers and switch the reverse on the thrusters.
Everything works fine in MANUAL, but when I put the USV into AUTO, it engages and turns 180 degrees to the course it is supposed to take and wobbles slowly in the opposite direction. See picture below:
I have tried plotting missions in Mission Planner and QGround Control and the result is the same. I have also tried reversing my thruster wires and reversing the channels on my radio, but that only yielded my USV aligning and moving backwards.
It looks great. Without seeing a log file my guess is your steering channel is reversed. Put the boat into STEERING mode and try and drive it around and see what happens. If that confirms your steering is reversed then assuming you have steering on channel 1 then set RC1_REV to -1 to fix the issue.
@gmorph Fixed my problem with AUTO today. I traced back all my wiring and it turns out I had my thrusters plugged into the opposite channels on the Pixhawk. Oops my mistake.
I took it out for a few hours today and although it can navigate to waypoints now, it has a pretty bad wobble which isn’t good for sidescan operations. I’m going through the documentation and trying to tune it in. Any feedback on settings for skid steer that have worked well in the past?
And about halfway through my day, I had my first engineering casualty and had to wait for the wind to blow it in…and found this…
I’ll have to work on some eelgrass thruster guards, there are some 3D printed ones out there.
Also, side note, I’m trying to ditch my RC controller and just use a gamepad that will connect to my tablet. However when I plug it in with Rover running I get a message saying that joysticks aren’t available on this firmware. Is this correct, or just an issue with QGC?
@seandepagnier Yes, I’m doing side scan and single beam surveys with a Lowrance HDS-7 and TotalScan Transducer. The data is then uploaded into Reefmaster software and mosaiced. You could probably use a sailing vessel, but your control would be a lot less because you would have to tack with the wind.
@Kevin_K I´ve read all your posts and you´ve done a great job. I´m very interested on what you are doing and would like to do it by myself. Could you start by posting a complete list of all the items you´ve bought to do this?
Also, why didn´t you a multibeam echosounder to do multibeam surveys? (just wondering)
Again, awesome job and very interesting, thanks for sharing!