2 ControlBlocks not working together

[petrockblog]

Hi!
Did you set the hardware address as described at https://github.com/petrockblog/ControlBlockService2#4-player-extension-with-two-controlblocks?

Can you post a picture of your hardware setup here?

[daviddam]

Here are some pics. Sorry the SJ1 pic isn't very clear. I verified with a multimeter that the one pad is not connected to the other two and that the other two are connected.

https://ibb.co/c8QwrS
https://ibb.co/ja40J7
https://ibb.co/diDud7

[daviddam]

Any chance anyone has any more ideas? It's been almost 4 weeks since I sent the images.

[petrockblog]

Sorry for this delay.
Another thing that I thought of is that maybe the two bent pins (11 & 12) are touching each other when the second CB is attached as well.
If you have a side cutter you could cut these two pins on CB1 to mitigate this.

If this idea does not help, I could provide you with a RetroPie image that I tested successfully with a four player configuration with two ControlBlocks. In that way we could rule out that it is a software issue.

[daviddam]

Yes, please send me the image you have. I tried cutting the pins and still no luck. At this point I'm out of ideas.

Thank you.

[petrockblog]

I just tested a four-player hardware setup in my side. It seems that something broke in the driver: Starting the ControlBlock service with a second ControlBlock enabled via the config file lets the driver return with error code 139 right after start:

pi@retropie:~/ControlBlockService2/build $ sudo ./controlblock 
pi@retropie:~/ControlBlockService2/build $ echo $?
139

I am sorry for that! I try to have that fixed until Wednesday. I let you know then here.

[daviddam]

@petrockblog Any luck getting the driver updated?

[petrockblog]

I am still working on it. I do not make progress as fast as I expected. Something got screwed up with one of the recent change sets of the driver.

[daviddam]

OK, thank you for the update.

[petrockblog]

I just pushed an update for the ControlBlock driver. The four-player feature should work again now!
Sorry for this bug!