![]() |
Update
Well, the box will be shipped back to Dynon tomorrow. By the way, Bob Mills updated his this afternoon with no problem (and I'm actually using his D100 for a trip this weekend because mine's TU). Here's the (short) story: Connected to D100, checked firmware version (I do this to confirm that I have good connectivity). Ran the backup program and got good backups (I think). Started the update from 5.2 to 5.4. While watching, I kept seeing errors go by, and the program would redo the errors, then go onto the next sectors or blocks or whatever. Maybe 10% into the update, it just failed with the yellow screen of death displaying. Tried reloading software, restarting update program etc. all to no avail - problem seemed to be that I could no longer connect to the D100. Called Mike at Dynon who advised to kill all power to unit (including battery backup) and start over. Did this and established connectivity, tried software update again and got errors and crash again. Tried a couple more times, no luck. Called Mike back and he was looking into what might be the cause.
Meanwhile, I went to work for a couple hours. I redownloaded the Dynon Support program, thinking that the original might have been corrupted or something. Headed back to the airport later this afternoon. Dynon dead - stone cold hard dead. Checked all my electrical connections, power etc. Not a wiring issue that I could tell. Pulled internal battery. 16.5V so battery is not dead. No clue at this point what the problem is/was, or why D100 went dead. Frustrating to say the least, as I am headed to CO from Reno tomorrow and was hoping to test the new autopilot features. Fortunately, Bob Mills lent me his D100 for the trip, so at least I can still go, but his D100 is running 5.4 and my D120 is running 5.2, so they're not talking. I've no clue what the autopilot servos are running at this point. Not the end of the world.... I'm still planning on testing the new configuration of my APRS. My lesson: don't try updating software the night before a trip.... greg |
Quote:
After trying many things upon arrival to resuscitate Greg's "brick", as Brian appropriately named it, we threw in the towel, got the RMA and did the swap. My update to 5.4 went through first try, as Greg mentioned. Different computer, different cable than Greg's. My cable is a Radio Shack USB to serial converter, and Greg uses a USB to 2.5mm (maybe 3.5mm) jack that he wired up quite slickly in his panel. We looked at that jack to see if it or the wires were suspect, but all looked good, and updates have been successful via that jack several times in the past. One difference in our procedures was that after detecting firmware (I do that to check comms too), Greg did the backup via the separate backup selection in the drop down menu, then started the update separately. I just went straight to the update selection, and said yes to "Do you want to create an update". Using that method, after the backup is saved, the update automatically runs. It shouldn't make a difference, but its just noted FYI. Greg will run my D100 non-networked into his DSAB for a couple of reasons. First, we did not want to try a 5.4 update on his EMS120, just in case his cable or computer was the cause of the failure, and risk him losing his EMS and his CO trip. Second, he would have had to run the update program via his computer on my EFIS to get to his servos, and we were concerned about making a second EFIS brick. And third, if he configured his network with my D100 as the bus master, he'd have to redo all of that again with his unit (he may have to anyway after the fix), and I'd have to do it with mine upon return (so he saved me some work!) He'll have to click off the DSAB warning upon start up, and won't have an AP for the trip, but he'll at least have an EFIS and an EMS, and his 496 was communicating with my EFIS, so he'll have an HSI for the VFR X-C. Just figured I'd dogpile to give folks some more data points, including my successful update to 5.4 for my D100, D10A, AP-74 and two SV-32 Servos. Question for you Brian in a seperate post to follow. Have a great trip Greg!! Cheers, Bob |
Brian,
Some great info here from you! I read the manual last night before I did my upgrade, and still have a few questions. I need to go on the Dynon forum to see if there are further explanations for the adjustments, but hope I can ask a few here since you're just out of beta-land. I will spend some good time testing and tweaking mine as well (when it gets back from CO), but thought I'd try to leverage your recent experience (I know I won't be alone in that desire! :)) I see you've dropped the Tq of the SV-42, then gone up on the pitch gain. Is that opposite adjustments? I know you may not need all the Tq from the bigger servo, but wondering if the two adjustments are similar...perhaps P gain is micro Tq? Or is P Gain an error tolerance adjustment for how far off alt before a correction is made in level flight. ALT GAIN also seems to be an error tolerance setting. but this time for level offs. Is that how you see it? VSI GAIN seems similar, though the adjustments are opposite (whether to INC or DEC for overshoots or early levels). Did you get more detail on these adjustments? Pull Rate makes sense...that's been one of my dislikes at times, so this may be a very nice tool! The two G Error adjustments confused me a bit. For gain, still trying to figure out the difference between "vertical speed changes are not smoothed enough" and "ride is too harsh", which call for opposite adjustments. Do you have a "dumb pilot Bob" way of describing that adjustment? :) The last one G Error G limit, seems self explanatory as well, and appears to be the cousin of pull rate. I noticed you adjusted the first two and left the others alone, and that the manual says to adjust them top-down, and stop moving down when you are happy (paraphrase). Did you find that the AP pitch mode was vastly (or nicely) improved out of the box on the default settings, and those minor tweaks were all it took to make you smile big? In other words, did just adding the new adjustments and using the defaults found in beta testing make for a large leap in pitch performance? I figure you played with all the settings along the beta trail...did the lower ones have smaller effects than upper settings, or did they have a more dramatic impact, and are better left alone unless really necessary? I know that's a lot of questions (probably over-anal-yzing), and much may be answered when I fly it, but I appreciate any illumination/clarification you may have from your test experience. If there is a Dynon discussion that adds detail to the manual, please do point me (us) there. Thanks for sharing your numbers and your experience! You da man!! Cheers, Bob Quote:
|
Bob, See reply below in blue...
Quote:
|
Brian and others,
In reviewing my post, it might seem that I am beating on Dynon. I'm not. I mostly wanted to post so that folks are more cautious than I am in doing the update. I am really looking forward to trying the new autopilot software and just got unlucky with this upgrade (or maybe there's a fundamental problem with my D100 that needs attention anyway). Guess I'll just have to plan another trip to test it when it returns..... cheers, greg |
No problem Greg, they will get you fixed up!
Flew from Kmor to Kchs today. AP worked great!!! |
Thanks Brian...great info...again!
I'll do as you did, try the default, and work top down as needed to dial it in. I don't need to play with the settings just to see what they do. Well, I like to tinker, but I know to not fix what aint broke!! ;) I'll respect that g-limit setting as well...no need to allow it to yank and bank...that's my job! :D Thanks again! Greg, how'd things work enroute to CO today? Cheers, Bob |
Bob
Your dynon worked fine though the AOA seems set too high ;). Aprs worked fantastic the entire trip if you check the track it got hits everywhere except on the ground. Glad we changed settings! Headed for LXV tomorrow and will meet up with Ron Lee enroute at Salida and then do some photos enroute to LXV. Having lots of fun! Greg |
This is not a great photo but this is Greg's plane heading north in the Buena Vista (KAEJ), Colorado area heading to Leadville.
![]() |
Has anyone used the autopilot to fly an approach? I just used mine today to fly the ILS and it seemed to S turn down the localizer course. I have yet to adjust all the gains and such, so they are still stock.
Hand flying the ILS, the dynon worked very well and I'd be comfortable going to mins...I just need to get the autopilot tied in correctly :) |
| All times are GMT -6. The time now is 08:39 AM. |