I read somewhere the official 2.46 had track steering problems. I understand the current beta fixes that issue. Many thanks to all developers. But the current beta now seems to have disabled the GPS's. Since I'm working with Piksis, I really don't know how far back I can go where I have track steering and my Pixhawk recognizes the Piksi RTK.... so which version is best?
BTW is backing up on the horizon?
Thanks
RoboBill
Replies
@Robobill,
The ArduRover v2.47 beta 1 and versions 2.44 and 2.45 correctly implement the skid (differential) steering, however I have not had any success getting the rangefinder (sonar) function to work correctly and I have informed Tridge about my rangefinder issue. Versions 2.44 and 2.45 lack some of the new functions implemented in v2.46.
The primary GPS worked just fine with v2.47 beta 1. I would have to look at the data flash log to see if the secondary GPS is working.
Did you enable the secondary GPS with the GPS_TYPE2 parameter?
As far as backing up goes, it will be up to Tridge to implement that function.
Regards,
TCIII AVD
@TCIII
Using the latest 2.47 beta, I enabled both GPS' and the auto switch. I plugged the 3DR into 1 and the Piksi is on 2. I toyed around with the type setting trying both Auto and specific. I could not get the Pixhawk to recognize either GPS... the LED stayed blue. If I went back to the original 2.46, the LED went to green and I got 3DR Fix on the HUD. (I still have yet to get RTK, but that's another issue).
Thanks
RoboBill
@Robobill,
Can you please provide a data flash log recorded during the time that you had that issue?
As I said in my post above, the primary GPS worked fine and I got the green led after a few minutes.
I have reviewed my data flash logs and both GPSs are indicating an Instance of 1 for that parameter. Therefore the Pixhawk is receiving data from both GPSs.
How are you powering your Pixhawk? I am supplying my Pixhawks using a 2 amp 5vdc supply tied into a USB breakout box. My laptop does not supply any power to the Pixhawk. Only the breakout box.
Regards,
TCIII AVD
@TCIII
I've never dealt with any log stuff. When reading about it, I got completely lost... i.e. the mission planner is looking for a *.log file. I found the tlog and rlog files. The rlog files go empty after I disconnect. So sorry, it's just too confusing. I just could not find a simple "for dummies" description on how to create the file you want. So I'll just have to wait.
For what its worth, I noted that the Pixhawk LED went green on start up as it should for ~ 10 seconds then went blue.
Thanks
RoboBill
@RoboBill,
There is a function bar under the HUD in the MP.
One of the functions is for the Data Log.
Click on that Tab and it will open a window allowing you to download the data logs that are on the SD card.
The downloaded data logs should be found in the MP/log/ArduRover/ directory once the download is complete.
Regards,
TCIII AVD
@TCIII
I clicked on "Download Dataflash via MavLink" and got the error "Cannot find Log List". After restarting the Pixhawk several times, I was finally able to get the screen you referred to. A whole bunch of files were created but I think I've attached the log file you want.
Thanks
RoboBill
2014-10-19 16-46-19 3.bin.log
@RoboBill,
An analysis of your data flash log indicates that neither GPS is giving an Instant parameter of 1 which means that the Pixhawk is not communicating with the GPSs.
Once question: why is your GPS_NAVFILTER parameter set to 3 when the default is 8?
Otherwise, I cannot tell from the data flash log why your GPSs are not communicating with the Pixhawk.
Regards,
TCIII AVD
@TCIII
Thanks for the quick analysis.
I set the gps_navfilter according to this ublox manual I found. After I changed the gps_navfilter to 8, the Pixhawk LED did turn green for a second but then went back to blue.
Since I can make the Pixhawk LED turn green with an older firmware, can I assume its a FW bug? If so, how can I help expedite the fix? Do I need to report it somewhere?
Thanks
RoboBill
@RoboBill,
Since I cannot duplicate your issue using the same ArduRover2 v2.47 beta 1 firmware, it might not be a firmware bug.
Do both of your GPSs show a flashing blue led as well as the red power led when you have been doing this testing?
I have asked Tridge and Linus Penzlien, one of our Developers, to take a look at your data log to see if he can spot anything unusual.
Regards,
TCIII AVD