GRS Star Wars flight yoke issues

[cool_factor]

20230114_112405.jpg (227.56 KiB) Viewed 22431 times

[dee2eR]

In mouse mode is it just a mouse or still a joystick too?

Had a thought, is there any way to have the ArPiCade OS show/create a log file when it initially first starts/boots up to see what just might be going on?

dmesg should be able to do that on the command line directly. Try something like this (this should bring up any joystick related kernel messages):
dmesg | grep joystick

[cool_factor]

In a file or ??? I know very very little of Linux.

[dee2eR]

it will output directly on the terminal but you could also make it write to a file if you liked (depending on the file location you may need to start the line with sudo for write permission). eg
sudo dmesg | grep joystick > /path/to/file.txt
the terminal can be hard to read on an arcade CRT, if you can do it on a high res monitor it will likely be easier to read.

Shame you can't just set the yoke to mouse mode and have it work as a mouse without joystick anything. I have some mouse experience after a fair bit of messing with Sindens and Gun4IR.

[cool_factor]

20250206_070830.jpg (95.59 KiB) Viewed 22413 times

[dee2eR]

was the yoke plugged in? If so it may not be using joystick in it's name presented to the linux kernel, you could try replacing joystick in the search with yoke or mouse or maybe pad...

From what I can see there the GPIO joysticks (ie the JAMMA controls) are player 1 and 2. At least I'm assuming that from the pad0 pad1... no sign of them being bumped.

[dee2eR]

Out of curiosity... do you still have ARpiCADE_5 on SD? If so does the yoke have the same behaviour on it when tested on the same Pi4? ARpiCADE_5 uses a different GPIO joystick method so may behave differently to the mk_arcade_joystick driver.

I get this isn't a solution for you if it works but I'm curious. If I had to guess it is probably just as bad going by the hotkeys issue...

[cool_factor]

Yes it was plugged into a usb port. Can that command be used to report usb stuff.. I can try and burn v5 with just Star Wars ROM and test but I was having issues on my vert cab with v5 so I left it alone until I figure this out on my horizontal cab

[cool_factor]

This was from 2023. Seems the flight yoke is first thing seen. I dont recall how I did this.

Re: Arpicade without the Raspberry Pi?
Post Sun Apr 23, 2023 10:22 am

heres whats happening with the GRS Star Wars flight yoke:

It pushes joy1 to joy 3, joy 2 to joy4 and breaks the hotkeys, if I unplug the GRS everything reverts back to normal.

This A.M. I managed to figure out device IDs:

Joystick: Start initialization Input: Adding joystick #0: BaolianindustryCo.,Ltd.BLflightyoke#1 (device id: 03000000be3200000214000011010000) Joystick: Baolian industry Co., Ltd. BL flight yoke #1 [GUID 03000000be3200000214000011010000] Joystick: ... 2 axes, 15 buttons 0 hats 0 balls Joystick: ... Physical id 0 mapped to logical id 1 Joystick: ... Does not have haptic capability

Input: Adding joystick #1: XboxGamepad(userspacedriver) (device id: 0000000058626f782047616d65706100) Joystick: Xbox Gamepad (userspace driver) [GUID 0000000058626f782047616d65706100] Joystick: ... 4 axes, 15 buttons 0 hats 0 balls Joystick: ... Physical id 1 mapped to logical id 2 Joystick: ... Does not have haptic capability

Input: Adding joystick #2: GPIOController1 (device id: 15000000010000000100000000010000) Joystick: GPIO Controller 1 [GUID 15000000010000000100000000010000] Joystick: ... 2 axes, 9 buttons 0 hats 0 balls Joystick: ... Physical id 2 mapped to logical id 3 Joystick: ... Does not have haptic capability

Input: Adding joystick #3: GPIOController2 (device id: 15000000010000000200000000010000) Joystick: GPIO Controller 2 [GUID 15000000010000000200000000010000] Joystick: ... 2 axes, 9 buttons 0 hats 0 balls Joystick: ... Physical id 3 mapped to logical id 4 Joystick: ... Does not have haptic capability Joystick: End initialization

[dee2eR]

No pressure to mess with the ARpiCADE_5 stuff if it isn't convenient.

You can replace 'joystick' in the dmesg | grep command with anything 'usb' may find what you're after. It's just looking through the kernel startup output, shouldn't hurt if you try a few things in the search *(one at a time).

EDIT having seen your new post. (is that output from MAME rather than the Linux kernel?)
What happens when the yoke is in mouse mode as per the instructions leaflet you posted? It may be worth having a look at the MAME output when it's in each of it's modes to see what (if anything) changes.