PostFrontal Forum
PostFrontal Forum
PF Home | International_Forum | Profile | Register | Active Topics | Members | Search | FAQ
Username:
Password:
Save Password
Forgot your Password?


 All Forums
 LK8000 International Support
 General Support
 LXNav S100 - LK8000 task Declaration failed
 New Topic  Reply to Topic
Previous Page | Next Page
Author Previous Topic Topic Next Topic
Page: of 4

falchettogiallo
Pulcino

Italy
34 Posts

Posted - 25/10/2020 :  09:51:00  Show Profile  Reply with Quote
quote:
Originally posted by falchettogiallo

quote:
Originally posted by AlphaLima

was changed in 7.1p
https://github.com/LK8000/LK8000/releases

you can dis-/enable it in the config file

_Configuration/DEFAULT_PROFILE.prf

changing the entry

DeclareTakeoffLanding=0

If you can't find that entry you version is too old.



Thank you very much!
I just upgraded to 7.1r and checked the configuration file.
Now I just have to wait next time I will go to the airfield.. ;)




Hello AlphaLima!
I confirm that with the new version and the suggested settings, now its working.

I must report that start and finish points defined of "line type" on LK are transferred as "sector type" to the S100

Go to Top of Page

AlphaLima
Moderator

Germany
1929 Posts

Posted - 02/11/2020 :  19:33:59  Show Profile  Visit AlphaLima's Homepage  Reply with Quote
The NanoIII driver does not declare sector types at all.
As far as I know, it is a lack of documentation from LXnav, how to do it.
Go to Top of Page

falchettogiallo
Pulcino

Italy
34 Posts

Posted - 03/11/2020 :  09:48:37  Show Profile  Reply with Quote
quote:
Originally posted by AlphaLima

The NanoIII driver does not declare sector types at all.
As far as I know, it is a lack of documentation from LXnav, how to do it.



Do you have an open communication channel with LX NAV in order to ask information or do you prefer I describe this issue to them ?

I thought you already had support by LX developers..
Go to Top of Page

AlphaLima
Moderator

Germany
1929 Posts

Posted - 03/11/2020 :  19:52:57  Show Profile  Visit AlphaLima's Homepage  Reply with Quote
Well none of the software tools I'm aware of is able to modify the sector type of the LXNav devices. Not even the LXNav dedicated tool NonoConfig allows changing the sectors.
Seems the LXNav concept is changing sector types on the device only.
So far I found a command to read the sector definitions but not to modify it on the device.
Go to Top of Page

falchettogiallo
Pulcino

Italy
34 Posts

Posted - 28/11/2020 :  17:39:08  Show Profile  Reply with Quote
quote:
Originally posted by AlphaLima

Well none of the software tools I'm aware of is able to modify the sector type of the LXNav devices. Not even the LXNav dedicated tool NonoConfig allows changing the sectors.
Seems the LXNav concept is changing sector types on the device only.
So far I found a command to read the sector definitions but not to modify it on the device.




Hello!
Before emailing to LXNAV to get support, today I managed to access my glider to perform some tests.
I can confirm the following:
- LK8000 declaration DOES NOT send sector type information
- NANO CONFIG app DOES send sector type information

So I'm now sure that there is a protocol to send that information.
Are you able to intercept NANO CONFIG output, in order to discover the protocol?

Edited by - falchettogiallo on 28/11/2020 17:40:04
Go to Top of Page

AlphaLima
Moderator

Germany
1929 Posts

Posted - 28/11/2020 :  18:01:08  Show Profile  Visit AlphaLima's Homepage  Reply with Quote
Are you sure?
I tested the same with a NANO4, not transfering sector types.
However, it is not documented! We will not implement it until it is documented.
Sorry, but we will not reverse engineer it.

Go to Top of Page

falchettogiallo
Pulcino

Italy
34 Posts

Posted - 29/11/2020 :  09:07:10  Show Profile  Reply with Quote
quote:
Originally posted by AlphaLima

Are you sure?
I tested the same with a NANO4, not transfering sector types.
However, it is not documented! We will not implement it until it is documented.
Sorry, but we will not reverse engineer it.







Well, you know how much I spent myself in order to force LxNavigation to provide you with a ERA variometer and support..
I'm in contact with LXNAV too, but if you tell me you dont want to implement this feature, I will not engage them.

Yesterday I declared a LK8000 task to LX S100: no sector types transferred.
Then I transferred same task from S100 to NANOCONFIG APP; I changed the start and arrival waypoints (enabling the LINE TYPE check box) on the APP and then transferred again the task to S100. So Im sure the information is correctly transferred from S100 and APP
I thought this information would be useful for you..
Bye


Edited by - falchettogiallo on 29/11/2020 09:09:49
Go to Top of Page

AlphaLima
Moderator

Germany
1929 Posts

Posted - 29/11/2020 :  10:35:18  Show Profile  Visit AlphaLima's Homepage  Reply with Quote
Of course it is, but it does not work for the Nano4 (or I don't know how) and it is a non documented command.
We cannot implement it without a command reference.
I will implement it when I get the command description and find the time. But I'm very busy next year building a house.
Go to Top of Page

AlphaLima
Moderator

Germany
1929 Posts

Posted - 29/11/2020 :  12:37:28  Show Profile  Visit AlphaLima's Homepage  Reply with Quote
OK found it, the Nano Config App has a complete different approach, it writes a new Task File in the filesystem of the Logger.
A lot of work to change this in LK8000.
Go to Top of Page

falchettogiallo
Pulcino

Italy
34 Posts

Posted - 29/11/2020 :  15:47:37  Show Profile  Reply with Quote
quote:
Originally posted by AlphaLima

OK found it, the Nano Config App has a complete different approach, it writes a new Task File in the filesystem of the Logger.
A lot of work to change this in LK8000.




Thanx for your reply AlphaLima..
I will try to ask LXNAX in order to obtain protocol documentation..
As if you are able to declare a task, in my opinion you should have the possibility to set the sector type information..

Edited by - falchettogiallo on 29/11/2020 15:50:11
Go to Top of Page

falchettogiallo
Pulcino

Italy
34 Posts

Posted - 08/01/2021 :  10:03:36  Show Profile  Reply with Quote
quote:
Originally posted by AlphaLima

Of course it is, but it does not work for the Nano4 (or I don't know how) and it is a non documented command.
We cannot implement it without a command reference.
I will implement it when I get the command description and find the time. But I'm very busy next year building a house.



Hello AL!
I got a protocol documentation file from LXNAV..
I think paragraphs 3.4 and 3.5 could be interesting..
LX has been very fast and responded me immediately..

I send the link to you privately

Ciao!


SAMPLE DECLARATION TO LX NANO

HFPLTPILOT:Uros Krasovic
HFCM2CREW2:
HFGTYGLIDERTYPE:
HFGIDGLIDERID:
HFCIDCOMPETITIONID:
HFCCLCOMPETITIONCLASS:
C041120134044041120110402
C0000000N00000000E
C4846667N01015883EAALEN HEIDENHEI::585.00000
C4711500N00942100ED21CH NENZING::572.00000
C4748667N01346550EEBENSEE EBXTRAUN::420.00000
C4744100N01133100EWACKERSBERG::731.00000
C0000000N00000000E
LLXVOZ=-1,Style=2,R1=3000m,A1=45.0,R2=0m,A2=0.0,A12=193.6,Maxa=0m,Line=1,Autonext=1,Lat=4846.667N,Lon=01015.883E,Near=0
LLXVOZ=0,Style=1,R1=5000m,A1=180.0,R2=0m,A2=0.0,A12=44.7,Maxa=0m,Autonext=1,Lat=4711.500N,Lon=00942.100E,Near=0
LLXVOZ=1,Style=1,R1=10000m,A1=90.0,R2=0m,A2=0.0,A12=261.9,Maxa=0m,Autonext=1,Lat=4748.667N,Lon=01346.550E,Near=0
LLXVOZ=2,Style=3,R1=500m,A1=180.0,R2=0m,A2=0.0,A12=87.9,Maxa=0m,Autonext=1,Lat=4744.100N,Lon=01133.100E,Near=0
LLXVTSK,StartOnEntry=false,Short=false,Near=false


OTHER LINES FOR DECLZONE part of the declaration

LLXVOZSTART=0,Style=2,R1=3000m,A1=45.0,R2=0m,A2=0.0,A12=16.7,Maxa=0m,Autonext=1,Lat=0000.000N,Lon=00000.000E,Near=0
LLXVOZPOINT=0,Style=1,R1=3000m,A1=45.0,R2=0m,A2=0.0,A12=165.8,Maxa=0m,Autonext=1,Lat=0053.961N,Lon=00016.188E,Near=0
LLXVOZFINISH=0,Style=3,R1=3000m,A1=45.0,R2=0m,A2=0.0,A12=315.0,Maxa=0m,Autonext=1,Lat=0016.188N,Lon=00053.961E,Near=0

Edited by - falchettogiallo on 08/01/2021 12:42:18
Go to Top of Page

AlphaLima
Moderator

Germany
1929 Posts

Posted - 08/01/2021 :  16:14:14  Show Profile  Visit AlphaLima's Homepage  Reply with Quote
THIS is the declaration file, it does not work for the serial protocol, and it is not documented at all.
I will not guess what eventually will work, so if LXNAV don't have a specification I will not programm change anything at all.
Go to Top of Page

falchettogiallo
Pulcino

Italy
34 Posts

Posted - 08/01/2021 :  17:18:55  Show Profile  Reply with Quote
quote:
Originally posted by AlphaLima

THIS is the declaration file, it does not work for the serial protocol, and it is not documented at all.
I will not guess what eventually will work, so if LXNAV don't have a specification I will not programm change anything at all.




I asked again LXNAV. I hope they will provider further informations (if they are interested)
Anyway the point is that ZONE TYPE and other parameters of the task CAN be transmitted through the declararion procedure.. So I just hope they will document the domains for every parameter
Go to Top of Page

falchettogiallo
Pulcino

Italy
34 Posts

Posted - 08/01/2021 :  23:24:06  Show Profile  Reply with Quote
This is the end..

Very very sad.. I think I did all I could do.. :(

I must say that, after I obtained support from LX Navigation during all the 2019 winter and convinced them to provide you with an ERA vario for development puposes, now I tried this action with LXNAV to obtain also their support... I think it's enough..

Ciao!



UPDATE: This morning I received an email from LXNAV, just a few words:
"We must update the protocol document"


Edited by - falchettogiallo on 09/01/2021 14:42:55
Go to Top of Page

falchettogiallo
Pulcino

Italy
34 Posts

Posted - 09/01/2021 :  01:34:12  Show Profile  Reply with Quote
Anyway, I found a solution:

in the S100 as in NANO or all the LX instruments, there is a SETUP MENU to define the DEFAULT zone type for START, POINTS and FINISH.
In this way, as far as my tasks usually have LINE START and LINE END, LK8000 can send the task declaration without specifying the zone types: the logger will use the DEFAULT types accordingly...

Ciao!
Go to Top of Page
Page: of 4 Previous Topic Topic Next Topic  
Previous Page | Next Page
 New Topic  Reply to Topic
Jump To:
PostFrontal Forum © PostFrontal - La community del Volo a Vela Go To Top Of Page
This page was generated in 0.2 seconds. Snitz Forums 2000

Suggerimenti dello staff:

                                         

Note legali (italiano):
Privacy Policy Cookie Policy
Legal notice (english):
Privacy Policy Cookie Policy

PostFrontal S.A.S. di Giuliano Golfieri & c. - P.I. 05264240960