CANServer v2 Settings
The Settings screen allows you to view and make changes to some system settings related properties
The CANServer has either one or two hardware CAN bus interfaces (depending on the version of the hardware you have). The specifics about those hardware interfaces can be configured based on what you are connecting them to. You can enable and disable the interfaces, specify the bus speed, and specify the Bus ID that gets assigned to the CAN frames received on a specific hardware interface.
Some applications expect CAN data to be tagged with a specific Bus ID.
As an example when plugging the CANServer into a Tesla Model 3/Y you should have hardware CAN interface that is connected to the vehicle's Vehicle bus set to Bus ID 0 and (for dual bus hardware) the hardware CAN interface that is connected to the vehicle's Chassis bus should be set to Bus ID 1.
If the CANServer is plugged into a Tesla Model S/X you should have hardware CAN interface that is connected to the vehicle's Powertrain bus set to Bus ID 0 and (for dual bus hardware) the hardware CAN interface that is connected to the vehicle's Chassis bus should be set to Bus ID 1.
Applications like SavvyCAN and tes•LAX (as well as an upcoming future release of ScanMyTesla) can use the Bus ID to associate data with a specific set of decoding rules.
The CANServer has 5 accessible IO pins. These pins can be used for either input or output. The pins can then be used via the scripting feature. By implementing scripting you can toggle pin states (or read pin states) based on CAN messages and do things like turn on and off external audio systems or lighting.
This section allows setup of each pin's configuration based on requirements.
Pins support either a Pull Up or Pull Down resistor depending on what the external circuit requirements are.
CANServer supports synchronizing it's internal clock from CAN frames. There are two ways that this can be done.
There are some preset buttons that will quickly setup the configuration details for a Tesla Model S/X or a Model 3/Y.
-
Single Signal Mode
In this mode the result of a single decoded CAN frame is expected to contain a 32 bit integer that is the number of seconds since January 1 1970 UTC (referred to as the Unix epoch). The CANServer will use this decoded value at most once every 60 seconds to synchronize it's internal clock. An example of this is a Tesla Model 3's CAN frame 0x528 which contains the required value.
-
Multiple Signal Mode
In this mode the CANServer will look for 6 different decoded values. The values can come from one or more frames. CANServer is expecting the following details for each decoded value:
Decoded Value Expected Value Year A full 4 digit year (eg. 2021) Month A number from 1-12 identifying the month.
(1 = January ... 12 = December)Day A number from 1-31 Hour A number from 0-23 Minute A number from 0-59 Second A number from 0-60 The CANServer waits till it gets a fresh value for all decoded values and then will use that at most once every 60 seconds to synchronize it's internal clock. An example of this is a Tesla Model 3's CAN frame 0x318 which contains all the required values.