I recently started getting numerous "Bad ___ Health" warnings. When I roll back the FW to 3.1.1, they stop. Does anyone know what's up?I see that Bad Accel Health is a big topic right now. It may be…Continue
Hello,I'm not sure if this is the right place to ask this. I have my Bixler pretty much tuned but have noticed a long period vertical oscillation. It's very minor but shows up in otherwise great HD…Continue
I was having many problems with 3.1.11 MP release. So, rather stupidly, I updated to the latest beta. Most of my prior issues were gone, good.I do a pre-launch calibration after the accels and…Continue
"i have the same issue with my setup, i wish it could be possible for a user to select a minimum and a maximum values for the rssi in the mission planner so anyone could use their diferent brand radios and have some reliability in the reading…"
"I'm fairly certain on the Pixhawk there is no need to adjust the settings. I've never adjusted mine and the MinimOSD works fine. Of course, it won't hurt anything if you do change as recommended above."
"This is a fantastic find!! It explains my issues much better than the "micro-fractured" solder joints. This is along the lines that I suggested in an earlier post. Great detective work.
Since "shorting" the Vcc connection…"
First, I fly fixed wing but commenting, seeking help in a copter thread. There may be differences by virtue of the FW.
That said, my specific experience wrt "bad accel health" does not lead me to conclude there is a solder joint…"
Thanks for the input. Are you stating that the IMU failures have not been intermittent? When they fail, they fail hard and not soft? I guess I didn't understand it that way.
Further, by deduction, the failures or should I say warnings,…"
"You were not out of line. My point was simply I am not certain the root cause has been found. Maybe I just haven't seen all the facts and data. None the less, intelligent and polite discussion, including challenging hypotheses, makes for more…"
"Huhh? So if the problem is intermittent and one sends the log that happens to be when the accel is operating within normal limits, is it an okay accel? If only some small number of accels were affected by a solder joint anomaly due to an incorrect…"
"I'm also a EE. I've worked on many detailed Failure Analyses, as well. A cracked solder joint on a SMT device could show up as intermittent with vibration or thermal excursion. In fact, I have seen this before. One could stretch and say…"
"Are you saying only accel x acts up and not Y and Z? It's very strange that rebooting can clear the problem. Of course, I am not privy to the root cause of the failure, the manufacturing process that Craig has alluded to.
Your point is also…"
"Craig, et al,
I sounds like 3DR has determined the root cause of this issue and contained it. Can we assume that all Pixhawks that are currently shipping have been screened for the Accel anomaly?
"Today, I flew my plane with the same Pixhawk that had Bad ___ Health warnings. Latest MP and 3.2.2 plane FW. This time, I had only a bad AHRS warning. I believe this was do to the GPS not having sufficient sats and/or HDOP. The warning did not go…"
Thanks for the reply and the advice Steven. I *think* I've gone through your checks correctly. Just in case you're able to it would be great if you could let me know if there's anything obvious I am missing here. I've now tried 2 XP machined and 1 Win 7 laptop...
Symptoms: Steady Green LED’s so the units have binded. Units data read but won’t connect in Mission Planner 1.2.1 Mav 1.0
APM2 not connected via USB, although it works when it is.
Using Com 4 set to 57,600, or Com 13 on a Win 7 laptop.
Installed FTD2XX on XP and Win 7.
Via 3DR application;
SiK 1.5 on HM-TRP
SiK 1.5 on HM-TRP
Click reset on APM2 as some suggest. APM 2 powered by ESC, blue GPS lock ok. SERIAL3_BAUD: 57.
Both units flash red when reading. Upgraded Firmware on both.
You make some excllent points there. I will ensure all the settings are the same. With regards to the Port Settings I've set everything to the same speed, 57 across the board. MP can deffo read the radios so they are working which is encouraging. Power is set to 11 as I am in the UK. I'll pump it up to test though.
I dont get flashing red on the air side, so I wonder if APM2 is throwing data at it? When working does the airside start flashing red even before MP is connected? Or does it wait for the handshake and connection to be estabilshed before it starts sending data? I am wondering if I need to do anything to get the APM2 to start sending telem data to the radio.
The connections look fine, the TX/RX leads are crossed. Good point though, that would seem like the obvious problem.
Most interestingly you mention that you need to hit "connect" in MP, there seems to be conflicting info on this on the forums and even MP itself has a pop up saying it's not required unless using mavlink. The Com port and Baud speed must be set right as I am getting the settings from the radio's when I hit load. When hitting connect I get a timeout after 30 secconds. I've seen people mention heart beat messages but I've not seen where they are displayed.
Thanks again for all your advice, I'll try setting all the remaining settings the same, bump up the power, and try to hit connect more often. Failing that I've emailed the support team earier in the week so I hope they may get back to me at somepoint soon.