Alta mxr 2018 not charging. - Solved


Redwolf

My dog thinks I'm cool
Likes
1,677
Location
Brinnon, Wa.
While an impressive capability, let's maybe try not to shred the magnetic fields out of our motors... Just right to the ragged edge perhaps.
 

C5tor

Chief Comedic Instigator
Likes
1,720
Location
SF Bay Area, CA
While an impressive capability, let's maybe try not to shred the magnetic fields out of our motors... Just right to the ragged edge perhaps.

You guys are thinking too small. We should be tapping directly into the Earth’s geomagnetic fields, thus accessing the vast electrical potential of the Earth’s core! None shall stand against our mighty earthmagnet powered Altas! Buwahaha!!!

1574221831540.png
 

sergeynik

Member
Likes
17
Location
Kazakhstan
Internal ALTA can 500kbit /s

DDCP Module

100ms period
dccp-analogs 0x660 00 00 00 00 0d 37
charger status 0x652 08 00 00 e7 ff ff ff ff
charger control 0x650 00 00 00 00 04
1sec period
0x1ffff010 00 02 01 06 5b 44 fa 69
0x1ffff018 87 00 00

The module seems to have to be done by itself. Help with these CAN ID what you have there when charging your motorcycle


External charger can 250kbit/s

https://www.nothnagel-marine.de/med...lCon_Ladegerät_CAN-Bus-Communication-Spec.pdf
 

Jared

Well-known member
Likes
159
Location
Arlington, WA
day 2 (problem found)
schematic diagram
View attachment 4145

tested hi voltage

View attachment 4146


this connector seal passes antifreeze inside the unit
View attachment 4147

View attachment 4148View attachment 4149
Can you replace the exploded SMD transistor and the surface mount resistor that appears to have been blown off its pads, and run jumpers from the other side of the board in place of the burned traces and then test the unit. I think the transistors energize the windings of the relays and the relays function to connect and disconnect the battery from the charger.
 

Jared

Well-known member
Likes
159
Location
Arlington, WA
Can you replace the exploded SMD transistor and the surface mount resistor that appears to have been blown off its pads, and run jumpers from the other side of the board in place of the burned traces and then test the unit. I think the transistors energize the windings of the relays and the relays function to connect and disconnect the battery from the charger.
You could always take the top cover off your battery (be careful as one of the battery connections to/through the BMS board is a “banana plug” but the other is attached with a wire/guide/cover and screw and this wire must be carefully pulled to allow enough slack to remove the cover) and run two wires to the outside (thus bypassing the contactors in the lid) to charge the battery with a charger of your choice or design. Unfortunately your cells won’t get balanced, but it is a way you could charge.
 

Jared

Well-known member
Likes
159
Location
Arlington, WA
Internal ALTA can 500kbit /s

DDCP Module

100ms period
dccp-analogs 0x660 00 00 00 00 0d 37
charger status 0x652 08 00 00 e7 ff ff ff ff
charger control 0x650 00 00 00 00 04
1sec period
0x1ffff010 00 02 01 06 5b 44 fa 69
0x1ffff018 87 00 00

The module seems to have to be done by itself. Help with these CAN ID what you have there when charging your motorcycle


External charger can 250kbit/s

https://www.nothnagel-marine.de/media/downloads/Elcon_TCCH/ElCon_Ladegerät_CAN-Bus-Communication-Spec.pdf
I don’t have multi tool or any other CAN tool that doesn’t automatically translate, otherwise I would gladly share the ID’s and maybe even put them on a graph/table with time and battery voltage.
 

sergeynik

Member
Likes
17
Location
Kazakhstan
this module two part low voltage and hi voltage
low voltage including master MCU 2 x can bus, relays HV, spi bus to slave mcu . only digital I/O
isolated hi voltage part including slave MCU
analog measuring Voltage in HV bus
isolation ADUM4154 ( SPIsolator™ digital isolator) and dcdc 12->5v
 

Jared

Well-known member
Likes
159
Location
Arlington, WA
this module two part low voltage and hi voltage
low voltage including master MCU 2 x can bus, relays HV, spi bus to slave mcu . only digital I/O
isolated hi voltage part including slave MCU
analog measuring Voltage in HV bus
isolation ADUM4154 ( SPIsolator™ digital isolator) and dcdc 12->5v
It seems like the low voltage (master MCU) is still working and can communicate. I can see where the heat from the exploded transistor burned all the way through the board. The worst damage to the slave/high voltage section appears to be the long burned trace. Why not take a tiny grinder and remove traces that lead to damaged areas, solder jumpers to origins of traces, build a breadboard with new transistor, resistor and any other damaged components there may be, attach jumpers to it and test?Might be fun, especially if it works. As long as the IC’s on the board are not compromised, it seems like it could be repairable.
 

sergeynik

Member
Likes
17
Location
Kazakhstan
# DC Charge Port
can_ids.CAN_ID_0x1FFFF010
0, 0xffffffff, "DC Charge Port Build Timestamp", rs_format_build_time
32, 0xffffffff, "DC Charge Port Version", rs_format_build_version
can_ids.CAN_ID_0x1FFFF011
32, 0xffffffff, "DC Charge Port Build Tools Version", "0x{0:08x}"
can_ids.CAN_ID_0x1FFFF018
40, 0xff, "DC Charge Port CAN Controller Re-init Count", "{0:d}", 5
48, 0xff, "DC Charge Port Max CAN TX Error Count", "{0:d}", 5
56, 0xff, "DC Charge Port Max CAN RX Error Count", "{0:d}", 5
can_ids.CAN_ID_0x650
24, 0xff , "Charger State Command" , "{0:d}", 1
32, 0xffff, "Idc lim (A)", "{0:.3f}", 1, 0.001
48, 0xffff, "Vdc lim (V)", "{0:.2f}", 1, 0.01

can_ids.CAN_ID_0x651 # charger status
0, 0xffff, "Charger Idc Feedback (A)", "{0:.3f}", 1, 0.001
16, 0xffff, "Charger Vdc Feedback (V)", "{0:.1f}", 1, 0.01
32, 0xffff, "Charger Standby Flags", "0x{0:04x}", 1
48, 0xff , "Charger Fatal", "{0:d}", 1),
56, 0xff , "Charger State", "{0:d}", 1

CHARGER_FLAG_NO_PROXIMITY = 0x0001
CHARGER_FLAG_AC_CABLE_DISCONNECT = 0x0002
CHARGER_FLAG_INTERNAL_COMMS_FAIL = 0x0004
CHARGER_FLAG_VEXT_PRESENT = 0x0008
CHARGER_FLAG_TEMPERATURE_HI = 0x0010
CHARGER_FLAG_EXTERNAL_COMMS_FAIL = 0x0020
CHARGER_FLAG_EXTERNAL_FAULT = 0x0040
CHARGER_FLAG_CHASSIS_CAN_TIMEOUT = 0x0080
CHARGER_FLAG_INTERNAL_AC_DETECT = 0x0100
CHARGER_FLAG_GROUND_ABSENT = 0x0200
CHARGER_FLAG_VAC_RANGE = 0x0400
CHARGER_FLAG_BOOT_INIT = 0x8000

can_ids.CAN_ID_0x652 #charger-status
0, 0xffff, "Charger Idc Feedback (A)", "{0:.3f}", 1, 0.001
16, 0xffff, "Charger Vdc Feedback (V)", "{0:.1f}", 1, 0.01
32, 0xffff, "Charger Standby Flags", "0x{0:04x}", 1
48, 0xff , "Charger Fatal", "{0:d}", 1
56, 0xf , "Charger State", "{0:d}", 1
60, 0xf , "Charger Limit", "{0:d}", 1

# Charger State
CHARGER_STATE_FAULT = 8
CHARGER_STATE_STANDBY = 9
CHARGER_STATE_CHARGE_ISOLATED = 10
CHARGER_STATE_CHARGE_NOT_ISOLATED = 11
# Charger Limit
CHARGER_LIMIT_NONE = 0
CHARGER_LIMIT_CHARGER_CAPABILITIES = 1
CHARGER_LIMIT_DC_CURRENT = 2
CHARGER_LIMIT_CHARGER_THERMAL = 3

can_ids.CAN_ID_0x660 # dccp analogs
16, 0xffff, "DCCP PCB Temperature (C)", "{0:.2f}", 1, 0.01, signed=True
32, 0xffff, "DCCP Vbus External (V)", "{0:.2f}", 1, 0.01
48, 0xffff, "DCCP Vbus Internal (V)", "{0:.2f}", 1, 0.01
 
Top Bottom