fixed [REPORTED] Probe Heat Not Working

Track size is 21MB so it's obviously not attached. If any of the mod/testers are interested I can email it.

Did a 1.5 hour tour of the Caucuses at ~26,000ft., ambient surface temp -9C. Around halfway through the flight (49 min according to TacView) the aircraft starts performing a sine wave while in ALT hold, slowly climbing then slowly descending with increasing amplitude but negligible change in indicated airspeed and altitude. Found probe heat switch at the back of the left console and turned it on. After another 30+minutes airspeed indicator and altimeter still hadn't recovered. Flipped Probe Heat switch to test and it blinks on the master caustion panel, but the light isn't illuminated when the switch is in the on position. Instruments didn't recover until dropping below ~12,000ft. while approaching the airport.

Probe heat should be on with no Weigh On Wheels (WOW) regardless of probe heat switch position. The switch is just there in case icing conditions exist on the ground prior to take off.

I have experience this before but can't reproduce it consistently.

https://forums.eagle.ru/showpost.php?p=4172859&postcount=38

I was a little surprised that I was having the issue. I know irl the probe heat is hand-checked prior to taxi. As it stands in DCS the probe heat switch sits in a position labeled as OFF (at least that's its default cold start position), it can be flipped down into a spring-loaded TEST position, and also up into, presumably, an ON position (though it's not labeled as such.) I flipped it on when I noticed the issue but saw no results.

Track size is 21MB so it's obviously not attached. If any of the mod/testers are interested I can email it.

 

Did a 1.5 hour tour of the Caucuses at ~26,000ft., ambient surface temp -9C. Around halfway through the flight (49 min according to TacView) the aircraft starts performing a sine wave while in ALT hold, slowly climbing then slowly descending with increasing amplitude but negligible change in indicated airspeed and altitude. Found probe heat switch at the back of the left console and turned it on. After another 30+minutes airspeed indicator and altimeter still hadn't recovered. Flipped Probe Heat switch to test and it blinks on the master caustion panel, but the light isn't illuminated when the switch is in the on position. Instruments didn't recover until dropping below ~12,000ft. while approaching the airport.

I encountered this in the same conditions. Cold and high. I think I was at 28k maybe higher? IMN of about .80 with a climb. The jet eventually departed flight and got into probably the deepest stall. I wish I had a video of it. Basically the jet turned into a Harrier with a flame.

Sent from my iPad using Tapatalk Pro

... As it stands in DCS the probe heat switch sits in the off position, or at least labeled as such...

The switch will be labeled as off but the probes heat will come on with no WOW, that is one of the reasons we pull the circuit brakes when raising the aircraft with fuselage jacks.

Yeah I’ve had this issue as well. Can’t reproduce it but it’s always in cold weather. Stuck/eronious airspeed readings and the sometimes it’ll depart and end up in a flat spin.

Track size is 21MB so it's obviously not attached. If any of the mod/testers are interested I can email it.

Did a 1.5 hour tour of the Caucuses at ~26,000ft., ambient surface temp -9C. Around halfway through the flight (49 min according to TacView) the aircraft starts performing a sine wave while in ALT hold, slowly climbing then slowly descending with increasing amplitude but negligible change in indicated airspeed and altitude. Found probe heat switch at the back of the left console and turned it on. After another 30+minutes airspeed indicator and altimeter still hadn't recovered. Flipped Probe Heat switch to test and it blinks on the master caustion panel, but the light isn't illuminated when the switch is in the on position. Instruments didn't recover until dropping below ~12,000ft. while approaching the airport.

What was the speed you were flying with?

No guys, the track file isn’t “missing”, I know exactly where it is. And you’re welcome to it:

If any of the mod/testers are interested I can email it.

Or update these archaic upload limitations to something useful smdh.

You can post it to an external site such as Google Drive, then share the link in this thread.

Or Dropbox

Sent from my iPhone using Tapatalk Pro

You know what, it’s alright. I’m aware that outside file hosting exists, but I’m not using my personal resources to cover ED’s (or vBulletin’s) deliberate shortcomings. And who are we kidding that they’d even be able to make it 49 minutes into the track to view the issue. The bug is thoroughly and accurately described, it’s corroborated by other users. Fix it or don’t, it’s your sim.

You know what, it’s alright. I’m aware that outside file hosting exists, but I’m not using my personal resources to cover ED’s (or vBulletin’s) deliberate shortcomings. And who are we kidding that they’d even be able to make it 49 minutes into the track to view the issue. The bug is thoroughly and accurately described, it’s corroborated by other users. Fix it or don’t, it’s your sim.

Regardless of it being accurately described and corroborated its a difficult bug to replicate, I know because I've wasted a couple of hours TRYING to replicate this issue, in the very same mission where I had it happen to me a couple of times in the past. Unless the devs can replicate it, it can be difficult for them to track down exactly what is causing the problem. So if you have a track of it, it would be great if you could find some way of hosting it so the devs can download it. Yes I know the forum size limit is annoying.

There should be also a probe Heat monitor that illuminates the PROBE HEAT caution

light in case the airflow decreases under certain value e.g. if blocked by ice. Apparently it doesn't work now.

EDIT: Also multiple FLCS FAULTs should occur in case of blocked air data probes and sensors.

I just want to check if it was already reported but in this case, I just add a trackfile here.

@Nineline, @BigNewy

This was the last time I encountered the PITOT Bug.

After switching it "on" manually, it took about 1-2 minutes and the speed came back.

https://drive.google.com/open?id=10ssVgcjxBCPG1PdX9xBX2jrM8kaCDl4-