The "offical" LXNAV V7 thread

[marshal...@gmail.com]

Let the praise and suggestions begin!

[Tony]

i suggest a lower price with more features :D

[Derek Mackie]

I LOVE mine!

[Bruno]

On Jun 7, 7:38 pm, marshallmccl...@gmail.com wrote:
> Let the praise and suggestions begin!

Just in case someone sees this thread and doesn't know about the first
thread that was hijacked where quite a bit of V7 discussions and
suggestions have already been made, please take a look at:

http://groups.google.com/group/rec.aviation.soaring/browse_thread/thread/e664af0bc4e1c338#

I am really enjoying my V7, think it is the most beautiful vario on
the marketplace period, and have been quite impressed with LXNAV's
responsiveness to issues and questions so far. Keep up the good
work! It would be nice to have a singular place provided by LXNAV to
list issues, ask questions and make suggestions. Until then, this
thread will suffice.

Safe soaring,
Bruno - B4

[bruced...@gmail.com]

Also love mine. Uros was very helpful over the winter getting it working, I assume he'll entertain the ideas you guys have suggested. I tend to set the MC and leave it alone as on all previous Varios. I installed a rocker switch for my V7 SC because I was already accustomed to one. I find the switch helpful for times when you want a vario to shut up, like prior to launch or when you're scratching in dire need of lift.

[Bastoune]

All, I have noticed on the LX Nav website that a new firmware revision V2.0 was released last week for the V7. Do we know what bug fix and/or feature addition was incorporated?

[Glen Kelley]

On Tuesday, June 26, 2012 10:42:51 PM UTC-4, Bastoune wrote:
> All, I have noticed on the LX Nav website that a new firmware revision V2.0 was released last week for the V7. Do we know what bug fix and/or feature addition was incorporated?

Not really sure, but it appears that the gps signal status indicator has vanished!

[Morteza Ansari]

From what I have heard:
Bug fixes
Improved needle initialization
Improved averager
Vario calculation and dynamics
Improved smart filter

[eric_k...@hotmail.com]

Op woensdag 27 juni 2012 05:39:34 UTC+2 schreef Glen Kelley het volgende:

> On Tuesday, June 26, 2012 10:42:51 PM UTC-4, Bastoune wrote:
> > All, I have noticed on the LX Nav website that a new firmware revision V2.0 was released last week for the V7. Do we know what bug fix and/or feature addition was incorporated?
>
> Not really sure, but it appears that the gps signal status indicator has vanished!

Are you sure the GPS source and the V7 are set at the same baudrate?

[Glen Kelley]

I did check. The feed from the powerflarm to the v7 and on to Oudie/SYM is working fine. The oudie is definitely using the gps stream from the PF. We were previously getting the gps symbol bad then good as the pf locked on. Now there is no gps symbol at all on the v7, but the gps data indicates fine on the oudie. Internal gps on the oudie is disabled as backup, so the gps is definitely coming from pf/v7.

[eric_k...@hotmail.com]

Op woensdag 27 juni 2012 23:37:58 UTC+2 schreef Glen Kelley het volgende:

Hmm, strange... I think the GPS symbol is very usefull and I can see no reason to skip that. (I'm also using Flarm as GPS source)
Did you allready give feedback to LXNAV? It's not unthinkable that this is a bug in V2.00

[Glen Kelley]

My Mistake! Sent Email to LXNAV and received rapid response from Uros to check NAV page on V7. The 'Use GPS Data' box was unchecked, which removed the GPS status indicator. Interestingly, the NMEA data was still being passed normally through V7 to OUDIE.

I have received very rapid email support from LXNAV whenever I have sent a message to them. Excellent support.

Sorry to add to any confusion out there.

[Rhubarb]

I am having difficulties getting to like my V7

There are so many settings its a bit of a jungle.Aand changes only get saved if you remember to power it down using the knob (why?). So, many of my settings changes get lost as I forget, and just kill the power after landing. If you try and save your changes in the air then MC, bugs, ballast, altitude etc get lost so that is a no-no unfortunately

This also means that you cannot pre-setup stuff like ballast on the grid and then power down to save batteries. This is really annoying cos the workload in a glider is so high these days that it is important to get as much stuff out the way as possible

The V2.00 firmware upgrade wiped all my settings so now I am doing it again (doh!). I have no idea what it changed/fixed cos there is no release notice. But it took me a while before it finally sunk in that selecting thermal flaps was now putting the V7 into cruise mode! (fixed after finding the correct config setting eventually)

The power down using the knob takes forever (after you have done it a few times). Firstly you have to hold it down for a few seconds and *then* it wants me to keep pushing for 3 more before shutting down....zzzz

I miss a polar degradation setting. I know I can do it with Bugs but I want it permanent. So, I have selected an inferior glider from the list of polars, which is good enough I suppose, but it realy should be handled better.

I miss a volume setup which changes the vario volume automatically with airspeed. It is 2012 and I am still having to adjust the volume in different phases of the flight!

I want to see the glider battery voltage - in volts eg 12.3 . I have a Redbox, V7, Becker AR6201 and XCSoar onboard all with digital displays and yet I still cant see the voltage without compromising. Either I use 1 of the V7s configurable number fields (which I would rather to use for something else) or keep the Becker in 1 of its 3 modes. V7 - please display the volts in a dedicated field.

I probably just need to tweak the settings some more, but I am having a hard time geting the V7 to behave somewhat like my old 302. (the 302 had its own issues of course)

The averager number seems to be updated on a timer (say every 0.2sec). So it often jumps from value to value, missing some intermediate values. I believe this is wrong. I want to see all intermediate values as well to get a trend feeling. This should work OK since it is a time averaged value and so changes fairly slowly. In contrast, the push/pull diamonds on the right dance up down like a break dancer and really need to be filtered a bit more.

Its a pity the V7 cannot offer a backup navigation facility a bit more advanced then the current "take me home functionality". If my Android PDA gives up the ghost then it would be nice to be able to continue round the task using the V7. I have a Redbox supplying NMEA to the V7. Why cant I put a WP list in the RB and select GOTOs from the V7. Or perhaps the V7 sniffs the declaration. OK, this is a bit more advanced wish. But it would be really great

Could someone post a good Vario and Display setup for the V7 for flying tasks. What do you configure the Needle, number fields, etc for cruise and climb. I know somethings are a matter of taste, but others are must haves. What are your must haves?

phase Cruise Climb
needle netto vario
big number ? average vario
small number altitude altitude
averager 20 sec
smart filter ?
other important settings?
etc

Peter

[Glen Kelley]

I understand some of your concerns, but my partner and I still think this is the best vario we have ever used - and our prior was a 302. Once the vario is set up and the settings saved, the only thing you should lose on power down are Mc Setting, bugs and ballast. These are not too hard to deal with. We power ours up 10 min prior to takeoff, configure, and then leave on for the duration.

Our current settings are

phase Cruise Climb
needle Relative Netto TE
big number Netto Average

small number altitude altitude
averager 20 sec

smart filter 2
other important settings?

TE 3 sec
Cruise/Climb on a switch on the stick

We would like to see the ability to change the filtering speed between cruise and climb. Cruise should be on a slower response. We also use a chopped tone in climb mode and a solid tone in cruise mode to help hear the difference between the two modes.

The vario is not perfect but seems to be getting steadily better. We started with 1.97, so no clue prior to that. We treat this as a smart vario and air data feed to SeeYou Mobile. It would be generally a waste to put nav data up on the limited display space. That is what SYM is for. However, it might be nice to add a third (NAV) display in the cruise/climb rotary. So now it would become cruise/climb/nav and the nav display could allow you to use bearing and distance to the nav point - something like that.
etc

[David Reitter]

On Monday, July 2, 2012 5:51:03 PM UTC-4, Rhubarb wrote:

> There are so many settings its a bit of a jungle.Aand changes only get saved if you remember to
> power it down using the knob (why?).

Because the idea is to set it up once (while on the ground) rather than to mess with the settings in flight.

> MC, bugs, ballast, altitude etc get lost so that is a no-no unfortunately

I agree, these things should be saved. I think that ground elevation will be saved eventually - I suggested that and LXNAV seemed OK with that idea.

> This also means that you cannot pre-setup stuff like ballast on the grid and then power down to
> save batteries.

Yes. Tell LXNAV. They're quite responsive.

> I miss a polar degradation setting.

Me too.

> I miss a volume setup which changes the vario volume automatically with airspeed. It is 2012
> and I am still having to adjust the volume in different phases of the flight!

+1

> I want to see the glider battery voltage - in volts eg 12.3 .

There will be something like that in a future version (on a separate screen).

> Its a pity the V7 cannot offer a backup navigation facility a bit more advanced then the current
> "take me home functionality".

Actually, if your GPS source sends waypoint coordinates, then the V7 will navigate to those. A Volkslogger with a task declaration would do this, for instance.

That said, I don't waste the display on NAV data. On a separate screen (easy to get to), sure. And that's actually something that I think might happen in the near future.

D

[RAS56]

Just an FYI for my fellow v7 users regarding updates....when the manual says use the 115k baud rate to do the update, it really means it!

I update my v7 via my Oudie, which I had set at a baud of 19k, along with the Nano I use as a FR. Since they were all talking nice to each other, I figured to not rock the boat and attempted to do the 2.00 update at the lower speed rate figuring it might just take a bit longer. Bad plan on my part...here's what I found out.

The first of the 2 firmware files updated w/o a hitch, but the 2nd update didn't seem to be installing properly. Be advised you are apparently performing two "separate" updates when performing these...the first one is for the v7 and another file upgrades the vario indicator itself. If you look on the v7's "about" page, you'll see two different lines detailing what firmware each of these separate items is running.

After attempting at the low baud rate, I had one line reading "1.96" and another reading "2.00"...when both should have read "2.00".

I finally gave up trying to preserve my settings, did the upgrade at the 115k rate and it went off w/o a hitch...after which I was able to get everything talking to each other again.

As to the up thread discussion on a nav option with the v7, I have mulled over the idea of getting a Colibri II FR in lieu of using my Nano. It has all the FR capabilities of the Nano with the added bonus of being a rudimentary nav system with a display were the primary to croak.

Rob

[resi...@sbcglobal.net]

On Tuesday, July 10, 2012 12:54:19 PM UTC-5, RAS56 wrote:
> Just an FYI for my fellow v7 users regarding updates....when the manual says use the 115k baud rate to do the update, it really means it!
>

> I update my v7 via my Oudie, which I had set at a baud of 19k, along with the Nano I use as a FR. Since they were all talking nice to each other, I figured to not rock the boat and attempted to do the 2.00 update at the lower speed rate figuring it might just take a bit longer. Bad plan on my part...here's what I found out.
>
> The first of the 2 firmware files updated w/o a hitch, but the 2nd update didn't seem to be installing properly. Be advised you are apparently performing two "separate" updates when performing these...the first one is for the v7 and another file upgrades the vario indicator itself. If you look on the v7's "about" page, you'll see two different lines detailing what firmware each of these separate items is running.
>
> After attempting at the low baud rate, I had one line reading "1.96" and another reading "2.00"...when both should have read "2.00".

>
> I finally gave up trying to preserve my settings, did the upgrade at the 115k rate and it went off w/o a hitch...after which I was able to get everything talking to each other again.
>
> As to the up thread discussion on a nav option with the v7, I have mulled over the idea of getting a Colibri II FR in lieu of using my Nano. It has all the FR capabilities of the Nano with the added bonus of being a rudimentary nav system with a display were the primary to croak.
>
> Rob

Rob, I think you need to go ahead and get the Colibri II and then donate the unneeded Nano to one of the student pilots at your home field... :)

Robert

[RAS56]

> Rob, I think you need to go ahead and get the Colibri II and then donate the unneeded Nano to one of the student pilots at your home field... :)
>
> Robert

Hey Robert, think so? ;-)

There's no doubt that that Colibri is a nifty looking piece of gear, definitely worth a closer look in the off season...could maybe work a deal with you for the Nano then if you're interested.

Then again, I'm running into more and folks that fly with multiple loggers "just in case"...

Get that PPL out of the way and then start making plans to come up to Dalhart with us next year!

Regards,

Rob S.
ZAP

[Bastoune]

Quick update from the LX Nav website. A new firmware V2.02 is now available:

V7 Firmware news
Version 2.02

Implementation for flarm dataport spec. ver.6 (undirected warnings A/C mode)
Implemented Flarm status indication
added polar for Silent 2 targa and JS1-21m

Version 2.01

Implemented support for V7 Bluetooth module (external module)
Implemented warning for C/A mode
Some compatibility issues with XCSoar
faster power off
fixed some minor bugs

Version 2.00

New smart vario filters
improved needle initialisation
Auto baudrate
fixed some minor bugs


It should be also noted that LXNAV has created several "Firmware loading" software that can be used on PDA's, PNA's, etc! No need to log the laptop at the field. A simple PNA should now do the trick. Well done!

Bastoune

[bruced...@gmail.com]

I Flew all 2012 with a V7 and never got the settings to my liking so I'm looking at possible other problems. The Temperature Offset reverts to 28.7F regardless of how many times I change it. I haven't yet updated the s/w due to PC issues. Any thoughts on the Temp Offset?
~Bruce

[Richard]

On Saturday, October 27, 2012 7:24:05 PM UTC-7, bruced...@gmail.com wrote:
> I Flew all 2012 with a V7 and never got the settings to my liking so I'm looking at possible other problems. The Temperature Offset reverts to 28.7F regardless of how many times I change it. I haven't yet updated the s/w due to PC issues. Any thoughts on the Temp Offset? ~Bruce

Bruce,

Update to the current Firmware 2.02, The temp thing at was a bug in the first firmware.

If you can't update send it to me Priority Mail at Craggy Aero and I will update the firmware for you.

Thanks,

Richard
www.craggyaero.com

[bruced...@gmail.com]

Thanks Richard, I hoped that it might be the firmware! Do you think a temperature offset of 28F would cause 'bad behavior'? 28 seems like a large number.
~Bruce

[Richard]

On Sunday, October 28, 2012 5:23:50 PM UTC-7, bruced...@gmail.com wrote:
> Thanks Richard, I hoped that it might be the firmware! Do you think a temperature offset of 28F would cause 'bad behavior'? 28 seems like a large number. ~Bruce

Bruce,

I think that you have a very early firmware one of the first. Changes were made almost immediately by LXNAV if bugs were found. I remember that bug on the first batch I got from LXNAV in Nov 2011. I set the first V7s up on a bench with a variety of GPS and Displays and went thru all the menus and tested. I believe the bug was in the unit conversion with the temperature. I make a practice of updating the firmware on all that I sell.

The update procedure and files are published on the LXNAV. Make sure you follow the procedure especially the 115200 Baud rate. If you need help call and we can set a time when you are at the instrument and I will talk you thru the procedure.

Richard
www.craggyaero.com

[Steve Koerner]

If this is the official V7 thread, then this would be a good place to let it be known that I have an official V7 vario available for sale at just $1200.

It is complete in the original box with both an Oudie cable and an IPAQ type cable as well as all the standard cables and accessories that come with the unit. The unit was purchased from Cumulus Soaring in March of this year. The provided speaker and several cables were never connected. The unit saw only a short period of in panel usage before the ClearNav vario came out and replaced it for best compatibility with my ClearNav unit. It is in perfect condition.

I suspect that this V7 unit may need a software update if you want to run the latest and greatest V7 software -- the latest software can be downloaded from the website and updated in the field. The latest manual can also be downloaded.

Please contact me offline.

[waremark]

Did you not value all the extra info the V7 can display compared to the Clearnav vario (eg speed director at the same time as vario, graphic whole thermal average, and much other stuff)? What advantages does the CN vario give you?

[Steve Koerner]

Waremark:

It's now sold. I'll trust that it's new owner will value that "other stuff" more than I did. Actually though, the ClearNav vario offers quit a bit of useful other stuff too.

[Dan]

I'm flying with a V7/Nano/Oudie combination, I was wondering if anyone else
had problems with this setup making Igc files when the set up is turned on
and then off with out moving the plane.
Dan

[Naviter Info]

Did Nano create an IGC file or did Oudie create one? please send such file to support at naviter dot com - it must be an easy settings fix. Or even just a matter of a firmware upgrade on any or all devices.

Regards,
Andrej Kolar
--
glider pilots use
http://www.Naviter.com

[Dan]

On Sunday, November 25, 2012 11:55:17 PM UTC-8, Naviter Info wrote:
> Did Nano create an IGC file or did Oudie create one? please send such file to support at naviter dot com - it must be an easy settings fix. Or even just a matter of a firmware upgrade on any or all devices. Regards, Andrej Kolar -- glider pilots use http://www.Naviter.com On Monday, November 26, 2012 3:10:58 AM UTC+1, Dan wrote: > I'm flying with a V7/Nano/Oudie combination, I was wondering if anyone else > > had problems with this setup making Igc files when the set up is turned on > > and then off with out moving the plane. > > Dan

Andrej,
It was the Oudie that created the file. All devices are running the latest firmware.
If you don't recall I sent you a file back in March of this year, to which
you responded "this will take some time". I waited 3 months, and sent a follow
up email to check on progress, to which you responded," please send me a file"
which I did. Then I was told this would not be addressed until sometime next year.
(I'm not holding my breath)
Regards,Dan

[Tim Taylor]

Looking for a wiring diagram for the LXNAV V7 to Oudie cable. I tried following the diagrams in the V7 manual but did not have success even using a proto board to try different configurations.. The offical cable I have has five wires rather than the four that the diagrams show. I would like to build cables for a pass through connection in the panel.

[Richard]

On Monday, November 26, 2012 8:20:56 PM UTC-8, Tim Taylor wrote:
> Looking for a wiring diagram for the LXNAV V7 to Oudie cable. I tried following the diagrams in the V7 manual but did not have success even using a proto board to try different configurations.. The offical cable I have has five wires rather than the four that the diagrams show. I would like to build cables for a pass through connection in the panel.

Check your email for the cable drawing.

Don't get dyslexia you may brick the stuff.

Richard
www.craggyaero.com

[Bastoune]

Help please!

I am unsuccessful at updating my V7 with the latest 3.02 software. (I did successfully upgrade to v2.02 two years ago). I am trying to update with my PNA Vertica V2. Part of the problem is that I am not sure which COM port to select from the PNA V2. Here's the combination of errors that I get:

COM1: "Load" message appears, but the "Discovery" message does not. I then get this error window pop up: "Update failed, error code = -5"

COM2 or COM3: Load message appears, Discovery then starts but after 5 seconds, error window message: "Update failed, error code = -10"

COM 4: Load message appears, Discovery then starts but stays stuck. When I eventually hit "cancel" on the PNA, the error message is: "Update failed, error code = -21" shows up.

Additional info:
-> The baud rate is set at 115200 on both the V7 and the PNA (I have been forewarned about using anything else so I always triple check)
-> The LXNav "PNA Update tool" and firmware are the latest versions from the LX website


What I am screwing up?

Thanks,

B

[sv.s...@mac.com]

Bastoune-

your v2 needs to use COM7 for the PNA update tool to talk to the v7 and that is not available from the pulldown. You will need to bring up a keyboard on your v2 and type in COM7 and I think it will work - at least it does from my Avier.

Mike O.

[busha...@gmail.com]

Has anyone accomplished this update with a MIO? I have my MIO connected to the V7 via the Glider Tools cable but have not attempted a firmware update via this connection.

Lane

[Bastoune]

Mike 0! This was the tip that I needed! Switching to COM7 manually did the trick. The installation when smooth as butter after that! Thanks!

Lane - Your MIO will work just fine as long as you select the correct COM port (!). I had used a MIO a year ago to upgrade my V7.

B

[son_of_flubber]

What is the difference between V7 and V7D? I did not find an answer on the LXNav website.

[Pete Startup]

V7D is the repeater for a 2 seat glider.

[busha...@gmail.com]

Bastoune,

I assume I put the update utility and update file in the primary file directory? Do I create a folder for them or just place them separately in the the primary file structure? Any chance you remember the correct com? I suppose I can start with the com setting I currently have that is communicating with the V7 from the MIO.

Lane

[Bastoune]

Lane,
The easiest way is to create a folder in the primary file directory and save all of the files (LNNUpdate.exe, CeLxV.dll, the VINB and VSEV files) in that directory.

Starting with the COM port that you are using to communicate with the V7 is the right approach (and this is where I got off track as my PNA did not show that COM port as an option in the LXNav Update tool)

Good luck! B.

[Paul Remde]

Hi,

The V7D is the 2nd-seat repeater version of the V7. It is a display without
the vario sensors. It works only when connected to a V7.

Best Regards,

Paul Remde
Cumulus Soaring, Inc.
________________________________

"son_of_flubber" wrote in message
news:dd3b1735-6d5c-4acb...@googlegroups.com...

[sv.s...@mac.com]

Bastoune,

Sent LXNav an email last night suggesting they add COM7 to the pulldown and Uros had a new PNA update tool file on their website by 7:30cst this morning! Now if we can just remember from one update to the next that COM7 is what we need to use!
Mike

[Bastoune]

This is fantastic. The LXNav team product support and responsiveness is second to none. This is another fine example!

[ES]

Has anyone had luck uploading tasks from Oudie to V7? This topic isn't discussed in the user guide, and I'm not having any luck repeating the settings in the youtube video on the subject (device = "LXNAV - Nano", interface = "COM4:", speed = "4800bps".

In the video, there is very quick connection and transfer.

When I try it (using the latest V7 firmware and Oudie version), I get "Connecting" on the Oudie, and the communication icon on the V7, but nothing else.

thanks

ted/ES

[Bastoune]

Ted,
I may be misunderstanding your question, but I do not think that you can upload a task "to" the V7. You can upload a task to your GPS Logger (e.g. Nano) by going "through" the V7 (See setup example in section 8.4.2 of the manual). The relevant section on how to perform the upload is 5.1.2. In the "Direct Link" mode, the Oudie communicates directly to the Logger.

[ES]

Okay, things are starting to make a little more sense. On page 16 (section 5.1.2)there is a turnpoint name ("Line 11") above the course direction indicator. When I saw that, I assumed I there was some task storage and processing in the V7. If the task is not in the V7, where does this turnpoint name come from? (From the Oudie, or from the logger?)

[Luke Szczepaniak]

On 02/28/2014 9:28 AM, ES wrote:
> Okay, things are starting to make a little more sense. On page 16 (section 5.1.2)there is a turnpoint name ("Line 11") above the course direction indicator. When I saw that, I assumed I there was some task storage and processing in the V7. If the task is not in the V7, where does this turnpoint name come from? (From the Oudie, or from the logger?)
>

The Oudie will have to send the active TP coordinates in an RMB sentence
back to the V7.

Luke

[Martin Gregorie]

It must also be getting at least the WPL sentence and possibly is also
getting ROO sentences. I say this because the RMB sentence conveys the TP
coordinates but doesn't contain its name. Both ROO and WPL include the TP
name. WPL contains the name and coordinates of a TP: by comparing
coordinates between RMB and WPL the receiver can work out the RMB's
target TP name. ROO defines the task (in our terminology). All it
contains is a list of TP names in task declaration sequence.

The reception frequency differs depending on the sentence type. An RMC+RMB
pair are received every second with a third sentence appended. This
sentence is either an ROO or a WPL. The ROO and associated WPLs are sent
in a repeating sequence, one each second, so if you have 'n' turnpoints
in the active task, the sequence takes n+1 seconds to be sent.

I researched this some time ago when I wanted to understand why my SDI C4
wouldn't calculate wind unless the GPS it was attached to, a Garmin GPS
II+ at that stage, had at least one active waypoint. I ended up with the
Garmin plugged onto a PC and displaying each sentence as it arrived so I
could work out what was going on.


--
martin@ | Martin Gregorie
gregorie. | Essex, UK
org |

[ch...@sifow.com]

You need to ensure the baud speed for your logger is the same as the baud speed for the PDA (as the V7 gives the PDA direct access to the logger when declaring a task). This should fix the problem

Chris

[Peter Wilson]

I load tasks from an oudie through a V7 to a red box flarm/logger. The red
box has a basic flarm display and communicates with it at max 19200 baud
(this can also be set to a lower figure and determines the speed of the
whole link). Consequently I have to set the V7 GPS and V7 PNA links to
19200 and it works fine.

Peter


At 16:53 01 March 2014, ch...@sifow.com wrote

[n...@uw.edu]

Can someone post the wiring diagram to connect the Vertica V2 / Avier to the V7?

Thank you,

Nick

[Craig Funston]

Google "glider guider USB/Serial Data Interface" There's a PDF that has the pinouts for the GliderGuider / Vertica V2. The pinouts for the V7 are available at the LXnav website in the V7 manual. I'm assuming you're using a separate GPS source for the V7. I'm not aware of a way to get the GPS data from the Vertica into the V7.

Cheers,
Craig

[J. Murray]

Howdy. Has anybody had trouble getting the V7 to display glide info from the Oudie lately?

Thanks, Jim

[Paul Remde]

Hi Jim,

I haven't tested it lately, but below is a note about how to get it working.
Some of the settings are not intuitive.
______________

Settings to have the Oudie send GPS data to the V7 and the V7 send vario and
airspeed data to the Oudie.

On the Oudie in the Menu > Settings > Hardware screen
Device: LXNAV V7
GPS Forwarding: enabled
Use backup GPS: disabled (may not be necessary)

Port Settings
Comm 4, 115200

On the V7 in the Communications screen
GPS-PDA Link: disabled
Auto baudrate: disabled
PDA port baudrate: 115200
GPS port baudrate: 115200

Tested – it works great.

Paul Remde
Cumulus Soaring, Inc.

________________________________________________

"J. Murray" wrote in message
news:e1ebc588-f70e-4bc8...@googlegroups.com...

[J. Murray]

I haven't tried disabling the PDA link. That'll be next...

Thanks!

[Richard]

On Thursday, June 5, 2014 1:55:08 PM UTC-7, J. Murray wrote:
> I haven't tried disabling the PDA link. That'll be next...
>
>
>
> Thanks!

This one worked yesterday.

V7 COM Menu
* Auto Baud checked
* PDA 4800
* GPS 4800
* NMEA enable
Oudie Hardware Menu
* Device V7
* COM 4
* 4800
* Check GPS Forwarding
Oude Input Manual
* Com 4
* 4800

Richard
www.craggyaero.com

[J. Murray]

That's worth a try too.

Thanks Richard.

[n...@uw.edu]

I'm connecting the 10 pin mini usb from the Avier V2/ Vertica V2 to the V7.

Has anyone installed their own male RJ45 connector on a mini USB to connect the V2 to the LXNAV V7?

I need the pin assignments for both.

[edwa...@uw.edu]

I think I can help since I've made a working cable. I can't post a diagram, but if you get out a piece of paper you can draw what I describe. I used the pinout diagrams from the LXNAV V7 and Vertica V2 manuals as sources. There is also a USB 10 pin cable diagram at Glidertools.

First draw the RJ45 port of the V7. The key (indentation) is at the top. Label the pins from 1 to 8 left to right. Pins 1 and 2 are GND. Draw an X through pins 3 and 4 because they are RS-232 higher voltage pins and you do not want to fry the V2 which uses LV-TTL. Next mark pin 5 RX-1 (V7 input) and pin 6 TX-1 (V7 output). Pins 7 and 8 are +5v.

Next draw the 10 pin USB mini port on the V2. It has a two long sides, one of which is a bit longer. Put the longer side on the top. Across the top label pins 2,4,6,8,10 and across the bottom label pins 1,3,5,7,9. Remember that this is the view of the port on the V2 NOT the pinout of the male cable. Pin 2 is +5v which should be connected to pin 7 or 8 of the V7. Pin 10 of the V2 is the GND, and that should be connected to pin 1 or 2 of the V7. Pin 7 on the V2 is the TX for Com 7 and should be connected to pin 5 of the V7. Finally, pin 9 of the V2 is the RX for Com 7 and should be connected to pin 6 of the V7. If you want COM 8 use pin 1 instead of 7 and 3 instead of 9 on the V2).

Remember that when you make the cable you have to stay oriented so that the male cable end is fitting into a mirror image female connector, so the numbers may appear reversed. The diagram you just made is the socket side of each connection

Just for the record I also got the LXNAV BT connector to work as well with the V2. It plugs into the same port, and there is one less cable. Most of the time, however, I use the cable because it keeps the V2 charged off the aircraft battery.