#Issue with LED Output - VKB STECS Mini Plus & FSM-GA

1 messages · Page 1 of 1 (latest)

toxic storm
#

Hi, I have an issue in MobiFlight with my FSM-GA, which is connected via my STECS Mini+ Mk1.
The STECS module is listed but the FSM-GA is not; consequently it does not show under Display in the Output Config Wizard, so I am unable to make use of the LEDs.

I created my own config with the Definer Tool as per the instructions on https://github.com/MobiFlight/MobiFlight-Connector/wiki/Using-VKB-controllers-with-MobiFlight, which I then edited to account for all but one of the swappable buttons on the right throttle being replaced with five-way hats.

I am running MobiFlight 10.5.1, VKB firmware is all up to date and Virtual BUS is enabled in VKB Device Config.

Please may someone assist?

modest sparrow
#

Did you put the joystick definition file that was generated into the mobiflight joysticks folder?

toxic storm
#

I did indeed

modest sparrow
#

I'm not super familiar with the VKB stuff, but it's possible you've got a mistake in the joystick file since you made a hand edit so it isn't loading

#

you can upload it here and I can see if I notice something. You could also enable logging in settings and look in the log window after launching mobiflight, I believe it'll give an error line if there was a problem reading the file

toxic storm
#

There doesn't appear to be an error in the log.

I'll upload my definition file, thanks for taking a look.

modest sparrow
#

well we can see in the logs it loaded the file, it's there just before the warning

#

@languid linden any ideas?

toxic storm
#

I've enabled debug in the log, and it doesn't look like it has loaded this definition file. I think it might instead just be applying the definition file for the STECS Mini Plus only (without FSM-GA)?

modest sparrow
#

ohhhh do they both have the same instance name?

#

easy thing to do, just rename the joystick.json file for that other device to something else. like, stick a .old on the end or something

#

or they might have the same vid/pid

toxic storm
#

Ahh, so rename the file I want it to load to the name of the file it's actually loading?

modest sparrow
#

no, just rename the one it is loading to something else that doesn't end in .joystick.json so we stop loading it

toxic storm
#

Oh I see, I shall give that a try.

modest sparrow
#

you could even move it out of the folder

toxic storm
#

Hmmmn, this is odd. I moved all of the STECS definition files besides the one I created out of the folder, but the log still indicated it's loading the same files as before.

modest sparrow
#

are you sure you've put things in the right folder?

#

sounds like you aren't working in the mobiflight install folder

toxic storm
#

I'm in C:\Users***\AppData\Local\MobiFlight\MobiFlight Connector\Joysticks

modest sparrow
#

I bet you have other installs in %localappdata%\MobiFlight and the one you're running isn't the one in the mobiflight connector folder.

#

I have three it appears 😬

toxic storm
#

By jove, I think you might have it!

modest sparrow
#

yeah. I just gave this a try locally, and when I manually run mfconnector.exe from the MobiFlight Connector folder it correctly skipped the joysticks I moved out of the folder

toxic storm
#

Yes, that's solved it, thank you!

modest sparrow
#

nice. my guess is the vid/pid are the same for the two devices so first loaded config with that vid/pid will win

toxic storm
modest sparrow
#

beautiful!!!

toxic storm
#

Yes, they are the same in both configs - "VendorId": "0x231D", "ProductId": "0x012C"

#

Thank you! Very much appreciated.

modest sparrow
#

glad we got it sorted out! I learned something today