-
Notifications
You must be signed in to change notification settings - Fork 1
Settings
The CANBadger will try to load provided settings at startup. This article will detail the format of the settings, how the CANBadger tries to load settings and how you can provide custom settings to your CANBadger.
A CANBadger settings file is a simple .txt, containing a key-value-pair in each line. The settings include the CANBadgers ID, with which it will advertise itself over Ethernet. They also include the speeds for CAN and KLINE interfaces and many boolean values the CANBadger uses internally. The CANBadger will create default settings on the SD when there are none provided. This allows you to get the default settings file from the SD and edit it to provide custom settings.
On startup, the CANBadger will search for valid settings according to the following decision tree.
When an SD is inserted, the CANBadger will check if there is a settings filename stored in EEPROM. If a filename is found in the EEPROM, it will try to load settings from it. If no filename is found in EEPROM, the CANBadger will look for the default filename on the SD.
The default filename for the settings is canbadger_settings.txt
If there is no SD or the previous methods fail, the CANBadger will look for valid settings in the EEPROM. When no valid settings are found anywhere, the CANBadger will start with default settings.
When running the CANBadger with a SD card, simply changing the canbadger_settings.txt on the SD card will allow you to provide custok settings for your CANBadger.
Using the CANBadger with the CANBadger Server GUI allows for quick access to the CAN interface settings and allows you to choose between different settings files on your SD.
Visit our website for more information, customized automotive security hardware or trainings.