LibrePilot Forum
General Category => General Discussion => Topic started by: oink on March 01, 2016, 03:45:27 pm
-
Hi all.. new to CC3D. I have the atom unit, been trying to set it up. When I first tried, plugged the Atom into the usb and ran through set up wizard, everything went well, firmware flashed to board, ran through vehicle set up. ( fixed wing, elevons), did all the motor neutral and aileron set ups etc etc. When I got to the calibrate TX section, the very first time it worked on the throttle setting, then the whole calibration set up stopped recognising my TX. I tried for a while, then ran out of time and gave up.. Came back to it today to carry on, but my Atom is refusing to upgrade/erase firmware, and won't move past this part of the programme. It just times out and tells me to upgrade manually . When I use the cancel or disconnect button, libre pilot ( or open pilot, I have both installed) crashes! The Atom is displaying a solid green led and a slow flashing blue, Any ideas?? Have I screwed something up big time or is it just 'newbie' finger trouble?? Any help would be much appreciated.. Thanks..
-
Hi oink,
I assume you upgraded from OpenPilot to LibrePilot and flashed LP firmware.
1) Does GCS connect to the board ? Can you see Scopes -> Gyro / Accel sampling running ?
2) What it shows in Firmware tab (screenshot) ?
3) Do you have any other application running at the same time, that could potentially conflict or claim USB-Serial device ? You should not run two GCS apps at once.
4) About LED behaviour slow blinking indicates normal functioning http://opwiki.readthedocs.org/en/latest/appendices/bootloader.html#led-behavior
5) As a dirty walk-around for crashing, you might want to install Ubuntu on VirtualBox and try Linux version of GCS ? I know it sounds complicated, but I thought maybe it's some sort of problem with Windows drivers and that's why GCS is crashing, so using Linux GCS could potentially solve the problem. But of course it would be good if someone with debugging skills could reproduce it.
-
Hi Mateusz.....
Thanks for replying.. Right... I started out with open pilot, but today when i tried to work on it, it wouldn't flash the firmware, just kept timing out. I tried several times, some other advice said ( on manual instal rather than wizard) to click on erase and refresh first then connect device, that didn't work either. Before the board worked fine, flashed easily and when you went to the flight control page and tilted/rocked it the horizons moved correctly. It was just the TX calibrate that wouldn't work.. Today, the firmware won't flash, the horizons aren't moving and the status box is showing.. 'NO INPUT', I have been into scopes, i get the 4 screens up, one is scrolling, the other 3 are static, but there is no output indicated on any of them.
The only other thing that was running at the time was my email client, so pretty sure no conflicts or usb issues there.
After my failure with openpilot i installed Librepilot, but EXACTLY the same things happen. The firmware won't flash there either, the board lights up, shows briefly on the rx bar at the bottom of the screen, with one green square on the TX bar as well, the ''Disconnect' tab is lit, then the lights on the bar go out. If i click on disconnect or on cancel, the whole programme freezes.
I really don't wish to get into linux, windows confuses me enough without trying to get my head around another operating system as well.. Hopefully this is a bit more help??............... :'(
-
Hi oink,
No problem. So you were not able to flash LibrePilot yet, because it stopped working with OpenPilot right ? I suspect you might have corrupted flash memory somehow and bricked CC3D.
I would suggest to read this thread https://forum.librepilot.org/index.php?topic=208.0 read it carefuly and ask if you don't understand before doing something :) But flashing recovery image may help if it's flash problem. Recovery image should also clean up external flash memory where settings are stored.
-
Further info.. After reading the openwiki page you provided, i have checked my firmware, and gone through the procedure for reinstalling the bootloader. After I had done that, i attempted to reflash the firmware. it almost looked as if it was going to work, the blue bar went across the screen, but when it reached 100% it still said .. timed out.
I am getting an error message that says.... Could not enter DFU mode.
Unit is still displaying one solid green and one slow flashing blue light, which 'should' indicate the board is satisfactorily running..
-
Further info.. After reading the openwiki page you provided, i have checked my firmware, and gone through the procedure for reinstalling the bootloader. After I had done that, i attempted to reflash the firmware. it almost looked as if it was going to work, the blue bar went across the screen, but when it reached 100% it still said .. timed out.
I am getting an error message that says.... Could not enter DFU mode.
Unit is still displaying one solid green and one slow flashing blue light, which 'should' indicate the board is satisfactorily running..
Atom is like CC3D. Did you locate SBL pads on the board and shortened them ? Only shortenning SBL pads will allow entering dfu bootloader on STMF3 chips. Only Revo and Sparky2 has STMF4 chip and does not require shortenning those pads. Once you shorten pads you should flash ef image with bin extension using dfu-util.exe tool. That imagine contains both bootloader and firmware. So it's not necessary to flash firmware afterwards. After flashing is successful with dfu-util tool, desolder SBL pads leaving them not connected. Then connect board and it should boot normally.
Whatever you do with hardware like soldering, board must be powered off for safety.
-
MMM.. I've just read through that second article.... soldering pins together, for me at least, seems a recipe for total and utter disaster. I'm no great computer wizard, as you can probably tell, so what I'm hoping for is a fairly simple fix..... I certainly appreciate your help and guidance though, and will try MOST things.. When you talk about '''Recovery ''' is that the same as ' rescue ', or something completely different??
The way this is going it looks like I may well have damaged the board.. If so i will probably succumb to the mighty hammer technique and purchase another board, and this time try to set it up more carefully, not that I thought I had been careless the first time... :-\
-
Unit is still displaying one solid green and one slow flashing blue light, which 'should' indicate the board is satisfactorily running..
Slow fading blue led ? This means no firmware.
- Disconnect board
- Hit Upgrade&Erase button
- Connect board
- Wait 30s after flash end until board connect again.
-
Hi F5soh.. The blue was not fading, just slow blinking. But I did as you suggested, and it ran through the firmware instal, got to the 100% mark, sat there for a while, then displayed... " Timed out , unable to reboot. " The unit is currently sat there in the slow blinking mode .
-
Did you update the bootloader ?
Double check if the BL version is v4:
- Rescue
- Connect board
-
Yes... BL Ver is 4. I went through the rescue procedure but that doesn't seem to have done the trick. But I will try again. I am currently just doing this with JUST the atom connected to the usb, no radio Receiver connected to the unit, that should make no difference I assume? When I was trying to upgrade firmware earlier the rx was connected, There was an intermittent 'beep' from somewhere in the system, but i think that was coming from the esc as i don't believe the atom has any audio output for faults??
-
Right.... ran through rescue again...... it says firmware has been installed, but once again then fails to reboot and displays . timed out whilst rebooting..:(
-
[img] [img]
-
You should not have any beep from your board/vehicle without external power.
Board should be only powered by usb.
In your screenshot there is no firmware, only bootloader.
-
Ok.. well, it said it was installing firmware!..
The external power was only connected when the programe prompted me to do so, for the later set up procedures, ie. motor neutral point, servo set up etc..
-
Ok.. well, it said it was installing firmware!..
Obviously you miss something:
- Disconnect board, no power at all.
- Hit Upgrade&Erase button
- Connect board (after you hit button above)
- Wait 30s after flash end until board connect again, be patient
-
It still does the same thing. (SAYS) installing firmware, then says rebooting the board, sits for about 10 to 15 seconds, the blue bar goes clear and it displays a message that says, timed out whilst waiting for the board to be fully connected.. I fear maybe the circuitry is damaged??
-
After a rescue you should have something like that, not only the bootloader like in your previous screenshot.
(https://forum.librepilot.org/index.php?action=dlattach;topic=964.0;attach=1766)
-
This has happened to me and it was an easy fix, I bet your "circuitry" is OK!
Go to your CONTROL PANEL and click on the DEVICE MANAGER. Look for something like CC3D or COPTER CONTROL, Right click on it an uninstall it.
Afterwards follow f5soh´s instructions.
It will take longer as windows will reinstall the drivers but it should work.
-
;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D
A BIG THANK YOU LUCAS!!!!!
That worked FIRST time... the Atom is now happy again... Hopefully this time when I run through the set up screens it won't all go 'Pete Tong' when i get to the transmitter calibration section!..
::) Does a little dance around the room shouting Whoop Whoop!!..
-
>:( >:( >:( >:( >:( >:(
Well, the unit sorted it's self out, as i said before. Everything was fine, LED's displaying green solid, blue slow blinking. Scopes running, artificial horizons moving, motor and servo set ups fine UNTIL...... I get to TX calibration, As before, this just doesn't work, goes to the move stick page ( throttle) i move the stick but no input, and the unit STOPS working again.. I'm obviously doing something basically stupid here, but I'm damned if I can see what.. I've watched several YouTube vids and it all seems to flow easily.. Right now, I'm back at the stage where the unit will not boot.. times out whilst waiting to be connected. Feeling mighty frustrated.. :(
-
Let´s try to sort this out!
What Radio and Receiver are you using? And, under what protocol (PWM, CPPM, serial)?
Could you please post a pic of your RX to Atom connections?
How are you powering your Receiver?
Please post a screenshot of your Input page!
-
Hi Lucas......Many thanks for this..:)
Radio is 2.4 ghz HiTec Aurora with a 4 channel Minima Rx. Lipo is connected to esc, esc to channel 3 on Atom, atom to channel 3 (throttle) on RX. Connection protocol is ppm. ( just the ONE cable connection to rx)..
Pics attached, hope they are clear enough..
-
I would add that, if i take the Atom out of the system and connect all the component parts up just under straight control, everything works fine, so all of the other components are working fine. :)
-
Do you have another computer and USB cable that you can try this on?
-
You should use the pin8 with the PPM+OneShot
(https://librepilot.atlassian.net/wiki/download/attachments/2818090/CC3D_PPM_Oneshot.png)
-
Also from receiver Manual:
https://www.aircraft-world.com/dl-1114174/FRS-V8R4II-HITEC-MAN.pdf
1. Put your transmitter into link mode.
Usually this is done by pressing the button on the transmitter module and
turning on the transmitter.
2. Ensure that your transmitter is in non-telemetry receiver link mode.
This can be done by looking on the transmitter module’s status light. If it is
flashing Blue, it is in the correct mode.
If it is flashing Red, you will need to change mode. To do this, press the button
on the transmitter module for around 2 seconds. The status light should change
between the two modes.
3. Connect a jumper between the top pins of servo connector 3 and 4
4. Press and hold the button on the receiver and then power up the receiver.
5. While the receiver is searching for the transmitter module, the Green light on the
receiver will flash slowly.
6. Once the receiver is successfully linked to the transmitter module, the Green
and Red lights on the receiver will flash rapidly.
This should only take a couple of seconds and is usually instant. If in doubt, try
increasing the distance from the transmitter modules antenna and the receiver.
It is recommended to have the receiver between 50cm and 2m away from the
transmitter when binding.
Notes:
• When the receiver is receiving a signal from the transmitter (i.e. the Red light is
lit constantly) in PPM and RSSI output mode, the Green light will also be lit.
• The PPM signal is outputted on servo connector 1.
• The RSSI signal is outputted on servo connector 2.
• Do not connect conventional servos or ESCs to the PPM and RSSI servo
connector outputs. Doing so, may burn out and destroy the servo.
• Some devices may need a low-pass filter or buffer on the RSSI output. Please
consult the devices’ instructions or manufacturer for help or advice on this.
• To disable PPM and RSSI output mode, just rebind the receiver as normal.
Maybe i found a wrong manual but you are connected to output 3 or 4 ?
The PPM signal is outputted on servo connector 1.
and
Connect a jumper between the top pins of servo connector 3 and 4
-
@ the other Cliff... No, I only have the one computer, :-\ and I use the lead for other things so it is ok..
@ f5soh.. on all the videos I have watched for the atom/mini unit it only shows using the 3 wire lead, straight onto Ch 3. Does that diag you posted intend that the the white core in that lead is disconnected and the purple ,single, lead connected to the rx in it's place, or is it just not clearly drawn and the purple wire goes to another pin on the rx?? .. Sorry to be so dense!
-
F5soh.. the rx is bound to the tx no problem. in the pic the light isn't on because at that time the lipo wasn't connected. the pic was just to show the connection arrangement.. which is as described in this screen shot.. :)
-
Just follow the receiver manual, PPM need to be connected on output1 and jumper between 3 and 4
Read wiki:
https://librepilot.atlassian.net/wiki/display/LPDOC/CC+Hardware+Configuration
Pin8 and set to PPM+OneShot in hardware tab, need reboot.
You are actually sending a PWM signal into a unused pin or a pin that need PPM signal if set as PPM-NOOneshot, this cannot work
-
F5soh.. the rx is bound to the tx no problem. in the pic the light isn't on because at that time the lipo wasn't connected. the pic was just to show the connection arrangement.. which is as described in this screen shot.. :)
Thanks, i know the screenshot :)
You didn't mention flying wing, or i miss.
No issue you can use pin8 also , set PPM-ONeshot and didn't use oneshot for motor
But i'm pretty sure you don't connect your receiver correctly.
The PPM signal is outputted on servo connector 1.
Connect a jumper between the top pins of servo connector 3 and 4
-
oink, take a look at the image attached. (Nevermind I´m using frSky) You should bind the signals on channel 3 and 4 and connect Pin 8 on the atom to Channel 1 on your receiver (White Cable).
btw F5soh codes for LibrePilot and he recently updated the Wing Wizzard Setup, so you are getting help from the direct source :)
-
I think I'm are SLOWLY getting there.. lead from rx to atom now on input 1. a link fitted between signal outputs on 3 & 4. now, with everything powered if i pick up the model the control surfaces move, ( the wrong way, but that's just a side issue). I have set hardware to pin8_ppm+oneshot. The ref to pin 8 is still confusing me now though.. I still get nothing working on the TX calibrate pages though. :'(
I think the flying wing ref was right at the start of the thread.
-
PIN 8. lilac on the picture.
-
I think the flying wing ref was right at the start of the thread.
Sorry again, i answer some amount of questions here.
-
Okay guys.. I REALLY am trying to understand this, but I am failing miserably... I have fitted a jumper between the signal pins of outputs 3 & 4. Connected the red/black/white connector to output 1, as per Lucas's photo. when i pick up the plane the servo's chatter and move the controls, the horizons move etc etc. There is an intermittent beep from the esc, about every 10 seconds or so when the plane is sat still on the desk. The tx and rx are bound, but I only get one green bar up on the TX bar at the bottom of the screen and as before, the TX calibration screen does nothing, just sits on the ... move throttle stick.. scene. Obviously something isn't seeing the TX, or so I'm guessing. Hardware is set to ppm+one shot. baud rate 56000, .. As i said before, if i take the atom out of play and just connect everything direct it all works, so all the individual components are fine.....
It's just the calibration screen that I can't make work.. when i look at the flight data page, on the alarms box, the input bar is showing Orange, not green.. Beginning to get a headache now, from constantly banging my head on the desk.... >:(
-
Okay guys.. I REALLY am trying to understand this, but I am failing miserably... I have fitted a jumper between the signal pins of outputs 3 & 4. Connected the red/black/white connector to output 1, as per Lucas's photo. when i pick up the plane the servo's chatter and move the controls, the horizons move etc etc. There is an intermittent beep from the esc, about every 10 seconds or so when the plane is sat still on the desk. The tx and rx are bound, but I only get one green bar up on the TX bar at the bottom of the screen and as before, the TX calibration screen does nothing, just sits on the ... move throttle stick.. scene. Obviously something isn't seeing the TX, or so I'm guessing. Hardware is set to ppm+one shot. baud rate 56000, .. As i said before, if i take the atom out of play and just connect everything direct it all works, so all the individual components are fine.....
It's just the calibration screen that I can't make work.. when i look at the flight data page, on the alarms box, the input bar is showing Orange, not green.. Beginning to get a headache now, from constantly banging my head on the desk.... >:(
- Green input - Transmitter is powered, receiver connected and model is selected in OpenTX. Revolution is receiving pulses from Transmiter via connected receiver
- Orange input - Transmitter is NOT powered, no input signal received (or fail-safe)
- Red input - No channel input configured
By the way health statuses are best explained by your best friend Wiki https://librepilot.atlassian.net/wiki/display/LPDOC/SystemHealth
-
Post a picture again and config file here
File > Export UAV settings
-
Thanks guys.. I'm away for a couple of days, I'll get back to this after the weekend.. Thanks for persisting with me!! Much appreciated..
:) :) :)
-
There is an intermittent beep from the esc, about every 10 seconds or so when the plane is sat still on the desk.
This is a detail unrelated to your other Qs but for completeness... the 10 sec beep is the 'armed' signal.
-
Hi Mateusz.....
Thanks for replying.. Right... I started out with open pilot, but today when i tried to work on it, it wouldn't flash the firmware, just kept timing out.
I have recently rescued what I thought were three defective CC3D Evo boards - I found the the timing out is usually due to not having the USB driver functioning. It took a while and repeated rounds of Rescue and I even used appdelete ( iMac) to get rid of the application and downloaded LP and re-installed. It still came back to a time out until I got the USB driver sorted.
I don't know if its relevant but I used the bottom Firmware link and worked from there.
I am a bit new to all this - so maybe its a bit of newbie luck that got me there finally...
-
Guys, I found the solution!!!
It was easier for me because I had the same problem so I could do several tests and try the solutions mentioned before.
Turns out you're all barking at the wrong tree. The problem isn't the CC3D, it's the PC.
@f5soh, install OpenPilot on a different computer and you'll see everything will work correctly.
I don't know exactly what's wrong with my PC (it might be some driver but I didn't have the time to uninstall it yet).
I'll post more updates once I find it.