Re: [Flightgear-devel] Citation Bravo ADF
On Mon, Mar 1, 2010 at 3:27 PM, syd adams wrote: > Ive switched back to the generic adf for the time being , I hadn't noticed > the kr-87 problem before . I also tried settiing the adf-btn to true in the > set file , but apparently that gets overridden . > I guess a quick fix would be to set the button to true in the code but > I'd need to dig through my manuals again to remember what ANT mode does > agian ... I think it focused more on the signal , (but that's from memory , > could be wrong)... ANT = antenna -- it disconnects the directional antenna and gives you a plain AM radio signal. It's officially used for hearing NDB station idents more clearly, and unofficially used for listening to AM-radio sports games during long flights. All the best, David -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Citation Bravo ADF
If you put this in your .fgfsrc, the ADF is alive at the start: > > --prop:/instrumentation/adf/adf-btn=true > > The property seems a bit broken, though, because it's really a toggle > among ADF and ANT modes (and others?), so something like > > --prop:/instrumentation/adf/mode=adf > > would make much more sense. I also notice that /radios or /avionics > (I don't remember which) got moved to /instrumentation. Most pilots > would never refer to avionics as "instruments" or "instrumentation", > but I do understand how the lines are blurring with glass panels, etc. > > > All the best, > > > Davids > > Ive switched back to the generic adf for the time being , I hadn't noticed the kr-87 problem before . I also tried settiing the adf-btn to true in the set file , but apparently that gets overridden . I guess a quick fix would be to set the button to true in the code but I'd need to dig through my manuals again to remember what ANT mode does agian ... I think it focused more on the signal , (but that's from memory , could be wrong)... Syd -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Citation Bravo ADF
On Sun, Feb 28, 2010 at 5:15 PM, syd adams wrote:
> Actually I think it might be a problem with kr-87.cxx , but I havent quite
> sorted that out yet ... as far as the ADF needle goes .
>
> Even with power , it doesnt appear to come alive until you toggle the ADF
> button on the radio .
If you put this in your .fgfsrc, the ADF is alive at the start:
--prop:/instrumentation/adf/adf-btn=true
The property seems a bit broken, though, because it's really a toggle
among ADF and ANT modes (and others?), so something like
--prop:/instrumentation/adf/mode=adf
would make much more sense. I also notice that /radios or /avionics
(I don't remember which) got moved to /instrumentation. Most pilots
would never refer to avionics as "instruments" or "instrumentation",
but I do understand how the lines are blurring with glass panels, etc.
All the best,
Davids
>
> I dont see the nasal errors your reporting .
> I'll keep digging .
>
>
>
> On Sat, Feb 27, 2010 at 2:22 PM, bitwPolly wrote:
>>
>> This, as far as I can tell, is the cause of the problems with Bravo's ADF
>> needle:
>> In Aircraft/Instruments-3d/primus-1000/P100.nas line 323: maghdg
>> -=getprop("environment/magnetic-variation-deg"); maghdg can return 'nil'
>> at startup so
>> the following addition fixes a thrown error: if (maghdg == nil ) maghdg=0;
>> Also, a nasal error is reported at startup from the following line 363:
>> me.NavTime.setValue(ttg); where ttg has apparently been formatted some
>> lines earlier.
>> I'm not sure what problem nasal has with the resulting format but
>> commenting out line 363 stops that error being flagged.
>> The result of either of the two errors is to stop the ADF/NAV needles
>> being updated, _only_ after the 'NAV' panel button has been clicked. ( On
>> startup the needles
>> work fine but freeze once that panel button is clicked).
>> The nasal error messages would be a lot easier to spot if the console
>> messages relating to multiplayer status and more particularly so many AI
>> models being missing could be suppressed. Thanks, (blucher)
>>
>>
>> --
>>
>>
>> --
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> ___
>> Flightgear-devel mailing list
>> Flightgear-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
>
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Citation Bravo ADF
Actually I think it might be a problem with kr-87.cxx , but I havent quite
sorted that out yet ... as far as the ADF needle goes .
Even with power , it doesnt appear to come alive until you toggle the ADF
button on the radio .
I dont see the nasal errors your reporting .
I'll keep digging .
On Sat, Feb 27, 2010 at 2:22 PM, bitwPolly wrote:
> This, as far as I can tell, is the cause of the problems with Bravo's ADF
> needle:
> In Aircraft/Instruments-3d/primus-1000/P100.nas line 323: maghdg
> -=getprop("environment/magnetic-variation-deg"); maghdg can return 'nil'
> at startup so
> the following addition fixes a thrown error: if (maghdg == nil ) maghdg=0;
> Also, a nasal error is reported at startup from the following line 363:
> me.NavTime.setValue(ttg); where ttg has apparently been formatted some
> lines earlier.
> I'm not sure what problem nasal has with the resulting format but
> commenting out line 363 stops that error being flagged.
> The result of either of the two errors is to stop the ADF/NAV needles
> being updated, _only_ after the 'NAV' panel button has been clicked. ( On
> startup the needles
> work fine but freeze once that panel button is clicked).
> The nasal error messages would be a lot easier to spot if the console
> messages relating to multiplayer status and more particularly so many AI
> models being missing could be suppressed. Thanks, (blucher)
>
>
> --
>
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Citation Bravo ADF
This, as far as I can tell, is the cause of the problems with Bravo's ADF
needle:
In Aircraft/Instruments-3d/primus-1000/P100.nas line 323: maghdg
-=getprop("environment/magnetic-variation-deg"); maghdg can return 'nil'
at startup so
the following addition fixes a thrown error: if (maghdg == nil ) maghdg=0;
Also, a nasal error is reported at startup from the following line 363:
me.NavTime.setValue(ttg); where ttg has apparently been formatted some
lines earlier.
I'm not sure what problem nasal has with the resulting format but
commenting out line 363 stops that error being flagged.
The result of either of the two errors is to stop the ADF/NAV needles
being updated, _only_ after the 'NAV' panel button has been clicked. ( On
startup the needles
work fine but freeze once that panel button is clicked).
The nasal error messages would be a lot easier to spot if the console
messages relating to multiplayer status and more particularly so many AI
models being missing could be suppressed. Thanks, (blucher)
--
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
