|T O P I C R E V I E W
||Posted - 19/04/2012 : 00:12:09
Betatester can download the new 3.1b
LK8000 VERSION 3.1b 120418
. Support for ASI FlyNet Vario Device
. [Quick gestures]
Only for paragliders and hangdliers mode: enable/disable quick gestures.
By default, quick gestures are enabled. Quick gestures allow the pilot to click
on right or left nearest/info pages to switch to next/previous like with gestures.
Using gloves during the flight will require this option be disabled.
. Support for UTM coordinate system in units (needed by PGs/HGs)
. Added Apis2 15m polar
. Clock is shown (if enabled) also in portrait mode.
Some resolutions will display the clock lower after right overlays.
Most resolutions will display it on top right, as usual.
. Vector icons for landables will display radio frequency at high zoom levels, and ICAO code at highest
Fix bug in 3.0 not disabling menu and wndproc actions when in MODE_TARGET_PAN (Crashes possible)
Fix old bug resetting flight statistics at 00UTC on some GPS devices like HP31x.
Fix bug with large topology maps on CE 5 devices with not enough memory
Allow Flarm task declaration even in multiplexed or serial bus setups
Fix logger: if no baro pressure available, log 0 for pressure altitude instead of GPS altitude.
AutoQNH fixed not to use TAKEOFF altitude
Fix Analysis olcmode should not use task scale, and print at max zoom the current trace.
(minor) Fix Next Waypoint infobox no more available
More internal code autochecks during execution in beta versions
Manual updated for 3.1 so far:
Calling menu, on first page a new button is replacing the old TrueWind button.
This is the Custom Menu button. Click on it, and you can find up to 10 menu buttons, plus the Cancel.
By default, some of these buttons are already preassigned. For example, TrueWind Calc, Lock Screen etc.
To configure the Custom Menu, enter System Setup and go to page 10, Interface.
There is a new button for Configure Custom Menu.
Each item can be assigned a custom key, or be Disabled.
The Custom Menu is itself available also as a custom key!
This means that you can assign Custom Menu recall from a custom key, like for example top right.
When you click top right, you would recall the custom menu.
SCREEN ROTATION IN LK8000
LK8000 3.2 detects automatically if the screen has been rotated or changed in resolution, and it will
reconfigure itself for the new state. It will only adapt for supported resolutions, of course.
This is totally automatic, and nothing has to be configured. For example, on an HX4700 PPC you can use an hardware key to force screen rotation from portrait to landscape and vice-versa.
LK will immediately adapt to the new orientation.
A menu has been added to force screen resize or rotation, in order to let LK adapt.
Click on Menu, Config 1/3. A new button is called SCREEN MODES.
Screen Modes menu is different for PC and PDA/PNA versions, because functionalities can be different for them.
Screen Modes for PC
Allows you to change to some resolution as 480x272, 640x480 etc., and to Turn Screen (landscape/portrait) using the current resolution.
For example you can change to 320x240, like on a small PNA, and then Turn Screen to get into 240x320 portait mode.
Screen modes for PNA and PPC
On PNA and PPC devices, you have only two buttons for Screen Modes:
Turn 90 degrees
Turn 180 degrees
Do you want to invert upside/down the screen? Use Turn 180. And do it again to go back to previous state.
To rotate by 270 degrees you can either turn 90 for 3 times, or turn 180 and the turn 90.
1. On exit LK will NOT turn screen automatically, nor does it on startup.
Screen rotation is totally manual operation.
2. Screen rotation must be supported by the PNA/PPC hardware and operating system.
Some devices cannot rotate the screen. Some other can do it only by adding unsupported unofficial
rotating drivers by third parties.
LK is simply asking to the operating system to rotate the screen. If nothing happens, there is nothing
we can do about it. We dont support hardware patches, nor external rotating drivers.
3. Although it is possible to rotate the screen also while moving/flying, it is NOT wise to do so.
During screen rotation the software will stop internally for a couple of seconds.
4. Custom fonts are always shared among all screen resolutions/orientations, be careful.
There is only 1 custom fonts configuration, and this will be used (if used) for all orientations.
Expecially on PC this can be confusing, because if you have configured a custom font perfect for
800x480 and then you change to 320x240 you can imagine the result: fonts are not rescaled!
Screen Rotation is still experimental.
ENHANCED PROFILE SETUP
From Menu, Config 2/3, LK8000 Setup you enter a new menu, with 6 buttons:
. System Setup, System Save
. Aircraft Setup, Aircraft Save
. Pilot Setup, Pilot Save
Aircraft and Pilot configurations have been exported from the old configuration setup
and they are now independent items.
LXnav V7 support
The LXnav V7 instrument has the ability to be controlled by a PDA.
Since the V7 is compatible to the older LX instruments, you can use the common LX drivers (LX, LX16xx). Thanks to LXnav we developed an additional commandset in oder to fully support the V7.
In order to use the full functionality of the V7 we recommend to use the LXV7driver, which gives the additional information to LK8000
-Outside air temperature
-External battery voltage
-Status of the Vario/STF switch
-XYZ accelometer values
The values for McReady, Ballast and Bug's (Efficiency) can be entered either be adjusted on the V7 both will have the same values after a few seconds.
One big advantage is, that the Auto McReady function of LK8000 can now adjust the MC value in the V7, so that the MC Value in the V7 is updated automatically.
Another good example is the automatic ballast dump in Basic settings; once the Ballast dump is activated the changing Wingload is continuously updated automatically until the Ballast dump is stopped
To connect a V7 instrument with LK8000 you must select LXV7 as the device in setup (8 Devices) dialog.
In order to test the communication change the MC value on the V7 it should be updated in the LK8000 as well.
Now open the "Basic Settings" dialog (Menu Config / Setup Basic)
Here you can change the "Ballast" and "Efficiency" values which should be changes in the V7 as well. If you press Dump ballast, the values are changed in the V7 at the same time.
The update will take up to 2 seconds.
While using Auto MC it is still possible to change the MC values on the V7 for both devices. The value will be changed automatically as soon the Auto MC algorithm changes the current MC value, which may take a while depending on the history and Auto MC settings.
The status of the STF/Vario switch can be used for changing the circling cruise mode in LK8000. In order to do so you must set the Display mode to DSP auto (Menue Display 2/3 DspMode _Auto_)
The polar coefficients of the V7 and LK8000 are independent from another. This is intended to prevent to change the instrument polar accidentally and possibly use different polar's at the same time.
The V7 instruments have a pressure sensor and deliver a barometric height. If you use a GPS source with Baro altitude you can decide which one will be used in the V7 setup. Please refer to the V7 manual.
The values of the V7 XYZ Accelometer values are drawn as a red dot in the Experimental page 1.6. This dot moves like the little ball in a real TRI indicator with additional information's movements: ------Accelerations towards the nose of the plane make the dot smaller.
-Accelerations towards the tail of the plane make the dot bigger.
-Accelerations towards the top of the aircraft will move the up, the opposite down.
Please not that this in an experimental feature and may not be used for navigation purposes.
New airfield symbols since V3.1x
With the Version 3.1x we introduced new airfield symbols. In order to enable it goto System Setup Page 11 and set the Appearance style from Alternate to Vector
The vector airfield symbols have new scalable airfield and outlanding icons with runway direction and type (dark grey = solid, white = grass).
The runway length is drawn proportional to the real length.
If an airfield is defined as glider site an, it will be marked with "white wings"
On an appropriate zoom level the radio frequency will be shown as well.
On higher zoom levels, more information such as ICAO name (if available) will be printed on the map
Like before if the runway is reachable with respect to the safety height and wind, the airfield/outlanding is green, otherwise red.
In order to use this additional information's it must be included in the waypointfile of course. We recommend to use the *.cup file format of SeeYou which is able to support this additional information. If you don't have the additional information's we recommend to use the old Alternate symbols.
|15 L A T E S T R E P L I E S (Newest First)
||Posted - 28/04/2012 : 15:45:46
Nice. You da' man. I'll check it out and report back after testing 3.1c.
||Posted - 27/04/2012 : 23:53:52
The reason is that Condor is .. not sending a valid date and for some reason LK will not detect takeoff having no valid data.
It is telling you that on screen and in the runtime log.
I will look into that to solve it for condor.
A gps sending RMC sentence with invalid date is faulty for sure, if it sending a valid fix in its opinion.
The date is not optional, we need it for UTC 00 crossing.
[It must be something introduced in 3.1, I will fix it by tomorrow]
[It is now fixed and committed for 3.1c . Tricky situation.
It might have fixes all problem mentioned.]
||Posted - 27/04/2012 : 23:49:59
Thanks, guys. I feel okay about flying with it now. :-) For what it's worth, I've noticed another Condor takeoff-related oddity lately (with 3.1a and maybe even 3.0b, I'm not sure). Sometimes well after takeoff, takeoff is "re-detected" - as evidenced by the takeoff sound and Th.All jumping to an unrealistically high value suddenly. I haven't figured out what scenario seems to cause this latter problem except that it seems to usually (always?) happen while circling.
||Posted - 27/04/2012 : 23:41:00
I am replicating an NMEA log from Condor, and indeed there is something strange with takeoff.
I will investigate.
On real conditions, and also with my NMEA generators, takeoff are always detected.
So no worry for flight..
||Posted - 27/04/2012 : 23:17:48
Yes! I had a successful takeoff detection with 3.1b, after an airtow takeoff.
||Posted - 27/04/2012 : 22:33:40
Originally posted by eric.carden
Is anyone else having this problem? Has anyone successfully used 3.1b with Condor?
Anyone...? Also, has anyone successfully had takeoff detected with 3.1b in real flight? I don't want to fly with it, if takeoff won't be detected.
||Posted - 25/04/2012 : 01:31:06
I noticed a problem last night and am wondering whether it's just me or a 3.1b bug. Using LK with Condor, LK never detected takeoff and thus wouldn't give me things like circling zoom and the glide terrain line. Before the online race, I quickly switched back to my 3.0b install, and it worked fine. Just now, I made a fresh copy of my 3.0b install folder and "installed" 3.1b on top of it. I repeated the test, and it still didn't detect takeoff. Is anyone else having this problem? Has anyone successfully used 3.1b with Condor? By the way, LK was receiving Condor GPS data and showed me in the right place, at the right speed, etc. It just wouldn't detect takeoff.
One more thing... 3.1b detects takeoff in simulator mode, and I haven't made a real flight with 3.1b yet.
||Posted - 24/04/2012 : 15:23:46
UTM Coordinate in Status and Waypoint detail is already fixed for next beta...
||Posted - 24/04/2012 : 15:04:17
thanks for the UTM coordinates.
Just one thing : the display in Info / Status is bad :-((
Thks for all,
||Posted - 22/04/2012 : 17:18:34
Is it possible to add the 270º rotate option?
||Posted - 20/04/2012 : 18:27:59
I would like to see the status of the LK. Often I have to click a button some times just to be sure I have the setting I want. If I could see current value no action would have been neccessary.
Displaying current status In my opinion would be the better choice. If current status is not satisfying you need a change, may be like this:
Press the regarding button results in opening a button list with all possible settings for the issue (including cancel).
For few buttons it is already similar to this (e.g. all sub menues).
This solution would neither need extra space for existing buttons nor changing current LK-layout.
||Posted - 20/04/2012 : 13:28:59
Kai has a point.
Is there room on the buttons for something like:
<Current status> "A"
"press for B"
<press for> "B"
Whatever, a standard logic helps.
||Posted - 20/04/2012 : 09:19:38
Menu->Screen views->overlay button
Here the information is given opposite: It shows what is, not what we will get (btw: I would prefer that for all buttons)
||Posted - 19/04/2012 : 21:08:50
IGC has two altitudes. One for GPS, one for pressure alt. Only the pressure alt will be zero, i guess.
||Posted - 19/04/2012 : 20:05:45
Fix logger: if no baro pressure available, log 0 for pressure altitude instead of GPS altitude.
Does it means that now, the IGC file that logger creates, has 0 altitude instead of GPS altitude unless a baro sensor is present?