search

clariusdev / solum

APIs for OEMs to Create Standalone Applications
https://www.clarius.com
BSD 3-Clause "New" or "Revised" License
16 stars 10 forks source link

Clarifying the meaning of "Software Communication Error" #65

Open danilogr opened 2 weeks ago

danilogr commented 2 weeks ago

Describe the bug Sometimes, when requesting several settings changes briefly (e.g., sliding the depth up or down in incremental steps), I get an error callback saying "software communication error." It would be great to know what to do in that case. Should I disconnect and connect the probe? Is it a wifi connectivity issue?

Also, would it be possible to receive error messages like these under a specific enumeration for future firmware (instead of returning a string)?

Environment:

clariusk commented 2 weeks ago

It typically means that a one ore more components within our architecture has a failed comm line, often resolved automatically or worst-case, a restart of the device. We will look for future updates to provide more context as needed.

danilogr commented 2 weeks ago

Is there a way to know if a restart of the device is needed?

I am running into a situation where the setting depth and gain through the solum API doesn't affect the probe; however, internally, solum returns the values I requested as if they were set.

clariusk commented 2 weeks ago

No, but what you're describing is likely not related to that specific error reporting, it could be a tcp message being delayed, parameter out of bounds etc. if reproducible all the time, happy to test on our side