Hi,

I'm trying out your demo of Axis and Ohs with the Knobster Bridge software.  Axis and Ohs Demo version 2.81 b05, Bridge Version 1.00 b07.  I'm running the latest Beta version of MSFS, Version 1.31.20.0.

I start both Axis programs as Adminstrator, then start MSFS, and connect.  First, to test the software, I set up a button assignment using a keyboard key to invoke AP_HDG_Hold Toggle.  I ran this in the sim, and it works just great, toggling Autopilot Heading Hold On and then off.

Next step in testing:  verified that the Green light was on in the Knobster Bridge UI, showing that it was recognized.  Changed the button assignment to the Knobster device, using the push button as the trigger.  Saved the assignment.  Pushed the Knobster button and the Garmin G1000 showed HDG mode in the annunciator.  All good so far, but that's where the good news stopped.  Subsequent presses of the button simply do not register.  Nothing changes. 

If I exit out of Axis and Ohs, and fire them both up again, the first press of the Knobster button works, but nothing after that. I tried changing the action from button push to button release, but it did not help.

Could you help?  I would really like this to work, and then purchase your software.  I want to set up scripts using voice recognition for VR, but also for monitor simming. 

Thanks very much,

Bill

 

 

2 hours ago, mastb said:

Could you help?

The bridge will only work with those Knobsters that support the API that the manufacturer provides - so most likely the more recent ones and also most likely no clones. That being said - I don't even have a Knobster. The Bridge is a hobby project (like all assets on the downloads page are), made "in the blind" for a fellow simmer. I know that a few people have been using it successfully, but I haven't heard about this specific piece of hardware in a long time.

2 hours ago, mastb said:

Subsequent presses of the button simply do not register.  Nothing changes. 

Do you mean that nothing happens in the sim or is the button press itself not being received (for example when you try to assign it again in a new config)?

When nothing happens in the sim but the button technically works, then you probably aren't using the correct method to operate the control in the sim. That is not as clear-cut as it may seem, this is potentially different for every aircraft (so it is important to know what aircraft is being used here and what instrument (default, modded, addon...)

Edited March 3, 20233 yr by Lorby_SI

2 hours ago, mastb said:

I would really like this to work, and then purchase your software. 

When it doesn'*t want to work, please don't purchase it. There is no difference between the DEMO and the retail version, they are identical. 

 

Hi, Lorby,

Thanks for the replies.  Essentially, every button push of the Knobster AFTER the first push was not registering.

I was able to get it to work by reading an older thread you had with another user where you mentioned the "Force Key Up Event" on the Bridge screen.  Checking that box fixed the problem.

I was in the C172 with G1000.  I purchased my Knobster about two weeks ago.

Thanks for the help!  Now I'm going to try your voice interface!

Bill

 

11 hours ago, mastb said:

"Force Key Up Event"

Right. Sorry, I forgot about that one. I think that some Knobsters are only sending the Key Down event, but not the Key Up. So your button was constantly pressed and never released as far as AAO was concerned.

Hi, Oliver,

I would like to use my single Knobster to operate different dual encoders (and single knobs, like the Heading knob) in MSFS in VR.  I am using voice recognition to issue commands like "Focus Heading" and "Focus Altitude".  These commands set a local variable to a certain numeric value, and I would like to write a script(s) to analyze the variable, and simply set the Knobsters left and right turns of both inner and outer knobs as well as the push click for different MSFS controls, based on the value of the variable.

I have successfully written two sample voice scripts to set the local variable to 1 for Heading and 2 for Altitude.

When using a button assignment to do one of these tasks, my Knobster Device shows as "WebApi: 772 # [-772]".  In the Assigned button/key field, turning one of the two knobs left (I forget which one right now), shows "CHN: 0 EVT: 12 TURN_LEFT". 

Based on a users recommendation on MSFS forums, I think I need to write one or more scripts for Incrementing and Decrementing, examining the variable set by voice. How do I assign this Device ID and Button event to, say, AP_ALT_VAR_DEC_in a script with the capability to set both 100 and 1000 feet decrements?

I've read your documentation and researched on Google, Youtube, and flightsim.to sample scripts.  I'm getting there!

Thanks for your superb software and all of your help.

Bill

Edited March 8, 20233 yr by mastb
modify text

I think that you have that backwards, at least that is how I read it.

- You need several voice scripts to set your local variable, that is correct (albeit not entirely, this can be done without scripts too, but don't concern yourself with that just yet)

- Then you need (only) two additional scripts that handle INC and DEC respectively. In these scripts you read your LVar and then trigger ALT_INC, HDG_INC, SPD_INC etc. according to its value. Be mindful that these AP commands are potentially different for every aircraft, especially addons. So you need these two scripts for every AP variant that your planes use.
The INC script would look something like this:

(L:mylvar) 0 == if{ ...alt inc...} 
(L:mylvar) 1 == if{ ...hdg inc...} 
(L:mylvar) 2 == if{ ...spd inc...} 
(L:mylvar) 3 == if{ ...vs inc...} 
(L:mylvar) 4 == if{ ...whatever inc...} 

- These two scripts you assign to the left and right turns of the Knobster. So when you turn it, either the INC or the DEC script gets called and it will act according to your Lvar. Also, in this context the LVar should NOT have a unit. (L:MyVar) , not (L:MyVar, Number). Without the Unit AAO will treat the LVar as "internal" and won't bother the simulator with it.

 

Edited March 8, 20233 yr by Lorby_SI

Thanks, that last paragraph was the key for me!

Ok, bought the software.  Things are coming together.  Quick question:

why does this work in the script

(L:myInput)·2·==·if{2·HEADING_BUG_INC}

and this does not (red light turns on in script editing)

(L:myInput)·1·==·if{1·HEADING_BUG_INC}
 

Using the number 1 seems to cause an error?

 

Thanks,

Bill

 

46 minutes ago, mastb said:

Ok, bought the software.  Things are coming together.  Quick question:

why does this work in the script

(L:myInput)·2·==·if{2·HEADING_BUG_INC}

and this does not (red light turns on in script editing)

(L:myInput)·1·==·if{1·HEADING_BUG_INC}
 

Using the number 1 seems to cause an error?

 

Thanks,

Bill

 

Both scripts are wrong. Spaces are set incorrectly, and the call to the K: event is incomplete. This is what a script like that is supposed to look like:

(L:myInput)·1·==·if{·1·(>K:HEADING_BUG_INC)·}

Please take a look at proper RPN syntax. This cannot be done using "trial & error", that only leads to deep frustration.

There is a chapter about Scripting in the AAO manual, including examples and lists of operators and commands. Further basic information can be found here: Reverse Polish Notation (flightsimulator.com)

1. Space characters are extremely important. Get those wrong and your script will not work. That is why the editor is highlighting them for you
2. All commands and variable names are case sensitive
3. The script must follow at least MSFS RPN basic guidelines.

Edited March 8, 20233 yr by Lorby_SI

Yeah, I screwed up there, for sure.  Thanks.

Oliver,

Just wanted to let you know that I have successfully programmed the Knobster to do everything I wanted via voice commands while in VR (or 2D, for that matter).  Mainly focused for now on the G1000 autopilot.  I can now control altitude, vertical speed, heading, COM1, Nav1, and all of the autopilot modes like Heading, Nav, FLC, VS, Alt, etc.  Your software works perfectly.

Thanks for all of your help, I know it wasn't easy at first <g>.

Is there a way for me to "buy you a coffee?

Regards,

Bill