GNS430W and SV-ARINC config

swatson999

Well-Known Member
Joined
Oct 6, 2010
Messages
1,689
Ran out of time and battery juice before the Garmin got a fix today after powering up the SV1000, ARINC module and 430W all together for the first time, but in the meantime, here's my question:

There are a lot of setup screens on the 430W.  The Skyview installation manual says to set the following

"Main AIRNC (sic) Config" page
In 1: High | EFIS/Airdata
In 2: Unused by SkyView...
Out: High | GAMA 429
SDI: Common
VNAV: Enable Labels

"VOR/LOC/GS AIRNC (sic) Config" page
TX: High
RX: High
SDI: Common
DME: Unused by SkyView


Fair enough...without a GPS fix from the Garmin, I knew I couldn't check the system out fully.  But...it didn't look like it was getting anything from the 430.  A little digging turned up this post:

For what its worth here are my settings for my GNS430W.
Main ARINC429 Config:
  In 1    Speed - High     Data - EFIS/Airdata
  In 2    Speed -Off     Data -
  Out     Speed - High     Data - GAMA429
  SDI    Common
  VNAV  Enable Labels

Main RS232 Configuration
  Chan 1  Input - Icarus-Alt        Output - Aviation
  Chan 2  Input - Off  Output - Off
  Chan 3  Input - Off        Output - Off
  Chan 4  Input - Off        Output - Off

VOR/LOC/GS ARINC429 Config:
Speed RX - High                TX - High
SDI     RX - Common
DME    Directed Freq 1


I could accept that DME may be a "no-op" from the SV-ARINC perspective, so the poster's setting may not matter.  But there's a whole config page that isn't listed in the installation manual, and guess what?  When I went there, it wasn't set to those values, and when I changed them, I got data flowing to SkyView.  Yay!

But...why wasn't that setup info listed in the installation manual?  What *else* is not in there that I need to know?

And lastly...the first time through the setup on the 430, I couldn't find that VOR/LOC/GS config page (nor a bunch of others).  Weird.
 

swatson999

Well-Known Member
Joined
Oct 6, 2010
Messages
1,689
Never got a reply on this thread, but I'll bump it to the top to ask a follow-up...I have this setting:

Main RS232 Configuration
  Chan 1  Input - Icarus-Alt        Output - Aviation
  Chan 2  Input - Off  Output - Off
  Chan 3  Input - Off        Output - Off
  Chan 4  Input - Off        Output - Off

Should the Input be "off" instead of Icarus-alt (whatever that is)? The 430 is giving me a message about not receiving 232 data on input 1...I presume that's correct because it's only *transmitting* 232 to the ARINC module. Correct? I.e., if I turn it "off" will that cause a problem?

BTW, everything is talking to each other correctly (SV1000 to ARINC to 430), and I see all the correct data (I think) from the 430 on the SV display.
 

dynonsupport

Dynon Technical Support
Staff member
Joined
Mar 23, 2005
Messages
13,226
We send altitude out over ARINC, so there may not be a need for the 430 to receive it over serial as well (not sure of this - this is a question for Garmin / Garmin experts that might be lurking here). It uses altitude for calculations like density altitude and such, and other things like that.

If it turns out it does need altitude over serial vs over ARINC If you want, you can use an unused serial transmit from SkyView, set it to Icarus, and then send it to chan 1's input. If it doesn't, you can just turn off the input side of that port as you suggest and then it won't be expecting altitude that it's not receiving anymore.
 

swatson999

Well-Known Member
Joined
Oct 6, 2010
Messages
1,689
We send altitude out over ARINC, so there may not be a need for the 430 to receive it over serial as well (not sure of this - this is a question for Garmin / Garmin experts that might be lurking here). It uses altitude for calculations like density altitude and such, and other things like that.

If it turns out it does need altitude over serial vs over ARINC If you want, you can use an unused serial transmit from SkyView, set it to Icarus, and then send it to chan 1's input. If it doesn't, you can just turn off the input side of that port as you suggest and then it won't be expecting altitude that it's not receiving anymore.

Thanks! That's the info I needed (for now). I'll turn it off unless/until someone comes up with a reason to connect it up and turn it back on :)
 
Top