I sharing the same Arduino proMicro for a SNES-to-USB and NES-to-USB daemonbyte: the arduino is connected to a male DB9 connector and my NES and SNES adaptors are connected to the arduino with a female DB9 connecting DATA1, DATA2, CLOCK, LATCH, GND and VCC properly.
The SNES controllers work perfectly both original and clonics.
The NES controllers are also detected in the PC as a 2 axes, 8 buttons controller.
My "clonic" NES controllers work perfectly (-32767 to +32767 on axes, A and B in buttons 0 and 2, SELECT and START in 6 and 7).
But my original PAL NES controllers report buttons 1, 3, 4, and 5 as pressed, making me impossible to use the controller in setups where I have also configured actions for those extra buttons.
Is it maybe because of region protection or something like that? Is it possible to fix this via software without forcing manually in the code buttons 1,3,4,5 = 0 (that would break the SNES controller setup)?
Please see screenshots attached to clarify the issue.
I sharing the same Arduino proMicro for a SNES-to-USB and NES-to-USB daemonbyte: the arduino is connected to a male DB9 connector and my NES and SNES adaptors are connected to the arduino with a female DB9 connecting DATA1, DATA2, CLOCK, LATCH, GND and VCC properly.
The SNES controllers work perfectly both original and clonics.
The NES controllers are also detected in the PC as a 2 axes, 8 buttons controller.
My "clonic" NES controllers work perfectly (-32767 to +32767 on axes, A and B in buttons 0 and 2, SELECT and START in 6 and 7).
But my original PAL NES controllers report buttons 1, 3, 4, and 5 as pressed, making me impossible to use the controller in setups where I have also configured actions for those extra buttons.
Is it maybe because of region protection or something like that? Is it possible to fix this via software without forcing manually in the code buttons 1,3,4,5 = 0 (that would break the SNES controller setup)?
Please see screenshots attached to clarify the issue.
Thanks!