I got them working...basically the confusing part is that, in mame...you go into a game and choose a control, lets say player 1's first button. Well, in mame you go into 'default controls - all games' and select that control you want to change and then push the button to set the gamepad button. In my case it might say Player1_Button0....and it works. However, then LEDBlinkey doesn't light it up right. When I went into the default cfg file, that same button is listed as Player1_button1.
At first I thought that was a problem, until I realized in LEDBlinkey's config that there's no Player1_Button0 option...so as soon as I changed LEDBlinkey to be one higher for every control, then everything started working.
So basically, mame's GUI doesn't match what it puts into the default.cfg file...so when you're trying to assign lights to buttons in the LEDBlinky config program, make sure you're using the data from the default.cfg file, or looking at the mame gui and adding 1 (so button0 would be button1, button7 would be button8, etc...)
My next issue is trying to get LEDBlinky to work with LEDSTART... for example, when Battlezone gets credits, it wants to flash LEDSTART, which is coming through the LEDBlinky mame troubleshooter app as 'unassigned'. If the game coins up and flashes LED0 or LED1, I have that working for player1 or player2 buttons to flash properly....but I'm not sure where to assign the 'unassigned' LEDSTART variable...to point it to the player1 button. In the case of Battlezone, basically nothing flashes, even though it's sending the commands to make it happen...
Pete