openinverter.org wiki - User contributions [en]

VCU Comparison

2025-01-01T18:58:52Z

Jokeitch: updated aem

A VCU can mean many things, but for the purposes of this page, a VCU means any programmable 12V controller that is designed or found to be useful in an EV conversion.

While "Primary use case" tells you what these controllers are intended for, the other fields tell you what they're capable of when configured or re-programmed for your use case.

In the spirit of open source, controllers with open source features are added leftmost on the table.

==== To-do ====

* Add other VCUs that have been used by people on the openinverter forums
** https://openinverter.org/forum/viewtopic.php?t=1148&hilit=arduino+due&start=125
*** https://github.com/arber333/Arduino-DUE-VCU
*** https://github.com/arber333/ESP32-VCU
** https://github.com/jamiejones85/ESP32CanGauge
** https://github.com/marlinarnz/eVCU
** https://github.com/MagnusThome/RejsaCAN-ESP32
** https://github.com/noisymime/speeduino
** https://github.com/chrskly/electric-mustang-wiring
** https://github.com/jamiejones85/ESP32-Chademo
** https://github.com/mumme74/CarTransporter/blob/aeda138992301123158cd2d2c1d10c55ae537238/libraries/system_things/PID.h#L263
* Fill in missing info
* Add links

Add open source VCUs:
* johu's stm32-car (https://github.com/jsphuebner/stm32-car)

Add closed source VCUs:
* AEM VCU275 (https://www.aemelectronics.com/products/ev_conversions/vehicle_control_unit/parts/30-8001) and VCU300 (https://www.aemelectronics.com/products/ev_conversions/vehicle_control_unit/parts/30-8100)
** Note that the VCU200 has been quietly sunset in favor of the vcu275
* Engovis EVS-VCU (https://citini.com/product/evs-vehicle-control-unit/)
* Thunderstruck VCU - for the Nissan Leaf, UQM, and Coda motors (https://www.thunderstruck-ev.com/dilithium-vcu.html)
* Resolve-EV Resolve Controller (https://www.resolve-ev.com/shop/p/resolve-controller)

==== The comparison table ====
{| class="wikitable"
|+ VCU Comparison
|-
! Comparison !! ZombieVerter !! GEVCU7 !! Mini-E-VCU !! iPDM56v1.1
|-
| Open source software (link) || [https://github.com/damienmaguire/Stm32-vcu Yes] || [https://github.com/collin80/GEVCU7 Yes] || [https://github.com/aot93/Mini-E-VCU Yes] || [https://github.com/celeron55/ipdm56 Yes]
|-
| Open source hardware (link) || [https://github.com/damienmaguire/Stm32-vcu Yes] || No || [https://easyeda.com/aot93/mini-e-t4-vcu_copy Yes] || No
|-
| Schematics and board layouts (link) || [https://github.com/damienmaguire/Stm32-vcu/tree/master/Hardware/Zombie Yes] || No || [https://easyeda.com/aot93/mini-e-t4-vcu_copy Yes] || [https://github.com/celeron55/ipdm56/tree/master/ipdmhw1.1 Yes]
|-
| In stock (link) || [https://www.evbmw.com/index.php/evbmw-webshop/vcu-boards/zombie-vcu Yes] || [https://store.evtv.me/products/generalized-electric-vehicle-control-unit-gevcu-version-7?_pos=1&_sid=597515b42&_ss=r Yes] || No || 2023-02
|-
| Price inc. VAT + shipping + enclosure || 350€ || 1500€ || ~80€ || 140€
|-
| External connector pins || 56 || || 48 || 56
|-
| External connector pin size (A) || 5A? || ? || 6A/12A || 5A?
|-
| Primary use case || Inverter control including Toyota || CAN inverter control, logging || Outlander inverter || Power distribution, I/O extension
|-
| Software platform || libopeninv || Arduino || Arduino || Arduino
|-
| External configuration interface || Wifi || Bluetooth, Wifi, USB serial || ? || USB serial, TTL serial
|-
| Configuration format || Parameter list || ? || Arduino sketch, ready-made || Arduino sketch, template
|-
| Out-of-the box supported inverter brands || OpenInverter, Nissan, Toyota, Lexus, Outlander? || DMOC, CODA, Brusa, PM100, C300 || Outlander || None
|-
| Official companion modules || No || No || aot93's BMS and dash || No
|-
| MCU family || STM32F107 || iMXRT1062 || iMXRT1062(Teensy) || AVR
|-
|CPU
|72 MHz
|600 MHz
|600 MHz
|
|-
| Flash ||256 kB || 16MB || 16MB || 32kB
|-
| RAM ||64 kB || 1024kB || 1024kB || 2kB
|-
| Supply voltage range || || || || 8...16V
|-
| Standby mode description || || || || 6mA running Arduino sketch at slow clock speed
|-
| Buses || 3x CAN, 1x Toyota, 1x LIN, 1x RS232? || 3x CAN || ? || 2x CAN
|-
| Number of inputs || 10? || 12 || ? || 14
|-
| Analog inputs (including throttle and external NTC channels) || 6? || 8 || ? || 5
|-
| PWM inputs || || || || 2
|-
| Additional special inputs || ? || ? || ? || 12V battery voltage monitoring
|-
| Signal PWM outputs || 1? || || || 0
|-
| Power PWM outputs (low / high side, A) || 3x L ?A || || || 4x L 3A
|-
| Low-side power outputs, total A || 5A? (limited by ground pin) || 16A || ? || 20A
|-
| Low-side power outputs, count || 9? || 8 || ? || 10
|-
| High-side power outputs, total A || ? || ? || ? || 15A
|-
| High-side power outputs, count || ? || ? || ? || 10
|-
| Analog outputs || 2x AC coupled, 2x digital resistors || ? || ? || 2x 0-500mA low side slow
|-
| Sensor power outputs || 5V || 5V 700mA, 3.3V 400mA || ? || 5V 500mA
|-
| Outputs readable as inputs || || || || 8
|-
| Customizable jumpers/resistors || 0? || ? || ? || 32
|-
| Used in projects (links) || [https://www.youtube.com/c/Evbmw/videos Pretty much everything Damien does] || || || [https://openinverter.org/forum/viewtopic.php?p=51531#p51531 celeron55's Omega]
|}

[[Category:VCU]]

Dilong/Cascadia Chargers

2024-10-28T17:42:33Z

Jokeitch: Added rear of charger image

== Overview ==
Dilong makes a series of combo OBC+DCDC charging units.

At least one of them is purchased and resold by Cascadia Motion as their branded combo charger.

This page mostly refers to the '''DA8KM22A-400C-14RC''' model, which has a 6.6kw OBC and 1.5kw DCDC

[[File:PXL 20241020 024043714.jpg|thumb|Overall image of DA8KM22A-400C-14RC]]

[[File:PXL 20241020 024034986.jpg|thumb|Front view of DA8KM22A-400C-14RC]]

[[File:PXL 20241027 210206729.jpg|thumb|Rear of charger, showing M8 ground bolt hole, and waterproof vent plug]]

== Learning/Resources ==
Documentation for Cascadia combo charger: https://www.cascadiamotion.com/productlist/22-charging-converters/21-combo

Page for equivalent Dilong charger: https://www.powerdilong.com/products/dilong-integrated-charger-2-in-1-6.6kw-obc-and-1.5kw-dcdc-combo-unit-for-electric-vehicle

''Note: to get direct documentation from dilong, you need to email them and request it''

== Terminal crimps ==

High voltage DC connector: '''AMP MCP 6.3/4.8K, CONTACT, SWS''', part number '''1241418-4''', 10awg wire

High voltage AC connector (charge port): Identical to the HVDC, '''AMP MCP 6.3/4.8K, CONTACT, SWS''', part number '''1241418-4''', 10awg wire

12v DCDC positive connection: '''Standard Circular Contacts Socket Contact, Machined, Crimp Barrel, Radsok, Size 6mm, Silver, Wire Range 20-25mm2, 4AWG''', part number '''HS25BCS''', 4awg wire

Low voltage signal connection: '''Standard Circular Contacts ECO MATE-RM, AQUARIUS''' , part number '''MS20M23F''', 22awg wire

Rear Ground lug: M8 bolt, roughly equivalent to SAE 5/16ths unknown thread pitch

== Connectors ==

== Pin out connections ==
Documentation for the chargers includes detailed pin out instructions, and they're identical between the cascadia and dilong versions, '''with one exception'''

'''If sourced from dilong''', use the dilong low voltage connector pinout:
A: CAN Bus High
B: BMS/VCU Power positive, 12V+ when AC power is applied
C: BMS/VCU Power negative, 12V-
E: HVIL interlock 1
F: HVIL interlock 2
G: CAN Bus Low
T: Power for DC/DC Converter logic, apply 9 to 16V to power internal logic
S: Enable for DC/DC Converter, apply 9to 16V to enable. This is OR’d with the CAN Enable Command.

The cascadia version pinout is slightly different

== Compatibility ==
This charger is drop-in compatible with the AEM VCU line of motor controllers, and AEMcal has the dilong charger as a selectable option in it's configuration for chargers

== References ==
<references />
[[Category:Dilong]] [[Category:Cascadia]] [[Category:Charger]] [[Category:DC/DC]]

File:PXL 20241027 210206729.jpg

2024-10-28T17:40:59Z

Jokeitch:

Rear of dilong combo charger

Dilong/Cascadia Chargers

2024-10-25T16:48:20Z

Jokeitch: Data dump page for dilong and cascadia combo chargers

== Overview ==
Dilong makes a series of combo OBC+DCDC charging units.

At least one of them is purchased and resold by Cascadia Motion as their branded combo charger.

This page mostly refers to the '''DA8KM22A-400C-14RC''' model, which has a 6.6kw OBC and 1.5kw DCDC

[[File:PXL 20241020 024043714.jpg|thumb|Overall image of DA8KM22A-400C-14RC]]

[[File:PXL 20241020 024034986.jpg|thumb|Front view of DA8KM22A-400C-14RC]]

== Learning/Resources ==
Documentation for Cascadia combo charger: https://www.cascadiamotion.com/productlist/22-charging-converters/21-combo

Page for equivalent Dilong charger: https://www.powerdilong.com/products/dilong-integrated-charger-2-in-1-6.6kw-obc-and-1.5kw-dcdc-combo-unit-for-electric-vehicle

''Note: to get direct documentation from dilong, you need to email them and request it''

== Terminal crimps ==

High voltage DC connector: '''AMP MCP 6.3/4.8K, CONTACT, SWS''', part number '''1241418-4''', 10awg wire

High voltage AC connector (charge port): Identical to the HVDC, '''AMP MCP 6.3/4.8K, CONTACT, SWS''', part number '''1241418-4''', 10awg wire

12v DCDC positive connection: '''Standard Circular Contacts Socket Contact, Machined, Crimp Barrel, Radsok, Size 6mm, Silver, Wire Range 20-25mm2, 4AWG''', part number '''HS25BCS''', 4awg wire

Low voltage signal connection: '''Standard Circular Contacts ECO MATE-RM, AQUARIUS''' , part number '''MS20M23F''', 22awg wire

== Connectors ==

== Pin out connections ==
Documentation for the chargers includes detailed pin out instructions, and they're identical between the cascadia and dilong versions, '''with one exception'''

'''If sourced from dilong''', use the dilong low voltage connector pinout:
A: CAN Bus High
B: BMS/VCU Power positive, 12V+ when AC power is applied
C: BMS/VCU Power negative, 12V-
E: HVIL interlock 1
F: HVIL interlock 2
G: CAN Bus Low
T: Power for DC/DC Converter logic, apply 9 to 16V to power internal logic
S: Enable for DC/DC Converter, apply 9to 16V to enable. This is OR’d with the CAN Enable Command.

The cascadia version pinout is slightly different

== Compatibility ==
This charger is drop-in compatible with the AEM VCU line of motor controllers, and AEMcal has the dilong charger as a selectable option in it's configuration for chargers

== References ==
<references />
[[Category:Dilong]] [[Category:Cascadia]] [[Category:Charger]] [[Category:DC/DC]]

File:PXL 20241020 024034986.jpg

2024-10-25T16:39:26Z

Jokeitch: Jokeitch uploaded a new version of File:PXL 20241020 024034986.jpg

front view of DA8KM22A-400C-14RC

File:PXL 20241020 024043714.jpg

2024-10-25T16:37:25Z

Jokeitch: Jokeitch uploaded a new version of File:PXL 20241020 024043714.jpg

Overview image of dilong charger DA8KM22A-400C-14RC

File:PXL 20241020 024034986.jpg

2024-10-25T16:34:43Z

Jokeitch:

front view of DA8KM22A-400C-14RC

File:PXL 20241020 024043714.jpg

2024-10-25T16:34:11Z

Jokeitch:

Overview image of dilong charger DA8KM22A-400C-14RC

Tesla Model 3 Charger/DCDC ("PCS")

2024-10-16T22:28:37Z

Jokeitch: Added known limitations section

== Overview ==
The Tesla Model 3 has a "Power Conversion System" (also known as the "PCS") which contains both a 10kW AC charger and a ??W DCDC converter. The PCS is located inside the "Penthouse" part of the main traction battery system.

== Learning/Resources ==
Video - The Tesla Project : Model 3 PCS First Look - https://youtu.be/_TYvSmDJSPQ

Video - Tesla Model 3 Power Conversion System - https://youtu.be/3ARHdRwfxjY

OpenInverter PCS overview/tech thread: https://openinverter.org/forum/viewtopic.php?f=10&t=171

OpenInverter PCS controller support thread: https://openinverter.org/forum/viewtopic.php?p=27744#p27744

Damien's GitHib: https://github.com/damienmaguire/Tesla-Model-3-Charger

== Troubleshooting/Seeking help ==
If you encounter issues with the PCS, it's generally good practice to collect the following information and [https://openinverter.org/forum/viewforum.php?f=10 create a thread on the forums] with a description as detailed as you can be about the problem

All of these instructions are also available in a [https://youtu.be/RYCl0ZL4cG4 youtube video demo by damien]

# model year of the car it came out of
# any serial numbers on the penthouse or pcs itself, from stickers or identifying markings
## Located on the top, above the high voltage connection plug, should be a rectangular white sticker with two numbers that begin with "DEV-" and "SDEVR-"
# firmware version on the pcs
## In the web interface, this is listed in the "version" row under the "spot values" header, for example "1.16.R"
##* ''edit, this may just be the firmware version of the PCS controller itself''
# a dump of parameters from the controller
## In the web interface, under the parameters section, there's a link to "download parameters file"
# A list of all alerts generated in the alert log
## First, enable the alert log system, by selecting "on" next to the row labeled "AertLog" under the "general" subsection under Parameters
## View the first saved alert by putting 0 into the Alerts row box and hitting enter, then hitting refresh on the top right, then scrolling down to the "PCSAlerts" row within the "spot values" section. This shows the first alert. To see other alerts, repeat by entering 1, 2, 3 etc into the Alerts row box and hitting enter+refresh again
## to see the total number of alerts you can scroll down to "PCSAlertCnt" in the "spot values" section, note that only 10 alerts can be stored at a time.

== Hardware ==

=== Controller ===
Damien from EVBMW has designed a control solution which is open source hardware and software. Design files for the controller hardware and software sources are available on Damien's GitHub [https://github.com/damienmaguire/Tesla-Model-3-Charger here]. Controllers are also available as a fully-built kit (with pre-loaded software) on the EVBWM webstore<ref>https://www.evbmw.com/index.php/evbmw-webshop/tesla-boards/tesla-model-3-pcs-con (Backup: [http://web.archive.org/web/20221016211810/https://www.evbmw.com/index.php/evbmw-webshop/tesla-boards/tesla-model-3-pcs-con Web Archive])</ref>.

=== Data Connector on PCS (12-way) ===
''EDITOR'S NOTE: my research shows some conflicting/different part numbers mentioned - would appreciate some clarification here once validated''

As per: https://openinverter.org/forum/viewtopic.php?p=26614#p26614<blockquote>''The connector used for communications with the PCS:'' <ref>https://www.te.com/global-en/product-1379662-5.html (Backup: [http://web.archive.org/web/20221016212020/https://www.te.com/global-en/product-1379662-5.html Web Archive])</ref><ref>https://www.mouser.ie/ProductDetail/TE-Connectivity-AMP/1379662-1?qs=yDt3hdeEHFPzMcXLhRNNtw%3D%3D (Backup: [http://web.archive.org/web/20221016212258/https://www.mouser.ie/ProductDetail/TE-Connectivity-AMP/1379662-1?qs=yDt3hdeEHFPzMcXLhRNNtw%3D%3D Web Archive])</ref>

''Pins:'' <ref>https://www.mouser.ie/ProductDetail/TE-Connectivity/1801069-2?qs=sGAEpiMZZMvlX3nhDDO4AIlVXMSSZRpGH8WODUA4Ad4%3D (Backup: [https://web.archive.org/web/20221016212418/https://www.mouser.ie/ProductDetail/TE-Connectivity/1801069-2?qs=sGAEpiMZZMvlX3nhDDO4AIlVXMSSZRpGH8WODUA4Ad4%3D Web Archive])</ref>

''In true Muskian fashion it seems they use the 1379662-5 natural color variant of the plug which has no coding tabs. It is of course unavailable from mouser. The black and green variants are functionally identical and should work with coding tabs removed.''</blockquote>
[[File:PXL 20231125 230415175~2.jpg|thumb|annotated view of PCS data connector viewed from the front]]
However, as per: https://github.com/muehlpower/EV-FFB, there is also mention of 1318774-1 (white) or 1318774-2 (black) for the comms/data connector.
[[File:V3 PCS controller pinout diagram.jpg|thumb]]

=== Power Connectors ===
The power-side connector assemblies are not widely available. The housings are a Tesla internal part (photos/part numbers [https://openinverter.org/forum/viewtopic.php?p=27744#p27744 here]), however, 3D printable housings have been made available [https://github.com/muehlpower/EV-FFB here]. The terminals also aren't widely available, but are known. As per https://github.com/muehlpower/EV-FFB:

Note: the US variant of the charger (1-phase) has a different AC pin layout; see photo for reference.<blockquote>''The contacts for 400V are Uni F630 from MTA, part number 1107940. For 12V Kostal PLK 14.5, part number 23124734300. The connector for the data is from TE connectivity, part number 1318774-1 for white or 1318774-2 for black.''</blockquote>
[[File:Model 3 US charger variant AC connector.png|thumb|AC connector pinout for US Model 3 PCS (1-phase)]]

=== Connections ===
[[File:Tesla PCS Connection diagram 8162022.png|thumb]]
The minimum wiring needed to wake the PCS:

# PCS controller connected to PCS via 12-way X420
# PCS controller is powered via 20-way +12V input pin and grounded to chassis via 20-way ground pin
# +12v and Chassis ground applied to PCS 12v Connector input terminal
# Chassis ground on the PCS case

== Firmware ==

=== Current Version ===
The current version of the PCS firmware can be found here: https://github.com/damienmaguire/Tesla-Model-3-Charger/releases

The current firmware will auto detect what Tesla firmware is installed on the PCS and adjusts the CAN messages accordingly (different versions of the PCS firmware from Tesla have different CAN requirements, '''if you encounter strange performance from the PCS it could have a different firmware version than expected''', see troubleshooting section). It will also auto detect if the PCS is EU or US spec and whether single or three phase AC is connected. It also includes an integrated alert logging function to help diagnose any issues the PCS sees.

=== Alerts Logging ===
The PCS has an array of potential alerts to help diagnose issues. The images below show a matrix of potential alerts
[[File:PCS Alert Table001.jpg|thumb]]
[[File:PCS Alert Table002.jpg|thumb]]

Initially alerts had to be identified through CAN logs (PCS IPC CAN). In later firmware releases, the PCS web interface incorporated a decoder to help identify alerts (decimal number identifier relating to the alert tables shown here). In the current version of firmware, the alerts are now displayed in word format to make it easier and quicker to troubleshoot.

'''''Below is a list of all alert codes the PCS can generate, with associated error code number, and plain text descriptions of what each one means'''''

{| class="wikitable mw-collapsible mw-collapsed"
|+ class="no wrap" | Alert Codes
|-
|
! scope="col" | Error code / name
! scope="col" | Error description
|-
! scope="row" | 01
| chgHwInputOc || ???
|-
! scope="row" | 02
| chgHwOutputOc|| ???
|-
! scope="row" | 03
| chgHwInputOv|| ???
|-
! scope="row" | 04
| chgHwIntBusOv|| ???
|-
! scope="row" | 05
| chgOutputOv|| ???
|-
! scope="row" | 06
| chgPrechargeFailedScr|| ???
|-
! scope="row" | 07
| chgPhaseTempHot|| ???
|-
! scope="row" | 08
| chgPhaseOverTemp|| ???
|-
! scope="row" | 09
| chgPfcCurrentRegulation|| ???
|-
! scope="row" | 10
| chgIntBusVRegulation || ???
|-
! scope="row" | 11
| chgLlcCurrentRegulation || ???
|-
! scope="row" | 12
| chgPfcIBandTracerFault || ???
|-
! scope="row" | 13
| chgPrechargeFailedBoost || ???
|-
! scope="row" | 14
| chgTempRationality || ???
|-
! scope="row" | 15
| chg12vUv || ???
|-
! scope="row" | 16
| chgAllPhasesFaulted || ???
|-
! scope="row" | 17
| chgWallPowerRemoval || ???
|-
! scope="row" | 18
| chgUnknownGridConfig || ???
|-
! scope="row" | 19
| acChargePowerLimited || ???
|-
! scope="row" | 20
| chgEnableLineMismatch || "Charge Enable Line Mismatch", Charger was commanded to start over CAN, but the enable line hasn't been correctly brought up
|-
! scope="row" | 21
| hvpMia || ???
|-
! scope="row" | 22
| bmsMia || ???
|-
! scope="row" | 23
| cpMia || ???
|-
! scope="row" | 24
| vcfrontMia || ???
|-
! scope="row" | 25
| cpu2Malfunction || ???
|-
! scope="row" | 26
| watchdogAlarmed || ???
|-
! scope="row" | 27
| chgInsufficientCooling || ???
|-
! scope="row" | 28
| chgOutputUv || The charger was commanded to start, but the AC high voltage is less than what is required to actually charge
|-
! scope="row" | 29
| chgPowerRationality || ???
|-
! scope="row" | 30
| canRationality || ???
|-
! scope="row" | 31
| uiMia || ???
|-
! scope="row" | 32
| unused || ???
|-
! scope="row" | 33
| hvBusUv || ???
|-
! scope="row" | 34
| hvBusOv || ???
|-
! scope="row" | 35
| lvBusUv || ???
|-
! scope="row" | 36
| lvBusOv || ???
|-
! scope="row" | 37
| resonantTankOc || ???
|-
! scope="row" | 38
| claFaulted || ???
|-
! scope="row" | 39
| sdModuleClkFault || ???
|-
! scope="row" | 40
| dcdcMaxPowerReached || ???
|-
! scope="row" | 41
| dcdcOverTemp || ???
|-
! scope="row" | 42
| dcdcEnableLineMismatch || ???
|-
! scope="row" | 43
| hvBusPrechargeFailure || ???
|-
! scope="row" | 44
| 12vSupportRegulation || ???
|-
! scope="row" | 45
| hvBusLowImpedance || ???
|-
! scope="row" | 46
| hvBusHighImpedence || ???
|-
! scope="row" | 47
| lvBusLowImpedance || ???
|-
! scope="row" | 48
| lvBusHighImpedance || ???
|-
! scope="row" | 49
| dcdcTempRationality || ???
|-
! scope="row" | 50
| dcdc12VsupportFaulted || ???
|-
! scope="row" | 51
| chgIntBusUv || ???
|-
! scope="row" | 52
| acVoltageNotPresent || ???
|-
! scope="row" | 53
| chgInputVDropHigh || ???
|-
! scope="row" | 54
| chgInputVDropTooHigh || ???
|-
! scope="row" | 55
| chgLineImedanceHigh || ???
|-
! scope="row" | 56
| chgLineImedanceTooHigh || ???
|-
! scope="row" | 57
| chgInputOverFreq || ???
|-
! scope="row" | 58
| chgInputUnderFreq || ???
|-
! scope="row" | 59
| chgInputOvRms || ???
|-
! scope="row" | 60
| chgInputOvPeak || ???
|-
! scope="row" | 61
| chgVLineRationality || ???
|-
! scope="row" | 62
| chgILineRationality || ???
|-
! scope="row" | 63
| chgVOutRationality || ???
|-
! scope="row" | 64
| chgIOutRationality || ???
|-
! scope="row" | 65
| chgPllNotLocked || ???
|-
! scope="row" | 66
| dcdcHvRationality || The PCS is attempting to start up the DCDC converter, but there isn't any high voltage provided / Are the high voltage lines hooked up to the PCS correctly?
|-
! scope="row" | 67
| dcdcLvRationality || ???
|-
! scope="row" | 68
| dcdcTankvRationality || ???
|-
! scope="row" | 69
| chgPfcLineDidt || ???
|-
! scope="row" | 70
| chgPfcLineDvdt || ???
|-
! scope="row" | 71
| chgPfcILoopRationality || ???
|-
! scope="row" | 72
| cpu2ClaStopped || ???
|-
! scope="row" | 73
| unexpectedAcInputVoltage || ???
|-
! scope="row" | 74
| hvBusDischargeFailure || ???
|-
! scope="row" | 75
| hvBusDischargeTimeout || ???
|-
! scope="row" | 76
| dcdcEnDeassertedErr || "DCDC enable, de-asserted error", Artifact in the software caused by few milisecond delay between DCDC being commanded to shut down over CAN and the hardware line being disabled
|-
! scope="row" | 77
| microGridEnergyLow || ???
|-
! scope="row" | 78
| chgStopDcdcTooHot || ???
|-
! scope="row" | 79
| eepromOperationError || ???
|-
! scope="row" | 80
| damagedPhaseDetected || ???
|-
! scope="row" | 81
| dcdcPchgTimeout || ???
|-
! scope="row" | 82
| dcdcPchgUnsafeDiVoltage || ???
|-
! scope="row" | 83
| triggerOdin || ???
|-
! scope="row" | 84
| unused || ???
|-
! scope="row" | 85
| dcdcFetsNotSwitching || ???
|-
! scope="row" | 86
| dcdcInsufficientCooling || ???
|-
! scope="row" | 87
| nvramRecordStatusError || ???
|-
! scope="row" | 88
| pchgParameters || ???
|-
! scope="row" | 89
| hvBusDischargeIrrational || ???
|-
! scope="row" | 90
| expectedAcVoltageSourceMissing || ???
|-
! scope="row" | 91
| chgIntBusRationality || ???
|-
! scope="row" | 92
| chgPowerLimitedByBusRipple || ???
|-
! scope="row" | 93
| powerRailRationality || ???
|-
! scope="row" | 94
| pcsDcdcNeedService || ???
|-
! scope="row" | 95
| dcdcSensorlessModeActive || ???
|-
! scope="row" | 96
| microGridOverLoaded || ???
|-
! scope="row" | 97
| rebootPhaseDetected || ???
|-
! scope="row" | 98
| gridFreqDroopDetectedSilent || ???
|-
! scope="row" | 99
| microGridOverLoadedSilent || ???
|-
! scope="row" | 100
| microGridEnergyLowSilent || ???
|-
! scope="row" | 101
| phMachineModelIrrational || ???
|-
! scope="row" | 102
| resetWithDCDCCmdAsserted || ???
|-
|}

== Testing ==

=== First Power Up ===

Set up to initially test connections between a PCS and the PCS controller are straightforward. This can be done without any HV DC battery or charging connected to the PCS. Once the PCS controller is connected to the PCS (follow the relevant V2 or V3 pin-outs) the basic steps are:

# Connect the PCS aluminium case to LV ground
# Connect PCS controller ground wire to 12V ground
# Connect PCS 12V power wire via a 5A fuse to +12V
# Observe the PCS controller continuous 3.3V indicator red LED and the flashing activity red LED
# Connect to the PCS controller wifi (SSID will be, for example , ESP-DC87FA) to view the web interface (v3 has a default IP address of 192.168.4.1). The interface will indicate that the PCS 'opmode' is 'Off' at this time
# On the web interface, change 'inputype' to 'Manual' in the drop down menu and select refresh at the top of the screen
# On the web interface, change 'activate' to 'Both'. This will tell the PCS to try start DC-DC and Charging if enabled (as above, these are not connected at this time so will generate alerts that will be mentioned further below)
# On the web interface, change 'AlertLog' to 'On'. This will tell the PCS to show any alerts
# To enable the PCS connect the PCS controller 'Input 1 (enable)' wire to +12V and select refresh at the top of the screen. 'Opmode' should now change to 'Run' on the web interface to show the PCS is now operational
# At this point, 'PCSAlertCnt' will likely show a number indicating the number of alerts the PCS has flagged and 'PCSAlerts' will show the first alert
# To see each alert separately, under General, change the number in the 'Alert' option (0 indicates first alert and should be default) to the next sequential number and select refresh at the top of the screen. 'PCSAlerts' will now show a description of the selected alert. Do this to step through each alert (total number indicated by 'PCSAlertCnt')
# Typical alerts with this configuration (no HV DC battery or charger interface connected) will be: 63chgVOutRationality, 66dcdcHVRationality
# Now the connections and communication with the PCS and controller are established, further testing can be carried out to check DC-DC and charging functionality. See below 

=== DC-DC First Test ===
TBC

=== AC Charging Test ===
TBC

=== Limitations/quirks ===
* The PCS reacts poorly to small capacity 12v batteries, specifically its DC voltage regulation can behave erratically. Small as in ~40AH

* The PCS CANNOT be commanded to charge over canbus to the controller. It must be told to charge by setting input pin 1 to 12v high (or pin 2 for dcdc charging). This makes it incompatible with certain combinations of controllers and BMS' such as the AEM vcu200 and the aem bms-18

* The minimum recommended HV DC battery voltage for testing is 250V (This needs to be confirmed)

=== Confirmed Working Models ===
to date a number of PCS units have been tested and confirmed to work with the current firmware:

* 1x 3p EU PCS from circa 2020 model year car
* 1x 1p US PCS from circa 2018 model year car. Running in BMW E46 touring conversion
* 1x 1p US PCS from circa 2020 model year car

== References ==
<references />
[[Category:OEM]] [[Category:Tesla]] [[Category:Charger]] [[Category:DC/DC]]

Tesla Model 3 Charger/DCDC ("PCS")

2024-10-03T18:39:24Z

Jokeitch: /* Confirmed Working Models */

== Overview ==
The Tesla Model 3 has a "Power Conversion System" (also known as the "PCS") which contains both a 10kW AC charger and a ??W DCDC converter. The PCS is located inside the "Penthouse" part of the main traction battery system.

== Learning/Resources ==
Video - The Tesla Project : Model 3 PCS First Look - https://youtu.be/_TYvSmDJSPQ

Video - Tesla Model 3 Power Conversion System - https://youtu.be/3ARHdRwfxjY

OpenInverter PCS overview/tech thread: https://openinverter.org/forum/viewtopic.php?f=10&t=171

OpenInverter PCS controller support thread: https://openinverter.org/forum/viewtopic.php?p=27744#p27744

Damien's GitHib: https://github.com/damienmaguire/Tesla-Model-3-Charger

== Troubleshooting/Seeking help ==
If you encounter issues with the PCS, it's generally good practice to collect the following information and [https://openinverter.org/forum/viewforum.php?f=10 create a thread on the forums] with a description as detailed as you can be about the problem

All of these instructions are also available in a [https://youtu.be/RYCl0ZL4cG4 youtube video demo by damien]

# model year of the car it came out of
# any serial numbers on the penthouse or pcs itself, from stickers or identifying markings
## Located on the top, above the high voltage connection plug, should be a rectangular white sticker with two numbers that begin with "DEV-" and "SDEVR-"
# firmware version on the pcs
## In the web interface, this is listed in the "version" row under the "spot values" header, for example "1.16.R"
##* ''edit, this may just be the firmware version of the PCS controller itself''
# a dump of parameters from the controller
## In the web interface, under the parameters section, there's a link to "download parameters file"
# A list of all alerts generated in the alert log
## First, enable the alert log system, by selecting "on" next to the row labeled "AertLog" under the "general" subsection under Parameters
## View the first saved alert by putting 0 into the Alerts row box and hitting enter, then hitting refresh on the top right, then scrolling down to the "PCSAlerts" row within the "spot values" section. This shows the first alert. To see other alerts, repeat by entering 1, 2, 3 etc into the Alerts row box and hitting enter+refresh again
## to see the total number of alerts you can scroll down to "PCSAlertCnt" in the "spot values" section, note that only 10 alerts can be stored at a time.

== Hardware ==

=== Controller ===
Damien from EVBMW has designed a control solution which is open source hardware and software. Design files for the controller hardware and software sources are available on Damien's GitHub [https://github.com/damienmaguire/Tesla-Model-3-Charger here]. Controllers are also available as a fully-built kit (with pre-loaded software) on the EVBWM webstore<ref>https://www.evbmw.com/index.php/evbmw-webshop/tesla-boards/tesla-model-3-pcs-con (Backup: [http://web.archive.org/web/20221016211810/https://www.evbmw.com/index.php/evbmw-webshop/tesla-boards/tesla-model-3-pcs-con Web Archive])</ref>.

=== Data Connector on PCS (12-way) ===
''EDITOR'S NOTE: my research shows some conflicting/different part numbers mentioned - would appreciate some clarification here once validated''

As per: https://openinverter.org/forum/viewtopic.php?p=26614#p26614<blockquote>''The connector used for communications with the PCS:'' <ref>https://www.te.com/global-en/product-1379662-5.html (Backup: [http://web.archive.org/web/20221016212020/https://www.te.com/global-en/product-1379662-5.html Web Archive])</ref><ref>https://www.mouser.ie/ProductDetail/TE-Connectivity-AMP/1379662-1?qs=yDt3hdeEHFPzMcXLhRNNtw%3D%3D (Backup: [http://web.archive.org/web/20221016212258/https://www.mouser.ie/ProductDetail/TE-Connectivity-AMP/1379662-1?qs=yDt3hdeEHFPzMcXLhRNNtw%3D%3D Web Archive])</ref>

''Pins:'' <ref>https://www.mouser.ie/ProductDetail/TE-Connectivity/1801069-2?qs=sGAEpiMZZMvlX3nhDDO4AIlVXMSSZRpGH8WODUA4Ad4%3D (Backup: [https://web.archive.org/web/20221016212418/https://www.mouser.ie/ProductDetail/TE-Connectivity/1801069-2?qs=sGAEpiMZZMvlX3nhDDO4AIlVXMSSZRpGH8WODUA4Ad4%3D Web Archive])</ref>

''In true Muskian fashion it seems they use the 1379662-5 natural color variant of the plug which has no coding tabs. It is of course unavailable from mouser. The black and green variants are functionally identical and should work with coding tabs removed.''</blockquote>
[[File:PXL 20231125 230415175~2.jpg|thumb|annotated view of PCS data connector viewed from the front]]
However, as per: https://github.com/muehlpower/EV-FFB, there is also mention of 1318774-1 (white) or 1318774-2 (black) for the comms/data connector.
[[File:V3 PCS controller pinout diagram.jpg|thumb]]

=== Power Connectors ===
The power-side connector assemblies are not widely available. The housings are a Tesla internal part (photos/part numbers [https://openinverter.org/forum/viewtopic.php?p=27744#p27744 here]), however, 3D printable housings have been made available [https://github.com/muehlpower/EV-FFB here]. The terminals also aren't widely available, but are known. As per https://github.com/muehlpower/EV-FFB:

Note: the US variant of the charger (1-phase) has a different AC pin layout; see photo for reference.<blockquote>''The contacts for 400V are Uni F630 from MTA, part number 1107940. For 12V Kostal PLK 14.5, part number 23124734300. The connector for the data is from TE connectivity, part number 1318774-1 for white or 1318774-2 for black.''</blockquote>
[[File:Model 3 US charger variant AC connector.png|thumb|AC connector pinout for US Model 3 PCS (1-phase)]]

=== Connections ===
[[File:Tesla PCS Connection diagram 8162022.png|thumb]]
The minimum wiring needed to wake the PCS:

# PCS controller connected to PCS via 12-way X420
# PCS controller is powered via 20-way +12V input pin and grounded to chassis via 20-way ground pin
# +12v and Chassis ground applied to PCS 12v Connector input terminal
# Chassis ground on the PCS case

== Firmware ==

=== Current Version ===
The current version of the PCS firmware can be found here: https://github.com/damienmaguire/Tesla-Model-3-Charger/releases

The current firmware will auto detect what Tesla firmware is installed on the PCS and adjusts the CAN messages accordingly (different versions of the PCS firmware from Tesla have different CAN requirements). It will also auto detect if the PCS is EU or US spec and whether single or three phase AC is connected. It also includes an integrated alert logging function to help diagnose any issues the PCS sees.

=== Alerts Logging ===
The PCS has an array of potential alerts to help diagnose issues. The images below show a matrix of potential alerts
[[File:PCS Alert Table001.jpg|thumb]]
[[File:PCS Alert Table002.jpg|thumb]]

Initially alerts had to be identified through CAN logs (PCS IPC CAN). In later firmware releases, the PCS web interface incorporated a decoder to help identify alerts (decimal number identifier relating to the alert tables shown here). In the current version of firmware, the alerts are now displayed in word format to make it easier and quicker to troubleshoot.

'''''Below is a list of all alert codes the PCS can generate, with associated error code number, and plain text descriptions of what each one means'''''

{| class="wikitable mw-collapsible mw-collapsed"
|+ class="no wrap" | Alert Codes
|-
|
! scope="col" | Error code / name
! scope="col" | Error description
|-
! scope="row" | 01
| chgHwInputOc || ???
|-
! scope="row" | 02
| chgHwOutputOc|| ???
|-
! scope="row" | 03
| chgHwInputOv|| ???
|-
! scope="row" | 04
| chgHwIntBusOv|| ???
|-
! scope="row" | 05
| chgOutputOv|| ???
|-
! scope="row" | 06
| chgPrechargeFailedScr|| ???
|-
! scope="row" | 07
| chgPhaseTempHot|| ???
|-
! scope="row" | 08
| chgPhaseOverTemp|| ???
|-
! scope="row" | 09
| chgPfcCurrentRegulation|| ???
|-
! scope="row" | 10
| chgIntBusVRegulation || ???
|-
! scope="row" | 11
| chgLlcCurrentRegulation || ???
|-
! scope="row" | 12
| chgPfcIBandTracerFault || ???
|-
! scope="row" | 13
| chgPrechargeFailedBoost || ???
|-
! scope="row" | 14
| chgTempRationality || ???
|-
! scope="row" | 15
| chg12vUv || ???
|-
! scope="row" | 16
| chgAllPhasesFaulted || ???
|-
! scope="row" | 17
| chgWallPowerRemoval || ???
|-
! scope="row" | 18
| chgUnknownGridConfig || ???
|-
! scope="row" | 19
| acChargePowerLimited || ???
|-
! scope="row" | 20
| chgEnableLineMismatch || "Charge Enable Line Mismatch", Charger was commanded to start over CAN, but the enable line hasn't been correctly brought up
|-
! scope="row" | 21
| hvpMia || ???
|-
! scope="row" | 22
| bmsMia || ???
|-
! scope="row" | 23
| cpMia || ???
|-
! scope="row" | 24
| vcfrontMia || ???
|-
! scope="row" | 25
| cpu2Malfunction || ???
|-
! scope="row" | 26
| watchdogAlarmed || ???
|-
! scope="row" | 27
| chgInsufficientCooling || ???
|-
! scope="row" | 28
| chgOutputUv || The charger was commanded to start, but the AC high voltage is less than what is required to actually charge
|-
! scope="row" | 29
| chgPowerRationality || ???
|-
! scope="row" | 30
| canRationality || ???
|-
! scope="row" | 31
| uiMia || ???
|-
! scope="row" | 32
| unused || ???
|-
! scope="row" | 33
| hvBusUv || ???
|-
! scope="row" | 34
| hvBusOv || ???
|-
! scope="row" | 35
| lvBusUv || ???
|-
! scope="row" | 36
| lvBusOv || ???
|-
! scope="row" | 37
| resonantTankOc || ???
|-
! scope="row" | 38
| claFaulted || ???
|-
! scope="row" | 39
| sdModuleClkFault || ???
|-
! scope="row" | 40
| dcdcMaxPowerReached || ???
|-
! scope="row" | 41
| dcdcOverTemp || ???
|-
! scope="row" | 42
| dcdcEnableLineMismatch || ???
|-
! scope="row" | 43
| hvBusPrechargeFailure || ???
|-
! scope="row" | 44
| 12vSupportRegulation || ???
|-
! scope="row" | 45
| hvBusLowImpedance || ???
|-
! scope="row" | 46
| hvBusHighImpedence || ???
|-
! scope="row" | 47
| lvBusLowImpedance || ???
|-
! scope="row" | 48
| lvBusHighImpedance || ???
|-
! scope="row" | 49
| dcdcTempRationality || ???
|-
! scope="row" | 50
| dcdc12VsupportFaulted || ???
|-
! scope="row" | 51
| chgIntBusUv || ???
|-
! scope="row" | 52
| acVoltageNotPresent || ???
|-
! scope="row" | 53
| chgInputVDropHigh || ???
|-
! scope="row" | 54
| chgInputVDropTooHigh || ???
|-
! scope="row" | 55
| chgLineImedanceHigh || ???
|-
! scope="row" | 56
| chgLineImedanceTooHigh || ???
|-
! scope="row" | 57
| chgInputOverFreq || ???
|-
! scope="row" | 58
| chgInputUnderFreq || ???
|-
! scope="row" | 59
| chgInputOvRms || ???
|-
! scope="row" | 60
| chgInputOvPeak || ???
|-
! scope="row" | 61
| chgVLineRationality || ???
|-
! scope="row" | 62
| chgILineRationality || ???
|-
! scope="row" | 63
| chgVOutRationality || ???
|-
! scope="row" | 64
| chgIOutRationality || ???
|-
! scope="row" | 65
| chgPllNotLocked || ???
|-
! scope="row" | 66
| dcdcHvRationality || The PCS is attempting to start up the DCDC converter, but there isn't any high voltage provided / Are the high voltage lines hooked up to the PCS correctly?
|-
! scope="row" | 67
| dcdcLvRationality || ???
|-
! scope="row" | 68
| dcdcTankvRationality || ???
|-
! scope="row" | 69
| chgPfcLineDidt || ???
|-
! scope="row" | 70
| chgPfcLineDvdt || ???
|-
! scope="row" | 71
| chgPfcILoopRationality || ???
|-
! scope="row" | 72
| cpu2ClaStopped || ???
|-
! scope="row" | 73
| unexpectedAcInputVoltage || ???
|-
! scope="row" | 74
| hvBusDischargeFailure || ???
|-
! scope="row" | 75
| hvBusDischargeTimeout || ???
|-
! scope="row" | 76
| dcdcEnDeassertedErr || "DCDC enable, de-asserted error", Artifact in the software caused by few milisecond delay between DCDC being commanded to shut down over CAN and the hardware line being disabled
|-
! scope="row" | 77
| microGridEnergyLow || ???
|-
! scope="row" | 78
| chgStopDcdcTooHot || ???
|-
! scope="row" | 79
| eepromOperationError || ???
|-
! scope="row" | 80
| damagedPhaseDetected || ???
|-
! scope="row" | 81
| dcdcPchgTimeout || ???
|-
! scope="row" | 82
| dcdcPchgUnsafeDiVoltage || ???
|-
! scope="row" | 83
| triggerOdin || ???
|-
! scope="row" | 84
| unused || ???
|-
! scope="row" | 85
| dcdcFetsNotSwitching || ???
|-
! scope="row" | 86
| dcdcInsufficientCooling || ???
|-
! scope="row" | 87
| nvramRecordStatusError || ???
|-
! scope="row" | 88
| pchgParameters || ???
|-
! scope="row" | 89
| hvBusDischargeIrrational || ???
|-
! scope="row" | 90
| expectedAcVoltageSourceMissing || ???
|-
! scope="row" | 91
| chgIntBusRationality || ???
|-
! scope="row" | 92
| chgPowerLimitedByBusRipple || ???
|-
! scope="row" | 93
| powerRailRationality || ???
|-
! scope="row" | 94
| pcsDcdcNeedService || ???
|-
! scope="row" | 95
| dcdcSensorlessModeActive || ???
|-
! scope="row" | 96
| microGridOverLoaded || ???
|-
! scope="row" | 97
| rebootPhaseDetected || ???
|-
! scope="row" | 98
| gridFreqDroopDetectedSilent || ???
|-
! scope="row" | 99
| microGridOverLoadedSilent || ???
|-
! scope="row" | 100
| microGridEnergyLowSilent || ???
|-
! scope="row" | 101
| phMachineModelIrrational || ???
|-
! scope="row" | 102
| resetWithDCDCCmdAsserted || ???
|-
|}

== Testing ==

=== First Power Up ===

Set up to initially test connections between a PCS and the PCS controller are straightforward. This can be done without any HV DC battery or charging connected to the PCS. Once the PCS controller is connected to the PCS (follow the relevant V2 or V3 pin-outs) the basic steps are:

# Connect the PCS aluminium case to LV ground
# Connect PCS controller ground wire to 12V ground
# Connect PCS 12V power wire via a 5A fuse to +12V
# Observe the PCS controller continuous 3.3V indicator red LED and the flashing activity red LED
# Connect to the PCS controller wifi (SSID will be, for example , ESP-DC87FA) to view the web interface (v3 has a default IP address of 192.168.4.1). The interface will indicate that the PCS 'opmode' is 'Off' at this time
# On the web interface, change 'inputype' to 'Manual' in the drop down menu and select refresh at the top of the screen
# On the web interface, change 'activate' to 'Both'. This will tell the PCS to try start DC-DC and Charging if enabled (as above, these are not connected at this time so will generate alerts that will be mentioned further below)
# On the web interface, change 'AlertLog' to 'On'. This will tell the PCS to show any alerts
# To enable the PCS connect the PCS controller 'Input 1 (enable)' wire to +12V and select refresh at the top of the screen. 'Opmode' should now change to 'Run' on the web interface to show the PCS is now operational
# At this point, 'PCSAlertCnt' will likely show a number indicating the number of alerts the PCS has flagged and 'PCSAlerts' will show the first alert
# To see each alert separately, under General, change the number in the 'Alert' option (0 indicates first alert and should be default) to the next sequential number and select refresh at the top of the screen. 'PCSAlerts' will now show a description of the selected alert. Do this to step through each alert (total number indicated by 'PCSAlertCnt')
# Typical alerts with this configuration (no HV DC battery or charger interface connected) will be: 63chgVOutRationality, 66dcdcHVRationality
# Now the connections and communication with the PCS and controller are established, further testing can be carried out to check DC-DC and charging functionality. See below 

=== DC-DC First Test ===
TBC

=== AC Charging Test ===
TBC

=== Confirmed Working Models ===
to date a number of PCS units have been tested and confirmed to work with the current firmware:

* 1x 3p EU PCS from circa 2020 model year car
* 1x 1p US PCS from circa 2018 model year car. Running in BMW E46 touring conversion
* 1x 1p US PCS from circa 2020 model year car

The minimum recommended HV DC battery voltage for testing is 250V (This needs to be confirmed)

== References ==
<references />
[[Category:OEM]] [[Category:Tesla]] [[Category:Charger]] [[Category:DC/DC]]

Tesla Model 3 Charger/DCDC ("PCS")

2024-10-01T16:22:08Z

Jokeitch: added possible location of identifying markers on the pcs case

== Overview ==
The Tesla Model 3 has a "Power Conversion System" (also known as the "PCS") which contains both a 10kW AC charger and a ??W DCDC converter. The PCS is located inside the "Penthouse" part of the main traction battery system.

== Learning/Resources ==
Video - The Tesla Project : Model 3 PCS First Look - https://youtu.be/_TYvSmDJSPQ

Video - Tesla Model 3 Power Conversion System - https://youtu.be/3ARHdRwfxjY

OpenInverter PCS overview/tech thread: https://openinverter.org/forum/viewtopic.php?f=10&t=171

OpenInverter PCS controller support thread: https://openinverter.org/forum/viewtopic.php?p=27744#p27744

Damien's GitHib: https://github.com/damienmaguire/Tesla-Model-3-Charger

== Troubleshooting/Seeking help ==
If you encounter issues with the PCS, it's generally good practice to collect the following information and [https://openinverter.org/forum/viewforum.php?f=10 create a thread on the forums] with a description as detailed as you can be about the problem

All of these instructions are also available in a [https://youtu.be/RYCl0ZL4cG4 youtube video demo by damien]

# model year of the car it came out of
# any serial numbers on the penthouse or pcs itself, from stickers or identifying markings
## Located on the top, above the high voltage connection plug, should be a rectangular white sticker with two numbers that begin with "DEV-" and "SDEVR-"
# firmware version on the pcs
## In the web interface, this is listed in the "version" row under the "spot values" header, for example "1.16.R"
##* ''edit, this may just be the firmware version of the PCS controller itself''
# a dump of parameters from the controller
## In the web interface, under the parameters section, there's a link to "download parameters file"
# A list of all alerts generated in the alert log
## First, enable the alert log system, by selecting "on" next to the row labeled "AertLog" under the "general" subsection under Parameters
## View the first saved alert by putting 0 into the Alerts row box and hitting enter, then hitting refresh on the top right, then scrolling down to the "PCSAlerts" row within the "spot values" section. This shows the first alert. To see other alerts, repeat by entering 1, 2, 3 etc into the Alerts row box and hitting enter+refresh again
## to see the total number of alerts you can scroll down to "PCSAlertCnt" in the "spot values" section, note that only 10 alerts can be stored at a time.

== Hardware ==

=== Controller ===
Damien from EVBMW has designed a control solution which is open source hardware and software. Design files for the controller hardware and software sources are available on Damien's GitHub [https://github.com/damienmaguire/Tesla-Model-3-Charger here]. Controllers are also available as a fully-built kit (with pre-loaded software) on the EVBWM webstore<ref>https://www.evbmw.com/index.php/evbmw-webshop/tesla-boards/tesla-model-3-pcs-con (Backup: [http://web.archive.org/web/20221016211810/https://www.evbmw.com/index.php/evbmw-webshop/tesla-boards/tesla-model-3-pcs-con Web Archive])</ref>.

=== Data Connector on PCS (12-way) ===
''EDITOR'S NOTE: my research shows some conflicting/different part numbers mentioned - would appreciate some clarification here once validated''

As per: https://openinverter.org/forum/viewtopic.php?p=26614#p26614<blockquote>''The connector used for communications with the PCS:'' <ref>https://www.te.com/global-en/product-1379662-5.html (Backup: [http://web.archive.org/web/20221016212020/https://www.te.com/global-en/product-1379662-5.html Web Archive])</ref><ref>https://www.mouser.ie/ProductDetail/TE-Connectivity-AMP/1379662-1?qs=yDt3hdeEHFPzMcXLhRNNtw%3D%3D (Backup: [http://web.archive.org/web/20221016212258/https://www.mouser.ie/ProductDetail/TE-Connectivity-AMP/1379662-1?qs=yDt3hdeEHFPzMcXLhRNNtw%3D%3D Web Archive])</ref>

''Pins:'' <ref>https://www.mouser.ie/ProductDetail/TE-Connectivity/1801069-2?qs=sGAEpiMZZMvlX3nhDDO4AIlVXMSSZRpGH8WODUA4Ad4%3D (Backup: [https://web.archive.org/web/20221016212418/https://www.mouser.ie/ProductDetail/TE-Connectivity/1801069-2?qs=sGAEpiMZZMvlX3nhDDO4AIlVXMSSZRpGH8WODUA4Ad4%3D Web Archive])</ref>

''In true Muskian fashion it seems they use the 1379662-5 natural color variant of the plug which has no coding tabs. It is of course unavailable from mouser. The black and green variants are functionally identical and should work with coding tabs removed.''</blockquote>
[[File:PXL 20231125 230415175~2.jpg|thumb|annotated view of PCS data connector viewed from the front]]
However, as per: https://github.com/muehlpower/EV-FFB, there is also mention of 1318774-1 (white) or 1318774-2 (black) for the comms/data connector.
[[File:V3 PCS controller pinout diagram.jpg|thumb]]

=== Power Connectors ===
The power-side connector assemblies are not widely available. The housings are a Tesla internal part (photos/part numbers [https://openinverter.org/forum/viewtopic.php?p=27744#p27744 here]), however, 3D printable housings have been made available [https://github.com/muehlpower/EV-FFB here]. The terminals also aren't widely available, but are known. As per https://github.com/muehlpower/EV-FFB:

Note: the US variant of the charger (1-phase) has a different AC pin layout; see photo for reference.<blockquote>''The contacts for 400V are Uni F630 from MTA, part number 1107940. For 12V Kostal PLK 14.5, part number 23124734300. The connector for the data is from TE connectivity, part number 1318774-1 for white or 1318774-2 for black.''</blockquote>
[[File:Model 3 US charger variant AC connector.png|thumb|AC connector pinout for US Model 3 PCS (1-phase)]]

=== Connections ===
[[File:Tesla PCS Connection diagram 8162022.png|thumb]]
The minimum wiring needed to wake the PCS:

# PCS controller connected to PCS via 12-way X420
# PCS controller is powered via 20-way +12V input pin and grounded to chassis via 20-way ground pin
# +12v and Chassis ground applied to PCS 12v Connector input terminal
# Chassis ground on the PCS case

== Firmware ==

=== Current Version ===
The current version of the PCS firmware can be found here: https://github.com/damienmaguire/Tesla-Model-3-Charger/releases

The current firmware will auto detect what Tesla firmware is installed on the PCS and adjusts the CAN messages accordingly (different versions of the PCS firmware from Tesla have different CAN requirements). It will also auto detect if the PCS is EU or US spec and whether single or three phase AC is connected. It also includes an integrated alert logging function to help diagnose any issues the PCS sees.

=== Alerts Logging ===
The PCS has an array of potential alerts to help diagnose issues. The images below show a matrix of potential alerts
[[File:PCS Alert Table001.jpg|thumb]]
[[File:PCS Alert Table002.jpg|thumb]]

Initially alerts had to be identified through CAN logs (PCS IPC CAN). In later firmware releases, the PCS web interface incorporated a decoder to help identify alerts (decimal number identifier relating to the alert tables shown here). In the current version of firmware, the alerts are now displayed in word format to make it easier and quicker to troubleshoot.

'''''Below is a list of all alert codes the PCS can generate, with associated error code number, and plain text descriptions of what each one means'''''

{| class="wikitable mw-collapsible mw-collapsed"
|+ class="no wrap" | Alert Codes
|-
|
! scope="col" | Error code / name
! scope="col" | Error description
|-
! scope="row" | 01
| chgHwInputOc || ???
|-
! scope="row" | 02
| chgHwOutputOc|| ???
|-
! scope="row" | 03
| chgHwInputOv|| ???
|-
! scope="row" | 04
| chgHwIntBusOv|| ???
|-
! scope="row" | 05
| chgOutputOv|| ???
|-
! scope="row" | 06
| chgPrechargeFailedScr|| ???
|-
! scope="row" | 07
| chgPhaseTempHot|| ???
|-
! scope="row" | 08
| chgPhaseOverTemp|| ???
|-
! scope="row" | 09
| chgPfcCurrentRegulation|| ???
|-
! scope="row" | 10
| chgIntBusVRegulation || ???
|-
! scope="row" | 11
| chgLlcCurrentRegulation || ???
|-
! scope="row" | 12
| chgPfcIBandTracerFault || ???
|-
! scope="row" | 13
| chgPrechargeFailedBoost || ???
|-
! scope="row" | 14
| chgTempRationality || ???
|-
! scope="row" | 15
| chg12vUv || ???
|-
! scope="row" | 16
| chgAllPhasesFaulted || ???
|-
! scope="row" | 17
| chgWallPowerRemoval || ???
|-
! scope="row" | 18
| chgUnknownGridConfig || ???
|-
! scope="row" | 19
| acChargePowerLimited || ???
|-
! scope="row" | 20
| chgEnableLineMismatch || "Charge Enable Line Mismatch", Charger was commanded to start over CAN, but the enable line hasn't been correctly brought up
|-
! scope="row" | 21
| hvpMia || ???
|-
! scope="row" | 22
| bmsMia || ???
|-
! scope="row" | 23
| cpMia || ???
|-
! scope="row" | 24
| vcfrontMia || ???
|-
! scope="row" | 25
| cpu2Malfunction || ???
|-
! scope="row" | 26
| watchdogAlarmed || ???
|-
! scope="row" | 27
| chgInsufficientCooling || ???
|-
! scope="row" | 28
| chgOutputUv || The charger was commanded to start, but the AC high voltage is less than what is required to actually charge
|-
! scope="row" | 29
| chgPowerRationality || ???
|-
! scope="row" | 30
| canRationality || ???
|-
! scope="row" | 31
| uiMia || ???
|-
! scope="row" | 32
| unused || ???
|-
! scope="row" | 33
| hvBusUv || ???
|-
! scope="row" | 34
| hvBusOv || ???
|-
! scope="row" | 35
| lvBusUv || ???
|-
! scope="row" | 36
| lvBusOv || ???
|-
! scope="row" | 37
| resonantTankOc || ???
|-
! scope="row" | 38
| claFaulted || ???
|-
! scope="row" | 39
| sdModuleClkFault || ???
|-
! scope="row" | 40
| dcdcMaxPowerReached || ???
|-
! scope="row" | 41
| dcdcOverTemp || ???
|-
! scope="row" | 42
| dcdcEnableLineMismatch || ???
|-
! scope="row" | 43
| hvBusPrechargeFailure || ???
|-
! scope="row" | 44
| 12vSupportRegulation || ???
|-
! scope="row" | 45
| hvBusLowImpedance || ???
|-
! scope="row" | 46
| hvBusHighImpedence || ???
|-
! scope="row" | 47
| lvBusLowImpedance || ???
|-
! scope="row" | 48
| lvBusHighImpedance || ???
|-
! scope="row" | 49
| dcdcTempRationality || ???
|-
! scope="row" | 50
| dcdc12VsupportFaulted || ???
|-
! scope="row" | 51
| chgIntBusUv || ???
|-
! scope="row" | 52
| acVoltageNotPresent || ???
|-
! scope="row" | 53
| chgInputVDropHigh || ???
|-
! scope="row" | 54
| chgInputVDropTooHigh || ???
|-
! scope="row" | 55
| chgLineImedanceHigh || ???
|-
! scope="row" | 56
| chgLineImedanceTooHigh || ???
|-
! scope="row" | 57
| chgInputOverFreq || ???
|-
! scope="row" | 58
| chgInputUnderFreq || ???
|-
! scope="row" | 59
| chgInputOvRms || ???
|-
! scope="row" | 60
| chgInputOvPeak || ???
|-
! scope="row" | 61
| chgVLineRationality || ???
|-
! scope="row" | 62
| chgILineRationality || ???
|-
! scope="row" | 63
| chgVOutRationality || ???
|-
! scope="row" | 64
| chgIOutRationality || ???
|-
! scope="row" | 65
| chgPllNotLocked || ???
|-
! scope="row" | 66
| dcdcHvRationality || The PCS is attempting to start up the DCDC converter, but there isn't any high voltage provided / Are the high voltage lines hooked up to the PCS correctly?
|-
! scope="row" | 67
| dcdcLvRationality || ???
|-
! scope="row" | 68
| dcdcTankvRationality || ???
|-
! scope="row" | 69
| chgPfcLineDidt || ???
|-
! scope="row" | 70
| chgPfcLineDvdt || ???
|-
! scope="row" | 71
| chgPfcILoopRationality || ???
|-
! scope="row" | 72
| cpu2ClaStopped || ???
|-
! scope="row" | 73
| unexpectedAcInputVoltage || ???
|-
! scope="row" | 74
| hvBusDischargeFailure || ???
|-
! scope="row" | 75
| hvBusDischargeTimeout || ???
|-
! scope="row" | 76
| dcdcEnDeassertedErr || "DCDC enable, de-asserted error", Artifact in the software caused by few milisecond delay between DCDC being commanded to shut down over CAN and the hardware line being disabled
|-
! scope="row" | 77
| microGridEnergyLow || ???
|-
! scope="row" | 78
| chgStopDcdcTooHot || ???
|-
! scope="row" | 79
| eepromOperationError || ???
|-
! scope="row" | 80
| damagedPhaseDetected || ???
|-
! scope="row" | 81
| dcdcPchgTimeout || ???
|-
! scope="row" | 82
| dcdcPchgUnsafeDiVoltage || ???
|-
! scope="row" | 83
| triggerOdin || ???
|-
! scope="row" | 84
| unused || ???
|-
! scope="row" | 85
| dcdcFetsNotSwitching || ???
|-
! scope="row" | 86
| dcdcInsufficientCooling || ???
|-
! scope="row" | 87
| nvramRecordStatusError || ???
|-
! scope="row" | 88
| pchgParameters || ???
|-
! scope="row" | 89
| hvBusDischargeIrrational || ???
|-
! scope="row" | 90
| expectedAcVoltageSourceMissing || ???
|-
! scope="row" | 91
| chgIntBusRationality || ???
|-
! scope="row" | 92
| chgPowerLimitedByBusRipple || ???
|-
! scope="row" | 93
| powerRailRationality || ???
|-
! scope="row" | 94
| pcsDcdcNeedService || ???
|-
! scope="row" | 95
| dcdcSensorlessModeActive || ???
|-
! scope="row" | 96
| microGridOverLoaded || ???
|-
! scope="row" | 97
| rebootPhaseDetected || ???
|-
! scope="row" | 98
| gridFreqDroopDetectedSilent || ???
|-
! scope="row" | 99
| microGridOverLoadedSilent || ???
|-
! scope="row" | 100
| microGridEnergyLowSilent || ???
|-
! scope="row" | 101
| phMachineModelIrrational || ???
|-
! scope="row" | 102
| resetWithDCDCCmdAsserted || ???
|-
|}

== Testing ==

=== First Power Up ===

Set up to initially test connections between a PCS and the PCS controller are straightforward. This can be done without any HV DC battery or charging connected to the PCS. Once the PCS controller is connected to the PCS (follow the relevant V2 or V3 pin-outs) the basic steps are:

# Connect the PCS aluminium case to LV ground
# Connect PCS controller ground wire to 12V ground
# Connect PCS 12V power wire via a 5A fuse to +12V
# Observe the PCS controller continuous 3.3V indicator red LED and the flashing activity red LED
# Connect to the PCS controller wifi (SSID will be, for example , ESP-DC87FA) to view the web interface (v3 has a default IP address of 192.168.4.1). The interface will indicate that the PCS 'opmode' is 'Off' at this time
# On the web interface, change 'inputype' to 'Manual' in the drop down menu and select refresh at the top of the screen
# On the web interface, change 'activate' to 'Both'. This will tell the PCS to try start DC-DC and Charging if enabled (as above, these are not connected at this time so will generate alerts that will be mentioned further below)
# On the web interface, change 'AlertLog' to 'On'. This will tell the PCS to show any alerts
# To enable the PCS connect the PCS controller 'Input 1 (enable)' wire to +12V and select refresh at the top of the screen. 'Opmode' should now change to 'Run' on the web interface to show the PCS is now operational
# At this point, 'PCSAlertCnt' will likely show a number indicating the number of alerts the PCS has flagged and 'PCSAlerts' will show the first alert
# To see each alert separately, under General, change the number in the 'Alert' option (0 indicates first alert and should be default) to the next sequential number and select refresh at the top of the screen. 'PCSAlerts' will now show a description of the selected alert. Do this to step through each alert (total number indicated by 'PCSAlertCnt')
# Typical alerts with this configuration (no HV DC battery or charger interface connected) will be: 63chgVOutRationality, 66dcdcHVRationality
# Now the connections and communication with the PCS and controller are established, further testing can be carried out to check DC-DC and charging functionality. See below 

=== DC-DC First Test ===
TBC

=== AC Charging Test ===
TBC

=== Confirmed Working Models ===
to date a number of PCS units have been tested and confirmed to work with the current firmware:
1x 3p EU PCS from circa 2020 model year car
1x 1p US PCS from circa 2018 model year car. Running in BMW E46 touring conversion
1x 1p US PCS from circa 2020 model year car

The minimum recommended HV DC battery voltage for testing is 250V (This needs to be confirmed)

== References ==
<references />
[[Category:OEM]] [[Category:Tesla]] [[Category:Charger]] [[Category:DC/DC]]

Tesla Model 3 Charger/DCDC ("PCS")

2024-09-30T20:01:29Z

Jokeitch: adding youtube link to troubleshooting section

== Overview ==
The Tesla Model 3 has a "Power Conversion System" (also known as the "PCS") which contains both a 10kW AC charger and a ??W DCDC converter. The PCS is located inside the "Penthouse" part of the main traction battery system.

== Learning/Resources ==
Video - The Tesla Project : Model 3 PCS First Look - https://youtu.be/_TYvSmDJSPQ

Video - Tesla Model 3 Power Conversion System - https://youtu.be/3ARHdRwfxjY

OpenInverter PCS overview/tech thread: https://openinverter.org/forum/viewtopic.php?f=10&t=171

OpenInverter PCS controller support thread: https://openinverter.org/forum/viewtopic.php?p=27744#p27744

Damien's GitHib: https://github.com/damienmaguire/Tesla-Model-3-Charger

== Troubleshooting/Seeking help ==
If you encounter issues with the PCS, it's generally good practice to collect the following information and [https://openinverter.org/forum/viewforum.php?f=10 create a thread on the forums] with a description as detailed as you can be about the problem

All of these instructions are also available in a [https://youtu.be/RYCl0ZL4cG4 youtube video demo by damien]

# model year of the car it came out of
# any serial numbers on the penthouse or pcs itself, from stickers or identifying markings
## (TBC, locate relevant stickers on pcs and penthouse casing)
# firmware version on the pcs
## In the web interface, this is listed in the "version" row under the "spot values" header, for example "1.16.R"
# a dump of parameters from the controller
## In the web interface, under the parameters section, there's a link to "download parameters file"
# A list of all alerts generated in the alert log
## First, enable the alert log system, by selecting "on" next to the row labeled "AertLog" under the "general" subsection under Parameters
## View the first saved alert by putting 0 into the Alerts row box and hitting enter, then hitting refresh on the top right, then scrolling down to the "PCSAlerts" row within the "spot values" section. This shows the first alert. To see other alerts, repeat by entering 1, 2, 3 etc into the Alerts row box and hitting enter+refresh again
## to see the total number of alerts you can scroll down to "PCSAlertCnt" in the "spot values" section, note that only 10 alerts can be stored at a time.

== Hardware ==

=== Controller ===
Damien from EVBMW has designed a control solution which is open source hardware and software. Design files for the controller hardware and software sources are available on Damien's GitHub [https://github.com/damienmaguire/Tesla-Model-3-Charger here]. Controllers are also available as a fully-built kit (with pre-loaded software) on the EVBWM webstore<ref>https://www.evbmw.com/index.php/evbmw-webshop/tesla-boards/tesla-model-3-pcs-con (Backup: [http://web.archive.org/web/20221016211810/https://www.evbmw.com/index.php/evbmw-webshop/tesla-boards/tesla-model-3-pcs-con Web Archive])</ref>.

=== Data Connector on PCS (12-way) ===
''EDITOR'S NOTE: my research shows some conflicting/different part numbers mentioned - would appreciate some clarification here once validated''

As per: https://openinverter.org/forum/viewtopic.php?p=26614#p26614<blockquote>''The connector used for communications with the PCS:'' <ref>https://www.te.com/global-en/product-1379662-5.html (Backup: [http://web.archive.org/web/20221016212020/https://www.te.com/global-en/product-1379662-5.html Web Archive])</ref><ref>https://www.mouser.ie/ProductDetail/TE-Connectivity-AMP/1379662-1?qs=yDt3hdeEHFPzMcXLhRNNtw%3D%3D (Backup: [http://web.archive.org/web/20221016212258/https://www.mouser.ie/ProductDetail/TE-Connectivity-AMP/1379662-1?qs=yDt3hdeEHFPzMcXLhRNNtw%3D%3D Web Archive])</ref>

''Pins:'' <ref>https://www.mouser.ie/ProductDetail/TE-Connectivity/1801069-2?qs=sGAEpiMZZMvlX3nhDDO4AIlVXMSSZRpGH8WODUA4Ad4%3D (Backup: [https://web.archive.org/web/20221016212418/https://www.mouser.ie/ProductDetail/TE-Connectivity/1801069-2?qs=sGAEpiMZZMvlX3nhDDO4AIlVXMSSZRpGH8WODUA4Ad4%3D Web Archive])</ref>

''In true Muskian fashion it seems they use the 1379662-5 natural color variant of the plug which has no coding tabs. It is of course unavailable from mouser. The black and green variants are functionally identical and should work with coding tabs removed.''</blockquote>
[[File:PXL 20231125 230415175~2.jpg|thumb|annotated view of PCS data connector viewed from the front]]
However, as per: https://github.com/muehlpower/EV-FFB, there is also mention of 1318774-1 (white) or 1318774-2 (black) for the comms/data connector.
[[File:V3 PCS controller pinout diagram.jpg|thumb]]

=== Power Connectors ===
The power-side connector assemblies are not widely available. The housings are a Tesla internal part (photos/part numbers [https://openinverter.org/forum/viewtopic.php?p=27744#p27744 here]), however, 3D printable housings have been made available [https://github.com/muehlpower/EV-FFB here]. The terminals also aren't widely available, but are known. As per https://github.com/muehlpower/EV-FFB:

Note: the US variant of the charger (1-phase) has a different AC pin layout; see photo for reference.<blockquote>''The contacts for 400V are Uni F630 from MTA, part number 1107940. For 12V Kostal PLK 14.5, part number 23124734300. The connector for the data is from TE connectivity, part number 1318774-1 for white or 1318774-2 for black.''</blockquote>
[[File:Model 3 US charger variant AC connector.png|thumb|AC connector pinout for US Model 3 PCS (1-phase)]]

=== Connections ===
[[File:Tesla PCS Connection diagram 8162022.png|thumb]]
The minimum wiring needed to wake the PCS:

# PCS controller connected to PCS via 12-way X420
# PCS controller is powered via 20-way +12V input pin and grounded to chassis via 20-way ground pin
# +12v and Chassis ground applied to PCS 12v Connector input terminal
# Chassis ground on the PCS case

== Firmware ==

=== Current Version ===
The current version of the PCS firmware can be found here: https://github.com/damienmaguire/Tesla-Model-3-Charger/releases

The current firmware will auto detect what Tesla firmware is installed on the PCS and adjusts the CAN messages accordingly (different versions of the PCS firmware from Tesla have different CAN requirements). It will also auto detect if the PCS is EU or US spec and whether single or three phase AC is connected. It also includes an integrated alert logging function to help diagnose any issues the PCS sees.

=== Alerts Logging ===
The PCS has an array of potential alerts to help diagnose issues. The images below show a matrix of potential alerts
[[File:PCS Alert Table001.jpg|thumb]]
[[File:PCS Alert Table002.jpg|thumb]]

Initially alerts had to be identified through CAN logs (PCS IPC CAN). In later firmware releases, the PCS web interface incorporated a decoder to help identify alerts (decimal number identifier relating to the alert tables shown here). In the current version of firmware, the alerts are now displayed in word format to make it easier and quicker to troubleshoot.

'''''Below is a list of all alert codes the PCS can generate, with associated error code number, and plain text descriptions of what each one means'''''

{| class="wikitable mw-collapsible mw-collapsed"
|+ class="no wrap" | Alert Codes
|-
|
! scope="col" | Error code / name
! scope="col" | Error description
|-
! scope="row" | 01
| chgHwInputOc || ???
|-
! scope="row" | 02
| chgHwOutputOc|| ???
|-
! scope="row" | 03
| chgHwInputOv|| ???
|-
! scope="row" | 04
| chgHwIntBusOv|| ???
|-
! scope="row" | 05
| chgOutputOv|| ???
|-
! scope="row" | 06
| chgPrechargeFailedScr|| ???
|-
! scope="row" | 07
| chgPhaseTempHot|| ???
|-
! scope="row" | 08
| chgPhaseOverTemp|| ???
|-
! scope="row" | 09
| chgPfcCurrentRegulation|| ???
|-
! scope="row" | 10
| chgIntBusVRegulation || ???
|-
! scope="row" | 11
| chgLlcCurrentRegulation || ???
|-
! scope="row" | 12
| chgPfcIBandTracerFault || ???
|-
! scope="row" | 13
| chgPrechargeFailedBoost || ???
|-
! scope="row" | 14
| chgTempRationality || ???
|-
! scope="row" | 15
| chg12vUv || ???
|-
! scope="row" | 16
| chgAllPhasesFaulted || ???
|-
! scope="row" | 17
| chgWallPowerRemoval || ???
|-
! scope="row" | 18
| chgUnknownGridConfig || ???
|-
! scope="row" | 19
| acChargePowerLimited || ???
|-
! scope="row" | 20
| chgEnableLineMismatch || "Charge Enable Line Mismatch", Charger was commanded to start over CAN, but the enable line hasn't been correctly brought up
|-
! scope="row" | 21
| hvpMia || ???
|-
! scope="row" | 22
| bmsMia || ???
|-
! scope="row" | 23
| cpMia || ???
|-
! scope="row" | 24
| vcfrontMia || ???
|-
! scope="row" | 25
| cpu2Malfunction || ???
|-
! scope="row" | 26
| watchdogAlarmed || ???
|-
! scope="row" | 27
| chgInsufficientCooling || ???
|-
! scope="row" | 28
| chgOutputUv || The charger was commanded to start, but the AC high voltage is less than what is required to actually charge
|-
! scope="row" | 29
| chgPowerRationality || ???
|-
! scope="row" | 30
| canRationality || ???
|-
! scope="row" | 31
| uiMia || ???
|-
! scope="row" | 32
| unused || ???
|-
! scope="row" | 33
| hvBusUv || ???
|-
! scope="row" | 34
| hvBusOv || ???
|-
! scope="row" | 35
| lvBusUv || ???
|-
! scope="row" | 36
| lvBusOv || ???
|-
! scope="row" | 37
| resonantTankOc || ???
|-
! scope="row" | 38
| claFaulted || ???
|-
! scope="row" | 39
| sdModuleClkFault || ???
|-
! scope="row" | 40
| dcdcMaxPowerReached || ???
|-
! scope="row" | 41
| dcdcOverTemp || ???
|-
! scope="row" | 42
| dcdcEnableLineMismatch || ???
|-
! scope="row" | 43
| hvBusPrechargeFailure || ???
|-
! scope="row" | 44
| 12vSupportRegulation || ???
|-
! scope="row" | 45
| hvBusLowImpedance || ???
|-
! scope="row" | 46
| hvBusHighImpedence || ???
|-
! scope="row" | 47
| lvBusLowImpedance || ???
|-
! scope="row" | 48
| lvBusHighImpedance || ???
|-
! scope="row" | 49
| dcdcTempRationality || ???
|-
! scope="row" | 50
| dcdc12VsupportFaulted || ???
|-
! scope="row" | 51
| chgIntBusUv || ???
|-
! scope="row" | 52
| acVoltageNotPresent || ???
|-
! scope="row" | 53
| chgInputVDropHigh || ???
|-
! scope="row" | 54
| chgInputVDropTooHigh || ???
|-
! scope="row" | 55
| chgLineImedanceHigh || ???
|-
! scope="row" | 56
| chgLineImedanceTooHigh || ???
|-
! scope="row" | 57
| chgInputOverFreq || ???
|-
! scope="row" | 58
| chgInputUnderFreq || ???
|-
! scope="row" | 59
| chgInputOvRms || ???
|-
! scope="row" | 60
| chgInputOvPeak || ???
|-
! scope="row" | 61
| chgVLineRationality || ???
|-
! scope="row" | 62
| chgILineRationality || ???
|-
! scope="row" | 63
| chgVOutRationality || ???
|-
! scope="row" | 64
| chgIOutRationality || ???
|-
! scope="row" | 65
| chgPllNotLocked || ???
|-
! scope="row" | 66
| dcdcHvRationality || The PCS is attempting to start up the DCDC converter, but there isn't any high voltage provided / Are the high voltage lines hooked up to the PCS correctly?
|-
! scope="row" | 67
| dcdcLvRationality || ???
|-
! scope="row" | 68
| dcdcTankvRationality || ???
|-
! scope="row" | 69
| chgPfcLineDidt || ???
|-
! scope="row" | 70
| chgPfcLineDvdt || ???
|-
! scope="row" | 71
| chgPfcILoopRationality || ???
|-
! scope="row" | 72
| cpu2ClaStopped || ???
|-
! scope="row" | 73
| unexpectedAcInputVoltage || ???
|-
! scope="row" | 74
| hvBusDischargeFailure || ???
|-
! scope="row" | 75
| hvBusDischargeTimeout || ???
|-
! scope="row" | 76
| dcdcEnDeassertedErr || "DCDC enable, de-asserted error", Artifact in the software caused by few milisecond delay between DCDC being commanded to shut down over CAN and the hardware line being disabled
|-
! scope="row" | 77
| microGridEnergyLow || ???
|-
! scope="row" | 78
| chgStopDcdcTooHot || ???
|-
! scope="row" | 79
| eepromOperationError || ???
|-
! scope="row" | 80
| damagedPhaseDetected || ???
|-
! scope="row" | 81
| dcdcPchgTimeout || ???
|-
! scope="row" | 82
| dcdcPchgUnsafeDiVoltage || ???
|-
! scope="row" | 83
| triggerOdin || ???
|-
! scope="row" | 84
| unused || ???
|-
! scope="row" | 85
| dcdcFetsNotSwitching || ???
|-
! scope="row" | 86
| dcdcInsufficientCooling || ???
|-
! scope="row" | 87
| nvramRecordStatusError || ???
|-
! scope="row" | 88
| pchgParameters || ???
|-
! scope="row" | 89
| hvBusDischargeIrrational || ???
|-
! scope="row" | 90
| expectedAcVoltageSourceMissing || ???
|-
! scope="row" | 91
| chgIntBusRationality || ???
|-
! scope="row" | 92
| chgPowerLimitedByBusRipple || ???
|-
! scope="row" | 93
| powerRailRationality || ???
|-
! scope="row" | 94
| pcsDcdcNeedService || ???
|-
! scope="row" | 95
| dcdcSensorlessModeActive || ???
|-
! scope="row" | 96
| microGridOverLoaded || ???
|-
! scope="row" | 97
| rebootPhaseDetected || ???
|-
! scope="row" | 98
| gridFreqDroopDetectedSilent || ???
|-
! scope="row" | 99
| microGridOverLoadedSilent || ???
|-
! scope="row" | 100
| microGridEnergyLowSilent || ???
|-
! scope="row" | 101
| phMachineModelIrrational || ???
|-
! scope="row" | 102
| resetWithDCDCCmdAsserted || ???
|-
|}

== Testing ==

=== First Power Up ===

Set up to initially test connections between a PCS and the PCS controller are straightforward. This can be done without any HV DC battery or charging connected to the PCS. Once the PCS controller is connected to the PCS (follow the relevant V2 or V3 pin-outs) the basic steps are:

# Connect the PCS aluminium case to LV ground
# Connect PCS controller ground wire to 12V ground
# Connect PCS 12V power wire via a 5A fuse to +12V
# Observe the PCS controller continuous 3.3V indicator red LED and the flashing activity red LED
# Connect to the PCS controller wifi (SSID will be, for example , ESP-DC87FA) to view the web interface (v3 has a default IP address of 192.168.4.1). The interface will indicate that the PCS 'opmode' is 'Off' at this time
# On the web interface, change 'inputype' to 'Manual' in the drop down menu and select refresh at the top of the screen
# On the web interface, change 'activate' to 'Both'. This will tell the PCS to try start DC-DC and Charging if enabled (as above, these are not connected at this time so will generate alerts that will be mentioned further below)
# On the web interface, change 'AlertLog' to 'On'. This will tell the PCS to show any alerts
# To enable the PCS connect the PCS controller 'Input 1 (enable)' wire to +12V and select refresh at the top of the screen. 'Opmode' should now change to 'Run' on the web interface to show the PCS is now operational
# At this point, 'PCSAlertCnt' will likely show a number indicating the number of alerts the PCS has flagged and 'PCSAlerts' will show the first alert
# To see each alert separately, under General, change the number in the 'Alert' option (0 indicates first alert and should be default) to the next sequential number and select refresh at the top of the screen. 'PCSAlerts' will now show a description of the selected alert. Do this to step through each alert (total number indicated by 'PCSAlertCnt')
# Typical alerts with this configuration (no HV DC battery or charger interface connected) will be: 63chgVOutRationality, 66dcdcHVRationality
# Now the connections and communication with the PCS and controller are established, further testing can be carried out to check DC-DC and charging functionality. See below 

=== DC-DC First Test ===
TBC

=== AC Charging Test ===
TBC

=== Confirmed Working Models ===
to date a number of PCS units have been tested and confirmed to work with the current firmware:
1x 3p EU PCS from circa 2020 model year car
1x 1p US PCS from circa 2018 model year car. Running in BMW E46 touring conversion
1x 1p US PCS from circa 2020 model year car

The minimum recommended HV DC battery voltage for testing is 250V (This needs to be confirmed)

== References ==
<references />
[[Category:OEM]] [[Category:Tesla]] [[Category:Charger]] [[Category:DC/DC]]

Tesla Model 3 Charger/DCDC ("PCS")

2024-09-30T07:35:34Z

Jokeitch: /* Troubleshooting/Seeking help */

== Overview ==
The Tesla Model 3 has a "Power Conversion System" (also known as the "PCS") which contains both a 10kW AC charger and a ??W DCDC converter. The PCS is located inside the "Penthouse" part of the main traction battery system.

== Learning/Resources ==
Video - The Tesla Project : Model 3 PCS First Look - https://youtu.be/_TYvSmDJSPQ

Video - Tesla Model 3 Power Conversion System - https://youtu.be/3ARHdRwfxjY

OpenInverter PCS overview/tech thread: https://openinverter.org/forum/viewtopic.php?f=10&t=171

OpenInverter PCS controller support thread: https://openinverter.org/forum/viewtopic.php?p=27744#p27744

Damien's GitHib: https://github.com/damienmaguire/Tesla-Model-3-Charger

== Troubleshooting/Seeking help ==
If you encounter issues with the PCS, it's generally good practice to collect the following information and [https://openinverter.org/forum/viewforum.php?f=10 create a thread on the forums] with a description as detailed as you can be about the problem

# model year of the car it came out of
# any serial numbers on the penthouse or pcs itself, from stickers or identifying markings
## (TBC, locate relevant stickers on pcs and penthouse casing)
# firmware version on the pcs
## In the web interface, this is listed in the "version" row under the "spot values" header, for example "1.16.R"
# a dump of parameters from the controller
## In the web interface, under the parameters section, there's a link to "download parameters file"
# A list of all alerts generated in the alert log
## First, enable the alert log system, by selecting "on" next to the row labeled "AertLog" under the "general" subsection under Parameters
## View the first saved alert by putting 0 into the Alerts row box and hitting enter, then hitting refresh on the top right, then scrolling down to the "PCSAlerts" row within the "spot values" section. This shows the first alert. To see other alerts, repeat by entering 1, 2, 3 etc into the Alerts row box and hitting enter+refresh again
## to see the total number of alerts you can scroll down to "PCSAlertCnt" in the "spot values" section, note that only 10 alerts can be stored at a time.

== Hardware ==

=== Controller ===
Damien from EVBMW has designed a control solution which is open source hardware and software. Design files for the controller hardware and software sources are available on Damien's GitHub [https://github.com/damienmaguire/Tesla-Model-3-Charger here]. Controllers are also available as a fully-built kit (with pre-loaded software) on the EVBWM webstore<ref>https://www.evbmw.com/index.php/evbmw-webshop/tesla-boards/tesla-model-3-pcs-con (Backup: [http://web.archive.org/web/20221016211810/https://www.evbmw.com/index.php/evbmw-webshop/tesla-boards/tesla-model-3-pcs-con Web Archive])</ref>.

=== Data Connector on PCS (12-way) ===
''EDITOR'S NOTE: my research shows some conflicting/different part numbers mentioned - would appreciate some clarification here once validated''

As per: https://openinverter.org/forum/viewtopic.php?p=26614#p26614<blockquote>''The connector used for communications with the PCS:'' <ref>https://www.te.com/global-en/product-1379662-5.html (Backup: [http://web.archive.org/web/20221016212020/https://www.te.com/global-en/product-1379662-5.html Web Archive])</ref><ref>https://www.mouser.ie/ProductDetail/TE-Connectivity-AMP/1379662-1?qs=yDt3hdeEHFPzMcXLhRNNtw%3D%3D (Backup: [http://web.archive.org/web/20221016212258/https://www.mouser.ie/ProductDetail/TE-Connectivity-AMP/1379662-1?qs=yDt3hdeEHFPzMcXLhRNNtw%3D%3D Web Archive])</ref>

''Pins:'' <ref>https://www.mouser.ie/ProductDetail/TE-Connectivity/1801069-2?qs=sGAEpiMZZMvlX3nhDDO4AIlVXMSSZRpGH8WODUA4Ad4%3D (Backup: [https://web.archive.org/web/20221016212418/https://www.mouser.ie/ProductDetail/TE-Connectivity/1801069-2?qs=sGAEpiMZZMvlX3nhDDO4AIlVXMSSZRpGH8WODUA4Ad4%3D Web Archive])</ref>

''In true Muskian fashion it seems they use the 1379662-5 natural color variant of the plug which has no coding tabs. It is of course unavailable from mouser. The black and green variants are functionally identical and should work with coding tabs removed.''</blockquote>
[[File:PXL 20231125 230415175~2.jpg|thumb|annotated view of PCS data connector viewed from the front]]
However, as per: https://github.com/muehlpower/EV-FFB, there is also mention of 1318774-1 (white) or 1318774-2 (black) for the comms/data connector.
[[File:V3 PCS controller pinout diagram.jpg|thumb]]

=== Power Connectors ===
The power-side connector assemblies are not widely available. The housings are a Tesla internal part (photos/part numbers [https://openinverter.org/forum/viewtopic.php?p=27744#p27744 here]), however, 3D printable housings have been made available [https://github.com/muehlpower/EV-FFB here]. The terminals also aren't widely available, but are known. As per https://github.com/muehlpower/EV-FFB:

Note: the US variant of the charger (1-phase) has a different AC pin layout; see photo for reference.<blockquote>''The contacts for 400V are Uni F630 from MTA, part number 1107940. For 12V Kostal PLK 14.5, part number 23124734300. The connector for the data is from TE connectivity, part number 1318774-1 for white or 1318774-2 for black.''</blockquote>
[[File:Model 3 US charger variant AC connector.png|thumb|AC connector pinout for US Model 3 PCS (1-phase)]]

=== Connections ===
[[File:Tesla PCS Connection diagram 8162022.png|thumb]]
The minimum wiring needed to wake the PCS:

# PCS controller connected to PCS via 12-way X420
# PCS controller is powered via 20-way +12V input pin and grounded to chassis via 20-way ground pin
# +12v and Chassis ground applied to PCS 12v Connector input terminal
# Chassis ground on the PCS case

== Firmware ==

=== Current Version ===
The current version of the PCS firmware can be found here: https://github.com/damienmaguire/Tesla-Model-3-Charger/releases

The current firmware will auto detect what Tesla firmware is installed on the PCS and adjusts the CAN messages accordingly (different versions of the PCS firmware from Tesla have different CAN requirements). It will also auto detect if the PCS is EU or US spec and whether single or three phase AC is connected. It also includes an integrated alert logging function to help diagnose any issues the PCS sees.

=== Alerts Logging ===
The PCS has an array of potential alerts to help diagnose issues. The images below show a matrix of potential alerts
[[File:PCS Alert Table001.jpg|thumb]]
[[File:PCS Alert Table002.jpg|thumb]]

Initially alerts had to be identified through CAN logs (PCS IPC CAN). In later firmware releases, the PCS web interface incorporated a decoder to help identify alerts (decimal number identifier relating to the alert tables shown here). In the current version of firmware, the alerts are now displayed in word format to make it easier and quicker to troubleshoot.

'''''Below is a list of all alert codes the PCS can generate, with associated error code number, and plain text descriptions of what each one means'''''

{| class="wikitable mw-collapsible mw-collapsed"
|+ class="no wrap" | Alert Codes
|-
|
! scope="col" | Error code / name
! scope="col" | Error description
|-
! scope="row" | 01
| chgHwInputOc || ???
|-
! scope="row" | 02
| chgHwOutputOc|| ???
|-
! scope="row" | 03
| chgHwInputOv|| ???
|-
! scope="row" | 04
| chgHwIntBusOv|| ???
|-
! scope="row" | 05
| chgOutputOv|| ???
|-
! scope="row" | 06
| chgPrechargeFailedScr|| ???
|-
! scope="row" | 07
| chgPhaseTempHot|| ???
|-
! scope="row" | 08
| chgPhaseOverTemp|| ???
|-
! scope="row" | 09
| chgPfcCurrentRegulation|| ???
|-
! scope="row" | 10
| chgIntBusVRegulation || ???
|-
! scope="row" | 11
| chgLlcCurrentRegulation || ???
|-
! scope="row" | 12
| chgPfcIBandTracerFault || ???
|-
! scope="row" | 13
| chgPrechargeFailedBoost || ???
|-
! scope="row" | 14
| chgTempRationality || ???
|-
! scope="row" | 15
| chg12vUv || ???
|-
! scope="row" | 16
| chgAllPhasesFaulted || ???
|-
! scope="row" | 17
| chgWallPowerRemoval || ???
|-
! scope="row" | 18
| chgUnknownGridConfig || ???
|-
! scope="row" | 19
| acChargePowerLimited || ???
|-
! scope="row" | 20
| chgEnableLineMismatch || "Charge Enable Line Mismatch", Charger was commanded to start over CAN, but the enable line hasn't been correctly brought up
|-
! scope="row" | 21
| hvpMia || ???
|-
! scope="row" | 22
| bmsMia || ???
|-
! scope="row" | 23
| cpMia || ???
|-
! scope="row" | 24
| vcfrontMia || ???
|-
! scope="row" | 25
| cpu2Malfunction || ???
|-
! scope="row" | 26
| watchdogAlarmed || ???
|-
! scope="row" | 27
| chgInsufficientCooling || ???
|-
! scope="row" | 28
| chgOutputUv || The charger was commanded to start, but the AC high voltage is less than what is required to actually charge
|-
! scope="row" | 29
| chgPowerRationality || ???
|-
! scope="row" | 30
| canRationality || ???
|-
! scope="row" | 31
| uiMia || ???
|-
! scope="row" | 32
| unused || ???
|-
! scope="row" | 33
| hvBusUv || ???
|-
! scope="row" | 34
| hvBusOv || ???
|-
! scope="row" | 35
| lvBusUv || ???
|-
! scope="row" | 36
| lvBusOv || ???
|-
! scope="row" | 37
| resonantTankOc || ???
|-
! scope="row" | 38
| claFaulted || ???
|-
! scope="row" | 39
| sdModuleClkFault || ???
|-
! scope="row" | 40
| dcdcMaxPowerReached || ???
|-
! scope="row" | 41
| dcdcOverTemp || ???
|-
! scope="row" | 42
| dcdcEnableLineMismatch || ???
|-
! scope="row" | 43
| hvBusPrechargeFailure || ???
|-
! scope="row" | 44
| 12vSupportRegulation || ???
|-
! scope="row" | 45
| hvBusLowImpedance || ???
|-
! scope="row" | 46
| hvBusHighImpedence || ???
|-
! scope="row" | 47
| lvBusLowImpedance || ???
|-
! scope="row" | 48
| lvBusHighImpedance || ???
|-
! scope="row" | 49
| dcdcTempRationality || ???
|-
! scope="row" | 50
| dcdc12VsupportFaulted || ???
|-
! scope="row" | 51
| chgIntBusUv || ???
|-
! scope="row" | 52
| acVoltageNotPresent || ???
|-
! scope="row" | 53
| chgInputVDropHigh || ???
|-
! scope="row" | 54
| chgInputVDropTooHigh || ???
|-
! scope="row" | 55
| chgLineImedanceHigh || ???
|-
! scope="row" | 56
| chgLineImedanceTooHigh || ???
|-
! scope="row" | 57
| chgInputOverFreq || ???
|-
! scope="row" | 58
| chgInputUnderFreq || ???
|-
! scope="row" | 59
| chgInputOvRms || ???
|-
! scope="row" | 60
| chgInputOvPeak || ???
|-
! scope="row" | 61
| chgVLineRationality || ???
|-
! scope="row" | 62
| chgILineRationality || ???
|-
! scope="row" | 63
| chgVOutRationality || ???
|-
! scope="row" | 64
| chgIOutRationality || ???
|-
! scope="row" | 65
| chgPllNotLocked || ???
|-
! scope="row" | 66
| dcdcHvRationality || The PCS is attempting to start up the DCDC converter, but there isn't any high voltage provided / Are the high voltage lines hooked up to the PCS correctly?
|-
! scope="row" | 67
| dcdcLvRationality || ???
|-
! scope="row" | 68
| dcdcTankvRationality || ???
|-
! scope="row" | 69
| chgPfcLineDidt || ???
|-
! scope="row" | 70
| chgPfcLineDvdt || ???
|-
! scope="row" | 71
| chgPfcILoopRationality || ???
|-
! scope="row" | 72
| cpu2ClaStopped || ???
|-
! scope="row" | 73
| unexpectedAcInputVoltage || ???
|-
! scope="row" | 74
| hvBusDischargeFailure || ???
|-
! scope="row" | 75
| hvBusDischargeTimeout || ???
|-
! scope="row" | 76
| dcdcEnDeassertedErr || "DCDC enable, de-asserted error", Artifact in the software caused by few milisecond delay between DCDC being commanded to shut down over CAN and the hardware line being disabled
|-
! scope="row" | 77
| microGridEnergyLow || ???
|-
! scope="row" | 78
| chgStopDcdcTooHot || ???
|-
! scope="row" | 79
| eepromOperationError || ???
|-
! scope="row" | 80
| damagedPhaseDetected || ???
|-
! scope="row" | 81
| dcdcPchgTimeout || ???
|-
! scope="row" | 82
| dcdcPchgUnsafeDiVoltage || ???
|-
! scope="row" | 83
| triggerOdin || ???
|-
! scope="row" | 84
| unused || ???
|-
! scope="row" | 85
| dcdcFetsNotSwitching || ???
|-
! scope="row" | 86
| dcdcInsufficientCooling || ???
|-
! scope="row" | 87
| nvramRecordStatusError || ???
|-
! scope="row" | 88
| pchgParameters || ???
|-
! scope="row" | 89
| hvBusDischargeIrrational || ???
|-
! scope="row" | 90
| expectedAcVoltageSourceMissing || ???
|-
! scope="row" | 91
| chgIntBusRationality || ???
|-
! scope="row" | 92
| chgPowerLimitedByBusRipple || ???
|-
! scope="row" | 93
| powerRailRationality || ???
|-
! scope="row" | 94
| pcsDcdcNeedService || ???
|-
! scope="row" | 95
| dcdcSensorlessModeActive || ???
|-
! scope="row" | 96
| microGridOverLoaded || ???
|-
! scope="row" | 97
| rebootPhaseDetected || ???
|-
! scope="row" | 98
| gridFreqDroopDetectedSilent || ???
|-
! scope="row" | 99
| microGridOverLoadedSilent || ???
|-
! scope="row" | 100
| microGridEnergyLowSilent || ???
|-
! scope="row" | 101
| phMachineModelIrrational || ???
|-
! scope="row" | 102
| resetWithDCDCCmdAsserted || ???
|-
|}

== Testing ==

=== First Power Up ===

Set up to initially test connections between a PCS and the PCS controller are straightforward. This can be done without any HV DC battery or charging connected to the PCS. Once the PCS controller is connected to the PCS (follow the relevant V2 or V3 pin-outs) the basic steps are:

# Connect the PCS aluminium case to LV ground
# Connect PCS controller ground wire to 12V ground
# Connect PCS 12V power wire via a 5A fuse to +12V
# Observe the PCS controller continuous 3.3V indicator red LED and the flashing activity red LED
# Connect to the PCS controller wifi (SSID will be, for example , ESP-DC87FA) to view the web interface (v3 has a default IP address of 192.168.4.1). The interface will indicate that the PCS 'opmode' is 'Off' at this time
# On the web interface, change 'inputype' to 'Manual' in the drop down menu and select refresh at the top of the screen
# On the web interface, change 'activate' to 'Both'. This will tell the PCS to try start DC-DC and Charging if enabled (as above, these are not connected at this time so will generate alerts that will be mentioned further below)
# On the web interface, change 'AlertLog' to 'On'. This will tell the PCS to show any alerts
# To enable the PCS connect the PCS controller 'Input 1 (enable)' wire to +12V and select refresh at the top of the screen. 'Opmode' should now change to 'Run' on the web interface to show the PCS is now operational
# At this point, 'PCSAlertCnt' will likely show a number indicating the number of alerts the PCS has flagged and 'PCSAlerts' will show the first alert
# To see each alert separately, under General, change the number in the 'Alert' option (0 indicates first alert and should be default) to the next sequential number and select refresh at the top of the screen. 'PCSAlerts' will now show a description of the selected alert. Do this to step through each alert (total number indicated by 'PCSAlertCnt')
# Typical alerts with this configuration (no HV DC battery or charger interface connected) will be: 63chgVOutRationality, 66dcdcHVRationality
# Now the connections and communication with the PCS and controller are established, further testing can be carried out to check DC-DC and charging functionality. See below 

=== DC-DC First Test ===
TBC

=== AC Charging Test ===
TBC

=== Confirmed Working Models ===
to date a number of PCS units have been tested and confirmed to work with the current firmware:
1x 3p EU PCS from circa 2020 model year car
1x 1p US PCS from circa 2018 model year car. Running in BMW E46 touring conversion
1x 1p US PCS from circa 2020 model year car

The minimum recommended HV DC battery voltage for testing is 250V (This needs to be confirmed)

== References ==
<references />
[[Category:OEM]] [[Category:Tesla]] [[Category:Charger]] [[Category:DC/DC]]

Tesla Model 3 Charger/DCDC ("PCS")

2024-09-30T07:26:18Z

Jokeitch: Added pcs alert #28 description,

== Overview ==
The Tesla Model 3 has a "Power Conversion System" (also known as the "PCS") which contains both a 10kW AC charger and a ??W DCDC converter. The PCS is located inside the "Penthouse" part of the main traction battery system.

== Learning/Resources ==
Video - The Tesla Project : Model 3 PCS First Look - https://youtu.be/_TYvSmDJSPQ

Video - Tesla Model 3 Power Conversion System - https://youtu.be/3ARHdRwfxjY

OpenInverter PCS overview/tech thread: https://openinverter.org/forum/viewtopic.php?f=10&t=171

OpenInverter PCS controller support thread: https://openinverter.org/forum/viewtopic.php?p=27744#p27744

Damien's GitHib: https://github.com/damienmaguire/Tesla-Model-3-Charger

== Troubleshooting/Seeking help ==
If you encounter issues with the PCS, it's generally good practice to collect the following information and [https://openinverter.org/forum/viewforum.php?f=10 create a thread on the forums] with a description as detailed as you can be about the problem

# model year of the car it came out of
# any serial numbers on the penthouse or pcs itself, from stickers or identifying markings
## (TBC, where on the penthouse/pcs to locate these)
# firmware version on the pcs
## (TBC, exact instructions on where to find this in the web interface)
# a dump of parameters from the controller
## (TBC, exact instructions on how to do this through the web interface)
# A list of all alerts generated in the alert log
## (TBC, exact instructions on how to find them all in the web interface)

== Hardware ==

=== Controller ===
Damien from EVBMW has designed a control solution which is open source hardware and software. Design files for the controller hardware and software sources are available on Damien's GitHub [https://github.com/damienmaguire/Tesla-Model-3-Charger here]. Controllers are also available as a fully-built kit (with pre-loaded software) on the EVBWM webstore<ref>https://www.evbmw.com/index.php/evbmw-webshop/tesla-boards/tesla-model-3-pcs-con (Backup: [http://web.archive.org/web/20221016211810/https://www.evbmw.com/index.php/evbmw-webshop/tesla-boards/tesla-model-3-pcs-con Web Archive])</ref>.

=== Data Connector on PCS (12-way) ===
''EDITOR'S NOTE: my research shows some conflicting/different part numbers mentioned - would appreciate some clarification here once validated''

As per: https://openinverter.org/forum/viewtopic.php?p=26614#p26614<blockquote>''The connector used for communications with the PCS:'' <ref>https://www.te.com/global-en/product-1379662-5.html (Backup: [http://web.archive.org/web/20221016212020/https://www.te.com/global-en/product-1379662-5.html Web Archive])</ref><ref>https://www.mouser.ie/ProductDetail/TE-Connectivity-AMP/1379662-1?qs=yDt3hdeEHFPzMcXLhRNNtw%3D%3D (Backup: [http://web.archive.org/web/20221016212258/https://www.mouser.ie/ProductDetail/TE-Connectivity-AMP/1379662-1?qs=yDt3hdeEHFPzMcXLhRNNtw%3D%3D Web Archive])</ref>

''Pins:'' <ref>https://www.mouser.ie/ProductDetail/TE-Connectivity/1801069-2?qs=sGAEpiMZZMvlX3nhDDO4AIlVXMSSZRpGH8WODUA4Ad4%3D (Backup: [https://web.archive.org/web/20221016212418/https://www.mouser.ie/ProductDetail/TE-Connectivity/1801069-2?qs=sGAEpiMZZMvlX3nhDDO4AIlVXMSSZRpGH8WODUA4Ad4%3D Web Archive])</ref>

''In true Muskian fashion it seems they use the 1379662-5 natural color variant of the plug which has no coding tabs. It is of course unavailable from mouser. The black and green variants are functionally identical and should work with coding tabs removed.''</blockquote>
[[File:PXL 20231125 230415175~2.jpg|thumb|annotated view of PCS data connector viewed from the front]]
However, as per: https://github.com/muehlpower/EV-FFB, there is also mention of 1318774-1 (white) or 1318774-2 (black) for the comms/data connector.
[[File:V3 PCS controller pinout diagram.jpg|thumb]]

=== Power Connectors ===
The power-side connector assemblies are not widely available. The housings are a Tesla internal part (photos/part numbers [https://openinverter.org/forum/viewtopic.php?p=27744#p27744 here]), however, 3D printable housings have been made available [https://github.com/muehlpower/EV-FFB here]. The terminals also aren't widely available, but are known. As per https://github.com/muehlpower/EV-FFB:

Note: the US variant of the charger (1-phase) has a different AC pin layout; see photo for reference.<blockquote>''The contacts for 400V are Uni F630 from MTA, part number 1107940. For 12V Kostal PLK 14.5, part number 23124734300. The connector for the data is from TE connectivity, part number 1318774-1 for white or 1318774-2 for black.''</blockquote>
[[File:Model 3 US charger variant AC connector.png|thumb|AC connector pinout for US Model 3 PCS (1-phase)]]

=== Connections ===
[[File:Tesla PCS Connection diagram 8162022.png|thumb]]
The minimum wiring needed to wake the PCS:

# PCS controller connected to PCS via 12-way X420
# PCS controller is powered via 20-way +12V input pin and grounded to chassis via 20-way ground pin
# +12v and Chassis ground applied to PCS 12v Connector input terminal
# Chassis ground on the PCS case

== Firmware ==

=== Current Version ===
The current version of the PCS firmware can be found here: https://github.com/damienmaguire/Tesla-Model-3-Charger/releases

The current firmware will auto detect what Tesla firmware is installed on the PCS and adjusts the CAN messages accordingly (different versions of the PCS firmware from Tesla have different CAN requirements). It will also auto detect if the PCS is EU or US spec and whether single or three phase AC is connected. It also includes an integrated alert logging function to help diagnose any issues the PCS sees.

=== Alerts Logging ===
The PCS has an array of potential alerts to help diagnose issues. The images below show a matrix of potential alerts
[[File:PCS Alert Table001.jpg|thumb]]
[[File:PCS Alert Table002.jpg|thumb]]

Initially alerts had to be identified through CAN logs (PCS IPC CAN). In later firmware releases, the PCS web interface incorporated a decoder to help identify alerts (decimal number identifier relating to the alert tables shown here). In the current version of firmware, the alerts are now displayed in word format to make it easier and quicker to troubleshoot.

'''''Below is a list of all alert codes the PCS can generate, with associated error code number, and plain text descriptions of what each one means'''''

{| class="wikitable mw-collapsible mw-collapsed"
|+ class="no wrap" | Alert Codes
|-
|
! scope="col" | Error code / name
! scope="col" | Error description
|-
! scope="row" | 01
| chgHwInputOc || ???
|-
! scope="row" | 02
| chgHwOutputOc|| ???
|-
! scope="row" | 03
| chgHwInputOv|| ???
|-
! scope="row" | 04
| chgHwIntBusOv|| ???
|-
! scope="row" | 05
| chgOutputOv|| ???
|-
! scope="row" | 06
| chgPrechargeFailedScr|| ???
|-
! scope="row" | 07
| chgPhaseTempHot|| ???
|-
! scope="row" | 08
| chgPhaseOverTemp|| ???
|-
! scope="row" | 09
| chgPfcCurrentRegulation|| ???
|-
! scope="row" | 10
| chgIntBusVRegulation || ???
|-
! scope="row" | 11
| chgLlcCurrentRegulation || ???
|-
! scope="row" | 12
| chgPfcIBandTracerFault || ???
|-
! scope="row" | 13
| chgPrechargeFailedBoost || ???
|-
! scope="row" | 14
| chgTempRationality || ???
|-
! scope="row" | 15
| chg12vUv || ???
|-
! scope="row" | 16
| chgAllPhasesFaulted || ???
|-
! scope="row" | 17
| chgWallPowerRemoval || ???
|-
! scope="row" | 18
| chgUnknownGridConfig || ???
|-
! scope="row" | 19
| acChargePowerLimited || ???
|-
! scope="row" | 20
| chgEnableLineMismatch || "Charge Enable Line Mismatch", Charger was commanded to start over CAN, but the enable line hasn't been correctly brought up
|-
! scope="row" | 21
| hvpMia || ???
|-
! scope="row" | 22
| bmsMia || ???
|-
! scope="row" | 23
| cpMia || ???
|-
! scope="row" | 24
| vcfrontMia || ???
|-
! scope="row" | 25
| cpu2Malfunction || ???
|-
! scope="row" | 26
| watchdogAlarmed || ???
|-
! scope="row" | 27
| chgInsufficientCooling || ???
|-
! scope="row" | 28
| chgOutputUv || The charger was commanded to start, but the AC high voltage is less than what is required to actually charge
|-
! scope="row" | 29
| chgPowerRationality || ???
|-
! scope="row" | 30
| canRationality || ???
|-
! scope="row" | 31
| uiMia || ???
|-
! scope="row" | 32
| unused || ???
|-
! scope="row" | 33
| hvBusUv || ???
|-
! scope="row" | 34
| hvBusOv || ???
|-
! scope="row" | 35
| lvBusUv || ???
|-
! scope="row" | 36
| lvBusOv || ???
|-
! scope="row" | 37
| resonantTankOc || ???
|-
! scope="row" | 38
| claFaulted || ???
|-
! scope="row" | 39
| sdModuleClkFault || ???
|-
! scope="row" | 40
| dcdcMaxPowerReached || ???
|-
! scope="row" | 41
| dcdcOverTemp || ???
|-
! scope="row" | 42
| dcdcEnableLineMismatch || ???
|-
! scope="row" | 43
| hvBusPrechargeFailure || ???
|-
! scope="row" | 44
| 12vSupportRegulation || ???
|-
! scope="row" | 45
| hvBusLowImpedance || ???
|-
! scope="row" | 46
| hvBusHighImpedence || ???
|-
! scope="row" | 47
| lvBusLowImpedance || ???
|-
! scope="row" | 48
| lvBusHighImpedance || ???
|-
! scope="row" | 49
| dcdcTempRationality || ???
|-
! scope="row" | 50
| dcdc12VsupportFaulted || ???
|-
! scope="row" | 51
| chgIntBusUv || ???
|-
! scope="row" | 52
| acVoltageNotPresent || ???
|-
! scope="row" | 53
| chgInputVDropHigh || ???
|-
! scope="row" | 54
| chgInputVDropTooHigh || ???
|-
! scope="row" | 55
| chgLineImedanceHigh || ???
|-
! scope="row" | 56
| chgLineImedanceTooHigh || ???
|-
! scope="row" | 57
| chgInputOverFreq || ???
|-
! scope="row" | 58
| chgInputUnderFreq || ???
|-
! scope="row" | 59
| chgInputOvRms || ???
|-
! scope="row" | 60
| chgInputOvPeak || ???
|-
! scope="row" | 61
| chgVLineRationality || ???
|-
! scope="row" | 62
| chgILineRationality || ???
|-
! scope="row" | 63
| chgVOutRationality || ???
|-
! scope="row" | 64
| chgIOutRationality || ???
|-
! scope="row" | 65
| chgPllNotLocked || ???
|-
! scope="row" | 66
| dcdcHvRationality || The PCS is attempting to start up the DCDC converter, but there isn't any high voltage provided / Are the high voltage lines hooked up to the PCS correctly?
|-
! scope="row" | 67
| dcdcLvRationality || ???
|-
! scope="row" | 68
| dcdcTankvRationality || ???
|-
! scope="row" | 69
| chgPfcLineDidt || ???
|-
! scope="row" | 70
| chgPfcLineDvdt || ???
|-
! scope="row" | 71
| chgPfcILoopRationality || ???
|-
! scope="row" | 72
| cpu2ClaStopped || ???
|-
! scope="row" | 73
| unexpectedAcInputVoltage || ???
|-
! scope="row" | 74
| hvBusDischargeFailure || ???
|-
! scope="row" | 75
| hvBusDischargeTimeout || ???
|-
! scope="row" | 76
| dcdcEnDeassertedErr || "DCDC enable, de-asserted error", Artifact in the software caused by few milisecond delay between DCDC being commanded to shut down over CAN and the hardware line being disabled
|-
! scope="row" | 77
| microGridEnergyLow || ???
|-
! scope="row" | 78
| chgStopDcdcTooHot || ???
|-
! scope="row" | 79
| eepromOperationError || ???
|-
! scope="row" | 80
| damagedPhaseDetected || ???
|-
! scope="row" | 81
| dcdcPchgTimeout || ???
|-
! scope="row" | 82
| dcdcPchgUnsafeDiVoltage || ???
|-
! scope="row" | 83
| triggerOdin || ???
|-
! scope="row" | 84
| unused || ???
|-
! scope="row" | 85
| dcdcFetsNotSwitching || ???
|-
! scope="row" | 86
| dcdcInsufficientCooling || ???
|-
! scope="row" | 87
| nvramRecordStatusError || ???
|-
! scope="row" | 88
| pchgParameters || ???
|-
! scope="row" | 89
| hvBusDischargeIrrational || ???
|-
! scope="row" | 90
| expectedAcVoltageSourceMissing || ???
|-
! scope="row" | 91
| chgIntBusRationality || ???
|-
! scope="row" | 92
| chgPowerLimitedByBusRipple || ???
|-
! scope="row" | 93
| powerRailRationality || ???
|-
! scope="row" | 94
| pcsDcdcNeedService || ???
|-
! scope="row" | 95
| dcdcSensorlessModeActive || ???
|-
! scope="row" | 96
| microGridOverLoaded || ???
|-
! scope="row" | 97
| rebootPhaseDetected || ???
|-
! scope="row" | 98
| gridFreqDroopDetectedSilent || ???
|-
! scope="row" | 99
| microGridOverLoadedSilent || ???
|-
! scope="row" | 100
| microGridEnergyLowSilent || ???
|-
! scope="row" | 101
| phMachineModelIrrational || ???
|-
! scope="row" | 102
| resetWithDCDCCmdAsserted || ???
|-
|}

== Testing ==

=== First Power Up ===

Set up to initially test connections between a PCS and the PCS controller are straightforward. This can be done without any HV DC battery or charging connected to the PCS. Once the PCS controller is connected to the PCS (follow the relevant V2 or V3 pin-outs) the basic steps are:

# Connect the PCS aluminium case to LV ground
# Connect PCS controller ground wire to 12V ground
# Connect PCS 12V power wire via a 5A fuse to +12V
# Observe the PCS controller continuous 3.3V indicator red LED and the flashing activity red LED
# Connect to the PCS controller wifi (SSID will be, for example , ESP-DC87FA) to view the web interface (v3 has a default IP address of 192.168.4.1). The interface will indicate that the PCS 'opmode' is 'Off' at this time
# On the web interface, change 'inputype' to 'Manual' in the drop down menu and select refresh at the top of the screen
# On the web interface, change 'activate' to 'Both'. This will tell the PCS to try start DC-DC and Charging if enabled (as above, these are not connected at this time so will generate alerts that will be mentioned further below)
# On the web interface, change 'AlertLog' to 'On'. This will tell the PCS to show any alerts
# To enable the PCS connect the PCS controller 'Input 1 (enable)' wire to +12V and select refresh at the top of the screen. 'Opmode' should now change to 'Run' on the web interface to show the PCS is now operational
# At this point, 'PCSAlertCnt' will likely show a number indicating the number of alerts the PCS has flagged and 'PCSAlerts' will show the first alert
# To see each alert separately, under General, change the number in the 'Alert' option (0 indicates first alert and should be default) to the next sequential number and select refresh at the top of the screen. 'PCSAlerts' will now show a description of the selected alert. Do this to step through each alert (total number indicated by 'PCSAlertCnt')
# Typical alerts with this configuration (no HV DC battery or charger interface connected) will be: 63chgVOutRationality, 66dcdcHVRationality
# Now the connections and communication with the PCS and controller are established, further testing can be carried out to check DC-DC and charging functionality. See below 

=== DC-DC First Test ===
TBC

=== AC Charging Test ===
TBC

=== Confirmed Working Models ===
to date a number of PCS units have been tested and confirmed to work with the current firmware:
1x 3p EU PCS from circa 2020 model year car
1x 1p US PCS from circa 2018 model year car. Running in BMW E46 touring conversion
1x 1p US PCS from circa 2020 model year car

The minimum recommended HV DC battery voltage for testing is 250V (This needs to be confirmed)

== References ==
<references />
[[Category:OEM]] [[Category:Tesla]] [[Category:Charger]] [[Category:DC/DC]]

Tesla Model 3 Charger/DCDC ("PCS")

2024-09-29T08:14:58Z

Jokeitch: Adding a collapsed list of all possible alert log messages, to be filled out with plain text descriptions, also starting a troubleshooting section with instructions on how to gather the specific information needed

== Overview ==
The Tesla Model 3 has a "Power Conversion System" (also known as the "PCS") which contains both a 10kW AC charger and a ??W DCDC converter. The PCS is located inside the "Penthouse" part of the main traction battery system.

== Learning/Resources ==
Video - The Tesla Project : Model 3 PCS First Look - https://youtu.be/_TYvSmDJSPQ

Video - Tesla Model 3 Power Conversion System - https://youtu.be/3ARHdRwfxjY

OpenInverter PCS overview/tech thread: https://openinverter.org/forum/viewtopic.php?f=10&t=171

OpenInverter PCS controller support thread: https://openinverter.org/forum/viewtopic.php?p=27744#p27744

Damien's GitHib: https://github.com/damienmaguire/Tesla-Model-3-Charger

== Troubleshooting/Seeking help ==
If you encounter issues with the PCS, it's generally good practice to collect the following information and [https://openinverter.org/forum/viewforum.php?f=10 create a thread on the forums] with a description as detailed as you can be about the problem

# model year of the car it came out of
# any serial numbers on the penthouse or pcs itself, from stickers or identifying markings
## (TBC, where on the penthouse/pcs to locate these)
# firmware version on the pcs
## (TBC, exact instructions on where to find this in the web interface)
# a dump of parameters from the controller
## (TBC, exact instructions on how to do this through the web interface)
# A list of all alerts generated in the alert log
## (TBC, exact instructions on how to find them all in the web interface)

== Hardware ==

=== Controller ===
Damien from EVBMW has designed a control solution which is open source hardware and software. Design files for the controller hardware and software sources are available on Damien's GitHub [https://github.com/damienmaguire/Tesla-Model-3-Charger here]. Controllers are also available as a fully-built kit (with pre-loaded software) on the EVBWM webstore<ref>https://www.evbmw.com/index.php/evbmw-webshop/tesla-boards/tesla-model-3-pcs-con (Backup: [http://web.archive.org/web/20221016211810/https://www.evbmw.com/index.php/evbmw-webshop/tesla-boards/tesla-model-3-pcs-con Web Archive])</ref>.

=== Data Connector on PCS (12-way) ===
''EDITOR'S NOTE: my research shows some conflicting/different part numbers mentioned - would appreciate some clarification here once validated''

As per: https://openinverter.org/forum/viewtopic.php?p=26614#p26614<blockquote>''The connector used for communications with the PCS:'' <ref>https://www.te.com/global-en/product-1379662-5.html (Backup: [http://web.archive.org/web/20221016212020/https://www.te.com/global-en/product-1379662-5.html Web Archive])</ref><ref>https://www.mouser.ie/ProductDetail/TE-Connectivity-AMP/1379662-1?qs=yDt3hdeEHFPzMcXLhRNNtw%3D%3D (Backup: [http://web.archive.org/web/20221016212258/https://www.mouser.ie/ProductDetail/TE-Connectivity-AMP/1379662-1?qs=yDt3hdeEHFPzMcXLhRNNtw%3D%3D Web Archive])</ref>

''Pins:'' <ref>https://www.mouser.ie/ProductDetail/TE-Connectivity/1801069-2?qs=sGAEpiMZZMvlX3nhDDO4AIlVXMSSZRpGH8WODUA4Ad4%3D (Backup: [https://web.archive.org/web/20221016212418/https://www.mouser.ie/ProductDetail/TE-Connectivity/1801069-2?qs=sGAEpiMZZMvlX3nhDDO4AIlVXMSSZRpGH8WODUA4Ad4%3D Web Archive])</ref>

''In true Muskian fashion it seems they use the 1379662-5 natural color variant of the plug which has no coding tabs. It is of course unavailable from mouser. The black and green variants are functionally identical and should work with coding tabs removed.''</blockquote>
[[File:PXL 20231125 230415175~2.jpg|thumb|annotated view of PCS data connector viewed from the front]]
However, as per: https://github.com/muehlpower/EV-FFB, there is also mention of 1318774-1 (white) or 1318774-2 (black) for the comms/data connector.
[[File:V3 PCS controller pinout diagram.jpg|thumb]]

=== Power Connectors ===
The power-side connector assemblies are not widely available. The housings are a Tesla internal part (photos/part numbers [https://openinverter.org/forum/viewtopic.php?p=27744#p27744 here]), however, 3D printable housings have been made available [https://github.com/muehlpower/EV-FFB here]. The terminals also aren't widely available, but are known. As per https://github.com/muehlpower/EV-FFB:

Note: the US variant of the charger (1-phase) has a different AC pin layout; see photo for reference.<blockquote>''The contacts for 400V are Uni F630 from MTA, part number 1107940. For 12V Kostal PLK 14.5, part number 23124734300. The connector for the data is from TE connectivity, part number 1318774-1 for white or 1318774-2 for black.''</blockquote>
[[File:Model 3 US charger variant AC connector.png|thumb|AC connector pinout for US Model 3 PCS (1-phase)]]

=== Connections ===
[[File:Tesla PCS Connection diagram 8162022.png|thumb]]
The minimum wiring needed to wake the PCS:

# PCS controller connected to PCS via 12-way X420
# PCS controller is powered via 20-way +12V input pin and grounded to chassis via 20-way ground pin
# +12v and Chassis ground applied to PCS 12v Connector input terminal
# Chassis ground on the PCS case

== Firmware ==

=== Current Version ===
The current version of the PCS firmware can be found here: https://github.com/damienmaguire/Tesla-Model-3-Charger/releases

The current firmware will auto detect what Tesla firmware is installed on the PCS and adjusts the CAN messages accordingly (different versions of the PCS firmware from Tesla have different CAN requirements). It will also auto detect if the PCS is EU or US spec and whether single or three phase AC is connected. It also includes an integrated alert logging function to help diagnose any issues the PCS sees.

=== Alerts Logging ===
The PCS has an array of potential alerts to help diagnose issues. The images below show a matrix of potential alerts
[[File:PCS Alert Table001.jpg|thumb]]
[[File:PCS Alert Table002.jpg|thumb]]

Initially alerts had to be identified through CAN logs (PCS IPC CAN). In later firmware releases, the PCS web interface incorporated a decoder to help identify alerts (decimal number identifier relating to the alert tables shown here). In the current version of firmware, the alerts are now displayed in word format to make it easier and quicker to troubleshoot.

'''''Below is a list of all alert codes the PCS can generate, with associated error code number, and plain text descriptions of what each one means'''''

{| class="wikitable mw-collapsible mw-collapsed"
|+ class="no wrap" | Alert Codes
|-
|
! scope="col" | Error code / name
! scope="col" | Error description
|-
! scope="row" | 01
| chgHwInputOc || ???
|-
! scope="row" | 02
| chgHwOutputOc|| ???
|-
! scope="row" | 03
| chgHwInputOv|| ???
|-
! scope="row" | 04
| chgHwIntBusOv|| ???
|-
! scope="row" | 05
| chgOutputOv|| ???
|-
! scope="row" | 06
| chgPrechargeFailedScr|| ???
|-
! scope="row" | 07
| chgPhaseTempHot|| ???
|-
! scope="row" | 08
| chgPhaseOverTemp|| ???
|-
! scope="row" | 09
| chgPfcCurrentRegulation|| ???
|-
! scope="row" | 10
| chgIntBusVRegulation || ???
|-
! scope="row" | 11
| chgLlcCurrentRegulation || ???
|-
! scope="row" | 12
| chgPfcIBandTracerFault || ???
|-
! scope="row" | 13
| chgPrechargeFailedBoost || ???
|-
! scope="row" | 14
| chgTempRationality || ???
|-
! scope="row" | 15
| chg12vUv || ???
|-
! scope="row" | 16
| chgAllPhasesFaulted || ???
|-
! scope="row" | 17
| chgWallPowerRemoval || ???
|-
! scope="row" | 18
| chgUnknownGridConfig || ???
|-
! scope="row" | 19
| acChargePowerLimited || ???
|-
! scope="row" | 20
| chgEnableLineMismatch || "Charge Enable Line Mismatch", Charger was commanded to start over CAN, but the enable line hasn't been correctly brought up
|-
! scope="row" | 21
| hvpMia || ???
|-
! scope="row" | 22
| bmsMia || ???
|-
! scope="row" | 23
| cpMia || ???
|-
! scope="row" | 24
| vcfrontMia || ???
|-
! scope="row" | 25
| cpu2Malfunction || ???
|-
! scope="row" | 26
| watchdogAlarmed || ???
|-
! scope="row" | 27
| chgInsufficientCooling || ???
|-
! scope="row" | 28
| chgOutputUv || ???
|-
! scope="row" | 29
| chgPowerRationality || ???
|-
! scope="row" | 30
| canRationality || ???
|-
! scope="row" | 31
| uiMia || ???
|-
! scope="row" | 32
| unused || ???
|-
! scope="row" | 33
| hvBusUv || ???
|-
! scope="row" | 34
| hvBusOv || ???
|-
! scope="row" | 35
| lvBusUv || ???
|-
! scope="row" | 36
| lvBusOv || ???
|-
! scope="row" | 37
| resonantTankOc || ???
|-
! scope="row" | 38
| claFaulted || ???
|-
! scope="row" | 39
| sdModuleClkFault || ???
|-
! scope="row" | 40
| dcdcMaxPowerReached || ???
|-
! scope="row" | 41
| dcdcOverTemp || ???
|-
! scope="row" | 42
| dcdcEnableLineMismatch || ???
|-
! scope="row" | 43
| hvBusPrechargeFailure || ???
|-
! scope="row" | 44
| 12vSupportRegulation || ???
|-
! scope="row" | 45
| hvBusLowImpedance || ???
|-
! scope="row" | 46
| hvBusHighImpedence || ???
|-
! scope="row" | 47
| lvBusLowImpedance || ???
|-
! scope="row" | 48
| lvBusHighImpedance || ???
|-
! scope="row" | 49
| dcdcTempRationality || ???
|-
! scope="row" | 50
| dcdc12VsupportFaulted || ???
|-
! scope="row" | 51
| chgIntBusUv || ???
|-
! scope="row" | 52
| acVoltageNotPresent || ???
|-
! scope="row" | 53
| chgInputVDropHigh || ???
|-
! scope="row" | 54
| chgInputVDropTooHigh || ???
|-
! scope="row" | 55
| chgLineImedanceHigh || ???
|-
! scope="row" | 56
| chgLineImedanceTooHigh || ???
|-
! scope="row" | 57
| chgInputOverFreq || ???
|-
! scope="row" | 58
| chgInputUnderFreq || ???
|-
! scope="row" | 59
| chgInputOvRms || ???
|-
! scope="row" | 60
| chgInputOvPeak || ???
|-
! scope="row" | 61
| chgVLineRationality || ???
|-
! scope="row" | 62
| chgILineRationality || ???
|-
! scope="row" | 63
| chgVOutRationality || ???
|-
! scope="row" | 64
| chgIOutRationality || ???
|-
! scope="row" | 65
| chgPllNotLocked || ???
|-
! scope="row" | 66
| dcdcHvRationality || The PCS is attempting to start up the DCDC converter, but there isn't any high voltage provided / Are the high voltage lines hooked up to the PCS correctly?
|-
! scope="row" | 67
| dcdcLvRationality || ???
|-
! scope="row" | 68
| dcdcTankvRationality || ???
|-
! scope="row" | 69
| chgPfcLineDidt || ???
|-
! scope="row" | 70
| chgPfcLineDvdt || ???
|-
! scope="row" | 71
| chgPfcILoopRationality || ???
|-
! scope="row" | 72
| cpu2ClaStopped || ???
|-
! scope="row" | 73
| unexpectedAcInputVoltage || ???
|-
! scope="row" | 74
| hvBusDischargeFailure || ???
|-
! scope="row" | 75
| hvBusDischargeTimeout || ???
|-
! scope="row" | 76
| dcdcEnDeassertedErr || "DCDC enable, de-asserted error", Artifact in the software caused by few milisecond delay between DCDC being commanded to shut down over CAN and the hardware line being disabled
|-
! scope="row" | 77
| microGridEnergyLow || ???
|-
! scope="row" | 78
| chgStopDcdcTooHot || ???
|-
! scope="row" | 79
| eepromOperationError || ???
|-
! scope="row" | 80
| damagedPhaseDetected || ???
|-
! scope="row" | 81
| dcdcPchgTimeout || ???
|-
! scope="row" | 82
| dcdcPchgUnsafeDiVoltage || ???
|-
! scope="row" | 83
| triggerOdin || ???
|-
! scope="row" | 84
| unused || ???
|-
! scope="row" | 85
| dcdcFetsNotSwitching || ???
|-
! scope="row" | 86
| dcdcInsufficientCooling || ???
|-
! scope="row" | 87
| nvramRecordStatusError || ???
|-
! scope="row" | 88
| pchgParameters || ???
|-
! scope="row" | 89
| hvBusDischargeIrrational || ???
|-
! scope="row" | 90
| expectedAcVoltageSourceMissing || ???
|-
! scope="row" | 91
| chgIntBusRationality || ???
|-
! scope="row" | 92
| chgPowerLimitedByBusRipple || ???
|-
! scope="row" | 93
| powerRailRationality || ???
|-
! scope="row" | 94
| pcsDcdcNeedService || ???
|-
! scope="row" | 95
| dcdcSensorlessModeActive || ???
|-
! scope="row" | 96
| microGridOverLoaded || ???
|-
! scope="row" | 97
| rebootPhaseDetected || ???
|-
! scope="row" | 98
| gridFreqDroopDetectedSilent || ???
|-
! scope="row" | 99
| microGridOverLoadedSilent || ???
|-
! scope="row" | 100
| microGridEnergyLowSilent || ???
|-
! scope="row" | 101
| phMachineModelIrrational || ???
|-
! scope="row" | 102
| resetWithDCDCCmdAsserted || ???
|-
|}

== Testing ==

=== First Power Up ===

Set up to initially test connections between a PCS and the PCS controller are straightforward. This can be done without any HV DC battery or charging connected to the PCS. Once the PCS controller is connected to the PCS (follow the relevant V2 or V3 pin-outs) the basic steps are:

# Connect the PCS aluminium case to LV ground
# Connect PCS controller ground wire to 12V ground
# Connect PCS 12V power wire via a 5A fuse to +12V
# Observe the PCS controller continuous 3.3V indicator red LED and the flashing activity red LED
# Connect to the PCS controller wifi (SSID will be, for example , ESP-DC87FA) to view the web interface (v3 has a default IP address of 192.168.4.1). The interface will indicate that the PCS 'opmode' is 'Off' at this time
# On the web interface, change 'inputype' to 'Manual' in the drop down menu and select refresh at the top of the screen
# On the web interface, change 'activate' to 'Both'. This will tell the PCS to try start DC-DC and Charging if enabled (as above, these are not connected at this time so will generate alerts that will be mentioned further below)
# On the web interface, change 'AlertLog' to 'On'. This will tell the PCS to show any alerts
# To enable the PCS connect the PCS controller 'Input 1 (enable)' wire to +12V and select refresh at the top of the screen. 'Opmode' should now change to 'Run' on the web interface to show the PCS is now operational
# At this point, 'PCSAlertCnt' will likely show a number indicating the number of alerts the PCS has flagged and 'PCSAlerts' will show the first alert
# To see each alert separately, under General, change the number in the 'Alert' option (0 indicates first alert and should be default) to the next sequential number and select refresh at the top of the screen. 'PCSAlerts' will now show a description of the selected alert. Do this to step through each alert (total number indicated by 'PCSAlertCnt')
# Typical alerts with this configuration (no HV DC battery or charger interface connected) will be: 63chgVOutRationality, 66dcdcHVRationality
# Now the connections and communication with the PCS and controller are established, further testing can be carried out to check DC-DC and charging functionality. See below 

=== DC-DC First Test ===
TBC

=== AC Charging Test ===
TBC

=== Confirmed Working Models ===
to date a number of PCS units have been tested and confirmed to work with the current firmware:
1x 3p EU PCS from circa 2020 model year car
1x 1p US PCS from circa 2018 model year car. Running in BMW E46 touring conversion
1x 1p US PCS from circa 2020 model year car

The minimum recommended HV DC battery voltage for testing is 250V (This needs to be confirmed)

== References ==
<references />
[[Category:OEM]] [[Category:Tesla]] [[Category:Charger]] [[Category:DC/DC]]

Tesla Model 3 Charger/DCDC ("PCS")

2023-11-27T02:33:25Z

Jokeitch: /* First Power Up */ , esp32 web service defaults

Tesla Model 3 Charger/DCDC ("PCS")

2023-11-25T23:14:19Z

Jokeitch: Added image to /* Data Connector on PCS (12-way) */

File:PXL 20231125 230415175~2.jpg

2023-11-25T23:12:20Z

Jokeitch:

Annotated view of PCS data connector, from the front