J1939 EV for GO Device Compatibility
Implementation Guide
0 mins to read
Learn how to implement the J1939 mandatory and optional signal sets for GO device compatibility. Browse frequently asked questions about implementation and review the EV mandatory Go device PGNs and SPNs.
For Medium-duty and Heavy-duty OEMs
Table of contents
Glossary
AC | Alternating Current |
BAM | Broadcast Announce Message |
CAN | Controller Area Network |
DC | Direct Current |
Dec | Decimal |
DT | Data Transfer |
ECU | Engine/Electronic Control Unit |
EV | Electric Vehicle |
EVSE | Electric Vehicle Supply Equipment |
FAQ | Frequently Asked Questions |
Hex | Hexadecimal |
HV | High Voltage |
HVES | High Voltage Energy Source |
HVESP1 | High Voltage Energy Source Pack 1 |
HVESP2 | High Voltage Energy Source Pack 2 |
HVESS | High Voltage Energy Storage System |
Hz | Hertz |
OBDII | On-board Diagnostic v2 |
OEM | Original Equipment Manufacturer |
PGN | Parameter Group Number |
RMS | Root Mean Square |
SLI | Starting, Lighting, and Ignition |
SPN | Suspect Parameter Number |
VIN | Vehicle Identification Number |
Introduction
This guide aims to help OEMs implement the J1939 signal set for GO device compatibility, and includes both mandatory and optional signal sets. For questions about the information in this document, or for additional clarification on how to implement a parameter, please reach out to your Geotab point of contact or send an email to evsoleng@geotab.com.
✱ NOTE: All parameters discussed in this document fall under the EV signals subset in the J1939 Digital Annex as set by SAE. The GO device also supports non-EV related parameters in J1939 Standard. If there is a particular parameter that you wish to implement and is not on this list, please reach out to your Geotab point of contact to check whether the parameter is supported with the GO device.
Implementation Process
The J1939 EV implementation process typically takes 4 to 6 weeks. A public-facing list of electric vehicles (EVs) supported by Geotab are found here.
As an overview, the following steps will be taken to implement the J1939 EV signal set:
1 | OEM agrees to adopt the J1939 EV signal set. |
2 | OEM sets up a test database in MyGeotab with assistance from an EV Solutions Engineer or Geotab point of contact, and creates user accounts for individuals who require access to the database. |
3 | OEM installs the GO device in the vehicle and adds the device to the test database with assistance from an EV Solutions Engineer or Geotab point of contact. Note: Depending on the type of diagnostic port on your vehicle, you may require a harness. Please ensure you notify the Geotab point of contact that ships the test device to you. Geotab has various straight and T-harnesses for standard diagnostic ports. Note: If your vehicle has a non-standard diagnostic port, please reach out to your Geotab point of contact or the EV Solutions Engineering team to determine the best method of integration. |
4 | OEM sets up their CAN network on the vehicle based on the J1939 EV signal set. Note: Do not hesitate to reach out to your Geotab point of contact if you require additional test devices or additional resources during this step. |
5 | Once the vehicle has fully conformed to the signal set, please reach out to your Geotab point of contact or the EV Solutions Engineering team to initiate the data validation process (details here). Also, please inform the Geotab point of contact or EV Solutions Engineering team if you would like additional devices during this step to verify compliance on more than one vehicle or platform. |
6 | The Geotab team completes the data validation process and adds the vehicle to the public-facing list of fully supported electric vehicles. Please see here for more details. |
GO Device Supported PGNs and SPNs - EV Mandatory
✱ NOTE: These are the mandatory PGNs and SPNs that the vehicle is required to broadcast on CAN in order to be compatible with the EV features seen on the MyGeotab portal. All vehicles supported by adopting J1939 EV are required to report these. There is also an expanded signal set that is optional, and will make more data available on the portal, should you choose to implement it. A full list of all GO device supported J1939 SPNs can be found here.
PGN | SPN | SPN Name | Description of data | SPN length | Bit Resolution (If applicable) | |||||
61584 | 5919 | High voltage battery voltage | The voltage level of the High Voltage Energy Storage 1 pack (or system). This parameter should be synchronized with SPN 5920 (HVES1 Current) such that a realized power value can be calculated. If the HVES component physically contains the contactors which connect it to the vehicle high voltage system, then this voltage is measured before those contactors. Note: The GO device is currently not capable of supporting data collection from multiple energy storage packs. | 2 bytes | 0.05 V / bit | |||||
61584 | 5920 | High voltage battery current | The current in or out of the High Voltage Energy Storage 1 pack (or system). This parameter should be synchronized with SPN 5919 (HVES1 Voltage Level) such that a realized power value can be calculated.This parameter is defined from the high voltage energy storage system’s point of view. A positive value represents current into (charging) the energy storage system. A negative value represents current out of (discharging) the energy storage system. This parameter provides HVES system level information. Note: The GO device is currently not capable of supporting data collection from multiple energy storage packs. Sign convention: HV Battery Current > 0 = Energy entering the battery
| 2 bytes | 0.05 A / bit | |||||
61590 | 8207 | Internal Charger Status | This signal is indicative of AC Charging status. Please see this FAQ for more information. SPN description from the J1939 DA is below. Vehicle charging status * 0x00 = Charging off * 0x01 = Charging on * 0x02 = Error * 0x03 = Not Available If 0x01 sets GENERIC_EV_CHARGING_STATE to 1 (EV_CHARGE_STATE_AC) | 2 bits | 4 states/2 bit | |||||
64706 | 7895 | Generic state of charge | Stored Energy Source Level indicates the current operating stored energy source capacity. In Electric Hybrids, this is the current percentage of the HVES useable capacity. When the state of charge is below the minimum HVES useable capacity, this parameter shall be set to 0 percent. When the state of charge of the HVES is above the maximum HVES useable capacity, this parameter shall be set to 100%. When charging the HVES, this parameter may be used to determine the progress towards the Stored Energy Source Set Point Request (SPN 7892). This parameter may also be used as a “fuel level” indicator for the vehicle operator. For example, a HVES manufacturer may define the HVES useable capacity to be between a notional 30% to 70% state of charge (SOC). In this example, the 0% stored energy level would be the equivalent of 30% or lower SOC and the 100% stored energy source level would be the equivalent of 70% or higher SOC. | 1 byte | 0.4% / bit | |||||
64706 | 7315 | Ignition | Vehicle enabled / ready to drive * 0x00 = Not Ready (ignition off) * 0x01 = Ready (ignition on) * 0x02 = SAE Reserved (treated as ignition off) * 0x03 = Not Available (treated as ignition off) | 2 bits | 4 states/2 bit | |||||
64706 | 7898 | External Energy Source Connection Status | This signal is indicative of Vehicle isCharging status. Please see this FAQ for more information. SPN description from the J1939 DA is below. External Energy Source Connection Status provides feedback to the External Energy Source Connection Demand (SPN 7890). This parameter allows for status of two external energy source connections. See External Energy Source Connection Demand (SPN 7890) for the detailed state definitions. In the case of a Diesel-Electric Hybrid, this parameter is sent by the hybrid system or Power System manager. 0000b = No Connection 0001b = Connection 1 – Error (Verification failed) 0010b = Connection 1 – Verification in Process 0011b = Connection 1 – Energy Source and Drain 0100b = Connection 1 – Energy Source 0101b = Connection 1 – Energy Drain 0110b = Connection 2 – Error (Verification failed) 0111b = Connection 2 – Verification in Process 1000b = Connection 2 – Energy Source and Drain 1001b = Connection 2 – Energy Source 1010b = Connection 2 – Energy Drain 1011b to 1101b = Reserved 1110b = Error 1111b = Not Available | 4 bits | 16 states/4 bit | |||||
57344 | 1856 | Seatbelt switch | Parameter to indicate seat belt data. Please see this FAQ for more information. | 2 bits | 4 states/2 bit | |||||
61445 | 523 | Transmission current gear | Contains the gear status. Please see this FAQ for more information. | 1 byte | 1 gear value/bit | |||||
64212 | 12866 | EVSE1 AC RMS Current | AC RMS current being drawn from the EVSE. Negative values indicate power being drained from the vehicle and returned to the grid. Sign convention
| 2 bytes | 0.05 A/bit | |||||
64212 | 12867 | EVSE1 AC RMS Voltage | AC RMS Voltage of this connected EVSE supply. Note: Not applicable if the EV only allows for DC charging. | 2 bytes | 0.05 V/bit | |||||
64184 | 13171 | DC Charging State | This signal is indicative of DC Charging status. Please see this FAQ for more information. SPN description from the J1939 DA is below. Overall State of the DC charging system 0 = Idle. No EVSE connected. 1 = Charging. 2 = Standby. 3-9 = reserved 10 = Initialising 11 = Pre-charge 12 = Terminating 13 = Battery failure. An error condition due to the battery state (high temperature, etc.) 14 = EVSE fault. An error condition due to the EVSE. 15 = Not available. | 4 bits | 16 states/4 bit | |||||
65217 | 917 | High resolution total vehicle distance | Contains the total distance covered by the vehicle | 4 bytes | 5 m/bit | |||||
65269 | 171 | Ambient Air Temperature | Temperature of air surrounding vehicle. | 2 bytes | 0.03125 degree C/ bit | |||||
65260 | 237 | Vehicle Identification Number (VIN) | Contains vehicle's VIN information. Please see this FAQ for more information. | Multilength | NA | |||||
65265 | 84 | Wheel based vehicle speed | Speed of the vehicle as calculated from the wheel or tailshaft speed | 2 bytes | 1/256 km/hr per bit | |||||
65226 | Active diagnostic trouble codes | Multilength | NA | |||||||
For additional details, please see the J1939 Digital Annex | ||||||||||
! Data Quality Reminder: Although J1939 is a low-level protocol, It is very important to consider data quality when implementing the J1939 EV signals specified in this document. The GO device typically does not filter data for validity and user readability. The recorded vehicle side data is presented as-is on the MyGeotab portal. Hence, in order to ensure users interpret the data correctly and the presented data helps the users manage their vehicles precisely and efficiently, Geotab requests that OEMs implement filtered J1939 data.
FAQ & Supplementary Information
This section answers frequently asked questions and provides additional information about the general implementation of the J1939 EV signal set, and supplementary information for the implementation of specific signals.
I have implemented the required signals, what’s next?
Once you have implemented all the J1939 messages specified in this section of the document, the next step is data validation. Please proceed with completing the validation scenarios listed below. These will ensure data from the vehicle is flowing correctly into MyGeotab. The scenarios must be completed with a GO9 device installed. Please work with your Geotab point of contact to ensure the GO device has the correct firmware version before executing the validation scenarios.
✱ NOTE: The validation scenarios listed below can be completed in any order
The validation scenarios to be completed are:
- A minimum of 5 km (preferably 15 km) of driving. This driving should include segments with combustion engine activity if the vehicle in question is a Plug-in Hybrid Electric Vehicle (PHEV).
- The minimum driving distance as stated above is a cumulative value, and therefore does not need to be completed in a single trip.
- A minimum of one (1) AC charging event where:
- The net gain in HV Battery SOC is at least 30%
- The end SOC value must be greater than 80%
- Not applicable if the EV only allows for DC charging.
- A minimum of one (1) DC Fast Charging event for 15 minutes.
Upon completion, please inform your Goetab point of contact (or a member from the EV Solutions Engineering team). Geotab will internally review the data and let you know if any changes need to be made or if the test procedure needs to be repeated.
What are the hardware and firmware requirements for J1939 EV?
From a telematics device perspective: A GO9 device with beta or stable release firmware is required to collect and interpret J1939 EV messages on a vehicle.
From a diagnostic port perspective: A standard 9-pin or 16-pin port is required. Custom ports pinouts will require a modified harness and will delay the time to completing the full integration. J1939 data needs to be read by the GO device either on pins 6 and 14, or on pins 3 and 11.
Where can I get more information about the GO device firmware?
The Firmware Product Guide contains information about firmware releases and the rollout process, LED lights, device beeps, listen only mode, odometer and seat belt logic, ignition detection logic, GPS precision, and more! It is recommended to read over this document so you better understand the functions and operation of the GO device.
What are the specifications and pinout of the GO9 device?
The specifications for the GO9 device are found in the GO9 support document. The GO9 device follows the standard OBDII pinout.
What is the data logging frequency?
All data collected by a GO device, regardless of whether or not it is J1939 EV data, is curve logged. The only exception to this is vehicle state of charge and signals that are “state” based such as ignition, seatbelt, etc. The curve logging algorithm decides which datapoints contain statistically significant information, and only sends those back to the database to avoid unnecessary data transmission overhead. The remaining datapoints are discarded prior to device data transmission. For more information, refer to the Geotab whitepaper on curve logging and a YouTube video of Geotab’s CEO explaining curve logic.
What are the minimum conditions for the GO device to recognize the vehicle as an EV and conforming to J1939 EV?
Geotab has incorporated a tagging mechanism in the GO device to identify different EVs on standard and proprietary CAN protocols. In order to correctly tag as an EV following the J1939 EV protocol, the GO device needs to see the PGNs and SPNs in the following table broadcast on CAN.
PGN | SPN | Description |
61584 | 5919 | High voltage battery voltage |
61584 | 5920 | High voltage battery current |
64706 | 7895 | Generic state of charge |
64706 | 7315 | Ignition |
64706 | 7898 | External energy source connection status. |
What CAN traffic must be present for the GO device to recognize and log driving and charging data?
This information will be useful during the testing phase of the J1939 EV implementation. For the GO device to log driving information (such as vehicle speed, energy consumption, etc.) the corresponding broadcast CAN traffic must indicate that the vehicle is in a “driving” state. This is done by setting the Ignition status to active, i.e. broadcasting PGN 64706, SPN 7315 = 1.
A similar concept applies to charging. The vehicle must be in a “charging” state in order for the GO device to log charging information (such as SOC, energy added, etc). Please see here for more information on how to implement vehicle charging status correctly.
What is the correct way to implement vehicle charging status?
The GO device firmware requires the following logic to distinguish between an AC and DC charge event:
- When vehicle is not charging, Set PGN 64706, SPN 7898 = 0
- When vehicle is charging (AC or DC), Set PGN 64706, SPN 7898 = 4
- For AC charging - Set PGN 61590, SPN 8207 = 1 (Not applicable if the EV only allows for DC charging.)
- For DC charging - Set PGN 64184, SPN 13171 = 1
What is the correct sign convention for HV battery current and EVSE1 AC RMS current?
The sign convention for HV battery current signal (PGN 61584, SPN 5920) for GO device compatibility follows what is specified in the J1939DA. The sign convention is as follows:
For HV battery current (PGN 61584, SPN 5920)
- Positive values denote energy flow entering the HV battery
- Negative values denote energy flow exiting the HV battery
For EVSE1 AC RMS Current (PGN 64212, SPN 12866)
How do I view the J1939EV data in MyGeotab?
Once you begin to implement J1939EV messages, you can also view the data on your MyGeotab database. This is encouraged so that you can verify the signals have been correctly implemented and all the data is correctly flowing into the Geotab ecosystem. Please follow the steps below to view the data in MyGeotab. For more information, refer to the EV Data Diagnostics and API User Guide.
1 | Log in to your database. |
2 | Navigate to Engine & Maintenance > Engine and Device… > Measurements from the navigation menu. |
3 | From the Options menu, select an appropriate date period and vehicle. |
4 | For Diagnostics, select the following:
|
5 | Click the Apply changes button to view engine measurements. Note: The data can also be downloaded in an Excel file by clicking the Report button and selecting Standard from the drop down menu. |
Why do I not see data in MyGeotab for HV Battery Current, when it is part of the required signals to implement?
Although the J1939 EV signal set requires the implementation of HV battery current and voltage signals, the diagnostics for HV battery voltage and power are presented on MyGeotab. This is because the GO device measures HV battery current and voltage, calculates power, and sends data to the database for voltage and power.
The HV battery current is a variable signal by nature and requires lots of data points to accurately represent the signal with curve logging. Sending HV battery voltage and power information to the database is more data-efficient. If you would like to see HV battery current from the vehicle in MyGeotab, you can set up a custom report where HV battery current is calculated.
The signal set does not include SLI battery voltage. Can this still be measured?
The SLI battery voltage parameter does not exist in the list of GO device supported PGNs and SPNs; however, the GO device voltage indicates the SLI battery voltage. To access this information, navigate to Engine & Maintenance > Engine and Device > Measurements. Then, for Diagnostics, select the Telematics device voltage parameter and click the Apply changes button to view the engine measurements.
What other J1939 SPNs are supported by the GO device?
A full list of all GO device supported J1939 SPNs can be found here.
What payloads are required when implementing transmission gear change?
The table below outlines the required payload for transmission gear change (PGN 61445, SPN 523).
✱ NOTE: The byte position is 4 in the payload.
Gear | Physical Value | Payload (PGN 61445, SPN 523) |
Park | 126 | FF-FF-FF-FB-FF-FF-FF-FF |
Reverse | -1 | FF-FF-FF-7C-FF-FF-FF-FF |
Neutral | 0 | FF-FF-FF-7D-FF-FF-FF-FF |
Forward | 1 | FF-FF-FF-7E-FF-FF-FF-FF |
Does the GO device send a J1939 request message for VIN? When does it do this?
After the first install, or after a device reset (unplug and replug), the GO device makes a J1939 VIN request shortly after ignition is turned on. VIN is a multi-frame CAN message and requires the use of a BAM (Broadcast Announcement Message). The table below demonstrates the transaction.
Time(s) | ID (Hex) | Direction | Payload | Description |
18EAFFFB | Tx from GO device | EC-FE-00 | Request the PGN for VIN (00-FE-EC) | |
xxECFFxx | Rx from ECU | 20-12-00-03-FF-EC-FE-00 | Broadcast Announcement Message (BAM). 00-12 is data length in hex, 03 number of frames, 00-FE-EC is the PGN to follow. | |
+0.05 | xxEBFFxx | Rx from ECU | 01-XX-XX-XX-XX-XX-XX-XX | Data Transfer (DT). Frame 1, VIN character 1-7. |
+0.05 | xxEBFFxx | Rx from ECU | 02-XX-XX-XX-XX-XX-XX-XX | Data Transfer (DT). Frame 2, VIN char 8-14. |
+0.05 | xxEBFFxx | Rx from ECU | 03-XX-XX-XX-2A-FF-FF-FF | Data Transfer (DT). Frame 3, VIN char 15-17, 2A is an ASCII “*” delimiter. |
For Seat Belt switch, why am I seeing the opposite values in MyGeotab to what I am sending in the message payload?
This pertains to PGN 57344 SPN 1856. The convention of buckled/unbuckled status in the GO device firmware and MyGeotab is opposite to the convention presented in the J1939DA.
In the J1939DA, the convention is:
- 0 = Unbuckled
- 1 = Buckled
However, in MyGeotab, the convention is:
- 1 = Unbuckled
- 0 = Buckled
- -1 = Unknown, this appears in MyGeotab at every ignition ON and ignition OFF
Therefore, when you send 0 in the message payload, it indicates an unbuckled status according to the J1939 standard, but displays as a 1 on MyGeotab. If you want to see a 0 in MyGeotab (buckled), you need to send a 1 in the message payload.
Optional: Expanded signal set
The PGNs & SPNs in the table below are also supported by the GO device. If you choose to implement them, you will see the corresponding data elements in MyGeotab. The full list of GO supported J1939 SPNs can be found here. Please contact your Geotab point of contact for more information.
PGN | SPN | SPN Name | Description of data | SPN length | Bit Resolution (If applicable) |
61443 | 91 | Accelerator pedal position 1 | The ratio of actual position of the analog engine speed/torque request input device (such as an accelerator pedal or throttle lever) to the maximum position of the input device. This parameter is intended for the primary accelerator control in an application. If an application has only one accelerator control, use SPN 91. For on-highway vehicles, this will typically be the operator’s accelerator pedal. Although it is used as an input to determine powertrain demand, it also provides anticipatory information to transmission and ASR algorithms about driver actions. In marine applications, this will typically be the operator’s throttle lever. If a low idle validation switch is used in conjunction with accelerator pedal position 1, use Accelerator Pedal Low Idle Switch 1, SPN 558. NOTE — See SPNs 29 and 974 for additional accelerator position parameters. SPN 28 is an additional diagnostic SPN for accelerator position. | 1 byte | 0.4 %/ bit |
61586 | 8075 | High Voltage Battery Highest Cell Temperature | The highest temperature level reported by any cell in the High Voltage Energy Storage System (or Pack 1 in systems with only one pack). If a single temperature sensor covers more than one cell, the value in this parameter is for the smallest group of cells measured. See SPN 8241 (HVESS Highest Cell Temperature Module Number) and SPN 8242 (HVESS Highest Cell Temperature Cell Number) for cell location information. | 2 bytes | 0.03125 °C/bit |
61586 | 8076 | High Voltage Battery Lowest Cell Temperature | The lowest temperature level reported by any cell in the High Voltage Energy Storage System (or Pack 1 in systems with only one pack). If a single temperature sensor covers more than one cell, the value in this parameter is for the smallest group of cells measured. See SPN 8243 (HVESS Lowest Cell Temperature Module Number) and SPN 8244 (HVESS Lowest Cell Temperature Cell Number) for cell location information. This parameter provides HVES system level information. If there are multiple packs in the system, then both individual pack messages (e.g. HVESP1, HVESP2 etc.) and system level messages (HVESS) may be required. | 2 bytes | 0.03125 °C/bit |
64505 | 8047 | Propulsion Motor Coolant Fan 1 Control Temperature | A temperature measured and reported by the device. It may be used for direct or remote (by another controller) control of the Fan 1. For example, this may be the temperature of the fluid flowing through the Fan 1, or some other temperature relating to the Fan 1 or controller. | 2 bytes | 0.03125 °C/bit |
64993 | 7853 | Air Conditioner Compressor Status | Signal which indicates if the Air Conditioner compressor is on or off. | 2 bits | 4 states/2 bit |
61589 | 9119 | High Voltage Battery Temperature | The temperature of High Voltage Energy Storage System (or Pack 1 in systems with only one pack). The value may be determined from a unique sensor specifically for this purpose, or by aggregating various temperature sensor readings within the system. This parameter provides HVES system level information. If there are multiple packs in the system, then both individual pack messages (e.g. HVESP1, HVESP2 etc.) and system level messages (HVESS) may be required. | 1 byte | 1 °C/bit |
61705 | 8234 | HVESS Thermal Management System Heater Status | The state of the High Voltage Energy Storage System (or Pack 1 in systems with only one pack) heater This parameter provides HVES system level information. If there are multiple packs in the system, then both individual pack messages (e.g. HVESP1, HVESP2 etc.) and System level messages (HVESS) may be required. 00b = Heater Off 01b = Heater On 10b = Error 11b = Not Available | 2 bits | 4 states/2 bit |
65279 | 8428 | Fuel Supply Estimated Remaining Distance | Estimated remaining distance based on existing fuel supply. | 2 bytes | 1 km/bit |
64933 | 3413, 3416, 3419, 3422, 3425, 3428, 3431, 3434, 3437, 3440. | Door open status for door 1 to 10 | Gives the door open status of doors 1 to 10 | 2 bits | N/A |
65258 | 180 | Trailer Weight | Total mass of freight-carrying vehicle designed to be pulled by truck, including the weight of the contents. | 2 bytes | 2 kg/bit |
65258 | 181 | Cargo Weight | The mass of freight carried. | 2 bytes | 2 kg/bit |
65136 | 1585 | Powered Vehicle Weight | Total mass imposed by the tires of the powered vehicle on the road surface. Does not include the trailer. | 2 bytes | 10 kg/bit |
65136 | 1760 | Gross Combination Vehicle Weight | The total weight of the truck and all attached trailers. | 2 bytes | 10 kg/bit |
65262 | 110 | Engine Coolant temperature | Temperature of liquid found in engine cooling system. | 1 byte | 1 °C/bit |
61585 | 5922 | Highest cell voltage | "The highest voltage level reported by any cell in the High Voltage Energy Storage System (or Pack 1 in systems with only one pack). If a single voltage sensor covers more than one cell, the value in this parameter is for the smallest group of cells measured. See SPN 8236 (HVESS Highest Cell Voltage Module Number ) and SPN 8237 (HVESS Highest Cell Voltage Cell Number) for cell location information. This parameter provides HVES system level information. If there are multiple packs in the system, then both individual pack messages (e.g. HVESP1, HVESP2 etc.) and system level messages (HVESS) may be required." | 2 bytes | 0.001 V/bit |
61585 | 5923 | Lowest cell voltage | "The lowest voltage level reported by any cell in the High Voltage Energy Storage System (or Pack 1 in systems with only one pack). If a single voltage sensor covers more than one cell, the value in this parameter is for the smallest group of cells measured. See SPN 8238 (HVESS Lowest Cell Voltage Module Number) and SPN 8239 (HVESS Lowest Cell Voltage Cell Number) for cell location information. This parameter provides HVES system level information. If there are multiple packs in the system, then both individual pack messages (e.g. HVESP1, HVESP2 etc.) and system level messages (HVESS) may be required." | 2 bytes | 0.001 V/bit |
65269 | 170 | Cab interior temperature | Temperature of air inside the part of the vehicle that encloses the driver and vehicle operating controls. | 2 bytes | 0.03125 °C/bit |
64605 | 15262 | HVESS Nominal Rated Capacity | "Per the HVES manufacturer, this is the manufacturer's nominal rated capacity of the High Voltage Energy Storage System (or Pack 1 in systems with only one pack). In a multipack system, this is the sum of all packs. This parameter provides HVES system level information. If there are multiple packs in the system, then both individual pack messages (e.g. HVESP1, HVESP2 etc.) and system level messages (HVESS) may be required." | 3 bytes | 0.001 kWh/bit |
64606 | 8121 | HVESS State of Health | "This signal represents the expected remaining ""Life"" of the High Voltage Energy Storage System (or Pack 1 in systems with only one pack), in percent. Battery life is a manufacturer-specific measure of how well the energy storage system is functioning relative to its nominal (rated) and end (failed) states. This value should begin at 100%, and end at 0% when “no” energy is able to be put in or taken out. “No” could be absolute zero, or it could be some rated value of the system. The pack supplier can develop their own algorithm to calculate this parameter, but in general it is a reverse Amp Hour Counter, reflecting the expected Amp Hours of energy throughput remaining in the Hybrid Battery. This parameter provides HVES system level information. If there are multiple packs in the system, then both individual pack messages (e.g. HVESP1, HVESP2 etc.) and system level messages (HVESS) may be required." | 1 byte | 0.4 %/bit |
