Some minor observations
-
Hey guys,
I've set up a complete new flight simming rig with only MSFS 2024 (SU 6), the Commander (1.1) and the KLN 90B. The last days I did the first system tests and one flight and want to share some observations concerning the Commander (TC) with you.
- With a valid ADF station tuned and signal received the morse code is heard when the ADF channel via the audio panel is activated. But it's even there if you don't pull out the MKR knob on the ADF or even if the ADF is shut off again.
- The settings on the audio panel aren't saved. Only the COM1 and MKR switch are on when starting a new session.
- The ILS 400 is alway on even if I shut it off last session (maybe one time it was saved but I'm not sure). (The same with the KLN 90B but that's maybe because it's not part of the Commander).
- With my new installation (and SU6?) first time in my MSFS2024 I experience the engine hours are saved between sessions (extreme cool!). But the hobbs does not start with the master switch but maybe with takeoff. It's not quite clear to me now. I've done a ground system check collecting 0.4 hours on the engine but the hobbs doesn't count time. Today I did my first flight and realized underway it started to count. There from comes my idea it started with takeoff. Another oddity: After shutdown the engine the engine tach showed 3.2 hours and the hobbs 3.1 hours. Seems the hobbs wants to overtake the engine hours...?
- The fuel estimates (REQ, RES etc.) of the EDM show the values concerning the next flight plan waypoint but not the destination of the flightplan. This is with the KLN 90B.
- Even if I delete the active (FPL 0) or stored flight plan (here: FPL 1) in the KLN 90B it's back with the next session. I suppose that has nothing to do with the Commander. But has anybody experienced such a behaviour with that unit?
- The KLN 90B and the MC60 digital localizer work together as the should but passing a flightplan waypoint the KLN 90B keeps alerting to adjust the the track forever. So you have the MSG alert alway on via the announciator and the KLN 90B keeps flashing the desired track and keeps the ADJ NAV IND CRS TO xxx message in the stack. From memory I'm not sure when the KLN 90B does stop this alert after passing a waypoint but I never had that persistant behaviour before. Maybe it has to do with the TRK function of the MC60: The KLN 90B awaits a kind of confirmation from the MC60 that the track was changed.
By the way: I'm waiting a least one minute with now interaction before ending the session. So persistence cycle should do it's work within the Commander.
The Commander is absolutey outstanding! I've flown a lot of study level MS aircraft over the last 30 years but that's the peak of the evolution for now!
Thanks!
-
Z Zacke referenced this topic
-
Correction:
-
The on/off state of the ILS 400 is saved correctly. It is just the rotating button that is not saved at the full left position but somewhere in between.
But the frequency of the ILS 400 seems not to be saved. -
AI says the problem with the restored flight plans within the KLN 90B could be that the state of the KLN is saved within the Commander system and then comes back up with the next seesion. But that seems not very plausible for me.
-
-
Hey guys,
I've set up a complete new flight simming rig with only MSFS 2024 (SU 6), the Commander (1.1) and the KLN 90B. The last days I did the first system tests and one flight and want to share some observations concerning the Commander (TC) with you.
- With a valid ADF station tuned and signal received the morse code is heard when the ADF channel via the audio panel is activated. But it's even there if you don't pull out the MKR knob on the ADF or even if the ADF is shut off again.
- The settings on the audio panel aren't saved. Only the COM1 and MKR switch are on when starting a new session.
- The ILS 400 is alway on even if I shut it off last session (maybe one time it was saved but I'm not sure). (The same with the KLN 90B but that's maybe because it's not part of the Commander).
- With my new installation (and SU6?) first time in my MSFS2024 I experience the engine hours are saved between sessions (extreme cool!). But the hobbs does not start with the master switch but maybe with takeoff. It's not quite clear to me now. I've done a ground system check collecting 0.4 hours on the engine but the hobbs doesn't count time. Today I did my first flight and realized underway it started to count. There from comes my idea it started with takeoff. Another oddity: After shutdown the engine the engine tach showed 3.2 hours and the hobbs 3.1 hours. Seems the hobbs wants to overtake the engine hours...?
- The fuel estimates (REQ, RES etc.) of the EDM show the values concerning the next flight plan waypoint but not the destination of the flightplan. This is with the KLN 90B.
- Even if I delete the active (FPL 0) or stored flight plan (here: FPL 1) in the KLN 90B it's back with the next session. I suppose that has nothing to do with the Commander. But has anybody experienced such a behaviour with that unit?
- The KLN 90B and the MC60 digital localizer work together as the should but passing a flightplan waypoint the KLN 90B keeps alerting to adjust the the track forever. So you have the MSG alert alway on via the announciator and the KLN 90B keeps flashing the desired track and keeps the ADJ NAV IND CRS TO xxx message in the stack. From memory I'm not sure when the KLN 90B does stop this alert after passing a waypoint but I never had that persistant behaviour before. Maybe it has to do with the TRK function of the MC60: The KLN 90B awaits a kind of confirmation from the MC60 that the track was changed.
By the way: I'm waiting a least one minute with now interaction before ending the session. So persistence cycle should do it's work within the Commander.
The Commander is absolutey outstanding! I've flown a lot of study level MS aircraft over the last 30 years but that's the peak of the evolution for now!
Thanks!
@Zacke said in Some minor observations:
But the hobbs does not start with the master switch but maybe with takeoff. It's not quite clear to me now. I've done a ground system check collecting 0.4 hours on the engine but the hobbs doesn't count time. Today I did my first flight and realized underway it started to count. There from comes my idea it started with takeoff.
https://community.justflight.com/topic/11138/hobbs-meter/5?_=1789409231747
That's just how the Hobbs meter is implemented in MSFS. It'll only start counting once airspeed exceeds 25 kts.
@Zacke said in Some minor observations:
The fuel estimates (REQ, RES etc.) of the EDM show the values concerning the next flight plan waypoint but not the destination of the flightplan.
That is how the EDM 700/800 is documented to work if there is a valid GPS signal.
-
@Zacke said in Some minor observations:
But the hobbs does not start with the master switch but maybe with takeoff. It's not quite clear to me now. I've done a ground system check collecting 0.4 hours on the engine but the hobbs doesn't count time. Today I did my first flight and realized underway it started to count. There from comes my idea it started with takeoff.
https://community.justflight.com/topic/11138/hobbs-meter/5?_=1789409231747
That's just how the Hobbs meter is implemented in MSFS. It'll only start counting once airspeed exceeds 25 kts.
@Zacke said in Some minor observations:
The fuel estimates (REQ, RES etc.) of the EDM show the values concerning the next flight plan waypoint but not the destination of the flightplan.
That is how the EDM 700/800 is documented to work if there is a valid GPS signal.
@fizzboy said in Some minor observations:
That's just how the Hobbs meter is implemented in MSFS. It'll only start counting once airspeed exceeds 25 kts.
Thanks! That was more or less my assumption. The Commander manual says it start's with the master switch.
@fizzboy said in Some minor observations:
That is how the EDM 700/800 is documented to work if there is a valid GPS signal.
Are you sure? I used that one with the A2A Aerostar and it showed the fuel at the destination. I think that makes much more sense. I think I have to read the EDM manual.
-
Update:
- The hobbs seems to run a little bit faster than the engine tach (or the tach is slower than the hobbs).
- KLN 90B: Today I entered new flight plans for FPL 0 and FPL 1 and the new ones are brought over to the next session. So it seems only blank FPL pages are not saved.
- Do I understand that right the prop does tick over by hand if the engine's hot but not if it's cold?
Thanks!
-
Mechanical tach timers run proportional to engine speed. Slower at low RPM and faster at higher RPM. The RPM at which tach hours equals clock hours varies with different tach models.
The Hobbs meter measures actual clock time that the engine is running.
At low power the tach should run a lot slower increase to near real time at full power.
-
Tach time should be calibrated to approximate accurate time at cruise rpm because that's where you spend most of your time. Here's a good description from https://pilotinstitute.com/hobbs-vs-tach-time/ :
The difference between Hobbs and tach time is the following:
Hobbs Time:
The time from when the engine starts to when the engine stops.
Tach Time:
At cruise RPM, tach time counts like a standard clock.
At an RPM less than cruise, tach time counts slower than a standard clock.
At an RPM more than cruise, tach time counts faster than a standard clock.Tach time can be compared to an odometer in a car. Tach time, which is measured by a tachometer, is primarily used to determine when maintenance should be performed on the aircraft.
Tach time can be thought of as “engine time” because it is a time measure of how much strain the engine has undergone.
Tach time is generally 20% less than Hobbs time, depending on the types of flights undertaken.
Both tach and Hobbs time are logged in the aircraft’s logbook (often referred to as a flight folio). This ensures that, if either the tachometer or Hobbs meter were to malfunction, the discrepancy between the two times would be noticed. It is imperative that you, as the pilot, confirm that both the tach and Hobbs time written in the flight folio corresponds to the indications in the aircraft before and after your flight.
