Kade Loader v1.1.2.0 Windows Binary

[netquik]

Hi all!
I'm trying to have the last windows binary for Kade Loader v1.1.2.0.
Anyone has this file or has managed to compile it from available source?
https://github.com/kadevice/KADE/tree/master/open%20software/loader
I tried with no luck.

Thanks

[PL1]

I'm trying to have the last windows binary for Kade Loader v1.1.2.0.
Anyone has this file or has managed to compile it from available source?

How about the last beta version v1.1.3.1?

https://web.archive.org/web/20160310031802/http://kadevice.com/loader/setup.zip


Scott

[netquik]

How about the last beta version v1.1.3.1?

Many thanks yes i got it!
i didn't think about using internet cache.
Many thanks.

Regarding a Minimus AVR like board i was using in my project years ago, i have another question/doubt related to Kade.
I would like to use an external LED to identify the using mode on the board.

Are there any details/suggestions or guide to have that implemented?

Thanks again

[PL1]

Glad to assist.   

Regarding a Minimus AVR like board i was using in my project years ago, i have another question/doubt related to Kade.
I would like to use an external LED to identify the using mode on the board.

Are there any details/suggestions or guide to have that implemented?

I'm guessing that you're referring to the "MAME (1 Player Multi-Mode)" firmware, right?

In that firmware the HWB input cycles the board through the four possible modes P1, P2, P3, and P4.
- If you connect an external LED to terminal B10, it will flash to indicate the current mode.
- P1 mode = 1 flash, P2 mode = 2 flashes . . .

Connecting an LED to terminal B10 is just like connecting an LED to any other 5v source.

    B10 ---- current limiting resistor ---- LED ---- ground

If you know the voltage and current specs for the LED, you can calculate the proper value resistor using an LED calculator like the one at https://ledcalculator.net/.

LED buttons that use an LED holder like this yellow one have a current limiting resistor hidden in the socket.




Scott

[netquik]

Thanks thanks thanks.
Perfect answer to my doubts! 
Yes i was referring to B10 that i see is also customizable for USB/HID Joystick Encoder (Custom) to external led.
In this case i'm not sure what it does on shifting.

I'm actually looking for a mapping that can be used for (with switch):

1. two players C64/amiga games (1 fire button) + helper keys (emu menus)
2. one player for MAME

but i don't think is possible
so probably the best option is using mame 1 player multi-mode and leave the idea of connecting two different sticks

thanks again

[PL1]

Yes i was referring to B10 that i see is also customizable for USB/HID Joystick Encoder (Custom) to external led.
In this case i'm not sure what it does on shifting.

It lights in the two situations when the encoder is going to output shifted functions.
  1. When you press HWB.
  2. When you activate the shift-lock by double-clicking HWB.

I'm actually looking for a mapping that can be used for (with switch):

1. two players C64/amiga games (1 fire button) + helper keys (emu menus)
2. one player for MAME

but i don't think is possible
so probably the best option is using mame 1 player multi-mode and leave the idea of connecting two different sticks

Pretty sure you can do that using the MAME Encoder (Custom) firmware and a rocker or toggle switch on HWB to switch between the MAME and C64/Amiga keystrokes -- one set normal and the other set shifted.

If you want an LED, you should be able to wire it like this with both the LED cathode (-) and the output of the switch connected to the HWB input.

  5v ---- current limiting resistor ---- LED ---- HWB input
                                                                |
  ground ----------- switch -----------------|

When the switch is open HWB input is high (ground is not applied), the LED is off, and you get normal keystrokes.

When the switch is closed HWB input is low (ground is applied), the LED is on, and you get shifted keystrokes.


Scott

[netquik]

It lights in the two situations when the encoder is going to output shifted functions.
  1. When you press HWB.
  2. When you activate the shift-lock by double-clicking HWB.

Thanks i will need to do some tests.
I'm actually put my hands on an old board (maximus like) i designed.
I see HWB switch (on board... EVQ-Q2U03W) shorts GND to PD7.
The result i want to target is having 2 leds that indicate the MODE in use.
but they should keep light.

Pretty sure you can do that using the MAME Encoder (Custom) firmware and a rocker or toggle switch on HWB to switch between the MAME and C64/Amiga keystrokes -- one set normal and the other set shifted.
If you want an LED, you should be able to wire it like this with both the LED cathode (-) and the output of the switch connected to the HWB input.

  5v ---- current limiting resistor ---- LED ---- HWB input
                                                                |
  ground ----------- switch -----------------|

When the switch is open HWB input is high (ground is not applied), the LED is off, and you get normal keystrokes.

When the switch is closed HWB input is low (ground is applied), the LED is on, and you get shifted keystrokes.

For MAME Encoder (Custom) firmware i don't see the possibility to set external Led in the mapping.
Also the problem with this solution is that it will work for a sigle device.
I mean mapping mode for MAME should target Player1 always so if i connect a second alike device it should target the same player.
I think the only real solution is to reprogram the device when need switching between Mame 1P multimode and Mame 2P multimode (pretty annoying)
I explain why i have this problem:
I want to reuse old/retrosticks (C64) and give the possibility to connect them directly to my device (that has avr and additionl buttons for mame)
Ideally i want to have two connectors on single device so that 2 players that want to play C64 games can play together attaching their stick to a single device.
That said i would like obviously to use 1 stick attached and full MAME buttons supports using the device.
Just trying to find the best solution to get near this idea.

Many thanks

[netquik]

Just trying to find the best solution to get near this idea.

the best should have a new firmware based on MAME 1P multimode that have 3 modes for 3 players and last 4 splitted to have C64 2 players layout.
unfortunately this mode can't be customized

Edit:
If anyone is able to create such a firmware please let me know. Thanks

[PL1]

I want to reuse old/retrosticks (C64) and give the possibility to connect them directly to my device (that has avr and additionl buttons for mame)
Ideally i want to have two connectors on single device so that 2 players that want to play C64 games can play together attaching their stick to a single device.

That's easy.   

Wire the C64 controller connector inputs in parallel with the corresponding MAME control inputs.

Configure your C64 emulator and MAME to use the same keys for those inputs.

For MAME Encoder (Custom) firmware i don't see the possibility to set external Led in the mapping.

The approach I suggested is a purely hardware solution, not a firmware configuration solution.
- There is no need to set an external LED in the firmware mapping.

I'm actually put my hands on an old board (maximus like) i designed.

So . . . you want to use a different board than the ones in the pulldown menu in Loader?

Good luck with that.   

The result i want to target is having 2 leds that indicate the MODE in use.
but they should keep light.

You'll have to rewrite the firmware to support 2 LEDs.

---------------------------

Sounds like your expectations are WAY out of alignment with what the KADE Loader and firmwares can do without substantial changes to the source code and compiling and troubleshooting a custom version of Loader.

Off the top of my head, I can't think of any one encoder with all of the features you're asking for.

Let's take a few steps back here.

The best approach is to start with what you want to accomplish instead of starting with an encoder that can't do what you are trying to do until someone else does some major rewrites.

The first step in choosing the right encoder(s) is to clearly and fully define what you want to do with which controls and what features you want/need.
- An incomplete or unclear list of info and desired features for a specialized use-case like you describe will always lead to bad advice and wasted time.   
- Do you want a keyboard encoder or gamepad encoder?
- How many joysticks, player buttons, and admin buttons?  Panel layout?
- Special features? (plug in C64 controllers for P1 and P2)
- Can you configure your C64 emulator and MAME to use the same keys so you can wire the external controller connectors in parallel with the MAME joystick?


Scott
P.S.  Check out the design process in the What type of build meets my needs? entry in the FAQ.  It will help you work through the important questions about your build in a logical, organized way.

[netquik]

First of all I would like to apologize for causing confusion and not being clear about my project (mainly due to my bad English).

Wire the C64 controller connector inputs in parallel with the corresponding MAME control inputs.

Yes exactly what i'm doing 
But before doing it in the prototype I am in this phase evaluating the possible options using Kade Loader

The approach I suggested is a purely hardware solution, not a firmware configuration solution.
- There is no need to set an external LED in the firmware mapping.

You'll have to rewrite the firmware to support 2 LEDs.

Yes i understood. Also i will lose 1 usefull pin. Just still evaluating all options for LEDs. Thanks

So . . . you want to use a different board than the ones in the pulldown menu in Loader?
Good luck with that.   

No. It is not the case. Let's assume I'm using a classic "Minimus AVR".
I had mentioned a new board because I simply redesigned the pcb for other reasons, keeping the same schematic and pinout.
We are talking about an ATmega32U2 board.
I apologize for not being clear about this

Sounds like your expectations are WAY out of alignment with what the KADE Loader and firmwares can do without substantial changes to the source code and compiling and troubleshooting a custom version of Loader. Off the top of my head, I can't think of any one encoder with all of the features you're asking for.

I am confident I can use Kade Loader for my purposes but I am trying to understand the various possibilities before making the prototype.

- Do you want a keyboard encoder or gamepad encoder?
- How many joysticks, player buttons, and admin buttons?  Panel layout?
- Special features? (plug in C64 controllers for P1 and P2)
- Can you configure your C64 emulator and MAME to use the same keys so you can wire the external controller connectors in parallel with the MAME joystick?

As said I will be using a Minimus AVR. Considering the use for MAME I will use the keyboard function.
The layout is still under development but will have six buttons + coin + start to which the stick (C64) will be added.
These are actually not important things as you said i can find a shared configure for these problems.


Now my last request in the previous post was related to the possibility of creating a custom firmware based on MAME 1p multimode.
If it were possible I would have solved all the problems.
 I was able to find the 1.0.2.0 setup related to the source on github. This is why I was trying to compile the source.

Unfortunately there are many things that are not clear to me about Kade Loader and not having the source of this latest beta version confuses me even more. However looking at the code it seems to me that the firmware is independent from the basic function of the executable. Now looking at the sources of the firmwares it seems to me quite easy to be able to modify the source of the MAME P1 multimode by changing the mapping to what I want.

https://github.com/kadevice/KADE/tree/master/open%20software/firmwares/KADE%20miniArcade/sources


Let's say that I would like to have this hex but with a different mode4 (specifically the same as the mode 1 of the MAME 2P profile)
This should be the new mappings.c

Code: [Select]

/*
DEGENATRONS ARCADE ENCODER: Configurable 20 Input Keyboard Encoder
https://sites.google.com/site/degenatrons/
In the arrays, 0-9 is A1-A10 and 10-19 is B1-B10
*/

//----------------------------------------------------------------------------
//Mode 1: Player 1 MAME Compatible
//----------------------------------------------------------------------------
void A1(void)
{
  map[0]  = KEY_5;
  map[1]  = KEY_1;
  map[2]  = KEY_RIGHT;
  map[3]  = KEY_LEFT;
  map[4]  = KEY_UP;
  map[5]  = KEY_DOWN;
  map[6]  = KEY_LEFT_CTRL;
  map[7]  = KEY_LEFT_ALT;
  map[8]  = KEY_SPACE;
  map[9]  = KEY_LEFT_SHIFT;
  map[10] = KEY_Z;
  map[11] = KEY_X;
  map[12] = KEY_C;
  map[13] = KEY_V;
  map[14] = KEY_ENTER;
  map[15] = KEY_P;
  map[16] = KEY_F7;
  map[17] = KEY_TAB;
  map[18] = KEY_ESC;
  map[19] = KEY_NONE;
}

//----------------------------------------------------------------------------
//Mode 2: Player 2 MAME Compatible
//----------------------------------------------------------------------------
void A2(void)
{
  map[0]  = KEY_6;
  map[1]  = KEY_2;
  map[2]  = KEY_G;
  map[3]  = KEY_D;
  map[4]  = KEY_R;
  map[5]  = KEY_F;
  map[6]  = KEY_A;
  map[7]  = KEY_S;
  map[8]  = KEY_Q;
  map[9]  = KEY_W;
  map[10] = KEY_I;
  map[11] = KEY_K;
  map[12] = KEY_J;
  map[13] = KEY_L;
  map[14] = KEY_ENTER;
  map[15] = KEY_P;
  map[16] = KEY_F7;
  map[17] = KEY_TAB;
  map[18] = KEY_ESC;
  map[19] = KEY_NONE;
}
//----------------------------------------------------------------------------
//Mode 3: Player 3 MAME Compatible
//----------------------------------------------------------------------------
void A3(void)
{
  map[0]  = KEY_7;
  map[1]  = KEY_3;
  map[2]  = KEY_END;
  map[3]  = KEY_HOME;
  map[4]  = KEY_PAGE_UP;
  map[5]  = KEY_PAGE_DOWN;
  map[6]  = KEY_RIGHT_CTRL;
  map[7]  = KEY_RIGHT_SHIFT;
  map[8]  = KEY_ENTER;
  map[9]  = KEY_SLASH;
  map[10] = KEY_PERIOD;
  map[11] = KEY_COMMA;
  map[12] = KEY_NONE;
  map[13] = KEY_NONE;
  map[14] = KEY_ENTER;
  map[15] = KEY_P;
  map[16] = KEY_F7;
  map[17] = KEY_TAB;
  map[18] = KEY_ESC;
  map[19] = KEY_NONE;
}


//----------------------------------------------------------------------------
//Mode 4: 2 Players C64
//----------------------------------------------------------------------------
void A4(void)
{
  map[0]  = KEY_5;
  map[1]  = KEY_1;
  map[2]  = KEY_RIGHT;
  map[3]  = KEY_LEFT;
  map[4]  = KEY_UP;
  map[5]  = KEY_DOWN;
  map[6]  = KEY_LEFT_CTRL;
  map[7]  = KEY_LEFT_ALT;
  map[8]  = KEY_SPACE;
  map[9]  = KEY_ENTER;
  map[10]  = KEY_6;
  map[11] = KEY_2;
  map[12] = KEY_G;
  map[13] = KEY_D;
  map[14] = KEY_R;
  map[15] = KEY_F;
  map[16] = KEY_A;
  map[17] = KEY_S;
  map[18] = KEY_Q;
  map[19] = KEY_ESC;
} 

so i'm just trying to understand if making an HEX from this (MAME 1P modded on mappings) and loading it on KADE could do the job.

Many thanks and sorry for everything 

[PL1]

First of all I would like to apologize for causing confusion and not being clear about my project (mainly due to my bad English).

No worries.   

So . . . you want to use a different board than the ones in the pulldown menu in Loader?
Good luck with that.   

No. It is not the case. Let's assume I'm using a classic "Minimus AVR".
I had mentioned a new board because I simply redesigned the pcb for other reasons, keeping the same schematic and pinout.
We are talking about an ATmega32U2 board.

The reason I asked is that if I recall correctly, the Minimus AVR has a unique ID and bootloader and the Loader program won't work with any board that does not have the correct combination of ID and bootloader for one of the boards listed in the pulldown menu.

If the Loader program recognizes your redesigned PCB as a Minimus AVR and can upload one of the default firmwares to the board, you should be able to modify the source like you mention and recompile a custom version.

If Loader doesn't recognize your redesigned PCB as a Minimus, it might be easier to translate the KADE code into an Arduino sketch.   


Scott

[netquik]

The reason I asked is that if I recall correctly, the Minimus AVR has a unique ID and bootloader and the Loader program won't work with any board that does not have the correct combination of ID and bootloader for one of the boards listed in the pulldown menu.

If the Loader program recognizes your redesigned PCB as a Minimus AVR and can upload one of the default firmwares to the board, you should be able to modify the source like you mention and recompile a custom version.

Well I've not read about that. But i can say that i use a Noogroove board for tests and it seems to work as expected. I will update with further details when i'm ready.
the pull-down menu shows the processor ... as long as i understand any breakout (usb) for those chips should work.
Anyway currently i need to to understand the feasibility of having a firmware as described in the previous post.
A MODDED CUSTOMIZED VERSION OF MAME 1P PROFILE
i'm going to have a look to winavr.
Any help or suggestions to have the possibility to burn a firmware as per code in my previous post is much appreciated.
A thousand thanks

[netquik]

UPDATE

I think i managed to compile the custom HEX with my mod mappings.
I will test this asap. No way to "see" the mappings in the loader.
WINAVR gave me some troubles but what make me think is this:

Code: [Select]

# MCU name, you MUST set this to match the board you are using
# type "make clean" after changing this, so all files will be rebuilt
#
# NOTE - Stuff compiled for 16k will work on both!!
MCU = at90usb162       # Minimus AVR 16K
#MCU = atmega32u2       # Minimus AVR 32k

well i tried changing to atmega32u2 bu WINAVR gave me error because seems not recognizing atmega32u2 for Power Reduction Register
changing back to at90usb162 compiled correctly. 

think that WinAVR is too old or something like that