My new config uploaded properly but none of the blades are lighting up. Posting here in hopes that someone can spot the issue
The hilt is a sabertrio with removebale core running a proffie 2.2
#Sabertrio Proffieboard Support
paper pebble
frozen dome
you can just drop the .h into chat, pastebin is a pain.
paper pebble
Whoops! the Facebook people always want pastebin lol
frozen dome
are you sure that the blade array is set up correctly for how your saber is wired.
paper pebble
I assumed it was, I’m using the config provided by S3
I was wondering if I had implemented the subblades correctly. The config is essentially a merged version of one of mine and their default one
This was my first time with subblades
frozen dome
This is what I'm seeing for their blade array in the default config I pulled from their support section:
hmm... you sure it's a v2.2 proffie, because when I just ran your config through the compiler it shows an overflow error. Meaning the config is too large for the board.
paper pebble
Yes I uploaded it as a v2 in arduino.
If you have the newest update on arduino it overflows faster than if you’re running an older one
I downgraded for that very reason
Running it through v2 it comes up as 99% capacity. V3 is much less, like on the 80% range
paper pebble
Yeah that’s probably right. I was just guessing to be honest
frozen dome
hmm... it's been a while since I set up subblades so I can't quite remember the process. all I can really say is verify the correct power pins and data pins are defined.
paper pebble
Yeah that’s probably right. I was just guessing to be honest
I had about 10 more fonts on there when I set it up for a v3. I took them off to fit it into v2, so I didn’t remember the exact numbers
frozen dome
still compiles, so not an issue there, so it's most likely how the blade array is configured vs how it's physically wired in. I do note the stock config from their support page shows 4 blades while yours shows 3.
paper pebble
Yeah, the 4th blade is for the Quillons, which my hilt doesn’t have
I took out the quillon blade styles to save space, changed the blade number to 3, and greyed out the quillon blade array with //
So I think that’s all good
frozen dome
so wouldn't you be able to take the setup out of subblade then?
paper pebble
Yeah I think so, but I wanted to leave it in case I ever needed it in the future
Just so I didn’t have to rewrite it or go searching in my config archive
I didn’t think it would be a problem because the primary style for that blade is the button and the secondary is the quillons so the board is still being told to use pixels 0-0 of blade 2 for the button
I’ll mess around with the power pads in a bit and see if that’s doing it too. Needed a break to clear my headache lol
frozen dome
I'd set it up like this just in case there is an issue with not having the second subblade:
paper pebble
Good call
frozen dome
but yeah, worth verifying the power pins and data pins defined are correct as well.
quaint oak
Three power pins for quillions seems overkill
I don’t know if not having the rest of the subblade would cause issues. That’s unfounded though.
frozen dome
yeah, no clue. all just a guess.
paper pebble
Update: removing the subblade wording and allowing the button to be its own individual blade did not solve the issue
quaint oak
Did you by chance put the battery in backwards or something?
I would say to try whatever config you last know was working. If it doesn’t, I’d guess something physical.
frozen dome
probably be other issues presenting if that were the case.
paper pebble
Yeah the sound comes on and I can cycle through all the fonts and tracks like normal, not the battery hahaha
It could be that the battery is a lower drain battery. I have another on the way, but after playing around audio only for 10 min it’s still reading over 75% charge. Plus I’m not using a blade right not, just testing with the lighting of the hilt
quaint oak
probably be other issues presenting if that were the case.
Not really. Everything else is protected.
frozen dome
eh, still, if he did blow a FET by that means, it would be visible on the board.
quaint oak
Not a FET
paper pebble
It’s the only battery I have out of storage right now (moving) but it was confirmed to work with the hilt (not blade) using the original default config that was on it when I received it
paper pebble
The chassis has very clearly marked + and - as does the battery lol
frozen dome
don't see how since power flow wouldn't be moving. part of the circuit still goes through the board.
quaint oak
The MOSFET body diodes
paper pebble
Def didn’t reverse the battery lol
I’ve fried a board doing an install. This wasn’t that I promise you lol
quaint oak
It’s the only battery I have out of storage right now (moving) but it was confir...
And that (config) doesn’t work anymore? Have you tried it?
paper pebble
I don’t have it
What I have is the default from S3 which should work but currently isn’t
But I’ve modified it too. I have the original default that I’ll put on if we can’t find the error in this one
But I’m 100% sure the issue is in the coding and not physical.
quaint oak
Your maxLedsPerStrip isn’t set high enough for the blade length
paper pebble
Thanks for the tip, what should it be for a 36” quantum?
Surely that wouldn’t affect all the lights on the hilt though, right?
quaint oak
I don't know how ProffieOS responds to that. It could just bail
quaint oak
Thanks for the tip, what should it be for a 36” quantum?
Surely that wouldn’t a...
Just set it to what the blade is set for
151
frozen dome
I think it's around 132, the 4 lines of pixels are mirror.
quaint oak
Oh, but yeah if that was random and it's a quantum then it should probably be lower (the blade length, not maxLedsPerStrip
frozen dome
yeah, 132. Info is thankfully on TCSS's page,
or wait, says 34", did they make a 36" one?
quaint oak
probably 36" with the blade tip and PCB 'n' stuff
If you're looking at the stick listing
frozen dome
quantum didn't have one of those tho, that was the KRv3. eh, doing the math, if it is 36", based off the pixel per inch it would be about 140.
quaint oak
quantum didn't have one of those tho, that was the KRv3. eh, doing the math, if...
No, like, the actual blade tip
the polycarbonate
quaint oak
@paper pebble Yeah proffie just bails whenever you've got it set wrong
Looks like it'd stop outputting to all blades.
Well, probably not
But it'd cause issues for the one blade at the very least.
frozen dome
you'd think it would error if it was mismatched like that in the compile process.
quaint oak
Hilariously there's a static assert in WS2811BladePtr but not WS281X
paper pebble
Okay so to clarify- the issue is that my define section sets it to 144 and the blade array has it set to 151?
quaint oak
Yeah
paper pebble
The mismatch makes it bail?
quaint oak
At least one of them
quaint oak
The mismatch makes it bail?
Not mismatch. The value in CONFIG_TOP is a max value.
So it needs to be more than the blade value.
frozen dome
the define is the upper limit so should be higher than the blade array number anyway.
paper pebble
Oh okay so then I need reduce the array to under 144 or increase the max to above 151?
frozen dome
correct, see if that gets it working.
paper pebble
You guys are awesome, I’ll try that right away
frozen dome
Ry spotted it, I missed it.
paper pebble
I just changed the max to 155, that’s what the s3 default is
Waiting to see now
Uploading
frozen dome
paper pebble
Thanks you guys, it worked! Would have sent the message sooner but I was having way too much fun playing with it lol
quaint oak
Yknow, that’s the kind of stuff ProffieConfig is real good about taking care of automatically 😛
quaint oak
Thanks you guys, it worked! Would have sent the message sooner but I was having ...
Glad to hear 🙂
Glow stick go brr
paper pebble
What is ProffieConfig
quaint oak
A tool, that does stuff for proffieboards.
||There's fancier words on the website||
paper pebble
That’s awesome dude! You made this? Is this relatively new tool? I would have loved to get my hands on this back when I was starting!
quaint oak
That’s awesome dude! You made this? Is this relatively new tool? I would have lo...
I did!
It’s something like 2.5 years old now, but it’s improved a lot 🙂
paper pebble
Thanks a lot for doing that! So this basically replaces arduino? Can it flash the board or does it just verify the config (and suggest fixes) before using arduino