LibrePilot Forum
General Category => General Discussion => Topic started by: MrFoo on February 18, 2016, 03:48:41 am
-
Hello! I recently acquired a Storm racing drone with the cc3d controller. I was able to get a few test flights in before I had a hard crash and now it won't work. I have reached out to the company I purchased it from and I am not getting much help. I have tried to connect to the Librepilot software but it doesn't appear to be connecting at all. I don't want to erase any settings that are already on there. I basically have a really nice paperweight at this point and have no idea where to go from here. Any assistance would be great at this point. Thank you in advance for any help.
-
I wouldn't be terribly concerned about losing your settings save maybe the PID timings which you can probably live without and come up with equivalent or better settings on your own. Try loading the board up in rescue mode and see if you can use it to flash the latest LP. I've found that I get better results with upgrades by wiping the board anyway. If it doesn't come up, congratulations! You have an excuse to upgrade to a Revo! :) swapping the boards either for a replacement CC3D or a Revo is actually pretty straightforward.
-
Hello! I recently acquired a Storm racing drone with the cc3d controller. I was able to get a few test flights in before I had a hard crash and now it won't work...
Won't work is a little broad a description. When you hook it up to your computer what happens? What lights on the cc3d come on, do they blink and if so how?
-
When I plug it up, the green light stays on and the blue light flashes quick for about 15-20 seconds. Then it goes into a steady on then off. From this video I saw about the lights it seems to be the "heartbeat disarmed" I also saw a guide about erasing the usb component device and reloading the driver. I don't see any components that relate to it to delete. I have tried this with the batter connected, disconnected, and the same with the controller. the tx/rx at the bottom don't light up. I click the connect button and nothing.
-
What are the symptoms?
Is it that the motors don't start at all anymore, or sth else?
-
What are the symptoms?
Is it that the motors don't start at all anymore, or sth else?
When I plug in the battery, the motors all do a small movement like they did before the accident. Other than that, there's no response.
-
When I plug in the battery, the motors all do a small movement like they did before the accident. Other than that, there's no response.
Ok, so first of all. You flashed it before with LibrePilot right ? and you could connected to GCS via USB ?
Then you were flying.
Now after a crash you can't connect to it via USB ? or did you do something to it after the crash ?
Anyway, if you could connect to it with GCS before crash and now you can't because of crash, then it's very likely that flight controller or part of it is damaged (maybe usb port), and you should replace it with a new one. Do you even see any device getting connected when you plug in USB cable ?
It could be also that you messed up something with your drivers on your computer at some point. Did you try another computer ?
-
I never flashed it. It came already programmed. The board is in a yellow case that had openpilot on it. It appears that program has been replaced by Librepilot and that's how I ended up here. It has a Devo 7 controller and RX701 receiver. I haven't changed any controller settings and from what there company indicated, they TX/RX are bound. But they are in Hong Kong and there is a bit of a language barrier...
-
I never flashed it. It came already programmed. The board is in a yellow case that had openpilot on it. It appears that program has been replaced by Librepilot and that's how I ended up here. It has a Devo 7 controller and RX701 receiver. I haven't changed any controller settings and from what there company indicated, they TX/RX are bound. But they are in Hong Kong and there is a bit of a language barrier...
Ok so you flashed it with LibrePilot. When you do that, you have to configure everything from scratch. Settings of OpenPilot are not compatible with the LibrePilot. Actually settings between versions are not always compatible. So you should have done full erase and upgrade before any attempt to fly.
There is a Wiki with documentation https://librepilot.atlassian.net/wiki/display/LPDOC/Firmware+Rescue
And thread about unbricking https://forum.librepilot.org/index.php?topic=208.0
But I would try first Wiki. If the reason you cant connect is crash though, then it may not help, but worth a try.
-
Are you sure the receiver is OK?
-
I didn't flash it at all. I just wanted to see what the current setting were. As far s the receiver, out appears OK it again I am not sure
-
Hi :)
I think communication was a bit shaky here: I think you think that Openpilot was replaced by Librepilot, not on your controller, but generally.
When you never flashed it, then you still have some version of Openpilot on it. This project is dead, and Librepilot jumped in into this vacance, continuing to develop the old codebase.
Now, in most cases, the ESCs produce some sound during initialization, at the moment when the motors slightly move. Did that happen happen before and disappear now? If there is a sound, is it the same sound as before or has it changed?
-
Cato, you are correct! It still makes the same initialization sound as it did before. The company contacted me a few hours ago and said to try this.
May I bother you to connect the CC3D controller to OpenPilot software and go to Input-> RC Input section and move the stick travel to see whether the radio controller action can reflect on the controller screen to test whether they are bound successfully. Many thanks.
I tried that but I don't see "input" anywhere on the program. For some reason, I seem to be missing something. Either my computer doesn't recognize this ESC is connected or I don't know how to connect it once I have the program open. I think I mentioned in an earlier post that I click the connect button ( in Openpilot in this case) and it doesn't seem to connect.
-
OK, first which GCS software are you using? If you still have the Openpilot GCS, then everything is fine. If you use the Librepilot GCS you will get a warning and need to be a bit careful. Do not change any values while running the Librepilot GCS on some old firmware. But it should be ok to take a look at some values.
So, now remove all your propellers from the quad. Do not go on if you did not do so. Switch your transmitter on, then start the GCS, connect your CC3D via USB to your computer, and power your quad with a battery, so that the receiver gets power. If all is fine, you will get a warning that your firmware is not up-to-date, and after a few second your controller should show up in the firmware tab.
If you get to that point, you can now go to the HITL tab, and try to move the sticks on your transmitter. The movements should show there (with a certain lag). If this is not the case, your connection between receiver and controller is somehow broken.
That should bring you so far as the supporter asked you to do. Please tell us your findings, then we certainly will get to the root of your problem.
-
Thanks for that info Cato. The company also responded with this video. https://www.youtube.com/watch?v=Xau0rCYcpmA I have tried this with Librepilot as well as the Openpilot v. 15.02.02. My computer doesn't seem to recognize the quad is connected. The cc3d lights up (from usb power). As you can see about 30 seconds into the video, the cc3d info pops up on the firmware tab. It doesn't do that when I try it. On my computer in the "connections" box at the bottom, there is not a USB option. The only 3 that are showing up is "serial:com3" "Logfile: logfile replay..." and "UDP:unconfigured".
With that being the case, would the next step be to test the wire continuity? The wires coming from the cc3d are bundled with other wires but do they run straight to the receiver?
-
- Disconnect board
- Hit Upgrade&Erase button
- Connect board
- Wait flash procedure and 30 seconds more for reboot / erase.
If you are using Bootloader v3, update to v4.
https://librepilot.atlassian.net/wiki/display/LPDOC/Firmware+Tab#FirmwareTab-UpdateBootloaderandUpdatefirmware
-
It just times out waiting on a connection. I am running Librepilot 15.09 and downloaded the cc3d bootloader. Also tried on OP as well. Same result.
-
If the following:
- Disconnect board
- Hit Upgrade&Erase button
give a time out, try another USB cable
-
Gotcha. I will have to find one somewhere. I had to dig this one up because of the style connection.
-
I got a new cable, the computer recognized it. I did the firmware update & erase and it gave me the following as you can see in the 1st image (firmware rev 1). I tried rescue, clicked open and loaded the "bu_cc3d.opfw" then flashed it next and got this (firmware rev 2) The setup wizard times out on the upgrade screen and says I will need to manually upgrade.
I am making progress, slowly but surely.
-
OK,
now, initially I thought it may be an issue with the Windows or connection. There are many bad USB cables out there, which do not work or do not work properly. As at some point your FC was recognized, the Windows driver seems to be ok (another possible issue).
For the update procedure, don't try any firmware files manually at the moment, you could brick your FC if you do it the wrong way. Instead use the procedure as said before in this thread:
- disconnect your FC from Computer and battery
- start GCS and click Update&Erase
- connect your FC within 20 seconds
If it still times out, try a cable of higher quality (cheep cables most likely won't work). The upgrade process should start automatically after a while. If it gives you an error then, just report back. Again, don't try any files you found, it may be the wrong one, causing the FC to be bricked, which would make the whole procedure more complicated. In detail: you tried to upload the bootloader. This is not necessary, as you already have version 4 running. What you need is the new firmware, this file will automatically be selected when you use above procedure.
-
Ok, I did the procedure and it seemed to take(no errors). I am not sure of the next step though. It shows connected at the bottom with 1 green next to Tx, the number keeps ranging from 24-120. The box in the top right that says "no link" changed to " log replay" but nothing comes up when I click it. When I power on the quad with battery, the startup sound is only 1 beep instead of 2. I have attached a screenshot of the firmware tab with the quad plugged into only USB power.
I bought the cable from Best Buy yesterday. Hopefully that isn't the problem.
-
The "only one Tx bar" looks a driver/windows issue.
try following steps from here:
https://librepilot.atlassian.net/wiki/display/LPDOC/Troubleshooting
-
Success!!! Now I am on the transmitter setup. I set transmitter mode 2. The throttle works, the roll animation is the right stick, the actual left stick is what sent it to the next one, pitch indicates right stick but moving either one gets no response and thats where I am at now.
-
Success!!! Now I am on the transmitter setup. I set transmitter mode 2. The throttle works, the roll animation is the right stick, the actual left stick is what sent it to the next one, pitch indicates right stick but moving either one gets no response and thats where I am at now.
I had similar issue twice, but I have 6 builds and it happened only first time on two of them. Not sure what was the cause as I can't reproduce this. But going back and forth in transmitter wizard helped. Just press back and couple of times and try again. What transmitter / receiver is that ? Is it connected via sbus/pwm/ppm ? I use Sbus on all my builds and FrSky.
Strange is that it didnt happen on other builds using the same transmitter receiver. So I considered it problem with cables or some interference, maybe you are too close to the receiver with your transmitter ? FrSky sometimes drops connection when you have transmitter too close to receiver.
-
Sometimes jitter on signal (wrong pot on radio usually) can do a wrong stick detection, just go back and try again.
This issue should be fixed for next release.
-
Mateusz, I am using a Devention Devo 7 remote and RX701 receiver. I tried going back, restarting my computer and still get the same result. Also tried moving the transmitter farther away and still no luck.
f5soh, I am not too sure what you mean by the wrong pot on the radio. Do you have any workarounds until the next release?
Just to clarify my process. I turn on the transmitter, plug in USB, plug in battery, turn on GCS.
I feel like I am so close to getting this working again and am itching to get it back in the air!!!!
-
Any ideas on how to get past this?
-
Power the board and transmitter on.
Go to UAVOBrowser and check the ReceiverActivity UAVO.
What do you see while you don't move sticks ?
You can also note every channel for all sticks and manually enter number on Input tab...
-
It looks just like the picture you have. When I move the right stick, it does not display a channel in the up/down or left/right movement.
-
So if you see no changes, there is another issue and you cannot detect or setup a input.
-
I was told by helipal to test the continuity between the RX and the FC, specifically the green cable. I tested the continuity between all cables and they all tested OK. Any other suggestions?
-
Is the receiver binded ?
Do you see a light on it when powered ?
Post a picture how you connect receiver and cc3d.
-
Sorry i'm lost now.
What working / not working while you start Transmitter wizard ?
-
This is how they are connected
-
I believe the receiver is bound. There is a solid red light that comes on when powered.
I am in the transmitter setup wizard. I am on the step where the sticks are being setup. I am able to move the corresponding left stick up and down according to the animation. The next stick is the right one. I try moving all sticks and there is no response on the screen and the setup can't go forward.
-
What do you mean with left stick ? Throttle ?
Throttle is detected and you can't go forward with others sticks ?
-
Correct
-
Can you post your config file ? File > Export UAV settings
Do you have some sort of mixing on your Rc Transmitter ?
Like flying wing mixer ?
-
I have attached the UAV settings.
I have no clue about any mixing or anything like that.
-
Try reloading the config attached.
- Connect all wires to receiver
- Power with external battery
- Power on your radio
Check the INPUT status in SystemHealth: Orange ? Green ?
-
The input tab is orange. It says the system may be in failsafe mode and failed to update one or more accessory channels.
-
If after checked you still got nothing about Receiver Activity you can ask for a replacement or try with another board.
https://forum.librepilot.org/index.php?topic=881.msg7245#msg7245
Go to Input tab and check if something move, refresh is slow so put full stick and wait change if any.
-
- Connect all wires to receiver
- Power with external battery
- Power on your radio
For nit picky completeness, safety, and to avoid confusion, 'power on radio' is #1. Correct?
-
For nit picky completeness, safety, and to avoid confusion, 'power on radio' is #1. Correct?
This allow failsafe testing :)
-
Unfortunately no channel shows when moving the right stick at all. Just to confirm, I should request a new CC3D board?
-
Feel free to ask.
Assuming there is something not working, maybe the board.
If you have a spare servo you can test every Receiver output to be sure its working fine.