Provided the controller pcbs (hacked pads, whatever) you are connecting to the Decoder outputs all use the same logic levels (+3V or +5V) and are common ground, thereās no reason why you canāt.
-ud
If the rules Iāve laid out are followed, yep. Though, I doubt thatās what he actually wants to do. More likely he wants to have the pads all wired together to have the ability to connect to a variety of consoles, but not necessarily all consoles running at the same time.
-ud
Youād still want to be careful though, because if you are controlling, say, a 360 PCB and an XB1 PCBā¦ each connected to their respective system at the same time controlled by 1 UD-USB. Youād be uniformly attaching the 5v rail and GND between the two systemsā USB.
While those interfaces are generally protected, it doesnāt mean some weird stuff couldnāt occur.
edit:
Agreed though, I donāt think this is what he wants to do, moreover just have the ability to connect to a variety.
For some reason, the UD-USB led doesnāt go green. Actually, it doesnāt output any color at all (so following the manual I cannot really understand whatās going on).
Note that the voltage works perfectly (5V clean), and it also arrives to the Tankstick.
Have you tested the setup with a usb device known to recognized by the decoder, such as a dual shock 3 or wired xbox 360 controller? It could just be that the decoder does not recognized that ps3 adapter you are using.
Iāve actually had a few people express problems using the Decoders on a MAK-Strike. The first couple cases had other extraneous issues going on, so I couldnāt 100% link it to the MAK-Strike, but just recently I had another person contact me and itās clear that there is something āspecialā about the MAK-Strike. Decoder works fine when user just powers it (not connected to MAK-Strike), but then behaves funny when the outputs are connected to MAK-Strike (like messing up the Decoderās ability to function properly, not just a button mapping issue).
I should have a MAK-Strike in-hand in the next few days for some testing. Just sit tight for the moment and Iāll post up when I figure out whatās going on.
-ud
Actually, Iām surprised about this because, according to the MAK-Strike DB15 layout, there is only a swap of connectors 2 and 10 (K3 and K2 according to the UD-USB manual). Everything else is the same.
Anyway, I hope you can figure out this problem finally making your beautiful decoder compatible with an important supergun such as the MAK-Strike.
No news on the MAK Strike yet. After messing with it for an evening, Iāve pretty much been in EVO prep mode. Have to hit it when I get back next week. Only thing strange about the MAK Strike Iāve noticed is that the power switch is not inline with the controller ports (controller ports are powered all the time, regardless of power switch). Not sure what the reasoning behind that design is, but I donāt know why that would matter to the decoders either. Iāve got an idea to test when I get back.
-ud
Sorry, when I first read your post, for some reason I thought you were trying to help one of the other guys? I was confused because I didnāt understand what your photo had to do with anything!
Ok. Exactly which controller are you plugging into it? have you tried just wiring up 5V and Ground to the appropriate screw terminals and plugging in your controller (with the decoder powered of course)? Do you know for certain you are powering it with 5V (checked with a multimeter/voltmeter)? What do you mean by āno ding that its recognizedā? Do you mean you connected it to a PC via USB for firmware update? If so, it wonāt be recognized by a PC unless in firmware update mode (see the 6-button manual for details on that: http://udgametech.blogspot.com/p/firmware.html).
-ud