You want the positive of the NPXL connector to be wired to either the positive battery tab itself, or on the same leg of the kill switch as the battery tab.
Is this one of them boards where R1 or R2 has to be removed? (in some cases)
Yes, but they are using option 2 which is the blade and onboard LEDs in parallel.
For that option you don’t remove either resistor and just run everything through the onboard D2 pad.
I’ll have to see if I can get it back apart to wire npxl pos to the tab directly. The original eco npxl pcb only had the one resistor. For the v4 npxl pcb, I’m wiring to D2 between the two resistors. I’ve done this without removing a resistor for just about every other build I’ve done without issue. I recall that being a valid config from the manual. In any case, both pcbs read 470 ohms on the data line.
Yeah, that’s option 2 in the manual.
It’s the only option without removing a resistor and it has the blade and onboard LEDs in parallel.
Alright, so I got it apart, and best I can tell, the wiring was like so:
It’s a very tight space up where the thin neck pcb is because the kill switch is sandwiched in between the pcb and the positive battery tab, all within about 1/2" length of the chassis. Any suggestions on a space-conscious way to wire that up?
EDIT: The only difference was that the data line was moved to Data2 on the Proffie board to check if Data1 was the culprit.
EDIT2: I wired the thin neck pcb positive directly to the positive battery tab. Same result. I also swapped the data line to Data3 (and adjusted config to use blade3Pin). Still same result. I’m at my wit’s end here, astounded that three data pads are all not performing. I’m getting constant 0 VAC readings between GND and the data pad whether the saber is ignited or not.
FINAL EDIT: Eureka! I was looking very closely at the thin neck pcb under a magnifying glass, and noticed a tiny bit of stray solder had bridged from negative to data. Once I fixed that, and restored the wiring and config to the original Data1 pad, it lit right up!
Congrats!
That build is pretty tight, I installed one for a coworker and that was something I ran into as well ![]()
