Duckling

I just reread the first post again from home PC (1st was via my iphone, to small screen) 4k Euro ? Must be a mean monster machine ;-) Understand your frustration. Some other steps are to check the motherboards current firmware etc and USB port driver installed versions for possibly known issues and avalible updates on manufacturers site (if not made already) Cheers B-O

Hi gadget. Had a problem very like that in my old rig (same os) and it was directly related to usb ports on the PC motherboard. Devices incl TM stick and stick was failing frequently or did not pop up at all. Can't say cause is the same in your case but try different USB ports and only use good quility powered USB hubs (if you already do that also try swap the hub connect usb cable just in case. And verify functionallity on a secondary PC ( avoid all firmware upgrade attempts till the basic funtions been verified)

Hi Mojo. Easiest solution is to add a network switch (such as this) at your Sim PC room that connects to the the router, and hook in the PC and Ardiono Ethershield to that. Dual routers in same network will get messy to handle. Cost for a switch compared with two splitters and an extra cable would be lower and installation is just to hook it in.

Thanks Mike/Tacno for the heads'up Still in 1.2.4 ;-) /Gus edit: Anyone seen any info of this from ED in the changelog of the new version ? Would be nice to know before making the plunge..

Thanks :-)

Hi Levinsky. You are correct, either a step up/down but you can also set an absolut value for each freq 'knob' and device. Was some time since I made my panels (and still got some issues with the code in one direction of change but they end up into the correct value). search my buildtheard 'HOGBOX' for a code example. edit: a bit 'sleepy' last night, you're spot on above as far I see, Either an application handling the steps (up or down) or write an absolute value within the range, to set desired freq per wheel. Buttonnumber for the FM radio differs from my set, guess its another module than 10C ? Good to review the sripts also. Found the couse of why my indicators spins oddly in one direction, thanks ;-)

HarSu. Seat looks... fantastic.. Do you have some pics from within the hull of how you made the rolls for the raisers?

Indicators work at last (hipp hipp...) Turned out to be me (again) ;-) In v1.1 I'd moved the handling to 'export after each event' together with some instrument data and it was ok there. In v1.2.x they worked erratic or not at all. Shifting'em to 'after each frame' got'em operational again.

You meaning 'JIMsCat', right ? :-) Sweet Pit. Looking forward to more pics

Amazing, just amazing HarSu

Ha ! It works, just got myself an extra display here. Great find, Thanks Gremlin :thumbup:

Hi Hornet An option when using mechanical dials whould be to have a prepped script that when activated sets the freq to a preset value, I.e adjust dials as needed and write the preassigned freq to the sim triggerd by an optional button or likewise to sync'em to the sim (havn't tried it out though but it should work) 7 Segments are more generic and was a 'bit' faster to implement then the mechanical. It's a lot of adjustments to make and also to consider the opening on the base and lightpanel, harder to get it visible and with correct detents depending on the encoder. Using dials as Linden do have a more genuin flavour though :-) edit: The bonus (besides better looking) would be the savings in output port on your interface

You're very welcome HarSu. Great start, seems you halfway there already. Seat looks great :thumbup:

Complemets to your progress Hans. Looks great. /Gus

One option to get it strong for a lifetime would be to bring the stuff a someone with a TIG welding equipment. Fixate the bars on the frame and a half'n hour with the TIG whould hold it for ever.

Hi Jan and welcome. Agree totaly. Making the start to complex can turn it into pain instead. Started my first build with a Mac keyboard controllers and wired keys to a fake panel. From that point to now,it have turned into an (almost) obsession. Hard to walk by a dumpster without to see if some pieces missing could be found inside ( not totally kidding ;-) Electronics, coding etc will be more and more fluent and most of all it's fun. Only obsticles might be space and wify that ragards me not totally sane

Yupp I understand that and it's a fine approach as long as one keep one board per quad or that UFC is the only panel of interest. Next panel to interface would require an extra board, usb port and cabling etc and raise the complexity and portcost. Theres no right or wrong here and most comes down to tech demands and personal flavour. Lot of cards out there and these are only a few of em. Can't tell if Brydling has any in stock though

If you need a board with addiational ports for further expansion, checkout Brydlings usb 256 ports card under the 'Sell' threads

Just made the leap into the World version (v1.2.4) and after a some hours got Helios and SIOC working. Viewports and softTH setup not yet updated and the the few quads I tested so far seems ok. Even all the flightinstrument data exports works as far I can see. Much better then I feared :-) Only issue found so far is indicator output (warning displays etc) is erratic. They don't come on allways and when they do, they're static (non blinking prior master caution switch is clicked). My Sioc/export etc scripts from the earlier v1.1.1.1 not modified so 'something' in the new DCS structure is diffrent Is there anyone that have had same issues or has some ideas where to start the troubleshooting ? All indicators are Opencockpit/SIOC controlled, Helios is used for visual reference of instrument data (no other cards involved) Cheers Gus

Welcome HarSu. Don't toss'em what ever you do (to expensive). Still running My rig on 1.1.x but pancake on 'world' i think. Must be more around here ?

Post 7 above updated with some additional info Enjoy /Gus

Just found this thread on cockpit .org: http://www.mycockpit.org/forums/general-builder-questions-all-aircraft-types/19893-huey-uh-1-details.html

Sure does , (missing in the our 'Huey' though)

Some measurements, taken with a 'yardstick'. In metric though.. - Floor width , behind pilot seats 207cm with doors opened, 197 cm with doors closed. - From that 'line' to front bubble 170 cm (floor level) (along the pedestal right side) - From line behind pilot seat to front of floor (excluding the feet-pads) 100 cm - From line behind pilot seat to front of feet-pads 120 cm - From line behind pilot seat to pedals (centered) 114 cm (floor level) - From line behind pilot seat to stick center 76 cm - Cockpit inside width measured at front instrument panel bottom, 175 cm - Instrumet panel width 100,8 cm - From line behind pilot seat to roof 160 cm (note that the roof inside is lightly higher just a few inches behind that line - Floor to roof in front (just aft the main 'window' and instrument panel, 140 aprox - Stick to Stick distance 108 cm (measured at base of handle) - Stick hight from floor (total) 58 cm - Stick top of 'bend' (same as beneath the Handle) from floor 45,6 cm - Stick diamater 1,5 inch (aprox) - Offset between lower part of stick to the base of handle 12,5 cm (center to center) - Hight of the seat (i.e. top of seat pad) front 36 cm, back 28 cm, - Collective , (right seat) lenght from floor to top, 64 cm, (that the total, oc) - Collective control (the box on top, not sure about name here) h10,5 x w11,5cm) - Space between pedestal and pilot seat (eerrhhh, missed that. be back on this) ** - Distance between door innerside and seat (measured in back of seat) 20 cm. The 'steelbar' on seatside not included. - Distance between seats 68 cm (excluding steelbar) - Distance bewteen seat 'inner' side to pedestal 19,5 cm - Pedestal width (main part exluding map pocket and other stuff) 29,7 cm - Pedestal Hight (to dzuz rails at rear 28,5cm, hight in front 43,5 mm (measured 90 degree angle from floor), pedestal lenght topside 68cm. - From 'line' behind pilot seat to pedestal 18 cm

It's included in the package. Check the unzipped package and the folder "LCDComVersion" for the file "LCDComVersion.ino"