Hi Eliot,
Thanks for the reply. Replay with log file recorded with new firmware is jerky/laggy. I have tested this with two different laptops so should not be PC issue.
I can elaborate a litlle bit on on the encode code part because I had to modify the code a bit. In the current encode_sensor_binary_log.py at your github there seems to be a bug on row 152 as it already gives warning in spyder when I open the code (undefined name ‘self’). The code works for some logs but with some logs it fails at this point. I guess it depends if there is some errors in the log as this code part is to my understanding related to error handling.
I should say I am not very good programmer so to fix this problem I gave the code to ChatGPT for fixing and it did notice the problem and then proposed a correction (chatGPT comment: To fix this, recover must be an instance method, not a class method. That way, you can access instance attributes like self.failed_bytes.). I also changed the code so that I can give the log file in the code and not as argument (easier for testing). Anyhow, after these changes I can read the old log file but with new log file it crashes as stated earlier. Here is the complete error traceback:
Traceback (most recent call last):
File ~\anaconda3\Lib\site-packages\spyder_kernels\py3compat.py:356 in compat_exec
exec(code, globals, locals)
File c:\users\ipera\dropbox\omat projektit\2025_ping360\fixed_pingviewer_log2.py:218
print(decoded_message)
File ~\AppData\Roaming\Python\Python311\site-packages\brping\pingmessage.py:264 in repr
- payload_string += "\n - " + attr + ": " + str(getattr(self, attr))*
AttributeError: ‘PingMessage’ object has no attribute ‘mode’
Here is the modified code I am using:
And here is a log file logged with the new firmware:
-Ilkka