Frequency pass through from Aera or GPSMap

[vlittle]

Up until release 11, frequency information sent from my Aera would be consolidated with freq info from the SkyView and sent to my SL-40. This was handy because the Aera automatically selects the nearest airport in flight, or the source, waypoint or destination on a flightplan. The SkyView would also work and I could push frequencies from either source.

Now, it seems that the SkyView is now ignoring the external freq info and only sending SkyView freq info to the Com. I have a source selector switch and I can select either the Aera or SkyView, but I no longer get the consolidated info from the SkyView .

Has something changed?

Vern

 

[Dynon]

Not sure. Will check with the dev team.

 

[Dynon]

So nothing should've changed there. Can you take a Dynon Diagnostics File within an hour of experiencing this issue? I'll PM instructions on how to get it to us.

 

[vlittle]

So nothing should've changed there. Can you take a Dynon Diagnostics File within an hour of experiencing this issue? I'll PM instructions on how to get it to us.

I have one more thing to do... I need to load hires terrain on the second screen and try again. That's the only inconsistency between screens right now.

Vern

 

[vlittle]

Zipped file sent.

I also checked the behaviour with both screens with identical databases... problem still exists.

I will check the serial port configuration to see if something got corrupted with the load of version 11.

 

[Dynon]

Vern - we're not seeing your diagnostics file. Did you send it via our upload tool or via another method?

 

[vlittle]

Well, the problem has been solved by some detailed wire tracing. Turns out that the SkyView #2 wiring harness had two wires crossed in the connector that plugs into the AXIS-25A.

I had a stern discussion with the avionics guy who installed it recently and sent him home for a nap. Everything works now, sorry about the alarm.

Blue/violet crossed with Blue/green as I recall.

Turns out that it depended on which SkyView took control of the serial port. One worked, the other didn't. Your onboard diagnostics proved to be useful.

Thanks, Vern

 

[dynonsupport]

Vern:

Glad it got sorted out.

The Tech Support guys have a quick test for serial port issues in systems with multiple displays:
1. Leaving one unit, on, turn one unit off. The serial port control passes to the one that stays on.
2. Then reverse that. If it works on one display, but not the other, the one that it works on has the serial port wiring correct.

Well, the problem has been solved by some detailed wire tracing.  Turns out that the SkyView #2 wiring harness had two wires crossed in the connector that  plugs into the AXIS-25A.

I had a stern discussion with the avionics guy who installed it recently and sent him home for a nap.  Everything works now, sorry about the alarm.

Blue/violet crossed with Blue/green as I recall.

Turns out that it depended on which SkyView took control of the serial port.  One worked, the other didn't. Your onboard diagnostics proved to be useful.

Thanks, Vern

 

[vlittle]

Vern:

Glad it got sorted out.

The Tech Support guys have a quick test for serial port issues in systems with multiple displays:
1. Leaving one unit, on, turn one unit off. The serial port control passes to the one that stays on.
2. Then reverse that. If it works on one display, but not the other, the one that it works on has the serial port wiring correct.

Well, the problem has been solved by some detailed wire tracing.  Turns out that the SkyView #2 wiring harness had two wires crossed in the connector that  plugs into the AXIS-25A.

I had a stern discussion with the avionics guy who installed it recently and sent him home for a nap.  Everything works now, sorry about the alarm.

Blue/violet crossed with Blue/green as I recall.

Turns out that it depended on which SkyView took control of the serial port.  One worked, the other didn't. Your onboard diagnostics proved to be useful.

Thanks, Vern

That's essentially how I found it. Thanks formthe help.

Vern

 

[vlittle]

Well. the plot thickens.  I can preload standby frequencies either from my Aera or the SV (pass through).

Unfortunately, the very handy and useful preload of the 'recall' list on the SL40 does not work with the SV.  I am used to the Aera pushing all the frequencies for the nearest (or flightplannned) airport into the SL40 memory so that they can be cycled through using the SL40 knobs and displayed by name.  With the SV in the loop, this capability is lost.

I have firmware 11.1 and current Pocket FMS databases.

Also, the SV does not use this capability in the SL40 at all, which makes the workload much higher because of the manual selection required to push the frequencies.

So maybe I'm asking for a feature enhancement here, but I swear it used to work fine until recently.

Thanks, Vern

 

[Dynon]

Basically, any data coming from a NMEA device (like your x86 or Aera) that looks like it's bound for an SL30/40 etc is supposed to get passed along. So there might be something up here. Can you play with it and get us a dynon diagnostic log? If you can, upload it here. Put "case 177480" in the message section.

As for the nearest list, why not just use SkyView's nearest list and then shoot the frequencies over from the airport COMMs tab? (I'm guessing "fewer button pushes via the SL40" might be the answer?)

 

[vlittle]

I'll send a diagnostics log. In the meantime, here's the problem with the SV implementation...I have to click the Info tab, select the airport, select Comms, select a frequency and push the button. Leave the window open and obscure the map in order to select other frequencies as I approach the airport.

Compare this with... Aera automatically pushes nearest or flight planned airport info to the SL40 memory, ready for selection by dialing the SL40 knob. No windows open, just happens.

I will try changing the Aera from a Position to a GPS source or vice versa and try again.

Vern

 

[mmarien]

The single frequency push works for the Garmin GPS devices also. On my GPS495 I select any frequency and press the enter button. It places the frequency in the STBY on the Garmin radio. It doesn't blank out the SV MAP page if that is what you are looking for.

Personally I like the automatic push that Garmin does, but once in a while I push a single frequency. Handy for monitoring AWOS on the way by.

The iCOM A210 gets the DTO/NRST frequencies but the single frequency push doesn't work.

 

[rvator51]

I have to push twice on the button to transfer the frequency to the Icom A210. I have reported it before and Dynon is looking into it.

 

[vlittle]

The single frequency push works for the Garmin GPS devices also. On my GPS495 I select any frequency and press the enter button. It places the frequency in the STBY on the Garmin radio. It doesn't blank out the SV MAP page if that is what you are looking for.

Personally I like the automatic push that Garmin does, but once in a while I push a single frequency. Handy for monitoring AWOS on the way by.

The iCOM A210 gets the DTO/NRST frequencies but the single frequency push doesn't work.

I can push single freq from either source.  To get the automatic group push to memory, I have to switch my SL40 input to the GPS and leave it there.  Kind of defeats the whole purpose of having map software in the SV if I have to depend the GPS for this.  The SV is somehow blocking the group load when it is in the loop.

I am running more experiments on this.  The combination of two screens, one with a Map trial license and a PFMS database and the other no license or database may be an issue.  I'm not sure that Dynon has tested this configuration.  I added my second screen after my trial map expired on the primary screen, so i just run the map on the second screen.

Vern

 

[mmarien]

I have to push twice on the button to transfer the frequency to the Icom A210.  I have reported it before and Dynon is looking into it.

Does this work for single frequencies to the STBY or just the whole airport push that you can use RCL to load to STBY?

 

[vlittle]

Here's some more info. I powered up only the EFIS with the map license and PFMS data and the Aera operating. The SL40 would respond to frequency pushes from either the Aera or SV. It would not, however group load into the SL40 memory. Switching the S40 to the Aera and I can get the group loading

I betcha there's a bug in the SV software that is filtering the group loads. May be a limitation of the PFMS data.

Vern

 

[vlittle]

I uploaded the log file. One correction, it's SW 11.0.

Vern

 

[rvator51]

I have to push twice on the button to transfer the frequency to the Icom A210.  I have reported it before and Dynon is looking into it.

Does this work for single frequencies to the STBY or just the whole airport push that you can use RCL to load to STBY?

This works for the single freqs to STBY. It will not do the whole airport push using Skyview. When I had a Garmin 496 hooked up , I could do the whole airport push and use RCL.

 

[mmarien]

This works for the single freqs to STBY.

The single frequency was a missing feature when the A210 was connected to a Garmin GPS. Great to know it works with Skyview even though it takes a double button push.

I was seduced by the stereo in the GTR200 so traded in my iCOM A210 last winter.