ok.. I'm having a couple of issues that I though someone could help me correct.
1. When I generate the input map, it doesn't seems to be saving the config I set up. For example, in the input map I set the player1 button1 for the top left button on my control panel, but when I go to the button configure editor and test the led it is lighting the top left button on my control panel as player1 button7 ?
Are you testing the button from the Controls Editor "New/Edit Control" dialog? If so, the LED that lights up is just for checking the color or intensity - it is not the actual button you may be adding or editing. You can change this using the "Test Single LED" drop-down.
But back to your actual problem - the input map must reflect how your LEDs are physically wired and match the input codes used by your input encoder. The control names like "P1B1" or "Player 1 Button 1" are just labels for reference.
So for example, let's say you have a LED under a button you refer to as "P1B1" and that LED is wired to port 1 on the PAC-Drive. And let's say the switch for P1B1 is wired to your input encoder and assigned to keycode "A". On LEDBlinky's input map, you would set the device to PACD-1 and for Port 1 you set the LED type to "single" and assign the input code as "KEYCODE_A". As for the label, you can use anything; "P1B1", "BUTTON-A", "FIRE", whatever makes sense for your cp layout. But the control label has no bearing on which LEDs light up when you play a game - it's the KEYCODE_A that's important. Because no matter how you remap controls in mame - that button will always respond to keyboard "A" (unless you rewire or reprogram your input encoder). Hope this makes sense.
2. I have something messed up with my trackball config somewhere also. I'm using a Ultimarc U-trac that has a RGB LED under it. When I test the LED it lights the green LED as blue and the blue LED as red. I can't seem to figure out how to configure which one goes to the correct color.
In this case you have a RGB LED which is wired to three ports on the PAC-Drive. So the input map for those three ports MUST have the same label and input code (in your case use "TRACKBALL" for the input code). The LED type for each port should be correctly set to "RGB-Red", "RGB-Green", and "RGB-Blue" as is
physically wired to the PAC-Drive ports. If you get the colors wrong here, then LEDBlinky will not use the correct colors.
3. In the button config editor under mame, there are only like 5 roms to edit, the ones that are there by default I think. The common games like centiped are not there to edit. I'm not sure if it is the correct way, but what I did was added the game manually and I was able to edit it that way. Is there a way to find these games and edit them without having to add each one?
For MAME, you shouldn't need to manually edit the games unless the Controls.ini file is wrong or a game is missing from Controls.ini. The five that are listed were included because I felt they needed additional values. So basically, if you have the LEDBlinky config correctly pointing to the controls.ini file, then the mame controls should all light up correctly!
Any help with this is appreciated....
If you can't get it working, turn on the debug and verbose options (on the "Misc Options" tab), run your FE and some games, then email me the debug.zip file in the LEDBlinky folder.