What's new
2) USB2DB15 doesn't seem to work unfortunately. It's known to work on previous HAS versions and it works on my Minigun without too much of an issue, but according to the built in button tester, plugging the USB2DB15 results in all buttons being pressed at once. Not sure why, and I've updated it to the latest firmware just to make sure. I notified Raph_Friend on their Discord, but unfortunately they don't have one of the newer ones on hand to test it with, and I'm not sure if this is an isolated issue or not.
Is this the case with every controller you tried through the USB2DB15 on the HAS 5.0 or just with the 8BitDo controller? I saw your message on the USB2DB15 Discord but it wasn't clear to me if you meant that it wasn't working properly in general, or just with the 8BitDo. They say that the 8BitDo compatibility problems with the USB2DB15 are a known issue.
 
Just received my HAS 5.0 a little bit ago and I've been running it through some tests for video output! Looks great going through the Retrotink 5X with fairly minimal work other than messing around with the sync a bit on the scaler. There was a couple things I noted about it.

1) Atomiswave requires you to turn Coin chute emulation on before it completely starts up, otherwise you get coin slot error and a loop.

2) USB2DB15 doesn't seem to work unfortunately. It's known to work on previous HAS versions and it works on my Minigun without too much of an issue, but according to the built in button tester, plugging the USB2DB15 results in all buttons being pressed at once. Not sure why, and I've updated it to the latest firmware just to make sure. I notified Raph_Friend on their Discord, but unfortunately they don't have one of the newer ones on hand to test it with, and I'm not sure if this is an isolated issue or not.

1. Have you tried to run the Atomiswave without the USB2DB15? This system was tested with the HAS and confirmed to work just fine.
2. The button test mode is basically for that, it shows what happens at the input side, so if it shows all buttons pressed, then the USB2DB15 must pull them down for some reason. There couldn't be an incompatibility with a specific controller or adapter on the HAS side, because the DB15 port uses discrete inputs, it just expects 'nothing' or ground for button inputs, it doesn't use any specific communication protocol like the SPI or so.
 
Last edited:
Ah, sure enough. That issue with the USB2DB15 causing all buttons to fire at once is what caused the coin error with the Atomiswave.
 
  • Like
Reactions: RGB
Recieved mine earlier week, it came super hyper fast!(shipped saturday, arrived monday 8sharp at the door in france) looks ridiculous on the Retrotink 4K (lg c9, game mode, VRR FrameGen, min lag etc)

I didn't look too much at the new settings before recieving/buying the 5.0 HAS asaide from naming...now that I really looked into it, gotta say, I'm super impressed with the implementation and all those new ideas!

having the same issue with the usb2db15, but I'm sure we'll get to the bottom of the issue soon^^
 
Last edited:
This morning I did a little investigation regarding the USB2DB15.

I checked it with my older HAS units, it worked just fine. Tried with the V5.0 - all inputs appear grounded, the adapter doesn't work.

I supplied power to the USB2DB15 via the DB15, but didn't connect it to any supergun or PCB game - it also didn't work, the LED wouldn't light up.

I opened the adapter and checked the voltages. The 3V3 regulator wouldn't get power.. so I checked the 2SA1213 transistor and found something weird:
Emitter - 0.05V
Collector - 5.14V
Base - 4.93V

How can you get voltage on the collector if there's no voltage on the emitter and the base is so high?

I checked the USB2DB15 schematic, voltage regulator/transistor datasheet, and board layout, and found the culprit:

schematic.jpg

2SA1213.jpg

usb2db15_PNP.jpg


If you look closely, the collector and emitter of the 2SA1213 are swapped places! The PCB uses an incorrect part library.

So why does the USB2DB15 work with older superguns, or at all? Because of the parasitic power supply effect. During startup, the USB2DB15 drains current from the JAMMA PCB game button inputs, just enough to power on the S-816 voltage regulator, which then saturates the 2SA1213 transistor. This way the whole USB2DB15 circuit is powered on.

Since the HAS V5.0 buffers all button lines, the DB15 inputs use 20-30K pull-ups. There's no way for the USB2DB15 to drain anything from such inputs, so it cannot start. Buttons appear grounded.

To confirm and test this for yourself, power on your supergun+USB2DB15 without any PCB game connected. The adapter won't turn on. Add a 1K pull-up resistor on whatever button output of the USB2DB15 to mimic the PCB game's button input - it will turn on just fine.

There are a few problems with this:
a) The USB2DB15 drains current from your PCB game's button inputs during startup. First of all, you don't want this to happen at all. Secondly, it can also cause damage to the microcontroller on the USB2DB15.
b) The collector and emitter are swapped places, so when the adapter turns on, the collector (output in this case) is shorted with the main 5V line.

@Raph_friend was made aware of the situation and I'm sure he will find a solution.

To HAS users (all versions), I don't recommend using the USB2DB15 until this is sorted.
 
Last edited:
Thanks a lot for taking the time to look into this and doing the writeup like you did!

we found this out by chance and we'll make our setups safer because of it, mistake happen, and we grow more knowledgeable from of it👍
 
Greatly appreciate you two looking into this! Will definitely be implementing the fix once it's confirmed.
 
Thank you both for troubleshooting this so fast. I had just ordered a USB2DB15 maybe a week or two ago with the intention of using it with the HAS (once that is back in stock and I can place an order). Looking forward to receiving my USB2DB15, and awaiting the next in-stock notification for the HAS. This community is awesome!
 
Back
Top