Main > Main Forum
SNK Rotary joystick controller project
<< < (3/5) > >>
brooksware2000:

--- Quote from: geekbrain on March 21, 2004, 12:11:43 pm ---I'm glad to see someone read the old post rather than having to rehash anything.  Brooksware2000 and knuttz - I will email tomorrow - I have the code at work at the moment.  I have absolutely no problem sharing the hex file freely in the spirit of MAME.  I will share the assembly source as well with the provision that if you use it you give credit where credit is due - don't plagarize and say you created it.

And most importantly - DO NOT ask me to burn chips - there are all sorts of resources on the net for doing this.  I'm an electrical engineer and have learned several useful things from the MAME experience that I have been able to apply at work.  Use the opportunity to learn something!

Like I said in my first post of this thread - the PIC code I have works well with the IPAC using Wordpad - it catches every detent (360 dgrees/12 = 30 degrees BTW).  The problem appears to be with the MAME setup.  It also might have to do with IPAC connection or motherboard BIOS (keyboard frequency) - it's presently been used with keyboard interface instead of the USB.  Don't know if that matters.  Again I will openly share based on my above comments!

--- End quote ---

No problem with that. I am a computer programmer myself and I spend so much time writing code for someone else I don't get enough time to do it for myself. I want this to be a free-for-all project. I think that we can all benefit if we work together on this. It sucks for someone to borrow from someone else without giving credit were credit is due. All the code that comes from this will be posted here for others to use/modify (with the consent of those whose portions of code may be included). If not for anything else but as a learning experience for others.

The Mame project itself is free so we can work to expand it even further with such projects as this.

Thanks to all ahead of time that are interested in this and want to help out.
knuttz:

--- Quote from: geekbrain on March 21, 2004, 12:11:43 pm ---I'm glad to see someone read the old post rather than having to rehash anything.  Brooksware2000 and knuttz - I will email tomorrow - I have the code at work at the moment.  I have absolutely no problem sharing the hex file freely in the spirit of MAME.  I will share the assembly source as well with the provision that if you use it you give credit where credit is due - don't plagarize and say you created it.

And most importantly - DO NOT ask me to burn chips - there are all sorts of resources on the net for doing this.  I'm an electrical engineer and have learned several useful things from the MAME experience that I have been able to apply at work.  Use the opportunity to learn something!

Like I said in my first post of this thread - the PIC code I have works well with the IPAC using Wordpad - it catches every detent (360 dgrees/12 = 30 degrees BTW).  The problem appears to be with the MAME setup.  It also might have to do with IPAC connection or motherboard BIOS (keyboard frequency) - it's presently been used with keyboard interface instead of the USB.  Don't know if that matters.  Again I will openly share based on my above comments!

--- End quote ---

Thank you so much.  I am very excited with this project and learning how to burn/possibly program PICs.  Also don't worry, I would never try to take credit for your work or anyone else's.  Thanks again.

Matthew
Tiger-Heli:

--- Quote from: spidermonkey on March 21, 2004, 02:04:05 am ---Uh oh, does this over/under rotate problem occur with Druins interface as well ? I'm using MAME 32 and I picked up one of Druins interfaces a couple months ago but I haven't hooked it up yet. Am I going to have to use MAME Analog plus with Druins interface or will it work ok with MAME 32 ? The reason I ask is because I haven't figured out how to use regular MAME yet.  ::)

--- End quote ---
It occurs with Druin's interface.  Specifically, I only KNOW of it occuring with Druin's interface and a custom non-interfaced rotary I was working on (with help) a long time ago.  I assume it would be a problem with these other interfaces as well.

You don't HAVE to use MAME Analog Plus with it, but otherwise you'll have to tweak the analog settings for each game, and while you can get pretty good results, it won't be perfect.

If you want to stay with MAME32, the analog plus changes have been added to NoNAMEMAME and NNM has a mame32 build - https://sourceforge.net/project/showfiles.php?group_id=91067&package_id=95932

And you can contact me if you want to migrate to command line MAME.
rdagger:

--- Quote from: menace on March 21, 2004, 07:57:55 am ---Here's that other thread in case anyone was interested
http://www.arcadecontrols.org/yabbse/index.php?board=1;action=display;threadid=14166

--- End quote ---

I had very good luck building my own rotary interface.
Here are the schematics and pics:

Rotary Interface
brooksware2000:

--- Quote from: rdagger on March 22, 2004, 08:56:19 pm ---
--- Quote from: menace on March 21, 2004, 07:57:55 am ---Here's that other thread in case anyone was interested
http://www.arcadecontrols.org/yabbse/index.php?board=1;action=display;threadid=14166

--- End quote ---

I had very good luck building my own rotary interface.
Here are the schematics and pics:

http://69.33.42.246/Arcade/ri.aspx

--- End quote ---

How did you overcome the debounce problem with the contacts on the joystick sending false signals as they slid across the terminals. I have yet to come across a solid way of dealing with this issue
Navigation
Message Index
Next page
Previous page

Go to full version