|
|
Post by sa22c on Nov 2, 2018 12:47:39 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. The SD test showed 10.6 streams. I didn’t have the serial monitor on during the slowdowns but the battery was fully charged and showing 4.07 V during the program flash. I’ll see if I can trigger it again with the monitor running so I can see the voltage and run the top command. I did notice that the compiler was set to smallest not fastest in the Arduino IDE. Does that refer to compile speed or execution on device speed? I ask because I reflashed the board with the compiler set to fastest and the slowdown appeared to be gone but I don’t have much time to test. |
|
|
|
Post by profezzorn on Nov 2, 2018 13:27:36 GMT -5
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. The SD test showed 10.6 streams. I didn’t have the serial monitor on during the slowdowns but the battery was fully charged and showing 4.07 V during the program flash. I’ll see if I can trigger it again with the monitor running so I can see the voltage and run the top command. I did notice that the compiler was set to smallest not fastest in the Arduino IDE. Does that refer to compile speed or execution on device speed? I ask because I reflashed the board with the compiler set to fastest and the slowdown appeared to be gone but I don’t have much time to test. Smallest vs. Fastest refers to how it optimizes the code to run on the device. It does not refer to compile time. As long as the code fits when you upload it, there isn't a real good reason not to use "fastest". However, "smallest" should still be fast enough I think. I'm not certain, but I would guess that the difference in speed between "smallest" and "fastest" is not all that great. |
|
|
|
Post by sa22c on Nov 2, 2018 16:34:48 GMT -5
Another thing I just noticed when I was connecting up to my computer to get some serial output:
The Proffieboard is drawing power from the USB port. I plugged in my saber to the USB when the kill key was inserted and I got a 'low battery' vocal warning from the board (though it was very garbled.). On the serial monitor, It showed voltage of 0.6 V. As soon as I pulled the key, the board rebooted and all seemed normal.
Should the Proffie be drawing USB power while the kill key is inserted (or at any other time?)
|
|
|
|
Post by profezzorn on Nov 2, 2018 16:40:36 GMT -5
Another thing I just noticed when I was connecting up to my computer to get some serial output: The Proffieboard is drawing power from the USB port. I plugged in my saber to the USB when the kill key was inserted and I got a 'low battery' vocal warning from the board (though it was very garbled.). On the serial monitor, It showed voltage of 0.6 V. As soon as I pulled the key, the board rebooted and all seemed normal. Should the Proffie be drawing USB power while the kill key is inserted (or at any other time?) Yes. However, USB only powers the CPU, not the booster or audio, so it may complain about low battery and audio will be super noisy, if it works at all. When I have some time, I will add some code that disables audio and low battery warnings while only on USB power. It's only meant to make programming the board easier. |
|
|
|
Post by mjm2086 on Nov 3, 2018 0:16:48 GMT -5
Question I listen to music on my iTunes on my HP computer. But want to transfer them to the board. To make track files for my own personal sound fonts, how does that all work? Let me know thanks.
|
|
|
|
Post by profezzorn on Nov 3, 2018 0:19:41 GMT -5
Question I listen to music on my iTunes on my HP computer. But want to transfer them to the board. To make track files for my own personal sound fonts, how does that all work? Let me know thanks. In itunes, you'll need to download the files. Then you'll need to load them into Audacity or something and save them as 16-bit 44100kHz Mono WAV files. Then transfer them to the SD card, I recommend putting them in "tracks/", but it's possible to put them anywhere. Make sure the filenames are short (8 characters, not counting the ".wav" part.) Finally, update your config file to use the new files and upload to the board. |
|
|
|
Post by mjm2086 on Nov 3, 2018 2:04:14 GMT -5
Hello. So as I’m aware that I can use any Plector or NEC fonts to put with in the ProffieBoard. So once I find me a font rather it be a Plector or a NEC, Do I need to delete any random txt on the font I have in my packages before uploading to the board? If so which txt do I delete from the font? Let me know thanks.
|
|
|
|
Post by profezzorn on Nov 3, 2018 3:55:11 GMT -5
Hello. So as I’m aware that I can use any Plector or NEC fonts to put with in the ProffieBoard. So once I find me a font rather it be a Plector or a NEC, Do I need to delete any random txt on the font I have in my packages before uploading to the board? If so which txt do I delete from the font? Let me know thanks. No You just put the font in a directory on the sd card, then update the configuration file to use it. |
|
|
|
Post by hexlee on Nov 3, 2018 6:24:08 GMT -5
Hi, I'm continuing on a conversation on facebook which went as follows..
Me
So now that ive "successfully" uploaded the program onto my Proffie, Should my mac detect the SD card when I plug it in? ..because its not..
how am i supposed to add sound fonts without access to the SD card?
Fredrik Hubinette
Unfortunately, not yet. I hope to make that work eventually, but it does not work right now.
My question is,
if my font folder needs to go into my SD card folder in my proffie, but my computer cant detect the SD card folder, how do I get the fonts folder into the SD card folder?
Will formatting the SD card reveal it so I can paste the files into it??
Thanks
Hex
|
|
|
|
Post by timeless on Nov 3, 2018 8:46:40 GMT -5
Just installed the proffie in my SH Kanan and I must say, it's amazing ! Wiring is fairly easy too, great work  But I still have some config to do : "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." That's what I did with Strobe effect for each blade but they're synchronized, they blink at the exact same time. I'm looking for a random pattern. Could I use the RandomFlicker effect with <BLACK,WHITE> parameters to get the desired effect ? Or maybe I could add a delay in the strobe effect so they are independent from each other ? Thanks EDIT : hexlee font folders go in the SD card indeed. Guess you're using a Mac, I had the same issue, couldn't copy paste files into it. Either try formatting your sd card ( I couldn't even do that though, it always gave me an error) or try another SD card reader (that worked for me). Seems like Mac are a pain with SD cards etc, Windows seems to be much easier to work with on that side. |
|
|
|
Post by wolsta on Nov 3, 2018 9:24:43 GMT -5
Please excuse my noobness but I'm having issues with my crystal chamber. It's lit by a standard RGB LED that won't play ball. Sometimes it lights the correct colour, other times completely wrong and sometimes no light at all. Green appears to be an issue, but I get cyan.. Red is also an issue but I get purple.. When the saber has power but isn't on, weirdly I get a dim green light on some of the styles. Below is my config. Any help is hugely appreciated. #ifdef CONFIG_TOP #include "proffieboard_v1_config.h" #define NUM_BLADES 2 #define NUM_BUTTONS 2 #define VOLUME 1000 const unsigned int maxLedsPerStrip = 125; #define CLASH_THRESHOLD_G 1.0 #define ENABLE_AUDIO #define ENABLE_MOTION #define ENABLE_WS2811 #define ENABLE_SD #endif #ifdef CONFIG_PRESETS Preset presets[] = { { "TeensySF", "tracks/venus.wav", StyleNormalPtr<CYAN, WHITE, 300, 800>(), StyleNormalPtr<CYAN, WHITE, 300, 800>(), "cyan"}, { "SmthJedi", "tracks/mars.wav", StylePtr<InOutSparkTip<EASYBLADE(BLUE, WHITE), 300, 800> >(), StylePtr<InOutSparkTip<EASYBLADE(BLUE, WHITE), 300, 800> >(), "blue"}, { "SmthGrey", "tracks/mercury.wav", StyleFirePtr<RED, YELLOW, 0>(), StyleFirePtr<RED, YELLOW, 1>(), "fire"}, { "SmthFuzz", "tracks/uranus.wav", StyleNormalPtr<RED, WHITE, 300, 800>(), StyleNormalPtr<RED, WHITE, 300, 800>(), "red"}, { "RgueCmdr", "tracks/venus.wav", StyleFirePtr<BLUE, CYAN, 0>(), StyleFirePtr<BLUE, CYAN, 1>(), "blue fire"}, { "TthCrstl", "tracks/mars.wav", StylePtr<InOutHelper<EASYBLADE(OnSpark<GREEN>, WHITE), 300, 800> >(), StylePtr<InOutHelper<EASYBLADE(OnSpark<GREEN>, WHITE), 300, 800> >(), "green"}, { "TeensySF", "tracks/mercury.wav", StyleNormalPtr<WHITE, RED, 300, 800, RED>(), StyleNormalPtr<WHITE, RED, 300, 800, RED>(), "white"}, { "SmthJedi", "tracks/uranus.wav", StyleNormalPtr<AudioFlicker<YELLOW, WHITE>, BLUE, 300, 800>(), StyleNormalPtr<AudioFlicker<YELLOW, WHITE>, BLUE, 300, 800>(), "yellow"}, { "SmthGrey", "tracks/venus.wav", StylePtr<InOutSparkTip<EASYBLADE(MAGENTA, WHITE), 300, 800> >(), StylePtr<InOutSparkTip<EASYBLADE(MAGENTA, WHITE), 300, 800> >(), "magenta"}, { "SmthFuzz", "tracks/mars.wav", StyleNormalPtr<Gradient<RED, BLUE>, Gradient<CYAN, YELLOW>, 300, 800>(), StyleNormalPtr<Gradient<RED, BLUE>, Gradient<CYAN, YELLOW>, 300, 800>(), "gradient"}, { "RgueCmdr", "tracks/mercury.wav", StyleRainbowPtr<300, 800>(), StyleRainbowPtr<300, 800>(), "rainbow"}, { "TthCrstl", "tracks/uranus.wav", StyleStrobePtr<WHITE, Rainbow, 15, 300, 800>(), StyleStrobePtr<WHITE, Rainbow, 15, 300, 800>(), "strobe"}, { "TeensySF", "tracks/venus.wav", &style_pov, StyleNormalPtr<BLACK, BLACK, 300, 800>(), "POV"}, { "SmthJedi", "tracks/mars.wav", &style_charging, StyleNormalPtr<BLACK, BLACK, 300, 800>(), "Battery\nLevel"} }; BladeConfig blades[] = { { 0, WS2811BladePtr<125, WS2811_ACTUALLY_800kHz | WS2811_GRB>(), SimpleBladePtr<CreeXPE2WhiteTemplate<550>, CreeXPE2BlueTemplate<240>, CreeXPE2BlueTemplate<240>, NoLED, bladePowerPin4, bladePowerPin5, bladePowerPin6, -1>() , CONFIGARRAY(presets) }, }; #endif #ifdef CONFIG_BUTTONS Button PowerButton(BUTTON_POWER, powerButtonPin, "pow"); Button AuxButton(BUTTON_AUX, auxPin, "aux"); #endif |
|
|
|
Post by hexlee on Nov 3, 2018 9:48:10 GMT -5
Just installed the proffie in my SH Kanan and I must say, it's amazing ! Wiring is fairly easy too, great work But I still have some config to do : "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." That's what I did with Strobe effect for each blade but they're synchronized, they blink at the exact same time. I'm looking for a random pattern. Could I use the RandomFlicker effect with <BLACK,WHITE> parameters to get the desired effect ? Or maybe I could add a delay in the strobe effect so they are independent from each other ? Thanks gh EDIT : hexlee font folders go in the SD card indeed. Guess you're using a Mac, I had the same issue, couldn't copy paste files into it. Either try formatting your sd card ( I couldn't even do that though, it always gave me an error) or try another SD card reader (that worked for me). Seems like Mac are a pain with SD cards etc, Windows seems to be much easier to work with on that side. Oh OK.. So I think my first mistake is actually assuming that I can access the SD card through the proffie. I need an SD card reader to do that. And If that doesn't work, I format the SD card.. Priceless information, thanks so much for the help Timeless. |
|
|
|
Post by mjm2086 on Nov 3, 2018 11:03:38 GMT -5
So I’m about to get started with my Neopixel build. Are there specific Neopixel connectors I will need to use for the ProffieBoard install? Or can I get any connectors as I wish? Rather I buy them from TCSS, the saber Armory etc? Let me know thanks.
|
|
|
|
Post by timeless on Nov 3, 2018 11:28:23 GMT -5
So I’m about to get started with my Neopixel build. Are there specific Neopixel connectors I will need to use for the ProffieBoard install? Or can I get any connectors as I wish? Rather I buy them from TCSS, the saber Armory etc? Let me know thanks. It's all up to you. They all work with the proffieboard. However I don't know if TCSS blade side connector works with SaberArmory hilt side connector etc. So if you already have pixel blades ready or want to use some pre-made blades from VV for example, just use the same connector just in case. |
|
|
|
Post by mjm2086 on Nov 3, 2018 11:54:28 GMT -5
So I’m about to get started with my Neopixel build. Are there specific Neopixel connectors I will need to use for the ProffieBoard install? Or can I get any connectors as I wish? Rather I buy them from TCSS, the saber Armory etc? Let me know thanks. It's all up to you. They all work with the proffieboard. However I don't know if TCSS blade side connector works with SaberArmory hilt side connector etc. So if you already have pixel blades ready or want to use some pre-made blades from VV for example, just use the same connector. So let’s say I buy a pre made blade from VV. Would you know what kind of connector I would need to use to put inside the hilt etc? Let me know thanks. |
|
|
|
Post by profezzorn on Nov 3, 2018 14:20:55 GMT -5
Hi, I'm continuing on a conversation on facebook which went as follows..
Me
So now that ive "successfully" uploaded the program onto my Proffie, Should my mac detect the SD card when I plug it in? ..because its not..
how am i supposed to add sound fonts without access to the SD card?
Fredrik Hubinette
Unfortunately, not yet. I hope to make that work eventually, but it does not work right now.
My question is,
if my font folder needs to go into my SD card folder in my proffie, but my computer cant detect the SD card folder, how do I get the fonts folder into the SD card folder?
Will formatting the SD card reveal it so I can paste the files into it??
Thanks
Hex
You'll need to take the SD card out, put it in an SD card reader and attach that to your computer. If you format the SD card, be sure to select FAT32. |
|
|
|
Post by profezzorn on Nov 3, 2018 14:24:30 GMT -5
Just installed the proffie in my SH Kanan and I must say, it's amazing ! Wiring is fairly easy too, great work But I still have some config to do : "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." That's what I did with Strobe effect for each blade but they're synchronized, they blink at the exact same time. I'm looking for a random pattern. Could I use the RandomFlicker effect with <BLACK,WHITE> parameters to get the desired effect ? Or maybe I could add a delay in the strobe effect so they are independent from each other ? Thanks EDIT : hexlee font folders go in the SD card indeed. Guess you're using a Mac, I had the same issue, couldn't copy paste files into it. Either try formatting your sd card ( I couldn't even do that though, it always gave me an error) or try another SD card reader (that worked for me). Seems like Mac are a pain with SD cards etc, Windows seems to be much easier to work with on that side. Adding a delay to the strobe effect is a great idea, and should work reasonably well. The blinking will still be synchronized, but it will at least be out of phase, it would look something like: StylePtr<IgnitionDelay<200, Strobe<BLACK, WHITE, 2, 250>>>() It's my intention to add more options for blinking and random blinking in the future, so stay tuned. |
|
|
|
Post by profezzorn on Nov 3, 2018 14:27:56 GMT -5
Please excuse my noobness but I'm having issues with my crystal chamber. It's lit by a standard RGB LED that won't play ball. Sometimes it lights the correct colour, other times completely wrong and sometimes no light at all. Green appears to be an issue, but I get cyan.. Red is also an issue but I get purple.. When the saber has power but isn't on, weirdly I get a dim green light on some of the styles. Below is my config. Any help is hugely appreciated. #ifdef CONFIG_TOP #include "proffieboard_v1_config.h" #define NUM_BLADES 2 #define NUM_BUTTONS 2 #define VOLUME 1000 const unsigned int maxLedsPerStrip = 125; #define CLASH_THRESHOLD_G 1.0 #define ENABLE_AUDIO #define ENABLE_MOTION #define ENABLE_WS2811 #define ENABLE_SD #endif #ifdef CONFIG_PRESETS Preset presets[] = { { "TeensySF", "tracks/venus.wav", StyleNormalPtr<CYAN, WHITE, 300, 800>(), StyleNormalPtr<CYAN, WHITE, 300, 800>(), "cyan"}, { "SmthJedi", "tracks/mars.wav", StylePtr<InOutSparkTip<EASYBLADE(BLUE, WHITE), 300, 800> >(), StylePtr<InOutSparkTip<EASYBLADE(BLUE, WHITE), 300, 800> >(), "blue"}, { "SmthGrey", "tracks/mercury.wav", StyleFirePtr<RED, YELLOW, 0>(), StyleFirePtr<RED, YELLOW, 1>(), "fire"}, { "SmthFuzz", "tracks/uranus.wav", StyleNormalPtr<RED, WHITE, 300, 800>(), StyleNormalPtr<RED, WHITE, 300, 800>(), "red"}, { "RgueCmdr", "tracks/venus.wav", StyleFirePtr<BLUE, CYAN, 0>(), StyleFirePtr<BLUE, CYAN, 1>(), "blue fire"}, { "TthCrstl", "tracks/mars.wav", StylePtr<InOutHelper<EASYBLADE(OnSpark<GREEN>, WHITE), 300, 800> >(), StylePtr<InOutHelper<EASYBLADE(OnSpark<GREEN>, WHITE), 300, 800> >(), "green"}, { "TeensySF", "tracks/mercury.wav", StyleNormalPtr<WHITE, RED, 300, 800, RED>(), StyleNormalPtr<WHITE, RED, 300, 800, RED>(), "white"}, { "SmthJedi", "tracks/uranus.wav", StyleNormalPtr<AudioFlicker<YELLOW, WHITE>, BLUE, 300, 800>(), StyleNormalPtr<AudioFlicker<YELLOW, WHITE>, BLUE, 300, 800>(), "yellow"}, { "SmthGrey", "tracks/venus.wav", StylePtr<InOutSparkTip<EASYBLADE(MAGENTA, WHITE), 300, 800> >(), StylePtr<InOutSparkTip<EASYBLADE(MAGENTA, WHITE), 300, 800> >(), "magenta"}, { "SmthFuzz", "tracks/mars.wav", StyleNormalPtr<Gradient<RED, BLUE>, Gradient<CYAN, YELLOW>, 300, 800>(), StyleNormalPtr<Gradient<RED, BLUE>, Gradient<CYAN, YELLOW>, 300, 800>(), "gradient"}, { "RgueCmdr", "tracks/mercury.wav", StyleRainbowPtr<300, 800>(), StyleRainbowPtr<300, 800>(), "rainbow"}, { "TthCrstl", "tracks/uranus.wav", StyleStrobePtr<WHITE, Rainbow, 15, 300, 800>(), StyleStrobePtr<WHITE, Rainbow, 15, 300, 800>(), "strobe"}, { "TeensySF", "tracks/venus.wav", &style_pov, StyleNormalPtr<BLACK, BLACK, 300, 800>(), "POV"}, { "SmthJedi", "tracks/mars.wav", &style_charging, StyleNormalPtr<BLACK, BLACK, 300, 800>(), "Battery\nLevel"} }; BladeConfig blades[] = { { 0, WS2811BladePtr<125, WS2811_ACTUALLY_800kHz | WS2811_GRB>(), SimpleBladePtr<CreeXPE2WhiteTemplate<550>, CreeXPE2BlueTemplate<240>, CreeXPE2BlueTemplate<240>, NoLED, bladePowerPin4, bladePowerPin5, bladePowerPin6, -1>() , CONFIGARRAY(presets) }, }; #endif #ifdef CONFIG_BUTTONS Button PowerButton(BUTTON_POWER, powerButtonPin, "pow"); Button AuxButton(BUTTON_AUX, auxPin, "aux"); #endif The problem seems to be that your SimpleBlade claims to have a white, and two blue LEDs. Maybe something like this will work better: SimpleBladePtr<CreeXPE2RedTemplate<1000>, CreeXPE2GreenTemplate<0>, CreeXPE2BlueTemplate<240>, NoLED, bladePowerPin4, bladePowerPin5, bladePowerPin6, -1>() |
|
|
|
Post by profezzorn on Nov 3, 2018 14:30:06 GMT -5
So I’m about to get started with my Neopixel build. Are there specific Neopixel connectors I will need to use for the ProffieBoard install? Or can I get any connectors as I wish? Rather I buy them from TCSS, the saber Armory etc? Let me know thanks. Any connectors will work, as long as they can handle the amount of current needed. |
|
|
|
Post by wolsta on Nov 3, 2018 14:40:39 GMT -5
Please excuse my noobness but I'm having issues with my crystal chamber. It's lit by a standard RGB LED that won't play ball. Sometimes it lights the correct colour, other times completely wrong and sometimes no light at all. Green appears to be an issue, but I get cyan.. Red is also an issue but I get purple.. When the saber has power but isn't on, weirdly I get a dim green light on some of the styles. Below is my config. Any help is hugely appreciated. #ifdef CONFIG_TOP #include "proffieboard_v1_config.h" #define NUM_BLADES 2 #define NUM_BUTTONS 2 #define VOLUME 1000 const unsigned int maxLedsPerStrip = 125; #define CLASH_THRESHOLD_G 1.0 #define ENABLE_AUDIO #define ENABLE_MOTION #define ENABLE_WS2811 #define ENABLE_SD #endif #ifdef CONFIG_PRESETS Preset presets[] = { { "TeensySF", "tracks/venus.wav", StyleNormalPtr<CYAN, WHITE, 300, 800>(), StyleNormalPtr<CYAN, WHITE, 300, 800>(), "cyan"}, { "SmthJedi", "tracks/mars.wav", StylePtr<InOutSparkTip<EASYBLADE(BLUE, WHITE), 300, 800> >(), StylePtr<InOutSparkTip<EASYBLADE(BLUE, WHITE), 300, 800> >(), "blue"}, { "SmthGrey", "tracks/mercury.wav", StyleFirePtr<RED, YELLOW, 0>(), StyleFirePtr<RED, YELLOW, 1>(), "fire"}, { "SmthFuzz", "tracks/uranus.wav", StyleNormalPtr<RED, WHITE, 300, 800>(), StyleNormalPtr<RED, WHITE, 300, 800>(), "red"}, { "RgueCmdr", "tracks/venus.wav", StyleFirePtr<BLUE, CYAN, 0>(), StyleFirePtr<BLUE, CYAN, 1>(), "blue fire"}, { "TthCrstl", "tracks/mars.wav", StylePtr<InOutHelper<EASYBLADE(OnSpark<GREEN>, WHITE), 300, 800> >(), StylePtr<InOutHelper<EASYBLADE(OnSpark<GREEN>, WHITE), 300, 800> >(), "green"}, { "TeensySF", "tracks/mercury.wav", StyleNormalPtr<WHITE, RED, 300, 800, RED>(), StyleNormalPtr<WHITE, RED, 300, 800, RED>(), "white"}, { "SmthJedi", "tracks/uranus.wav", StyleNormalPtr<AudioFlicker<YELLOW, WHITE>, BLUE, 300, 800>(), StyleNormalPtr<AudioFlicker<YELLOW, WHITE>, BLUE, 300, 800>(), "yellow"}, { "SmthGrey", "tracks/venus.wav", StylePtr<InOutSparkTip<EASYBLADE(MAGENTA, WHITE), 300, 800> >(), StylePtr<InOutSparkTip<EASYBLADE(MAGENTA, WHITE), 300, 800> >(), "magenta"}, { "SmthFuzz", "tracks/mars.wav", StyleNormalPtr<Gradient<RED, BLUE>, Gradient<CYAN, YELLOW>, 300, 800>(), StyleNormalPtr<Gradient<RED, BLUE>, Gradient<CYAN, YELLOW>, 300, 800>(), "gradient"}, { "RgueCmdr", "tracks/mercury.wav", StyleRainbowPtr<300, 800>(), StyleRainbowPtr<300, 800>(), "rainbow"}, { "TthCrstl", "tracks/uranus.wav", StyleStrobePtr<WHITE, Rainbow, 15, 300, 800>(), StyleStrobePtr<WHITE, Rainbow, 15, 300, 800>(), "strobe"}, { "TeensySF", "tracks/venus.wav", &style_pov, StyleNormalPtr<BLACK, BLACK, 300, 800>(), "POV"}, { "SmthJedi", "tracks/mars.wav", &style_charging, StyleNormalPtr<BLACK, BLACK, 300, 800>(), "Battery\nLevel"} }; BladeConfig blades[] = { { 0, WS2811BladePtr<125, WS2811_ACTUALLY_800kHz | WS2811_GRB>(), SimpleBladePtr<CreeXPE2WhiteTemplate<550>, CreeXPE2BlueTemplate<240>, CreeXPE2BlueTemplate<240>, NoLED, bladePowerPin4, bladePowerPin5, bladePowerPin6, -1>() , CONFIGARRAY(presets) }, }; #endif #ifdef CONFIG_BUTTONS Button PowerButton(BUTTON_POWER, powerButtonPin, "pow"); Button AuxButton(BUTTON_AUX, auxPin, "aux"); #endif The problem seems to be that your SimpleBlade claims to have a white, and two blue LEDs. Maybe something like this will work better: SimpleBladePtr<CreeXPE2RedTemplate<1000>, CreeXPE2GreenTemplate<0>, CreeXPE2BlueTemplate<240>, NoLED, bladePowerPin4, bladePowerPin5, bladePowerPin6, -1>() Do you know, I looked at that and wondered why it had white and two blues. But didn't think that could possibly be it for some reason. Funny how the answer is usually staring you in the face. Thank you, sir, I'll try that and let you know how I get on. |
|
|
|
Post by wolsta on Nov 3, 2018 16:22:51 GMT -5
All sorted - a fully functioning RGB LED CC now. Thanks Prof.
|
|
|
|
Post by timeless on Nov 3, 2018 17:00:31 GMT -5
It's all up to you. They all work with the proffieboard. However I don't know if TCSS blade side connector works with SaberArmory hilt side connector etc. So if you already have pixel blades ready or want to use some pre-made blades from VV for example, just use the same connector. So let’s say I buy a pre made blade from VV. Would you know what kind of connector I would need to use to put inside the hilt etc? Let me know thanks. VV use TCSS connector. |
|
|
|
Post by hdjoe22 on Nov 3, 2018 20:22:17 GMT -5
Can someone help me with this code please? I'm trying to get the second blade in a 3 blade setup to stay pulsing until i kill power to the saber. I have the pulsing working but it only pulses for a few seconds and stops on its own
StylePtr<InOutHelper<SimpleClash<Lockup<Blast<ColorCycle<Blue,0,1,Rgb<2,0,236>,100,3000,5000>,White>,
AudioFlicker<Blue,White>>,White,40>,300,800,Pulsing<Blue,Pulsing<White,Red,5000>,4000>>>(),
thank you!
|
|
|
|
Post by profezzorn on Nov 3, 2018 21:09:53 GMT -5
Can someone help me with this code please? I'm trying to get the second blade in a 3 blade setup to stay pulsing until i kill power to the saber. I have the pulsing working but it only pulses for a few seconds and stops on its own StylePtr<InOutHelper<SimpleClash<Lockup<Blast<ColorCycle<Blue,0,1,Rgb<2,0,236>,100,3000,5000>,White>, AudioFlicker<Blue,White>>,White,40>,300,800,Pulsing<Blue,Pulsing<White,Red,5000>,4000>>>(), thank you! Seems to work as intended in the style editor, which means there is probably a bug in the code, like maybe something doesn't realize that it needs to stay on... If you provide the whole file I will try it out when I get a chance. |
|
|
|
Post by megtoothsith on Nov 4, 2018 0:07:16 GMT -5
I think its an issue with wrapping colorcycle up in InOutHelper. I had lots of issues with cycle bladhines when you wrap them. I think it has to do with cycle close out ms. Shuts off blade completely, including off behavior.
Tom
|
|
|
|
Post by profezzorn on Nov 4, 2018 0:19:52 GMT -5
I think its an issue with wrapping colorcycle up in InOutHelper. I had lots of issues with cycle bladhines when you wrap them. I think it has to do with cycle close out ms. Shuts off blade completely, including off behavior. Tom I think you are right. Guess I need to figure out better "off" semantics. |
|
|
|
Post by megtoothsith on Nov 4, 2018 1:00:00 GMT -5
Did proffie show up on any com port in the tools menu in Arduino?
|
|
|
|
Post by jedi3251 on Nov 4, 2018 1:04:36 GMT -5
Yes. I'm getting it to say this now... which I see was an issue before with other users but not sure what the resolution was. I am on a Windows machine if that matters.
Sketch uses 133040 bytes (54%) of program storage space. Maximum is 245760 bytes.
Cannot open DFU device 0483:df11
1
Cannot open DFU device 0483:df11
2
Cannot open DFU device 0483:df11
3
Cannot open DFU device 0483:df11
4
Cannot open DFU device 0483:df11
5
Cannot open DFU device 0483:df11
6
Cannot open DFU device 0483:df11
7
Cannot open DFU device 0483:df11
8
Cannot open DFU device 0483:df11
9
Cannot open DFU device 0483:df11
10
Cannot open DFU device 0483:df11
|
|
|
|
Post by hdjoe22 on Nov 4, 2018 1:19:33 GMT -5
Can someone help me with this code please? I'm trying to get the second blade in a 3 blade setup to stay pulsing until i kill power to the saber. I have the pulsing working but it only pulses for a few seconds and stops on its own StylePtr<InOutHelper<SimpleClash<Lockup<Blast<ColorCycle<Blue,0,1,Rgb<2,0,236>,100,3000,5000>,White>, AudioFlicker<Blue,White>>,White,40>,300,800,Pulsing<Blue,Pulsing<White,Red,5000>,4000>>>(), thank you! Seems to work as intended in the style editor, which means there is probably a bug in the code, like maybe something doesn't realize that it needs to stay on... If you provide the whole file I will try it out when I get a chance. Do you need the entire .h file still? Or is it just a bug that needs to get worked out? |
|
|
|
Post by megtoothsith on Nov 4, 2018 5:15:48 GMT -5
The cycle is a finicky complex bladestyle that is still fairly new. While I think it works as a normal bladestyle ok, and Fredrdik worked out most of its earlier bugs, compounding it with other styles still brings out its ugly past. I'm pretty sure its a code bug, so be patient for the fix, remember Fredrik is still in the middle of the run.
|
|
