1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
0
There could be a few reasons for the difference in total vibration RMS values between what is shown in the raw export data versus the mobile app:
- The app may apply additional filtering, averaging or calculations to the raw sensor data before displaying results.
- There could be minor delays between when the data is captured by the sensor and exported versus when it is processed and displayed in the app.
- The coordinate system or units of measurement may differ between the raw data export and what is used in the app's calculations and display.
To better understand what calculations or processing is done before displaying results in the app, I'd recommend checking the app documentation or contacting AWS Support. You could also try exporting raw acceleration data from the sensor itself to compare directly with the Kinesis export values.
Some things to check in the raw export data include:
- Verifying the timestamps match between records
- Comparing the individual x, y, z axis RMS values
- Calculating your own
sqrt(x^2 + y^2 + z^2)to see if it matchestotalVibration
관련 콘텐츠
- 질문됨 한 달 전
AWS 공식업데이트됨 일 년 전- AWS 공식업데이트됨 4년 전
- AWS 공식업데이트됨 6달 전
- AWS 공식업데이트됨 4년 전
I've been able to check the things you listed previously. Matching timestamps, comparing individual RMS values, and calculating my own totalVibration. When I calculate my own, it matches what is calculated in Kinesis, but again, not in the app.
At this point, I wonder about that potential extra filtering. There is little to no documentation related to my questions that I have been able to find. Sounds like the best bet would be to go with your recommendation of contacting AWS support.