Project Version

015 ERS3 2.0

Document Type Date
IRS 21/08/2024

List of Tables
Table 1 - Modbus/TCP functions ...................................................................................................................................................... 8

References

[1] E. M. AB, "015 ERS3 Alarms Table," Stockholm, 2023.

[2] E. M. AB, "015 ERS3 IRS Modbus Address Reference Table," Stockholm, 2023.

Echandia Group AB Registered in Sweden

Karlbergs strand 4L, 171 73 Solna, Sweden Org. No: 556704-1529
www.echandiagroup.com VAT SE5567041529-01 Page 2 of 9
 Project Version
015 ERS3 2.0
Document Type Date
IRS 21/08/2024

1 System philosophy
The BV- and DNV-approved Echandia Battery System is designed for use in a marine environment.
Therefore, the demand for stable and robust communication is essential.
The standard communication interface is Modbus TCP, other interfaces may be available upon request.

Echandia Group AB Registered in Sweden

Karlbergs strand 4L, 171 73 Solna, Sweden Org. No: 556704-1529
www.echandiagroup.com VAT SE5567041529-01 Page 3 of 9
 Project Version
015 ERS3 2.0
Document Type Date
IRS 21/08/2024

2 General information and components

The BMS has an internal private network used for communication between its various components.
The parent system connects to the BMS via Modbus TCP.

2.1 Network topology

2.1.1 Internal network
The internal network is used for communication between BMS and the strings (SCU), E-LAN.

2.1.1.1 SCUs
All SCUs are connected to the BMS via E-LAN. A group of SCUs form a pack. The BMS controls SCUs based
on the pack they are associated with.

2.1.1.2 Packs
A pack is a group of SCUs, on the same HV bus, controlled together as a group by the BMS. The BMS is an
IPC responsible to coordinate all parts of the battery system.

2.1.2 Parent System Integration

The external network connects the BMS to the parent system via Modbus TCP.

2.1.3 HMI
The HMI is a screen located in the battery room used to display detailed BMS information and allows for
limited control of the system.

2.1.4 Remote Access

To allow for remote maintenance, collection of warranty data, and performance metrics. The E-BMS
system needs an internet connection through the maintenance network interface on the BMS IPC allowing
for the system to connect to the Echandia VPN.
Enabling and disabling connectivity is controlled through the Remote Access settings in the BMS HMI. The
connection is always only enabled for a limited time period that can be extended if needed. The network
the maintenance interface is connected to should preferably provide the system network settings with
the DHCP protocol, but static network settings can also be entered through the system's HMI.

2.1.4.1 Remote Access - Modes of operation

2.1.4.1.1 Metrics and warranty data mode
When this mode is enabled the BMS uploads historical metrics and data of the system to Echandia's cloud
hosted environment. This communication is only outbound and does not allow any incoming
communication. The outbound communication is done through a TLS connection to data retrieval host in
the Echandia domain and authentication is done with an installation-specific authentication token.
2.1.4.1.2 Remote maintenance mode
This mode cloud-hosted is possible for maintenance personnel at Echandia to access the system remotely.
Typical remote access scenarios are troubleshooting and system software upgrades. When this mode is
enabled the BMS sets up an encrypted tunnel to Echandia’s remote access gateway. Authentication to the
gateway is done with an installation-specific authentication token. The remote gateway can only be
accessed by Echandia service personnel with MFA. To access the BMS from the remote access gateway an
additional installation specific access token is needed.

Echandia Group AB Registered in Sweden

Karlbergs strand 4L, 171 73 Solna, Sweden Org. No: 556704-1529
www.echandiagroup.com VAT SE5567041529-01 Page 4 of 9
 Project Version
015 ERS3 2.0
Document Type Date
IRS 21/08/2024

2.1.5 Redundancy
An optional secondary BMS can be configured for redundancy. Both BMSs will be active and responding
in normal operation. The secondary BMS is acting as a failover and will only accept external commands if
the primary BMS is unavailable. A register flag is set to indicate which redundancy interface is operational
at a given time.

2.2 Cabling
2.2.1 RJ45 ethernet cable
Only fully screened S/FTP CAT6 cable shall be used. UTP cables shall not be used. Echandia does not
guarantee compatibility with CAT7 cables.

2.3 Hardware
2.3.1 Power supply
The system shall be supplied with a 24VDC supply that shall comply with BV and/or DNV regulations
unless stated otherwise in the product or project documentation. Intermittent power shortages shall be
avoided. If a power outage happens, the system shall need several seconds to fully reset and enter a safe
state.
The voltage on the BMS supply shall be 24VDC +/- 17% [20V – 28V].

2.3.2 BMS
The BMS software is running on a BV approved IPC with two network cards.

2.3.3 PLC type

Siemens PLC S7-1200 works as an interface between BMS and PMS.

Echandia Group AB Registered in Sweden

Karlbergs strand 4L, 171 73 Solna, Sweden Org. No: 556704-1529
www.echandiagroup.com VAT SE5567041529-01 Page 5 of 9
 Project Version
015 ERS3 2.0
Document Type Date
IRS 21/08/2024

3 Variables and communication

The BMS consists of multiple packs which is a group of strings (max 16 SCUs) connected to the same HV
bus. Each pack is controllable separately in the BMS system; operation control, alarms [1] and charging
control are done on a pack level. Communication with the BMS is on a pack configuration. Each pack has
an interface to the parent system acting as a separate entity.

3.1 General interface information

Upon startup or reboot of the BMS the Redundancy Flag parameter will be set to Not available, the parent
system must monitor the Redundancy flag register combined with the BMS Sync counter to ensure the
data provided is up to date. On link lost the register values will remain as last seen before the link was
lost. Values will return to normal when system is running in safe condition again, and Redundancy state
will be updated.
On a string level, a reboot or startup of a SCU will result in following the start-up mode sequence to reach
interlock state.
In case of a power loss to the SCU the string will disconnect and the BMS will raise a warning message
indicating lost SCU. All SCU specific registers will be as last seen before connection loss.
In case of a communication loss between a SCU and the BMS, the SCU will keep its most recent state for a
given time and the BMS system will raise a warning message indicating lost SCU. After this time period
the SCU will disconnect its contactors and return to the standby state. All SCU specific registers will be as
last seen before connection loss.

3.1.1 BMS TCP/IP interface

All communication with parent system is on the external network interface, a suggested setup is listed
below.

3.1.2 Addresses
The Echandia BMS system has a closed internal network infrastructure which is not exposed to parent
system.
The external interfaces of the system are:
- The PMS communication (Modbus) port, which has a static configurable IP to simplify
integration.
- Service communication interface, i.e., VPN (Configurable IP / DHCP)

If the system is configured with redundancy the above interfaces are duplicated in a second cabinet. The
interface contains parameters indicating which interface is primary at any given time.

3.2 Modbus TCP/IP interface

3.2.1 Connection
To establish connection with PLC’s Modbus TCP server, the client (parent system) must have the same
subnet mask configured above in the addresses section but a different IP.
The server will have the following configuration:
- Connection reference / Identifier: 1
- Port: 502

Echandia Group AB Registered in Sweden

Karlbergs strand 4L, 171 73 Solna, Sweden Org. No: 556704-1529
www.echandiagroup.com VAT SE5567041529-01 Page 6 of 9
 Project Version
015 ERS3 2.0
Document Type Date
IRS 21/08/2024

3.2.2 Data registers

Holding registers 16 bits (read/write) are used for sending commands from parent system to BMS
whereas input registers 16 bits (read) are used to send BMS status data back to parent system.

3.2.2.1 BMS control register

The information that should be written by the parent system to BMS has been organized into holding
registers, or more specifically, data is organized into the holding registers starting at 3001.
Where address 3001 and 3002 are allocated for Heartbeat Parent and Select SCU Detail respectively.
The parent system is responsible for incrementing the count in the Heartbeat Parent register to indicate
to the BMS the connection is working properly.
Select SCU detail [3002] is used to define which SCU specific register to be sent back to parent system
where last 8 bit is to define pack number and the first 8 bits is for which SCU in selected pack.
An example for that, if parent system sends: 0x0203 that means pack 2 and SCU 3.

3.2.2.2 Pack control register

Pack control register has address formula as Base Address [3001] + (P * 10) where P is pack number, for
example:
Pack control register (holding register)
Pack 1 – starts at 3011, ends at 3020.
Pack 2 – starts at 3021, ends at 3030.
Pack 3 – starts at 3031, ends at 3040.

3.2.2.3 BMS status register

The status information that is provided by the BMS to the Parent system has been organized into holding
registers, or more specifically, data is organized into the holding registers starting at 1001.
Where address 1001 and 1002 are allocated for BMS Sync counter and Redundancy State respectively.
The parent system is required to monitor the incrementing BMS Sync counter in order to detect if the link
is functioning.
The redundancy state indicates if this interface currently is functioning and in control, Not available here
indicates problems with the BMS link or internal errors. Primary indicates that this interface has control
and the BMS can be controlled on this link. Secondary indicates the redundant system has control and this
interface will only provide status, not act upon control register input.

3.2.2.4 Pack status register

Pack status register has address formula as Base Address [1036] + ((P-1) * 45) where P is pack number, for
example:
Pack status register (input register)
Pack 1 – starts at 1036, ends at 1080.
Pack 2 – starts at 1081, ends at 1125.
Pack 3 – starts at 1126, ends at 1170.
Pack 10 – starts at 1441, ends at 1485.

3.2.2.5 SCU detail register

For SCU specific register, the registers start at 4001 and end at 5825. The specific register is selected by
holding register 3002 mentioned above.

Echandia Group AB Registered in Sweden

Karlbergs strand 4L, 171 73 Solna, Sweden Org. No: 556704-1529
www.echandiagroup.com VAT SE5567041529-01 Page 7 of 9
 Project Version
015 ERS3 2.0
Document Type Date
IRS 21/08/2024

There are optional SCU’s individual status registers for each SCU that follows the formula Base Address
[44001] + ((S - 1) * 25) where S is SCU number,
SCU individual status register (input register)
SCU 1 – starts at 4001, ends at 4025.
SCU 2 – starts at 4026, ends at 4050.
SCU 3 – starts at 4051, ends at 4075.
Note; this SCU number is the sequence number for the whole system, not pack relative. As an example, in
a system where all packs have 6 SCUs, then SCU number 9 would correspond to the third SCU in the
second pack.

3.2.3 Modbus functions

The interface has been specified to use the following Modbus TCP functions code:

Table 1 - Modbus/TCP functions

Function Type Address Size Function

FC 03, FC 16, Control registers

Holding Register 3XXX
FC 23 Read/Write

Status registers
FC 03, FC 23 Holding Register 1XXX
Read

FC 03, FC 23 Holding Register 4XXX SCU Status registers Read

The complete Modbus register map can be found in [2].

Echandia Group AB Registered in Sweden

Karlbergs strand 4L, 171 73 Solna, Sweden Org. No: 556704-1529
www.echandiagroup.com VAT SE5567041529-01 Page 8 of 9
 Project Version
015 ERS3 2.0
Document Type Date
IRS 21/08/2024

4 Revision history
Revision Date and Signature Description
0.1 19/01/2023 K.D. Initial draft
0.2 23/05/2023 A.A. ERS3 draft
0.3 27/06/2023 A.A. Updates based on given commits from approval request
0.4 29/06/2023 A.A. Echandia’s template applied
0.5 12/07/2023 A.A. Minor changes based on internal feedback
0.6 03/08/2023 A.A. Operation stats removed as they are mentioned in functional
description document.
1.0 21/08/2023 A.A Official release of document
1.1 25/02/2024 K.D Updated appendix after DNV tests
2.0 21/08/2024 C.B. Updated modbus address ranges to ease integration and sequential
read. Update information regarding external networks.

4.1 Abbreviations and nomenclature

Term Meaning
IRS Interface Requirement Specification
BMS Battery Monitoring System
CMU Cell Monitoring Unit, Toshiba proprietary unit for module cell and temperature
monitoring
BMU Battery Monitoring Unit, Toshiba proprietary unit for string control
E-LAN Echandia’s private internal network
EMS Electric Management System, a control system that connects the battery system to
consumers and chargers
Parent system EMS or other control systems that are connected to the BMS.
System Unless stated otherwise, the BMS.
HV bus High Voltage bus
SOC State of Charge
SOH State of Health
TTG Time To Go

Echandia Group AB Registered in Sweden

Karlbergs strand 4L, 171 73 Solna, Sweden Org. No: 556704-1529
www.echandiagroup.com VAT SE5567041529-01 Page 9 of 9