just upgraded my proffie board to 6.5 using Megatooths tutorial. installed it and my saber was working perfectly fine for the past couple days. randomly when I turned it on the ignition would play but then nothing else would happen motion wise, swings clashes no nothing the only things that would work were things that didn’t use motion. any idea why this is happening?
Could it be the same as this thread?
The advice is the same, add the ENABLE_DIAGNOSTIC_COMMANDS, and once the problem occurs, run the i2cstate command and post the output here.
Also, we may need to see your config file, so posting that would also be helpful.
it’s similar to his yes nothing that has to do with moving the saber works. I tried plugging it into the computer to see if the motion works when its plugged in but the audio is so bad I honestly can tell what even happening.
Heres the config file Config File - Pastebin.com
You might need to connect the battery too, but really, it’s the serial monitor that will tell you what’s going on, not the sound.
couple questions. I thought plugging in the saber while the battery is in could damage the board? I put the define onto the board. how do i use the command?
No, plugging in the saber while the battery is in will not damage the board.
To use the command, you enter it in to the serial monitor.
As soon as I plug the saber in it starts spamming I guess that’s the problem? xD
“Motion chip timeout, trying auto-reboot of motion chip!
Motion setup … Motion chip timeout, trying auto-reboot of motion chip!
Motion setup … Motion chip timeout, trying auto-reboot of motion chip!
Motion setup … Motion chip timeout, trying auto-rMotion setup … Motion chip timeout, trying auto-reboot of motion chip!
Motion setup … Motion chip timeout, trying auto-reboot of motion chip!
Motion setup … Motion chip timeout, trying auto-reboot of motion chip!
Motion setup … Motion chip timeout, trying auto-reboot of motion chip!
Motion setup … Motion chip timeout, trying auto-reboot of motion chip!
Motion setup … Motion chip timeout, trying auto-reboot of motion chip!
Motion setup … Motion chip timeout, trying auto-reboot of motion chip!
Motion setup … Motion chip timeout, trying auto-reboot of motion chip!
Motion setup … Motion chip timeout, trying auto-reboot of motion chip!”
And what does the “i2cstate” command say?
Hopefully this is helpfull
Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Playing Bank01/swingl01.wav
channels: 1 rate: 44100 bits: 16
Playing Bank01/swingh01.wav
channels: 1 rate: 44100 bits: 16
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
I2CBUS: last_request = 1033635 (now = 1033995) i2c_detected_ = 1 used = 1
I2C STATE: 8
current: 536881456 id= 106 next= 0
LSM6DS3H: last_event_ 0 LINE: 207
last: 536881456 id= 106 next= 0
LSM6DS3H: last_event_ 0 LINE: 207
Motion requested: 1 (millis() - last_motion_request=27419)
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... EVENT: Power-Pressed#1 ON millis=1035045
EVENT: Power-Pressed ON millis=1035045
EVENT: Power-Released#1 ON millis=1035174
EVENT: Power-Released ON millis=1035174
EVENT: Power-Shortclick#1 ON millis=1035174
EVENT: Power-Shortclick ON millis=1035174
Motion chip timeout, trying auto-reboot of motion chip!
EVENT: Power-SavedShortclick#1 ON millis=1035353
unit = 4 vol = 0.50, Playing Bank01/blst02.wav
channels: 1 rate: 44100 bits: 16
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Battery voltage: 4.03
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Playing Bank01/hum01.wav
channels: 1 rate: 44100 bits: 16
Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ... Motion chip timeout, trying auto-reboot of motion chip!
Motion setup ...
So this means that no motion events have been generated since boot, which is different from the other thread. It seems odd that it would be random though. It could be a problem with the motion chip, or possibly some sort of short on one of the I2C pads on the board. (Like maybe they are touching the chassis from the inside?)
The board is on a Crimson Dawn chassis and it doesn’t seem like anything is touching any sort of metal. the whole thing is plastic. I’m not sure what could be wrong with it.
Does it work again if you install ProffieOS 5.9 again?
nope, same issue
So what were you running before when it was working?
when I got the saber it was in 5.9 worked fine. I updated it to 6.5 a few days ago, worked fine no issues. day later, turned it on and no motion was registering. it could be something to do with a bad 6.5 update job on my part but even after switching it back to 5.9 it didn’t work.
Did the saber come with a copy of 5.9 on the SD card?
If you so, use that copy and see if it works any better?
it had a Config file in the SD card that came with the saber along with the actual sound contents. I formatted the sd card and replaced it with the stock SD card and Changed the config file to the one it came with.
Still same issue 
I think you should try reaching out to Crimson Dawn.
I’m not sure if this is something they (or LGT) caused, or if if it’s something you caused while doing the update, but it doesn’t sound like it’s a bug in the software, since going back to 5.9 doesn’t make it work again.
1 Like
ill reach out to them. thank you for the help 