Howdy, my Kaimana has arrived along with the winter storm so it’s the perfect time for me to get knee deep in wiring/coding. I’m trying to affix the Kaimana Js to my Sanwas but I feel like they are a hair loose and will slip with gravity or a Final Atomic Buster motion. How’re you all securing your Kaimana Js?
The J’s are just a bit loose on the Sanwa’s, can’t press fit every micro 
I have been using a dab of hot glue. It’s almost invisible, can be removed and does the job.
I know people have used a small amount of hot glue for securing the J’s to their buttons.
@armi0024 @YellowCan Thanks guys, that helped me out.
In related news, I got the wiring completed and cleaned up plus got started on the coding. Some basic stuff, just getting the buttons working and divided the colors. Gonna work on animations next.
Looks really cool @Zensouken . I can’t wait until I get my Foehammer stick from PAS so I can start playing with this thing 
@Zensouken Amazing, I posted to Youtube
@iNENDOi, I need to stop getting in toys, the project just had fun little addition show up, but should ship by Friday. I’m trying to incorporate a new product we just received stock on!
So I’ve tried every combination of code I can think of with my very limited knowledge of Arduino and I can’t figure out how to make it so that when two buttons are pressed, those two specific LEDs light up a certain color. Right now I have my P1 button dark when idle and illuminating magenta when pressed. I want it to be so that when P1 and K1 are pressed at the same time, they both illuminate white.
This seems very simple but I keep running into a wall during execution. Any pointers?
Also has anyone figure out a simple flashing LED code when the button is held rather than pressed?
[details=Spoiler] // test switch and set LED based on result
if(!digitalRead(PIN_P1))
{
switchActivity |= ATTACK_P1;
// switch is active
if(iLED[LED_P1] == true)
{
//maintain color while switch is active
iLED[LED_P1] = true;
}
else
{
// select new color when switch is first activated
kaimana.setLED(LED_P1, MAGENTA);
iLED[LED_P1] = true;
}
}
else
{
// switch is inactive
kaimana.setLED(LED_P1, BLACK);
iLED[LED_P1] = false;
}[/details]
It is really hard to explain without just writing code so here’s something that should get you started in the right direction. This is a brute force method but it is often the best way to learn how something works and you can always optimize later.
I pulled the info from the paradise kaimana wiki page and have not tested the code so your mileage may, and probably will, vary.
// check switch P1
if(!digitalRead(PIN_P1))
{
kaimana.setLED(LED_P1, MAGENTA); // MAGENTA if pressed
}
else
{
kaimana.setLED(LED_P1, BLACK); // black if not pressed
}
// check switch K1
if(!digitalRead(PIN_K1))
{
kaimana.setLED(LED_K1, MAGENTA); // MAGENTA if pressed
}
else
{
kaimana.setLED(LED_K1, BLACK); // black if not pressed
}
// check if P1 + K1 and replace colors
if( (!digitalRead(PIN_P1)) && (!digitalRead(PIN_K1)) )
{
kaimana.setLED(LED_P1, WHITE); // replace color with WHITE if both pressed
kaimana.setLED(LED_K1, WHITE); // replace color with WHITE if both pressed
}
// send the new color values to the LEDs
kaimana.updateALL();
New to LED lighting, Kaimana J’s are the way to go from reading the thread. Can Pele’s be daisy chained to the Kaimana as well with the jumper harness?
Peles can’t be daisy chained by themselves, as they require an adapter board to be compatible with the Kaimana. However the adapters are daisy chain-able.
As long as you aren’t too pressed for space you should be fine with all of the boards in your stick.
Just as a precaution if you have PS-14-KNs you will want to go with Pele’s instead of Kaimana Js. They’re the only sanwa/ seimitsu button the Js aren’t compatible with. I am not sure if you already know but still good to put the info out there just in case.
Thanks for the info, I’ve search and found out what I need if using Pele’s vs to Kaimana J’s.
That part right there is what really helped me. The double ampersands got it working 99%. There was this weird flickering going on and and something about the interchanging of the inputs with the LEDs so I refined it a little and now it works correctly.
Here’s what I’m using now, it counts as an entirely separate entry so you’ll still need the regular code detecting single button presses.
// test switch and set LED based on result
if( (!digitalRead(PIN_P1)) && (!digitalRead(PIN_K1)) )
{
switchActivity |= ATTACK_P1 && ATTACK_K1;
// switch is active
if(iLED[LED_P1] && iLED[LED_K1] == true)
{
//maintain color while switch is active
iLED[LED_P1] = true;
iLED[LED_K1] = true;
}
else
{
// select new color when switch is first activated
kaimana.setLED(LED_P1, WHITE);
iLED[LED_P1] = true;
kaimana.setLED(LED_K1, WHITE);
iLED[LED_K1] = true;
}
}
else
{
// switch is inactive
kaimana.setLED(LED_P1, BLACK);
iLED[LED_P1] = false;
kaimana.setLED(LED_K1, BLACK);
iLED[LED_K1] = false;
}
@Zensouken you should check out the arduino reference page for the difference between logical and bitwise operators which appear to be causing you some confusion.
arduino.cc/en/Reference/HomePage
In your code below I changed the switchActivity assignment statement to get you the results you were looking for and hopefully resolve your last outstanding issues. You used a logical AND which is the double && operator for the switchActivity assignment. What you really wanted was the bitwise OR which is the single | operator. You could have also use a standard addition + operator to achieve the same results with the caveat that you only add each ATTACH_** value exactly one time and never more.
switchActivity |= ATTACK_P1 && ATTACK_K1; // incorrect, using logical AND operator
switchActivity |= ATTACK_P1 | ATTACK_K1; // correct: using bitwise OR operator
switchActivity |= ATTACK_P1 + ATTACK_K1; // correct: using addition + operator
// test switch and set LED based on result
if( (!digitalRead(PIN_P1)) && (!digitalRead(PIN_K1)) ) // logical AND is a double &&, bitwise AND is single &
{
switchActivity |= ATTACK_P1 | ATTACK_K1; // bitwise OR is a single |, logical OR is a double ||
// switch is active
if(iLED[LED_P1] && iLED[LED_K1] == true) // logical AND is a double &&, bitwise AND is single &
{
//maintain color while switch is active
iLED[LED_P1] = true;
iLED[LED_K1] = true;
}
else
{
// select new color when switch is first activated
kaimana.setLED(LED_P1, WHITE);
iLED[LED_P1] = true;
kaimana.setLED(LED_K1, WHITE);
iLED[LED_K1] = true;
}
}
else
{
// switch is inactive
kaimana.setLED(LED_P1, BLACK);
iLED[LED_P1] = false;
kaimana.setLED(LED_K1, BLACK);
iLED[LED_K1] = false;
}
@ZonbiPanda Thanks for the tip. I tried it as you said and there was not much of difference in the LED effect but what is happening now is that if I utilize the same kind of code for a combination of P1 and K1, P1 and P2, the P1 button tends not to maintain the effect. Like there’s an overlap of some sort. In that instance P1 and P2 will then change to the same color when pressed together but then P1 and K1 won’t share the same color. There’s a ghost in this machine here.
I was looking at @wahoo747 's code to dissect some sort of function to get the LED to strobe or flash while being held but it’s so specific for MAHVEL that I’m having trouble alienating what I’d like to use.
EDIT: http://youtu.be/NW9z2P96oyw
I have no idea why but on the 2P side, whenever any combination of 4 buttons from that side is pressed, they all light up. I have no idea why and I’m certain I haven’t programmed it in. Any thoughts, anyone?
@Zensouken it is really hard to speculate on what’s wrong if you wanted to share your complete source code I can take a look over the weekend and look for anything obviously out of place. There’s really not a lot to making the leds light up but the animations do require a little more thought when creating a new one from scratch. Expanding an existing animation should not be difficult once you get started.
You can always strip your code down to the bare basics to isolate your the problem on your own. If you have your main loop monitor just a single button and drive only one led with the brute force method, you can validate each of the switch input to led output mappings. After you have done this for all 10 of your switches you can start expanding your code to support the full left bank then center bank then right bank of buttons.
I honestly suspect it is something really simple like the logic vs. bitwise operators or even your #define statements in the kaimana_custom.h file have duplicate values. Verifying the kaimana_custom.h could be a good place to start if you are using the LED_XXX constants defined there.
// uncomment exactly one of the _LED_ORDER_*_ choices below or make your own
// based on the order you have your LEDs connected to the Kaimana board
//
#define _LED_ORDER_DEFAULT_ true
//#define _LED_ORDER_JWYDER_ true
#ifdef _LED_ORDER_DEFAULT_
// Map function names to default LED index numbers
// specific to ParadiseArcadeShop.com Kaimana board (PS360+LED)
// change or expand as needed
//
// KAIMANA->LED_JOY->LED_HOME->LED_SELECT->LED_START->LED_P1->LED-P2->LED_P3->LED-P4->LED_K1->LED-K2->LED_K3->LED-K4
//
#define LED_JOY 0
#define LED_HOME 1
#define LED_GUIDE 1
#define LED_SELECT 2
#define LED_BACK 2
#define LED_START 3
#define LED_P1 4
#define LED_P2 5
#define LED_P3 6
#define LED_P4 7
#define LED_K1 8
#define LED_K2 9
#define LED_K3 10
#define LED_K4 11
#endif
Finally, post a reply with the order in which your leds are connected. The factory default expects the order below but the constants in the code above can be changed to fit your specific installation. In fact, the example includes a second led mapping order that is used if you define the constant LED_ORDER_JWYDER . Either way, the LED order defined in the kaimana_custom.h must match your wiring.
// KAIMANA->LED_JOY->LED_HOME->LED_SELECT->LED_START->LED_P1->LED-P2->LED_P3->LED-P4->LED_K1->LED-K2->LED_K3->LED-K4
@ZonbiPanda Thanks for the insightful advice, I’m currently out knocking out some X-MAS shopping so when I get back I’ll post a link for my full code. But off the top of my head I do know my wiring input.
KAIMANA->LED_P1->LED_K1->LED_K2->LED_P2->LED_P3->LED_K3->LED_START->LED_SELECT->LED_DOWN->LED_UP->LED_RIGHT->LED_LEFT->LED_P4->LED_K4
@Zensouken do you have two kaimana boards installed?
If not, it appears you are using the stick inputs and P4/K4 for the second set of buttons and not wiring up an actual stick in the mix? It looks that way from your video + diagram.