• Re: Why does Clearnav II display "fc" after windspeed?

    From carbonprop@21:1/5 to cjk on Thu May 25 15:12:57 2023
    On Thursday, May 25, 2023 at 3:48:03 PM UTC-6, cjk wrote:
    In my ClearNav II flight computer's wind speed/direction box, it gives the wind speed as (for example) "16 fc". I would expect "16 kts", or just "16". What the heck is an "fc"?
    “f" indicates CN II is communicating with FLARM. “c" indicates CN II is communicating with a Cambridge 302

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From cjk@21:1/5 to All on Thu May 25 14:48:01 2023
    In my ClearNav II flight computer's wind speed/direction box, it gives the wind speed as (for example) "16 fc". I would expect "16 kts", or just "16". What the heck is an "fc"?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From cjk@21:1/5 to carbonprop on Fri May 26 06:32:06 2023
    On Thursday, May 25, 2023 at 5:12:59 PM UTC-5, carbonprop wrote:
    On Thursday, May 25, 2023 at 3:48:03 PM UTC-6, cjk wrote:
    In my ClearNav II flight computer's wind speed/direction box, it gives the wind speed as (for example) "16 fc". I would expect "16 kts", or just "16". What the heck is an "fc"?
    “f" indicates CN II is communicating with FLARM. “c" indicates CN II is communicating with a Cambridge 302

    Thanks! While I do have FLARM, I don't have a Cambridge 302. Do you suppose the CN II displays "c" because it's communicating with my ClearNav vario?

    Is the wind speed/direction calculation more accurate because CN II is getting data from FLARM &/or a vario? I would think the CN II itself would have all of the inputs for that calculation, without getting data from another device...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dan Daly@21:1/5 to cjk on Fri May 26 09:53:20 2023
    On Friday, May 26, 2023 at 9:32:10 AM UTC-4, cjk wrote:
    On Thursday, May 25, 2023 at 5:12:59 PM UTC-5, carbonprop wrote:
    On Thursday, May 25, 2023 at 3:48:03 PM UTC-6, cjk wrote:
    In my ClearNav II flight computer's wind speed/direction box, it gives the wind speed as (for example) "16 fc". I would expect "16 kts", or just "16". What the heck is an "fc"?
    “f" indicates CN II is communicating with FLARM. “c" indicates CN II is communicating with a Cambridge 302
    Thanks! While I do have FLARM, I don't have a Cambridge 302. Do you suppose the CN II displays "c" because it's communicating with my ClearNav vario?

    Is the wind speed/direction calculation more accurate because CN II is getting data from FLARM &/or a vario? I would think the CN II itself would have all of the inputs for that calculation, without getting data from another device...

    CNv shows as a 302; do a declaration to the CNv and it shows as C302. I like that they adopted something that worked when they designed it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From carbonprop@21:1/5 to Dan Daly on Sat May 27 06:11:49 2023
    On Friday, May 26, 2023 at 10:53:22 AM UTC-6, Dan Daly wrote:
    On Friday, May 26, 2023 at 9:32:10 AM UTC-4, cjk wrote:
    On Thursday, May 25, 2023 at 5:12:59 PM UTC-5, carbonprop wrote:
    On Thursday, May 25, 2023 at 3:48:03 PM UTC-6, cjk wrote:
    In my ClearNav II flight computer's wind speed/direction box, it gives the wind speed as (for example) "16 fc". I would expect "16 kts", or just "16". What the heck is an "fc"?
    “f" indicates CN II is communicating with FLARM. “c" indicates CN II is communicating with a Cambridge 302
    Thanks! While I do have FLARM, I don't have a Cambridge 302. Do you suppose the CN II displays "c" because it's communicating with my ClearNav vario?

    Is the wind speed/direction calculation more accurate because CN II is getting data from FLARM &/or a vario? I would think the CN II itself would have all of the inputs for that calculation, without getting data from another device...
    CNv shows as a 302; do a declaration to the CNv and it shows as C302. I like that they adopted something that worked when they designed it.

    I believe that CNII calculates its own wind without FLARM and CNv calculates its own wind using the ADC.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Cochrane@21:1/5 to All on Sun May 28 10:46:24 2023
    Actually, an important part of your pretakeoff checklist ought to be to make sure the clarnav does show "fc." It's possible that it doesn't make connection with flarm or vario, and if so you need to recycle power.
    John Cochrane

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dan Marotta@21:1/5 to John Cochrane on Sun May 28 17:16:24 2023
    Happened to me today. I looked at the ClearNav and it only showed the
    little "c". I cycled the power and it did not come back up. Another
    power cycle and the CN came back up with only the "f". A couple more
    switch actions and I got "fc". What a pain...

    Dan
    5J

    On 5/28/23 11:46, John Cochrane wrote:
    Actually, an important part of your pretakeoff checklist ought to be to make sure the clarnav does show "fc." It's possible that it doesn't make connection with flarm or vario, and if so you need to recycle power.
    John Cochrane

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Moshe Braner@21:1/5 to John Cochrane on Mon May 29 19:39:25 2023
    On 5/28/2023 1:46 PM, John Cochrane wrote:
    Actually, an important part of your pretakeoff checklist ought to be to make sure the clarnav does show "fc." It's possible that it doesn't make connection with flarm or vario, and if so you need to recycle power.
    John Cochrane


    A friend has a CNav2, and it shows "fc", but does not show FLARM traffic
    on the map. What is he missing in the settings or whatever? He's got
    the latest (as it is) firmware installed.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From S9@21:1/5 to All on Tue Jun 6 18:10:22 2023
    The "fussiness" of the power on sequence is driven by software in the ClearNav flight computer. It polls the serial ports roughly 40 seconds after switch on and if there is nothing on the port, it does not poll it again.

    Once com is established, the peripheral device may be power cycled at will, CN will pick it up as soon as it becomes available again.

    If you have some sort of problem in flight that requires power cycling CN flight computer, all current flight information and the flight log is saved (continuously) and will be restored on reboot. Task statistics included. Flight log will be continuous
    (less whatever period of time CN is shut down) and fight log will be secure an valid.

    This is the latest info I have, it may have been changed in the latest release....

    Stephen

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dan Marotta@21:1/5 to All on Wed Jun 7 08:12:26 2023
    Thanks! From now on I'll turn on the vario and Flarm first and have
    them established before turning on the CNII.

    Dan
    5J

    On 6/6/23 19:10, S9 wrote:
    The "fussiness" of the power on sequence is driven by software in the ClearNav flight computer. It polls the serial ports roughly 40 seconds after switch on and if there is nothing on the port, it does not poll it again.

    Once com is established, the peripheral device may be power cycled at will, CN will pick it up as soon as it becomes available again.

    If you have some sort of problem in flight that requires power cycling CN flight computer, all current flight information and the flight log is saved (continuously) and will be restored on reboot. Task statistics included. Flight log will be
    continuous (less whatever period of time CN is shut down) and fight log will be secure an valid.

    This is the latest info I have, it may have been changed in the latest release....

    Stephen

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)