# CLASH\_THRESHOLD\_G setting not "working" **URL:** \ **Category:** ProffieOS\ **Created:** [February 16, 2024, 5:07pm UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883 "2024-02-16T17:07:53Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![KalCestis](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/kalcestis/32/4476_2.png) [@KalCestis](https://crucible.hubbe.net/u/KalCestis)\ **Post date:** [February 16, 2024, 5:07pm UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883/1 "2024-02-16T17:07:53Z")
Hi despite setting my CLASH\_THRESHOLD\_G to extremely low settings (less than 1), it does not seem to have any effect on the blade clash sensitivity. However, I do believe CLASH\_THRESHOLD\_G is working because I am using a 1-button setup, and setting CLASH\_THRESHOLD\_G to low levels causes the volume control to trigger all the time when I long press with the blade OFF. However, I need to bang extremely hard to get the blade to clash when it is on. AUDIO\_CLASH\_SUPPRESSION\_LEVEL is not present. ---
**Author:** ![profezzorn](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/profezzorn/32/8_2.png) [@profezzorn](https://crucible.hubbe.net/u/profezzorn)\ **Post date:** [February 16, 2024, 7:12pm UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883/2 "2024-02-16T19:12:52Z")
See this thread maybe? > [@Clash Settings and Questions](https://crucible.hubbe.net/t/clash-settings-and-questions/4651): > > Yo, it’s me again XD This time I want to take a more in depth look into the changes that’ve been made to Clashes through the years. My stock saber has a relatively low clash threshold, so that phantom clashes (clashes where nothing is touching the saber) happen if you’re trying to make them happen. Now, I happen to LIKE these phantom clashes, especially where you can set them off if you’re practicing blocking movements and such. Full disclosure, I have NO idea what my stock settings are, I never got the manufacturer’s config, just a similar one that works, so I don’t know what the original settings are. Fast Forwards to OS7, and the clash detection is WAY different. Better in some ways and worse in others (IMO! Fett and Fred are doing amazing work always :D) but I’ve messed around with all sorts of clash thresholds and top config defines, but nothing seems to be able to replicate these phantom clashes I like. I’ve noticed that there’s nearly no way to make a clash happen mid-swing, which seems very intentional, but… Is there a way to change this? How could one go about messing with the clash detection on a more fundamental level? Any thoughts or ideas…? ---
**Author:** ![KalCestis](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/kalcestis/32/4476_2.png) [@KalCestis](https://crucible.hubbe.net/u/KalCestis)\ **Post date:** [February 16, 2024, 7:26pm UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883/3 "2024-02-16T19:26:04Z")
Thanks! I shall play with the prop\_base.h file and report back. ---
**Author:** ![profezzorn](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/profezzorn/32/8_2.png) [@profezzorn](https://crucible.hubbe.net/u/profezzorn)\ **Post date:** [February 16, 2024, 8:11pm UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883/4 "2024-02-16T20:11:11Z")
> [@KalCestis](#): > > prop\_base.h Wait, what? Just try this define first: ```cpp #define PROFFIEOS_DONT_USE_GYRO_FOR_CLASH ``` ---
**Author:** ![KalCestis](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/kalcestis/32/4476_2.png) [@KalCestis](https://crucible.hubbe.net/u/KalCestis)\ **Post date:** [February 16, 2024, 9:47pm UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883/6 "2024-02-16T21:47:25Z")
Thanks so much for the help. Please bear with me as I am completely new to this and is my first time editing a Proffie. #define PROFFIEOS\_DONT\_USE\_GYRO\_FOR\_CLASH did not fix it. ☹ However, it no longer respects the CLASH\_THRESHOLD\_G when the blade is off (no longer goes into Sound Volume mode constantly). Also, prior to the change above, another strange symptom was that I accidentally banged the saber really hard and it put the blade hum into mute. But, it fixed the clash issue (saber would clash just from moving it). When the blade is humming it seems to ignore CLASH\_THRESHOLD\_G ---
**Author:** ![profezzorn](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/profezzorn/32/8_2.png) [@profezzorn](https://crucible.hubbe.net/u/profezzorn)\ **Post date:** [February 18, 2024, 4:42am UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883/7 "2024-02-18T04:42:57Z")
> [@KalCestis](#): > > However, it no longer respects the CLASH\_THRESHOLD\_G when the blade is off (no longer goes into Sound Volume mode constantly). I don’t know what this means. What prop file are you using? Was it doing this before you changed PROFFIEOS\_DONT\_USE\_GYRO\_FOR\_CLASH ? Can you post your config file? ---
**Author:** ![KalCestis](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/kalcestis/32/4476_2.png) [@KalCestis](https://crucible.hubbe.net/u/KalCestis)\ **Post date:** [February 18, 2024, 7:24pm UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883/8 "2024-02-18T19:24:35Z")
> [@profezzorn](#): > > I don’t know what this means. When Saber is OFF and CLASH\_THRESHOLD\_G 0.1 (the saber will detect clash all the time because Volume Control is always triggered on long press) When Saber is OFF and CLASH\_THRESHOLD\_G 0.1 PROFFIEOS\_DONT\_USE\_GYRO\_FOR\_CLASH (the saber will NOT detect clash all the time and requires a hard smack to trigger Volume Control) In both cases when the Saber is ON it requires a hard smack to trigger Clash. > [@profezzorn](#): > > What prop file are you using? saber\_fett263\_buttons.h > [@profezzorn](#): > > Was it doing this before you changed PROFFIEOS\_DONT\_USE\_GYRO\_FOR\_CLASH ? See above > [@profezzorn](#): > > Can you post your config file? [https://pastebin.com/uHhteAr7](https://pastebin.com/uHhteAr7) ---
**Author:** ![profezzorn](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/profezzorn/32/8_2.png) [@profezzorn](https://crucible.hubbe.net/u/profezzorn)\ **Post date:** [February 18, 2024, 9:03pm UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883/9 "2024-02-18T21:03:46Z")
Does your saber have an OLED display? > [@KalCestis](#): > > When Saber is OFF and > CLASH\_THRESHOLD\_G 0.1 > (the saber will detect clash all the time because Volume Control is always triggered on long press) This would mean that 0.1 is too low (which makes sense, it’s very very low) > [@KalCestis](#): > > When Saber is OFF and > CLASH\_THRESHOLD\_G 0.1 > PROFFIEOS\_DONT\_USE\_GYRO\_FOR\_CLASH > (the saber will NOT detect clash all the time and requires a hard smack to trigger Volume Control) That’s weird. I’m not sure what that means. 0.1 is so low that it should trigger all the time either way. Maybe your accelerometer is broken? > [@KalCestis](#): > > In both cases when the Saber is ON it requires a hard smack to trigger Clash. This also makes no sense to me. Ok, so suggestions: 1. Does your saber actually have an OLED display? If not, remove ENABLE\_SSD1306 from your config. 2. Temporarily remove DISABLE\_DIAGNOSTIC\_COMMANDS from your config file, then use the “monitor gyro” and “monitor accel” commands to see the values generated by your gyro and accelerometer in the serial monitor. Does those values look reasonable? (Post them here so we can take a look at them.) ---
**Author:** ![KalCestis](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/kalcestis/32/4476_2.png) [@KalCestis](https://crucible.hubbe.net/u/KalCestis)\ **Post date:** [February 18, 2024, 9:50pm UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883/10 "2024-02-18T21:50:52Z")
> [@profezzorn](#): > > Does your saber have an OLED display? Yes it has an OLED. > [@profezzorn](#): > > That’s weird. I’m not sure what that means. 0.1 is so low that it should trigger all the time either way. Maybe your accelerometer is broken? Every other motion sensing function works fine. Including Volume control on clash. It’s only when the blade is ON that Clash doesn’t work properly. I’ll try your suggestions. ---
**Author:** ![profezzorn](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/profezzorn/32/8_2.png) [@profezzorn](https://crucible.hubbe.net/u/profezzorn)\ **Post date:** [February 18, 2024, 9:56pm UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883/11 "2024-02-18T21:56:33Z")
> [@KalCestis](#): > > Every other motion sensing function works fine. Including Volume control on clash. It’s only when the blade is ON that Clash doesn’t work properly. I’m not sure what this means though. A few possibilities include: 1. something in the code behaves differently when on, either because it’s configured that way (unintentionally) or because of a bug somewhere. 2. A short somewhere which doesn’t really cause any problems when the blade is off. 3. High power draw from the blade is causing problems with the 3.3v supply, which could affect the motion chip. 4. Motion chip is not working properly for some reason. Either way, getting the serial monitor output help. If the output from the monitoring looks reasonable, then the problem must be (1), if the output from the serial monitor looks bad/broken then it’s probably not (1)… ---
**Author:** ![KalCestis](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/kalcestis/32/4476_2.png) [@KalCestis](https://crucible.hubbe.net/u/KalCestis)\ **Post date:** [February 18, 2024, 11:07pm UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883/12 "2024-02-18T23:07:09Z")
Here are the monitor logs: (begin from reflash) done Activating polyphonic font. Activating SmoothSwing V2 Accent Swings Enabled. Polyphonic swings: 19 Monophonic swings: 0 Accent Slashes NOT Detected: unit = 0 vol = 0.50, Playing 1-Cal\_Kestis\_Blue/boot/boot1.wav channels: 1 rate: 44100 bits: Welcome to ProffieOS v7.13 For available serial commands, see: > **[Serial Monitor Commands](https://pod.hubbe.net/tools/serial-monitor-commands.html)** > > Documentation for ProffieOS I2C init… Motion chip … 106 found. Display initialized. EVENT: ?47 millis=1448 EVENT MENU TURN RIGHT Saving Global State Amplifier off. Playing common/idle.bmp Unmounting SD Card. EVENT: ?47 millis=19774 EVENT MENU TURN RIGHT Battery voltage: 4.15 EVENT: ?48 millis=21586 EVENT MENU TURN LEFT EVENT: ?47 millis=22536 EVENT MENU TURN RIGHT EVENT: Swing millis=24283 EVENT: Swing millis=24831 EVENT: ?48 millis=25070 EVENT MENU TURN LEFT EVENT: Swing millis=25274 EVENT: Swing millis=27348 EVENT: Swing millis=27839 EVENT: Clash millis=27971 EVENT: Swing millis=28368 EVENT: ?48 millis=28691 EVENT MENU TURN LEFT EVENT: ?47 millis=28773 EVENT MENU TURN RIGHT EVENT: Swing millis=28805 EVENT: Clash millis=31322 EVENT: Clash millis=31536 EVENT: Clash millis=31786 EVENT: Clash millis=32212 EVENT: Clash millis=32943 EVENT: Clash millis=33525 Battery voltage: 4.16 (monitor gyro) GYRO: -1.89, -2.92, -0.18 ACCEL: {-0.02, 0.71, 0.73} GYRO: 3.33, -2.19, -1.45 ACCEL: {-0.02, 0.71, 0.73} GYRO: 3.44, -1.42, -1.61 ACCEL: {-0.02, 0.72, 0.73} GYRO: 2.07, -2.73, -1.30 ACCEL: {-0.02, 0.71, 0.73} GYRO: 0.26, -2.70, -0.41 ACCEL: {-0.02, 0.71, 0.73} GYRO: 1.30, -2.50, -0.74 ACCEL: {-0.02, 0.72, 0.73} GYRO: 1.62, -2.26, -0.23 ACCEL: {-0.02, 0.71, 0.73} GYRO: 0.84, -1.27, -0.61 ACCEL: {-0.02, 0.72, 0.72} GYRO: 0.35, -2.00, -0.43 ACCEL: {-0.02, 0.72, 0.73} GYRO: -1.08, -1.04, -0.33 ACCEL: {-0.02, 0.71, 0.73} GYRO: 1.53, -0.74, -0.95 ACCEL: {-0.02, 0.72, 0.73} GYRO: 3.79, -7.45, -5.39 ACCEL: {-0.01, 0.71, 0.74} GYRO: -18.73, -57.19, 86.81 ACCEL: {-0.23, 0.99, 1.72} EVENT: Swing millis=334198 GYRO: 52.35, -229.47, 191.24 ACCEL: {-0.04, 0.18, -0.19} EVENT: Swing millis=334400 GYRO: 43.04, 365.16, -238.09 ACCEL: {-0.77, 0.92, 0.53} EVENT: ?47 millis=334541 EVENT MENU TURN RIGHT GYRO: 105.95, -90.94, 102.47 ACCEL: {0.04, 1.08, 0.78} GYRO: -2.23, -1.43, 5.49 ACCEL: {0.74, -0.34, -0.34} GYRO: 53.61, -28.15, 19.26 ACCEL: {0.77, 0.38, -0.41} EVENT: Clash millis=335092 EVENT: Swing millis=335129 GYRO: -10.19, 28.54, 16.94 ACCEL: {0.48, 0.51, 0.79} EVENT: Clash millis=335341 GYRO: 48.91, -15.54, 4.92 ACCEL: {0.51, 0.81, 0.53} EVENT: Clash millis=335569 EVENT: Swing millis=335604 GYRO: -71.89, 39.53, -32.76 ACCEL: {0.16, 1.78, 3.07} EVENT: Clash millis=335792 GYRO: -158.75, 118.54, 7.25 ACCEL: {0.32, 1.34, 1.73} GYRO: -7.15, -144.26, 129.07 ACCEL: {0.57, 0.01, 0.37} EVENT: ?47 millis=336145 EVENT MENU TURN RIGHT GYRO: 88.45, -96.06, -195.02 ACCEL: {0.62, -0.42, -1.46} EVENT: Swing millis=336295 GYRO: -13.33, 194.28, -9.23 ACCEL: {-0.05, 2.69, 0.38} GYRO: -243.64, -77.48, 176.07 ACCEL: {0.31, -0.74, 0.66} GYRO: -67.58, 94.13, -166.36 ACCEL: {0.76, -0.61, -0.20} EVENT: Swing millis=336893 EVENT: Clash millis=336994 GYRO: 92.50, 91.93, -110.09 ACCEL: {-0.16, 2.94, 1.72} GYRO: -22.41, -87.10, 124.25 ACCEL: {-0.07, 1.16, 0.41} EVENT: Clash millis=337380 GYRO: -17.72, 157.79, -95.46 ACCEL: {0.45, 0.10, 1.91} EVENT: Clash millis=337607 GYRO: -109.51, 165.19, -73.66 ACCEL: {-0.03, 1.07, 1.59} GYRO: -12.29, 6.86, -53.00 ACCEL: {0.07, 1.01, 0.85} EVENT: Swing millis=338064 ---
**Author:** ![KalCestis](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/kalcestis/32/4476_2.png) [@KalCestis](https://crucible.hubbe.net/u/KalCestis)\ **Post date:** [February 18, 2024, 11:17pm UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883/13 "2024-02-18T23:17:07Z")
> [@KalCestis](#): > > Accent Slashes NOT Detected: Also why is it not detecting my Accent Slashes? I have wav files in /swng ---
**Author:** ![profezzorn](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/profezzorn/32/8_2.png) [@profezzorn](https://crucible.hubbe.net/u/profezzorn)\ **Post date:** [February 19, 2024, 1:09am UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883/14 "2024-02-19T01:09:59Z")
> [@KalCestis](#): > > Also why is it not detecting my Accent Slashes? I have wav files in /swng Accent swings and accent slashes are different files. > [@KalCestis](#): > > ACCEL: {-0.05, 2.69, 0.38} > GYRO: -243.64, -77.48, 176.07 > ACCEL: {0.31, -0.74, 0.66} > GYRO: -67.58, 94.13, -166.36 > ACCEL: {0.76, -0.61, -0.20} > EVENT: Swing millis=336893 > EVENT: Clash millis=336994 These values look reasonable. Are they still reasonable when the blade is on? (Or maybe the blade is on here?) Have you tried setting your clash threshold to 2.0 or something reasonable? ---
**Author:** ![KalCestis](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/kalcestis/32/4476_2.png) [@KalCestis](https://crucible.hubbe.net/u/KalCestis)\ **Post date:** [February 19, 2024, 1:17am UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883/15 "2024-02-19T01:17:46Z")
> [@profezzorn](#): > > Are they still reasonable when the blade is on? I’ll try it with the blade on. > [@profezzorn](#): > > Have you tried setting your clash threshold to 2.0 or something reasonable? These logs are with threshold set to 2.0. ---
**Author:** ![profezzorn](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/profezzorn/32/8_2.png) [@profezzorn](https://crucible.hubbe.net/u/profezzorn)\ **Post date:** [February 19, 2024, 3:55am UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883/16 "2024-02-19T03:55:22Z")
> [@KalCestis](#): > > These logs are with threshold set to 2.0. And I see clashes in the logs, are they true or false clashes? Is it still easy to clash? Maybe the value should be higher? ---
**Author:** ![KalCestis](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/kalcestis/32/4476_2.png) [@KalCestis](https://crucible.hubbe.net/u/KalCestis)\ **Post date:** [February 19, 2024, 7:31am UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883/17 "2024-02-19T07:31:54Z")
Here you go. This is with CLASH\_THRESHOLD\_G set to 0.5. In these logs you can see that before Turning the saber ON I am easily triggering Clash events with little movement. Then after IGNITION you see it takes much more movement to trigger Clash. All of those “swings” you see after IGNITION is me trying to trigger Clash. Welcome to ProffieOS v7.13 For available serial commands, see: > **[Serial Monitor Commands](https://pod.hubbe.net/tools/serial-monitor-commands.html)** > > Documentation for ProffieOS GYRO: -0.62, -2.12, -1.03 GYRO: -0.96, -1.27, -0.89 GYRO: 1.46, -0.10, -4.95 GYRO: -1.26, 0.42, -1.00 GYRO: 2.32, -2.58, -1.25 GYRO: 10.46, -3.00, -1.58 GYRO: 19.23, -8.68, 1.98 GYRO: 45.58, -33.72, 14.84 GYRO: -64.17, 52.78, -31.03 GYRO: 4.90, 37.20, -43.06 GYRO: 31.81, -30.29, -1.98 GYRO: -32.61, -77.02, 126.54 GYRO: -28.59, 85.43, -64.24 GYRO: 78.65, -49.59, -79.58 GYRO: 0.09, -120.79, 137.34 EVENT: ?47 millis=39039 EVENT MENU TURN RIGHT GYRO: 9.84, 107.60, 45.09 EVENT: ?48 millis=39264 EVENT MENU TURN LEFT GYRO: 34.22, 56.00, -134.21 GYRO: 46.30, -52.83, -59.35 GYRO: 21.22, -24.62, 99.27 GYRO: -11.01, 36.19, 17.68 Battery voltage: 4.15 GYRO: -35.41, 62.09, -46.19 GYRO: 35.06, -141.73, 135.58 EVENT: ?47 millis=40530 EVENT MENU TURN RIGHT GYRO: -27.32, -26.82, -35.21 GYRO: -45.72, 152.86, -89.18 EVENT: ?48 millis=40791 EVENT MENU TURN LEFT GYRO: -7.08, -1.53, -5.60 GYRO: 31.17, -155.83, 49.93 EVENT: ?47 millis=41320 EVENT MENU TURN RIGHT GYRO: 15.49, -75.21, -16.72 GYRO: 2.70, 116.33, -13.03 EVENT: ?48 millis=41715 EVENT MENU TURN LEFT GYRO: -8.08, 86.00, -13.26 GYRO: -6.85, -26.81, 4.50 GYRO: 3.07, -4.59, 4.84 GYRO: 87.50, -110.34, 26.03 GYRO: 13.25, 34.45, -31.66 GYRO: -48.68, 76.73, -89.77 GYRO: 16.63, -18.36, -5.52 GYRO: -81.74, -38.06, 169.28 GYRO: 23.22, 40.08, -21.50 GYRO: 0.95, 12.96, -24.32 GYRO: 8.08, -69.07, 104.61 GYRO: 3.33, -77.17, -49.14 EVENT: ?47 millis=44044 EVENT MENU TURN RIGHT GYRO: -22.26, 32.64, -176.75 GYRO: -107.72, 43.53, 44.39 GYRO: -33.19, -78.17, 123.62 EVENT: Swing millis=44698 GYRO: 51.99, 81.95, -75.82 EVENT: ?48 millis=44992 EVENT MENU TURN LEFT GYRO: -33.48, -21.26, 79.92 GYRO: -40.86, 62.17, -41.41 GYRO: 10.63, 27.16, -20.96 GYRO: -7.45, 52.81, 1.23 GYRO: -27.10, -56.61, 4.71 GYRO: 18.28, -24.76, 26.45 GYRO: 3.30, -23.40, -11.38 GYRO: -6.38, 11.98, -3.11 GYRO: 18.93, -9.36, 17.51 GYRO: 0.55, -1.97, 5.76 GYRO: 0.54, -1.80, -1.24 GYRO: -1.25, -2.54, -1.07 GYRO: 0.68, 0.39, 0.39 GYRO: -1.11, 0.38, 2.22 GYRO: -1.13, 0.52, 4.79 GYRO: -0.71, -2.71, -2.62 EVENT: Clash millis=48194 GYRO: 2.53, 5.86, 12.93 GYRO: 1.26, -3.03, -2.59 GYRO: 1.46, -4.42, -3.93 EVENT: Clash millis=48619 GYRO: 0.37, -3.27, -1.25 GYRO: 0.91, -1.37, -0.23 GYRO: 0.88, -3.77, -1.01 GYRO: -1.12, 0.56, -1.19 GYRO: 1.19, -2.81, -2.85 GYRO: -0.94, -2.30, -1.47 GYRO: 2.17, -2.22, 0.59 GYRO: -1.73, -0.49, -1.08 GYRO: 0.36, -1.09, -0.58 GYRO: -0.89, -0.50, 0.01 EVENT: Stab millis=50707 GYRO: 0.91, -1.68, 0.58 GYRO: 9.02, -0.31, 6.25 EVENT: Clash millis=51206 GYRO: -13.69, 1.75, 4.34 GYRO: -2.63, -2.18, -2.66 GYRO: 0.70, 1.31, 3.72 GYRO: -1.31, -3.32, -3.68 EVENT: Stab millis=51956 GYRO: 5.41, -2.17, 2.67 GYRO: 2.60, -4.46, -1.57 EVENT: Clash millis=52323 GYRO: 0.81, -0.81, 0.16 GYRO: 1.60, -2.54, -1.65 GYRO: 0.81, -3.87, 0.11 GYRO: -0.34, -1.95, -1.32 GYRO: 0.31, -1.96, -0.56 GYRO: -0.51, -1.13, -0.17 GYRO: -0.65, -3.12, -1.87 GYRO: 0.88, -1.86, -0.74 GYRO: -0.60, -1.51, -0.39 GYRO: -0.78, -4.11, -0.62 GYRO: -5.05, -9.01, -4.25 GYRO: -1.09, -2.01, -3.94 GYRO: 1.17, -2.72, -2.25 GYRO: 1.70, -1.77, -1.32 GYRO: -3.69, -1.90, -5.20 GYRO: -13.00, -12.86, -13.39 GYRO: -1.20, -5.31, -10.46 GYRO: 6.94, 1.67, 0.36 GYRO: 2.56, 0.53, -0.07 GYRO: 2.40, 1.85, -2.24 GYRO: 0.79, 0.86, -1.51 GYRO: 0.47, 0.91, 1.58 GYRO: -2.54, -1.59, -4.78 GYRO: 1.79, -1.99, -2.74 Ignition. unit = 0 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/hum/hum.wav channels: 1 rate: 44100 bits: 16 unit = 1 vol = 0.50, Playing 1-Cal\_Kestis\_Blue/out/out2.wav channels: 1 rate: 44100 bits: 16 humstart: 1700 unit = 2 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingl/swingl1.wav channels: 1 rate: 44100 bits: 16 unit = 3 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingh/swingh1.wav channels: 1 rate: 44100 bits: 16 Playing common/on.bmp GYRO: 4.55, -1.44, 0.60 GYRO: 2.77, 3.07, 4.47 GYRO: 6.52, -2.76, 4.36 GYRO: 3.07, 1.58, 6.30 GYRO: 1.97, -0.23, -0.31 Playing 1-Cal\_Kestis\_Blue/swingl/swingl1.wav channels: 1 rate: 44100 bits: 16 GYRO: -1.42, -0.66, 1.02 GYRO: 0.18, -0.99, 0.76 GYRO: -0.10, -2.30, -2.33 GYRO: 5.94, -0.44, -2.38 GYRO: 3.69, 4.29, -1.25 GYRO: -0.39, -3.38, -0.25 GYRO: 2.72, -0.15, 1.52 GYRO: 3.09, -0.85, -1.07 GYRO: 0.16, -2.65, -0.71 Battery voltage: 4.11 GYRO: 1.82, -3.10, -0.59 GYRO: 1.17, -3.05, -2.42 GYRO: -0.98, -3.63, -3.23 GYRO: 7.94, -0.71, 2.42 GYRO: 5.86, -3.09, 2.81 GYRO: 41.92, -85.19, 38.37 unit = 2 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingl/swingl3.wav channels: 1 rate: 44100 bits: 16 unit = 3 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingh/swingh3.wav channels: 1 rate: 44100 bits: 16 GYRO: 9.71, 29.88, -18.12 GYRO: -22.38, 15.49, -15.84 GYRO: 29.27, -53.81, 35.44 GYRO: -6.19, 57.69, -28.98 GYRO: 41.40, -91.15, 53.95 unit = 2 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingl/swingl3.wav channels: 1 rate: 44100 bits: 16 unit = 3 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingh/swingh3.wav channels: 1 rate: 44100 bits: 16 GYRO: 62.59, 16.02, -59.75 Playing common/on.bmp GYRO: -56.80, -39.13, 74.54 GYRO: 9.09, 2.88, 36.52 GYRO: 51.04, 23.42, -102.95 GYRO: -35.33, -7.72, 43.39 unit = 2 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingl/swingl3.wav channels: 1 rate: 44100 bits: 16 unit = 3 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingh/swingh3.wav channels: 1 rate: 44100 bits: 16 GYRO: -1.59, -3.45, 20.10 GYRO: 33.80, -12.84, -57.23 GYRO: -9.05, 0.09, 5.75 GYRO: -13.34, -4.75, 22.15 GYRO: -1.35, -17.31, -31.80 GYRO: -0.70, -6.48, -4.19 unit = 3 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingl/swingl3.wav channels: 1 rate: 44100 bits: 16 unit = 2 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingh/swingh3.wav channels: 1 rate: 44100 bits: 16 GYRO: -0.03, -4.54, -2.12 GYRO: 0.02, -5.39, 0.11 GYRO: 0.70, -2.72, 1.31 GYRO: -1.61, -0.85, -1.45 GYRO: 4.29, -6.75, -0.62 unit = 3 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingl/swingl3.wav channels: 1 rate: 44100 bits: 16 unit = 2 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingh/swingh3.wav channels: 1 rate: 44100 bits: 16 GYRO: 1.49, -4.08, -5.20 GYRO: -2.55, -4.97, -4.24 GYRO: -18.74, -6.02, -18.96 GYRO: -10.13, -30.21, -71.69 GYRO: -14.23, -5.64, -22.28 unit = 2 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingl/swingl1.wav channels: 1 rate: 44100 bits: 16 unit = 3 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingh/swingh1.wav channels: 1 rate: 44100 bits: 16 GYRO: 9.53, -10.17, -7.85 GYRO: -1.72, -5.31, -2.92 GYRO: -12.56, 3.11, 5.26 GYRO: 102.99, -90.18, 93.95 GYRO: -6.74, 76.87, -132.59 unit = 2 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingl/swingl3.wav channels: 1 rate: 44100 bits: 16 unit = 3 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingh/swingh3.wav channels: 1 rate: 44100 bits: 16 GYRO: -35.09, -113.56, 117.71 Playing common/on.bmp GYRO: -15.29, 84.89, -114.96 GYRO: 2.11, -0.92, 13.84 GYRO: -8.76, 2.96, 15.91 EVENT: Clash ON millis=68361 unit = 1 vol = 0.50, Playing 1-Cal\_Kestis\_Blue/clsh/clsh3.wav channels: 1 rate: 44100 bits: 16 Playing common/clsh1.bmp GYRO: -6.26, 11.89, -6.57 GYRO: 3.17, -6.15, 0.57 Playing common/on.bmp GYRO: -0.67, -5.08, -0.65 Playing 1-Cal\_Kestis\_Blue/hum/hum.wav channels: 1 rate: 44100 bits: 16 GYRO: 7.36, -5.61, -0.57 unit = 2 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingl/swingl2.wav channels: 1 rate: 44100 bits: 16 unit = 3 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingh/swingh2.wav channels: 1 rate: 44100 bits: 16 GYRO: 3.70, 7.87, 4.30 GYRO: -4.20, 6.82, 17.36 GYRO: -6.41, -36.63, -75.32 GYRO: -6.51, -3.50, -8.94 GYRO: -3.97, -5.58, -3.74 unit = 3 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingl/swingl1.wav channels: 1 rate: 44100 bits: 16 unit = 2 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingh/swingh1.wav channels: 1 rate: 44100 bits: 16 GYRO: -3.83, -5.37, -1.88 GYRO: -3.82, -2.44, -2.57 GYRO: -1.78, 0.00, -3.28 EVENT: Clash ON millis=70817 unit = 4 vol = 0.50, Playing 1-Cal\_Kestis\_Blue/clsh/clsh4.wav channels: 1 rate: 44100 bits: 16 Playing common/clsh1.bmp GYRO: -1.74, -5.46, -1.95 GYRO: -19.59, -16.40, -4.38 Playing common/on.bmp GYRO: -16.46, -11.68, -13.94 GYRO: 3.22, -5.06, -2.73 GYRO: -1.54, 0.98, -5.40 GYRO: 3.16, 5.23, -3.62 GYRO: 3.32, 17.50, -0.62 GYRO: -0.31, 5.27, -2.10 GYRO: 4.34, -6.24, 3.53 GYRO: 8.03, 1.58, -6.77 GYRO: 10.24, -1.89, -11.57 GYRO: -32.70, -25.68, -8.34 GYRO: -19.45, -28.09, 3.94 unit = 3 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingl/swingl2.wav channels: 1 rate: 44100 bits: 16 unit = 2 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingh/swingh2.wav channels: 1 rate: 44100 bits: 16 GYRO: -1.35, -10.96, -1.48 EVENT: Clash ON millis=73752 unit = 1 vol = 0.50, Playing 1-Cal\_Kestis\_Blue/clsh/clsh5.wav channels: 1 rate: 44100 bits: 16 Playing common/clsh1.bmp GYRO: 14.71, -26.73, 9.94 GYRO: 43.42, -10.19, -1.86 Playing common/on.bmp GYRO: 84.20, -13.39, -20.07 GYRO: -17.00, 17.21, -26.98 GYRO: -35.24, 24.30, -111.68 unit = 2 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingl/swingl2.wav channels: 1 rate: 44100 bits: 16 unit = 3 vol = 0.00, Playing 1-Cal\_Kestis\_Blue/swingh/swingh2.wav channels: 1 rate: 44100 bits: 16 GYRO: 5.71, 76.95, 46.50 GYRO: 17.81, -28.35, -50.29 GYRO: 57.02, 15.56, 18.20 GYRO: 47.66, 7.86, 17.21 GYRO: -2.98, 2.12, 1.95 GYRO: 20.40, -7.25, 7.08 GYRO: -1.63, 2.85, 1.76 GYRO: -29.24, -6.77, 6.46 GYRO: -2.95, -2.52, -0.71 GYRO: -9.70, -3.34, 3.82 GYRO: -21.96, -10.29, 2.93 ---
**Author:** ![profezzorn](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/profezzorn/32/8_2.png) [@profezzorn](https://crucible.hubbe.net/u/profezzorn)\ **Post date:** [February 19, 2024, 9:39am UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883/18 "2024-02-19T09:39:51Z")
I’m confused. This doesn’t have the ACCEL values though, only the GYRO values. I don’t actually see any swing events though. Only the swingl/h starting over, which happens when you _don’t_ swing. However, I _do_ see three clash events after the ignition, so I guess you did manage to trigger some clashes? ---
**Author:** ![KalCestis](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/kalcestis/32/4476_2.png) [@KalCestis](https://crucible.hubbe.net/u/KalCestis)\ **Post date:** [February 19, 2024, 7:15pm UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883/19 "2024-02-19T19:15:01Z")
I’ll post a video and show you the logs. I tried “monitor accel” and “monitor acceleration” and it doesn’t recognize those commands. ---
**Author:** ![KalCestis](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/kalcestis/32/4476_2.png) [@KalCestis](https://crucible.hubbe.net/u/KalCestis)\ **Post date:** [February 19, 2024, 9:05pm UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883/20 "2024-02-19T21:05:34Z")
This is with CLASH\_THRESHOLD\_G 0.5 You see that when I tap on the hilt while the saber is OFF, it triggers CLASH events. But after I turn it ON, when I tap on the saber no CLASH events occur. [![](https://img.youtube.com/vi/LkHyuqv-NVc/maxresdefault.jpg "Proffie clash difficult to detect when ON") ](https://www.youtube.com/watch?v=LkHyuqv-NVc) ---
**Author:** ![KalCestis](https://crucible.hubbe.net/user_avatar/crucible.hubbe.net/kalcestis/32/4476_2.png) [@KalCestis](https://crucible.hubbe.net/u/KalCestis)\ **Post date:** [February 19, 2024, 9:26pm UTC](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883/21 "2024-02-19T21:26:43Z")
> [@profezzorn](#): > > However, I _do_ see three clash events after the ignition, so I guess you did manage to trigger some clashes? I had to bang it _really_ hard to trigger those events. All the other bumps without events are of me holding back. [Next page](https://crucible.hubbe.net/t/clash-threshold-g-setting-not-working/4883.md?page=2)