Speed Posted March 12, 2011 Posted March 12, 2011 either that, or replacing one widget a billion times. In which case, you'll need to buy stock in "Microdyne Widgets, Inc. 5 ohm resistor, type B" :megalol: Hell, by that time, the pilot, having fixed it himself three dozen times, would just carry spares in his pocket and replace it while on altitude hold :D Intelligent discourse can only begin with the honest admission of your own fallibility. Member of the Virtual Tactical Air Group: http://vtacticalairgroup.com/ Lua scripts and mods: MIssion Scripting Tools (Mist): http://forums.eagle.ru/showthread.php?t=98616 Slmod version 7.0 for DCS: World: http://forums.eagle.ru/showthread.php?t=80979 Now includes remote server administration tools for kicking, banning, loading missions, etc.
Conure Posted March 12, 2011 Author Posted March 12, 2011 Hell, by that time, the pilot, having fixed it himself three dozen times, would just carry spares in his pocket and replace it while on altitude hold :D You're presuming the altitude hold works! Intel i7 6700k, Asus GTX1070, 16gb DDR4 @ 3200mhz, CH Fighterstick, CH Pro Throttle, CH Pro Rudder Pedals, Samsung Evo 850 SSD @ 500GB * 2, TrackIR 5 and 27" monitor running at 2560 * 1440, Windows 10.
todd022 Posted March 12, 2011 Posted March 12, 2011 This kind of thing is pretty much real life as far as the Marine Corps is concerned. I work with "C" model (and a spattering of A++) Hornet drivers, they no-$#it, brief non-technical troubleshooting procedures for specific aircraft in the squadron. For example: "If 402 won't select JDAM with, LITENING pod active, above 90% humidity, etc., etc., kick the $#IT out of the box behind the DDI". Point is, parts aren't ALWAYS replaced just because there is an infrequent problem. At least not in the Marine Corps (but we don't have a budget like the Air Force either....not at all). [SIGPIC][/SIGPIC]
effte Posted March 12, 2011 Posted March 12, 2011 Unfortunately, "infrequent" is the thing complete CADC failures are not at this point. I'm with MrYenko. I think they have hold of an MTBF indicating roughly how often the unit is squawked, which could be for very minor issues which do not really degrade the mission capability, and they have used this to model how often we get a complete failure. ----- Introduction to UTM/MGRS - Trying to get your head around what trim is, how it works and how to use it? - DCS helos vs the real world.
MrYenko Posted March 12, 2011 Posted March 12, 2011 For example: "If 402 won't select JDAM with, LITENING pod active, above 90% humidity, etc., etc., kick the $#IT out of the box behind the DDI".. Non-technical people would probably be amazed how often solutions like that actually work... :thumbup:
Conure Posted March 12, 2011 Author Posted March 12, 2011 Non-technical people would probably be amazed how often solutions like that actually work... :thumbup: I've always thought that - Often when electronics don't work, they start working when they're knocked! Very strange...Probably something to do with dodgy connections? Intel i7 6700k, Asus GTX1070, 16gb DDR4 @ 3200mhz, CH Fighterstick, CH Pro Throttle, CH Pro Rudder Pedals, Samsung Evo 850 SSD @ 500GB * 2, TrackIR 5 and 27" monitor running at 2560 * 1440, Windows 10.
effte Posted March 12, 2011 Posted March 12, 2011 Avionics troubleshooting 101: Swap the L/H and R/H side units and see if the fault changes sides or disappears. Actually, that's probably the 201. First, you write it off as failure of the nut connecting the yoke to the seat at least two times... ----- Introduction to UTM/MGRS - Trying to get your head around what trim is, how it works and how to use it? - DCS helos vs the real world.
MrYenko Posted March 12, 2011 Posted March 12, 2011 I've always thought that - Often when electronics don't work, they start working when they're knocked! Very strange...Probably something to do with dodgy connections? "F/O's ILS pitch crossbar will not move from stowed position." "Cleaned cannon-plug connections with electrical contact cleaner, IAW DC-10 MM 24-00-00, ops check good." Translation: I re-racked the box downstairs with a FURIOUS VENGEANCE, and sprayed the back with canned air.
Slayer Posted March 12, 2011 Posted March 12, 2011 I like how armchair pilots come here to complain about the statistical anomolies of component failure. Nothing like splitting hairs. [sIGPIC][/sIGPIC] System Specs Intel I7-3930K, Asrock EXTREME9, EVGA TITAN, Mushkin Chronos SSD, 16GB G.SKILL Ripjaws Z series 2133, TM Warthog and MFD's, Saitek Proflight Combat pedals, TrackIR 5 + TrackClip PRO, Windows 7 x64, 3-Asus VS2248H-P monitors, Thermaltake Level 10 GT, Obutto cockpit
Conure Posted March 12, 2011 Author Posted March 12, 2011 I like how armchair pilots come here to complain about the statistical anomolies of component failure. Nothing like splitting hairs. Many of us armchair pilots also fly in real life! Also, a statistical anomaly is one thing, starting up and waiting for EGI to align, then spending 10 minutes configuring flight plan etc only for the CACD to fail for no apparent reason is quite another. Of course we split hairs..Many of us aren't here simply to play a game, but to get as close to possible as flying an aircraft out of reach for many of us...We aspire for absolute perfection and will complain when anything deviates :D Intel i7 6700k, Asus GTX1070, 16gb DDR4 @ 3200mhz, CH Fighterstick, CH Pro Throttle, CH Pro Rudder Pedals, Samsung Evo 850 SSD @ 500GB * 2, TrackIR 5 and 27" monitor running at 2560 * 1440, Windows 10.
effte Posted March 12, 2011 Posted March 12, 2011 I like how armchair pilots come here to complain about the statistical anomolies of component failure. Great! I'm sure a lot of people were wondering how you felt about it. Now we know! :thumbup: 1 ----- Introduction to UTM/MGRS - Trying to get your head around what trim is, how it works and how to use it? - DCS helos vs the real world.
MadTommy Posted March 12, 2011 Posted March 12, 2011 3 CACD failures in one 1:30 session, 2 in 5 minutes... whether it is accurate or not, its bloody annoying, happened twice while taxiing. I fly for fun, these failures don't fall into that category... it would be nice if this could be reduced please. I don't mind random failures.. but at this frequency its tedious. i5-3570K @ 4.5 Ghz, Asus P8Z77-V, 8 GB DDR3, 1.5GB GTX 480 (EVGA, superclocked), SSD, 2 x 1680x1050, x-fi extreme music. TM Warthog, Saitek combat pro pedals, TrackIR 4
andysim Posted March 12, 2011 Posted March 12, 2011 Its like that old maintainence report. "Autopilot seems a little rough. Fixed: Autopilot not installed on this aircraft"
effte Posted March 12, 2011 Posted March 12, 2011 Psst, Andy, I think that was "autoland". ;) "Autopilot produces 200 fpm descent in level hold" "Unable to reproduce on ground" There's a long list of those wonderful squawks out there on the international e-intrawebs. ----- Introduction to UTM/MGRS - Trying to get your head around what trim is, how it works and how to use it? - DCS helos vs the real world.
Stretch Posted March 12, 2011 Posted March 12, 2011 How come so many people are calling it the CACD?? Guys ... it's CADC. Central Air Data Computer. Tim "Stretch" Morgan 72nd VFW, 617th VFS Other handles: Strikeout (72nd VFW, 15th MEU Realism Unit), RISCfuture (BMS forums) PC and Peripherals: https://pcpartpicker.com/user/RISCfuture/saved/#view=DMp6XL Win10 x64 — BMS — DCS — P3D
Conure Posted March 12, 2011 Author Posted March 12, 2011 How come so many people are calling it the CACD?? Guys ... it's CADC. Central Air Data Computer. No no, you're mistaken...We're all talking about the CACD...You've obviously not got to that part of the manual yet... :bounce::bounce::bounce: Been wanting to use them for a while...Sorry... 1 Intel i7 6700k, Asus GTX1070, 16gb DDR4 @ 3200mhz, CH Fighterstick, CH Pro Throttle, CH Pro Rudder Pedals, Samsung Evo 850 SSD @ 500GB * 2, TrackIR 5 and 27" monitor running at 2560 * 1440, Windows 10.
wickedfastball Posted March 13, 2011 Posted March 13, 2011 I'll cast my vote for "bloody annoying." Was flying a quick MP mission the other day, got all started up, sitting there waiting for my flight to taxi, master caution starts going off.... CADC failure. Dang. Decided to press on with the flight anyway. Kinda tedious without that device but I still got a gun kill with no PAC. Hooah!
Leachman Posted March 13, 2011 Posted March 13, 2011 Yeah please allow probability adjustment, at least in a file.
Topgun505 Posted March 14, 2011 Posted March 14, 2011 Ok now I don't feel bad. On a recent mission I started up and took off. Fenced in and at the IP got a target on the TGP ... just as I hit the switch to make it SPI my right MFD and HUD blinked off and my CICU caution light came on. I know I hadn't gotten close enough yet to be shot at (but just to be sure I checked external view for holes .... nada) ... so this musta been a random failure. But yeah ... quite annoying spending 20 min getting the bird warmed up, all options set, and getting in to the target area, only to have to abort and RTB. Topgun505 Win 11 Pro, Intel Core i9-14900kF, Gigabyte RTX 4080 Super, 128 GB DDR5, Corsair Hx1000i, Alienware 34" 2K LED, TrackIR 5 Pro, WinWing F-16EX, WinWing F-15Ex throttle, VPC Warbird rudder, Thrustmaster MFDs x3, Black Hog box.
Ptroinks Posted March 21, 2011 Posted March 21, 2011 I don't mind there being a random failure generator. What I DO mind, is that we can't turn it off if we want to! I am sick and tired of starting up my jet, going through all the checklists, and then have some #¤%& random failure just after take off. It doesn't exactly make me look forward to my next flight! Yes, having system failures is realistic, but pleeease, give us the ability to turn it off! [sIGPIC][/sIGPIC]
Rainmaker Posted March 21, 2011 Posted March 21, 2011 In 20 years and 10000 + hours of flying modern jets with Air Data Computers just like those in the A-10, I have never had one fail. In the severest of icing I have never had a modern pitot system become blocked. I have only had the pitot system overheat once and that was in LAS in July when the FO mistakenly turned it on during the Recieving flow and not during the After Start flow (and it was easily reset once it cooled). In other words, in one month of flying this sim, I've experienced this failure enough for 20 lifetimes. Please fix it. Not saying the mean time between failures is not too high at the current moment, but comparing a civilian aircraft to a military one is apples and oranges. Most aged fighters in the AF right now are running in the upper teens for maintenenance hours per flying hours. As an example, the last time I looked for the F-15, we were somewhere around a 17 to 1. Meaning for every flight hour, you are looking at 17 maintenance hours on the same aircraft. The F-14 was in the high 20's before retirement, hance it's decision to get shwacked from service. Our maintenance is a lot higher than the civilian equivalent. I've got a few avionics buds from my time on the E models(avionics coded folks in the AF are coded to work F-15's and A-10's) that work A-10C's over at Spang, and from spending some time with them out in Vegas, the A-10C's are not doing that much better for having a new avionics suite in them. Now granted a lot of these are PMC discrepancies and don't impose an a non mission capable status, but they are still broke none the less. Many faults that you would find troubling, are flown with day in and day out on most aircraft. Something like a air data computer would certainly ground an aircraft, and I am not disagreeing with you on that...just pointing out that our discrepancy rate is a lot higher that what is posed on the civilian side of the house.
latearrival Posted March 21, 2011 Posted March 21, 2011 ED: can you tell us what MTBF you are using for the CADC so that we can compare this to our experiences? It might be a bug after all. Windows 10 | i5 2500k @ 4.4Ghz | MSI GTX 970 4GB | 8GB RAM | ASRock P67 Extreme4 | Seasonic X-Series 650W PSU | Oculus Rift DK2 | CH Fighterstick, Throttle & Pedals
Smokin Hole Posted March 21, 2011 Posted March 21, 2011 OK let's talk ADC: This component is so vital to safe operation that you cannot compare it to other, far more failure-prone, "avionics". It has the added benefit of being simple which further explains why 99% of us who fly professionally, either in the military, civilian, or mixed worlds will NEVER see this failure. The closest thing you might encounter is an "Airspeed Unreliable" warning (or something similar), which would indicate a less than nominal operation of the air data system but not a complete failure. There are at least two pitot systems, at least two static systems, temperature probes, computers, etc which all combine to make this thing about as fail-safe as possible. And when it does fail, a la Air France, it is as I keep repeating extremely rare and usually the result of extreme circumstances not contemplated by the designer.
Jinja Posted March 21, 2011 Posted March 21, 2011 +1 for option to turn off random failures. With 2 young kids, I only get the odd chance to get away for a short 2 mission sortie. Having 20 minutes of preflight and ferrying to the action wasted by a random failure definitely wastes my valuable time. Not cool! i7@3.5Ghz, ATI 5870, 16GB RAM, win7 64bit, TH2GO, Track-IR, 4screen pit, TM WArthog HOTAS
Temphage Posted March 21, 2011 Posted March 21, 2011 Not saying the mean time between failures is not too high at the current moment, but comparing a civilian aircraft to a military one is apples and oranges. Most aged fighters in the AF right now are running in the upper teens for maintenenance hours per flying hours. As an example, the last time I looked for the F-15, we were somewhere around a 17 to 1. Meaning for every flight hour, you are looking at 17 maintenance hours on the same aircraft. The F-14 was in the high 20's before retirement, hance it's decision to get shwacked from service. Our maintenance is a lot higher than the civilian equivalent. I've got a few avionics buds from my time on the E models(avionics coded folks in the AF are coded to work F-15's and A-10's) that work A-10C's over at Spang, and from spending some time with them out in Vegas, the A-10C's are not doing that much better for having a new avionics suite in them. Now granted a lot of these are PMC discrepancies and don't impose an a non mission capable status, but they are still broke none the less. Many faults that you would find troubling, are flown with day in and day out on most aircraft. Something like a air data computer would certainly ground an aircraft, and I am not disagreeing with you on that...just pointing out that our discrepancy rate is a lot higher that what is posed on the civilian side of the house. As a 2A371 (C for what it's worth), I support this message. Although I've not touched an A-10, honestly it's amazing that F-15Es don't explode in midair or flip over off the runway, careen into the ramp, and blow up everything else. Pilots literally end missions carrying bits of the cockpit with them, and a 12-turn-8 typically ends with fifteen or more writeups, most of which aren't the 'sign it off' kind (up yours 'display too dim in night mode'). That said, if they're simulating a failure as being 'working 100% or totally inop', that's wrong. I seriously would love to see real failures simulated. For example, rather than your HUD going out, it experiences a video failure that makes all the stroke video blurry, or maybe it's scrunched on one side. An ADP failure on an F-15E can induce all kinds of crazy bullshit like Pitch Ratio warnings. Buttons get stuck, display lines blank out, and partial functionality is the norm. You might get TACAN bearing, but no range or distance. Your radio works fine, except it produces an irritating squeal every time it's keyed...
Recommended Posts