Closed udellc closed 11 months ago
Needs testing but I have refactored the Analog module to use a struct to contain the data within a vector, in addition, the names are now created once in the constructor which should fix the problem that arises when you change a char* resulting in garbage names
This has been fixed in f66c101
Describe the bug When using these analog channels (but I assume this is similar with any combination) Loom_Analog analog(manager, A0, A2); I am getting the following data reported: { 09:09:36.586 -> "module": "Analog", 09:09:36.586 -> "data": { 09:09:36.586 -> "Vbat": 4.307080269, 09:09:36.586 -> "Vbat_MV": 4311.914063, 09:09:36.586 -> " ": 1567, 09:09:36.586 -> "Vbat_MVuM_MV": 1262.783936 09:09:36.586 -> } What does uM_MV mean? I should be seeing Vbat, A0 and A2 reported, Also, for sake of minimizing data, do we need to have both V and MV reported? This is an easy conversion. Let's just pick one, V is fine.
Hardware in Use Trying to get the SmartRock code updated for a CUAHSI visiting researcher this week.
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Code
Output Copy and paste the serial output here if possible wrapped in ``` ```
SD Config .json is here