Page 1 of 2 1 2 LastLast
Results 1 to 10 of 19

Thread: Prizm 5.1 Neoxpixel install fails, weird beep sound and then nothing happens.

  1. #1

    Default Prizm 5.1 Neoxpixel install fails, weird beep sound and then nothing happens.

    Hello,
    I am new here and last week i exitedly opened my package with my prizm 5.1 in it to start my install for a photon neopixel build.

    After soldering for a test-wiring my prizm just makes some beep sounds as soon as i take out the kill key but thats all for it, nothing more to happen..
    if i put the killkey back in and pull it out again i will always get that same sound without anymore functions. I use a saber essential speaker, a full-charged panasonic 3400mah 3,7V Li-Ion-Battery, two momentary switches and the tcss pcb connectors for the led strips ws2812b.
    I bridged the resistor pads on LS pad with a 0603 smd.
    SD Card shows no issues whatsoever when i read it with the cardreader, didnt solder or work with the board with sd card in it, worked on a antistatic mat and always wear an antistatic wrist band. I dont know what the issue could be, pls anyone help to get me that neopixel build i want so badly.

    https://ibb.co/c5tP3z
    https://ibb.co/hexLAe
    https://ibb.co/mJH6GK

  2. #2

    Default

    Is the battery protection circuit tripping? Have you measured voltage on the supply pads? Is the battery fully charged? Do you have the right configs loaded? Photos look OK from a brief perusal of your soldering.

    Tom

    "Let the past die."

  3. #3

    Default

    Quote Originally Posted by Tom Tilmon View Post
    Is the battery protection circuit tripping? Have you measured voltage on the supply pads? Is the battery fully charged? Do you have the right configs loaded? Photos look OK from a brief perusal of your soldering.

    Tom
    I checked everything twice. At least i found the solution. Was quite simple but hard to recognize. My data on the SD-Card was all in a Folder called Prizm5. As soon as i deleted the folder and shifted the data directly to the diskfolder everything worked fine.

  4. #4

    Default

    yes, there should only be folders entitled: bank1, bank2, bank3, bank4, bank5, and bank6. glad you got it working.

    "Let the past die."

  5. #5

    Default

    Well, unfortunately problems are continueing..

    My double strip only lights up red instead of blue (1st bank) or green (2nd bank). On the bank for green the red is flickering quite strong. There is some crackling on the speakers when lit, on the green setting the crackling is even louder. Foc and blaster work absolutely fine in white, thats why i dont understand why i cant adress blue or green colours. Battery is fully charged. Resistor 330 ohm is on dataline. I already snipped the first two pixels of the strings away and resoldered it to make sure its not a fried first pixel. Still the same..
    Does anyone know what the issue could be?
    Last edited by erazer; 08-03-2018 at 06:03 AM.

  6. #6

    Default

    so the strips you got are RGB, instead of the GRB. Most strips are GRB, but every now and then I get a pair that is RGB. On the boards I use, you can change the color order profile. I'll read the prism manual and see if color order is adjustable. The speaker crackling is typical of a struggling battery. Do you have room in the hilt for a bigger battery? Also, is that battery fully charged when the speaker crackles?

    I'll check the prism manual to see if you can adapt it to those RGB strips.

    Tom

    "Let the past die."

  7. #7

    Default

    yes thats what i thought too so i charged the battery fully before i tried again to make sure. Its a 3400mah NCR fully charged, though i still will try to modify my chassis for a 26650 with a handmill. the space in the hilt should be enough. Unfortunately it doesnt seem to be the issue here. I set my banks for 1st bank 0,0,1023 2nd bank 0,1023,0, 3rd bank 1023,0,0 but all of them light up red, 2nd bank hard flickering with very loud crackling. The strips are actually stated as RGB. Could it be just the no-brand cheap WS2182b strips itself that wont handle the data? Maybe i should by the real adafruit, i read about so many problems with cheap strips, but you had never any issues with the skinny adafruits right? so maybe worth the money but they are so freaking expensive..

  8. #8

    Default

    You cannot remap the strip controller codes. They are set in stone. You can however, change your color configs in the config for each bank, as well as the main override file (where I think all the color profiles are stored for color changing functions).

    Here is paste from Prism P. 34:

    Ledstrip color definition - Color Order
    For a ledstrip, the color of the blade and FoC are defined by the same keywords and technique as high-power LEDs. Color profiles are set with a list of 3 numbers defining the color mix of R, G and B using the keyword color and fcolor (FoC). For standard blade color definition (config.txt) the same color mix is defined by the keywords drive and fdrive.
    The color order is however specfic in the case of a ledstrip as you cannot remap the way the strip controller codes colors. We've kept the classic RGB order which works for all the pixels we've tested except the PL family which will be GRB.
    For instance, a red blade using regular Neopixels would be defined by :
    drive=1023,0,0 <per font color definition>
    or
    color0=1023,0,0 <color profile 0>
    Tom

    "Let the past die."

  9. #9

    Default

    cheap strips can be spotty. I have bought good ones ane bad ones. I really wish we could get standard strips that are trustworthy, but right now its a crapshoot. I"ve been buying from Fleabay and here lately have mostly had good luck. Don't toss your prism out, most of the problems might be those strips. Yeah this stuf is expensive. I built 2 neopixel Kylos and the one guy was like is it done yet? I had to look at him as Anakin looked at the Tusken Village, but was able to gain control again. My frustration was I ran into bad strips back to back, and then the intelliblade I bought didn't work either. So I had spent about 400 bucks in stuff that didn't work.

    There are decent strips out there. You can buy the adafruit ones that will work for sure, or take another stab at some more Chinese strips. I'd post a link but this is TCSS site. NO can do. I hope you get better strips. PS, the way you say they are acting, you could have a bad pixel on one of your stirps. Is the weird behavior on both sides of the strips or only on one side. Does it start in a specific spot, or is the whole entire length of the strip involved?

    Tom

    "Let the past die."

  10. #10

    Default

    Ok I tried various drive settings, especially 0, 1023, 1023/ 0, 1023, 0/ 0, 0, 1023/ 1023, 0, 0. They all light up red. As I tried to set various foccolours i tried fdrive 0, 1023, 0/ 1023, 1023, 1023/ 1023, 0, 0/ 0, 0, 1023. All of them light up white. Furthermore i noticed that at pulling the kill key theres one short initial flicker of white over all the strip for a short half second or sth.

    Yes thats what i meant, i guess its the chinese strips itself that cant handle the data well. They light up from the first pixel to the very end of the strip evenly in red with a slight flickering, getting worse on the green setting. On both strips its the very same behaviour. I already clipped the first two pixels of both strips to make sure they arent fried or defect. But i think i will buy adafruits now instead of trying more cheap ones.. thats frustrating...

    and btw.. thanks so much for these prompt answers, i appreciate that so much
    Last edited by erazer; 08-03-2018 at 06:36 AM.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •