Anton5

About a year back, I bought the PCB's and components to make two of Dr. Scott Baker's PS2 to 5200 controller adaptors for using both PS2 analog sticks on Space Dungeon and Robotron 2084. Being wowed by the experience of playing these games with the PS2 Dual Shock controller, I took little time to check out full functionality. My friend who I made the second adaptor for just recently noticed that none of the number pad buttons register inputs in either game on his two port 5200 console. I then tried it on my own two port console, and sure enough, none of the number buttons, * or # buttons, register inputs to these games. I have tested both adaptor assemblies with my multimeter and register continuity on all twelve number pad buttons when they are depressed, so the components are, in fact, good. Has anyone seen similar behavior from their SM Baker controller adaptor, or have any idea about what is possibly causing this issue?

Yes. Already used Zadig and installed the USBasp programmer using libusk driver. Windows 10 recognizes the device and says it is operating correctly.

I purchased Scott Baker's PS2 Dual Shock to 5200 adaptor PCB recently along with the complete list of electronic components from his website. After soldering it all together nicely, the real headache has been in not being able to properly program the IC from my PC via USBasp and AVRDudess app. I do everything as should be, including loading Scott Baker's fuse settings first, but ultimately end up with a range of error messages returned in AVRDudess, from saying it cannot locate the IC to something about an incorrect address being returned. Does anyone have any good suggestions that might help?

Was the core reason for the blurry distorted Activision text seen in posts #4 and #9 ever figured out? I have the same on a recent A/V mod done to my 4-switch woody.