General > Victory Empulse

System Fault A6: AIM Module Not Communicating

<< < (3/3)

new-brammo-guy:
Wow - thanks EV promise! OK - I see those notes here: http://www.e-motorraeder.eu/t218f52-Softwareupdate-Empulse-R.html.

Based on the "Victory EV Diagnostics" software (see screenshots above), my VCU F130 firmware is "05.02.05"

Looks like the VCU F130 firmware 05.02.26 is named 75516491_VCU2V2M26.BIN and is available in the "Calibration" files from Digital Wrench here: http://polaris.diagsys.com/modules.php?name=Downloads&d_op=viewdownload&cid=45

*I found the .BIN and firmware number here (attached as .pdf): https://dot.report/bulletins/10195281
------
Dash
Victory Diagnostics
92906016_2_11_FIRMWARE_DASH_ICU.BIN
01.02.11
VCU F130
Victory Diagnostics
75516491_VCU2V2M26.BIN
05.02.26
VCU CPI 506
Victory Diagnostics
89210795_CPIV1_22.BIN
01.01.22
BMC
Battery Diagnostics
54302376_8X_00M67_FIRMWARE_BMS.BIN
87.00.67
Motor Controller
Victory MC Setup
19680795_SN0076-07_0X3F53.dld
SN0076.07 ROM
checksum: 0x3f53
M.C. Configuration
Victory MC Setup
77218397_02_SCFG_0076-07_0x6e21.dcf
Configuration
checksum: 0x6e21[/img]

new-brammo-guy:
Updated all of the firmware (attached).

No longer getting the A6 Fault (EV Promise to the rescue on that one!), but still have the B40 error because of the battery sensor errors (see attached).

Since it seems that the BMS board in the battery module is having issues, I'm wondering if I could just fake the temp sensors on the CANBUS. I'd have to hijack the CANBUS and pass everything through my own microcontroller then spit out the "cleaned" values with OK temps. Anyone try this?

Navigation

[0] Message Index

[*] Previous page