Anybody ever tried enabling normal mode and one of the turbos at the same time?

[Chuplayer]

I was having issues with the I button being unresponsive at times with what appeared to be all of my controllers. I swapped the controller port from my Duo-R with the fifth port on my multitap. It's a tighter fit, but it didn't help.

I had thought I ruled out the controllers as being at fault, but after fiddling with the turbo switch on one controller, I began suspecting the circuit wasn't closing when in normal mode. I found that when no state is selected, the button does not respond at all.

To try fixing this, I cut some soldermask off of the two appropriate traces and jumpered them with some wire. Since then, the button has been properly responsive. However, while doing this fix, I removed the switch entirely. Therefore, turbo isn't operable on the I button.

The fix I did wouldn't block the switch from moving if I put it back in. I was just wondering what would end up happening if more than one state was enabled at one time. Remember, the normal state is hardwired.

Do things go haywire? Does any damage result?

Just a little background information. I am using this fix on a Blaster controller. However, I believe I experienced this problem on a normal PC Engine two button turbo-equipped controller. I know I experienced this on at least one of my other Blasters, and maybe it happened on my third Blaster, too. It's still possible that it's a problem with the console, but I'm fairly convinced that it was the controller or controllers at this point. I may have been mistaken with the other controllers, and this fixed one is really performing well.

Also, based on information from GameSX and Deathskull Labs, I imagine the I button might not be the only button to fail if it was a problem with the console. Up would also fail, and I've had no problem with up. I guess if pin 2 only has problems when low, it could be the console, but I'm not convinced that's what's going on.

http://www.gamesx.com/controldata/turbocont.htm
http://web.archive.org/web/20041118024643/http://users.erols.com/tiltonj/games/tech/tg16cont.html

[Chuplayer]

I played a bunch of Ys IV today, and I've had no more problems with my I button. In addition, I plugged in my original PCE pad, and it still had the I button problem. I fiddled with and pressed on the turbo switch a little bit, and it immediately responded to being touched. I button action improved so much. I wonder why it's seemingly always the I button. Are turbo switches on the I button always this bad? Even among multiple types of controllers? Or am I just bad luck?

If nobody knows what enabling multiple modes at one time does, I might try it next weekend. I hope turbo low or turbo high would take priority over no turbo.

Maybe I'll see what I can do to improve turbo switch functionality. I'd like to keep it as stock as possible. The funny thing is, two of my Blasters are new old stock. Well, maybe that's what they are. Old. They might need some contact cleaner regardless.

[ProfessorProfessorson]

Extend/bend the metal prongs on the slide switches back out some and lightly sand, then clean their connection ends. It will improve contact to ensure the buttons keep working.

[Chuplayer]

I've given thought to that. All in due time.

I also gave more thought to the being able to enable two levels at once, and it probably won't work. It hit me in the shower this morning, believe it or not. The non-oscillating one is going to be fed no matter what. Oh well.