wow… last week i would have never bothered with a joystick for any console, but after seeing this, i ordered an se stick and plan on re-wiring 2 jamma cabs for this.
my wife is going to hate me 
oooooohhhhhh…pretty things are afoot. different arc-eyes/KNserts, LED controllers… stick builders everywhere are going to have a lot more options real soon. Love it!
Toodles, do you have any more of the KNSerts? I’d love to try a set for a project I’m working on. I think Arc Eyes may be overkill on this one (though I’ll need a set for d3v’s and my son’s projects)
Well, the ones I have here at the moment don’t have any spots for resistors on them (the production ones being made do have an optional spot for resistor, but I dont know when they’ll be done). If you’re going to do an LED mod without the FGW LED controller, it would probably be cleaner with arceyes until the production KNserts are ready.
I see. I was considering the LED controller as well, but I haven’t quite figured our exactly what I’m doing with this project. If I go that route I’ll let you know.
Yes these are exciting times for stick builders I think many many people would love to see the tech talk geniuses try to work together on a LED controller. I kno I would 
Ok this is the last week before my soldering iron gets packed away for a while, for anyone who wants LED soldering service onto arc-eyes.
I can still ship out orders up until the end of the month!
/cry
ditto. Gotta order mine quick then XP
I"m in before the lock!
And the assembled ones are here and ready to go. Now I gotta figure out how to pack them.
I need some!
As soon as Chad tells me how many to put in each grab bag, I’ll have them sent off and up on LizardLick in short order.
So some people start to ask about me the difference between ARC EYEs and KInserts and it seems that there is some confusion. Perhaps it`s a good idea to create a own thread for the KNserts. I summarize in short:
ARC EYE advantages :
-
Available since february 2010 and sold about hundered of some. They`re well tested and there a lots of best practice sticks around. Goto joystick vault and view in the top 3 purpleamrs stick
-
ARC EYEs are available in my shop www.arcadeforge.de and purplearms in near future again. I can send some ready assembled ARC EYEs to purplearms to place them in the near to the states.
-
ARC EYEs have RGB LED. You can choose whatever color you want. KNserts only support one color.
-
ARC EYEs have ready assembled resistors. KNSerts seems to have no led resistors. So go for the ARC EYEs if you want to have ready to go fully assembled LED PCBs for your buttons without care about resistor values.
Here some videos from my own work with ARC EYE.
[media=youtube]FcFcpY6xRKk[/media]
[media=youtube]hh3sjGJmryM[/media]
[media=youtube]HaF5h63sgNA[/media]
[media=youtube]SvLECooUZUI[/media]
[media=youtube]O4uvZsu_d80[/media]
[media=youtube]oy9LjUzsZ10[/media]
So, have fun with the ARC EYEs ;))
Arceye Meets Sparky
- Open Source (Purplearms is not doing any more, but has happily provided Schema and Board files for adaptation and extendibility)
- Multiple Contributors
- Support for additional controllers (official and 3rd party)
a. Masterstrike
b. Sparky Jr (see below)
c. Custom
So, with that said, late last evening i received some PCBs and have assembled them!
The only one not in hand yet is the Sparky Jr
Ladies and Gentlemen - Sparky!
Sparky, Sparky Shield and Sparky Jr are RGB LED controllers.
- Both the Sparky and Sparky Jr feature FTDI headers for programming a user supplied ATMEGA328 chip
- All feature multiplexing for up to independently controlled 8 RGB LEDs
- Each Color is addressable via the RGB pin header and the common are supported via the headers labeled so. This version includes the addition of screw terminal for the RGB if desired.
- A unique feature is the jumper to support common anode. By default, the chipset / code are set for common cathode. the jumper provides a software level detection and switches accordingly
- Additionally a ‘remote’ reset via holes are provided for wiring to external pushbutton / momentary switch only on the Sparky Jr
- An Open Source Library supported by the CC community
- EEPROM for saving custom profile
- LED RGB designer interface
- Screw Terminals on Sparky Jr for RGB lines
Sparky Shield (Arduino Shield)
- Base Board
- Soldered Up
- In Action (Running Test Pattern)
[media=youtube]omm9hQyG2eM[/media]
Sparky
- Base Boards
- Soldered up
note: the Sparky board has separate wiring for each RGB LED, it can be used in your fightstick, but needs 24 wires (LOL), the footprint for the RGB LEDS is the standard footprint. But it still makes a great toy!
footprint: 1.30" x 2.34"
Sparky Jr (in the mail now)
Sparky Jr remedies the 24 wires nonsense of Sparky and trims that number to 11… …thats right 11. 8 for the common for each ArcEye and 3 for each color (Red, Green, Blue)
- The Boards (like i said, they are in the mail, but here is the BRD images)
and in good faith of the open source community and willingness to share these details… …voila!!!
http://www.fakesite.com/UPLOADS/SparkyJrMini001.png
http://www.fakesite.com/UPLOADS/SparkyJrMini002.png
http://www.fakesite.com/UPLOADS/SparkyJrMini003.png
http://www.fakesite.com/UPLOADS/SparkyJrMini004.png
http://www.fakesite.com/UPLOADS/SparkyJrMini005.png
footprint for Sparky Jr: 0.9" x 1.94"
If you would like the Source Files for the Sparky Jr project (Software = .cpp + .h files, Hardware = .brd and .sch files) please send me a PM and you can have SVN access
More details as soon as i get the Sparky Jr boards in hand.
Oh yeah!!
Megatron meets sparky… coming soon!
Good shit! made my evening! just bought a leo2, but i hope these are up for sale in 2 weeks when i get paid again
Im sorry for the onslaught of impending questions:
- So whas the sparky shield about?
- Will these play nice with wireless setups?
- I kno 8 buttons are supported. but what if i wanted to do the other 3 buttons (start, sel, home/guide) + joystick would need to add another sparky or combination of sparkies? would that be possible?
- who are some of the others working on / contributing on this project, besides yourself, purps, and ben?
- any idea of the cost per board are going to be?
- would it be safe to say that all the boards have most of the same functionality? with exception being sparky jr using 11 wires? featuring optional screw terminals and external reset?
- average cost of an ATMEGA328 chip?
- how will this interface with the masterstike board?
you can tell me to just stfu and wait for a proper faq / welcome document and i will kindly do so
Bonus question: 32teeth, been wanting to ask since i saw your flickr set but i keep forgetting. where can i get pin headers thingys similar to the ones you used for your custom harness and/or the ftdi header, not the swiss type. even some search engine friendly terms would be helpful. the scope of my project is already tremendous i want to make harnesses where i can to make life neater and easier.
sorry for so many questions but my short weekend is here and its only time i really have available to do research, notes, window shopping and questions 
Thank you and all that contributed to this project! Looks like an excellent toy for us to play with I can wait. BTW i really love the name sparky for this project. Its really catchy :tup:
Great News, I`m absolutley stunned!
Sparky Shield
Great addition for Arduino and for developers prototyping their firmware. Arduino has a big comunity and is very simple to use.
Sparky
Im wiring up each ARC_EYE with ribbon cables, to its great to have the between direct wiring and matrix wiring like in sparky jr.
Sparky Jr
Great design!
I was wondering about the current use of this friends and the maximum limlits of a AVR. The worst case of using all RGB led and all colors at the time is very unlikey, so for the use in Fight Sticks no led drivers are needed.
My input :
-
Arduino based development platform, makes prototyping much easier.
-
Sure, go with common ground setups like the leo for buttons input and make sure your batteries are full
-
Sure, another sparky will help. You`ve to consider more power use and take care about this cable twirling in led ball setups.
-
I`m quite sure that IvlePhisto is interested in this stuff. I ask him.
-
Does Sparky jr feature STerminals?
-
The MCU unporgrammed about 3? I guess.
-
MastserStrike could see the whole Sparky setup as LED1 device. Just wire the button inputs as described and wire then Sparky as LED1 Device. Then Masterstrike can switch on and of Sparky. BTW So far I didn’t feed the MasterStrike Boards to my cats
My questions :
Does the current fw fits to 168?
Thank you for kindly answering all my questions! So as i understand the shield then, its a board that i would plug into an already had audrino dev board to aid in programming of the chip, illustrating how the leds would look instead of directly plugging in to a led setup in an existing fightstick?
so the all of the said hardware is done, arrived or in transit, and what people are contributing is different snippets or entire sets code that will make our leds look rad. i am so excited about all this stuff. never realized that wanting to build my own kick ass stick lead me down so many different paths of enlightenment!
Ok,
I just started to port the Sparky FW to Dual Strike PCB. Dual Strike uses a external clock, so I have two pins less. Here`s the current pin mapping
int boards[][size][size] = {
/*Sparky*/
{{0,1,2,3,13,14,15,16},{19,18,17},{12,11,10,9,8,7,6,5},{4}},
/*Sparky Junior*/
{{15,14,13,12,11,10,9,8},{18,17,16},{0,1,2,3,4,5,6,7},{19}},
/*Sparky Shield*/
{{13,12,11,10,9,8,7,6},{2,3,5},{0,1,14,15,16,17,18,19},{4}},
/*Saprky Sanguino*/
{{0,1,2,3,4,5,6,7},{12,13,14},{15,16,17,18,19,20,21},{23}},
/*Dual Strike
Pin Mapping
output control common leg of RGB LED
HK (PC2, analog pin 2) -> P1
SELECT (PC1, analog pin 1) -> P2
START (PC0, analog pin 0) -> P3
MP (PB5, digital pin 13) -> P4
MK (PB4, digital pin 12) -> K1
LK (PB3, digital pin 11) -> K2
LP (PB2, digital pin 10) -> K3
S4 (PC6, reset) -> K4
output control rgb legs
HOME (PC5, analog pin 5) -> Red
4K (PC4, analog pin 4) -> Blue
4P (PC3, analog pin 3) -> Green
input control (pushbutton)
S3 (PD4, digital pin 4) -> P1
HP (PD5, digital pin 5) -> P2
S1 (PD0, digital pin 0) -> P3
S2 (PD3, digital pin 3) -> P4
UP (PD6, digital pin 6) -> K1
DW (PD7, digital pin 7) -> K2
LF (PB0, digital pin 8) -> K3
RG (PB1, digital pin 9) -> K4
input control for jumper read for common anode
Dual Strike does not have any pin left. Using a input here
RG (PB1, digital pin 9) -> K4
*/
{{16,15,14,13,12,11,10,reset},{19,18,17},{4,5,0,3,6,7,8,9},{9}},
};
First question : Is it possible to use the reset line as input?
Second question : no pin left for the common anode or cathode jumper. Sure, there`re some solution to avoid this. Can I just map one of the inputs as the jumper and the default is taken. I see the issue that the user changes the common setup by pressing a button on startup by accident.
Second the fw must be re-compiled to change the common setup, but this is not really an issue. Any ideas?
Short answer… …no.
i can look into a soft override
thoughts here are
/*
assume that reset is PIN 1;
Change the jumper to an out of range number, lets call it -1
*/
int reset = 1;
{16,15,14,13,12,11,10,reset},{19,18,17},{4,5,0,3,6,7,8,9},{-1}}
/*
you now have your extra pin available (in this case PIN #2 is not used yet)
*/
Lastly
The jumper pin is a 2 pin male header with a jumper, not a button the user can solder a contact to. it is out of the way from the 8 input on purpose.