Uuuuaaaah..! I have started building now..!

[Sokol1_br]

Setelios2000,

 

Look in pags. 21-28 and 45 these topic, the TH69 arrange for engines control - with switch's.

 

Your can use pots for:

Cyclic X and Y axis and brake lever

Collective axis - some guys put a micro-stick (2 axis) to control shkval cam.

 

FOV zoom can by made by axis too - if you don't use TrackIR/Freetrack.

 

Soko1_Br

[londo-cat]

Setelios2000,

 

Look in pags. 21-28 and 45 these topic, the TH69 arrange for engines control - with switch's.

 

Your can use pots for:

Cyclic X and Y axis and brake lever

Collective axis - some guys put a micro-stick (2 axis) to control shkval cam.

 

FOV zoom can by made by axis too - if you don't use TrackIR/Freetrack.

 

Soko1_Br

 

I thought the Collective had 2 hat switches on it?

[Sokol1_br]

I thought the Collective had 2 hat switches on it?

 

Yes, two HAT's.

Front for storages select

External, internal, all and Air2air

 

Rear for control lights

Searchlight and landing

 

So, guys replace this one for a mini-stick (micro-stick like in PS2 gamepad)

for better control - with axis - of Shkval cam.

 

Sokol1

[talisman]

and tell me....

Does 1&2 want pots or just an ON/OFF switch(with a spring) ?

I saw that the 3 want ON/OFF switch only.

How about 4 ???

I saw that it goes for 3 different positions...

the one that posses and other 3.

So it wants a (3+1=) 4-way linear switch ?

pity i thought pots would be better.

thanks in advance

Ps so pots take only the centrall Joystic and the rudders right ?

 

Hello there, in your picture i have my layout as the following:

 

Rotor brake (3) - toggle on/off

 

engine cut offs (1 and 2) - two toggles (easy)

 

engine throttle - i have both of these mapped to a single axis - in this configuaration you can change the power settings proportionally just like the real thing.

 

as for the above - i decided that a slewable landing light wasnt high on my priority list and added a thumbjoy to my collective. The one i used has a switch activated by pressing down on the joy. therefor i have schval slew and target lock under my thumb on the collective. My collective in on the ikea pit thread somewhere.

 

cheers

[stelios2000]

Hello there, in your picture i have my layout as the following:

 

Rotor brake (3) - toggle on/off

 

engine cut offs (1 and 2) - two toggles (easy)

 

engine throttle - i have both of these mapped to a single axis - in this configuaration you can change the power settings proportionally just like the real thing.

 

as for the above - i decided that a slewable landing light wasnt high on my priority list and added a thumbjoy to my collective. The one i used has a switch activated by pressing down on the joy. therefor i have schval slew and target lock under my thumb on the collective. My collective in on the ikea pit thread somewhere.

 

cheers

thanksssssss

Edited August 5, 2009 by stelios2000

[ruprecht]

Trigger et al,

 

Don't mean to hijack the thread, but I've just finished my targeting mode control panel (image attached) - not my neatest work ever, but it's done. I've had a look through the lua export and can't find state objects for those button lights! is it just me, or are they missing from the data export?

 

I'd hate to have wasted all that money on lit pushbuttons if the data export isn't available for those buttons!

 

Thanks

[stelios2000]

Hello there, in your picture i have my layout as the following:

 

Rotor brake (3) - toggle on/off

 

engine cut offs (1 and 2) - two toggles (easy)

 

engine throttle - i have both of these mapped to a single axis - in this configuaration you can change the power settings proportionally just like the real thing.

 

as for the above - i decided that a slewable landing light wasnt high on my priority list and added a thumbjoy to my collective. The one i used has a switch activated by pressing down on the joy. therefor i have schval slew and target lock under my thumb on the collective. My collective in on the ikea pit thread somewhere.

 

cheers

 

 

 

can you please show me how you did it ?

cause with ON/OFF switch it is easy but with toggle im having a hard time

thanks in advance

stelios

[Triggerhappy69]

Hey guys. I'm off sailing on the East coast of Sweden right now. But I'll try to reply whatever I can tonight. 'Dunno when I'll be in a harbour with internet next time.

 

PS. The coast outside Stockholm is a just gorgeous..!

[Triggerhappy69]

Trigger et al,

 

Don't mean to hijack the thread, but I've just finished my targeting mode control panel (image attached) - not my neatest work ever, but it's done. I've had a look through the lua export and can't find state objects for those button lights! is it just me, or are they missing from the data export?

 

I'd hate to have wasted all that money on lit pushbuttons if the data export isn't available for those buttons!

 

Thanks

 

I think the only way to achieve this (as of right now) is by conytrolling the lights through a secondary software (like SIOC for Opencockpits cards). What type IO card do you use?

[Triggerhappy69]

Guys guys guys..! No more talking about "highjacking" the thread.. This is OUR thread and as such can not be highjacked..

[Triggerhappy69]

How are you gonna fabricate this panel, especially with the angle between the top part and side part?

 

the angle is set by the end panels mate. My plan for the panel as a whole is to first glue all sides and fronts together, ignoring the gaps and minor flaws that come from sawing. And the cover it all with a couple of layers of fibreglass to bring structural strength and gap-filling. then I'll sand all sides and fronts smooth with a belt sander, add some filler to the holes in the fibreglass, and THEN cut out the openings for the panels.

 

I might just skip cutting out holes for the panels all together. Depending on what is more practical.

 

Trigger... seriously - where do you *GET* the time to do all this. Just reading your advancements on the pit make my head spin! Thanks for uploading the specs on the panel sir!

 

He he.. 'dunno mate..? I guess not being married gives me some time to spare.. I just enjoy doing it so much I spend (to much) time on it I guess..

 

Yes! I'm building this tomorrow! Thank you Trigger! :pilotfly:

 

Cool.. Give us pictures..! With me being on my sailing trip untill the 17th you'll be way ahead of me in your progress.. Pics Pics Pics:thumbup:

[Triggerhappy69]

Trigger et al,

 

Don't mean to hijack the thread, but I've just finished my targeting mode control panel (image attached) - not my neatest work ever, but it's done. I've had a look through the lua export and can't find state objects for those button lights! is it just me, or are they missing from the data export?

 

I'd hate to have wasted all that money on lit pushbuttons if the data export isn't available for those buttons!

 

Thanks

 

Where did you get that HUGE toggle switch with safety lock for your Flaps? Drool...!

[Alex_rcpilot]

the angle is set by the end panels mate. My plan for the panel as a whole is to first glue all sides and fronts together, ignoring the gaps and minor flaws that come from sawing. And the cover it all with a couple of layers of fibreglass to bring structural strength and gap-filling. then I'll sand all sides and fronts smooth with a belt sander, add some filler to the holes in the fibreglass, and THEN cut out the openings for the panels.

 

Couldn't wait to see you finish this part. Let's talk after you come back. lol:)

[CAT_101st]

Well looks like I have to build a set of rudder pedals now. Fricken win 7 only reconises 1 of my pedals for the rudder. Boy it is hard to fly this ting wilh 1 rudder pedle.

My curint peddles have 2 pots that work as one in XP but win 7 sees both pots as seprat axes. So BS only sees 1 pedal for the rudder. What a pain in the ars. And the western version seams a little diffrent when it comes to the joy commands. I cant seem to get the BS to trim. acts like the FFB is still on even thoe I put it to false in the cfg file.

 

Any I deas guys that can help me?

 

PS: wont be back till friday:(

[Alex_rcpilot]

Well looks like I have to build a set of rudder pedals now. Fricken win 7 only reconises 1 of my pedals for the rudder. Boy it is hard to fly this ting wilh 1 rudder pedle.

My curint peddles have 2 pots that work as one in XP but win 7 sees both pots as seprat axes. So BS only sees 1 pedal for the rudder. What a pain in the ars. And the western version seams a little diffrent when it comes to the joy commands. I cant seem to get the BS to trim. acts like the FFB is still on even thoe I put it to false in the cfg file.

 

Any I deas guys that can help me?

 

PS: wont be back till friday:(

 

Dude, that really sucks. I'm wondering what the device property sheets look like in XP and Win 7. Could you take a snapshot with each one of them?

[londo-cat]

Well looks like I have to build a set of rudder pedals now. Fricken win 7 only reconises 1 of my pedals for the rudder. Boy it is hard to fly this ting wilh 1 rudder pedle.

My curint peddles have 2 pots that work as one in XP but win 7 sees both pots as seprat axes. So BS only sees 1 pedal for the rudder. What a pain in the ars. And the western version seams a little diffrent when it comes to the joy commands. I cant seem to get the BS to trim. acts like the FFB is still on even thoe I put it to false in the cfg file.

 

Any I deas guys that can help me?

 

PS: wont be back till friday:(

Well, Windows 7 hasn't been completely released yet - and *while* you might like it, it's still a little under-cooked.

 

Things like drivers for joysticks and rudders will take a while, at *LEAST* six months for good _stable_ drivers for those kinds of peripherals.

 

I've been in I.T. for 20 years now, mucking around with PC's since 1981 - so believe me, if you are having issues with Windows 7 now, it will take a while for these things to be resolved. Talk to your manufacturer to see if they have some beta device drivers for Windows 7.

[Alex_rcpilot]

Well, Windows 7 hasn't been completely released yet - and *while* you might like it, it's still a little under-cooked.

 

Things like drivers for joysticks and rudders will take a while, at *LEAST* six months for good _stable_ drivers for those kinds of peripherals.

 

I've been in I.T. for 20 years now, mucking around with PC's since 1981 - so believe me, if you are having issues with Windows 7 now, it will take a while for these things to be resolved. Talk to your manufacturer to see if they have some beta device drivers for Windows 7.

 

hi londo, since you've been into I.T industry before I was born, I'd presume that you might have good knowledge regarding WDM and WDF. But if you're not from the R&D dept. and not interested in programing, please just ingnore what I'm about to write below. Thank you anyway:).

 

Here's the thing I don't understand - by default, DirectInput supports up to 32 buttons, 8 axisies, and 1 hat switch on each LOGICAL HID device. Any device with less than that amount of inputs can simply borrow the default driver coming with Windows.

 

The buttons, axisies and hat switch are described within USB ReportDescriptor as 'Usage' items. Each Usage is declared according to the USB HID standard.

 

That means, what used to be - for example - Axis_Z in Win XP, actually has no direct correlation with XP, but is coherent with the HID standard v1.11. Win XP sees it that way just because Win XP utilizes HID standard 1.11.

 

Then if Win 7 also implements the same standard, the same button should also appear exactly as Axis_Z in Win 7. So is it with all other inputs. That's the way it should be. But some folks here find things different, I'm curious about what's behind those issues. Is there something common with those hardware problems?

[Feuerfalke]

It depends if it really is just a driver-issue. If it is, just use the Vista-drivers. As the system-files of Win7 are almost identical to Vista, most of the drivers from Vista run perfectly under Win7, too. Only difference are those with version-checks, but you can still install these manually.

 

This may be not the problem here, though. Vista changed the way gamecontrollers are recognized and as the technology below the surface is the same in Win7, of course you have the same problems in Win7, too. Best or rather worst example is the famous BU0836. They are not recognized under 64bit-Versions of Vista and thus not running with Win7 64bit either, but can be installed with some workarounds with on Vista/Win7 manually.

[Alex_rcpilot]

Hi Feuerfalke, Since the BU0836 homepage is currently closed, I have to ask those who have this board, is BU0836 shipped with a driver or does it use the standard USB driver from the system?

 

To my understanding, when it comes to driver issues, I/O card developers have two options to with:

A - Building a card that's fully compliant with the minimum requirement according to default HID standard. This kind of devices are shipped hardware only, they're plug-n'-play, no driver is required whatsoever.

 

B - For various purposes, customized drivers are required to extend the device capabilities. These drivers are usually OS specific, and are generally to be blamed when compatibility problems arise.

 

So by this statement:

It depends if it really is just a driver-issue.

Were you hinting that all those incompatibility issues fall into the second catagory, or did I get it wrong?:music_whistling:

[Sokol1_br]

BU0836 use Windows HID drivers (A option).

 

The only software provide is for invert axis and one for select encoders.

 

Sokol1_Br

[Alex_rcpilot]

BU0836 use Windows HID drivers (A option).

 

The only software provide is for invert axis and one for select encoders.

 

Sokol1_Br

 

Thanks, that makes me wonder why it fails. I don't have any problem with my own I/O card, which has been tested with XP 32 bit and Vista 64 bit. Straight and smooth.

[Sokol1_br]

Accord I remember, L.Bodnar say in their forum that M$ change USB protocol in Vista, so old BU0836 have problem in Vista 64, the new versions of BU, with new firmware don't have problem. But since the card don't allow firmware actualization, no way for old ones.

 

Sokol1_Br

[Alex_rcpilot]

Accord I remember, L.Bodnar say in their forum that M$ change USB protocol in Vista, so old BU0836 have problem in Vista 64, the new versions of BU, with new firmware don't have problem. But since the card don't allow firmware actualization, no way for old ones.

 

Sokol1_Br

 

oops, That sounds weird to me. Like I said, the USB protocol should be independent from operating systems. Since it's a standard released by the USB organization, any operating system utilizing USB interface should comply to this standard.

 

But I may speculate. The issues with old BU boards might attribute to one or multiple causes listed below:

 

A - BU firmware not fully compliant with USB_HID1.11 standard;

B - Windows XP not fully compliant with USB_HID1.11 standard;

C - Windows Vista/7 not fully compliant with USB_HID1.11 standard;

D - USB.org has released a new USB_HID standard after Windows XP, which has been implemented in Windows Vista and later versions.

 

I don't see how D is possible, because I've just downloaded the exact HID spec and HID Usage page tables a couple of weeks ago, and it says 1.11 on them.

 

Any ideas?:music_whistling:

[Triggerhappy69]

Well looks like I have to build a set of rudder pedals now. Fricken win 7 only reconises 1 of my pedals for the rudder. Boy it is hard to fly this ting wilh 1 rudder pedle.

My curint peddles have 2 pots that work as one in XP but win 7 sees both pots as seprat axes. So BS only sees 1 pedal for the rudder. What a pain in the ars. And the western version seams a little diffrent when it comes to the joy commands. I cant seem to get the BS to trim. acts like the FFB is still on even thoe I put it to false in the cfg file.

 

Any I deas guys that can help me?

 

PS: wont be back till friday:(

 

Just a thought...

 

Isn't it possible to set the rudder axis as two half axis with "flat end" from 0 to 55% on one and another with "flat end" from 45 to 100%?

 

Something like this?

[Alex_rcpilot]

Dude! welcome back....

Ready to move on with the prj? lol.