LibrePilot Forum
General Category => General Discussion => Topic started by: RC Madman on July 19, 2015, 06:46:13 pm
-
I was able to get a Nano from the first batch and have spent close to 30 hours trying to figure out it's issues.
It connects to GCS fine on my older laptop but has been super touchy configuring and calibrating. Would lock up the GCS when the reboot command is sent to the Nano and will not show GPS as connected even tho the GPS is powered on correctly and LED indicates Sat lock.
I did manage to get basic setting installed and bench test seemed fine but test flight did not go well. Hovered for about 2 minutes but was drifting badly and when I gave it about 65% the front motors cut out and it flipped upside down. I installed the Nano on a perfectly good flying quad using a CC3D so all parts were good to go before adding the Nano.
I ordered a second Nano and it should be here tomorrow so I will be able to see if it's a defective unit but in case it acts the same as the first I was hoping to find some answers if possible.
-
Hi, can you post here the .uav file?
I'll try to look at it and, if not me, definitely a developer will tell you if there is some wrong settings or if there is a possibility that the board is defective.
-
Thanks for the reply. Sorry I am not sure where to look for the UAV file?
I did save a UAV file but can not seem to figure out how to upload it?
-
Thanks for the reply. Sorry I am not sure where to look for the UAV file?
I did save a UAV file but can not seem to figure out how to upload it?
You can zip the file and attach to your reply. Clic on "+ Attachment and other options" and then browse to your zip file.
-
Thanks here you go.
-
Happy to see you are finally getting some help! 😜
-
Thanks here you go.
I had a quick look and found no particular problems.
I submitted the file to the attention of the developers for further confirmation.
-
Which OS is GCS running on?
-
I have it on Windows Vista 32bit, Windows 7 64bit and Windows 8.1 64bit. Both 64bit OS's GCS crashes when the reboot command is sent to the FC. It runs pretty well on the old laptop with 32bit Vista but that thing is slow so GCS is a bit sluggish.
I can not even begin to figure out what is conflicting with the GCS on my PC? Could it be hardware? I have a I5 3570k, 12gbs or ram, AMD 280x 120gb SSD HD and and 1TB SATA HD.
-
Can you try to run GCS with "-log gcs.log" as additional command line arguments and post the resulting log file after a crash.
Could help...
-
Thanks here you go.
Well, seems your board settings are ok.
Are you sure that your board is firmly locked to the frame or in his box?
On the gcs side, try to post the log file as suggested by filnet.
Open the command prompt and type these two lines followed by the enter key.
cd C:\Program Files (x86)\OpenPilot\bin
openpilotgcs.exe -log gcs.log
After the crash you can find the file gcs.log in the path C:\Program Files (x86)\OpenPilot\bin
-
Thanks guys, I will update with the log asap. The FC seems to be firmly attached to the frame. 3M double sided tape.
-
The FC seems to be firmly attached to the frame. 3M double sided tape.
Ok, take a look at the board inside its box too ;)
I think if tomorrow the other nano will come, we can narrow the field of suppositions.
-
The first crash log is right at the beginning of Vehicle setup when you have the option to "Erase and Update". The second log is skipping the Update and going to the end where you save.
-
How does this log look? A couple of the caution light kept going on and off while just sitting.
-
@RC Manman,
I have a (pre-production) nano that will not connect in windows 8.1, but everything works great on windows 10 tech preview. If you have a spare windows box you can still download Win 10 TP for free and it might speed up an old machine. Just a thought - may kill two birds with one stone so to speak.
https://insider.windows.com/
-
The first crash log is right at the beginning of Vehicle setup when you have the option to "Erase and Update". The second log is skipping the Update and going to the end where you save.
RC Madman, where do you take these crash logs? I cannot read them.
The file filnet asked for is named gcs.log.
It is created with the command suggested by filnet in the directory C:\Program Files (x86)\OpenPilot\bin.
-
Yes I used the code to create the logs. When I saved them I renamed them so they would be easier to find. I will try again.
-
@RC Manman,
I have a (pre-production) nano that will not connect in windows 8.1, but everything works great on windows 10 tech preview. If you have a spare windows box you can still download Win 10 TP for free and it might speed up an old machine. Just a thought - may kill two birds with one stone so to speak.
https://insider.windows.com/
No longer available for PC only Phones.
-
I tried again and this log file is not located C:\Program Files (x86)\OpenPilot\bin??
-
I tried again and this log file is not located C:\Program Files (x86)\OpenPilot\bin??
How are you launching the GCS?
In win7 if I launch it with the command prompt the file is generated...
-
When I press enter on the second command GCS starts. Once GCS crashes I look for the log file but it is not in that location?
-
Well Nano #2 GPS does not work either! Who wants some Nano's?
-
Well Nano #2 GPS does not work either! Who wants some Nano's?
Man, that must be the first thing I'll try when my nano comes!
But at this point, it might be a problem with win64/GCS...
-
When I press enter on the second command GCS starts. Once GCS crashes I look for the log file but it is not in that location?
I have it...
(http://imagizer.imageshack.us/v2/640x480q90/540/zfJKVa.png) (http://imageshack.com/a/img540/9871/zfJKVa.png)
-
Madman, you need to add the command line arguments as indicated by liftbag a few posts above.
Are you familiar with command line interfaces (CLI) ?
Once you get the gcs.log file, please send it along screen shots of the crash dialogs?
-
Well as I was about to give up I have seemed to figure it out?
The first Nano is defective. The second board works fine as to showing GPS info. I am finishing up and will get it out for a test flight.
I got 9 Sats indoors with Nano #2 and then tried the Nano #1 again just to be extra sure and it does not work.
I am also able to run right on through the setup on the 64bit windows desktop without a problem. Not one crash and I ran it a few times just to check.
-
I guess that´s good news. Who did you buy it from? I assume they´ll take care of you as soon as the re-stock.
-
I bought it from FPVline. I am not sure who would take the return seeing they don't have any to send me back?
-
Well you are entitled to a replacement or refund ;)
If you have the time, please still send us the gcs.log file and crash dialogs screen shots (with details shown).
A defective nano should not crash GCS... GCS should have reported some kind of error (would have been helpful in your situation... or not).
-
I will try and figure out how to get you those files.
All I know it that the difference when running the second Nano on GCS is night and day. Everything runs smoother and the best part no crashes.
I test flew Nano #2 and it flies pretty well aside from a pretty bad forward drift and the Baro bounces like a rubber ball! I did the freezer Baro calibration and retested and the same thing. I was super excited to get this new FC but now I am pretty disappointed.
-
Sorry you're having troubles. The boards do require a bit of tuning for each frame.
Maybe the Nano is not your cup of tea, nothing's automatic.
All I can say is I have had no issues with my Nano on a Toad quad with GPS. I've heard that GPS setup on a mini can be a challenge. Twist and braid, twist and braid.
And remember, the OP folks do this as a hobby, not to take over the world. And LibrePilot!
-
What do you mean by "bounces like a rubber ball"? The craft bounces?
-
What do you mean by "bounces like a rubber ball"? The craft bounces?
Yes it bounces pretty violently. I know I should see some up and down movement in normal Baro use but this does not seem normal. I am trying different tuning setting and it seems to be improving some. I will also add some foam which I was going to do before I installed it but some told me it was not necessary because it is in a case.
I flew again today in non-gps modes and it was better as far as the drift goes but I am not having much luck using a Non-OP GPS for GPS modes. I have a couple Neo 6m's and I am getting good sat lock (9) but I can only arm while connected to GCS. The motors do not sound "Normal" while GPS is engauged. I have other quads with other GPS FC's running the same motors that do not sound like this. I will continue to read up and see if there is something I may be missing.
A FYI I ran GCS all last night and today on the 64bit Windows 7 desktop without one crash with Nano #2??? Has to be something to do with Nano #1 being defective... My guess anyway.
-
Good luck with tuning those bounces out, I wish I could help but I´ve only flown CC3Ds (No baro) and my Nano hasn´t arrived.
-
The foam help a bit and it seems ok now but the drift is back big time and I was able to get the GPS modes "Working" by switching to the Flexi port. The sad thing is that it is out of control while it GPS assisted modes. Flip it to position hold and it banked hard right into a evergreen which saved it from a total!
Recalibrated everything once again and it did the same but the drift was much much worst in attitude mode non-GPS assisted??
-
Sorry you're having troubles. The boards do require a bit of tuning for each frame.
Maybe the Nano is not your cup of tea, nothing's automatic.
All I can say is I have had no issues with my Nano on a Toad quad with GPS. I've heard that GPS setup on a mini can be a challenge. Twist and braid, twist and braid.
And remember, the OP folks do this as a hobby, not to take over the world. And LibrePilot!
What GPS unit are you using?
-
I have a Nano also. It flew well before, but now I am having some real problems with it. When I erase settings and restore/save a working UAV file (usually via USB), I see the correct settings before reboot, but some of the settings are not stored permanently every time.
Now I have a case where the PFD flips upside down and right side up over and over. It seems to be doing something different each time I try to get it working.
It even has problems with the OP 15.05 rc8 that it used to work with.
Someone else reported that using OPLink with higher RF power made his act strangely. I need to look into that. It is also possible that it just doesn't save settings correctly in a reliable fashion.
I also find that having a signal coming in an incorrectly configured or even an unconfigured port will lock it up when you plug in the flight battery and power the other devices. Example: All I have to do to lock it up is to plug in my PPM receiver. Unplug the receiver and it comes back to life.
I will post back when I find out more.
-
I have found the to Nano be touchy to what voltage it is running on. I scratched my head for a long time and was about to give up when I went back to what seemed to work when I first tested the Nano when it arrived. A 1s (3.7v likely 4.2v as it was fully charged) along with being plugged into the USB seemed to run and configure the Nano without lockups. When it was running on a 5v UBEC powered by 4s or 3s flight packs and USB I had all kinds of issues. The UBEC could be dipping much lower than the 4.8v I tested on it before so? I changed to a 6v UBEC and flight pack power no longer causes issues while saving settings or running GCS in general.
-
I am running stock 5V (linear) BECs in the ESC's.
I will definitely add this voltage check to my list of things to test.
-
Saving Setting Problems
I finally got my Nano to save settings. It has been a while now, and I forget exactly what I did. I think I had more luck using my real PC than using my laptop, and with laptop, I have to reboot Nano and make sure that settings were still there, and save just the bad settings again? I don't have this problem at all with my laptop with my Revos.
I think that one of the problems only happens because of two issues and I need to research more to make sure all this is true:
- After erasing settings, the board will not boot up with just a battery because it knows that some settings must be changed. For instance Input and Output settings.
- Maybe my laptop USB power is not good enough to save settings reliably in Nano (but it works with Revo).
I want to save settings with the flight battery plugged in for good power, but I can't because it wont boot up with the battery plugged in. I think I tried both USB then add battery and battery then add USB.
Bouncy Baro Problem
I have that problem too. I am flying an F330 clone with 9 inch props and I think there is just too much prop blast, too close to the Nano. I packed a thicker foam inside the Nano case, and the bounces went away, but were replaced with big drift up and down and up and down (vertical oscillation). This setup appears to be very picky about exactly how much foam to use.
-
I was able to get Altitude Hold to work perfectly by adjusting Altitude and Velocity proportional on my Hoverthings Flip 385mm. In no wind it hovers almost as in PH.
-
Another thing that I found is a must to get your Baro to function at it's best is to do the thermal calibration.
I put it in the freezer for 5mins and once the temp rise starts to slow but not stopped I use a heat gun from a good distance as to not heat up the plastic and melt anything.
I was easily able to get 30c rise.
Once this is done adjust the settings above to fine tune the "Bounce" out.
Edit: I have been testing different props and motors on my setup and noticed a big change in Altitude Holds stability when I installed 8" props on my 385mm Hoverthings Flip frame. much improved flight. Rock solid AH position and almost completely bounce free. Amazing what a prop change can do!