I just received my first proffie saber core from LGT, not the highest quality I know, but I’m on a budget. The saber was working fine and then I plugged it into my PC to try the proffie workbench. That did not work so I changed the USB type in IDE to “Serial+mass storage+webusb” since then, my saber will not ignite or respond at all. I’ve done the boot&reset dance a few times and now the saber is recognized by IDE and my computer as a proffieboard, and even connects to the workbench, but the workbench is not able to load any tracks or presets, and the controls do nothing. I also cannot use the IDE serial monitor to command the saber “on” either. I’m not sure what the problem is and any help would be greatly appreciated, as I cannot find a similar situation out there. TIA
Have removed the sd card to see if it’s corrupted? When using mass storage you need to dismount the SD card before flashing the board this can cause corruption of the SD card. Remove the battery or flick the Killswitch off. Remove the SD card add insert it into computer.
Changing the USB type doesn’t actually do anything unless you hit “upload”.
Did you upload?
Yes I forgot to mention that I did upload after that, which is when the saber went unresponsive
I did not remove the SD when I flashed the board, but I just removed it and inserted it into my PC and it reads just fine so I don’t think it’s corrupted
You don’t have to physically remove it when flashing the board, just dismount it from the system tray when you have mass storage selected,
gotcha, that makes more sense, my other saber is CFX so this is all very new to me. After reinserting the SD, the saber is still unresponsive even though it is recognized by IDE
The workbench connects to the saber in some capacity as it brings up the home page for the controls and such, but it’s stuck on “waiting to list presets” and “waiting to list tracks” the battery percentage also is not shown and none of the controls work
What was the purpose of your flashing it was you adding fonts or updating the OS? Did you use the config file provided on the SD card?
I actually might have gotten my terminology wrong. A recap of events was that I initially wanted to see how the workbench works, but I needed to update the USB type to webusb in order for that to work, so I went into IDE, changed the USB type and hit upload, after that the saber has not worked. Since then I have done the Boot/Reset dance and uploaded from IDE successfully but still no response from the saber. When trying to use the config file that is on the sd card in proffieOS, IDE can’t find the file, even though everything is spelled correctly, my assumption is because the file is named “sd config” instead of just “config” and the space is causing issues. So I have not been able to reupload the OS to the saber, which might be the problem
Did u make a copy the config file from the sd card and paste it into the config folder within the proffieOS folder, the “sd config” in an lgt sd card is a folder, inside that are the config files you need to use just the .h file, 32 or 36 depending on the blade length
always always hit compile (tick) button to check for errors before uploading to the saber
I did that about 4 times, and re-downloaded proffieOS just as many, and now suddenly it works! Not sure what changed or how, but it is functioning like normal now!
Might have just been that you went through and named the inputs of those different ports the same.
When I did that I noticed that it would still be able to upload to both ports, but only the new port that I made worked.
Even though it would recognize the Proffie Board I had it defaulted to using the original type of port to upload through.
Obviously it wasn’t uploading because it was trying to do it through a different type of port. I just looked at the different ports available & there was a different one with the same that actually uploaded it.
And always always hit compile first!
Why? When you hit upload, it also compiles.
I mean like compile a sketch before you compile an upload!
Basically Verify the .h file before you upload. I’ve haven’t had too serious problems, but one time I had copied/pasted some blade styles from a custom saber I got. A good number of them had a code that I couldn’t submit in a style editor, but they still uploaded just fine. I had some issues with it not lining up with things like effect swings, & the sound font smooth swings, accent swings, ect.
Tried to do a sketch of it & it wouldn’t work. Had to mess around the the blade style code. Looked like they had some repeating effects on them that I took out & everything was fine. Multi-Phase stuff I’ve been reading about lately maybe?
I don’t know, but before I got on here I was watching a Sabertrio vid learning about all this & that’s one of the things it said when uploading to a Proffie.
Ok, but why?
What you’re saying is wrong, ill-founded, and/or simply confused, to risk sounding perhaps overly-harsh.
You don’t compile a header file, and as profezzorn stated, Arduino will recompile ProffieOS whenever you try to upload. There’s no reason to verify first if you’re going to upload anyways.
You can read up on C++, Arduino, and the compilation process if you’re really interested in it, but generally it’s more than you need to know to use proffie.
Just know that it’s unnecessary to do what you’re saying.
Sorry, still somewhat new to this.
Just some of the info I got from some training vids from Sabertrio.
@MFBoom All good man.
Simply put, if you watch the upload, you’ll see it’s compiling, just like verify does.
What people are saying is that you are somewhat “wasting your time” if you verify AND upload because you’re already doing the verify step as part of the upload process.
If it comes across a problem, it’s going to give you an error either way.
You can’t upload a failed compile, so there’s no “danger”.
Makes sense?
Yeah it makes sense.
Just still in the “Cautious Phase” I guess, because some stuff still in the learning phase.