• Categories
  • Recent
  • Tags
  • Popular
  • Users
Collapse
Just Flight Community Forum

Prop Heat is not working properly

Scheduled Pinned Locked Moved Piston & Turbine Dukes
5 Posts 3 Posters 312 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • RallerR Offline
    RallerR Offline
    Raller
    wrote on last edited by Raller
    #1

    I have the Piston Duke and Prop Heat is not working properly. All circuit breakers are pushed. No aktiv failures. Version 1.1

    • The "Prop Heat Ground Test" does not work on the ground. No display on the Prop Amps Meter.
    • In flight only the left prop heat works. The right one does not generate any deflection on the Prop Amp Meter.
    • The 20A Prop Circuit Breaker does not work either and has no effect.

    Is this a bug or am I doing something wrong?

    RandolfR 1 Reply Last reply
    0
  • RandolfR Offline
    RandolfR Offline
    Randolf
    replied to Raller on last edited by
    #2

    @Raller more info on how prop heat works on the Duke in this thread: https://community.justflight.com/topic/6411/propeller-heating

    1 Reply Last reply
    0
  • RallerR Offline
    RallerR Offline
    Raller
    wrote on last edited by
    #3

    @Randolf Thanks for the hint. Now I understand it and it works that left and right change every 30 seconds. The ground test also works if either the left or right or both prop heaters are switched on.

    Then there is only one thing left:

    • The 20A circuit breaker only interrupts the right prop heater. The left one continues to work every 30 seconds.
    1 Reply Last reply
    1
  • RallerR Offline
    RallerR Offline
    Raller
    wrote on last edited by
    #4

    Have you read this so that you can include it in the next update? @Black-Square

    1 Reply Last reply
    0
  • Black SquareB Online
    Black SquareB Online
    Black Square Black Square Developer
    wrote on last edited by
    #5

    I just went looking now. It was a single character error in the XML. The failure triggered from the tablet would have worked correctly, believe it or not. Thanks for pointing it out. It's nice when the problems are easy, but then it takes me ten times longer to reply and document the change than it did to actually fix the problem!

    1 Reply Last reply
    3

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Users