LedBlinky mysterious problem

[Marcoqwerty]

Hello...shortly i'll try to explain my courios issue with LEDBLINKY

this is my setup:

- Ledblinky
- Mame 160 but also 187
- Hyperspin/Rochetlauncher
- SmartASD encoder (working with LB trought Output port)
- Some output (two specially : Change View = CV and Rumble = RU)

Aim: Blink the Output for MAME (in this case spyhunter)

Issue:

- Launch LB and setting the LED ID in the GenLEDBlinkyInputMap.exe (all the input working correcly, click on he test and every single led and the Rumble start single)
- Setup mameoutput.txt ,for example spyhunter, to Blink only CV led when there are credits.
- Launch Mame and CV and RU starting togheter

Now i cant reverse the condition every time i run Mame start BOTH...CV and RU

Extra Test:

- Disconnected, deleted, unlinked LB from the system and use MAMEHOOKER for a test with mame...i getting the same result when blink the credit CV start RU at the same time.
- All the other light game with LB during Hyperspin menu etc....works correcly.

After hors i have reset to initial condition (but i dont know how) and Mamehooker works correcly, but if i try to launch again LB the issue coming back.

That's all...i start to getting crazy about this! 

[arzoo]

Hi, I think for me to help with this I'll need to see how you have LEDBlinky configured. Could you turn on the Debug Log option (Misc Options tab), run Spyhunter, then email me the debug.ZIP file and MameOutputs.ini file in your \LEDBlinky folder.

[Marcoqwerty]

Thank you for the reply...i start to investigate this week for this issue...and im not totally sure its a LB issue...

I restored the old working stable situation but after another test with only Mamehooker this happens again.

For sure this issue starts after i had made a test with LB.

I send the log soon.

 

[Marcoqwerty]

Ok i solved the situation in other way....chache the output from my output device, maybe there is an issue with these two pin.

Thank you for the support!

[arzoo]

Glad you got it working!

[Marcoqwerty]

Definitely not a LedBlinky issue!