Jump to content
The simFlight Network Forums
Sign in to follow this  
gippslandblanik1

Leo Bodnar board not seen by FSUIPC

Recommended Posts

After installing the Bodnar circuit board in my Saitek Yoke system to eliminate the significant dead zone in the X and Y axis the FSXSE  control settings see the new Bodnar board signals ( which has eliminated the dead zone!!! ) but FSUIPC does not see the new Bodnar X or Y axis. I followed Pete Dowson's suggestion re JoyIDs - " Fixing joystick connections not seen by FSUIPC",  but it didn't fix the problem. Counting the BU0836A Bodnar interface I have a total of 6 controllers for my FSXSE flight sim.  Thank you in advance for any help. Max

Share this post


Link to post
Share on other sites

YOU POSTED THIS TO A REFERENCE SUBFORUM CLEARLY MARKED, IN RED Not for support requests
Please do look at where you are posting. You are lucky I saw this and moved it to the correct Support Forum!

8 hours ago, gippslandblanik1 said:

After installing the Bodnar circuit board in my Saitek Yoke system to eliminate the significant dead zone in the X and Y axis the FSXSE  control settings see the new Bodnar board signals ( which has eliminated the dead zone!!! ) but FSUIPC does not see the new Bodnar X or Y axis.

I use many Bodnar boards with no difficulty, so it must be a configuration issue. Did you check that it is seen by Windows, and have you calibrated the axes in Windows first?

I can't help without some information. Please show me the following files, all provided in your FS Modules folder:

FSUIPC4.INI
FSUIPC4.log
FSUIPC4 JoyScan.csv

Pete

 

Share this post


Link to post
Share on other sites

FSUIPC4 (2).zipFSUIPC4.logFSUIPC4.JoyScan.csv   Hi Pete, Thanks for the quick response. My apologies for the posting error but my general lack of PC skills and the fact I am red/green color blind came into play. I started flying back in 1968 but now do most of my flying on the sim and your FSUIPC add on (registered) has been a fantastic upgrade in realism and immersion - thank you very much. In answer to your questions - the BU0836A Interface does show up in my Windows 7 Devices and Printers and I did calibrate the bodnar board in FSXSE. Also the yoke/bodnar outputs are working normally in the FS with those axis selected in the default FSX control settings.  I only have one set of MFG rudder pedals connected but I notice there appears to be 2 shown in the FSUIPC.ini file JoyNames?  Best wishes, Max 

Share this post


Link to post
Share on other sites
2 hours ago, gippslandblanik1 said:

I only have one set of MFG rudder pedals connected but I notice there appears to be 2 shown in the FSUIPC.ini file JoyNames? 

The Bodnar board is recognise, with and X and Y axis connected:

      812 Product= BU0836A Interface
      812    Manufacturer= Leo Bodnar
      812    Serial Number= BY0C28
      812    Vendor=16C0, Product=05BA (Version 1.38)
      812    GUIDs returned for product: VID_16C0&PID_05BA:
      812       GUID= {41C9B2E0-C1F4-11EA-8001-444553540000}
      812       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X4095,Y4095,Z0

It is assigned ID 6:

      843 Device acquired for use:
      843    Joystick ID = 6 (Registry okay)
      843    6=BU0836 Interface
      843    6.GUID={39B97A80-9FC5-11E7-8001-444553540000}


And there are no conflicts on this ID, so it must surely work ok.

There are other problems though. There two have the same ID (0) assigned:

      827 Device acquired for use:
      827    Joystick ID = 0 (Registry okay)
      827    0=T.16000M
      827    0.GUID={58FEFF80-FAE9-11E7-8002-444553540000}

      843 Device acquired for use:
      843    Joystick ID = 0 (Registry okay)
      843    0=MFG Crosswind V2
      843    0.GUID={58FEFF80-FAE9-11E7-8002-444553540000}

and so do these two (ID 3)

      843 Device acquired for use:
      843    Joystick ID = 3 (Registry fixed)
      843    3=Flight Yoke System
      843    3.GUID={A969C360-7F30-11EA-8001-444553540000}

      843 Device acquired for use:
      843    Joystick ID = 3 (Registry okay)
      843    3=MFG Crosswind V2
      843    3.GUID={A969C360-7F30-11EA-8001-444553540000}


You say you used JoyIDs to sort things out. What exactly did you do in JoyIDs?

Of your "two" Crosswinds I'd guess that, from the assignments you have, historically ID 3 is the correct one, though that does give the worst results in the Joyscan. I've no idea how the registry got into such a mess with that device. I suggest that you find its entry in the Windows device manager and uninstall it there, along with any driver software it says is installed, then unplug the device and reboot the PC. Then plug the device in and see if the registry entries have sorted themselves out.

But the Bodnar board should certainly be recognised as device 6 with an X and Y axes. This shows definitely okay.

BTW you are using FSUIPC 4.974, which is out of date. Please update to 4.975a.

Pete

 


 

Share this post


Link to post
Share on other sites

Hi Pete, I followed all your suggestions and now all is fixed - eliminated the second Crosswind/FSUIPC now see's Bodnar/updated to 4.975a. Thank you very much for taking the time to help, I really appreciate it. Best wishes, Max

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.