LIS3MDL - Register Wrap Around #2

New Issue

muellerr · 2020-10-30T15:46:21+01:00

muellerr commented

2020-10-30 15:46:21 +01:00

The LIS3MDL auto increment function wraps around after reading the second Z-Axis register.
Therefore, all values read after that register propably are not correct in the current
implementation.

I suggest splitting up the the read process in two-steps. In one step, the regular control register + data registers are read and in the second one, the the temperature and rgisters after that are read. The second step could also read the WHO_AM_I register every once in a while (e.g. every 5th read?).

The LIS3MDL auto increment function wraps around after reading the second Z-Axis register. Therefore, all values read after that register propably are not correct in the current implementation. I suggest splitting up the the read process in two-steps. In one step, the regular control register + data registers are read and in the second one, the the temperature and rgisters after that are read. The second step could also read the WHO_AM_I register every once in a while (e.g. every 5th read?).

👍 1

lloidold commented

2020-10-30 16:33:38 +01:00

I support the idea to split the commands, but give to consider that you need two SPI Requests to the LIS3MDL to get the WHOAMI Register together with the temperature and the subsequent registers.

Additional suggestion: Just ask for the WHOAMI Register at initialization of the DeviceHandler. To monitor the proper functionality compare the values of the control registers between two measurements as they should not change without commanded reconfiguration. So you couls neglect the WHOAMI register during operation.

I support the idea to split the commands, but give to consider that you need two SPI Requests to the LIS3MDL to get the WHOAMI Register together with the temperature and the subsequent registers. Additional suggestion: Just ask for the WHOAMI Register at initialization of the DeviceHandler. To monitor the proper functionality compare the values of the control registers between two measurements as they should not change without commanded reconfiguration. So you couls neglect the WHOAMI register during operation.

muellerr commented

2020-11-05 11:48:21 +01:00

Okay, I will make these adaptions soon as I have connected an EVAL board to our OBC dev board.
Maybe it's also a good idea to convert gauss to micro tesla to have SI units and because the RM3100 produces microtesla values as well.

Okay, I will make these adaptions soon as I have connected an EVAL board to our OBC dev board. Maybe it's also a good idea to convert gauss to micro tesla to have SI units and because the RM3100 produces microtesla values as well.

👍 1

muellerr commented

2020-11-25 17:21:45 +01:00

Adaptions done and tested. As soon as local pools have been integrated into the FSFW, I will create the pull request.

muellerr referenced a pull request that will close this issue

2020-12-14 22:31:39 +01:00

TMTC + MGM Handler + Host build update #5

muellerr referenced a pull request that will close this issue

2020-12-27 18:50:48 +01:00

Device Handler Updates #9

meierj closed this issue

2020-12-28 11:09:09 +01:00