• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

ADF and NAV IDs

O

oliver_mpt

Messages
45
Country
france
Hello to All !

Has anyone used the ADF IDENT and NAV IDENT variables mentionned in the doc file ? I am trying to get the tuned facility names (ICAO codes), but these variable apparently don't work, I get an exception in the log file :

> 8046.24987 [63, 3]AddToDataDefinition:DefineID=0, DatumName="adf ident", UnitsName="string", DatumType=5, fEpsilon=0.000000, DatumID=1
< 8046.24989 [63] >>>>> EXCEPTION=7, SendID=3, Index=3 <<<<<

You experts have an idea about what I missed ?
 
oliver_mpt said:
Has anyone used the ADF IDENT and NAV IDENT variables mentionned in the doc file ? I am trying to get the tuned facility names (ICAO codes), but these variable apparently don't work, I get an exception in the log file
Click to expand...

Although the documentation doesn't show it (editing error I assume), anything connected with an ADF, COM or NAV needs an index to tell SimConnect which one of the possible two such radios you are asking about. i.e. "ADF IDENT:1" for ADF1, etc.

Regards

Pete
 
Thanks again Pete for your help,

I tried with an index of 1 and I get the same exception in the log file

> 234.57648 [63, 3]AddToDataDefinition:DefineID=0, DatumName="adf ident:1", UnitsName="string", DatumType=5, fEpsilon=0.000000, DatumID=1
< 234.57652 [63] >>>>> EXCEPTION=7, SendID=3, Index=3 <<<<<

?? This is not my day ...

Oliver
 
more about it:

I have taken the SDK sample "Variable Strings" which reads the Title, Airline and Type strings for the aircraft. I changed the var name of the required strings to test :

ADF NAME:1 --> works perfectly
ADF IDENT:1 --> return an empty string

NAV NAME:1 --> works perfectly
NAV IDENT:1 --> empty string

Anyone succeeded to get the ICAO code of the navaids ?

:banghead:
Oliver
 
oliver_mpt said:
I tried with an index of 1 and I get the same exception in the log file

> 234.57648 [63, 3]AddToDataDefinition:DefineID=0, DatumName="adf ident:1", UnitsName="string", DatumType=5, fEpsilon=0.000000, DatumID=1
< 234.57652 [63] >>>>> EXCEPTION=7, SendID=3, Index=3 <<<<<
Click to expand...

Hmm. I've never used the units "string" -- all of the strings I read are typed "number". They work then. Don't ask me why.

with these errors, note the "Index=n" response. The index is a zero-based count to the parameter which is in error. In this case it is 3, meaning the 4th parameters, which is the units parameter.

Anyone succeeded to get the ICAO code of the navaids ?
Click to expand...

Yes, FSUIPC4 gets all these things, and all using SimConnect.

Try "number".

Regards

Pete
 
Solved :

Following pete's wise advice, I used "number" for the units of:
"adf ident:1"
"adf ident:2"
"nav ident:1"
"nav ident:2"
The index are effectively NOT mentionned in the documentation. I used a SIMCONNECT_DATATYPE_INT64 format and stored the result in a __int64 type variable, then casting it to a char string.

Works perfectly then.

Thanks again, Pete.

Oliver
 
You must log in or register to reply here.
Back
Top