# PB V3.7 beta test thread

**URL:** <https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440>\
**Category:** Proffieboards\
**Created:** [May 30, 2021, 8:12pm UTC](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440 "2021-05-30T20:12:04Z")\
**Posts on this page:** 20\
**Page:** 5

<div class="post-metadata">

**Author:** ![NoSloppy](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/nosloppy/32/3865_2.png) [@NoSloppy](https://crucible.hubbe.net/u/NoSloppy)\
**Post date:** [June 7, 2021, 1:36am UTC](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440/82 "2021-06-07T01:36:18Z")

</div>

Confirmed same sound issue using my MacbookPro to compile and upload.

---

<div class="post-metadata">

**Author:** ![profezzorn](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/profezzorn/32/8_2.png) [@profezzorn](https://crucible.hubbe.net/u/profezzorn)\
**Post date:** [June 7, 2021, 1:39am UTC](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440/83 "2021-06-07T01:39:29Z")

</div>

The more I think about this, the weirder it gets too.  
I’ve been thinking that this is a race condition that only occurs when things are running _fast_. However, style doesn’t run every loop of the main loop. Most of the time we’re just waiting for the previous blob of data to be fed out to the blade.

Could you try if a super-simple style, like StylePtr() still causes this problem?

---

<div class="post-metadata">

**Author:** ![NoSloppy](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/nosloppy/32/3865_2.png) [@NoSloppy](https://crucible.hubbe.net/u/NoSloppy)\
**Post date:** [June 7, 2021, 1:49am UTC](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440/84 "2021-06-07T01:49:51Z")

</div>

error: no matching function for call to ‘StylePtr()’  
Trying ` StylePtr<Black>() instead`  
**EDIT** Probably what you typed but the site modified

---

<div class="post-metadata">

**Author:** ![profezzorn](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/profezzorn/32/8_2.png) [@profezzorn](https://crucible.hubbe.net/u/profezzorn)\
**Post date:** [June 7, 2021, 1:57am UTC](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440/85 "2021-06-07T01:57:17Z")

</div>

That is in fact what I typed…

---

<div class="post-metadata">

**Author:** ![NoSloppy](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/nosloppy/32/3865_2.png) [@NoSloppy](https://crucible.hubbe.net/u/NoSloppy)\
**Post date:** [June 7, 2021, 2:34am UTC](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440/86 "2021-06-07T02:34:24Z")

</div>

> [@profezzorn](#):
>
> try if a super-simple style, like `StylePtr<Black>()` still causes this problem?

It does not. It plays cleanly with that style.  
I am currently installing everything on a Windows 10 Virtual machine for variety testing.

---

<div class="post-metadata">

**Author:** ![NoSloppy](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/nosloppy/32/3865_2.png) [@NoSloppy](https://crucible.hubbe.net/u/NoSloppy)\
**Post date:** [June 7, 2021, 2:53am UTC](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440/87 "2021-06-07T02:53:38Z")

</div>

Same result uploading via virtual Windows 10.

---

<div class="post-metadata">

**Author:** ![SA22C](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/sa22c/32/45_2.png) [@SA22C](https://crucible.hubbe.net/u/SA22C)\
**Post date:** [June 7, 2021, 3:12am UTC](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440/88 "2021-06-07T03:12:48Z")

</div>

Ok, flashed my test board with a config from the new configurator, used SDIO High Speed.

On MacOS, copying files to the SD card via usb is still only running at the original speed of roughly 300-500 Kbps. Don’t have a PC to test right now, but curious what speeds I _should_ be expecting?

---

<div class="post-metadata">

**Author:** ![profezzorn](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/profezzorn/32/8_2.png) [@profezzorn](https://crucible.hubbe.net/u/profezzorn)\
**Post date:** [June 7, 2021, 3:13am UTC](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440/89 "2021-06-07T03:13:18Z")

</div>

I wonder if there is maybe something about the power handling for blades that is messing with the sound.

That leads to an additional two things to try:

```auto
StylePtr<InOutHelper<Green, 800, 300>>() // Does this work?

```

The other one is your style that you pasted above, but without the on-demand battery layer.

---

<div class="post-metadata">

**Author:** ![profezzorn](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/profezzorn/32/8_2.png) [@profezzorn](https://crucible.hubbe.net/u/profezzorn)\
**Post date:** [June 7, 2021, 3:18am UTC](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440/90 "2021-06-07T03:18:42Z")

</div>

> [@SA22C](#):
>
> 300-500 Kbps.

The USB read/write speed really isn’t expected to be all that much higher than before.  
The real benefit of SDIO is to support more audio streams and other things that require high bandwidth, like color screens.

---

<div class="post-metadata">

**Author:** ![SA22C](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/sa22c/32/45_2.png) [@SA22C](https://crucible.hubbe.net/u/SA22C)\
**Post date:** [June 7, 2021, 3:19am UTC](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440/91 "2021-06-07T03:19:28Z")

</div>

Ah, ok. I had thought I read somewhere that transfer to the SD card over USB would also be improved. Thanks!

---

<div class="post-metadata">

**Author:** ![SA22C](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/sa22c/32/45_2.png) [@SA22C](https://crucible.hubbe.net/u/SA22C)\
**Post date:** [June 7, 2021, 3:49am UTC](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440/92 "2021-06-07T03:49:12Z")

</div>

Well, didn’t get very far tonight but there’s always tomorrow. Going to put together one of the v2 Graflex Helper boards and test with the new dedicated pads for remote USB tomorrow.

---

<div class="post-metadata">

**Author:** ![NoSloppy](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/nosloppy/32/3865_2.png) [@NoSloppy](https://crucible.hubbe.net/u/NoSloppy)\
**Post date:** [June 7, 2021, 4:48am UTC](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440/93 "2021-06-07T04:48:52Z")

</div>

> [@profezzorn](#):
>
> ```auto
> StylePtr<InOutHelper<Green, 800, 300>>() // Does this work?
> 
> ```

Yes, that’s clean.  
Now, the default file has 2 styles per preset.  
The above works fine with both as that same style.

I found something interesting.  
So the default bladeconfig array has  
first blade - WS2811BladePtr\<97, WS2811\_800kHz\>(),  
2nd blade - SimpleBladePtr\<Cree…stuff

Depending on how I order the styles in the preset makes it work or not.

```auto
my style w/ NO batt-level layer
InOutHelper style

```

Good  
Adding batt-level layer back in also Good.

So I tried

```auto
StylePtr<Black>(),
mystyle 

```

This sounds worse, actually just a blip of out.wav, then no sound until last 1/2 of in.wav

So then I flipped them

```auto
mystyle,
StylePtr<Black>(),

```

and it’s good.

Lastly, I brought a RgueCmdr Rainbow preset into MY config and it had no issues (I had to add 3 more dummy blade styles) because bladeconfig array has:  
WS281XBladePtr\<  
WS281XBladePtr\<  
WS281XBladePtr\<  
SimpleBladePtr\<  
SimpleBladePtr\<

So is there something about the  
WS2811BladePtr\<97, WS2811\_800kHz\>(),  
in the default config or…?

---

<div class="post-metadata">

**Author:** ![NoSloppy](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/nosloppy/32/3865_2.png) [@NoSloppy](https://crucible.hubbe.net/u/NoSloppy)\
**Post date:** [June 7, 2021, 5:22am UTC](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440/94 "2021-06-07T05:22:32Z")

</div>

Ok. It’s the `SimpleBladePtr<Cree.....` blade array somehow is an issue.

I did the default\_proffieboard\_config from scratch with NUM\_BLADES 1  
and commented out the 2nd style in all presets and the  
`SimpleBladePtr<Cree.....` blade array, leaving just  
`WS2811BladePtr<97, WS2811_800kHz>(),`

Every preset sounded fine.

I swapped blade arrays, leaving only the  
`SimpleBladePtr<Cree.....`

**Lo and behold Everything was bad, same as in all other tests before.**

Then just to confirm, I changed the RgueCmdr test preset in MY config file where only the last 2 blades out of 5 are `SimpleBladePtr< `'s  
I had only brought over the top 2 styles from the default, and filled in the bottom 3 styles with ones from elsewhere in the config, so it was:

```auto
{ "RgueCmdr", "tracks/mercury.wav",
  StyleRainbowPtr<300, 800>(),
  StyleRainbowPtr<300, 800>(),
// Switches
  StylePtr<Stripes<16000,100,Red,Black,Green,Black,Blue,Black,White,Black,Rainbow,Black,Yellow,Black,Rgb<60,0,255>,Black>>(),
// Pommel
  StylePtr<Layers<Pulsing<Blue,Black,200>,InOutTrL<TrInstant,TrInstant,Pulsing<Blue,Black,2500>>>>(),
//Bluetooth
  StylePtr<Blue>(),
  "rainbow"},

```

which sounded fine.  
When those Rainbow styles hit the `SimpleBladePtr<` with:

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

```

It had bad sound again.

Also, keeping this tied to this V3 board beta test thread, this same test works fine on a 2.2 board.

---

<div class="post-metadata">

**Author:** ![profezzorn](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/profezzorn/32/8_2.png) [@profezzorn](https://crucible.hubbe.net/u/profezzorn)\
**Post date:** [June 7, 2021, 6:17am UTC](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440/95 "2021-06-07T06:17:46Z")

</div>

Dumb question: What do you have hooked up on LED3/4/5?

---

<div class="post-metadata">

**Author:** ![NoSloppy](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/nosloppy/32/3865_2.png) [@NoSloppy](https://crucible.hubbe.net/u/NoSloppy)\
**Post date:** [June 7, 2021, 6:24am UTC](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440/96 "2021-06-07T06:24:28Z")

</div>

```auto
{ NO_BLADE, // 1" Ciel_Tan_A 132 
  WS281XBladePtr<132, bladePin, Color8::GRB, PowerPINS<bladePowerPin2, bladePowerPin3> >(),// Main Blade
  WS281XBladePtr<5, blade2Pin, Color8::GRB, PowerPINS<bladePowerPin2, bladePowerPin3> >(),// HiltPCB
  WS281XBladePtr<11, blade3Pin, Color8::GRB, PowerPINS<bladePowerPin5> >(),// Switches mini strip
  SimpleBladePtr<AccentsLED, NoLED, NoLED, NoLED, bladePowerPin1, -1, -1, -1>(),// Pommel
  SimpleBladePtr<CH3LED, NoLED, NoLED, NoLED, bladePowerPin6, -1, -1, -1>(),// Bluetooth
CONFIGARRAY(noblade),
"00_NO_BLADE_save"}, 

```

---

<div class="post-metadata">

**Author:** ![NoSloppy](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/nosloppy/32/3865_2.png) [@NoSloppy](https://crucible.hubbe.net/u/NoSloppy)\
**Post date:** [June 7, 2021, 6:27am UTC](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440/97 "2021-06-07T06:27:02Z")

</div>

> [@NoSloppy](#):
>
> Could this be due to a totally different blades setup on the install vs what the default file has in some way?

Note, my first post about this issue posed this question.  
So is that a thing?  
But when MY config is used, with the appropriate blades config’d for the install build, still has issues when a Rainbow blade style is applied to the SimpleBladePtr?

Also, the switches area mini-neostrip was added after this first showed up.

---

<div class="post-metadata">

**Author:** ![profezzorn](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/profezzorn/32/8_2.png) [@profezzorn](https://crucible.hubbe.net/u/profezzorn)\
**Post date:** [June 7, 2021, 7:43am UTC](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440/98 "2021-06-07T07:43:14Z")

</div>

Having a config file that is completely different from what you have plugged in can do some weird stuff. It’s rarely harmful, but it is possible for it to be harmful. An example would be to have a high-powered blade plugged in while only turning on one FET instead of two.

In this case, we’re potentially feeding an 800Hz PWM signal into a neopixel strip. That might cause 800Hz of werdness coming back through the data wire, or pull 800Hz through the + wire for that neopixel strip. I’m not entirely certain what that would do.

Still, it could just be the speed of evaluation that is causing problems. `SimpleBladePtr<>` only has one LED, which makes it very fast. However, we should be able to narrow things down further by trying the following blades:

```auto
WS2811BladePtr<1, WS2811_800kHz>() // also fast

```

or

```auto
   SimpleBladePtr<CreeXPE2WhiteTemplate<550>,
                    CreeXPE2BlueTemplate<240>,
                    CreeXPE2BlueTemplate<240>, NoLED, bladePowerPin1, bladePowerPin2, bladePowerPin3, -1>(),

```

This last one should be equally fast, but flips different pins.

---

<div class="post-metadata">

**Author:** ![NoSloppy](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/nosloppy/32/3865_2.png) [@NoSloppy](https://crucible.hubbe.net/u/NoSloppy)\
**Post date:** [June 7, 2021, 8:01am UTC](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440/99 "2021-06-07T08:01:37Z")

</div>

Okay. I’ll try these tomorrow. Note that I have been testing with no blade inserted.

---

<div class="post-metadata">

**Author:** ![NoSloppy](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/nosloppy/32/3865_2.png) [@NoSloppy](https://crucible.hubbe.net/u/NoSloppy)\
**Post date:** [June 7, 2021, 12:56pm UTC](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440/100 "2021-06-07T12:56:45Z")

</div>

Assuming you meant as replacements for the 2nd blade, using this:

```auto
BladeConfig blades[] = {
 { 0, WS2811BladePtr<97, WS2811_800kHz>(),
      WS2811BladePtr<1, WS2811_800kHz>(),
     CONFIGARRAY(presets) },

```

and then trying this:

```auto
BladeConfig blades[] = {
 { 0, WS2811BladePtr<97, WS2811_800kHz>(),  
     SimpleBladePtr<CreeXPE2WhiteTemplate<550>,
                    CreeXPE2BlueTemplate<240>,
                    CreeXPE2BlueTemplate<240>, NoLED, bladePowerPin1, bladePowerPin2, bladePowerPin3, -1>(),
     CONFIGARRAY(presets) },

```

Everything sounds normal with both of those versions of the bladeConfig.

---

<div class="post-metadata">

**Author:** ![profezzorn](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/profezzorn/32/8_2.png) [@profezzorn](https://crucible.hubbe.net/u/profezzorn)\
**Post date:** [June 7, 2021, 5:05pm UTC](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440/101 "2021-06-07T17:05:41Z")

</div>

To me, this indicates that the problem is one of LED4, LED5 or LED6.  
Basically, it seems that whenever you have a SimpleBladePtr\<\> that output PWM to those three, then the sound gets messed up.

I suggest taking this one:

> [@NoSloppy](#):
>
> ```auto
> BladeConfig blades[] = {
> { 0, WS2811BladePtr<97, WS2811_800kHz>(),  
> SimpleBladePtr<CreeXPE2WhiteTemplate<550>,
> CreeXPE2BlueTemplate<240>,
> CreeXPE2BlueTemplate<240>, NoLED, bladePowerPin1, bladePowerPin2, bladePowerPin3, -1>(),
> CONFIGARRAY(presets) },
> 
> ```

and then replacing one at a time of bladePowerPin1/2/3 with bladePowerPin4/5/6 and see when the problem starts appearing.

It’s either because the accent neopixels are causing interference, which is probably normal, or because of some sort of short, which is not.

[Previous page](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440.md?page=4)

[Next page](https://crucible.hubbe.net/t/pb-v3-7-beta-test-thread/440.md?page=6)