This is a poor product, look at this: that describes exactly the problems you (and me) are experiencing. Correct me if you've found any solutions so far.
Try looking at description of regster 0x2f in datasheet and to this question.
I think that the first problem you describe can be solved this way, the second behaviour sounds like you fried the device.
In a comment about rZero = 511;, you wrote:
For illustrative purposes only - should be measured to calibrate
This may well be the cause of your problem. If, instead of 511, the
“zero” of your measurement is around 445, then you end up measuring a
non-existing DC current of about 3.23 A. When you turn on the light
bulb, you add roughly 435 mA (100 W ...
I don't know why the three of them don't work together.
I already answered that question in my answer to your previous question.
why I'm using this calculation in my code and why if I removed it the lidar will not give me any measurement?
That code part is reading the data from the first SoftwareSerial interface. If you don't read this data (by removing ...
The process of integrating acceleration to derive velocity and integrating velocity to derive position are commonly known as dead reckoning. In this link it is stated:
Dead reckoning is subject to cumulative errors. Advances in
navigational aids that give accurate information on position, in
particular satellite navigation using the Global Positioning ...
You could measure the total acceleration (g + lift acceleration) with an accelerometer, and use that value in your calculation instead of 9.81m/s2. If the measured value is 0, sound an alarm.
Or, assuming the elevator only accelerates/decelerates for short periodes only (say, less than 2s) during a "trip", you could make a series of measurements in ...
The force due to acceleration is: F = m*a
So to calculate the weight while accelerating the formula is:
F = mg + ma or F = m(g + a)
Note, of course, that a can be positive or negative depending on whether the elevator is accelerating or decelerating.
The trick here is to know what "a" is. The best approach is probably to get an accelerometer and ...
I recently looked into this again, and it turns out that Broadcom had released a porting guide for this library in August 2020 (nearly a year after I originally posted this question) that should prove useful to anyone trying to make use of this sensor. It's for the STM32 platform, not Arduino, but it's the most detail Broadcom has provided with regards to ...