Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing Necroware adapter with SwFFBPro #51

Closed
PinkBaron1949 opened this issue Mar 4, 2023 · 3 comments · Fixed by #54
Closed

Testing Necroware adapter with SwFFBPro #51

PinkBaron1949 opened this issue Mar 4, 2023 · 3 comments · Fixed by #54
Assignees
Labels
duplicate This issue or pull request already exists

Comments

@PinkBaron1949
Copy link

Hi folks, I hope to do this right so here is my current situation:
I now have 5 Necroware boards, 3 with micro connector, 2 with c connector and one SWFFBPro and I did a little bit of testing.
Machines used to test:
ASUS ROG Laptop with Win 10 Home 64 Bit with all updates,
Toshiba Satellite Pro Win 10 Home 32 Bit with all updates,
ASUS Desktop Win 10 Home 64 Bit with all updates.
Used software Arduino v 1.8.19
Firmware v2.1.1 (originally not for SwFFBPro)
Firmware "main" (why is this not v2.1.2 or similar)

  1. When flashing all 5 boards with the 2.1.1 firmware and connecting to every machine, the indications are consistent.
  2. When connecting, Windows accepts the boards as Arduino pro micro. X,Y Axis do not move and there is no chance to calibrate,
    so it seems the Sw is not initilized.
    Sw_Softw_v2_1_1.docx
  3. When connecting it also happens as in the following file documented.
    Sw_Softw_v2_1_1B.docx
    The X,Y axis is trembling but also reacts at inputs from the joystick, Z axis is trembling but reacts to Z rotation on the joyst., X rotation trembling but reacts to movemant of the X axis, all buttons flicker but correspond to input of the joystick buttons, hats flickers in all direction but also react to coolie hat input on the joystick.
    Now I rely on your expertise to investigate the bug. Because I have no knowledge of coding etc. I am only able to test and submit the results.
    When using the firmware from the main branch, the results are also consistent with all boards but very different.
    Sw_Softw_main.docx
    Thats all for today.
    Regards.PB
@Hedda
Copy link

Hedda commented Mar 6, 2023

@PinkBaron1949 for reference, there is another existing issue here -> #12 however that is specifically requesting/discussing support for the "Force Feedback" (haptic technology) with original Microsoft SideWinder Force Feedback Pro joystick via Necroware gameport adapter/firmware, but I believe that you are reporting issues with just basic input of the MS SideWindows FFB Pro without "Force Feedback", correct?

FYI, @NolanNicholson and @creopard reported at basic input should work with MS SideWindows FFB Pro and the Precision Pro.

@necroware
Copy link
Owner

necroware commented Mar 9, 2023

You can use the serial console in the Arduino IDE to find out, what's wrong. The serial output can be enabled by commenting the line #define NDEBUG in Utilities.h. If you are not familiar with serial monitoring, you can enable serial monitor in Tools menu of the Arduino IDE.

It would be also interesting to know, what exactly Windows is complaining about. The Precision Pro uses exactly the same packet format, only the initialization differs a little bit. You can try to comment the lines 109-113 in Sidewinder.h to make the adapter think, that FFB Pro is a Precision Pro. If this works, we have to investigate, what it doesn't like about the FFB Pro path.

@necroware
Copy link
Owner

necroware commented Mar 12, 2023

Let's continue the discussion in the duplicate issue #53

@necroware necroware self-assigned this Mar 12, 2023
@necroware necroware added the duplicate This issue or pull request already exists label Mar 12, 2023
@necroware necroware linked a pull request Mar 26, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants