Hi,

I downloaded the knobster plugin to connect my knobster to AAO. When starting up the bridge, Knobster #0 is immediately recognized, channel A selected, but the light doesn't turn green? In AAO itself, I checked the WebAPI window and the bridge entry is shown as red. I glanced over the documentation but couldn't find anything about the knobster bridge.

The knobster is an authentic siminnovations part. Am I missing something in the installation?

2 hours ago, mattbaker said:

I checked the WebAPI window and the bridge entry is shown as red

Then the WebAPI port that has been set in the Bridge program is different from what it needs to be to communicate with AAO (valid port numbers are at the top) and must be changed

1. Close the WebAPI dialog
2. Close the Bridge program
3. Reopen the WebAPI dialog
4. Clear all checkboxes, then set one checkmark next to the red entry
5. Press "Set primary port" at the bottom of the dialog.
6. Press "Apply"

 

Hi and thank you, indeed the entry in AAO Web API Dialogue is now not red anymore. However, in the Knobster bridge software, the light still won't turn green. It says Knobster #0 Channel A, but the green light is off. Something wrong with the connection? When I only use air manager, the knobster works fine.

22 minutes ago, mattbaker said:

Hi and thank you, indeed the entry in AAO Web API Dialogue is now not red anymore. However, in the Knobster bridge software, the light still won't turn green. It says Knobster #0 Channel A, but the green light is off. Something wrong with the connection? When I only use air manager, the knobster works fine.

I would say that not the Knobster is the problem, but the Bridge program can't connect to the AAO WebAPI.

AAO must be started with the "Run as administrator" option. The two green LEDs on the bottom right indicate if the WebAPI is active or not. There also is a PDF troubleshooting guide concerning the WebAPI on the download page. 

Ah, when I changed the WebAPI port, i didn't have the sim running, therefore the light wasn't turning green. I now launched the sim and the webapi is connected.

I'm trying to set the rotary knob and click button to some functions, however something peculiar is happening. It seems that the first time I turn the knob or push the button, AAO registers a click (CHN: 0 EVT: 1 CLICK), and then the second time a turn (CHN: 0 EVT: 1 TURN_RIGHT). For the rotarys it differentiates on the second turn by right and left, but even pushing the button first triggers "click", then the second time "turn_right". In the SIM, this translates to having to push the button twice before the action is executed. Can I circumvent this?

4 hours ago, mattbaker said:

Can I circumvent this?

Don't press the button again when assigning things. Keep it on CLICK.

For assigning the button, in principle, that makes sense, however in that case, only the first press of the button will perform the assigned function in the simulator. After that, pressing the button doesn't work anymore because the button is now recognized as TURN_RIGHT/LEFT.

I worked around the problem by duplicating all my assignments and assigning the first press (CLICK) and second press (TURN_RIGHT/LEFT) to the same action. Just wondering if there is a more clever solution that I missed?

1 minute ago, mattbaker said:

After that, pressing the button doesn't work anymore because the button is now recognized as TURN_RIGHT/LEFT.

That doesn't sound right, that shouldn't be the case. On the assignment dialog that can happen, but in actual operation it shouldn't matter.

Ther real problem is, that I actually never had a Knobster. The bridge has been programmed "blind" for a friend a long while ago, and I am actually not sure about anything here.

I will take a look at the bridges' code, see if I can find anything obvious. What AAO version are you using, is it the latest one (4.52)?

21 minutes ago, mattbaker said:

For assigning the button, in principle, that makes sense, however in that case, only the first press of the button will perform the assigned function in the simulator. After that, pressing the button doesn't work anymore because the button is now recognized as TURN_RIGHT/LEFT.

I worked around the problem by duplicating all my assignments and assigning the first press (CLICK) and second press (TURN_RIGHT/LEFT) to the same action. Just wondering if there is a more clever solution that I missed?

OK, one thing I do see in the code: in the Knobster Bridge program, there is a setting called "Force <key up> event". If I remember correctly, there are some Knobster builds that don't send an event when the button is released. That would explain what you are seeing. Please change that setting and try again.

Edited April 29, 20251 yr by Lorby_SI