T O P I C R E V I E W |
Alessandro_1978 |
Posted - 12/10/2017 : 13:01:09 I tested the LXNav S100 linked via BT to LK8000 installed on Naviter Oudie forn a while. BT link works perfectly: the link is bi-directional (i can change MC, ballast, etc from both); i can see flarm traffic and get baro altitude as well.
i tryed all the LX drivers (like LXV7_xxx, LX16xx, etx) but after declaring the task, appears the message "logger not found"
i did tryed to link S100 to TopHat installed on my mobile (android version) using LXNAV standard driver and i can declare the task with easy.
is there a way to solve the declaration issue?
Alessandro
|
15 L A T E S T R E P L I E S (Newest First) |
falchettogiallo |
Posted - 25/02/2021 : 13:50:52 quote: Originally posted by wrogers
quote: Originally posted by falchettogiallo
quote: Originally posted by falchettogiallo
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!
Hello, this morning I had the opportunity to test this procedure and I confirm it's working! So, if your task have line start and stop and same sector type for all other points, just use the default "observation zones setup" menu. Your declared tasks will then be correct.
Ciao!
Does that mean it does not matter what you say in the LK8000 start, stop line/circle or TP sectors... the S100 will not see it. Just make sure you use the S100 default "observation zones setup" menu?
Exactly!
|
wrogers |
Posted - 24/02/2021 : 03:27:06 quote: Originally posted by falchettogiallo
quote: Originally posted by falchettogiallo
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!
Hello, this morning I had the opportunity to test this procedure and I confirm it's working! So, if your task have line start and stop and same sector type for all other points, just use the default "observation zones setup" menu. Your declared tasks will then be correct.
Ciao!
Does that mean it does not matter what you say in the LK8000 start, stop line/circle or TP sectors... the S100 will not see it. Just make sure you use the S100 default "observation zones setup" menu?
|
falchettogiallo |
Posted - 13/02/2021 : 14:38:57 quote: Originally posted by falchettogiallo
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!
Hello, this morning I had the opportunity to test this procedure and I confirm it's working! So, if your task have line start and stop and same sector type for all other points, just use the default "observation zones setup" menu. Your declared tasks will then be correct.
Ciao! |
falchettogiallo |
Posted - 15/01/2021 : 14:41:36 quote: Originally posted by brunotl
i don't understand the signification of "I think it's enough.." can you explain ?
I wanted to say that I'm tired of fighting in order to obtain support by LXNAV or LX Navigation.. They look at me as if I'm disturbing them.. So, if they are not interested in having proud customers, it's their problem... I will not fight anymore.. It's enough..
Ciao! ;) |
brunotl |
Posted - 14/01/2021 : 10:55:24 quote: Originally posted by falchettogiallo
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"
i don't understand the signification of "I think it's enough.." can you explain ?
|
wrogers |
Posted - 14/01/2021 : 06:25:49 falchettogiallo,
Thank you for the LXNav S100 and Nano declaration investigation. Your final solution will be investigated by me with my S100 in the Spring when flying. For sure... I'm going to carefully check my LK8000 declaration to the S100 recorder ! ... to verify this
Walt Rogers WX Discus 2a
|
falchettogiallo |
Posted - 09/01/2021 : 01:34:12 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!
|
falchettogiallo |
Posted - 08/01/2021 : 23:24:06 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"
|
falchettogiallo |
Posted - 08/01/2021 : 17:18:55 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 |
AlphaLima |
Posted - 08/01/2021 : 16:14:14 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.
|
falchettogiallo |
Posted - 08/01/2021 : 10:03:36 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
|
falchettogiallo |
Posted - 29/11/2020 : 15:47:37 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..
|
AlphaLima |
Posted - 29/11/2020 : 12:37:28 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.
|
AlphaLima |
Posted - 29/11/2020 : 10:35:18 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. |
falchettogiallo |
Posted - 29/11/2020 : 09:07:10 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
|
|
|