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
At the moment, CANBUS-Analyzer can only load the hard-coded Model S packet definitions for analysis.
Adding a "mode" or "definitions" selector (e.g. dropdown list) to the UI would allow the user to switch between different analysis modes (assuming the modes are exclusive of one another). Options might include:
Model S Defaults (hard-coded definitions)
Model 3 Defaults (hard-coded definitions)
Model S RWD DBC file
Model S AWD DBC file
Model 3 DBC file
The text was updated successfully, but these errors were encountered:
I think we are close, if not already at where we could just load any DBC file for any car. So maybe the dropdown should be
Model S (ScanMyTesla)
Model 3 (ScanMyTesla)
Load DBC file
the latter would pop up an open dialog. After loading several DBC files, they should stay in that box for quick select/load later on.
The reason I tag it with ScanMyTesla is that those options would show also the compound signals SMT provides, that are impossible in DBC, such as battery power (kW) calculated from simply watt*volts.
Just an idea, but we are moving fast towards compatibility with any DBC file, and we should start preparing the UI for it.
Hope:
At some point hopefully there will be one or more packets we can use to identify the vehicle type enough to appropriately choose the right DBC file automatically.
At the moment, CANBUS-Analyzer can only load the hard-coded Model S packet definitions for analysis.
Adding a "mode" or "definitions" selector (e.g. dropdown list) to the UI would allow the user to switch between different analysis modes (assuming the modes are exclusive of one another). Options might include:
Model S Defaults (hard-coded definitions)
Model 3 Defaults (hard-coded definitions)
Model S RWD DBC file
Model S AWD DBC file
Model 3 DBC file
The text was updated successfully, but these errors were encountered: