First saber build! Graflex 2.0 (ESB) w/CF9

Gregatron

Master Member
Greetings! This is my very first FX saber build. I’ve done a good number of static props, over the years, but I decided to finally jump into the deep end and build a proper FX saber. East Coast Sabers’ “How to Build a Graflex” tutorial series was both an inspiration and an invaluable learning tool, but those videos feature a Nano Biscotte install, not a Crystal Focus, so I can’t just follow along with that tutorial step-by-step. I chose CF because of its flexibility, its motion sensitivity, and its sound bank capacity. I intend this to be a fairly simple build, though.

Anyway, I acquired a Graflex 2.0 and various parts from WannaWanga, The Graflex Shop, and KR sabers to accurize it. I’ve finished the bulk of the prep work with the inner core, but I got a little overeager, and my first attempt at installing the electronics went wrong, somehow. I had a CF8 board, and soldered it to the TCSS 7.4v 18650 battery, but something went wrong. When I tried to charge the battery, the battery charger light turned green as soon as I plugged it in, with no functionality whatsoever in the board. I’m not sure what went wrong. I also made the stupid mistakes of epoxying the recharge port (which I didn’t realize was designed to screw into place until later) into my Goth3D chassis (Padawan Graflex 2.0 model), and soldering the wires onto the CF board from the wrong side, initially, with the result being that the board sat upside-down on the chassis, and so the chassis wouldn’t slide into the Graflex’s bottom half, because the SD slot was obstructing things.

I also think I may have somehow damaged the board, in desoldering then resoldering the wires on the correct (bottom) side. After totally freaking out, I bit the bullet, and got a new 3D-printed chassis, speaker, and recharge port, as well as upgrading to a CF9 board. I’ll deal with the old CF8 board at a later date, and maybe another build. I’m still not sure what the deal was with my first attempt—why the charger indicated a full battery, or what went wrong. My multimeter wasn’t much help, since the speaker and recharge port were already permanently in place. LESSON ONE: Don’t install until you’re sure everything works!


I’m by no means an electronics expert, but I have basic knowledge and experience with soldering. I just went too far too fast, and made a mistake somewhere. I’d appreciate the help of the learned people in this form to help me avoid any further mistakes. In theory, this build is in the final stages, but I’m going slowly (and now taking the step of joining this forum to have feedback from the experts). As it stands, I have the LED module (Tri-Cree BBW) wired up, as well as some 5ohm/5w resistors ready to go. I presume that my resistor calculations are correct (the Blue LEDs are rated at a forward voltage of 1000ma at 3.4v, and the White at 1000ma at 3.15v). That would require one resistor for each LED at 4.7ohms/4.7w, yes?


I do have a question about CF9’s FoC feature. If I read the manual right, it seems that a resistor would be required for the white LED die. However, research indicates that a resistor might not be necessary, given that the FoC LED would only be in operation for short bursts at a time. And, according to the manual, the board has a footprint for a 2512/2W resistor. Should I go to the trouble of adding such a resistor to the board, or adding a resistor at all?


Also, I’m still deciding on whether to have a clamp card aux switch, or a red button aux switch. My activation will be in the clamp, but it would be nice to have dual aux switches—one in the clamp, and one in the red button. Is that doable? Or will I have to choose one or the other? My research hasn’t clearly indicated if the board can be wired with two aux buttons or not.


Any advice or warning about potential pitfalls would be appreciated! Thanks in advance.

Here’s where the build stands. A heavy static replica (still temporarily sporting the stock clamp card), without its beating CF heart! More photos as I make progress.

8611AD2D-D222-4FEA-8047-690460E470FE.jpeg

8611AD2D-D222-4FEA-8047-690460E470FE.jpeg
 
Last edited by a moderator:
Sounds like you have really done your homework!

It is looking great!

Cf9 is top of the line!!

I too have heard people say you don’t have to put a resistor on the white, but I don’t think it would hurt to throw one on there anyway

I am by no means a expert, and only repeating what I have read on here and therebelarmory.com

I’m doing a graflex 2.5 right now for a friend. He wants activation in the clamp and the red button, aux on the clamp

I’ve been told to just wire in the extra button on the same pad as the aux/activation (which ever one you choose you want double points of access)

Keep us posted and be sure to make a video of this sucker in action!!
 
It’s proven a lot easier than I expected, by and large. Just a hiccup or two, and the nagging fear that I’ll make a major boo-boo. The trick is going for 80%, 20% actual work. Watching lots of videos, reading lots of build threads. If and when I get this done, I hope that others will see that it doesn’t have to be so intimidating.
 
This build is all but finished. I’m just tweaking the sound configurations. One question, though—for some reason, both the font sound and then the boot sound both play after I select a soundfont from the sound bank. When I was first experimenting with the stock CF9 soundfonts, that wasn’t the case. Any thoughts on why the board is now suddenly doing that, and how to fix it?
 
This build is all but finished. I’m just tweaking the sound configurations. One question, though—for some reason, both the font sound and then the boot sound both play after I select a soundfont from the sound bank. When I was first experimenting with the stock CF9 soundfonts, that wasn’t the case. Any thoughts on why the board is now suddenly doing that, and how to fix it?

When you added the new files into the SD card did you fallow all instructions and format the card before putting new files on?


Sent from my iPhone using Tapatalk
 
I’d initially forgotten to format the card, but did so after my initial addition of new soundfonts.

I’m still a little confused, I would start over. Download the fonts again, format the card, install fonts

Give it a go


Sent from my iPhone using Tapatalk
 
Sorry for not being clear. When I cycle through the sound banks, each font sound (font.wav) plays when the aux button is pressed so as to provide the soundfont selections. So far, so good. When a particular font is selected by holding down the aux button, the font sound plays again to confirm it, but THEN the boot sound (boot.wav) plays immediately after the font sound. I was under the impression that only the font (font.wav) sound is supposed to play when a font is selected. It seems a bit redundant for the soundboard to play two distinct identifying sounds in a row after a font selection, but maybe I’m wrong.

I formatted the SD card, and reinstalled all of the original fonts and configurations which came with the SD card, and it does the same thing. Come to think of it, I seem to recall it doing so when I first tested the saber with the stock soundfonts. I dunno if this is normal, or if there’s some issue I’m overlooking. Anyway, I then reinstalled all of my custom work. Getting closer to properly adjusting the many, many parameters to suit my fancy. It’s tedious work, but I’m making progress.
 
This thread is more than 5 years old.

Your message may be considered spam for the following reasons:

  1. This thread hasn't been active in some time. A new post in this thread might not contribute constructively to this discussion after so long.
If you wish to reply despite these issues, check the box below before replying.
Be aware that malicious compliance may result in more severe penalties.
Back
Top