Avare with FSX

429 views
Skip to first unread message

bob thron

unread,
Jan 29, 2015, 11:34:12 AM1/29/15
to apps4a...@googlegroups.com
I've tried just about everything I can find trying to get Avare to work with FSX. Does anyone have any tips? I'm using the most up to date versions of Avare and the I/O app

Zubair Khan

unread,
Jan 29, 2015, 11:45:14 AM1/29/15
to bob thron, t v, Apps4Av Forum
It needs a special connectivity software that is paid I think. TV can elaborate or paste a link here.
Zubair

On Thu, Jan 29, 2015 at 11:34 AM, bob thron <orbi...@gmail.com> wrote:
I've tried just about everything I can find trying to get Avare to work with FSX. Does anyone have any tips? I'm using the most up to date versions of Avare and the I/O app

--
You received this message because you are subscribed to the Google Groups "Apps4Av Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to apps4av-foru...@googlegroups.com.
To post to this group, send email to apps4a...@googlegroups.com.
Visit this group at http://groups.google.com/group/apps4av-forum.
For more options, visit https://groups.google.com/d/optout.



--
Zubair Khan
apps4av.com
zk4u.blogspot.com
Sudbury, MA 01776

fly...@yahoo.com

unread,
Jan 29, 2015, 12:20:51 PM1/29/15
to apps4a...@googlegroups.com
Hi Bob.
In order to communicate with MSFSX you will need Xconnect (Xconn.exe), MSFSX, Avare, Avare IO, see more info below. There used to be detailed instructions in the Apps4av that may have been removed, just follow the instructions below and post here if you need more help. Your device IP may be something different than what posted, look it up i the Avare IO after you start the process.
TV

Set up used: Desktop PC, win 7 Pro 64, with "MS FSX Gold"  with "XConn"  Ver. 0.5 and

Samsung Tablet 7 or 10 in. running Android Ver. 4.1.2

"Avare" Ver.:   5.2.7

 

Note:  "XConn" by Ubi Sumus, Must be installed / used to output NMEA to LAN port.

         I used Ver. 0.5. To locate Search for "ms fsx nmea output" on the Inet.

 

In "XConn"  enter the IP 192.168.0.6 and the 49002 in "Output" selection. I also changed the Baud rate to 4800 in the "xConn.cfg" file but it may not be needed.

 

These are basically the same steps as described at "apps4av.com" by the initial help for XPlane steps 1-4, document, and in addition  I added some steps to make it easier for first time users to get started and modified it for MS FSX.

 

See details before step 4.

 

1) Make sure your Avare device and computer are on the same WIFI network.

2) Start FSX.

3) Start XConn and verify IP 192.168.0.6 and 49002.

 

Added:

{To get to step 4:

Make sure GPS is disabled in your device Settings.

Start Avare, answer No to "GPS enable" and send it to background (press Home key), do Not Exit.

Start Avare External I/O, and do step 4.}

 

4) Check the checkbox on the FSX line on the Avare External I/O module to start receiving position from FSX.

 

Added:

{

5) Send the Avare External I/O to background (Home key), do Not Exit.

6) Reactivate Avare (press icon).

7) If Chart does not display in Avare go to "Options", (icon above "Map", in map mode only, and toggle "Navigate" to "Simulation", click "Find" icon >click on your airport, go back to "Map">"Options",  and disable "Simulation"  / enable "Navigate", you should have the Chart. If no joy repeat steps 5-7.

Go to your XPlane and fly.}

bob thron

unread,
Jan 29, 2015, 1:33:12 PM1/29/15
to apps4a...@googlegroups.com
I've tried this multiple times. Doesn't work unfortunately. Where can I see my IP address in Avare IO? I don't see it anywhere

fly...@yahoo.com

unread,
Jan 29, 2015, 6:12:04 PM1/29/15
to apps4a...@googlegroups.com
Hi Bob.
At this point I am Not able to get any of the AvareIO versions to communicate with MSFSX, wee need see what has changed in the IO, it does some strange things on power up / Start when the WiFi is on, verifying / transferring data, it may have something to do with that.
I will notify Z and I am sure there will be an explanation. For now, until I, or someone else, will post here consider waiting. TV

Zubair Khan

unread,
Jan 29, 2015, 7:27:25 PM1/29/15
to t v, Apps4Av Forum
Hi TV

What is the issue? I see the IP address in the MSFS box and text saying Connect to MSFS on WIFI-NMEA(192.168.1.2). Port is 9002.

When I check Listen, it says success and listening. I do not have a Windows machine or MSFS. What do you mean by verifying data?

Thanks
Zubair

--
You received this message because you are subscribed to the Google Groups "Apps4Av Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to apps4av-foru...@googlegroups.com.
To post to this group, send email to apps4a...@googlegroups.com.
Visit this group at http://groups.google.com/group/apps4av-forum.
For more options, visit https://groups.google.com/d/optout.

Doug Du Plessis

unread,
Jan 30, 2015, 12:48:10 AM1/30/15
to apps4a...@googlegroups.com
As Zubair says, the ip address and port number are displayed once you select the Listen check box. Make sure that the ip and port setting match on your xconn utility (Output settings). My port setting is 49002. You may need to restart the xconn app after changing the settings. As long as FSX is running, those parameters are matched and the Listen box is checked, you should see coordinate and altitude information beginning to flow. Minimize the io app and restore Avare and your plane position will reflect the FSX position. As was stated above, turn off your device location setting otherwise the built in GPS will conflict with the io app within Avare. I have found that this stop works flawlessly with FSX.

Good luck!

Doug

fly...@yahoo.com

unread,
Feb 4, 2015, 2:09:30 PM2/4/15
to apps4a...@googlegroups.com
Hi Bob and everyone.
I was a able to make some sense of what the problem was that did not allow Avare to comunicate with the MSFSX using the Avare I/O and I found the problem to be, at least in my case, the ISP provider has decided to make some subtle changes to the handshake protocol, that for some reason it only affected the Android devices, not any of my PCs. Long story short, the problem was resolved, in my case, by resetting the modem, Power up/ down.

Conclusion is that the previous description on how to interface / communicate with MSFSX is still valid and it works, if it's not working for you try to reset your modem. TV
Reply all
Reply to author
Forward
0 new messages