FX-Sabers.com

The S.A.B.E.R. GUILD: Saber Manufacturers => Plecter Labs => Topic started by: Ben300 on January 10, 2020, 01:44:34 PM

Title: CFX Motion Sensor going haywire
Post by: Ben300 on January 10, 2020, 01:44:34 PM
I'm having a bit of an issue with my saber. I purchased a Sabertrio Neo saber, which uses a CFX board (and a neopixel setup). Out of the box, it worked fine. However, after installing a new soundfont, I noticed that sometimes the motion sensor would start acting up, and when the blade was ignited it would start making sounds as if I was swinging the blade around wildly even if I wasn't moving it at all. In an effort to fix it I tried restoring the settings with RICE, but now the issue has not only not gone away, but it's happening all the time with every soundfont no matter what. I tried upgrading the firmware to the latest beta (1.0.003), but it didn't fix the issue (in fact it made it so the blade wouldn't even turn on at all), so I reverted back to what the saber came with (1.0.001)

I've read in a Facebook post from Sabertrio that this might be caused by an issue with the motion sensor, but it's mainly a software issue. From their post:

Quote
[CFX MOTION SENSOR GLITCH]

There has been a handful of reported cases where a Crystal Focus X equipped Neo Saber would exhibit one of the following symptoms:

- Clash sounds triggering even though the saber is stationery.
- Smoothswing sounds going haywire.
- No swing sounds playing.

The reason for this is due to a production variance of the on board motion sensor where certain pieces required just a little more time than what was given during the boot stage to initialize. Further compounding this was that battery charge level also played a part in influencing the timing required which made this issue hard to detect during production quality checks and testing. As a result, the motion sensor did not properly reset and started given false readings which then creates the symptoms as described above.

Since it was sort of working out of the box, is there perhaps something I can do to fix it manually on my end? I'm kind of new to this whole saber stuff, so any help would be appreciated. It would suck to have my first saber already struck by hardware issues ^^
Title: Re: CFX Motion Sensor going haywire
Post by: erv on January 11, 2020, 12:29:46 AM
I'm having a bit of an issue with my saber. I purchased a Sabertrio Neo saber, which uses a CFX board (and a neopixel setup). Out of the box, it worked fine. However, after installing a new soundfont, I noticed that sometimes the motion sensor would start acting up, and when the blade was ignited it would start making sounds as if I was swinging the blade around wildly even if I wasn't moving it at all. In an effort to fix it I tried restoring the settings with RICE, but now the issue has not only not gone away, but it's happening all the time with every soundfont no matter what. I tried upgrading the firmware to the latest beta (1.0.003), but it didn't fix the issue (in fact it made it so the blade wouldn't even turn on at all), so I reverted back to what the saber came with (1.0.001)

I've read in a Facebook post from Sabertrio that this might be caused by an issue with the motion sensor, but it's mainly a software issue. From their post:

Quote
[CFX MOTION SENSOR GLITCH]

There has been a handful of reported cases where a Crystal Focus X equipped Neo Saber would exhibit one of the following symptoms:

- Clash sounds triggering even though the saber is stationery.
- Smoothswing sounds going haywire.
- No swing sounds playing.

The reason for this is due to a production variance of the on board motion sensor where certain pieces required just a little more time than what was given during the boot stage to initialize. Further compounding this was that battery charge level also played a part in influencing the timing required which made this issue hard to detect during production quality checks and testing. As a result, the motion sensor did not properly reset and started given false readings which then creates the symptoms as described above.

Since it was sort of working out of the box, is there perhaps something I can do to fix it manually on my end? I'm kind of new to this whole saber stuff, so any help would be appreciated. It would suck to have my first saber already struck by hardware issues ^^

Hello ben (thank you for your first post here),
I indeed have 2 boards that got reported to have that issue and the 10.003 fixed the issue clearly.
Do you mean that the issue is still there after updating (to the version from yesterday) ?


as for the saber not lighting up, you need to read the fw changelog and adjust your timings. A lot of things have changed since 10.001. It's now stabilizing in the config structure and parameters, and sabertrio (like others) will soon produce a standard package for their saber relative to the current fw version. But until we get a stable release, you have work to do in your configs.

Please let me know about the sensor. The 10.003 did fix the clash issue for us. For the gyro (unwanted swings) we don't have a board with that issue on hands, and it's still unknown if it's a HW issue or not.

Title: Re: CFX Motion Sensor going haywire
Post by: Ben300 on January 11, 2020, 02:03:25 AM
I'm having a bit of an issue with my saber. I purchased a Sabertrio Neo saber, which uses a CFX board (and a neopixel setup). Out of the box, it worked fine. However, after installing a new soundfont, I noticed that sometimes the motion sensor would start acting up, and when the blade was ignited it would start making sounds as if I was swinging the blade around wildly even if I wasn't moving it at all. In an effort to fix it I tried restoring the settings with RICE, but now the issue has not only not gone away, but it's happening all the time with every soundfont no matter what. I tried upgrading the firmware to the latest beta (1.0.003), but it didn't fix the issue (in fact it made it so the blade wouldn't even turn on at all), so I reverted back to what the saber came with (1.0.001)

I've read in a Facebook post from Sabertrio that this might be caused by an issue with the motion sensor, but it's mainly a software issue. From their post:

Quote
[CFX MOTION SENSOR GLITCH]

There has been a handful of reported cases where a Crystal Focus X equipped Neo Saber would exhibit one of the following symptoms:

- Clash sounds triggering even though the saber is stationery.
- Smoothswing sounds going haywire.
- No swing sounds playing.

The reason for this is due to a production variance of the on board motion sensor where certain pieces required just a little more time than what was given during the boot stage to initialize. Further compounding this was that battery charge level also played a part in influencing the timing required which made this issue hard to detect during production quality checks and testing. As a result, the motion sensor did not properly reset and started given false readings which then creates the symptoms as described above.

Since it was sort of working out of the box, is there perhaps something I can do to fix it manually on my end? I'm kind of new to this whole saber stuff, so any help would be appreciated. It would suck to have my first saber already struck by hardware issues ^^

Hello ben (thank you for your first post here),
I indeed have 2 boards that got reported to have that issue and the 10.003 fixed the issue clearly.
Do you mean that the issue is still there after updating (to the version from yesterday) ?


as for the saber not lighting up, you need to read the fw changelog and adjust your timings. A lot of things have changed since 10.001. It's now stabilizing in the config structure and parameters, and sabertrio (like others) will soon produce a standard package for their saber relative to the current fw version. But until we get a stable release, you have work to do in your configs.

Please let me know about the sensor. The 10.003 did fix the clash issue for us. For the gyro (unwanted swings) we don't have a board with that issue on hands, and it's still unknown if it's a HW issue or not.

Thanks for the reply

I tried updating the firmware again and fiddling with the settings. The blade not lighting up was indeed an error on my part, I didn't set the ledstrip parameter correctly. However, after doing the update this morning the motion sensor is not working at all now. It still recognizes clashes, but no swing sounds. Also the dragtip leds don't light up anymore. Meaning, when I set the ledstrip to 120 and the dragstrip to 20 (the blade has 140), those 20 leds at the tip of the blade don't light up.

I've tried reverting back to the firmware Sabertrio put in, the 1.0.001, but the issue remains the same: no swing sounds anymore. I'm honestly not sure if this is actually a software issue, or I got unlucky and got a defective gyro :(
Title: Re: CFX Motion Sensor going haywire
Post by: erv on January 11, 2020, 02:38:22 AM
blade lenght in your case would be 140. Drag tip defines the size from the tip (as before).

thank you for confirming the issue you have about the gyro. It seems to be rather a HW issue with the gyro working or not working sometimes. I'll try to work with another person facing the same issue to try several FW experiments, to get a further diag of what is happening, then I'll keep people posted here for sure
Title: Re: CFX Motion Sensor going haywire
Post by: Ben300 on January 11, 2020, 03:30:58 AM
blade lenght in your case would be 140. Drag tip defines the size from the tip (as before).

thank you for confirming the issue you have about the gyro. It seems to be rather a HW issue with the gyro working or not working sometimes. I'll try to work with another person facing the same issue to try several FW experiments, to get a further diag of what is happening, then I'll keep people posted here for sure

Much appreciated :)

I'm keeping the 1.0.003 firmware installed for now. Like I said: everything seems to work, clashes included. It's just the motions, like swings, that don't. I looked at the debug logs too, and I does print out attempts to play the swing sounds, but no sound actually occurs (and I don't think they match my movement either, so not sure if that's a sign that something is working or not).

If you need me to perform some tests and report the debug logs let me know.

Thanks again
Title: Re: CFX Motion Sensor going haywire
Post by: erv on January 11, 2020, 03:38:44 AM
really ? That's very interesting ? Would you mind emailing me your whole SD card structure please (zip archive by dropbox or other big file transfer service). If you get logs that it's trying to play sound but don't get them, it's something else and it means that the sensor is actually working.
Thank you
Title: Re: CFX Motion Sensor going haywire
Post by: Ben300 on January 11, 2020, 04:17:21 AM
really ? That's very interesting ? Would you mind emailing me your whole SD card structure please (zip archive by dropbox or other big file transfer service). If you get logs that it's trying to play sound but don't get them, it's something else and it means that the sensor is actually working.
Thank you

I mailed you my current SD card structure, and also an example log. Hope that helps ^^
Title: Re: CFX Motion Sensor going haywire
Post by: erv on January 11, 2020, 04:55:40 AM
thanks a lot. From the log, it's indeed playing the smoothswing pairs fact which isn't triggered by the motion sensor. I'll try your package to see if it shades new light to the issue then report and eventually have you try a couple of test FW if you're happy to do so
Title: Re: CFX Motion Sensor going haywire
Post by: Ben300 on January 11, 2020, 05:03:50 AM
thanks a lot. From the log, it's indeed playing the smoothswing pairs fact which isn't triggered by the motion sensor. I'll try your package to see if it shades new light to the issue then report and eventually have you try a couple of test FW if you're happy to do so

I'll gladly help out however I can ^^
Title: Re: CFX Motion Sensor going haywire
Post by: Ben300 on January 12, 2020, 11:33:03 AM
thanks a lot. From the log, it's indeed playing the smoothswing pairs fact which isn't triggered by the motion sensor. I'll try your package to see if it shades new light to the issue then report and eventually have you try a couple of test FW if you're happy to do so

Just wanted to add one more detail I've noticed. When running the readsensor command I'm getting different values from the sensor that appear to be somewhat reasonable. The initsensor command doesn't report any errors either. However, after running the readsensor command a few times in a row the board did hang on me, and I had to remove the battery to force it to restart. Again, I'm not sure if this says anything about the issue, but it might be useful to know.

The log from me running the commands:

Code: [Select]
DEBUG Enabled
 WHO_AM_I_M = 3D - WHO_AM_I_XG = 68
 XG boot ended
 MG boot ended
 ACX -409 ACY -4879 ACZ 6997
 ACX -314 ACY -4462 ACZ 6727
 ACX -300 ACY -4556 ACZ 6596
 ACX -307 ACY -4616 ACZ 6593
 ACX -278 ACY -4377 ACZ 6659
 ACX -301 ACY -4558 ACZ 6609
 ->SLEEP
...
Title: Re: CFX Motion Sensor going haywire
Post by: erv on January 12, 2020, 12:32:48 PM
thanks a lot for testing this. It's normal to have the sensor "crash" after polling it this way, that's a former test command that was never meant to be used in real time while the sensor is analyzed by the rest of the fw, but it remains handy to get some reading. I have to do the same for the gyro.

thank you for confirming again that the boot and init of the sensor go well, perfect !

would you mind testing those two voltages for me (with the black probe of the DMM on the main negative power supply pad of the CFX). That's more 14V you'll read on the +9V measure point.
thank you

(https://www.plecterlabs.com/Media/Doc/gyro-voltages.png)
Title: Re: CFX Motion Sensor going haywire
Post by: Ben300 on January 12, 2020, 01:11:02 PM
thanks a lot for testing this. It's normal to have the sensor "crash" after polling it this way, that's a former test command that was never meant to be used in real time while the sensor is analyzed by the rest of the fw, but it remains handy to get some reading. I have to do the same for the gyro.

thank you for confirming again that the boot and init of the sensor go well, perfect !

would you mind testing those two voltages for me (with the black probe of the DMM on the main negative power supply pad of the CFX). That's more 14V you'll read on the +9V measure point.
thank you

(https://www.plecterlabs.com/Media/Doc/gyro-voltages.png)

Unfortunately I don't have a DMM on hand. Also, Sabertrio put a warranty sticker on the board that covers part of it, so I can't do a reading without breaking it, and I'm not sure I wanna do that in case there is indeed a hardware fault and I need to return the saber. I'm not exactly an expert when it comes to installing sabers, so I don't trust myself with replacing the board on my own. Sorry about this :(
Title: Re: CFX Motion Sensor going haywire
Post by: erv on January 13, 2020, 09:06:51 AM
here's something to try
http://www.plecterlabs.com/Media/CFSounds/V10/firmware/beta/CrystalFocusX-v10-work-10.003C-TestGyro.zip (http://www.plecterlabs.com/Media/CFSounds/V10/firmware/beta/CrystalFocusX-v10-work-10.003C-TestGyro.zip)

that firmware will:
- deliberately pause at boot time for 2 seconds so that you have plenty of time for opening the serial port and observe the log
- display additional register contents info after initalizing the motion sensor
- log accel and gyro readings every 200 ms so that we can have a look to the values

set debug=0, info is printed regardless and that will make a shorter log with only what we need currently.

that's what you should have

[... some preamble with serial number etc]
Code: [Select]
SDHC init
high speed turbo mode clock = 50000000
SDHC turbo clock mode
File System Mounted OK
SDHC Init success
SPECS:Sectors 7744512 (3584MB)
SD Clock (CSD) 25000000 Hz
SD Clock 50000000 Hz
Type SD
SD Version 3.0
High Speed
Card Installed
Initialized
Plecter Labs Crystal Focus
v10.003C - 01/2020
Init Motion Sensor
XG boot ended: OK (waited 1ms)
M boot ended: OK (waited 1ms)
WHO_AM_I_M = 3D - WHO_AM_I_XG = 68
Success
Motion sensor Debug:
CTRL_REG1_G = 10111000
CTRL_REG2_G = 00000000
CTRL_REG3_G = 00000001
CTRL_REG4 = 00000011








Allocating DMA channel...DMA Ch# 0
Status: OK
I2S DMA Ch=0
I2S CLOCK source = 90312500
Setting up audio DMA transfer
Adding Audio DMA callback
[BOOT] Scanning SD contents:


then after boot ended (those are values for my motion sensor, board on the bench). Spinning / rotating the board or hilt should produce higher gyro numbers in the range of (easily or greater) 3000-5000 (peak is 32000 ish)

Code: [Select]
[BMP] found extra/UI/blade.bmp
[BMP] found extra/PLI/pli.bmp
[BMP] found extra/PLI/bar.bmp
[BMP] found boot.bmp
[ACC] -250 -27 7997
[GYRO] 28 26 18
[ACC] -242 -21 7992
[GYRO] 23 23 22
[ACC] 221 -25 7998
[GYRO] -24 -27 21
[ACC] 234 -33 8009
[GYRO] -26 -26 24
[ACC] 222 -40 8015
[GYRO] 22 23 22
[ACC] 226 -37 8005
[GYRO] 24 24 22
[ACC] 233 -18 8019
[GYRO] 24 27 23

Title: Re: CFX Motion Sensor going haywire
Post by: Ben300 on January 13, 2020, 09:46:28 AM
here's something to try
http://www.plecterlabs.com/Media/CFSounds/V10/firmware/beta/CrystalFocusX-v10-work-10.003C-TestGyro.zip (http://www.plecterlabs.com/Media/CFSounds/V10/firmware/beta/CrystalFocusX-v10-work-10.003C-TestGyro.zip)

that firmware will:
- deliberately pause at boot time for 2 seconds so that you have plenty of time for opening the serial port and observe the log
- display additional register contents info after initalizing the motion sensor
- log accel and gyro readings every 200 ms so that we can have a look to the values

set debug=0, info is printed regardless and that will make a shorter log with only what we need currently.

that's what you should have

[... some preamble with serial number etc]
Code: [Select]
SDHC init
high speed turbo mode clock = 50000000
SDHC turbo clock mode
File System Mounted OK
SDHC Init success
SPECS:Sectors 7744512 (3584MB)
SD Clock (CSD) 25000000 Hz
SD Clock 50000000 Hz
Type SD
SD Version 3.0
High Speed
Card Installed
Initialized
Plecter Labs Crystal Focus
v10.003C - 01/2020
Init Motion Sensor
XG boot ended: OK (waited 1ms)
M boot ended: OK (waited 1ms)
WHO_AM_I_M = 3D - WHO_AM_I_XG = 68
Success
Motion sensor Debug:
CTRL_REG1_G = 10111000
CTRL_REG2_G = 00000000
CTRL_REG3_G = 00000001
CTRL_REG4 = 00000011








Allocating DMA channel...DMA Ch# 0
Status: OK
I2S DMA Ch=0
I2S CLOCK source = 90312500
Setting up audio DMA transfer
Adding Audio DMA callback
[BOOT] Scanning SD contents:


then after boot ended (those are values for my motion sensor, board on the bench). Spinning / rotating the board or hilt should produce higher gyro numbers in the range of (easily or greater) 3000-5000 (peak is 32000 ish)

Code: [Select]
[BMP] found extra/UI/blade.bmp
[BMP] found extra/PLI/pli.bmp
[BMP] found extra/PLI/bar.bmp
[BMP] found boot.bmp
[ACC] -250 -27 7997
[GYRO] 28 26 18
[ACC] -242 -21 7992
[GYRO] 23 23 22
[ACC] 221 -25 7998
[GYRO] -24 -27 21
[ACC] 234 -33 8009
[GYRO] -26 -26 24
[ACC] 222 -40 8015
[GYRO] 22 23 22
[ACC] 226 -37 8005
[GYRO] 24 24 22
[ACC] 233 -18 8019
[GYRO] 24 27 23

Alright, installed the firmware, and this is what I got at bootup:

Code: [Select]
[DISPLAY] not found
 MCU serial #: E36C3981:53385333:35202020:FF0E393B
 SDHC init
 high speed turbo mode clock = 50000000
 SDHC turbo clock mode
 File System Mounted OK
 SDHC Init success
 SPECS:Sectors 31116288 (15872MB)
 SD Clock (CSD) 25000000 Hz
 SD Clock 50000000 Hz
 Type SD
 SD Version 3.
 High Speed
 Card Installed
 Initialized
 Plecter Labs Crystal Focus
 v10.003C - 01/2020
 Init Motion Sensor
 XG boot ended: OK (waited 1ms)
 M boot ended: OK (waited 1ms)
 WHO_AM_I_M = 3D - WHO_AM_I_XG = 68
 Success
 Motion sensor Debug:
 CTRL_REG1_G = 11111111
 CTRL_REG2_G = 10001111
 CTRL_REG3_G = 11111111
 CTRL_REG4 = 11111111
 Allocating DMA channel...DMA Ch# 0
 Status: OK
 I2S DMA Ch=0
 I2S CLOCK source = 90312500
 Setting up audio DMA transfer
 Adding Audio DMA callback
 [BOOT] Scanning SD contents:

Not sure what the motion sensor debug messages mean, but they don't match.

As for the motion sensor readings, they do seem reasonable. Here's me holding it still:

Code: [Select]
[ACC] 256 -1663 7791
 [GYRO] -86 -952 -17
 [ACC] 253 -1653 7812
 [GYRO] 101 946 -27
 [ACC] 266 -1669 7810
 [GYRO] 83 953 -18
 [ACC] 271 -1665 7821
 [GYRO] 90 961 -14
 [ACC] 278 -1642 7776
 [GYRO] 79 961 -18
 [ACC] -272 -1649 7788
 [GYRO] 95 950 -8
 [ACC] 234 -1662 7769
 [GYRO] -93 -954 -16

And me moving it left and right a bit:

Code: [Select]
[ACC] 1033 -2044 5245
 [GYRO] 90 956 -21
 [ACC] 2489 -3057 6388
 [GYRO] 92 961 -13
 [ACC] -1024 -716 9292
 [GYRO] 92 964 -14
 [ACC] 3199 -2534 7532
 [GYRO] 84 955 -11
 [ACC] 2332 -1852 5500
 [GYRO] -90 -940 -18
 [ACC] -1482 -4815 9694
 [GYRO] -93 -949 -20
 [ACC] 5098 -950 9553
 [GYRO] -84 -953 -20

I hope this helped a bit ^^
Title: Re: CFX Motion Sensor going haywire
Post by: erv on January 14, 2020, 02:27:30 AM
Another fw to try, it SHOULD provide proper readback of the sensor debug (in the middle of the boot log)

http://www.plecterlabs.com/Media/CFSounds/V10/firmware/beta/CrystalFocusX-v10-work-10.003C-TestGyro2.zip (http://www.plecterlabs.com/Media/CFSounds/V10/firmware/beta/CrystalFocusX-v10-work-10.003C-TestGyro2.zip)

please do the same as you did, ie hilt still, then hilt moving with shake/clash and some rotations. No need to have full amplitude moves, small gestures will work too
Title: Re: CFX Motion Sensor going haywire
Post by: Ben300 on January 14, 2020, 02:42:30 AM
Another fw to try, it SHOULD provide proper readback of the sensor debug (in the middle of the boot log)

http://www.plecterlabs.com/Media/CFSounds/V10/firmware/beta/CrystalFocusX-v10-work-10.003C-TestGyro2.zip (http://www.plecterlabs.com/Media/CFSounds/V10/firmware/beta/CrystalFocusX-v10-work-10.003C-TestGyro2.zip)

please do the same as you did, ie hilt still, then hilt moving with shake/clash and some rotations. No need to have full amplitude moves, small gestures will work too

Alrighty, installed that, and this is the boot log I got (including the whole thing just in case):

Code: [Select]
[DISPLAY] not found
 MCU serial #: E36C3981:53385333:35202020:FF0E393B
 SDHC init
 high speed turbo mode clock = 50000000
 SDHC turbo clock mode
 File System Mounted OK
 SDHC Init success
 SPECS:Sectors 31116288 (15872MB)
 SD Clock (CSD) 25000000 Hz
 SD Clock 50000000 Hz
 Type SD
 SD Version 3.
 High Speed
 Card Installed
 Initialized
 Plecter Labs Crystal Focus
 v10.003C - 01/2020
 Init Motion Sensor
 Reset Motion Sensor
 XG boot ended: OK (waited 1ms)
 M boot ended: OK (waited 1ms)
 WHO_AM_I_M = 3D - WHO_AM_I_XG = 68
 Success
 Motion sensor Debug:
 CTRL_REG1_G = 10111000
 CTRL_REG2_G = 0
 CTRL_REG2_G (second time) = 0
 CTRL_REG3_G = 0
 CTRL_REG4 = 111000
 Allocating DMA channel...DMA Ch# 0
 Status: OK
 I2S DMA Ch=0
 I2S CLOCK source = 90312500
 Setting up audio DMA transfer
 Adding Audio DMA callback
 [BOOT] Scanning SD contents:
 Found 19 FONT(S)
 Found tracks folder : /tracks
 (Last) Selected Sound Bank : 2
 [DEBUG] Enabled
 [DEBUG] Log Msg to PORT(s):USB
 Font Volume:100%
 Menu Volume:100%
 Beep volume:40%
 sleep:50000ms
 deep:61102ms
 orient=0
 switch polarity/type=2 / Mom. Switch
 Delayed offd=200 ms
 Delayed ond=20 ms
 swing_flow flow:360ms
 clash_flow flow:300ms
 spin_flow flow:400ms
 [SMOOTHSWING] smooth_flow:1000ms
 [MOTION] lockup activation=300 ms
 iSaber loop: 1
 iSaber shuffle: 2
 plilh range (mV)={3400 ; 4200}
 omnisabers Enabled
 bladepower:100%
 LedStrip Mode with = 140 LEDs
 Allocating DMA channel for Ledstrip generator...
 DMA Ch# 1
 Status: OK
 Ledstrip DMA Ch=1
 Adding Ledstrip callback - instance #0
 dragstrip:20
 strippower:15
 ls1 {0}=350 {1}=700 {L}=24
 ls1 Color Order: 1-GRB
 ls1 Color Space: (3)-RGB
 ls2_timings {0}=350 {1}=700 {L}=24
 ls2_timings Color Order: GRB
 ls2_timings Color Space: (3)-RGB
 [MOTION] gate=50
 [SMOOTHSWING] smooth_gate:50
 [MOTION] hswing=450
 [MOTION] hhybrid=550
 [MOTION] hforce=300
 [MOTION] hfclash=650
 [MOTION] hclash=850
 [MOTION] hstab=500, -20, 20
 [MOTION] hspin=750
 [MOTION] htwist=350
 [MOTION] hdrag=500, -90, 0
 [MOTION] htemp=40
 Profile Selection method #0
 Dial Axis: PITCH
 Reference Magnetic Field {10 ; 10 ; 10}
 [BLADE] Profile Section #0 found
 Wakeup En.
 ColorRandomizer:0%
 Random mode=2
 saberlock Saber:0
 Blaster Random=2
 shmrd dur.:50ms
 shmrp period:6ms
 shmrr Random:13ms
 shmr% Min Depth:0%
 shmr% Max Depth:50%
 focd dur.:50ms
 focp period:10ms
 focr random:10ms
 foc% Min Depth:0%
 foc% Max Depth:80%
 focl w/ Lockup
 focb w/ Blasters
 focf1 w/ Force
 focf2 w/ Force-Clash
 focf3 w/ StabFx
 flks Period:6ms
 flkd Depth:25%
 tridentflk:0%
 PWR ON w/ Flicker
 PWR OFF w/ Flicker
 pulsed Depth=0%
 pulsel Dur.:0ms
 LedStrip On Fade
 LedStrip Off Fade
 unstable:0
 style_pon:4
 style_poff:0
 style_lockup:2
 style_drag:2
 style_blaster:2
 style_flicker:2
 style_clash:3
 style_stab:4
 over_pon:1
 over_poff:1
 mapping_unstable:0
 mapping_lockup:1
 mapping_lockup:0
 mapping_flicker:1
 mapping_color:1
 pos_lockup:78
 size_lockup:143
 hcool:93
 lcool:0
 sparkf:141
 sparkd:29
 drift:1
 mapb:100
 mapc:70
 Strip FX Update @83 FPS or 12ms
 sbolt={8, 20}
 dbolt={40, 810}ms
 lbolt={15, 30}
 fbolt:1%
 rbolt=10%
 qbolt:30%
 [COLOR] Profile Section #0 found
 Main Color Profile #0=0, 1023, 0, 0,
 FoC Color Profile #0=1023, 1023, 1023, 0,
 Lockup Color Profile #0=1023, 1023, 0, 0,
 Bolt Color Profile #0=1023, 1023, 1023, 0,
 Crystal Color Profile #0=0, 1023, 0, 0,
 focmix config:7
 tridentm config:0
 [COLOR] Profile Section #1 found
 Main Color Profile #1=350, 1023, 0, 0,
 FoC Color Profile #1=1023, 1023, 1023, 0,
 Lockup Color Profile #1=1023, 1023, 0, 0,
 Bolt Color Profile #1=1023, 1023, 1023, 0,
 Crystal Color Profile #1=350, 1023, 0, 0,
 focmix config:7
 tridentm config:0
 [COLOR] Profile Section #2 found
 Main Color Profile #2=1023, 750, 0, 0,
 FoC Color Profile #2=1023, 1023, 1023, 0,
 Lockup Color Profile #2=1023, 1023, 1023, 0,
 Bolt Color Profile #2=1023, 1023, 1023, 0,
 Crystal Color Profile #2=1023, 750, 0, 0,
 focmix config:7
 tridentm config:0
 [COLOR] Profile Section #3 found
 Main Color Profile #3=1023, 450, 0, 0,
 FoC Color Profile #3=1023, 1023, 1023, 0,
 Lockup Color Profile #3=1023, 1023, 1023, 0,
 Bolt Color Profile #3=1023, 1023, 1023, 0,
 Crystal Color Profile #3=1023, 450, 0, 0,
 focmix config:7
 tridentm config:0
 [COLOR] Profile Section #4 found
 Main Color Profile #4=1023, 125, 0, 0,
 FoC Color Profile #4=1023, 1023, 1023, 0,
 Lockup Color Profile #4=1023, 1023, 1023, 0,
 Bolt Color Profile #4=1023, 1023, 1023, 0,
 Crystal Color Profile #4=1023, 125, 0, 0,
 focmix config:7
 tridentm config:0
 [COLOR] Profile Section #5 found
 Main Color Profile #5=1023, 30, 0, 0,
 FoC Color Profile #5=1023, 1023, 0, 0,
 Lockup Color Profile #5=1023, 1023, 1023, 0,
 Bolt Color Profile #5=1023, 1023, 0, 0,
 Crystal Color Profile #5=1023, 30, 0, 0,
 focmix config:7
 tridentm config:0
 [COLOR] Profile Section #6 found
 Main Color Profile #6=1023, 0, 0, 0,
 FoC Color Profile #6=1023, 1023, 0, 0,
 Lockup Color Profile #6=1023, 1023, 1023, 0,
 Bolt Color Profile #6=1023, 1023, 0, 0,
 Crystal Color Profile #6=1023, 0, 0, 0,
 focmix config:7
 tridentm config:0
 [COLOR] Profile Section #7 found
 Main Color Profile #7=1023, 0, 350, 0,
 FoC Color Profile #7=1023, 1023, 1023, 0,
 Lockup Color Profile #7=1023, 1023, 0, 0,
 Bolt Color Profile #7=1023, 1023, 1023, 0,
 Crystal Color Profile #7=1023, 0, 350, 0,
 focmix config:7
 tridentm config:0
 [COLOR] Profile Section #8 found
 Main Color Profile #8=1023, 0, 600, 0,
 FoC Color Profile #8=1023, 1023, 1023, 0,
 Lockup Color Profile #8=1023, 1023, 0, 0,
 Bolt Color Profile #8=1023, 1023, 1023, 0,
 Crystal Color Profile #8=1023, 0, 600, 0,
 focmix config:7
 tridentm config:0
 [COLOR] Profile Section #9 found
 Main Color Profile #9=1023, 0, 1023, 0,
 FoC Color Profile #9=1023, 1023, 1023, 0,
 Lockup Color Profile #9=1023, 1023, 0, 0,
 Bolt Color Profile #9=1023, 1023, 1023, 0,
 Crystal Color Profile #9=1023, 0, 1023, 0,
 focmix config:7
 tridentm config:0
 [COLOR] Profile Section #10 found
 Main Color Profile #10=0, 0, 1023, 0,
 FoC Color Profile #10=1023, 1023, 1023, 0,
 Lockup Color Profile #10=1023, 1023, 0, 0,
 Bolt Color Profile #10=1023, 1023, 1023, 0,
 Crystal Color Profile #10=0, 0, 1023, 0,
 focmix config:7
 tridentm config:0
 [COLOR] Profile Section #11 found
 Main Color Profile #11=0, 150, 1023, 0,
 FoC Color Profile #11=1023, 1023, 1023, 0,
 Lockup Color Profile #11=1023, 1023, 0, 0,
 Bolt Color Profile #11=1023, 1023, 1023, 0,
 Crystal Color Profile #11=0, 150, 1023, 0,
 focmix config:7
 tridentm config:0
 [COLOR] Profile Section #12 found
 Main Color Profile #12=0, 350, 1023, 0,
 FoC Color Profile #12=1023, 1023, 1023, 0,
 Lockup Color Profile #12=1023, 1023, 0, 0,
 Bolt Color Profile #12=1023, 1023, 1023, 0,
 Crystal Color Profile #12=0, 350, 1023, 0,
 focmix config:7
 tridentm config:0
 [COLOR] Profile Section #13 found
 Main Color Profile #13=0, 1023, 1023, 0,
 FoC Color Profile #13=1023, 1023, 0, 0,
 Lockup Color Profile #13=1023, 1023, 1023, 0,
 Bolt Color Profile #13=1023, 1023, 1023, 0,
 Crystal Color Profile #13=0, 1023, 1023, 0,
 focmix config:7
 tridentm config:0
 [COLOR] Profile Section #14 found
 Main Color Profile #14=0, 1023, 75, 0,
 FoC Color Profile #14=1023, 1023, 1023, 0,
 Lockup Color Profile #14=1023, 1023, 0, 0,
 Bolt Color Profile #14=1023, 1023, 1023, 0,
 Crystal Color Profile #14=0, 1023, 75, 0,
 focmix config:7
 [SPECIAL SETTINGS]
 Font Switching: o, -, -, -, -, -, -, -, -, -, -, -, -, -, -, X,
 oledscreensaver:20000ms
 "oledcustom:# Diatium OS #"
 bladeplistyle:3
 blademusicstyle:3
 Special Settings File Found
 [TANGIBLE] Tangible Voltage:3299mV - Index:15
 Lookup font #2 on path /2-THE_BALANCE
 Check font sanity on path /2-THE_BALANCE
 [FONT] file humM1.wav found
 [FONT] file poweronf.wav not found
 [FONT] file color.wav found
 [FONT] file lowbattery.wav found
 [FONT] file deadbattery.wav found
 [FONT] file temperature.wav found
 [FONT] file nostart.wav found
 [FONT] file plus.wav found
 [FONT] file minus.wav found
 [FONT] max Boot: 1
 [FONT] max Power on: 9
 [FONT] max Power off: 1
 [FONT] max Clash: 16
 [FONT] max Swing: 16
 [FONT] max Hum: 1
 [FONT] max Blaster: 8
 [FONT] max Spin: 4
 [FONT] max Stab: 4
 [FONT] max Force: 4
 [FONT] max Force-Clash: 0
 [FONT] max Pre-ON: 0
 [FONT] max Post-OFF: 0
 [FONT] max Lockup: 1
 [FONT] max Start Lockup: 0
 [FONT] max End Lockup: 4
 [FONT] max Drag: 1
 [FONT] max Start Drag: 0
 [FONT] max End Drag: 0
 [FONT] max Combo: 0
 [FONT] max SmoothSwing High: 4
 [FONT] max SmoothSwing Low: 4
 [FONT] max Local Tracks: 0
 [FONT] max iSaber Tracks: 1
 [FONT] SmoothSwing Enable - 4 pairs
 [FONT] is polyphonic
 Double click disabled
 used_profiles_color= 9223372036854775807
 used_profiles_blade= 9223372036854775807
 start_blade #0
 start_color #0
 font glyph #2=16
 [SMOOTHSWING] smooth_sharp:3.00
 [SMOOTHSWING] smooth_gain:100%
 [SMOOTHSWING] smooth_width1:45°
 [SMOOTHSWING] smooth_width2:160°
 [SMOOTHSWING] smooth_sens:250°/s
 [SMOOTHSWING] smooth_physics:950
 [SMOOTHSWING] smooth_dampen:80%
 [SMOOTHSWING] smooth_mode:HYBRID
 Bolt#0=1,
 Bolt#1=1,
 Bolt#2=1,
 Bolt#3=1,
 Bolt#4=1,
 Bolt#5=1,
 Bolt#6=1,
 Bolt#7=1,
 [ERROR] Bolt #8 exceeds Blaster snds from sound font
 [ACCENTS=POWERON]
 accent # 12345678
 accents= aaaaaaaa
 [ACCENT] state:1 w/ del:0
 [ACCENT] state:3 w/ del:0
 [ACCENT] state:7 w/ del:0
 [ACCENT] state:15 w/ del:0
 [ACCENT] state:31 w/ del:0
 [ACCENT] state:63 w/ del:0
 [ACCENT] state:127 w/ del:0
 [ACCENT] state:255 w/ del:0
 [ACCENT] seq. ends w/ stop
 [ACCENT] repeat seq. len:8 w/ 1 repeat
 [ACCENTS=POWEROFF]
 accent # 12345678
 accents= aaaaaaaa
 [ACCENT] state:170 w/ del:0
 [ACCENT] state:85 w/ del:0
 [ACCENT] seq. ends w/ stop
 [ACCENT] repeat seq. len:2 w/ 6 repeat
 [ACCENTS=LEDS]
 accent # 12345678
 accents= aaaaaaaa
 [ACCENT] state:1 w/ del:100
 [ACCENT] state:2 w/ del:100
 [ACCENT] state:4 w/ del:100
 [ACCENT] state:8 w/ del:100
 [ACCENT] state:16 w/ del:100
 [ACCENT] state:32 w/ del:100
 [ACCENT] state:64 w/ del:100
 [ACCENT] state:128 w/ del:100
 [ACCENT] state:64 w/ del:100
 [ACCENT] state:32 w/ del:100
 [ACCENT] state:8 w/ del:100
 [ACCENT] state:4 w/ del:100
 [ACCENT] state:2 w/ del:100
 [ACCENT] forever seq. len:13
 [ACCENTS=IDLE]
 accent # 12345678
 accents= aaaaCRYS
 [ACCENT] state:0 w/ del:1000
 [ACCENT] state:1 w/ del:1000
 [ACCENT] state:2 w/ del:1000
 [ACCENT] state:3 w/ del:1000
 [ACCENT] state:4 w/ del:1000
 [ACCENT] state:5 w/ del:1000
 [ACCENT] state:6 w/ del:1000
 [ACCENT] state:7 w/ del:1000
 [ACCENT] state:8 w/ del:1000
 [ACCENT] state:9 w/ del:1000
 [ACCENT] state:10 w/ del:1000
 [ACCENT] state:11 w/ del:1000
 [ACCENT] state:12 w/ del:1000
 [ACCENT] state:13 w/ del:1000
 [ACCENT] state:14 w/ del:1000
 [ACCENT] state:15 w/ del:1000
 [ACCENT] state:16 w/ del:1000
 [ACCENT] state:17 w/ del:1000
 [ACCENT] state:18 w/ del:1000
 [ACCENT] state:19 w/ del:1000
 [ACCENT] state:20 w/ del:1000
 [ACCENT] state:21 w/ del:1000
 [ACCENT] state:22 w/ del:1000
 [ACCENT] state:23 w/ del:1000
 [ACCENT] state:24 w/ del:1000
 [ACCENT] state:25 w/ del:1000
 [ACCENT] state:26 w/ del:1000
 [ACCENT] state:27 w/ del:1000
 [ACCENT] state:28 w/ del:1000
 [ACCENT] state:29 w/ del:1000
 [ACCENT] state:30 w/ del:1000
 [ACCENT] state:31 w/ del:1000
 [ACCENT] forever seq. len:32
 [ACCENTS=LOCKUP]
 accent # 12345678
 accents= rrrrrrrr
 [ACCENT] state:1 w/ del:100
 [ACCENT] state:1 w/ del:100
 Config load & parse time = 895 ms
 [BOOT] Trying to play /2-THE_BALANCE/boot.wav

As for the motion sensor log, here's me leaving the saber on the table still:

Code: [Select]
Vbatt = 958 / 3.79 volts
 Free RAM = 111151 bytes or 56.5%
 Current Magnetic Field: {14763 ; -550 ; 3674}
 Reference Magnetic Field {10 ; 10 ; 10}
 Current Magic:15211
 Magic score at boot time should be as low as possible
 [ACC] 257 -4354 6700
 [GYRO] -88 -937 -18
 [ACC] 260 -4356 6734
 [GYRO] 87 941 -16
 [ACC] 244 -4351 6709
 [GYRO] 98 944 -19
 [ACC] 230 -4363 6715
 [GYRO] 98 940 -14
 [ACC] 245 -4360 6702
 [GYRO] 82 951 -15
 [ACC] 225 -4359 6724
 [GYRO] 89 956 -16
 [ACC] 226 -4352 6723
 [GYRO] -76 -942 -16
 [ACC] 243 -4351 6739
 [GYRO] -87 -943 -14
 [ACC] 254 -4345 6718
 [GYRO] -88 -957 -16
 [ACC] 228 -4346 6710
 [GYRO] -87 -951 -19
 [ACC] 270 -4341 6728
 [GYRO] -90 -957 -13
 [ACC] 230 -4334 6728
 [GYRO] 93 965 -27
 [ACC] 248 -4355 6756
 [GYRO] 92 947 -12
 [ACC] 239 -4364 6746
 [GYRO] 80 949 -17
 [ACC] 229 -4352 6753
 [GYRO] 100 941 -21
 echo
 [ACC] 255 -4364 6743
 [GYRO] 90 932 -13
 [ACC] 248 -4361 6736
 [GYRO] -93 -954 -19
 [ACC] 261 -4366 6713
 [GYRO] -95 -944 -21
 [ACC] 247 -4329 6711
 [GYRO] -89 -951 -15
 [ACC] 234 -4367 6757
 [GYRO] -88 -933 -15
 [ACC] 265 -4370 6730
 [GYRO] -86 -949 -13
 [ACC] 242 -4354 6737
 [GYRO] 92 954 -12
 [ACC] 228 -4381 6742
 [GYRO] 85 945 -20
 [ACC] 237 -4344 6745
 [GYRO] 88 951 -19
 [ACC] 239 -4321 6679
 [GYRO] 93 962 -22
 [ACC] 261 -4357 6726
 [GYRO] 83 957 -11
 [ACC] -254 -4356 6727
 [GYRO] 88 949 -24
 [ACC] 246 -4325 6725
 [GYRO] -87 -955 -25
 [ACC] 271 -4350 6728
 [GYRO] -87 -956 -15
 [ACC] 226 -4343 6718
 [GYRO] -84 -942 -10
 [ACC] 254 -4361 6753
 [GYRO] -96 -959 -13
 [ACC] 254 -4333 6710
 [GYRO] 99 964 -14
 [ACC] 258 -4362 6740
 [GYRO] 91 948 -20
 [ACC] 267 -4355 6734
 [GYRO] 90 958 -18
 [ACC] 238 -4346 6734
 [GYRO] 96 941 -18
 [ACC] 267 -4359 6736
 [GYRO] 82 961 -7
 [ACC] -249 -4374 6733
 [GYRO] 84 946 -19
 [ACC] 238 -4363 6731
 [GYRO] -97 -950 -18
 [ACC] 235 -4351 6713
 [GYRO] -102 -956 -17
 [ACC] 261 -4371 6723
 [GYRO] -87 -954 -14
 [ACC] 241 -4340 6729
 [GYRO] -80 -939 -19
 [ACC] 244 -4355 6755
 [GYRO] -100 -952 -19
 [ACC] 229 -4366 6758
 [GYRO] 84 955 -24
 [ACC] 239 -4362 6742
 [GYRO] 90 942 -17
 [ACC] 239 -4353 6732
 [GYRO] 92 960 -15
 [ACC] 223 -4361 6736
 [GYRO] 88 938 -13
 [ACC] -217 -4343 6729
 [GYRO] 97 957 -14
 [ACC] 251 -4363 6757
 [GYRO] -90 -947 -11
 [ACC] 223 -4363 6729
 [GYRO] -86 -941 -19
 [ACC] 247 -4360 6750
 [GYRO] -92 -956 -24
 [ACC] 235 -4347 6712
 [GYRO] -84 -942 -12
 [ACC] 253 -4360 6729
 [GYRO] 93 939 -18
 [ACC] 236 -4355 6732
 [GYRO] 99 931 -7
 [ACC] 235 -4366 6727
 [GYRO] 86 948 -22
 [ACC] 236 -4333 6733
 [GYRO] 87 959 -11
 [ACC] 251 -4363 6722
 [GYRO] 88 965 -16
 [ACC] -236 -4348 6725
 [GYRO] 97 954 -13
 [ACC] 248 -4342 6729
 [GYRO] -89 -940 -20
 [ACC] 244 -4358 6743
 [GYRO] -84 -944 -14
 [ACC] 234 -4351 6719
 [GYRO] -98 -948 -10
 [ACC] 254 -4354 6732
 [GYRO] -86 -946 -14
 [ACC] 244 -4346 6719
 [GYRO] 96 951 -16
 [ACC] 241 -4350 6720
 [GYRO] 90 956 -12
 [ACC] 244 -4340 6727
 [GYRO] 85 959 -12
 [ACC] 242 -4361 6737
 [GYRO] 91 949 -16
 [ACC] 261 -4362 6737
 [GYRO] 81 953 -16
 [ACC] 265 -4355 6745
 [GYRO] -86 -931 -8

And this with me moving it around a bit:

Code: [Select]
[ACC] 451 -8063 -411
 [GYRO] 82 954 -13
 [ACC] 3190 -7158 -33
 [GYRO] 94 954 -16
 [ACC] 5875 -6179 1192
 [GYRO] 92 951 -23
 ->WAKEUP
 [ACC] 5866 -2819 6191
 [GYRO] 88 950 -18
 [ACC] 791 -4104 6069
 [GYRO] 88 945 -13
 [ACC] -1311 -4811 6800
 [GYRO] 100 957 -14
 [ACC] -3030 -4962 6780
 [GYRO] 89 958 -15
 [ACC] -2751 -6953 4064
 [GYRO] 96 947 -7
 [ACC] -222 -5924 4826
 [GYRO] 94 953 -19
 [ACC] 3153 -4464 6937
 [GYRO] -90 -956 -13
 [ACC] 4921 -1039 4981
 [GYRO] -99 -965 -18
 [ACC] 4489 1483 7116
 [GYRO] -97 -939 -21
 [ACC] 374 215 8441
 [GYRO] -98 -959 -14
 [ACC] -4695 -3236 5141
 [GYRO] -89 -964 -17
 [ACC] -3897 -5923 4375
 [GYRO] 90 954 -15
 [ACC] 1793 -7023 2957
 [GYRO] 84 958 -10
 [ACC] 5891 -5256 -1032
 [GYRO] 90 952 -14
 [ACC] 7199 -764 -4192
 [GYRO] 89 954 -18
 [ACC] 5958 3294 -5877
 [GYRO] 81 950 -14
 [ACC] 3900 7294 -2638
 [GYRO] -97 -946 -15
 [ACC] 3380 3532 5836
 [GYRO] -94 -959 -22
 [ACC] -300 -5305 6395
 [GYRO] -83 -955 -19
 [ACC] -2668 -5706 3653
 [GYRO] -83 -950 -17
 [ACC] 2000 -7841 1032
 [GYRO] -77 -963 -24
 [ACC] 5658 -5801 -4568
 [GYRO] 82 945 -14
 [ACC] 6374 -2339 -4699
 [GYRO] 99 970 -18
 [ACC] 8327 343 -603
 [GYRO] 87 947 -16
 [ACC] 4910 -412 5340
 [GYRO] 84 951 -13
 [ACC] -2359 -3330 4164
 [GYRO] 91 952 -15
 [ACC] -7681 -4893 2972
 [GYRO] -88 -948 -21
 [ACC] -8370 -1786 -1766
 [GYRO] -84 -949 -24
 [ACC] -5981 -3755 -269
 [GYRO] -102 -959 -16
 [ACC] -212 -7881 3389
 [GYRO] -89 -953 -16
 [ACC] 5653 -5362 4985
 [GYRO] 94 960 -15
 [ACC] 8492 -318 -289
 [GYRO] 80 964 -19
 [ACC] 7164 749 -5866
 [GYRO] 100 942 -10
 [ACC] 3307 444 -7060
 [GYRO] 94 966 -19
 [ACC] 1840 -512 -8196
 [GYRO] -99 -963 -19
 [ACC] -771 -8698 -3322
 [GYRO] 86 954 -20
 [ACC] -71 -5139 5511
 [GYRO] 96 938 -16
 [ACC] -522 -1481 8220
 [GYRO] -91 -955 -19
 [ACC] 5086 3376 6373
 [GYRO] -86 -942 -13
 [ACC] 7188 3378 -40
 [GYRO] -100 -958 -17
 [ACC] 5601 -99 -4203
 [GYRO] -90 -962 -22
 [ACC] 1719 -1818 -8574
 [GYRO] 90 964 -16
 [ACC] -3368 3051 -7812
 [GYRO] 85 966 -19
 [ACC] -4390 2745 -4419
 [GYRO] 96 933 -13
 [ACC] -6118 2188 -3118
 [GYRO] 85 944 -18
 [ACC] -4206 2302 -8049
 [GYRO] 87 948 -20
 [ACC] -1882 1902 -7600
 [GYRO] 91 949 -11
 [ACC] 7933 3277 -3097
 [GYRO] -100 -959 -14
 [ACC] 6432 28 3632
 [GYRO] -97 -951 -17
 [ACC] -1057 -7548 5815
 [GYRO] -89 -951 -9
 [ACC] -6309 -4007 4683
 [GYRO] -95 -959 -20
 [ACC] -658 -8597 5902
 [GYRO] -90 -943 -21
 [ACC] 4898 -6282 753
 [GYRO] 89 963 -24
 [ACC] 8485 -1744 1322
 [GYRO] 90 946 -19
 [ACC] 6479 3114 2171
 [GYRO] 89 950 -20
 [ACC] 1183 2742 6487
 [GYRO] 95 955 -21
 [ACC] -411 -2671 6149
 [GYRO] -90 -947 -20
 [ACC] -795 -6989 6309
 [GYRO] -81 -941 -14
 [ACC] 3274 -7082 2294
 [GYRO] -80 -945 -13
 [ACC] 6549 -3164 1973
 [GYRO] -88 -950 -10
 [ACC] 7468 1488 3726
 [GYRO] -88 -951 -19
 [ACC] 3499 1247 5404
 [GYRO] -94 -967 -18
 [ACC] -455 -2601 8604
 [GYRO] 88 962 -17
 [ACC] -1150 -3994 7649
 [GYRO] 89 961 -14
 [ACC] -415 -3161 8477
 [GYRO] 89 952 -20
 [ACC] -325 -3192 7288
 [GYRO] 98 964 -16
 [ACC] 856 -2034 7824
 [GYRO] 99 939 -16
 [ACC] -302 -1849 7672
 [GYRO] -94 -963 -11
 [ACC] 1027 -1839 8585
 [GYRO] -90 -947 -14
 [ACC] 230 -1835 7939
 [GYRO] -91 -958 -12

Let me know what you think.
Title: Re: CFX Motion Sensor going haywire
Post by: erv on January 14, 2020, 04:57:05 AM
thanks a lot for taking that time, much obliged  :smiley:
so :
- sensor gets initalized and read back properly
- data can be grabbed from the sensor

from what I see, the gyro unit (the MEMs inside) is dead. The ADC still provide readings which are just the offsets and the "noise level" of the gyro but nothing else so the sensor is probably dead.
I don't have explanations for it sorry, I really tested all options to eventually diagnose the fact initialization would fail or else, but that special fw bring 2s of delay to have the power supply ramp correctly before init, and beside, it's not a temporarily issue, but rather something permanent.

Where are you located ? Instead of having the saber sent back to sabertrio, I can see if we can arrange something to a repair station to have it looked at. Obviously, if you prefer to have the board swapped, it has to return to the saber builder.

Let's see how we can handle this the best way
Title: Re: CFX Motion Sensor going haywire
Post by: Ben300 on January 14, 2020, 05:33:22 AM
thanks a lot for taking that time, much obliged  :smiley:
so :
- sensor gets initalized and read back properly
- data can be grabbed from the sensor

from what I see, the gyro unit (the MEMs inside) is dead. The ADC still provide readings which are just the offsets and the "noise level" of the gyro but nothing else so the sensor is probably dead.
I don't have explanations for it sorry, I really tested all options to eventually diagnose the fact initialization would fail or else, but that special fw bring 2s of delay to have the power supply ramp correctly before init, and beside, it's not a temporarily issue, but rather something permanent.

Where are you located ? Instead of having the saber sent back to sabertrio, I can see if we can arrange something to a repair station to have it looked at. Obviously, if you prefer to have the board swapped, it has to return to the saber builder.

Let's see how we can handle this the best way

At this point I'm not surprised. There was no other explanation :(

I'm located in Switzerland, so if you guys are located in France sending it over that way is definitely quicker than sending it to where Sabertrio is from (Malaysia). Although, as I've mentioned in a previous post, having it repaired elsewhere may void their warranty unless an arrangement is done directly with them as well. I'm not sure.

I'll let Sabertrio's support know as well. Let me know what you think.

And thank you for everything noneless ^^