Frequency pass through from Aera or GPSMap
- Thread starter vlittle
- Start date
We think, but are not certain, that we have a fix for this issue for v12, but we'd still like to get a log of the behavior. It doesn't look like we ever caught a diagnostics log from you in our system. What day did you actually send it? If you could upload it again and put "case 177480" in the message area, maybe we'll get it on a second attempt. Zipping it up will reduce the upload time and reduce the chances that the upload doesn't make it because of browser/connection issues.
vlittle
Active Member
- Joined
- May 7, 2006
- Messages
- 540
Well, the plot thickens. After probing the Aera serial input into the SkyView system and sending it into Dynon, the next flight worked fine. The flight after that didn't.
Very frustrating. I can check the diagnostics in the serial port setup and everything is fine, the SkyView is just not recognizing or passing through the frquency info sometimes.
So this problem is still open while I keep looking for the root cause.
Very frustrating. I can check the diagnostics in the serial port setup and everything is fine, the SkyView is just not recognizing or passing through the frquency info sometimes.
So this problem is still open while I keep looking for the root cause.
vlittle
Active Member
- Joined
- May 7, 2006
- Messages
- 540
More info:
Powered up today, no joy on the passthrough. Manually powered down one screen and shazam, it worked!
Powered up the second screen and pass-through still worked.
Tried to recreate the problem by shutting the system down and up again, pass-through worked.
It looks like I am getting a random deadlock situation at power on. Somehow the two screens are interacting to block pass-through. Since it appears to be random, it's hard to replicate. Are there any procedures that can illuminate this better?
Vern
Powered up today, no joy on the passthrough. Manually powered down one screen and shazam, it worked!
Powered up the second screen and pass-through still worked.
Tried to recreate the problem by shutting the system down and up again, pass-through worked.
It looks like I am getting a random deadlock situation at power on. Somehow the two screens are interacting to block pass-through. Since it appears to be random, it's hard to replicate. Are there any procedures that can illuminate this better?
Vern
jakej
Well-Known Member
Vern
I've found some issues sometimes with pass-throughs with SV transponder ( hex code was changing randomly) & VPX too but not Aera 500, solution appears to be letting the SV's power up completely & then powering up the avionics.
HTH
Jake J
I've found some issues sometimes with pass-throughs with SV transponder ( hex code was changing randomly) & VPX too but not Aera 500, solution appears to be letting the SV's power up completely & then powering up the avionics.
HTH
Jake J
vlittle
Active Member
- Joined
- May 7, 2006
- Messages
- 540
Thanks, Jake.
I will try this. I may have to rewire a bit, but its a simple experiment. I have one SkyView with battery on the master bus and one on the avionics bus with the Aera. I will force the Aera and/or the Sl-40 Off until the SkyView systems are online. Right now the sequence is: SkyView 1, SL-40, Aera, SkyView 2.
If the experiment is successful, we'll have some real data.
I'm surprised that others are not complaining... Maybe my unique combination of power up sequencing or maybe folks are not familiar with the features of the Garmin GPS pushing frequencies.
Cheers, Vern
I will try this. I may have to rewire a bit, but its a simple experiment. I have one SkyView with battery on the master bus and one on the avionics bus with the Aera. I will force the Aera and/or the Sl-40 Off until the SkyView systems are online. Right now the sequence is: SkyView 1, SL-40, Aera, SkyView 2.
If the experiment is successful, we'll have some real data.
I'm surprised that others are not complaining... Maybe my unique combination of power up sequencing or maybe folks are not familiar with the features of the Garmin GPS pushing frequencies.
Cheers, Vern
A couple more troubleshooting thoughts:
Check and see if the pass through is working with the screens individually. Power up one screen, does it work? Turn off that screen. Power up the second screen. Does it work?
If one screen works, but the other doesn't then that screen might have a broken RX connection from the GPS or TX connection to the SL-40.
If it works in both cases, then we need to see if some of the fancier things we do to inhibit serial transmit from one screen at a time isn't working right. To test this:
Boot one screen and let it boot. Then, boot the next screen. Does the pass through work? Shut everything down and try again, booting the screens in the reverse order.
Also, can you email your results to support at dynonavionics dot com (where we're tracking our internal discussion of your issue). We'd like to migrate the nitty gritty troubleshooting over to there. In you email the subject line, include "case 177480".
Check and see if the pass through is working with the screens individually. Power up one screen, does it work? Turn off that screen. Power up the second screen. Does it work?
If one screen works, but the other doesn't then that screen might have a broken RX connection from the GPS or TX connection to the SL-40.
If it works in both cases, then we need to see if some of the fancier things we do to inhibit serial transmit from one screen at a time isn't working right. To test this:
Boot one screen and let it boot. Then, boot the next screen. Does the pass through work? Shut everything down and try again, booting the screens in the reverse order.
Also, can you email your results to support at dynonavionics dot com (where we're tracking our internal discussion of your issue). We'd like to migrate the nitty gritty troubleshooting over to there. In you email the subject line, include "case 177480".
vlittle
Active Member
- Joined
- May 7, 2006
- Messages
- 540
I had a long go at this before I saw this email. It appears to be about a 50/50 chance after booting up that this function does not work. Rebooting individual EFIS screens does not seem to help it, but rebooting the whole system does in some cases.
The TX lines to the SL-40 always work because I can send frequencies from either SV to the SL-40, but not from the Aera in all cases. Restarting the Aera does not help because I think the Aera serial port is still active when the Aera is powered down but still connected to the bus.
I'll run the test as above and send in the results.
vlittle
Active Member
- Joined
- May 7, 2006
- Messages
- 540
I emailed a complete analysis to Dynon on this issue.
One way to reliably repeat the problem is to power up one SkyView, then the Aera on its battery, then the second SkyView, com and Aera main bus. Fails every time.
Knowing that, I have a workaround but it would be nice to see if my unique sequencing is exciting some obscure deadlock condition that may have other consequences.
Thanks, Vern
One way to reliably repeat the problem is to power up one SkyView, then the Aera on its battery, then the second SkyView, com and Aera main bus. Fails every time.
Knowing that, I have a workaround but it would be nice to see if my unique sequencing is exciting some obscure deadlock condition that may have other consequences.
Thanks, Vern
jakej
Well-Known Member
Vern,
Just wondering - did you try my suggestion of powering up the Dynons first ? Result of that ?
Jake J
Just wondering - did you try my suggestion of powering up the Dynons first ? Result of that ?
Jake J
vlittle
Active Member
- Joined
- May 7, 2006
- Messages
- 540
My normal startup works fine... Boot d1000, start engine, then boot d700, aera, sl40 together. However, I then tested scenarios of simulated efis failure that did not operate as expected.
I have provided 24 scenarios to Dynon and will wait for their feedback before reaching any conclusions.
Vern
jakej
Well-Known Member
Waiting for the good news , Merry Xmas. ;D
Jake J
Jake J