CFX Build LED strip is always on when kill key removed (SOLVED)

[Timewarp2morow]

Greetings,

I am at a loss. My Neopixel build with CFX is having an issue where the LED blade is constantly powered on when the kill key is removed. My saber is wired up correctly as far as I can tell from the manual. I have 2 ground wires coming off of the TCSS spring loaded hilt side PCB. Those grounds are wired into L1 and L3. L1 is spliced to L2. L3 is spliced to L4. My data line has continuity and is resisting at 330 ohms. The positives of the hilt side PCB spring connector are tied into the positive going to the board power positive (which is coming from the recharge port).  I have the LED Strip setting in R.I.C.E. set to 130 pixels.

When i pull the kill key from the recharge port, the boot sound happens and the blade lights come on. Then when press the activator switch the ignition sound happens and the sound font seems to work properly. But the LED strip does not react to anything. I tried changing colors through RICE. When i power the saber down, the LED stays on.

There is something I have to be missing. I would appreciate any ideas.

[erv]

wrong ledstrip timings

[Timewarp2morow]

wrong ledstrip timings

Thank you for the quick response! I went into the config.txt file. These were the parameters in place:

ls1_timings=350,700,24,1,3
ls2_timings=350,700,24,1,3

I am still having the same issue.

I am using the SK6812 LED strips sold on TCSS.

[Timewarp2morow]

The problem is solved. Thank you, Erv!

I just toyed around with the led strip timings until it worked. I still don't quite understand what those parameters do exactly.

ls1_timings=300,600,24,1,3

[erv]

The problem is solved. Thank you, Erv!

I just toyed around with the led strip timings until it worked. I still don't quite understand what those parameters do exactly.

ls1_timings=300,600,24,1,3

timings are covered in the manual and should match the strip datasheet

[Timewarp2morow]

The problem is solved. Thank you, Erv!

I just toyed around with the led strip timings until it worked. I still don't quite understand what those parameters do exactly.

ls1_timings=300,600,24,1,3

timings are covered in the manual and should match the strip datasheet

Thank you. I was aware that it was covered in the manual. I am just very new to technical information like this and took some extra time and guidance to understand. Thanks for pointing me in the right direction! I would never have figured out the issue. I think I understand where the zero and one timings are derived from the datasheet now. Where do you get the "latch timing" from? That is still stumping me. The blade functionality seems to be fine. I am just trying to make sure I am using the optimal parameters.

[erv]

the latch is the duration of idle data line to latch the new data in the strips. I've observed some variance there and it opens room for optimizing the stream transfer, so I made it as a parameter