V3.3
- Thread starter marchudson
- Start date
swatson999
Well-Known Member
- Joined
- Oct 6, 2010
- Messages
- 1,534
Or both...a la the TAWS stuff?
"Whoop whoop Pull Up"
- Joined
- Mar 23, 2005
- Messages
- 13,226
We considered allowing tones instead of a voice, and in fact we do use them for Angle of Attack. However, we have over 15 messages we can announce, and this means we'd need a lot of tones, some of which you would hopefully never hear. We felt that it was much easier for a pilot to understand right away what the system was telling them if it said "warning" or "Autopilot disconnect" then "be-doop" and "waah-zoonk". We also at one point reduced the voice messages so you got less unique messages and had to look at the screens more, but our flight testers said that was a step backwards.
We have consolidated many of the alerts into a few simple categories of "warning," "caution," and "message" which is the way the FAA likes to see things announced. So those are the messages we use to draw your eye to the text message on the screen telling you exactly what is wrong when it isn't one of the more common things like the autopilot telling you "trim up."
You can turn the voice off completely for individual messages at your discretion.
Fly with the system for a while and give us some feedback. We tried to minimize the chatter and make the messages clear, so that even someone that had never flown SkyView would know what the system was trying to tell them instead of just a cacophony of "ahh-ooog-bzzz-rumbama-blop-cachinga".
We have consolidated many of the alerts into a few simple categories of "warning," "caution," and "message" which is the way the FAA likes to see things announced. So those are the messages we use to draw your eye to the text message on the screen telling you exactly what is wrong when it isn't one of the more common things like the autopilot telling you "trim up."
You can turn the voice off completely for individual messages at your discretion.
Fly with the system for a while and give us some feedback. We tried to minimize the chatter and make the messages clear, so that even someone that had never flown SkyView would know what the system was trying to tell them instead of just a cacophony of "ahh-ooog-bzzz-rumbama-blop-cachinga".
- Joined
- Mar 23, 2005
- Messages
- 13,226
It's actually announcing the face you should be making when you're pulling Gs
Re: V3.3 Audio
Dynon;
I have alerts with my VP-200 and I'll say I like your warning far more at this point. Knowing what the issue is versus a "dong" or "check Engine" is far more useful for someone to know where to look to correct the alarms than having to search for what it is.
I agree doing anything less than you did would have been better than nothing but not much better. Youe flight testers were right on!
Thank you!
Dynon;
I have alerts with my VP-200 and I'll say I like your warning far more at this point. Knowing what the issue is versus a "dong" or "check Engine" is far more useful for someone to know where to look to correct the alarms than having to search for what it is.
I agree doing anything less than you did would have been better than nothing but not much better. Youe flight testers were right on!
Thank you!
- Joined
- Mar 23, 2005
- Messages
- 13,226
You can upgrade from any version direct to 3.3.
jbeaver
New Member
Problems updating to 3.3
I was previously running 3.2.2 and everything was working fine, but I'm seeing quite a lot of problems after upgrading to 3.3.
First, not all of the network devices are detected each time I boot the system (the list of detected devices each boot varies). Once, virtually all devices failed to be detected (see http://www.flickr.com/photos/26691727@N00/6817535740/in/set-72157629538041789/lightbox/ ). When this happened, the light on the EMS was blinking much more slowly than normal and the light on the ARINC box was off.
I'm also having problems with the ARINC box. Even when I am able to get the SkyView to see all of the network devices, the light on the ARINC box wasn't flashing (it was off) and there was clearly no communication between the SkyView and my GTN-635. On other boots, I've seen the light on the ARINC box be on solid while it is flashing normally on other devices.
The final problem I'm running into is audio related. This may not be new as the audio lines weren't connected prior to yesterday. The issue is that after the full screen Dynon logo disappears on boot, I get a series of very loud clicks and pops right up until the phrase "Dynon SkyView" is spoken. After that, the audio is quiet.
I was previously running 3.2.2 and everything was working fine, but I'm seeing quite a lot of problems after upgrading to 3.3.
First, not all of the network devices are detected each time I boot the system (the list of detected devices each boot varies). Once, virtually all devices failed to be detected (see http://www.flickr.com/photos/26691727@N00/6817535740/in/set-72157629538041789/lightbox/ ). When this happened, the light on the EMS was blinking much more slowly than normal and the light on the ARINC box was off.
I'm also having problems with the ARINC box. Even when I am able to get the SkyView to see all of the network devices, the light on the ARINC box wasn't flashing (it was off) and there was clearly no communication between the SkyView and my GTN-635. On other boots, I've seen the light on the ARINC box be on solid while it is flashing normally on other devices.
The final problem I'm running into is audio related. This may not be new as the audio lines weren't connected prior to yesterday. The issue is that after the full screen Dynon logo disappears on boot, I get a series of very loud clicks and pops right up until the phrase "Dynon SkyView" is spoken. After that, the audio is quiet.
Re: V3.3 issues
Being I need to install the database today to stay current, I am forced to install 3.3 so this is quite concerning. Anyone else having the issues Jason has? I assume he configured all the network, but I had this issue with a AP servo, and 3.2.2. Needed to configure both screens before it finally stuck.
With the audio I am thinking its a early model that is known to have the clicking issue.
Thx
Being I need to install the database today to stay current, I am forced to install 3.3 so this is quite concerning. Anyone else having the issues Jason has? I assume he configured all the network, but I had this issue with a AP servo, and 3.2.2. Needed to configure both screens before it finally stuck.
With the audio I am thinking its a early model that is known to have the clicking issue.
Thx
cperry
New Member
Installed 3.3 yesterday, along with the VPX license, no issues, love it! The only thing I couldn't figure out without the manual was how to get the flap/trim positions from the VPX on to the EMS screens...but now that I've read the manual, I should be able to handle it tonight. Voice alerts are fantastic...love the Homer comments above! First flight tomorrow! I hope...
First flight tomorrow! I hope...jbeaver
New Member
All of the network devices updated successfully and when they do connect, they show the correct software version.
- Joined
- Mar 23, 2005
- Messages
- 13,226
Jason - it does sound like one of your modules may have had an issue during the upgrade, and it may be affecting the network adversely. The ARINC 429 module is probably the one I'd be most suspicious of given what you've described.
I'd start by unplugging all of your modules, starting with your display + an ADAHRS, then work up from there. The LED behavior on the modules themselves are as follows:
Flashing Fast: The module is operating normally and is configured and communicating on a SkyView Network.
Flashing Slowly: The module is operating normally, but is not active on SkyView Network.
Off: The module is not receiving power (from a SkyView Network / Display)
On Solid - the module is receiving power, but is not operating normally.
I'd start by unplugging all of your modules, starting with your display + an ADAHRS, then work up from there. The LED behavior on the modules themselves are as follows:
Flashing Fast: The module is operating normally and is configured and communicating on a SkyView Network.
Flashing Slowly: The module is operating normally, but is not active on SkyView Network.
Off: The module is not receiving power (from a SkyView Network / Display)
On Solid - the module is receiving power, but is not operating normally.
jbeaver
New Member
I did a little more investigation tonight, and here's what I'm seeing:
I unplugged the ARINC module and powered up the SkyView system multiple times. Each time, all modules were present and working correctly.
I then plugged the ARINC module back in and powered up the SkyView system several times. Most of the time, all modules other than the ARINC module appeared on the network, but the behavior of the ARINC module was still inconsistent. On one try, all devices appeared as online when I accessed the network status page, but the light on the ARINC module was off. On another try, the ARINC module appeared as offline, but the light was on solid. On yet another try, all devices showed as online and the ARINC light was blinking fast, but when I entered a flight plan on the GTN, the SkyView HSI didn't show the course. I checked the light on the ARINC module and it was now off. A couple of times, all devices showed as offline, but I only saw this happen when the ARINC module was connected to the network
I also wanted to see if I could determine why I was getting so much audio clicking. If I connected the audio lines to either display separately, I didn't get any clicking. It appears to only happen if both displays are connected together.
I unplugged the ARINC module and powered up the SkyView system multiple times. Each time, all modules were present and working correctly.
I then plugged the ARINC module back in and powered up the SkyView system several times. Most of the time, all modules other than the ARINC module appeared on the network, but the behavior of the ARINC module was still inconsistent. On one try, all devices appeared as online when I accessed the network status page, but the light on the ARINC module was off. On another try, the ARINC module appeared as offline, but the light was on solid. On yet another try, all devices showed as online and the ARINC light was blinking fast, but when I entered a flight plan on the GTN, the SkyView HSI didn't show the course. I checked the light on the ARINC module and it was now off. A couple of times, all devices showed as offline, but I only saw this happen when the ARINC module was connected to the network
I also wanted to see if I could determine why I was getting so much audio clicking. If I connected the audio lines to either display separately, I didn't get any clicking. It appears to only happen if both displays are connected together.
I installed the updated firmware and it appeared to have wiped out my Magnetic Calibration, as it "cautions" me to do "user Mag Cal." Strange as I was hoping this was going to be a quick upgrade, which the software was, but getting it recalibrated will take time to go across my airport and do the compass rose again.
mmarien
Murray M.
bignose. Try the manual. Start at page 7-35 of the Pilots user Guide. Also page 7-27 for temporary waypoints.
Great job on the navigation software Dynon. I like the choice of format for the waypoint import.
Great job on the navigation software Dynon. I like the choice of format for the waypoint import.
- Joined
- Mar 23, 2005
- Messages
- 13,226
The update didn't wipe out your mag cal. This has been highly tested, and it doesn't delete cals.
What's new is the message for a missing cal. We never had this before, so it was non-obvious if a cal had never been done. It was even worse if you had two AHRS modules, where you may have only had a cal on one, and maybe your backup wasn't cal'd. We added the message because we had a lot of customers add a backup AHRS and not realize that they never calibrated the compass there.
Your heading performance will be no different before 3.3 and after 3.3, we're just warning you that it wasn't optimal before 3.3.
What's new is the message for a missing cal. We never had this before, so it was non-obvious if a cal had never been done. It was even worse if you had two AHRS modules, where you may have only had a cal on one, and maybe your backup wasn't cal'd. We added the message because we had a lot of customers add a backup AHRS and not realize that they never calibrated the compass there.
Your heading performance will be no different before 3.3 and after 3.3, we're just warning you that it wasn't optimal before 3.3.
Ham_Goulding
New Member
- Joined
- Jul 3, 2007
- Messages
- 44
I have a list of User Waypoints that I want to import into my Skyview. Can someone tell me how to put them into a CSV file on a Mac? Thanks.
- Joined
- Mar 23, 2005
- Messages
- 13,226
Start by creating a single waypoint on your display, and then export it. Then, you have a template to work with. From there, you can use Excel (or whatever Mac spreadsheet app you have. I'm sure it supports CSV) to add as many as you want in additional rows of the CSV file you've started with. Save (make sure it's still in CSV), then re-import into SkyView.
Actually, attached is a zip file that contains a CSV you can start with. It has Dynon and Mount Rushmore.
Actually, attached is a zip file that contains a CSV you can start with. It has Dynon and Mount Rushmore.