Hello, I am using the STM32CubeMonitor software for the first time and find it very helpful. My question is about the root cause for erroneous zero values in the time series displayed by the STM32CubeMonitor software. It's first first use was monitoring the joystick x/y displacement signals of the Adafruit Gamepad QT.
- Figure 1 shows the test setup with the Gamepad and the Nucleo-G071RB board. Pairs of 16-bit data points were received by the Nucleo board using the I2C protocol (hi2c1). I confirmed that the x/y signal integrity was good: no outliers or erroneous values were received by the Nucleo board, the I2C master.
- Figure 2 shows a Basic Flow used with the STM32CubeMonitor software for monitoring the x/y time series.
- Figure 3 shows the Node-RED Dashboard with the constant value (490) of the joysticks x-axis. The graph also show regular zero values, which are not present in the original time series received by the Nucleo board.
- Figure 4 shows the same time series as Figure 3, but zoomed in on three groups of zero values.
Question: Can anyone explain the phenomenon of erroneous zero values? Are parameters in my Basic Flow configuration incorrect?
Figure 1. Test setup with Gamepad QT and Nucleo board.
