Blade Array - Do these subblades make sense?

ProffieOS
1

I’m installing my own Desert Wanderer, which is an OWK thin neck (my first and prob only) using the Goth3d Eco CC Chassis (also my first “real” chassis) and I’m trying to figure out how to set up the blade array. I can report that everything is assembled loosely, ready to be glued, and only the board has to be wired with no melted plastic. Having never seen a Goth3D chassis IRL, I am a little amazed. Thanks to all of the installers here who generously share wiring tips!

Since the chassis is removable and it’s a thin neck, the emitter pcb only gets one data line, but it’s a shtok V3 NPXL connector and I’d like tp preserve that cool set up that comes from the V3 configuration generator.

I think I need 6 blades total, power on bladePowerPin2 and 3 for everything (the CC power lines are connected to the chassis NPXL connector), and all 3 data pins (with one external resistor for the CC).

Does this starter config, partcularly the blade array, make sense? It compiles without issue:

//Desert Wanderer

#ifdef CONFIG_TOP
#include "proffieboard_v2_config.h"
#define NUM_BLADES 6
#define NUM_BUTTONS 2
#define VOLUME 1000
const unsigned int maxLedsPerStrip = 144;
#define CLASH_THRESHOLD_G 1.0
#define ENABLE_AUDIO
#define ENABLE_MOTION
#define ENABLE_WS2811
#define ENABLE_SD
#define SHARED_POWER_PINS
#endif

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

};
BladeConfig blades[] = {
 { 0, 

//16 LED Emitter PCB in series with 125 LED Main Blade
// PCB 
 SubBladeWithStride(0, 15, 2, WS281XBladePtr<141, bladePin, Color8::GRB, PowerPINS<bladePowerPin2, bladePowerPin3> >()),
 SubBladeWithStride(1, 15, 2, NULL),
//Main Blade
 SubBlade (16, 140, NULL),

//Interior Chassis PCB, Seperate Data
 SubBladeWithStride(0, 15, 2, WS281XBladePtr<16, blade2Pin, Color8::GRB, PowerPINS<bladePowerPin2, bladePowerPin3> >()),
 SubBladeWithStride(1, 15, 2, NULL),

//2 Pixel CC, Seperate Data
  WS281XBladePtr<2, blade3Pin, Color8::GRB, PowerPINS<bladePowerPin2,bladePowerPin3> >(), 
  CONFIGARRAY(presets) },
};
#endif

Thank you!

2

So presumably you’ll wire data 1 directly to the back of the data pin on the first neo pcb, and data 2 to the normal data pad (as per Shtok wiring setup V4 in his manual)? Then your emitter wiring takes data from the disc and wires it to the normal data pad on the emitter pcb which is setup with Shtok setup V3?

That being the case, nothing obvious jumps out to me as being wrong. :slight_smile:

1 Like
3

Yep! And data 3 is just for the crystal chamber which is 2 5050 neopixel pcbs in series. I also used your advice concerning routing positive power. It goes from the battery to the first shtok connector, then down to the kill switch from another pad, and then to the board.

I normally have several joints in a build, but this time I only have one (crazy!) and it’s just for the switch grounds because I ordered the wrong pcb and it’s often sold out :slight_smile:

1 Like