FX-Sabers.com

The S.A.B.E.R. GUILD: Saber Manufacturers => Plecter Labs => Sound boards technical issues / questions / problems => Topic started by: pakken on August 06, 2019, 12:05:53 AM

Title: Prizm 5.5 - Aux issue (clash only registers)
Post by: pakken on August 06, 2019, 12:05:53 AM
I have an issue with my Prizm 5.5, would appreciate if anyone could help. When I press the Aux, somehow the blaster block registered as clashes, any idea what could be the cause? The fonts remained unchanged (in terms of the naming), tapping on the saber to clash is fine but no blaster block, been at it for hours trying to figure it out.

I hope it's not a board issue


(https://i.ibb.co/x2PfwpB/issue.jpg) (https://ibb.co/x2PfwpB)
Title: Re: Prizm 5.5 - Aux issue (clash only registers)
Post by: erv on August 06, 2019, 01:08:29 AM
make sure your remove un necessary files from the sd card package like the archive and the PDF. I also suggest you turn file extension on in your file manager to ensure what files are what type.
Finally, the best is to log the TX output of the board with a serial terminal (and a RICE cable or any serial to USB adapter, 3.3V version) to read the log and see what file is played when you get that issue happening. set debug=1 in your override file to enable a more verbose output.
Also make sure your sd card was fully formatted before re installing the package you're working on (minus the un necessary files) is copied back on it.
Title: Re: Prizm 5.5 - Aux issue (clash only registers)
Post by: pakken on August 06, 2019, 10:03:16 AM
The .RAR and .pdf files haven't messed with the card.  Been doing it for all of the boards (to have a respective config files in .rar and .pdf) as I have plenty of space on the SD card and it just ignores them.  It's good to have just in case if anything happens.

I figured out what the problem is, it's the Battery.  I need to fully charge the thing because when blaster block I heard has a bit of crackling, it becomes a clash when pressing the AUX and clash when tapping the saber makes no difference.  Anyways, false alarm just wanted to pass that information


Furthermore, I realized that less than an hour the battery drained and the crackling is heard... is there a way to extend the battery life?  I believe it has to do with the LED output, I may need to knock it down a few notches.  Please let me know
Title: Re: Prizm 5.5 - Aux issue (clash only registers)
Post by: erv on August 06, 2019, 10:13:55 PM
That would make sense (sound wise). Overall I'd suggest to use a better battery with more capacity.
Title: Re: Prizm 5.5 - Aux issue (clash only registers)
Post by: pakken on August 14, 2019, 08:44:28 PM
The battery drain is too much.... by any chance could you modify the color profile to make where it doesn't draw too much power to the LED, make it more like Prizm v4 friendly?  And that you can modify the Color Profiles so I can just copy into the Prizm 5.5?

Prizm V4
## Color profiles
color0=0,940,0
fcolor0=940,430,0
color1=0,0,940
fcolor1=900,0,940
color2=940,0,0
fcolor2=0,630,400
color3=0,830,400
fcolor3=700,940,0
color4=840,0,630
fcolor4=0,0,940
color5=940,430,0
fcolor5=0,940,0
color6=740,930,0
fcolor6=0,740,600

Prizm V5.5
## Color profiles
color0=1023,0,0
fcolor0=1023,1023,1023
mcolor0=001
color1=1023,255,0
fcolor1=1023,1023,1023
mcolor1=111
color2=1023,660,0
fcolor2=1023,1023,1023
mcolor2=111
color3=340,1023,0
fcolor3=1023,1023,1023
mcolor3=111
color4=145,1023,0
fcolor4=1023,1023,1023
mcolor4=111
color5=0,1023,0
fcolor5=1023,1023,1023
mcolor5=010
color6=0,1023,340
fcolor6=1023,1023,1023
mcolor6=111
color7=0,1023,635
fcolor7=1023,1023,1023
mcolor7=111
color8=0,1023,1023
fcolor8=1023,1023,1023
mcolor8=110
color9=0,0,1023
fcolor9=1023,1023,1023
mcolor9=100
color10=115,0,1023
fcolor10=1023,1023,1023
mcolor10=111
color11=355,0,1023
fcolor11=1023,1023,1023
mcolor11=111
color12=1023,0,1023
fcolor12=1023,1023,1023
mcolor12=101
color13=1023,0,50
fcolor13=1023,1023,1023
mcolor13=111


Please make the max value to be 940 and that the color change is the same but less draw on the pushing the LEDs.  Would greatly appreciate the help.  Thanks!
Title: Re: Prizm 5.5 - Aux issue (clash only registers)
Post by: K-2SO on August 14, 2019, 10:20:41 PM
Why donít YOU modify the profiles to be the values you want?? You can just as easily edit the Color profiles as any of us could.
Title: Re: Prizm 5.5 - Aux issue (clash only registers)
Post by: pakken on August 15, 2019, 12:27:23 AM
Why donít YOU modify the profiles to be the values you want?? You can just as easily edit the Color profiles as any of us could.

I'd like to keep it as stock and consistent as much as possible.  I'm not understanding which value is safe without ruining the configuration.  I asked for help
Title: Re: Prizm 5.5 - Aux issue (clash only registers)
Post by: EXAR KUN on August 15, 2019, 08:50:46 AM
My friend, what you can do is this:

Take all the '1023' numbers you see and reduce them to 800.

Don't forget to copy your files first, so you have the original text config files just in case something goes wrong.


Once you reduce all those 1023's to 800's, see if that helps your situation. Of course, the light from your hilt might appear slightly less bright.
Title: Re: Prizm 5.5 - Aux issue (clash only registers)
Post by: pakken on August 15, 2019, 10:14:58 AM
The colors may not look consistent... There are other values like color and mcolor.  I'm hoping more like V4 friendly in terms of LED intensity.  I don't want to make sudden changes without his help.  Any way to knockdown a bit of the intensity off the LED and hoping a consistent color profile that I could just copy and load it to the SD card.  The V4 I like, but it's missing a lot of the color profiles and hoping they would be filled in to compensate Prizm 5.5
Title: Re: Prizm 5.5 - Aux issue (clash only registers)
Post by: Forgetful Jedi Knight on August 15, 2019, 05:20:55 PM
Why donít you just take, say 10% off of each of the numbers and use those. Also the Mcolor parameters wonít need to be touched.
Title: Re: Prizm 5.5 - Aux issue (clash only registers)
Post by: erv on August 15, 2019, 11:23:09 PM
Prizm 4 profiles were pretty much 8-9% off from the max drive (1023).
As proposed above you can simply knock 5 or 10% off from the colours defined in v5 to reduce intensity in current while preserving color.
Keep in mind that the drive is just a remote: the maximum current on each die obscure LED is defined by the external resistor to the led. If you have an excess of current the resistor could have to be adjusted, or eventually a better battery be used.