Build Your Own Arcade Controls Forum

Main => Main Forum => Topic started by: Kordova on November 03, 2009, 03:22:45 pm

Title: IPac4/Pushbutton not sending continuously, please help.
Post by: Kordova on November 03, 2009, 03:22:45 pm
Hello all,
I am use the IPac4 for my control panel.  Everything has been working on it well for the last couple of months, however, I noticed yesterday that one of my pushbuttons seems to be malfunctioning.  All of the other 35 or so pushbuttons are operating continuously, if I were to hold it down it would constantly send the key code.  However, one of my buttons will only send once the button is released.  The only way to get it to activate, in other words, is to push the button, and release the button, only then does it send the code.  It is the player 2 button 2 that I am having the problem with.  I have swapped out the microswitch with a couple of extras I had and it's the same story.  Is there a setting somewhere in the iPac controls to fix this problem?
Title: Re: IPac4/Pushbutton not sending continuously, please help.
Post by: Deadly on November 03, 2009, 03:38:36 pm
Hello all,
I am use the IPac4 for my control panel.  Everything has been working on it well for the last couple of months, however, I noticed yesterday that one of my pushbuttons seems to be malfunctioning.  All of the other 35 or so pushbuttons or continuous, if I were to hold it down it would constantly send the key code.  However, one of my buttons will only send one the button is released.  The only way to get it to activate, in other words, is to push the button, and release the button, only then does it send the code.  I have swapped out the microswitch with a couple of extras I had and it's the same story.  Is there a setting somewhere in the iPac controls to fix this problem?

This acts the same way in NOTEPAD? If so I'd start by reflashing your mapping.
Title: Re: IPac4/Pushbutton not sending continuously, please help.
Post by: Kordova on November 03, 2009, 03:45:10 pm
Yeah, it does the same thing in Notepad and Microsoft Word.  I reflashed the key mapping just now and its still having the same problem.
Title: Re: IPac4/Pushbutton not sending continuously, please help.
Post by: Deadly on November 03, 2009, 03:54:33 pm
Disconnect IPAC4 shutdown
Boot up.
Shutdown
Reconnect IPAC4 and boot up

If that still fails:
If you have a boot disk handy boot to it and try to see if it's windows causing this. If it still fails outside of the GUI environment I'd have to say it's something physically worng with the IPAC4.
You could try flashing it back to stock form.
Title: Re: IPac4/Pushbutton not sending continuously, please help.
Post by: Kordova on November 03, 2009, 05:06:09 pm
So, following the advice here and a little trial and error I was able to fix the problem.  It seems that my key map file had become corrupted somehow.  I restored back to factory and then just remapped, saving the map as a new totally different file.  Thanks for your help.
Title: Re: IPac4/Pushbutton not sending continuously, please help.
Post by: surface tension on November 04, 2009, 04:13:59 am
It sounds like this button had become the shift button as this works on release for obvious reasons.
Title: Re: IPac4/Pushbutton not sending continuously, please help.
Post by: MAME TIME on November 04, 2009, 09:35:30 am
i have the same problem with the first player button, if i remember correctly its the button thats mapped to left-CTRL, which config holds the mappings? ctrlr files ??
Title: Re: IPac4/Pushbutton not sending continuously, please help.
Post by: surface tension on November 04, 2009, 10:32:24 am
When you install the winipac utility, it should include a generic config file which is default-2(or4).ipc. Check the key mappings and from within winipac. The only time I've seen that kind of behaviour is for the shift-function button. Is it possible you re-designated this? It's normally 1UP.
Title: Re: IPac4/Pushbutton not sending continuously, please help.
Post by: Kordova on November 04, 2009, 04:11:23 pm
Andy at Ultimarc confirms that the button had somehow been designated as the shift button.  I didn't do this, so I am not really sure how it happened.  If anyone else has this problem, just clear the shift button designation.  Thanks for the help everyone.