Swing Millis constant events - should I worry?

Sabersense · November 12, 2022, 7:18pm

Bit of an odd one - I just flashed a brand new loose board and serial monitor is showing constant Swing Milli events, even though the board is completely still (sitting on my desk with a paperweight on the USB cable a couple of inches from the board to stop any ‘creep’).

Have tried re-flashing again, but no difference.

Bad board or nothing to worry about?

Thoughts welcome.

NoSloppy · November 12, 2022, 8:25pm

Did you try different OS versions?
Is this file the same as latest / greatest?

github.com

profezzorn/ProffieOS/blob/7adbbcaa5a3fdd1fd6b97929dfa8c64cd0174a21/motion/lsm6ds3h.h

#ifndef MOTION_LSM6DS3H_H
#define MOTION_LSM6DS3H_H

constexpr int ProffieOS_log2(int x) {
  return (x <= 1) ? 0 : (ProffieOS_log2(x/2) + 1);
}

// Supports LSM6DS3, LSM6DSM and LSM6DSO
class LSM6DS3H : public I2CDevice, Looper, StateMachine {
public:
  const char* name() override { return "LSM6DS3H"; }
  enum Registers {
    FUNC_CFG_ACCESS = 0x1,
    SENSOR_SYNC_TIME_FRAME = 0x4,
    FIFO_CONTROL1 = 0x6,
    FIFO_CONTROL2 = 0x7,
    FIFO_CONTROL3 = 0x8,
    FIFO_CONTROL4 = 0x9,
    FIFO_CONTROL5 = 0xA,
    ORIENT_CFG_G = 0xB,

This file has been truncated. show original

Sabersense · November 12, 2022, 8:43pm

It was 5.9. Just loaded the same config onto another board with no issues.
But I’ll try 6.7 and report back…

Sabersense · November 12, 2022, 9:55pm

Well I’ll be…
Loaded the identical config with the same prop in 6.7 - fixed;
Went back to 5.9 - problem returned.

So what’s all that about just out of interest?

Anyway I guess that’s the problem solved. Thanks as always Brian!

NoSloppy · November 13, 2022, 2:26am

Manufacturers took it upon themselves to use a different motion chip, and Fredrik had to account for it in code afterwards.
I don’t remember when that happened, but it seems like after 5.9, if that’s indeed what the issue was.

This line in particular, but there’s likely more to it.

github.com

profezzorn/ProffieOS/blob/7adbbcaa5a3fdd1fd6b97929dfa8c64cd0174a21/motion/lsm6ds3h.h#L138


      
              while (1) {
                first_motion_ = true;
                first_accel_ = true;
                
                STDOUT.print("Motion chip ... ");
                I2CLOCK();
          
          
      I2C_READ_BYTES_ASYNC(WHO_AM_I, databuffer, 1);
                id_ = databuffer[0];
                STDOUT.print(id_);
                if (id_  == 105 || id_ == 106 || id_ == 108) {
                  STDOUT.println(" found.");
                } else  {
                  STDOUT.println(" not found.");
          	goto i2c_timeout;
                }
          
          
#ifndef PROFFIEOS_ACCELEROMETER_RANGE
          #define PROFFIEOS_ACCELEROMETER_RANGE 16
          #endif
          #if PROFFIEOS_ACCELEROMETER_RANGE == 4

Sabersense · November 13, 2022, 11:46am

Ahhhh! That makes sense.
Thanks so much for the explanation Brian. Always good to know what I’m dealing with.
And also goes to show that my routine of programming and testing loose boards before install is sound.