No leds lighting up

ProffieOS
1

Hi everyone.

I tried wiring this diagram for anakin ep 2 and the modifications i did was use a button with accent leds and use a sthock 10pin over 7 pin.

Leds seem to not turn on. Non of them. Neo pixel and accents uses data 1, leds 2/3.

Switch one power is working fine but the accents wont light up. It uses its own data 2 and led 1.
Switch Two Aux is working fine but the accents wont light up. It uses its own data 3 and led 6.
Accent led and Neo pixel pcb are in series and share data 1 and LEDS 2,3.

Battery + to neo pixel positive wires/pads when ON: measures 3.7v.

when on/off - Measures 0 v when i do battery + to leds 1/2/3/6. It could be multimeter issue as it stops at 40amps (not sure volts).

Negative terminal and postive terminal use 22 awg wires to proffie and NEO pcb respectively. 22 awg to the leds 2/3. Rest all use 28 awg and specifically for the buttons and accents on the buttons, we used 30 awg.

All accents/switch leds and neo pixel share a common positive.

How is it not even 1 led lights up?

Everything is wired correctly due to continuity test on all wires. Here are pics of mosfets too. (Another post due to post limit)

PLEASE NOTE, those are not exposed copper wires! It is enamel coated it is the only readily available 30 awg wires I can find. Solderer tested for shorts and the company/shop strong said it will not short anything. U need to remove the coating by sanding and heat.

Link to switch led :
SHTOKCUSTOMWORX PXL SWITCH PCB

Each switch has a 470ohm resistor.

2

IMG_8611
IMG_86111512×2016 454 KB

3

IMG_8610
IMG_86101512×2016 549 KB

4

IMG_8612
IMG_86123024×4032 1.14 MB

6

IMG_8562
IMG_85621330×2016 809 KB

8 
#ifdef CONFIG_TOP
#include "proffieboard_v2_config.h"
#define NUM_BLADES 3
#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
#endif

#ifdef CONFIG_PRESETS
Preset presets[] = {
   { "TeensySF", "tracks/venus.wav",
    StyleNormalPtr<CYAN, WHITE, 300, 800>(),
    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> >(),
    StylePtr<InOutSparkTip<EASYBLADE(BLUE, WHITE), 300, 800> >(), "blue"},
   { "SmthGrey", "tracks/mercury.wav",
    StyleFirePtr<RED, YELLOW, 0>(),
    StyleFirePtr<RED, YELLOW, 1>(),
    StyleFirePtr<RED, YELLOW, 2>(), "fire"},
   { "SmthFuzz", "tracks/uranus.wav",
    StyleNormalPtr<RED, WHITE, 300, 800>(),
    StyleNormalPtr<RED, WHITE, 300, 800>(),
    StyleNormalPtr<RED, WHITE, 300, 800>(), "red"},
   { "RgueCmdr", "tracks/venus.wav",
    StyleFirePtr<BLUE, CYAN, 0>(),
    StyleFirePtr<BLUE, CYAN, 1>(),
    StyleFirePtr<BLUE, CYAN, 2>(), "blue fire"},
   { "TthCrstl", "tracks/mars.wav",
    StylePtr<InOutHelper<EASYBLADE(OnSpark<GREEN>, WHITE), 300, 800> >(),
    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>(),
    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>(),
    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> >(),
    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>(),
    StyleNormalPtr<Gradient<RED, BLUE>, Gradient<CYAN, YELLOW>, 300, 800>(), "gradient"},
   { "RgueCmdr", "tracks/mercury.wav",
    StyleRainbowPtr<300, 800>(),
    StyleRainbowPtr<300, 800>(),
    StyleRainbowPtr<300, 800>(), "rainbow"},
   { "TthCrstl", "tracks/uranus.wav",
    StyleStrobePtr<WHITE, Rainbow, 15, 300, 800>(),
    StyleStrobePtr<WHITE, Rainbow, 15, 300, 800>(),
    StyleStrobePtr<WHITE, Rainbow, 15, 300, 800>(), "strobe"},
   { "TeensySF", "tracks/venus.wav",
    &style_pov,
    StyleNormalPtr<BLACK, BLACK, 300, 800>(),
    StyleNormalPtr<BLACK, BLACK, 300, 800>(), "POV"},
   { "SmthJedi", "tracks/mars.wav",
    &style_charging,
    StyleNormalPtr<BLACK, BLACK, 300, 800>(),
    StyleNormalPtr<BLACK, BLACK, 300, 800>(), "Battery\nLevel"}
};
BladeConfig blades[] = {
 { 0, WS281XBladePtr<144, bladePin, Color8::GRB, PowerPINS<bladePowerPin2, bladePowerPin3> >(),
    WS281XBladePtr<2, blade2Pin, Color8::GRB, PowerPINS<bladePowerPin1> >(),
    WS281XBladePtr<2, blade3Pin, Color8::GRB, PowerPINS<bladePowerPin6> >()
  , CONFIGARRAY(presets) },
};
#endif

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

ztest_config.h (3.6 KB)

10

Wiring:

The bottom of LED2/3 looks like they may be touching the side of the fet. If they are the could cause a short. It’s not possible to tell from the picture though.

You have soldered BATT- to GND, which means the full power of the blades and stuff will be going through a tiny solder bridge between GND and BATT-. The solder bridge looks in good shape right now, byt you should probably fix that.

Configuration:

It seems you have an accent LED (and maybe some LEDs on the pogo pin PCB) hooked in series with the main blade. You probably want to use subblade fo that. It should still light up even if you don’t do that though.

Troubleshooting:

Are you testing this with USB power plugged in?
It’s possible that battery power just isn’t making it to the board, which would make the LEDs not light up. Have you measure the voltage at the LEDs when they are supposed to be on?

It could also be a data problem, here is a page that describes how to test if there is data flowing or not:

1 Like
11

Thanks. I will test soon. Just as a note. Battery + to led 4,5 and even 6 and led 1 measures 3.7v when on. No led light ups anyway. The switches have 2 470 ohm resistors. I wonder if that is doing anything.

Though I removed the wire + of the switches so not sure.

Switches 2/3 to battery + measure 4v btw. Just wondering what that means.

I did use subblades first but after not working (no code errors) I just decided to go with the most basic config programming.

12

I did the fet test. 0.2 (0.199) v when off and 3.7 when on. It should be 0.1 when off.

I did data test and got variable a/c so for all ports when turned on so it works fine.

Jumped the battery- to leds (4,5 cause I changed from 2/3 to test fett). Did not turn on

Any clue what that means?

13

Only this turned on when we tried to connect the blade and with the battery- to the led (4/5 over 2/3) bridge.

IMG_8616
IMG_86161512×2016 752 KB

This colour never changes even with changing sound font.

14

What camera is taking those crisp closeups?

1 Like
15

It can basically read any value when off.

It basically means that power is not the problem.

Time to check the data connections. (Set your multimeter to AC to check for data.)

1 Like
16

15 pro max

17

0.123 v when off A/C.
0.67 v when on A/C (red colour on a single led).

This behaviour is happening when i use just a basic no resistor switch.

No continuity between data 1 and battery +, 3.3V and ground.

I removed the old switches, led 1/6, data 2/3.

18

Seems like the first LED just comes on when it gets power. (And turn off when the power goes away.) That would still indicate a problem with the data.

1 Like
19

But as you see the program file is correct.

And with the data test, i got 0.123 v when off A/C.
0.67 v when on A/C (red colour on a single led).

I tried connecting blade again. This time the a single green led turned immediately on then off. Not doing it again.

So what now haha? :smiling_face_with_tear:

20

Side note from manufacturer who mentioned maybe this could be an issue:
IMG_8620

21

Possibly.
Those components are involved in making sound though, it would be a bit odd if a problem in this area would cause LED issues.

1 Like
22

I don’t suppose at some point you plugged the battery in backwards?
Proffieboards have protection for this, but pixel-leds don’t.
If you have any other pixels, maybe try those?

1 Like