Thanks Spenz I will make sure I hide my ftdi breakouts ;p
I picked up the basic breakout one, holy jeez they are tiny, definitely gonna lose that one. Thank god for the mint tin it makes a good storage device
Yep. the breakout board I had was roughly the same size as Gum’s SMD TE strike, so it was super tiny. I’ve got no idea where it went. So, I"ll just add it to the list of things to get at Sparkfun this week…
The color config on the website wasn’t updated to take advantage of the single button colors that you added. Is that coming before or after your little one? If it’s in the updated code so be it; I can make the change once I get the boards
Code Base update.
Hey all, if you are using an FTDI to program / reprogram your Sparky, i strongly urge you to do an update to your firmware.
See the firmware modding section in the how to of the saprky site
If you are pleased with your current config. So be it.
Spenzalii
You are correct. The codebase for this enabler is sitting in the Beta folder of the Arduino Files SVN repo. You can get it from there.
The big change was the pattern definition in the Config. (disregard the hex schema i have)
Release - SparkyConfig.pde
char* pattern[12] = {
"66FFFF",// 1x punch
"6699FF",// 2x punch (ex with punch buttons SFIV & SSFIV)
"6666FF",// 3x punch (ultra with punch buttons SFIV & SSFIV)
"6666FF",// 4x punch
"FF6600",// 1x kick
"FF6600",// 2x kick (ex with kick buttons SFIV & SSFIV)
"FF3300",// 3x kick (ultra with kick buttons SFIV & SSFIV)
"FF0000 ",// 4x kick
"66FF00",// P1 + K1 (throw SFIV & SSFIV)
"669900",// P2 + K2 (focus SFIV & SSFIV)
"669900",// P3 + K3 (taunt SFIV & SSFIV)
"660099" // P4 + K4
};
Beta - SparkyConfig.pde
char* pattern[18] = {
"00FFFF", // P1
"FF00FF", // P2
"FF0000", // P3
"00FF00", // P4
"00FFFF", // K1
"FF00FF", // K2
"FF0000", // K3
"00FF00", // K4
"0000FF", // 2x P
"FFFF00", // 3x P
"FFFFFF", // 4x P
"0000FF", // 2x K
"FFFF00", // 3x K
"FFFFFF", // 4x K
"FF0033",// P1 + K1 (throw SFIV & SSFIV)
"0000FF",// P2 + K2 (focus SFIV & SSFIV)
"00FF00",// P3 + K3 (taunt SFIV & SSFIV)
"FF0000" // P4 + K4
};
There are some overhauls in the .CPP file as well, but i won’t bore you with that. LOL
Everything you need to start plugging away is in the Beta folder.
The reason it’s not in the purchasing is that the Software Configurator has not been updated yet.
I need to get all these things in order before Round 2 pops out!
Soon though, soon.
What exactly do you need help with during your baby break? Id be down to help out.
I would say for the most part being patient with me LOL as I may suffer severe latency and you may experience some lag.
Jokes aside, maybe someone who may be interested:
- Hardware support
- software support
- Distribution & Assembly (will require SMD soldering chops)
- Community support
- Anything to keep the pace and cadence of the project efforts
I may be able to do some assembly ans distro. Possibly hardware support. FIgure if I can solder arc eyes I shoudl be able to do this. HIt me up
Is that both headers and screw terminals?
ha, i recently replaced my USB BUB (i fried it on another project) with the FTDI Basic Breakout from SparkFun. It’s faster than the USB bub.
it’s so small, i may just sink it into a few projects
congrats on the new challenger 32teeth i havent posted in a min, but i am still lurking around, just been really busy leveling up my modelling skills…anyways i may not be able to help with of the physical aspects because of the distance, but i can def help out any other way, just let me kno and we’ll make it happen!
@ butteroj, looks very nice with the programmer added, im looking to do something similar with mine, and use a switch for the various usb lanes and a rj45
question. will there be any implementation of this pcb supporting leds stick signals? meaning if i have a led bubble top.
^ interested to know this too
sorry for the noob question but about the usb, for the FTDI, can I use it without opening my arcade stick ? (I’m planning on chthulhu+IMP+Sparky PWM) or should I use Bluetooth instead of usb ? cheapest was to use BT?(component from sparkfun I mean)
thanks again!
Maybe one day. @purplearms has a laundry list for me LOL
For bluetooth, your would need both having transceivers, i don’t have much experience with BT though.
All that being said, let’s get back to the laundry list and what is now available in the Beta folders for both Processing and Arduino in the Sparky SVN.
- the singletons implementation is in the svn.
a) upload the new code to your Sparky from the Arduino / Beta Folder
b) run the Sparky.pde from the Processing / Beta Folder - what you will now see
a) multi / combo button controls

b) single button controls

The above pics only illustrate the usage for the PWM board, but the multi / single controls are available to the regular Sparky as well.
Also, further to @purplearms laundry list, there is an off switch now on boot.
Plug in your stick, it will go through the kick colors (red, yellow, green), when it starts, press and hold P4 (8 button config) until ALL the buttons flash WHITE. Your ArcEyes will now be turned off.
So whats up next for development?
- Potential of adding an FTDI chip on board so that you will only need a usb cable to interface with the Sparky. (this version will be slightly more expensive, but not as much as a Sparky + an FTDI breakout)
- more software updates.
getting this guy. since i lost my last board, i will just stick with this cable
FTDI Cable 5V - SparkFun Electronics
Sneek Peek!

Although the board is designed, i am still fully supporting the current PWM build.
For the FTDI version (Q3 2011) i have a lot to think about costing and assembly.
That would definitely be an all in one solution. While I’m sure more people would want inputs for lighted joysticks, an integrated ftdi is much more practical and easier on the end user. I’m loving it
@purplearms - yes the secondary headers will be there
@spenzalii - it’s going through design iterations and now, looking at including joystick directionals and guide/select/start as well, that’s 7 more pins.
right after i purchased my 4 boards…nooooooooooooo 32teeth lol. owell. maybe i can use them for future clients and shell out when these are available for project mewlix -whispers-
He did say no sooner than Q3, which is half a year from now… lol
Oh man, a built in FTDI chip would be splendid.
Now, if you could then get everything put onto a TEasy Strike…