Thanks! Perhaps typing it out led to a moment of clarity, I eventually figured it out last night! It was after I found a tutorial video on CH Control Manager that had a quick comment about unchecking DX and assigning a specific key. I had been trying to edit the key file in hopes that I could maintain the shift functionality of that button, but not a big deal. PTT works now so that’s good enough!

Pager

OK, forgot about this thread, but it turns out cleaning didn’t fix anything (the problem came back after a while), because it wasn’t the pot. It was the cable. However, it seems it was worn out in some weird way, inside the throttle, probably from stress from being flexed back and forth when the handle was being moved. I have not yet found the fault in the cable itself, but the jury-rigged replacement had cleared it.

It sure seemed like it was the pot, because the fault appeared, for most part, in the same place along the throttle range (presumably, the cable was being bent into shape that caused a momentary loss of contact). However, after a few assembly-disassembly sequences, that spot started popping up in different places along the range, likely from the faulty cable behind shifted around. This took me a long time to track down, but I got it. I’ve had it on the temporary cable for a while, the original one should not be difficult to fix, though. Just posting it there, in case anyone has the same problem.

Sorry, my posted script has the “cms.b2=js1.b1” because I assigned b2 to keystroke " \ " which is 1st detent (shoot laser) which I notice was not in your script.

When I tried your script verbatim (without my added cms.b2=js1.b1) the guns could not shoot, but the laser worked perfectly.

After many attempts, I found a solution!
I programmed a simple:

cms.b2=js1.b1;
cms.b3=js1.b1; which was what I tried originally (making both 1st detent and 2nd detent to be operated by the push of the trigger).
But,
after much playing about, I found that for the laser to stop shooting, the last keystroke it must sense is 1st detent released.
I realised that since I programmed CMS.B2 to " \ " 1st detent and CMS.B3 to " / " 2nd detent, when I checked in the Key Check of CH Ctrl Mgr, on pressing and releasing the trigger it showed:
Pressed:
Pressed: /
Released :
Released: /

That means what it sensed last is " / " 2nd detent release.
Reason being is on a single press of trigger it will ‘press’ CMS.B2 " \ " 1st detent first, then ’ press’ CMS.B3 " / " 2nd detent. Same sequence on release.

So I just swapped the keystroke for CMS.B2 to " / " 2nd detent and CMS.B3 to " \ " 1st detent.
That way, the last keystroke sensed is 1st detent release.
Problem solved!

Thank you very much for your help ewildcat.
Really admire your scripting knowledge.
Reminds me a bit about programming on GWBasic & BasicA back in the old DOS days…

@Tazz:

I assume you mean this schema?

http://www.realsimulator.com/assets/images/Schema_RandB_440.jpg

I’ll have a look today and see if I can find any resistance on pin 13 and 14.

Yep, that’s it, pins 4 and ~ been a while since…

thanks for the help everyone….i’am flying again…cap45

Does anyone know any place where I could get a CH Throttle pot with cheap shipping to central Europe? I just need one pot, and have a tight budget, so 30$ shipping for a 4$ part puts me off the store in the OP. 22 euros (plus unknown shipping costs) is also a bit too much.

Of course, the thing had to start acting up just as BMS devs fixed the tankers…

Sooooo… program it as you like? This isn’t written in stone, it’s a game, enjoy it!

Cool, it’s great to have options when stuff stops working

As you’ve posted in the CH subforum I’ll assume that’s what you’ve got.

In your \Falcon BMS 4.34\Docs\01 Input Devices\03 HOTAS Setup\CH FS&PT folder you will see all the files for setting up a CH setup, including keyfiles with/without MFDs, layout and a text-based Quick Setup Guide.

The BMS Device Setup Guide is in the 03 HOTAS Setup folder one level up and Chapter 3.6 on page 54 goes through this CH setup in more detail with screenshots.

Hopefully that’s what you need. If not, please give us a bit more information to go on.

I’ve managed to break a CH Pro Throttle and Ruder pedals over the years (since I started flying BMS really…) but my Fighterstick is still hanging in there. I don’t use it much as I find the throw force to be far too light, making the stick too “fast” to be even close to realistic.

The Warthog stick and Cougar TQS are my favorite setup, with a set of Saitek Combat Pro pedals…which unfortunately, you can’t get anymore…

Hello,
Watch this BurnerTactical video on your YouTube channel.
Maybe you can solve your problem !!!
Link:
Good Flights !!!

I was kinda hoping its that easy,will give it a try.Tks Eagle-Eye.

Cheers

Use the .map file that is in ch folder with device manager .then use the excel of the key file editor and import the full keystrokes from the bms and then change what ever you want ,export the file and save the excel if you want .thats it

this video has English subtitles if you know the number of your devices then you need the second part of the video , watch the 2 parts and you will not have any problem ,don’t forget to use the .map file and then configure the buttons as you like

You can use the key file editor; it is in no means limited to only the packaged control options.

Use the Generic Primary and simply bind DX buttons to callbacks.

+1. VP is THE place for pit builders.

@danster:

Thanks Malpaso. The video was interesting, especially the piece about making the files read only- once all is working. Same advice that Flow32 kindly gave.

i think my problem is solved. Went into CH Manager and simply gave the offending button a different random number. It now responds in BMS GUI although there was apparently no conflict before. And they say computers are logical….

So I’ve now made the relevant files read only.:D

Very cool that you have been able to solve, danster.
My joystick is X52 PRO, but I’m going to buy a Fighterstick and a Pro CH Throttle.
Now just enjoy the BMS !!!
Good luck !!!
Good flight !!! :plane:

malpaso

Thanks yet again! I’ll tackle it. And any idea why I can’t now use some keyboard keys ( for infrequent commands), like P and G, which don’t respond, but do work if allocated on my Hotas?

Got it! Loaded up the CH control software, followed the instructions in the docs folder and got it up and running.

@Blu3wolf:

How about taking it further: the poetry of one’s words reveals the path they have walked

how about 1 little mods: “thy poetry of one’s words reveals thy path they have walked”

Thanks Blu3wolf. You have no idea how much my eyes have been bleeding reading manuals and trolling this site and others in my quest for answers.