Yeh, but it's never the board

Sabersense · February 10, 2025, 3:24pm

…except maybe this one is…?

Got a loose 3.9, loaded the config, but with the board perfectly still, it’s reading constant clashes (see below). Tried exactly the same setup with another 3.9 and that one looked fine.

So is this one of the rare occasions when it is actually the board? And if it is, is there a hack/workaround I can use to save it?

Thanks as always.

15:19:39.516 -> Welcome to ProffieOS ProffieOS 7.14.
15:19:39.516 -> For available serial commands, see:
15:19:39.516 -> https://pod.hubbe.net/tools/serial-monitor-commands.html
15:19:40.218 -> EVENT: Stab millis=37022
15:19:40.472 -> EVENT: Stab millis=37265
15:19:41.074 -> EVENT: Clash millis=37856
15:19:41.296 -> EVENT: Stab millis=38085
15:19:41.470 -> EVENT: Stab millis=38252
15:19:41.576 -> EVENT: Stab millis=38371
15:19:41.714 -> EVENT: Stab millis=38519
15:19:41.855 -> EVENT: Clash millis=38646
15:19:42.699 -> EVENT: Clash millis=39492
15:19:43.119 -> EVENT: Stab millis=39930
15:19:43.221 -> Battery voltage: 3.36
15:19:43.602 -> EVENT: Clash millis=40415
15:19:43.716 -> EVENT: Stab millis=40516
15:19:43.893 -> EVENT: Clash millis=40687
15:19:44.928 -> EVENT: Stab millis=41738
15:19:45.501 -> EVENT: Clash millis=42300
15:19:45.851 -> EVENT: Clash millis=42636
15:19:45.965 -> EVENT: Stab millis=42743
15:19:46.067 -> EVENT: Clash millis=42865
15:19:46.415 -> EVENT: Clash millis=43197
15:19:46.591 -> EVENT: Clash millis=43382
15:19:46.739 -> EVENT: Stab millis=43535
15:19:47.277 -> EVENT: Stab millis=44057
15:19:48.006 -> EVENT: Clash millis=44818
15:19:48.149 -> EVENT: Clash millis=44945
15:19:48.373 -> EVENT: Clash millis=45168
15:19:48.802 -> EVENT: Stab millis=45604
15:19:49.047 -> EVENT: Stab millis=45849
15:19:49.469 -> EVENT: Stab millis=46253
15:19:49.580 -> EVENT: Clash millis=46356
15:19:49.722 -> EVENT: Clash millis=46514
15:19:50.455 -> EVENT: Clash millis=47266
15:19:51.408 -> EVENT: Stab millis=48185
15:19:51.869 -> EVENT: Clash millis=48655
15:19:52.080 -> EVENT: Stab millis=48863
15:19:52.578 -> EVENT: Clash millis=49372
15:19:52.759 -> EVENT: Stab millis=49572
15:19:52.942 -> EVENT: Clash millis=49737
15:19:53.129 -> EVENT: Clash millis=49931
15:19:53.237 -> EVENT: Clash millis=50049
15:19:53.414 -> EVENT: Clash millis=50223
15:19:53.692 -> EVENT: Stab millis=50485
15:19:53.870 -> EVENT: Clash millis=50663
15:19:54.155 -> EVENT: Stab millis=50942
15:19:54.438 -> EVENT: Stab millis=51221
15:19:54.722 -> EVENT: Clash millis=51508
15:19:54.968 -> EVENT: Stab millis=51780
15:19:55.110 -> EVENT: Stab millis=51897
15:19:56.593 -> EVENT: Stab millis=53406
15:19:56.846 -> EVENT: Clash millis=53649
15:19:57.216 -> EVENT: Stab millis=54015
15:19:57.434 -> EVENT: Stab millis=54230
15:19:58.069 -> EVENT: Clash millis=54879
15:19:58.311 -> EVENT: Stab millis=55120
15:19:58.698 -> EVENT: Clash millis=55492
15:19:59.314 -> EVENT: Clash millis=56097
15:19:59.571 -> EVENT: Clash millis=56373
15:19:59.928 -> EVENT: Stab millis=56705
15:20:00.287 -> EVENT: Clash millis=57079

profezzorn · February 10, 2025, 6:24pm

What is your clash threshold?
You don’t have KEEP_SAVEFILES_WHEN_PROGRAMMING, right?
Have you tried “monitor clash” and/or “monitor gyro” to see the values from the motion chip?

Sabersense · February 10, 2025, 6:55pm

Clash threshold is 3.5.
And no, I never use the keep save files define. Though bizarrely it does seem to do it when the SD card is fitted but not with no SD card. Have swapped the card but no change. The only thing I can see different is the voltage drops a little from 3.45 to 3.7 with no card, to around 3.3 with the card in, so maybe that’s it, and once the board is installed and running off a battery, it will be fine.

Anyway FWIW here’s a monitor clash sample:

18:44:51.072 -> ACCEL: {-0.08, -0.09, -0.97}
18:44:51.292 -> ACCEL: {-0.08, -0.10, -0.98}
18:44:51.468 -> ACCEL: {-0.08, -0.10, -0.98}
18:44:51.681 -> ACCEL: {-0.08, -0.10, -0.99}
18:44:51.895 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:52.071 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:52.283 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:52.495 -> ACCEL: {-0.08, -0.10, -0.98}
18:44:52.673 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:52.890 -> ACCEL: {-0.08, -0.10, -0.98}
18:44:53.100 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:53.286 -> ACCEL: {-0.08, -0.10, -0.98}
18:44:53.499 -> ACCEL: {-0.08, -0.10, -0.98}
18:44:53.704 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:53.882 -> ACCEL: {-0.08, -0.09, -0.99}
18:44:54.099 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:54.279 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:54.484 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:54.698 -> ACCEL: {-0.08, -0.10, -0.98}
18:44:54.911 -> ACCEL: {-0.08, -0.10, -0.98}
18:44:55.091 -> ACCEL: {-0.08, -0.10, -0.98}
18:44:55.300 -> ACCEL: {-0.08, -0.09, -0.99}
18:44:55.508 -> ACCEL: {-0.08, -0.10, -0.98}
18:44:55.715 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:55.901 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:56.112 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:56.297 -> Battery voltage: 3.41
18:44:56.297 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:56.512 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:56.687 -> ACCEL: {-0.08, -0.10, -0.98}
18:44:56.902 -> ACCEL: {-0.08, -0.10, -0.98}
18:44:57.109 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:57.315 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:57.498 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:57.710 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:57.929 -> ACCEL: {-0.08, -0.10, -0.98}
18:44:58.101 -> ACCEL: {-0.08, -0.10, -0.98}
18:44:58.317 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:58.504 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:58.714 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:58.922 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:59.099 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:59.316 -> ACCEL: {-0.08, -0.10, -0.98}
18:44:59.529 -> ACCEL: {-0.08, -0.09, -0.98}
18:44:59.711 -> ACCEL: {-0.08, -0.10, -0.98}
18:44:59.918 -> ACCEL: {-0.08, -0.10, -0.98}
18:45:00.130 -> ACCEL: {-0.07, -0.06, -0.97}
18:45:00.206 -> EVENT: Clash millis=43935
18:45:00.310 -> ACCEL: {-0.08, -0.10, -0.98}

And here’s a monitor gyro sample:

18:46:07.437 -> GYRO: -27.50, -5.25, -1.55
18:46:07.648 -> GYRO: 1.93, -3.75, 0.48
18:46:07.648 -> EVENT: Stab millis=11893
18:46:07.790 -> EVENT: Clash millis=12032
18:46:07.864 -> GYRO: 1.75, -3.86, 0.05
18:46:08.044 -> GYRO: 5.66, -2.18, 0.15
18:46:08.256 -> GYRO: 7.22, -3.46, 0.96
18:46:08.436 -> EVENT: Clash millis=12657
18:46:08.470 -> GYRO: 18.56, -2.96, 0.62
18:46:08.646 -> GYRO: -3.90, -3.73, -0.77
18:46:08.751 -> EVENT: Stab millis=12973
18:46:08.861 -> GYRO: 4.80, -2.22, -1.35
18:46:08.897 -> EVENT: Clash millis=13147
18:46:09.075 -> GYRO: -9.34, -2.80, -0.94
18:46:09.146 -> EVENT: Clash millis=13397
18:46:09.256 -> GYRO: -4.38, -3.49, 2.72
18:46:09.471 -> GYRO: 3.53, -3.22, -0.57
18:46:09.510 -> EVENT: Stab millis=13727
18:46:09.647 -> GYRO: 8.39, -3.80, 2.08
18:46:09.719 -> EVENT: Stab millis=13949
18:46:09.863 -> GYRO: -13.52, -3.83, -0.84
18:46:10.070 -> GYRO: 3.00, -2.49, -0.12
18:46:10.253 -> GYRO: -9.27, -5.00, 0.07
18:46:10.326 -> EVENT: Clash millis=14555
18:46:10.465 -> GYRO: -5.29, -2.54, 0.87
18:46:10.567 -> EVENT: Stab millis=14795
18:46:10.674 -> GYRO: -24.61, -4.10, -0.70
18:46:10.843 -> EVENT: Clash millis=15096
18:46:10.843 -> GYRO: 23.37, -1.88, 0.78
18:46:11.052 -> GYRO: 7.94, -2.04, -0.47
18:46:11.260 -> GYRO: -1.66, -3.55, 0.23
18:46:11.335 -> EVENT: Stab millis=15553
18:46:11.475 -> GYRO: -2.82, -4.13, -0.62
18:46:11.686 -> GYRO: -4.53, -4.40, 0.26
18:46:11.761 -> EVENT: Clash millis=15993
18:46:11.868 -> GYRO: 0.67, -3.14, 0.95
18:46:12.079 -> GYRO: -16.30, -4.00, 0.46
18:46:12.288 -> GYRO: -3.92, -3.24, 0.05
18:46:12.288 -> EVENT: Stab millis=16512
18:46:12.465 -> GYRO: 19.34, -1.46, 1.09
18:46:12.540 -> EVENT: Clash millis=16785
18:46:12.679 -> GYRO: 13.95, -2.22, 0.44
18:46:12.784 -> EVENT: Stab millis=17013
18:46:12.885 -> GYRO: 19.72, -2.07, -0.04
18:46:13.024 -> EVENT: Clash millis=17267
18:46:13.058 -> GYRO: -4.03, -1.79, 0.43
18:46:13.269 -> GYRO: 1.94, -2.83, -0.37
18:46:13.488 -> GYRO: 6.24, -1.79, -1.14
18:46:13.661 -> GYRO: -7.14, -1.95, -1.29
18:46:13.834 -> EVENT: Stab millis=18064
18:46:13.871 -> GYRO: 10.69, -2.78, 0.52
18:46:14.086 -> GYRO: 13.35, -3.18, 0.61
18:46:14.302 -> GYRO: 0.65, -2.59, -0.14
18:46:14.337 -> EVENT: Stab millis=18562
18:46:14.481 -> GYRO: 13.68, -1.10, -0.23
18:46:14.691 -> GYRO: 7.66, -1.39, 0.23

I’m guessing both look fine, so I’ll probably keep this board either for one of my own installs or for an eco where it can be easily swapped out if it does start playing up.

profezzorn · February 10, 2025, 7:02pm

I think those values are reasonable.
Maybe try changing this zero to one and see what it prints:

github.com

profezzorn/ProffieOS/blob/43bdfbdea9338f8f0937fcbea4fe65b1ca8de938/props/prop_base.h#L810


      
                accel_ = accel;
                diff = Vec3(0,0,0);
                v = 0.0;
              } else {
          #ifndef PROFFIEOS_DONT_USE_GYRO_FOR_CLASH
                v = (diff.len() + fusor.gyro_clash_value()) / 2.0;
          #else
                v = diff.len();
          #endif
              }
          #if 0
              static uint32_t last_printout=0;
              if (millis() - last_printout > 1000) {
                last_printout = millis();
                STDOUT << "ACCEL: " << accel
                       << " diff: " << diff
                       << " gyro: " << fusor.gyro_clash_value()
                       << " v = " << v << "\n";
              }
          #endif
              // If we're spinning the saber or if loud sounds are playing,

You could also try PROFFIEOS_DONT_USE_GYRO_FOR_CLASH

Sabersense · February 10, 2025, 9:26pm

Thanks Prof.
Yeh, DONT_USE_GYRO_FOR_CLASH would have been my next step if it does it when it’s installed.
I tried the zero thing too, but sadly it made no difference.
Not to worry - at least I now have a plan for it and a few options going forward.
Thanks as always for the help.

profezzorn · February 10, 2025, 10:29pm

The zero thing isn’t a potential solution, it just prints out more stuff which you (or I) would need to look at to maybe understand what is happening.