PS1 G-Con as USB Mouse

[sonik]

I'm trying to adapt a ps1 guncon to usb mouse using an arduino.
Already got some readings from the guncon and mapped it as a mouse. This could theoretically work on any machine with usb hid mouse support.
It's reporting error from time to time. Seems like it can not be read in the middle of a vsync (witch I don't have any control)
Any advice? I can't find much info on this and the drivers for windows are all closed source.

Update:
Project is now on github
https://github.com/sonik-br/GunconDuino

[sonik]

After some tweaks it's working very stable!
I will make a video later.
If anyone wants to make it just needs an arduino (I'm using a Leonardo) and a way to connect the gun to it (I'm an ps1 extension cord).
Tested on windows only. Should work in any OS as it's reporting as a usb hid mouse.

[sonik]

Testing on windows 10 at 240p

[burn_654]

Very, very interested in following this! Especially your code on extracting the location from sync data.

I've been on and off over the last several years working on a concept to get (3rd party) Guncon2's working with crt's using the TopGun driver (I've nicknamed it TopGunCon in some old threads). I've more or less accomplished the goal but it's a spaghetti mess of code and hardware. In its last running form it used 555 circuits to delay the shot just slightly, pulse an input on a usb interface (I used an input on jpac but most any would work) to launch a full-screen screen 'flasher' app. This limited shots to be timed within a white screen flash from my app so all locations on the screen could be properly shot and allow off-screen reload. If I had to get my specific scheme out there now I'd definitely clean it up and implement as much as possible in an arduino. Having a solution with an open code-base could solve a lot of problems I was solving because of the specific behavior of the Topgun driver.

The flash becomes necessary even in games that have one, some (such as mame) only determine a *shot* or *miss* input after the controller logic has already happened - it plays dumb in that respect. If mame gets a left click (shot) it submits a left click to the mouse hardware coordinates. If it receives a right click it thinks it's offscreen. Thus, it's up to you to determine the on-screen/offscreen logic of the gun and send the appropriate left click/right click to the computer. At least that's the logic I followed. The flasher app my brother and I developed used the windows gamma ramp as a fullscreen *white* flash so it worked no matter resolution/fullscreen or windowed etc. It can map timed flashes to most hid devices (keyboard, mouse, gamepad). There are some minor issues with some colors not reaching all the way to white (windows protections because of the gamma ramp method), but overall it's been successful. It sounds like you may be able to use it with this, if it helps with your prototyping? I would be glad to provide it privately.

I'll be following this with great interest...I'm not sure on the vsync issue. But I would be glad to test/chat about this!

[sonik]

I'm not touching video signal at all.
Just reading the guncon with an arduino and the amazing library PsxNewLib.

If you have a guncon1, a arduino and a way to connect the guncon to it, you could try it!
My code works but it needs some adjustments and a propper way to calibrate.
I still need to test it with games and see if it's required to flash the screen.

I have also a code to access a guncon2 via usb and move the mouse. Works on windows 10. It's not a "driver".
Works with guns that dont have the "rolling x" problem. It's possible to fix but I have not done it yet.

I can share everything if there's any interest.

[burn_654]

I'd say yeah, go for it!

I've loaded up with a few extra arduino pro micro's (same chip as leonardo), I can definitely order a psx extension to mess with this.

Given there's been so little love in crt light gun projects (and to suddenly see two very interesting projects just appear!) I'd say whatever you have is worth sharing for people to look at.

[sonik]

Cool!
I will release the code in the coming days.
But be warned that it still needs a lot of fine tuning to be usable. Also I got it working with oficial namcon guncon. Could not make it work with a "clone" guncon that I have.

If/when it works as it should I will definitely get this arduino shield:
https://www.pcbway.com/project/shareproject/PsxControllerShield_V1.html

[sonik]

I'd say yeah, go for it!

I've loaded up with a few extra arduino pro micro's (same chip as leonardo), I can definitely order a psx extension to mess with this.

Given there's been so little love in crt light gun projects (and to suddenly see two very interesting projects just appear!) I'd say whatever you have is worth sharing for people to look at.

Project is now on github
https://github.com/sonik-br/GunconDuino

[Marsupial]

Would this work with other PS1 light gun?
You only mention having tried one guncon clone.


I got a nyko super cobra light gun and my arcade has a CRT vga screen... If there are chances this actually works I'd be willing to give it a test.

[sonik]

I only have one guncone clone gun to test.
Can't say if it will work with others.
I will try to make it work again in the coming days. Will let you know if it works.
And I could not make it work with a vga monitor. only standard def crt tv.
For real vga support you should check GUN2CRT.

[Marsupial]

Thanks.
Not vga compatible is a bummer.

Keep us posted of the progress.

[manhunt]

Let’s make a tutorial, the compilation is unsuccessful, the production code is unsuccessful, thank you

[sonik]

I've sent a PM to you.
Need more details.

[bandicoot]

no problem for me to program it , it really work well ( i need to increase brightness of my CRT but this is the same with my Playstation )
In the future if we could turn G-CON45 to a GUNCON2 to make this work on PS2 too 
Thankls for your work @sonik

[sonik]

no problem for me to program it , it really work well ( i need to increase brightness of my CRT but this is the same with my Playstation )
In the future if we could turn G-CON45 to a GUNCON2 to make this work on PS2 too 
Thankls for your work @sonik

I'm glad it's been useful
I've added support to use it as a mouse or a joystick. Need to do some testings before I will update the source on github...
For PS2 output I will need some help. Have no idea how to do it. It's my first project arduino project and I also don't have good knowledge with electronics.
Would be great to have it output to PS2 and the original Xbox.

[sonik]

Playstation accessories works with 3.3v.
Arduino is sending 5v on it's data pins. It can damage the guncon.

I'm doing some tests with a level shifter and also using the hardware SPI on the Leonardo.
I'm waiting for my arduino shield to arrive then will do more testings.

I advise to not use it with 3.3v.

BTW by using the correct voltage and the hardware SPI, seems like my thirdy party gun will work! This is great news!

[Marsupial]

There are several 3.3v arduino. Maybe change board model?

[sonik]

The 3.3v boards have half processor clock speed.
At least the ones I know.

[PL1]

The 3.3v boards have half processor clock speed.
At least the ones I know.

A 3.3v 32u4 AVR board running at 8MHz should be fast enough for an encoder firmware.   
- Bruno used 3.3v from various consoles such as PS1, PS2, Wii, Wii U, NES Classic, GC (3.43v), and N64 to power the AVR board for the miniArcade 2.0 firmware. (see page 7 of the User Guide)


Scott

[sonik]

Cool!
It might work then if it can be used as a USB HID device.

For now I will keep using the Leonardo as it's the only arduino I have. And I'm waiting for the shield to arrive.

[PL1]

It might work then if it can be used as a USB HID device.

For now I will keep using the Leonardo as it's the only arduino I have. And I'm waiting for the shield to arrive.

Yes, you can define any of the 32u4 series boards as a USB HID device via the firmware, assuming you use the proper code.
- I can't help with the HID code, but baritonomarchetto might.

On second thought, a lightgun mouse needs a lot more processing power than a console encoder for buttons and A/D conversion for analog thumbsticks so 3.3v/8MHz might not be fast enough to avoid lag.   
- It can't hurt to try and many of the boards have a solder pad jumper to select 3.3v or 5v so if running the board at 3.3v/8MHz doesn't work, you can easily revert to 5v/16MHz.
- Of course, if the board does work well with 3.3v, you don't need the 3.3v<=>5v logic level converter chips to protect the gun.   

If you want to make it compatible with more AVR boards like the commonly-available and very-inexpensive Pro Micro, you might want to only use pins/ports that are available on that board.
- Avoid the seven pins/ports listed at the bottom of this diagram.
- For example, the miniArcade 2.0  firmware uses port C7 (32u4 pin 32) for rotary joystick #2 (Rot. 2B) so you can't run two rotary sticks on a single Pro Micro. 




Scott

[sonik]

Pins are not a problem.
User can map the 4 PSX data pins to any 4 arduino I/O pins. Just need to update the sketch file with the pins numbers.

But I will start to interface the PSX controller using arduino's hardware SPI so it will need those dedicated pins.

[sonik]

Project updated.
Now it uses the arduino's ICSP headers and proper 3.3v.

And it now can work in mouse or joystick mode.
I prefer to use joystick mode with Mame. And it's required to work on the Mister FPGA.