It's been a while since I took another look into this, but I have a lead that this forum could possibly help with. On a side note, the Arduino forum was not very helpful at all. The only thing that I could think of was if the Arduino was being driven too much power (or if the power is inconsistent somehow), and the switched I have in the dance mat are acting as capacitors and letting some current through. I haven't done any measurements or math to look into this, but it seems very unlikely to me.

Asking chatgpt, I got lead to check permissions of the usb device, and even giving the decide all permissions does not help. However, I decided to check the dmesg log, and noticed something. I am transcribing this from a photo I took of the text on a CRC tv, so I apologize if there's errors.

[ 153.053753] usb 1-1.1.3 New USB device strings Mfr=1, Product=2 SerialNumber=3 [ 153.053758] usb 1-1.1.3 Product: Arduino Leonardo [ 153.053763] usb 1-1.1.3 Manufacturer: Arduino LLC [ 153.053768] usb 1-1.1.3 SerialNumber: HIDAF [ 153.067997] input: Arduino LLC Arduino Leonardo as /devices/platform/scb/61500000.pcie/pci0000:00/0000:00:00.0/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.2/0003:2341:0036.0003/input/input4 [ 153.068204] hid-generic: 0003:2341:8036.0003: input.hidraw2: USB HID v1.01 joystick (Arduino LLC Arduino Leonardo) on usb-0000:01:00.0-1.1.3/input2 [ 154.009506] cdc_acm 1-1.1.3:1.0: ttyACM0: USB ACM device [ 154.092227] usbcore: registered new interface driver cdc_acm [ 154.092232] cdc_acm: USB Abstract Control Model driver for USB *[illegible]* and USB adapter

A couple things I noticed here: The arduino is being read as an input into input 4, and it is being read as a HID joystick into input 2, and it is being read as an ACM device. Do any of you think that being registered as multiple inputs/systems could cause the issues I am seeing? And if so, how can I make Debian only recognize the arduino as one device? I am not linux savvy enough to know how to do that.

Thanks!

@drog1998 I use an Arduino Leonardo (Atmega32 chip) to connect an Amiga keyboard to my Raspberry PI. It works very well, no bug at all. I never have to unplug and replug for instance. I use it with every emulator of computers.

I use a self-powered hub to connect it to my Raspberry Pi 4 (actually, every USB thing is connected to this self-powered USB hub in my configuration).

@mitu alright thanks man! this will help me so much on this project!

The repo is now live:

https://github.com/DirtBagXon/hypseus_scoreboard

Please share your creations with the community.....

You can send commands to your led panel also from EmulationStation's event system, which was expanded recently to support more entry points - https://retropie.org.uk/docs/EmulationStation/#scripting.
There have been a few integration using this method:

https://retropie.org.uk/forum/topic/30528/ https://retropie.org.uk/forum/topic/22195/

As long as you have the commands to control your panel, you can create scripts to send those commands based on EmulationStation's state and operations.

@bollwerk said in How to configure both analog stick and d-pad for retroarch arcade config?:

I assume the Arduino config (or any joypad input config) overrides the retroarch.cfg in some way?

Your configuration in retroarch.cfg - as it is right now - configures a keyboard.

input_player1_r = "w"

When configuring a gamepad, the syntax is different:

input_player1_r_btn = "12"

RetroArch will load - indeed - the configuration from the autoconfig sub-folder if it finds one. The gamepad's auto-configuration file was generated by EmulationStation when you configured the gamepad in the Input Configuration step.

I find it easier to open up the RetroArch's menu (via Hotkey + X) and use the Controls menu to change things, test them and then save it with a Core input configuration remap.

For more details, see https://retropie.org.uk/docs/RetroArch-Configuration/.

@arduinoGamepad Emulationstation is using SDL's joystick sub-system to handle joysticks, my guess it's not detected as such. There's a similar sdl-jstest utility -which is similar to jstest - that tests whether the joystick is detected by SDL.

To get it detected by ES, try one of these - in order

add a local udev rule to force the device to appear as a joystick: SUBSYSTEM=="input", ATTRS{idVendor}=="<VID>", ATTRS{idProduct}=="<PID>" ENV{ID_INPUT_JOYSTICK}="1"

substituting VID and PID with the values you get for your controller from running lsusb.

Use Xboxdrv to make your device be seen as an Xbox driver.

@samco friend, I’m looking at your videos about your samco project since 2016 videos.
This concept almost same with wiimote and dolphin bar right?
I has a big problem with wiimote and dolphin bar.
If I use 1 wiimote as a lightgun, it works properly.
But after I connected the 2nd wiimote the crosshair always merge beetwen player 1 and player 2.
I’m already change the dolphin bar mode (1-4)
What I want to ask is, is the wiimote not supported for 2nd players at retropie ? I’m affraid if I build the samco project I will experience the same things.

@dankcushions said in Design dilemma for retro arcade machine:

plus of course, if you play any console games the 'insert coin' button is by default also the 'select' button, which is used in SNES, PSX, etc.

No plans to play any console games. I was always a C64/Amiga fan, but I emulate these on my PC 'cause it's a more suitable environment than a arcade machine. The one game I wouldn't mind from a console would be Alex the Kid from the Master System (I believe).

Thanks for your input

@meleu said in Retroachievements Help:

I replied your other topic, and gonna repost here:
I think you can get some inspiration in this thread here:
https://retropie.org.uk/forum/topic/11793/gpio-triggered-by-retroachievements

That's really amazing and easy to do as you already presented a good solution :D

wow, awesome...thanks that points me in the right direction at least

@thomen It looks like it is an older, D-Link model DUB-H7 USB2.0 powered hub. You can see it in my project build thread (click link in my signature below). I have since cleaned up a bunch of USB cables using custom ones I built to length, but the shorter, white USB cable in the image is the power for my LEDs.

This hub definitely pre-dates high-power charging for smartphones and tablets, so might be an out-moded design. It seems these days, folks would want their devices to continue to get power for charing even if their computer is OFF. I wonder if a modern version of this hub will work differently.

What do you want to do with that arduino?
Retropie is built for the raspberry pi, not an arduino.

Use python and it's native GPIO support :)
But thank you for the link... So Arduino programs can be ported to RPi.
You can usually use programms in the background to control switches even with ES running - because these programs are not "active" like in windows. They just wait for a trigger to act (=set interrupt)

http://mheironimus.blogspot.gr/2015/09/linux-support-for-arduino-leonardo.html

Solution Found! For anyone else having problems with Leonardo/Micro problems, it's just a matter of adding a string to the end of the line in /boot/cmdline.txt depending on your setup:

usbhid.quirks=0x2341:0x8036:0x040 (for Leonardo)
usbhid.quirks=0x2341:0x8037:0x040 (for Micro)

Yay!

Hello, are you sure that emulator have binded "right key" ? I mean, if emulator doing something when you press right arrow on keyboard?

@rbaker Hi!
retroarch.cfg I'll post few hours later, when I'll get home.

Regarding power supply - I use an external 5V 2A USB power adapter and the joystick works fine in Emulation Station, I can scroll pages, select menu items, etc. with it, but it stops working in any configuration tool from RetroArch I try to start.