PB V3.7 beta test thread

Proffieboards
102

Okay I’ll try that when I get home. I suspect the Bluetooth module on 6. Does that sound likely?

103

That does sound likely, yes.

104

And … we have a winner!
Swapping 1>4 was fine. 2>5 fine.
But 3>6 with the BT630 on it causes the sound issue to appear.

So. What have we learned?
The Ptr and the style matters, because the simple Black or InOutHelper ones were fine etc…
Trying to understand the takeaway here.

1 Like
105

Additionally, on that v2.2 board I compared against…I had the BT to GND, not an LED pad.
Mirroring the V3 setup, it ALSO DOES the sound crackling weirdness.
So this dispels previous comments that it’s only a v3 board issue.

3 Likes
106

23.5 SAS

I have begun. My first config compiled successfully, 33% memory usage. That SD speed is something!!! Install begins tonight, doing it live! Pray for me.

3 Likes
107

Fredrik said he wanted pics and video of builds. Did mine tonight live! I have some cleaning up to do, but the saber is working. Here:

3 Likes
108

Board almost installed:

20210607_234120
20210607_2341201908×4032 829 KB

PS, Data 1 and 2 work to drive neopixels as expected. I’ll jump the Shtok pixels over to data 3 and 4 to check them. I missed that in my last beta. Then I think I’ll move onto OLED, and maybe Blue Tooth via Red Bear Nano II BLE.

1 Like
109

I’ll have to watch later but looks like great work as always!

110

Skip to the end, I used your “test” font!!! Its a blast.

111

I will say this. SD cards are corrupted much easier it seems by not ejecting properly from the computer first before disconnecting.
I have had a few times now I have forgotten to unmount with all this testing, and files go bye bye quickly.

112

I wonder if it’s due to SDIO being faster somehow, or if it’s related to having prop files that saves more things now. Or maybe it’s just because you’re messing with it?

1 Like
113

I can only speak from experience. With other boards, I have certainly forgotten to eject before uploading plenty of times, and while of course that’s not ideal, I never had corrupt files more than maybe once. This has happened three times to me on this board. It could be the card I suppose, but I’ve used the same brand several other boards as well. My first inkling was SDIO, but that shouldn’t have anything to do with it being mounted to the computer right? So it’s weird.

1 Like
114

So with the speed and memory increases, does this open up actual quad blade animations? THey are slow / big as I am sure you know. I feel like 3.7 will let them shine and get smooth animations

2 Likes
115

Im running 6 blades on proffie 2.2 with no issues in my mentor graflex, but Im sure tge sd read speed will improve everything. The SDIO and increased ram are huge upgrades on 3.7 for speed.

3 Likes
116

Quad-blades work with 2.2 proffieboards (as evidenced by my k4 saber) but it can certainly be hard to make everything fit when you turn on optimizations, which is more or less required to make some of the animations smooth. WIth V3 boards, it should be easy.

2 Likes
117

I misunderstood. Sorry.

118

On my initial install, I used data 1 for main blade, and data 2 for onboard Shtok Pixels. Both worked as expected. Tonight, I swapped the data line and config to test data 3 and data 4. I’m running a Shtok NXPL connector in V4 (independent behavior for onboard pixels and blade). So, the connector requires 2 data lines (one for the main blade, and one for onboard pixels). Tonight, I modified my config for onboard Shtok Pixels to run off data pad 3, tested successfully. Then I modified my config to run them off data pad 4, and experienced a glitch. Accent pixels in the Shtok NXPL Adapter lit up all white in all presets. I then moved the data line back to Data 3, and the saber functioned as expected. I then took it back to data 4, and recreated the same issue. Now, the pixels are getting power, and some signal, but are lighting up white. I think there is an issue with Data4. Video below if needed.

119

Sounds like it might be a problem with the neopixel data proxy mode.
Could you post your config file?

120

lets try this backtick thing:

#include "proffieboard_v3_config.h"
#define NUM_BLADES 2
#define NUM_BUTTONS 2
#define VOLUME 2000
const unsigned int maxLedsPerStrip = 144;
#define CLASH_THRESHOLD_G 1.9
#define ENABLE_AUDIO
#define ENABLE_MOTION
#define ENABLE_WS2811
#define ENABLE_SD
#define SHARED_POWER_PINS
#endif

#ifdef CONFIG_PRESETS
Preset presets[] = {
   { "test", "tracks/track4.wav",
    StyleNormalPtr<CYAN, WHITE, 300, 800>(),
    StyleNormalPtr<CYAN, WHITE, 300, 800>(), "cyan"},

      { "kross", "tracks/kylo.wav",
    StyleFirePtr<RED, YELLOW, 0>(),
    StyleFirePtr<RED, YELLOW, 1>(), "fire"},

   { "vader", "tracks/hall.wav",
    StyleNormalPtr<RED, WHITE, 300, 800>(),
    StyleNormalPtr<RED, WHITE, 300, 800>(), "red"},

      { "rotj", "tracks/jaba.wav",
    StylePtr<InOutHelper<EASYBLADE(OnSpark<GREEN>, WHITE), 300, 800> >(),
    StylePtr<InOutHelper<EASYBLADE(OnSpark<GREEN>, WHITE), 300, 800> >(), "green"},   

{ "RgueCmdr", "tracks/swars.wav",
    StyleRainbowPtr<300, 800>(),
    StyleRainbowPtr<300, 800>(), "rainbow"},

 { "SmthJedi", "tracks/mando.wav",
    &style_charging,
    &style_charging,
"Battery\nLevel"}
};

BladeConfig blades[] = {
 { 0, WS281XBladePtr<130, bladePin, Color8::GRB, PowerPINS<bladePowerPin2, bladePowerPin3> >(),
    WS281XBladePtr<16, blade4Pin, Color8::GRB, PowerPINS<bladePowerPin2, bladePowerPin3> >()
  , CONFIGARRAY(presets) },
};
#endif

#ifdef CONFIG_BUTTONS
Button PowerButton(BUTTON_POWER, powerButtonPin, "pow");
Button AuxButton(BUTTON_AUX, auxPin, "aux");
#endif
121

Well the “good” news is that I get the same results.
Time to figure out why.

1 Like