I'm looking for pictures of the internals for the NES turbo blaster, schematics would be better: From what I gather it should de-multiplex the signal to look for the a/b inputs;in turn that drives a variable timer, then it puts it back in the original shift-register format that the nes can read. Anyone have any comments on this? I would love to build one that accepts a snes input, leaving the Y/B alone(as the b/a buttons respectfully) with the X/A/R/L buttons be variable turbo. Basically the ultimate nes controller.
Surely it'd be easier to just modify the control pad so that when a button is pressed, you're allowing current from a 555 timer to pass through and that goes into the encoding chip inside the control pad? Much easier to do it that way than decode the signal, check it and re-encode it, I've got some dodgy 3rd party SNES pad around here somewhere that does that.
this works great except some games only allow so many bullets in the air at a time. so to have a way to adjust the turbo speed , to a fine tune the turbo; like the nes advantage, but without having bulky pots on the orignal nes controller would be amazing. Also having dedicated turbo buttons is awesome.
You've got the idea, deserialize, mix with oscillator, reserialize. You could either implement it in logic with a state machine or in code with a microcontroller. For each button you want turbo'd you would OR the original button with the oscillator/software timer. Clearly the logic/oscillator route is more hardcore, but for controller applications microcontrollers are more than adequate and will save you a bunch of parts, plus you can easily add in programmability so you don't need to get up at all to change the configuration.
