suggest hmc5883 and lsm303d failed to start, can’t seem to start them from the command line either
That is a bit curious.
Have these 2 sensors packed up?
I doubt it
Or is this a symptom of a failed firmware update? I’ve downloaded px4io.bin onto the microsd card but there are no indicators that the firmware has been updated.
No need to put px4io.bin on the SD card as the code is automatically loaded out of ROM FS now.
It will automatically load at startup as well, but that relies on having compatible FMU and IO code installed in the first place. If they are not then you have to do the update manually.
Load copter or plane and the power up while holding the safety button. That will force the px4io.bin to install from ROMFS and should resolve the issue.
It will automatically load at startup as well, but that relies on having compatible FMU and IO >>code installed in the first place. If they are not then you have to do the update manually.
Ahhh, now this might be where the problem lies. How do I update FMU and IO code manually, and which versions are compatible?
I have loaded the firmware from QGroundcontroller, but at the end of that I get some very odd behaviours. The Pixhawk starts, but the startup tones are very different to the tones on the wiki page and the main LED is flashing slowly a bright blue. Sometimes it connects to QGC (and can be armed/disarmed) or MissionPlanner, sometimes it doesn’t. Sometimes the accelerometers work, sometimes they don’t.
Does this need to go back, has something internal failed? Or is it a software compatability issue?
Try loading the stable firmware from mission planner and then follow Craig’s instruction:
Ta for the info, but yes have tried that many times with no success. Looks like the Pixhawk is now a paperweight, will have to investigate returning it, it would be interesting to find out what went wrong and failed. We have a spare, but obviously don’t want the same thing to happen.
Hello, i have the same problem.
the building of my setup finally completed and now the pixhawk won’t boot! it just have worked fine the whole time.
I have found out when i unplug the I2C from the 3dr ublox it will boot…
What could be the problem?
Hi, I have the exact same problem as hangie here I think. Was there ever a resolution to this or did you send it back to manufacturer?
My Pixhawk initially worked well for a couple of days, and then spontaneously started being less functional (it suddenly stopped recognizing the rc receiver for example) and it now doesn’t seem at all happy.
I have tried flashing it every which way in QGC, APM Planner 2, Mission Control, all to no avail.
It starts up with promising tones, but then interrupted by two long low tones. The PX4IO lights no longer come on apart from the green power one. Checking logs on the SD card there is always something along the lines of “PX4IO board not found” or “PX4IO update failed”.
Hardware error? Strange if so because it was working fine a few days ago.
Maybe there is not enough power from the computer USB port. If possible, try a powered USB hub or connecting the power module to the Pixhawk, then flash the firmware using mission planner or APM planner. Finally format the SD card and follow Craig’s instruction.
I have tried that. I Re-flashed arduplane onto it by plugging a battery in as soon as I had connected the USB back into it, and then after it finished, I disconnected, formatted the SD card, inserted SD card, rebooted pixhawk on battery only (not uSB) with safety switch down and started it. It didn’t give successful firmware noise, and inspecting the sd card the APM/boot.log file says “no PX4IO board found”
Hi Marco
We have already covered off on this one in another thread. I have sent you replacement and I would be interested to get this one back. I suspect it suffered an over voltage event and the board has been damaged.
Cheers,
Yes Craig, is possible, i use the new “3DR Power Module” prototype with this Pixhawk, but i’ve check the output voltage before connect the plug to the board and is right.
I’m having a similar problem, when I first got the pixhawk it worked fine with the external GPS, now I keep getting the two beep error tone, only way it will boot up normally is if I diconnect the I2C connection to the gps, I have tried different cables, used the I2C splitter and even tried to update firmware and the startup with button trick. Can’t get the pixhawk to start up, note I did leave in the gps connection when I disconnected the I2C cable and it does boot, so looks like in the I2C…
Figured out this problem, when I installed the extended GPS mount it came with two cables on a 5 pins and the other with 6, I had the 5 pin cable installed and based on what I read in another thread here I swapped cables and now no problem starting up with the GPS…
Next issue is the Pixhawk with the SimonK flashed ESC’s, looks like I am experiencing the sync issue I have read about in other posts…
I just bought a pixhawk from Canadadrones.com. Received it earlier in the week and had the pixhawk all working on the bench. The 3DR power module (5.24V) was providing power to the unit with X8R via SBus plugged into RC port. I also had a Turnigy plush 60A ESC that was outputting 5.2V on Ch.3 on the board, RFD900 on the Telem 1 port, 3dr gps/compass, and 4 servos plugged into 1, 2 4, 7. Everything working like a charm. Next thing I know my transmitter started beeping like it lost the RX. I noticed the power led disappeared from the RX and MissionPlanner reported loss of signal. I repowered the pixhawk I could not get anything working again and I had the same tones and leds as piersc, except for the IO B/C led was solid red and the IO ACT is solid blue. I too inspected the log file on the SD card and it stated ‘PX4IO board not found’. I measured the voltage coming out of the RC port on the Pix hawk and it is only showing 3.4V. After I had a small panic attack and came back to do some further troubleshooting, I measured the voltage again and it was now only 2.0V out of the RC port? the Pixhawk also seems to have a slight burnt electrical smell to it. gulp!
What has happened? What should my next steps be…except away from the window. Your help is greatly appreciated.
I likewise have a pixhawk that fails to start. I tried all of the above methods, none worked. I did a full start up diagnosis and have determined that my ms5611 is failing to start. Also, the mpu6000 starts fine, but sometimes other tests say that it fails. Here is the bootlog,
[size=85]Running rc.APM
binfs already mounted
nsh: rm: unlink failed: No such file or directory
Detected FMUv2 board
[uorb] already loaded
uorb started OK
px4io: already loaded
PX4IO board OK
CRCs match
PX4IO CRC OK
Setting FMU mode_pwm
<fmuservo> MODE_6PWM
<fmuservo> set_pwm_rate 0 50 50
Starting APM sensors
[MS5611_SPI] on SPI bus 1 at 3
<MS5611_SPI> crc failed
<MS5611_SPI> prom readout failed
ms5611: interface init failed[/size]
Having used Mission Planner, APM Planner 2.0 and QGround Control to try and shake things loose, I decided to erase the flash and load a new boot loader version (4) onto the pixhawk, then load firmware for the FMU and IO board using Mission Planner (it seemed most reliable). Having done this, it reports that I am up to date and it still fails to initialize. I contacted 3DR and asked for help, they offered me a discount on a new unit and told me that could not repair the one that I have. Does anyone know a good place to source the ms5611? I’m going to try and repair it myself.
