Duckling

Hehe, lets not show that statement to wify :-) I build the frame with 20 degrees verusus base for throttle and 30 for the fuel pan. I guess 10 deg for throttle and 25-30 would have been closer to the real thing. The front inst pan distance from bottom to base would be 2 cm less also then on my rig ending up with aprox 9,5 cm. As fortunate I got long arms :pilotfly:to reach the panels

Throttle to large to fit ? Use a saw ... took some time before I descided to try it though...:smilewink:

icemaker, can't thank you (and the others contributing here). You just made my day here :notworthy: /Gus

Sweet setup Red. The pics are stunning and the setup is even better :thumbup:

Hehe. Great setup Gadroc. Goes beyond the wideview term. Must be great rig to use

Red, check http://forums.eagle.ru/showthread.php?t=66885 post #14 Added a few pics from real A-version instrument panel, centerpart and 'step' dims should be the same as C-version (but can't say for sure though ;-)

Added some measurement of real A-10A instrument panel Even if most of you goes for the C-version, overall dims and center part should by correct. Enjoy -edit: dims in Metric (mm) Cheers /Gus

Must getting to familuar to the A version :doh: . Just realised that the "pole" on your instrument pan lower left side is missing, the segment isolating the AHCP and the pan with clock, standby ADI, UHF display and AoA. Might been stated above in the thread though. (or you probably aware of it allready) cheers Gus

It worked like a charm. Used "HW_Stick Calibration_V1_11" and I'm home free Many thanks Keiserb Why TM not has this for download is amazing ;-) cheers Gus

Hi Guys edit: (hehe, typo in subject, should been "stick" :-) Got an odd thing after I made the firmware upgrade of the stick to version 11 (from version 6). Movement is limited to top left quadrant, see pic Had it unplugged some weeks while I made an upgrade to Win7 but was operational till that point. Fw upgrade made twice and shows "successful". Throttle fw upgarded with no problem. (i didn't verify it prior the fw upgrade though) This is either a fw upgrade issue or the sensor/mechs in base are damaged or likewise. Verified that the handle itself is "operational" on another base (i.e. calibrates ok and operates hole 360 degrees) The base has not been opened or modified in any way Ticket to TM opened a week ago but yet no answer from them any ideas ?

Hi Red I was wrong :-/ about "capacitor" Turned out it's diodes instead to be used, hehe , sorry You find a solution in the first thread below, second for more info Check: http://www.viperpits.org/smf/index.php?topic=4583.0 http://www.viperpits.org/smf/index.php?topic=5902.0 I got 4 connected currently on my SAS panel. 12V source for the coil triggerd by 4 outputs from a Mastercard. Switch position controlled by 8 inputports on same Mastercard http://strandedduckling.com/HOGBOX_SAS_4.JPG http://strandedduckling.com/L06_SAS_PCB_connection_schema.jpg I got an old "no-name" PC powersupply for testing the quads (+5 and +12 Volts) Cheers Gus

Hey Red. Got a hunch you know it already but to avoid any mistakes, those Magswitchitches you got (congrats, a very nice catch), make sure you get that diode cross poles in place (I see it on at lest one of the switches on the "group pic"). Without it, the switch produce a large voltage "spike" when released, causing a havoc on the IF boards I'm running mine on 12 V, so a regular PC Voltage supply probably be sufficient without going to MIL levels. Can't say for yours though /Gus

Hi Red. With your pace of progress it's hard for an oldie just to get time to read the updates (very nice pics btw) What measurement do you search for ? /Gus

And a few others MS33638_case_instrument.pdf MS33639_instrument_case.pdf

Some inputs on gauges Not all the correct ones but it spec the console and panel cut-outs MS33545_case_instrument.pdf MS33549_case_instrument.pdf MS33556_case_instrument.pdf

Hi Red. That pan is a good start, congrats. Looking forward to see your progress. Can't agree on the statment about "not knowing" though. You sure seem to be in control :-) I'm using Alu also (3 mm flat currently) but if cashflow increases, plan is to have the mid sections cut in blocks and and then TIG'ed to main panel.

Welcome back DM Guess it gonna be some realy nice pics. You have a habit of finding all the nice parts we others just dreams about. Looking forward to an update :-)

Distiler, Nate, Burner many thanks Right on spot, Distiler. It related to either the 7950GT , driver or Win7 (cant say what of these) The "bad" card worked well under XP so I guess its a Win7 driver issue (tried at least three different versions but the all gave allmost the same results as the posted pics displays) I swapped to the even older X1650 and the graphics returned to normal. Application "crash" when quitting also gone :thumbup: Since I made a complete new installation of win7 , and also rebuild the rig with "new" cards and drivers, also the new app and patch it's hard to track down the cause. Babysteps next time for me :smilewink: I know these cards are oldies as my rig and both needs a refresh, but know I'm at least able to start it up. Cheers Gus

Thanks Nate , "tweaks" made or installed Nvidia driver updated to 266.58 Win7SP1 (32), 4gig RAM Sim installed and patch .6 remains as is (no modification) Must be something I overlooked :-/ Greatfull for any input pics below from the training missions Extract from "dcs" file: 00018.539 ERROR DXRENDERER: DXDefTextureManager: can't find gausse.bmp 00018.977 ERROR DXRENDERER: DXDefTextureManager: can't find rl_target_sprite.bmp 00018.979 ERROR DXRENDERER: DXDefTextureManager: can't find noise_beam_0_256x1.bmp <snip> 00033.022 WARNING NGMODEL: Model '/models//uaz-469.lods' has invalid bounding box. 00041.799 ERROR WRADIO: "NDB" beacon is on the water! 00043.965 WARNING WRADIO: Map objects for beacon site Ялта NOT FOUND! Ojbects created. 00044.067 WARNING WRADIO: Map objects for inactive beacon site Мыс Кыз-Аул NOT FOUND! Ojbects created. 00045.077 WARNING WRADIO: Map objects for inactive beacon site Мыс Сухумский NOT FOUND! Ojbects created. 00045.151 WARNING WRADIO: Map objects for beacon site Мыс Евпаторийский NOT FOUND! Ojbects created. 00045.231 ERROR WRADIO: "NDB" beacon is on the water! 00045.231 ERROR WRADIO: "NDB" beacon is on the water! 00045.243 WARNING WRADIO: Map objects for inactive beacon site Мыс Железный Рог FOUND. Beacon linked to this objects. 00045.341 WARNING WRADIO: Map objects for beacon site Мыс Херсонесский NOT FOUND! Ojbects created. 00045.498 WARNING WRADIO: Map objects for beacon site Потийский NOT FOUND! Ojbects created. 00045.667 WARNING WRADIO: Map objects for inactive beacon site Мыс Анапский NOT FOUND! Ojbects created. 00045.691 ERROR WRADIO: "NDB" beacon is on the water! 00045.995 WARNING WRADIO: Map objects for inactive beacon site Мыс Кодошский FOUND. Beacon linked to this objects. <snip> 00050.442 WARNING NGMODEL: Model '/models//an-26b.lods' has invalid bounding box. <snip> 00054.751 ERROR LIVERY_MANAGER: Can't open livery '0' for model 'uh-1h'. Reason: no such dir or archive. 00055.128 ERROR LIVERY_MANAGER: Can't open livery '0' for model 'uh-1h'. Reason: no such dir or archive. 00059.860 ERROR LIVERY_MANAGER: Can't open livery '81st fs spangdahlem afb (sp)_01' for model 'a-10c'. Reason: no such dir or archive. 00075.883 ERROR COCKPITBASE: Cockpit::avDevice::link_all: unable to find link variable 'TGPinterface' for device 'MAIN_PANEL' 00075.883 ERROR COCKPITBASE: Cockpit::avDevice::link_all: unable to find link variable 'padlock' for device 'MAIN_PANEL' 00075.883 ERROR COCKPITBASE: Cockpit::avDevice::link_all: unable to find link variable 'betty' for device 'AAR47' 00078.762 WARNING COCKPITBASE: Cockpit: MapObjectsBuffer . Specific element 23 not implemented, map may be incorrect 00078.762 WARNING COCKPITBASE: Cockpit: MapObjectsBuffer . Specific element 24 not implemented, map may be incorrect 00080.263 WARNING COCKPITBASE: Cockpit: MapObjectsBuffer . Specific element 23 not implemented, map may be incorrect 00080.263 WARNING COCKPITBASE: Cockpit: MapObjectsBuffer . Specific element 24 not implemented, map may be incorrect 00081.175 ERROR COCKPITBASE: Cockpit: Clickable - Wrong connector name EW-LGT-R1 <snip> 00103.944 ERROR EDTERRAINGRAPHICS3: Material: edgemat FxMaterial_Runway31 terrain/shaders31/Runway31.fx|FOG_ENABLE|LIGHT_TEXTURE airfield_asphalt_06.png airfield_asphalt_06_nm.png black.tga black.tga 0 00103.944 ERROR EDTERRAINGRAPHICS3: dont bind geometry edgelgeom 37231258 00104.093 ERROR EDTERRAINGRAPHICS3: Material: edgemat FxMaterial_Runway31 terrain/shaders31/Runway31.fx|FOG_ENABLE|LIGHT_TEXTURE airfield_asphalt_06.png airfield_asphalt_06_nm.png black.tga black.tga 0 00104.093 ERROR EDTERRAINGRAPHICS3: dont bind geometry edgelgeom 37230e10 00106.657 WARNING NGMODEL: Model '/models//trees_1_blk.edm' has invalid bounding box. 00106.660 WARNING NGMODEL: Model '/models//trees_3_blk.edm' has invalid bounding box. 00106.662 WARNING NGMODEL: Model '/models//trees_5_blk.edm' has invalid bounding box. 00106.664 WARNING NGMODEL: Model '/models//trees_6_blk.edm' has invalid bounding box. 00106.666 WARNING NGMODEL: Model '/models//trees_7_blk.edm' has invalid bounding box. 00107.114 WARNING NGMODEL: Model '/models//trees_8_blk.edm' has invalid bounding box. 00107.116 WARNING NGMODEL: Model '/models//trees_9_blk.edm' has invalid bounding box. 00108.221 WARNING NGMODEL: Model '/models//trees_2_blk.edm' has invalid bounding box. 00108.360 WARNING NGMODEL: Model '/models//trees_4_blk.edm' has invalid bounding box. 00111.043 ERROR DXRENDERER: DXDefTextureManager: can't find white.png 00111.044 ERROR DXRENDERER: DXDefTexture: failed to load white.png. Reason: D3DXERR_INVALIDDATA. 00113.417 ERROR GRAPHICSXP: ModelManager: can't find LAP-CABLES <snip> 00121.698 ERROR DXRENDERER: DXDefTexture: failed to load gausse.bmp. Reason: D3DXERR_INVALIDDATA. 00121.710 ERROR DXRENDERER: DXDefTexture: failed to load rl_target_sprite.bmp. Reason: D3DXERR_INVALIDDATA. 00121.720 ERROR DXRENDERER: DXDefTexture: failed to load noise_beam_0_256x1.bmp. Reason: D3DXERR_INVALIDDATA. 00127.962 ERROR DXRENDERER: Create texture "_resampleToLumMap" (RENDER_TARGET - D3DFMT_R16F) failed!, D3DERR_INVALIDCALL 00128.594 INFO DXRENDERER: Creating Resource "Unicode" of type 5 00133.760 WARNING FLIGHT: HELIPAD + FARP-1 has no ATC communicator! 00133.760 WARNING FLIGHT: HELIPAD + FARP-2 has no ATC communicator! <snip> Cheers Gus DCS10C_1.0.0.6errs.zip

Just made a complete new install of Win7 (32bit) on my old rig, version 1 and patch .6 Been running XP and Beta 3 earlier. Water as background but nothing else seen. Thats true for ramp starts and a few training missions etc. Starting in air shows panels "distorted" and details missing here and there. Stick handle shown opaque and some other odd graphics overlayed here and there. I know this isn't much for a problem description but gotta catch some sleep before tomorrow. Tried the option above to uncheck the Hotas sync but no joy. Back to troubleshooting tomorrow ;-) Since it a complete reinstall and upgrade before checking functionallity, the cause is a bit hard to track with all new drivers etc. Could it be Direct X related ? ps. running on 2 gig only. additional is inbound . ds Cheers Gus

Looking very good Jon. A bit hard to see all the details though but no worries :-) Only note is the courner radius of the baseplate's/lightpanels but I guess it's known You plan to make a customized/home made throttle ? Cheers Gus

Agree Those looks amazing !!! Congrats

Separating the PCB from the display is doable but the risk of damaging either of'em in the process is high. One option would be to cut the pins between display from the PCB and soldering a ribbon cable extension or likewise between'em (short as possible) but there's no guarantee it will be successfull. I asked the same quiz some time ago to one of the soldering Wizards I know but he turned me down due to the above reasons. If it shows possible though, it would realy ease build of the panel.

Myself, I'll go for a VFD (hopfully) controlled by IOcard LCD card. Got two of the displays (2*20 +2*16) on the shelf. 2*16 fits on the quad but I've fiddled around still with the 2*20 display to fit the pieces together. 2*20 will allow a blank character between the sections. Problem is that the PCB expands over where the buttons needs to be. 2*16 fits but will not allow the needed space bwteween the sections. Interfacing OLED (that would do the trick) is out of my reach. (still a long way go :-) /Gus

As long as you ask for planning but not yet in 'production'... ;-) I'll go for IOCard 7 segment display card output controlled by SIOC /Gus