Need help with LedWiz Clone board testing

[Ron_Michallick]

Hello,

I programmed a promicro 32u4 with lwclone2u software and that seemed to work well. Not sure why there was an EEPROM file from the build. All the pin setup seems to be in the pin.h file. For this round, I left the pin.h file as is.

Device manger sees seven devices. The 'keyboard' input pins work. The analog inputs work in Mame, but I couldn't see the analog in the Kade padtest program. Is there a different padtest that works with lwclone2u? 

The part that I can't test is the LED outputs. The pin.h says two LED are setup, the onboard TX and RX leds.
I tried turning the LEDs on with mamehooker command test and LWsend.exe

Here is the pin.h section that mentions LED
#define LED_MAPPING_TABLE(_map_) \
   /* the following corresponds to the Arduino Leonardo mapping */ \
   \
   _map_( B, 0, 1 ) /* RX LED */ \
   _map_( D, 5, 1 ) /* TX LED */ \
   \
   /* end */

These are the right pins for the LED. I assume this is LED 1 and LED2.

Any advice on what to try next? 

[PL1]

Device manger sees seven devices. The 'keyboard' input pins work. The analog inputs work in Mame, but I couldn't see the analog in the Kade padtest program. Is there a different padtest that works with lwclone2u?  ??

Maybe I'm misunderstanding what you're asking here.

Are you trying to put lwclone2u and KADE miniArcade 2.0 on one single Pro Micro AVR board?   

Great if you can pull it off, but AFAIK that is not possible.   
------
IF analog works in MAME, it must also work in Windows.
- Did you verify that MAME analog is actually working by setting the "Inc" and "Dec" inputs to "none"?



XP has a gamepad test/calibration option in Control Panel -- Game Controllers.
- The KADE should show up in the Game Controllers window.
- Click on "properties" to bring up the test/calibration window.


Scott

[Ron_Michallick]

Scott,

Once again you solved my analog XY test problems. [Control Panel -- Game Controllers-- Properties] works on my Kade board and on my LWclone board. 
I have 3 boards in total. One has Kade, one has LWclone, and the last board is still in the original ESD bag.

I have only two tests that have issues.
1- LWclone LED control. Mamehooker test: "systray-test" and LWsend.exe (for the original LedWiz) won't turn on the RX or TX LED on the board.
2- Mame hooker doesn't see output events while running Spyhunt.zip ; My next test is to see if MameHooker see outputs in digdug.zip (per the instructions)

Once I solve these two issues, I can begin construction of the Spy Hunter cabinet. Not now; the garage is too hot to work in, probably Late October. 
I'll get my friend to 3-D print the four weapon indicators. (LED back lighting)

[PL1]

Glad to assist.   

2- Mame hooker doesn't see output events while running Spyhunt.zip ; My next test is to see if MameHooker see outputs in digdug.zip (per the instructions)

I'm just spitballing here, but this thread may have relevant info about enabling the MAME output system.   


Scott

[Ron_Michallick]

Update:

Scott's link is correct, in newer MAME.ini files look for 'OUTPUT' (not outputs) and change it to 'windows'. Now Mame Hooker will see Mame messages.
Led wiz clone by default is board #4 ; Luckily Led Blinky recognized the board #. Note: Mame hooker test commands crash when you use 4 as board number.
After some digging I found board ID in (LWclone2) descriptors.h file; look for #define USB_PRODUCT_ID to change board #, I changed to board #1
Now the Mame hooker test commands work well. They don't work in in the game ini files at all.
For led wiz clone (maybe original too) you should always use two characters for Board # and LED # otherwise it probably wont work.
'lws 1 01 %s%' doesn't work in ini file 'lws 01 1 %s%' does work, but so does 'lws 01 01 %s%' and promotes using two chars. I spent hours learning this.

All other changes for your needs should be made in pinmap.h file.
devconfig.h is useful to turn features on and off, like mouse or no mouse.