|
|
Post by hexlee on Nov 1, 2018 10:44:21 GMT -5
Is it possible for Proffie to use a slider switch for that sliding side bladeholder part of the graflex?
If so, what would I put that as in the configurater??
Thanks
Hex
|
|
|
|
Post by megtoothsith on Nov 1, 2018 11:22:55 GMT -5
Is it possible for Proffie to use a slider switch for that sliding side bladeholder part of the graflex?
If so, what would I put that as in the configurater??
Thanks
Hex
Most people use a momentary switch in the "slide" switch location on graflex replicas. The "slide" refers to the actuator on the outside which slides back and forth, but most installers actually use a momentary switch on their chassis, and the "slide switch" either has a plunger on it, or the switch is a plunger switch that makes contact. |
|
|
|
Post by hexlee on Nov 1, 2018 11:42:11 GMT -5
Is it possible for Proffie to use a slider switch for that sliding side bladeholder part of the graflex?
If so, what would I put that as in the configurater??
Thanks
Hex
Most people use a momentary switch in the "slide" switch location on graflex replicas. The "slide" refers to the actuator on the outside which slides back and forth, but most installers actually use a momentary switch on their chassis, and the "slide switch" either has a plunger on it, or the switch is a plunger switch that makes contact. Ok, I think I saw a KR sabers tutorial for that using magnets. I was also thinking of using a slider on/off switch inside, on the chassis instead of a kill Key because the goth padawan chassis seems to have a space for one. Is this an ok idea in your opinion? |
|
|
|
Post by megtoothsith on Nov 1, 2018 11:56:56 GMT -5
If you're on facebook, Graflex Addicts Support Group. Here on TRA, look at the build threads. I know Scarecrow just finished a TGS build with slider. On/off slider in Goth's chassis will work fine. Right now, both TeensySaber and Proffie really need a kill key, on/off switch, or battery removal until Fredrik gets a breather and a chance to begin working on deep sleep. He is pretty building/shipping Proffies right now, and answering all of these Proffie support questions, which is what this thread is for. For basic hilt building/wiring questions there are several other threads available outside of Profezzorn's section for that. So, no additional coding needed for either application of your build.  |
|
|
|
Post by hexlee on Nov 1, 2018 12:08:36 GMT -5
If you're on facebook, Graflex Addicts Support Group. Here on TRA, look at the build threads. I know Scarecrow just finished a TGS build with slider. On/off slider in Goth's chassis will work fine. Right now, both TeensySaber and Proffie really need a kill key, on/off switch, or battery removal until Fredrik gets a breather and a chance to begin working on deep sleep. He is pretty building/shipping Proffies right now, and answering all of these Proffie support questions, which is what this thread is for. For basic hilt building/wiring questions there are several other threads available outside of Profezzorn's section for that. So, no additional coding needed for either application of your build. Thats great.. Thanks for all your help.
P.s I bought a Meg tooth in Edinburgh last year.. been after one for years.. amazing things right!
I always wanted to try diving for them in Carolina one day, though it sounds quite dangerous at times..  |
|
|
|
Post by profezzorn on Nov 1, 2018 15:49:50 GMT -5
Hi Frederick,
I finally managed to upload the program to the board.
I just have a question about the configurator options. I want to be sure ive chosen the right options for the blade.
What I want is a 2 strip neopixel blade with a rotary style pbc connector.
Do I choose the blade connector and the dual neopixel?
Thanks for all your help
Hex
No, you don’t want to pick dual or blade connector. Just pick single blade because: - Both strips of the blade act as one. They are wired together and display the same effects. Dual in the configurator refers to a staff style dual-bladed saber. - the blade connector in the configurator refers to an 8-pin gx-16 avitation connector, which can be wired to allow the Proffie to ID and use different blades. Using the rotary PCB doesn’t allow for that function, so skip the connector part of the configuration. sa22c is right, but if you like you can choose two (dual) blades, which gives you individual control over the two blades, which can be nice for having different colors. |
|
|
|
Post by profezzorn on Nov 1, 2018 15:52:23 GMT -5
Is it possible for Proffie to use a slider switch for that sliding side bladeholder part of the graflex?
If so, what would I put that as in the configurater??
Thanks
Hex
Right now, toggling switches are only supported for power on/off. It wouldn't be too difficult to add some code to use them for other functionality, but it's not there yet. |
|
|
|
Post by hdjoe22 on Nov 1, 2018 20:15:04 GMT -5
I got it cleared of errors thanks to Tom. It checks fine and uploads.
The new issue is now it seems to skip my changes completely. Does not play soundfont I have on the sd card, nor the blade style attached to it. It also does not seem to recognize that I changed a track on a teensy soundfont either. Like it’s only seeing the stock config from the site.
Am I supposed to add my blade styles elsewhere in the file?
My soundfont folder in named vengence (8 characters) in the as. It’s a plecter font
|
|
|
|
Post by jedi3251 on Nov 1, 2018 20:48:45 GMT -5
So I've read through everything and think I have this figured out for the blades... can you please confirm? I want 3 "blades" and will also use the following as my "wiring diagram". Thank you in advance!
BladeConfig blades[] = {
{ 0, // blade ID resistor not used
// Main blade, 120 LEDs
WS2811BladePtr<120, WS2811_800kHz | WS2811_GRB>(),
// First Accent, 1 LEDS, power on LED4, data on pixel data 2
WS2811BladePtr<1, WS2811_800kHz | WS2811_GRB, blade2Pin, PowerPINS<bladePowerPin4> >(),
// Second Accent, 10 LEDS, power on LED5, data on pixel data 3
WS2811BladePtr<10, WS2811_800kHz | WS2811_GRB, blade3Pin, PowerPINS<bladePowerPin5> >(),
CONFIGARRAY(presets)
},
};
|
|
|
|
Post by mjm2086 on Nov 1, 2018 21:16:08 GMT -5
Hello.! Just have a question on a specific 3.7v battery I want use for my Neopixel build. Can a ProffieBoard except a 26650 3.7v lithium battery? Let me know thanks.
|
|
|
|
Post by profezzorn on Nov 1, 2018 21:23:28 GMT -5
Hello.! Just have a question on a specific 3.7v battery I want use for my Neopixel build. Can a ProffieBoard except a 26650 3.7v lithium battery? Let me know thanks. yes |
|
|
|
Post by profezzorn on Nov 1, 2018 21:35:32 GMT -5
So I've read through everything and think I have this figured out for the blades... can you please confirm? I want 3 "blades" and will also use the following as my "wiring diagram". Thank you in advance! BladeConfig blades[] = { { 0, // blade ID resistor not used // Main blade, 120 LEDs WS2811BladePtr<120, WS2811_800kHz | WS2811_GRB>(), // First Accent, 1 LEDS, power on LED4, data on pixel data 2 WS2811BladePtr<1, WS2811_800kHz | WS2811_GRB, blade2Pin, PowerPINS<bladePowerPin4> >(), // Second Accent, 10 LEDS, power on LED5, data on pixel data 3 WS2811BladePtr<10, WS2811_800kHz | WS2811_GRB, blade3Pin, PowerPINS<bladePowerPin5> >(), CONFIGARRAY(presets) }, }; Looks good to me. |
|
|
|
Post by profezzorn on Nov 1, 2018 21:37:41 GMT -5
I got it cleared of errors thanks to Tom. It checks fine and uploads. The new issue is now it seems to skip my changes completely. Does not play soundfont I have on the sd card, nor the blade style attached to it. It also does not seem to recognize that I changed a track on a teensy soundfont either. Like it’s only seeing the stock config from the site. Am I supposed to add my blade styles elsewhere in the file? My soundfont folder in named vengence (8 characters) in the as. It’s a plecter font Either it didn't actually upload it, or you ediited one file and uploaded another. For the first one, make sure you get progress bar and percentages if you scroll down in the window at the bottom the Arduino program. For the second one: Introduce a deliberate error and hit "upload". If it still succeeds, it's not reading the file you think... |
|
|
|
Post by hdjoe22 on Nov 1, 2018 21:43:38 GMT -5
I got it cleared of errors thanks to Tom. It checks fine and uploads. The new issue is now it seems to skip my changes completely. Does not play soundfont I have on the sd card, nor the blade style attached to it. It also does not seem to recognize that I changed a track on a teensy soundfont either. Like it’s only seeing the stock config from the site. Am I supposed to add my blade styles elsewhere in the file? My soundfont folder in named vengence (8 characters) in the as. It’s a plecter font Either it didn't actually upload it, or you ediited one file and uploaded another. For the first one, make sure you get progress bar and percentages if you scroll down in the window at the bottom the Arduino program. For the second one: Introduce a deliberate error and hit "upload". If it still succeeds, it's not reading the file you think... all it shows when i hit the upload button is a countdown 1-10 then it says done uploading. But nothing changes |
|
|
|
Post by profezzorn on Nov 1, 2018 21:46:25 GMT -5
Either it didn't actually upload it, or you ediited one file and uploaded another. For the first one, make sure you get progress bar and percentages if you scroll down in the window at the bottom the Arduino program. For the second one: Introduce a deliberate error and hit "upload". If it still succeeds, it's not reading the file you think... all it shows when i hit the upload button is a countdown 1-10 then it says done uploading. But nothing changes Then it's not actually uploading. The countdown should stop when it finds the board and be replaced with a progress bar (which doesn't work quite correctly, so you have to scroll down to see the progress.) |
|
|
|
Post by profezzorn on Nov 1, 2018 21:48:18 GMT -5
all it shows when i hit the upload button is a countdown 1-10 then it says done uploading. But nothing changes Then it's not actually uploading. The countdown should stop when it finds the board and be replaced with a progress bar (which doesn't work quite correctly, so you have to scroll down to see the progress.) You should see something like this if you scroll down in the window at the bottom of the arduino program: www.facebook.com/photo.php?fbid=2469359803104639&set=gm.354884438581043&type=3&theater&ifg=1 |
|
|
|
Post by hdjoe22 on Nov 1, 2018 21:52:20 GMT -5
Nope... non of that shows up |
|
|
|
Post by jedi3251 on Nov 1, 2018 21:59:22 GMT -5
Thanks Prof!
|
|
|
|
Post by profezzorn on Nov 1, 2018 22:04:04 GMT -5
Nope... non of that shows up That means that Arduino can't find the board. Things to try: 1. Try checking Tools->Port, Select the one that says butterfly and try again 2. Try pressing BOOT+RESET on the board to put it in bootloader mode. 3. If you're on Win10, check settings->printers and devices to make sure that "proffieboard" or STM32 BOOTLOADER shows up there. 4. Try a different USB cable and/or port |
|
|
|
Post by mjm2086 on Nov 1, 2018 23:27:17 GMT -5
Hello.! Just have a question on a specific 3.7v battery I want use for my Neopixel build. Can a ProffieBoard except a 26650 3.7v lithium battery? Let me know thanks. yes Awesome.! Thank you |
|
|
|
Post by thedoctor on Nov 2, 2018 4:45:31 GMT -5
Morning all - I've wired everything up to test my soldering skills (I'm brand new to custom sabering and I've not soldered with this precision for ages!) I'm using 2 back-to-back neopixel strips for the blade) - and everything works perfectly with the stock versions of the config (copy-pasted from Prof's website).
Problem I'm having is when I use the Style Editor to create a color cycle preset, using this in the config file;
{ "TthCrstl", "tracks/mars.wav",
ColorCycle<DodgerBlue, 0, 1, BLUE, 100, 3000, 5000>(), "bluecycle"},
I get the following error on compiling;
In file included from C:\Users\thund\Downloads\ProffieBoard\lightsaber\lightsaber.ino:753:0:
sketch\config/my_saber1.h:36:1: error: cannot convert 'ColorCycle<Rgb<2, 72, 255>, 0, 1, Rgb<0, 0, 255>, 100, 3000, 5000>' to 'StyleFactory*' in initialization
};
^
exit status 1
Error compiling for board Proffieboard.
Just wondering what error I've made, and what I need to do to get this sorted - I've done a tiny bit of Arduino programming previously but I can't get to the bottom of the problem!
Other question I was wondering about was if the preset I'm trying to create will do clash/lock/drag effects etc. The style editor suggests it won't, so if that's the case, what would I need to do to add it in?
Dead chuffed the boards arrived as quick as they did - great bit of hardware, Prof!
|
|
|
|
Post by sa22c on Nov 2, 2018 7:30:14 GMT -5
First off, you need to wrap blade styles in a StylePtr<> declaration. The blade editor doesn’t add that to the generated config file.
Second, the easiest way to get a blade is to use on of the solid colour examples and then replace the colour with your effect. This is an example of the spark blade, with the primary colour replaced with your colour cycle effect.
{ “TthCrstl”, “tracks/mars.wav”,
StylePtr<InOutHelper<EasyBlade<OnSpark<ColorCycle<DodgerBlue, 0, 1, BLUE, 100, 3000, 5000>>, WHITE>, 300, 800> >>(), “bluecycle”},
That should compile, just check it for typos.
|
|
|
|
Post by timeless on Nov 2, 2018 7:36:48 GMT -5
Hello, I just received my Proffieboards this morning, I'm so excited ! I do have a question though, can I have Neopixel blade and 2 regular led blinking (control box) ? Chassis just doesn't have enough room to use single pixels and use the sub blades function... How would I get that ? I was thinking about something like that : BladeConfig blades[] = { { 0, WS2811BladePtr<144, WS2811_ACTUALLY_800kHz | WS2811_GRB>(), SimpleBladePtr<CreeXPE2WhiteTemplate<550>, CreeXPE2WhiteTemplate<240>, NoLED, NoLED, bladePowerPin6, bladePowerPin5, -1, -1>() , CONFIGARRAY(presets) }, }; And then use "Strobe" style for regular led so they blink randomly : #ifdef CONFIG_PRESETS Preset presets[] = { { "TeensySF", "tracks/venus.wav", StyleNormalPtr<BLUE, WHITE, 300, 800>(), StylePtr<Strobe<BLACK,WHITE,2,250>>(), "cyan"}, ... Does that sound correct ? Thanks  |
|
|
|
Post by thedoctor on Nov 2, 2018 7:58:43 GMT -5
First off, you need to wrap blade styles in a StylePtr<> declaration. The blade editor doesn’t add that to the generated config file. Second, the easiest way to get a blade is to use on of the solid colour examples and then replace the colour with your effect. This is an example of the spark blade, with the primary colour replaced with your colour cycle effect. { “TthCrstl”, “tracks/mars.wav”, StylePtr<InOutHelper<EasyBlade<OnSpark<ColorCycle<DodgerBlue, 0, 1, BLUE, 100, 3000, 5000>>, WHITE>, 300, 800> >>(), “bluecycle”}, That should compile, just check it for typos. Ah OK I get it. Didn't realise about the StylePtr bit. That effect combo was exactly what I was gunning for actually - thanks! Didn't initially compile but realised it didn't like the quotation marks as they pasted into Notepad++, also there was one extra pointy bracket before the (). Retyped the quote marks and removed that ">" and everything compiled great. Cheers! |
|
|
|
Post by sa22c on Nov 2, 2018 9:09:37 GMT -5
Excellent. Glad you got it working. Playing with these effects is super fun.
|
|
|
|
Post by megtoothsith on Nov 2, 2018 10:25:05 GMT -5
Morning all - I've wired everything up to test my soldering skills (I'm brand new to custom sabering and I've not soldered with this precision for ages!) I'm using 2 back-to-back neopixel strips for the blade) - and everything works perfectly with the stock versions of the config (copy-pasted from Prof's website). Problem I'm having is when I use the Style Editor to create a color cycle preset, using this in the config file; { "TthCrstl", "tracks/mars.wav", ColorCycle<DodgerBlue, 0, 1, BLUE, 100, 3000, 5000>(), "bluecycle"}, I get the following error on compiling; In file included from C:\Users\thund\Downloads\ProffieBoard\lightsaber\lightsaber.ino:753:0: sketch\config/my_saber1.h:36:1: error: cannot convert 'ColorCycle<Rgb<2, 72, 255>, 0, 1, Rgb<0, 0, 255>, 100, 3000, 5000>' to 'StyleFactory*' in initialization }; ^ exit status 1 Error compiling for board Proffieboard. Just wondering what error I've made, and what I need to do to get this sorted - I've done a tiny bit of Arduino programming previously but I can't get to the bottom of the problem! Other question I was wondering about was if the preset I'm trying to create will do clash/lock/drag effects etc. The style editor suggests it won't, so if that's the case, what would I need to do to add it in? Dead chuffed the boards arrived as quick as they did - great bit of hardware, Prof! He Doc! Anytime you make a new bladestyle with the editor, to write it into your preset, you use this format below: StylePtr<INSERT NEW BLADESTYLE HERE> (), So paste your bladestyle into that sort of template! Also, start with the stock configuration file, and only change one thing at a time. This way if you have compilation erros, you will know precisely where they are at. ALso, the very first few lines of orange / red text on compilation error portray where the errors are! Good luck! |
|
|
|
Post by sa22c on Nov 2, 2018 11:47:04 GMT -5
Folks,
I'm getting a lot of slowdown on effects, similar to what the Teensy was doing before I overclocked it but more severe. For example, the fireblade slows nearly to halt on multiple blaster blocks and even simple blade styles like an spark tip with an audioflicker base colour is acting odd, with the clash effect hanging for 2-3 seconds before returning to the base colour.
Is there an overclock for the proffie that could help the slowdowns?
|
|
|
|
Post by profezzorn on Nov 2, 2018 11:53:35 GMT -5
Folks, I'm getting a lot of slowdown on effects, similar to what the Teensy was doing before I overclocked it but more severe. For example, the fireblade slows nearly to halt on multiple blaster blocks and even simple blade styles like an spark tip with an audioflicker base colour is acting odd, with the clash effect hanging for 2-3 seconds before returning to the base colour. Is there an overclock for the proffie that could help the slowdowns? Weird, generally there should be enough processing speed for things to not slow down. However, sudden battery drain can cause brownouts which the cpu detects and tries to survive by slowing down. Another option is that the sd card is too slow, Finally, you could try using the "top" command in the serial console to see what is actually using cpu. Also, you can use "sdtest" to test your sd card. |
|
|
|
Post by profezzorn on Nov 2, 2018 12:01:38 GMT -5
Hello, I just received my Proffieboards this morning, I'm so excited ! I do have a question though, can I have Neopixel blade and 2 regular led blinking (control box) ? Chassis just doesn't have enough room to use single pixels and use the sub blades function... How would I get that ? I was thinking about something like that : BladeConfig blades[] = { { 0, WS2811BladePtr<144, WS2811_ACTUALLY_800kHz | WS2811_GRB>(), SimpleBladePtr<CreeXPE2WhiteTemplate<550>, CreeXPE2WhiteTemplate<240>, NoLED, NoLED, bladePowerPin6, bladePowerPin5, -1, -1>() , CONFIGARRAY(presets) }, }; And then use "Strobe" style for regular led so they blink randomly : #ifdef CONFIG_PRESETS Preset presets[] = { { "TeensySF", "tracks/venus.wav", StyleNormalPtr<BLUE, WHITE, 300, 800>(), StylePtr<Strobe<BLACK,WHITE,2,250>>(), "cyan"}, ... Does that sound correct ? Thanks This sounds about right. However, with this setup you can't control the two LEDs individually. There are two ways to change the config to be able to control the two LEDs individually: 1. Pretend like they are different colors. You do this by changing the CreeXPE2White templates into CreeXPE2GreenTemplate/CreeXPE2BlueTemplate. Then you could make your style blink between green and blue to have the lights alternate. The advantage of this method is that it's easy to synchronize the lights, the disadvantage is that it mixes up leds and colors. 2. Create two simpleblades, one for each LED. Then you add a style for each LED as well. This has the advantage of giving you more inuitive control over the two pixels, and they can run completely separate patterns. However, synchronizing them becomes harder. There is a third way, which is to make the two leds into a blade with two segments, but I don't think you actually want that. |
|
|
|
Post by timeless on Nov 2, 2018 12:17:30 GMT -5
Hello, I just received my Proffieboards this morning, I'm so excited ! I do have a question though, can I have Neopixel blade and 2 regular led blinking (control box) ? Chassis just doesn't have enough room to use single pixels and use the sub blades function... How would I get that ? I was thinking about something like that : BladeConfig blades[] = { { 0, WS2811BladePtr<144, WS2811_ACTUALLY_800kHz | WS2811_GRB>(), SimpleBladePtr<CreeXPE2WhiteTemplate<550>, CreeXPE2WhiteTemplate<240>, NoLED, NoLED, bladePowerPin6, bladePowerPin5, -1, -1>() , CONFIGARRAY(presets) }, }; And then use "Strobe" style for regular led so they blink randomly : #ifdef CONFIG_PRESETS Preset presets[] = { { "TeensySF", "tracks/venus.wav", StyleNormalPtr<BLUE, WHITE, 300, 800>(), StylePtr<Strobe<BLACK,WHITE,2,250>>(), "cyan"}, ... Does that sound correct ? Thanks This sounds about right. However, with this setup you can't control the two LEDs individually. There are two ways to change the config to be able to control the two LEDs individually: 1. Pretend like they are different colors. You do this by changing the CreeXPE2White templates into CreeXPE2GreenTemplate/CreeXPE2BlueTemplate. Then you could make your style blink between green and blue to have the lights alternate. The advantage of this method is that it's easy to synchronize the lights, the disadvantage is that it mixes up leds and colors. 2. Create two simpleblades, one for each LED. Then you add a style for each LED as well. This has the advantage of giving you more inuitive control over the two pixels, and they can run completely separate patterns. However, synchronizing them becomes harder. There is a third way, which is to make the two leds into a blade with two segments, but I don't think you actually want that. Exactly what I was looking for, thanks ! I'll probably create 2 simpleblades so both leds can blink randomly. |
|
