Can someone confirm that the controller board at https://github.com/MiSTer-devel/Retro-C ... rollersUSB will support this controller and all of its buttons?
It looks like the board supports 4 controllers at once and I suppose that for a single controller the data line of the NDK10 goes to DATA1 of the board. Is this correct?
Thanks
SNES NDK10 controller
-
- Posts: 257
- Joined: Sun May 24, 2020 9:06 pm
- Has thanked: 64 times
- Been thanked: 13 times
Re: SNES NDK10 controller
You will likely get the first 12 buttons (normal SNES buttons) but none of the others will work.
These pads need the host to allow 16 extra clock cycles to read in the other buttons. It's probably not too difficult to do.
If you have the means to test I'd be happy to have a go at adding support.
These pads need the host to allow 16 extra clock cycles to read in the other buttons. It's probably not too difficult to do.
If you have the means to test I'd be happy to have a go at adding support.
-
- Top Contributor
- Posts: 1911
- Joined: Wed May 27, 2020 1:59 pm
- Has thanked: 145 times
- Been thanked: 454 times
Re: SNES NDK10 controller
Thanks,
It will take a while before I get it: Spain -> Netherlands -> Curacao plus 1 week before it clears customs.
I am ordering the arduinos and will have a look at the code. I found a timing diagram on raphnet.net: it clocks in the first 12 buttons, after that there are 4 clocks cycles which are used to see if it is the end or if more data is available in which case the remaining buttons are clocked in. It should not be very difficult to modify the existing code. Thanks for the help and I will post when I have everything in my hands.
It will take a while before I get it: Spain -> Netherlands -> Curacao plus 1 week before it clears customs.
I am ordering the arduinos and will have a look at the code. I found a timing diagram on raphnet.net: it clocks in the first 12 buttons, after that there are 4 clocks cycles which are used to see if it is the end or if more data is available in which case the remaining buttons are clocked in. It should not be very difficult to modify the existing code. Thanks for the help and I will post when I have everything in my hands.
-
- Posts: 257
- Joined: Sun May 24, 2020 9:06 pm
- Has thanked: 64 times
- Been thanked: 13 times
-
- Top Contributor
- Posts: 1911
- Joined: Wed May 27, 2020 1:59 pm
- Has thanked: 145 times
- Been thanked: 454 times
Re: SNES NDK10 controller
While awaiting for my stuff to arrive I had a look at the code and there is detection of the NTT controller. I will have a more detailed look at the code to see how it works just by curiosity. The software can handle 4 controllers but due some USB HID issue it is limited to 2 controllers which is not a problem as it is for only one controller in my case. I think I will change GAMEPAD_COUNT to 1 although I do not think it is necessary: it won't change the timing as the sampling of the 4 controllers is done within the same clock cycle, it will reduce the memory footprint but who cares. It may affect the USB communication as it will show up as 1 controller instead of 2 but as I know nothing about USB programming and communication it may not matter.
I also have 2 questions regarding the programming of the chip: the pro micro has been developed by Sparkfun and is not an official Arduino.
It appear that Arduino Leonardo has to be used for the board type.
It also appear that it need Windows drivers to be installed which I found on the Sparkfun web site.
Is this correct?
Another question:
Why are Up, Down, Left and Right treated differently from other button? On this controller this is done in software but for the other controllers developed by DaemonBite these buttons have to be connected to specific pins unlike the other buttons.
I also have 2 questions regarding the programming of the chip: the pro micro has been developed by Sparkfun and is not an official Arduino.
It appear that Arduino Leonardo has to be used for the board type.
It also appear that it need Windows drivers to be installed which I found on the Sparkfun web site.
Is this correct?
Another question:
Why are Up, Down, Left and Right treated differently from other button? On this controller this is done in software but for the other controllers developed by DaemonBite these buttons have to be connected to specific pins unlike the other buttons.