System Fault A6: AIM Module Not Communicating

[new-brammo-guy]

Hi All,

2016 Victory Empulse TT here. Has anyone had the System Fault A6: AIM Module Not Communicating? I read a couple other posts regarding A6 but I'm not even sure what the "Auxiliary Input Module" even is on the Empulse TT.

The bike won't run.

You can see my other recent threads that my bike has had a few faults recently and it's not working. Now the A6 comes on right away with key-on and then after some waiting the B40 is the final blow.

Thanks a lot

[EV promise]

Hi, this is an image of the AIM unit from the Brammo Empulse manual if it shows up this time! It was mentioned in a previous post for the A6 issue.

[new-brammo-guy]

Thanks a lot EV promise!

The vehicle and battery control electronics were changed from Brammo to Victory. Does the summary below look correct?

Brammo Empulse:
AIM horizontal on top of batteries with two connectors. VCU vertical in front of the batteries with one connector

Victory Empulse TT:
BMC (one connector) mounted above the VCU. Both lay horizontally on top of battery modules.

[1] The Auxiliary Input Module (AIM, in the Brammo Empulse with two connectors) was renamed and possibly redesigned as the Battery Management Controller (BMC, Victory Empulse TT with one connector). See attached images both the two different Brammo and Victory Empulse manuals.

[2] The Vehicle Control Unit (VCU) in the Brammo Empulse with one connector was redesigned and moved to sit below the BMC in the Victory Empulse TT with two connectors.

Note: One of the images in the Victory Empulse TT manual shows the BMC with two connectors - which doesn't seem correct. Maybe they reused an image from the Brammo AIM incorrectly (?!).

[new-brammo-guy]

One more attachment for previous post

[new-brammo-guy]

Final attachment from previous post

[new-brammo-guy]

Do any Victory Empulse TT owners have experience with Fault A6? If the Victory Empulse doesn't have an AIM, what's actually failing here?!

[new-brammo-guy]

Here's the view from the Victory Diagnostic Software. Nothing shows up in the "AIM" software version box (assuming that means it's not responding?). I also didn't find any "AIM" .bin files in the Calibration files.

So does anyone have more details on the AIM and A9 (for a 2016 Victory Empulse TT)?

Does anyone have the AIM .bin calibration file?

Thanks a lot

[new-brammo-guy]

When I "start" the motorcycle, the motor controller firmware shows up (but still not the AIM). See attached.

p.s. I have an IXXAT dongle and made a CANBUS connector thanks to info from others on this forum (thank you!)

[EV promise]

Hi, I read somewhere about the notes about the various versions of the firmware and I don't believe you are missing it. It was renamed. If I can find it I'll post the txt. I don't have any Victory Empulse wiring diagrams etc so not going to be of much help. I to have the IXXAT dongle but never made the lead thought I have the parts.

[EV promise]

VCU_F130 firmware:
o Fixed CPI firmware upload issues
o Eliminated the skipped speed values by reworking the PCA counter algorithm
o No longer prevent drive if the headlight is detected to be off (broken, or fuse blown)
o Added a filter for Instant Power but only when motor power is displayed, because the controller reports voltage and current much more often than the BMS
o Added support for BMU firmware upload
o Added support for MC firmware upload via a fast CAN bridge, DASH-MC
o Now can switch between performance modes while moving, but only if the throttle is 0%.
o The Interlock fault due to the loopback missing (as opposed to relay open) now also reports a C3 on the Dash
o Remove the check for AIM firmware version, since there is no AIM anymore
o Reduced the on-time of the top green LEDs during the "low SOC, please recharge" mode. Also, the LEDs now flash three times instead of constant on
o Charger or Charging faults alert the user to the fault using the headlight and green LEDs. They are flashed once every 15 seconds

[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?