You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The timestamp in the main window shows always '0', or, depending on settings, the corresponding System Time Jan-01 etc.
When I use CANgaroo to capture CAN messages, the timestamps are OK.
The problem did not occur on first installation, but after i played around with the settings. I was unable to get it back to working.
Even deleting the entire SavvyCAN folder and re-downloading the release didn't help. (Since the programm doesn't install in the classic way - where does it store the settings?)
V213,
Windows 11
SLCAN devices (CANable 2.0)
The text was updated successfully, but these errors were encountered:
Thanks for the quick reply!
Found the .ini file at: AppData\Roaming\EVTV\SavvyCAN.ini, renamed it and started from scratch.
Unfortunately, this didn't solve the issue - timestamps are still 0.
For now, I can do what I need to do with python and cantools, but you might want to look into that one anyways.
this will solve ur problem Recording with Time Stamp File → Preference→ Time Keeping → Select system clock → back → Use Start Continuous logging → Check for Red LOGGING Text Blinking on main window . if u follow dees steps wen the logging it self u'll be able to see time stamp in log file csv or txt
The timestamp in the main window shows always '0', or, depending on settings, the corresponding System Time Jan-01 etc.
When I use CANgaroo to capture CAN messages, the timestamps are OK.
The problem did not occur on first installation, but after i played around with the settings. I was unable to get it back to working.
Even deleting the entire SavvyCAN folder and re-downloading the release didn't help. (Since the programm doesn't install in the classic way - where does it store the settings?)
V213,
Windows 11
SLCAN devices (CANable 2.0)
The text was updated successfully, but these errors were encountered: