Aimtrak Installation Issue

Efriim

@a1084426
Okay, thanks for being understanding, I've been away and did not read many the updates.

I have no aimtrak device, the script gunconf calibration works for me from a RetroPie 4.4 image. So it is probably not the usb device.

I just got a 64gb sdcard so I'm starting new, and I'll try some things to see if I can understand your scenario better.

a1084426

@Efriim that's fine I'm a windows admin so Raspberry and Linux is a little foreign. I've got some commands to run on the install "sudo python setup.py install /home/pi/gunconf/test.log 2>&1" this will log everything to a file on the install so I can see if anything gets a denied or error and then go from there. I do see a permission denied on some folder but it scrolls off to quick so I cant see if that's an issue or not.

I also updated to latest Raspberry OS and made sure it is using python 2.7.
the script actually mostly works and detects the trigger pull fine, just then doesn't goto the next step to read the gun config

Efriim

@a1084426
What raspberry pi model, and which retropie image have you built up from?

a1084426

@Efriim pi 3 b+ Debian - Stretch image, then everything on top, emulation station etc etc. I upgraded raspi config OS modules to the latest from the retropie setup menu. If you want specific version numbers I can get these when I get home and post. Retropie is 4.4.12 I think or updated last 3 weeks ago

a1084426

@Efriim I also tried a pre built Stretch image from arcade punks 32gb one and updated and same issue, thinking its either version related or permission issue somewhere. I could try use the default image with noobs on it, just install emulation station and retropie, no upgrades then run this script or the Easy Hax to install advance mame and try again

Efriim

@a1084426
Yeah, try this first python --version

running the sudo python setup.py install, required an internet connection or at least used it when the script was executed. I'm wondering now how to uninstall

sudo python setup.py install /home/pi/gunconf/test.log 2>&1
did not work for me the command wasn't interpreted correctly and the install was ignored no log file created.

EDIT
I think I was able to uninstall by running
sudo pip uninstall pyusb pgu gunconf
and removing
sudo rm /etc/udev/rules.d/99-aimtrak.rules

you could give me a list of your installed python scripts by typing
pip list

also what is the shell environment you are using
echo $0

and
python --version

a1084426

@Efriim yeah the log didn't work either for me. I will try the above when I get back home and post. I also spoke to the Linux guys here about adding 0777 as the access on the rules fiel just incase it was a perms issue to the usb device

a1084426

@Efriim pip list
dnspython (1.15.0)
evdev (0.7.0)
gunconf (0.2.0rc2)
numpy (1.12.1)
pgu (0.18)
pip (9.0.1)
pycrypto (2.6.1)
pygame (1.9.3)
pygobject (3.22.0)
pyudev (0.21.0)
pyusb (1.0.2)
RPi.GPIO (0.5.11)
setuptools (33.1.1)
six (1.12.0)

running bash environment

a1084426

@Efriim python version 2.7.13

Efriim

@a1084426
Everything looks good except for evdev (0.7.0) and RPi.GPIO (0.5.11)
I have evdev (1.2.0) and RPi.GIPO (0.6.5)
We could try uninstalling them they are easy to reinstall
pip uninstall evdev
pip uninstall RPi.GPIO
sudo apt-get install --reinstall apt-transport-https python-dev python-pygame python-setuptools
cd
cd gunconf
sudo python setup.py install
evdev should be installed with the setup.py script, an internet connection may be required for it to download, or you could try simply the command below, to see if it will update.
pip install evdev

a1084426

@Efriim will try this when home. One issue I have atm with mame 2003 is with my Xarcade Tank stick and the lightgun install it sends the autoconfig haywire. so I have started to use advmame on all my arcade roms as this seems to play nicer with a light and 2 joysticks installed. Have you found mame 2003 with devices like lightguns is harder to config

Efriim

@a1084426
No experience with light guns, the usual problems I encounter with Mame are finding the parent roms and Mame versions.

There was another thread before this one, where the solution we discovered for off screen aimtrak reticle drifit was solved by changing the Mame setting for mouse/device/lightgun sensitivity from 100 to %50.

I am %80 confident that the evdev being the correct version will solve the earlier problem with gunconf.

a1084426

@Efriim sorry same error. ive even re-imaged to noob install no other updates other than default retropie basic install

python version

2.7.13

pip list

automationhat (0.1.0)
blinker (1.3)
blinkt (0.1.2)
buttonshim (0.0.2)
Cap1xxx (0.1.3)
chardet (2.3.0)
click (6.6)
colorama (0.3.7)
cryptography (1.7.1)
dnspython (1.15.0)
drumhat (0.1.0)
enum34 (1.1.6)
envirophat (1.0.0)
evdev (1.2.0)
ExplorerHAT (0.4.2)
Flask (0.12.1)
fourletterphat (0.1.0)
gpiozero (1.4.1)
gunconf (0.2.0rc2)
idna (2.2)
ipaddress (1.0.17)
itsdangerous (0.24)
Jinja2 (2.8)
keyring (10.1)
keyrings.alt (1.3)
MarkupSafe (0.23)
mcpi (0.1.1)
microdotphat (0.2.1)
mote (0.0.4)
motephat (0.0.2)
numpy (1.12.1)
oauthlib (2.0.1)
pantilthat (0.0.7)
pgu (0.18)
phatbeat (0.1.1)
pianohat (0.1.0)
picamera (1.13)
picraft (1.0)
piglow (1.2.4)
pigpio (1.38)
Pillow (4.0.0)
pip (9.0.1)
pyasn1 (0.1.9)
pycrypto (2.6.1)
pygame (1.9.3)
pygobject (3.22.0)
pyinotify (0.9.6)
PyJWT (1.4.2)
pyOpenSSL (16.2.0)
pyserial (3.2.1)
pyudev (0.21.0)
pyusb (1.0.2)
pyxdg (0.25)
rainbowhat (0.1.0)
requests (2.12.4)
requests-oauthlib (0.7.0)
RPi.GPIO (0.6.5)
RTIMULib (7.2.1)
scrollphat (0.0.7)
scrollphathd (1.2.1)
SecretStorage (2.3.1)
sense-emu (1.1)
sense-hat (2.2.0)
setuptools (33.1.1)
simplejson (3.10.0)
six (1.12.0)
skywriter (0.0.7)
sn3218 (1.2.7)
spidev (3.3)
touchphat (0.0.1)
twython (3.4.0)
unicornhathd (0.0.4)
urllib3 (1.19.1)
Werkzeug (0.11.15)
wheel (0.29.0)

a1084426

the aimtrak firmware is 9.2 as well on the device if that helps too that's the only other thing I can think of

Efriim

@a1084426
It's my fault for believing the resolution must exist in the guncon installation.
Perhaps then using the windows aimtrak utility to change the device mode and parameters. I'm at a loss. Either mouse mode and the device ids and firmware you have now, should all be okay.

The rpi model is rpi zero? Why not have installed the retropie image found on the website here?
I'll read about udev as I forgot my last question.
The gunconf script closes after which function?

a1084426

@Efriim Raspberry pi 3 b+ with new noobs based raspberry pi 3 image, then a default Retropie image installed on it, from the main retropie uk website. So it's as vanilla as possible and as default as possible.

The gunconf never closes it just sits there trying to read the gun config. The Exit button is highlighted and if you execute that, it then drops out to terminal mode.

if you have a particular image I can try that as well as I have a few spare microsd cards

Efriim

@a1084426
I don't have an image to suggest than the retropie one. It is information for a better frame of reference.

Do you have any dtparams or dtoverlays enabled in /boot/config.txt?

gunconf/utils/gunconf_w_logs.sh
That is the guncon script with logs.
I think it will create a file ~/.gunconf.log
Have you been able to read this log previously, it may have info for what is happening?

a1084426

@Efriim there enabled should they be turned off. ill get the log file out and post it

a1084426

Efriim

@a1084426
I'm almost out of ideas.
check out the folder /etc/udev/rules.d/ for duplicates or misnamed "99-aimtrak.rules"
ls /etc/udev/rules.d

I don't remember if you tried this already. On windows computer using the aimtrak utility to try updating the firmware again, maybe it got unplugged during update a loose connection or something while saving settings.

I think that is all I've got, but if I think of something or stumble on something else I'll update you.
Try contacting the the aimtrak people, there might be someone who would be happy to give you sound advice for that device.