VDGS: Stop Fail always with TFDI 717

Home Forums Support VDGS Pack VDGS: Stop Fail always with TFDI 717

Topic Resolution: Resolved
Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • #3676
    Urmel81

    Hello,

    with the TFDI 717 I’ll get always the STOP FAIL message. Doesn’t matter how far I’m away. As soon as I start activating VDGS this message appears, after a few seconds the whole VDGS goes off. Then I need to Activate it again, but with the same reaction. An friend get’s the same message with the TFDI, other Aircraft are working.

    VDGS: APIS ++

    Any idea?

    Thanks

    #3678
    12bPilot

    In the aircraft.cfg, what is defined for the „atc_model“ key in the [General] section?

    #3679
    Urmel81

    In the aircraft.cfg, what is defined for the „atc_model“ key in the [General] section?

     

    Seems correct, checked it already.

    B717

     

    Regards Urmel

     

    #3681
    Urmel81

    Any more ideas?

    Thanks Urmel

    #3685
    12bPilot

    Alright, found the problem.

    An entry in the AircraftParameters.ini file is missing for the B717

    [B717]

    1L = 2.0, -0.2, 4.0, 1.50, 1.65

    While these figures are not tested (they define how the jetway hood is fitting the aircraft door), it makes the VDGS work at least.

    The entry will be included in the next SODE release, but you can just manually add it to the file (and fine tune the values if you wish, since I don’t own the B717)

    Thanks for reporting!

    #3687
    Urmel81
    1. Alright, found the problem. An entry in the AircraftParameters.ini file is missing for the B717

      [B717] 1L = 2.0, -0.2, 4.0, 1.50, 1.65

      While these figures are not tested (they define how the jetway hood is fitting the aircraft door), it makes the VDGS work at least. The entry will be included in the next SODE release, but you can just manually add it to the file (and fine tune the values if you wish, since I don’t own the B717) Thanks for reporting!

    Great. Thanks for the support and you fantastic tool.

    Regards

    Urmel

    #3817
    vekant

    Hello, I would like to point out that the ERJ Feelthere makes the same error.

    #3977
    Urmel81

    After some time I didn’t use the 717 I’ll get now an ERROR message from the VDGS.

     

    The Sode log tells me: could not detect Nosewheel.

    Any idea?

    Regards

    Urmel

    #3981
    12bPilot

    After some time I didn’t use the 717 I’ll get now an ERROR message from the VDGS. The Sode log tells me: could not detect Nosewheel. Any idea? Regards Urmel

    SODE tries to figure out the nosewheel position from the aircraft.cfg data, more specifically from the [contact_points] entry. How does that look like for the 717?

    #3983
    Urmel81

    I think it’s faulty.

    The aircraft received an update.

    My installation is brand new.

    [contact_points]
    // Gear    0     1        2       3      4    5   6      7    8     9     10    11    12   13     14     15
    point.0  = 1,  54.00,   -0.40, -9.14, 2500.0, 0, 1.07, 82.0, 0.50, 2.24, 1.50, 4.00, 5.00,  0, 250.0, 300.0
    point.1  = 1,  54.00,    0.40, -9.14, 2500.0, 0, 1.07, 82.0, 0.50, 2.24, 1.50, 4.00, 5.00,  0, 250.0, 300.0
    point.2  = 1,  -4.10,  -9.20, -9.89, 2500.0, 1, 1.80,  0.0, 2.50, 0.550, 0.95, 6.00, 7.50,  2, 250.0, 300.0
    point.3  = 1,  -4.10,  -7.20, -9.89, 2500.0, 1, 1.80,  0.0, 2.50, 0.550, 0.95, 6.00, 7.50,  2, 250.0, 300.0
    point.4  = 1,  -4.10,   7.20, -9.89, 2500.0, 2, 1.80,  0.0, 2.50, 0.550, 0.95, 6.50, 7.00,  3, 250.0, 300.0
    point.5  = 1,  -4.10,   9.20, -9.89, 2500.0, 2, 1.80,  0.0, 2.50, 0.550, 0.95, 6.50, 7.00,  3, 250.0, 300.0

    // Scrapes 0     1        2       3         4   5   6      7    8     9     10    11    12   13     14     15
    point.6  = 2,  53.500,   0.000,  -5.30, 700.0, 0, 0.00,  0.0, 0.00, 0.00, 0.00, 0.00, 0.00,  4,   0,0,   0.0 //Front fuselage
    point.7  = 2,  62.000,   0.000, -1.80,  700.0, 0, 0.00,  0.0, 0.00, 0.00, 0.00, 0.00, 0.00,  4,   0,0,   0.0 //Nose
    point.8  = 2, -22.000,   0.000, -4.90,  700.0, 0, 0.00,  0.0, 0.00, 0.00, 0.00, 0.00, 0.00,  4,   0,0,   0.0 //Lower rear fuselage
    point.9  = 2, -29.800,   0.000, -4.10,  700.0, 0, 0.00,  0.0, 0.00, 0.00, 0.00, 0.00, 0.00,  4,   0,0,   0.0 //Scrape fin
    point.10  = 2, -13.50, -45.750,  -0.90, 700.0, 0, 0.00,  0.0, 0.00, 0.00, 0.00, 0.00, 0.00,  5,   0,0,   0.0 //Port wingtip
    point.11  = 2, -13.50,  45.750,  -0.90, 700.0, 0, 0.00,  0.0, 0.00, 0.00, 0.00, 0.00, 0.00,  6,   0,0,   0.0 //Starboard wingtip
    point.12  = 2, -50.800,  0.000,  1.00,  700.0, 0, 0.00,  0.0, 0.00, 0.00, 0.00, 0.00, 0.00,  6,   0,0,   0.0 //Rear fuselage tip
    point.13  = 2, -45.000,   0.000, 19.50, 700.0, 0, 0.00,  0.0, 0.00, 0.00, 0.00, 0.00, 0.00,  6,   0,0,   0.0 //Vertical stabiliser front
    point.14  = 2, -59.00,   0.000, 20.50,  700.0, 0, 0.00,  0.0, 0.00, 0.00, 0.00, 0.00, 0.00,  6,   0,0,   0.0 //Vertical stabiliser rear
    point.15  = 2, -60.50, -18.250,  16.50, 700.0, 0, 0.00,  0.0, 0.00, 0.00, 0.00, 0.00, 0.00,  6,   0,0,   0.0 //Horizontal stabiliser port
    point.16  = 2, -60.50,  18.250,  16.50, 700.0, 0, 0.00,  0.0, 0.00, 0.00, 0.00, 0.00, 0.00,  6,   0,0,   0.0 //Horizontal stabiliser starboard

    static_pitch         = 0

    #3991
    12bPilot

    Thanks.

    I see…why would they split the front gear in two individual entries? Never seen that before, every other aircraft just has one contact point defined per gear, and for the nosegear I assumed the contact point to be on the longitudinal axis, so on 0.0. That’s why SODE doesn’t pick it up.

    For this 717, the are on -0.4 and 0.4 (point.0 and point.1, third parameter).

    Well I guess I need to change that within SODE and hope it doesn’t break other aircraft…

    #3993
    Urmel81

    Thanks. I see…why would they split the front gear in two individual entries? Never seen that before, every other aircraft just has one contact point defined per gear, and for the nosegear I assumed the contact point to be on the longitudinal axis, so on 0.0. That’s why SODE doesn’t pick it up. For this 717, the are on -0.4 and 0.4 (point.0 and point.1, third parameter). Well I guess I need to change that within SODE and hope it doesn’t break other aircraft…

     

    I’ve posted it in the TFDi support forum. Maybe you should ask if the can remove it. Than no other aircraft will have maybe an issue.

    #4045
    12bPilot

    Released V1.6.8 of SODE, supporting slight lateral offsets of nosewheel definitions in the aircraft.cfg (up to 0.5)

    #4072
    Urmel81

    Released V1.6.8 of SODE, supporting slight lateral offsets of nosewheel definitions in the aircraft.cfg (up to 0.5)

    Fantastic support, thanks for your fast help! Great

    Regards

    Urmel

Viewing 14 posts - 1 through 14 (of 14 total)
  • You must be logged in to reply to this topic.