LibrePilot Forum
Users => Vehicles - MultiRotors => Topic started by: Patrick40 on October 19, 2016, 09:12:58 pm
-
Help needed from a compleet newbie
Oke i connected the robocat to Librepilot.
Then i upgraded the firmware.
Then i did go to configuration.
And entered hardware configuration.
when i did come to the point where i needed to connect the lipo to the robocat, my computer shut of suddenly
After restarting my computer and hooked the robocat on Librepilot again, nothing? It does connect but no light's on the board?
In Librepilot, when in frimware upgrade it does connect but in the right corner it say's: Log Replay
The only buttons i can start are:
Upgrade and Upgrade and erase.
But these are not working, because it say time out.
All the other buttons are not working.
Any help welcome
Thx Patrick
-
Hi, Welcome.
Be sure you do not have a wiring issue, computer reboot while connecting the battery looks weird :)
If you get a timeout you should do a manual update
- Disconnect board from USB and battery.
- Hit Upgrade&Erase
- Connect board to USB
- Wait until the board reboot, after the flashing it may take around 30s
-
Thx for the answer
I did try that allready, but nothing.
I think i need to look at all the wires again, and search if something is wrong?
Don't hope i fried the board.
Patrick
-
...It does connect but no light's on the board?...
...in the right corner it say's: Log Replay...
Log Replay means it isn't seeing the board. That could be either a hardware or firmware problem.
Not even a power led on? The firmware has nothing to do with that, even with no firmware the power led should be on if the board is receiving power from either USB or the battery. Having the power led off would indicate either wiring problems or a bad board.
I don't see where you mention what board it is or how it's wired up. You might try disconnecting all the wires from the board so the only thing hooked up is the USB cable and see if that helps. Maybe try the manual update process f5soh recommended with a different USB cable and port on the computer.
-
Oke i found the problem!
Somehow i thought that the 2 connections below the 12v connections on the PB where 5v
It turnes out to give more then 12v when i put a multimeter on them.
I can't believe that i made that mistake :-[
It even say GND and VCC!
So i think that is also the reason that my computer stopped?
I use this board:
http://m.banggood.com/OpenPilot-CC3D-Revolution-Revo-10DOF-STM32F4-Flight-Controller-Staight-Pin-p-1000068.html
And this PB:
http://m.banggood.com/Matek-LED-POWER-HUB-5in1-V3-Power-Supply-Board-BEC-5V-12v-Low-Voltage-Alarm-Tracker-p-1019353.html
-
Maybe you fried some parts, there is 3 regulators on the Revolution board.
This can cause one part works and other not and something like sensors not responding create infinite reboot.
Here is the schematic:
https://github.com/librepilot/LibrePilot/raw/next/hardware/Production/OpenPilot%20Revolution/Revolution%20Schematic.pdf
Clone boards uses most of the time regulators that can handle 10V max.
Double check first the U2 regulator providing the VCC_ANA to sensors.
-
Maybe you fried some parts, there is 3 regulators on the Revolution board.
This can cause one part works and other not and something like sensors not responding create infinite reboot.
Here is the schematic:
https://github.com/librepilot/LibrePilot/raw/next/hardware/Production/OpenPilot%20Revolution/Revolution%20Schematic.pdf
Clone boards uses most of the time regulators that can handle 10V max.
Double check first the U2 regulator providing the VCC_ANA to sensors.
I seem to be in a similar situation, having accidentally run current from an esc through to my Revolution flight controller. I have no LED lights on either of the two flight controllers I managed to brick.
When you say to check U2, you mean to pass current into U2 on pin 1 and measure the output from pin 5? What about the other components in the circuit? Under microscope inspection, I could find no obvious physical faults with the flight controller.
-
Look at the schematic. Power comes from the usb connector, goes through the D1 diode pair, through L4, and then to pin 1 on each of the regulators (U1 and U2). Check that with usb plugged in there is 5v all along there. If not figure out where you lose it. If there is check the outputs of both regulators on their pin 5 for 3.3v. The power LED gets it's power from U1 pin 5.
-
1: power from external battery / Esc, around 5V
2: power from USB port, around 5v
3: voltage after dual diode (5V - diode junction)
4: voltage after regulator (3.3V)
(https://forum.librepilot.org/index.php?action=dlattach;topic=2492.0;attach=4575)
Assuming the green Led powered with Vcc from first regulator is off, that a start.
-
Look at the schematic. Power comes from the usb connector, goes through the D1 diode pair, through L4, and then to pin 1 on each of the regulators (U1 and U2). Check that with usb plugged in there is 5v all along there. If not figure out where you lose it. If there is check the outputs of both regulators on their pin 5 for 3.3v. The power LED gets it's power from U1 pin 5.
Thank you for the guidance, I'll go ahead with that right now.
In addition to the information from earlier - it's worth mentioning that the flight controller passes power through to an accessory OPLink Mini over the main port. I'll start a new thread if I'm still left confused. Thank you hwh.
f5soh - The green power LED is off on both boards, even in DFU mode. Thank you for the clear and concise directions, I'll work through them and do my best not to hijack the OP's thread.
-
Quick question for you guys. When Revolution is powered by 5v are the 3 regulators on the board supposed to put out 3.3v? I ask because I have two that are putting out ~3.3v and one that is putting out ~2 volts.
-
All regulators are the same, 3.3v output.
Check schematic: https://github.com/librepilot/LibrePilot/raw/next/hardware/Production/OpenPilot%20Revolution/Revolution%20Schematic.pdf
-
All regulators are the same, 3.3v output.
Check schematic: https://github.com/librepilot/LibrePilot/raw/next/hardware/Production/OpenPilot%20Revolution/Revolution%20Schematic.pdf
It seems my board is marked 'Revision C' - the default assembly instructions from the docs are different from my board layout. That said, I think I was able to figure it out despite the confusion.
1: power from external battery / Esc, around 5V
2: power from USB port, around 5v
3: voltage after dual diode (5V - diode junction)
4: voltage after regulator (3.3V)
(https://forum.librepilot.org/index.php?action=dlattach;topic=2492.0;attach=4575)
Assuming the green Led powered with Vcc from first regulator is off, that a start.
I have two boards with the same problem, so testing should provide clear answers that others may be able to learn from. From now on, referred to as board A. or B.
- Across 1) and 2) from my USB power Board A. 4v | Board B. 4.5v
- At 3) coming out of the diode pair is Board A. 4.5v | Board B. 4.5v
- At 4) on pin 5 of U1 Board A. 0.2v | Board B. 0.3v [/]
I assume from this that my reg at U1 is in need of replacement? U2 has 3.2v on pin 5 still.
Offtopic: Is there any good reason why the same USB cable/port/computer would deliver a .5v difference between the boards?
-
The difference can be due to a different load form the fried regulator.
USB ports are usually designed to provide around 1A
You can try to replace the regulator but expect others damages...
"Rev C" simply mean that a redesigned Chinese clone.
-
The difference can be due to a different load form the fried regulator.
USB ports are usually designed to provide around 1A
You can try to replace the regulator but expect others damages...
"Rev C" simply mean that a redesigned Chinese clone.
Thank you for the note about the Chinese clone designation on the design.
Would you say that the extent of the damage should be isolated to this area of the board, or are there other more complicated components that have likely failed? I can put together a Digikey bin and repopulate a whole area of the board if that's a more likely fix.
-
You can check the others regulators, one that power sensors and last that power the modem side.
the best option is remove regulators not working anymore and power the cpu side and sensor using an external 3.3v source.
This allow checking the cpu and sensors still working.
Powering only the cpu side should give some led blinking but boot fail due to sensor missing.