Re: [Flightgear-devel] Citation Bravo ADF

2010-03-01 Thread David Megginson
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

2010-03-01 Thread syd adams
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

2010-03-01 Thread David Megginson
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

2010-02-28 Thread syd adams
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

2010-02-28 Thread bitwPolly
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


[Flightgear-devel] Citation Bravo Launch Problem (syd Adams)

2006-03-28 Thread Stephen Miller
Syd: Tried to launch this, but I get what appears to be an "enhanced"
C-172 panel, but with jet engine sound??? Also get a "primitive basic
aircraft" model showing up in the external views. Just downloaded the
Bravo today from the FG web site.
Steve



---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Citation Bravo ....

2006-03-24 Thread Julien Pierru
No problem, I understand completly, i just pointed it out.
And thanks for your nice work, i really enjoy the Bravo.

Julien


[Flightgear-devel] Citation Bravo ....

2006-03-24 Thread syd & sandy

Hi Julien ,
the Bravo , (and the rest of my aircraft)  are works in progress  
it may be a long time before every aspect is finished (if ever) ... but 
I should be able to send an update in a few days with the flightdirector 
/ autopilot partially functional (heading & altitude).

These things take a lot of time and research
Cheers,
Syd


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] Citation Bravo

2006-03-23 Thread Julien Pierru
The Citation Bravo has a couple of "broken" instruments, the autopilot doesn't do anything when engaged and the fuel gauges do not show any fuel level at all. I am runnging CVS/HEAD as of 03/23/2006 20:44 GMT.
Julien