7.1.2. Using the f_Debug CAN Message
7.1.3. f_Debug
The following information can be requested or action can be performed via the
f_Debug message:
f_Debug.FramInitializationresets all entries stored within the FRAM to their default values.f_Debug.IdentifyHardwarerequests the hardware information for every connected BMS-Slave.f_Debug.Rtcrequests to set the provided time as timestamp on the BMS-Master.f_Debug.SoftwareResetrequests the BMS-Master to perform a power cycle (not yet implemented).f_Debug.TimeInforequests to return the current time info of the RTC.f_Debug.UptimeInforequests to return the current uptime of the BMS-Master.f_Debug.VersionInforequests to return the current version information of the BMS-Master software.
7.1.4. f_DebugResponse
The following f_DebugResponse signals are available:
f_DebugResponse.BmsSoftwareVersionInfotransmits the current version information.f_DebugResponse.BootInformationmay be send with either0xFEFEFEFEFEFEFEfor start or0x01010101010101for end of the boot pattern.f_DebugResponse.BootTimestamptransmits the system startup time.f_DebugResponse.CommitHashHigh7transmits the first 7 high characters of the commit hash.f_DebugResponse.CommitHashLow7transmits the last 7 low characters of the commit hash.f_DebugResponse.McuLotNumbertransmits the DieID high.f_DebugResponse.McuUniqueDieIdtransmits the device ID.f_DebugResponse.McuWaferInformationtransmits the DieID low.f_DebugResponse.RtcTimetransmits the current device time.f_DebugResponse.Uptimetransmits the uptime since the first 1ms Task started.
These messages are either sent by foxBMS 2 as part of its normal operation or
on request via a f_Debug message.