Manual 1030 Model Acuity

Manual 1030 Model Acuity
Manual
Model 1030
Acuity ® Battery Monitoring System
Curtis Instruments, Inc.
200 Kisco Avenue
Mt. Kisco, NY 10549
www.curtisinstruments.com
Read Instructions Carefully!
Specifications are subject to change without notice.
© 2015 Curtis Instruments, Inc. ® Curtis is a registered trademark of Curtis Instruments, Inc.
© The design and appearance of the products depicted herein are the copyright of Curtis Instruments, Inc.
38442, Rev B 9/15
CONTENTS
CONTENTS
1. OVERVIEW ............................................................................. 1
2. INSTALLATION AND WIRING .......................................... 3
Mounting the module ......................................................... 3
Connecting B+, B-, and the temperature sensor .................. 4
Installing the current sensor ................................................ 4
CAN connections ............................................................... 5
3. ACU-Set software ........................................................... 6
Connecting the Acuity to the computer .............................. 6
Establishing Communication
between Acuity and computer ...................................... 7
Configuring the Acuity ....................................................... 8
Power prover ....................................................................... 9
Handling historical data .................................................... 10
Programming the Acuity ................................................... 12
4. CANopen COMMUNICATIONS ......................................... 13
Minimum state machine ................................................... 13
Baud rates ......................................................................... 13
Node addresses .................................................................. 13
Standard message identifiers .............................................. 14
NMT messages ................................................................. 14
Heartbeat messages ........................................................... 15
5. PDO COMMUNICATIONS ............................................... 16
6. SDO COMMUNICATIONS ................................................ 17
7. device parameter objects ...................................... 20
Definitions ........................................................................ 21
Configuring parameters .................................................... 22
Resetting the SoC ............................................................. 22
8. device monitor objects .......................................... 23
Historical records .............................................................. 23
Retrieving historical records .............................................. 26
9. SPECIFICATIONs ................................................................ 23
Curtis 1030 Acuity Manual, Rev. B
iii
FIGURES / TABLES
FIGURES
fig. 1: Curtis Acuity ............................................................................ 1
fig. 2: Mounting dimensions .............................................................. 3
fig. 3: Typical installation ................................................................... 4
.
TABLES
table 1: Communication profile objects ............................................ 19
table 2: Device parameter objects ...................................................... 20
table 3: Device monitor objects ......................................................... 23
table 4: Specifications ........................................................................ 28
iv
Curtis 1030 Acuity Manual, Rev. B
1 — OVERVIEW
1 overview
The Curtis Model 1030 Acuity ® Battery Monitoring System includes:
• The Model 1030 Curtis Acuity ® Module — 17668700-xxx.
• Acu-Set™ Software — 17668889-01Rxx.xx.
• CAN-to-USB Dongle — 17697USBCANI-01.
• Acuity Setup Harness — 17668357.
Fig. 1 Curtis Acuity ®
Battery Monitoring System.
The system mounts directly to an industrial vehicle lead acid battery and measures, records, and transmits battery performance data throughout the life of
the battery.
The Curtis Acuity is ideal for use in electric vehicles with applications
such as material handling, airport ground support, floor cleaning, light-on-road,
golf/utility, and aerial work platforms. Features include:
3 Highly accurate state-of-charge calculation that uses a weighted
average of ampere-hour counting and voltage under load
measurements.
3 Witness data that demonstrates the battery has been operated
within the conditions of its warranty.
3 Since Acuity is permanently attached to the battery, information
is collected consistently and accurately over the lifetime of the
battery, no matter how many times the battery is moved.
3 Data can used to optimize productivity of a battery fleet/vehicle.
3 CANbus allows simple system integration.
3 Installation is simple and non-invasive, with no need for special
hardware and no cutting of cables or drilling into the battery.
3 Integral real-time-clock allows date and time stamping of
significant events related to the battery or any vehicle component
of the CANbus.
3 CANbus isolation eliminates ground loops that can cause
component damage as well as data errors due to differences in
ground potentials among the nodes on the CANbus.
More Features +
Curtis 1030 Acuity Manual, Rev. B
1
1 — OVERVIEW
3 By measuring, recording, and communicating battery current,
voltage, temperature, and use-time, Acuity can compensate
for the effects of variations in load, duty cycle, and operating
temperature of any given application.
3 Calculates the percent of rated capacity remaining in the battery
as an indication of remaining battery life.
3 Curtis Acu-Set software, when installed on a computer connected
to an Acuity via a CAN-to-USB dongle, allows Acuity to be
configured to match the specific battery to which it is mounted.
3 Historical data can be uploaded to a PC.
3 Instantaneous battery performance data can be viewed on a PC
(Power Prover mode).
CANopen Convenience
The Acuity is CANopen compliant, responding to the standard NMT, PDO,
and SDO communications as well as the DS301-required identity and standard objects. The Curtis CANopen extensions allow additional features, such
as OEM and User default configurations.
The Acuity will receive a single SDO and respond with a single SDO.
These SDOs are fixed, simplifying the interface to a VCL-enabled device. All
programmable parameters and viewable values within the Acuity are accessible
via standard SDO transfer.
Battery information is displayed in real time on the Curtis enGage ® VII
or any other CAN-based display.
Familiarity with your Curtis Acuity system will help you install and operate it
properly. We encourage you to read this manual carefully. If you have questions,
please contact your local Curtis office.
2
Curtis 1030 Acuity Manual, Rev. B
2 — INSTALLATION & WIRING
2 Fig. 2 Mounting
INSTALLATION AND WIRING
The outline and dimensions for the 1030 Acuity are shown in Figure 2.
Perform the installation in an area that is well ventilated. Before installing the Acuity module, clean the battery, cables, and terminals.
MODEL 1030
DIMENSIONS mm
47
dimensions, Curtis 1030
Acuity.
54
SEE NOTE 2
26
NOTES:
1. Case & Current Sensor Housing
Material: Glass-filled PBT.
CURRENT SENSOR
Arrow shows direction
of discharge current
2. Current Sensor can accomodate
most cable sizes up to 4/0.
940±15
44
3. Current Sensor to be held to
battery cable by tie-wraps
(2 places).
4. Acid resistant tie-wraps should
be used to secure unit.
5. This unit not fitted with a CAN
termination resistor.
ALLOWABLE
MENISCUS
3mm MAX
179
30
125±15
605±15
POWER
CABLES
B+ : Red
B– : Black
960±15
CAN CONNECTOR
Pin 1 & Pin 2
TEMP SENSOR
CABLE
CAN CONNECTOR
PIN 1: CAN Hi — White Mates
with Molex 19038-0001.
PIN 2: CAN Low — Black mates
with Molex 19034-0005.
5/16" RING
TERMINALS
TYP 3X
Dimensions in millimeters
Curtis 1030 Acuity Manual, Rev. B
3
2 — INSTALLATION & WIRING
Mounting the Acuity module
Locate the Acuity module on the battery in such a way as to avoid damage to
the Acuity through normal battery/vehicle use. Use acid-resistant tie wraps to
secure the Acuity to the battery using the intercell connectors and the ribs that
are molded into the Acuity module; see Figure 3.
Fig. 3 Typical installation,
showing batteries with
Acuity installed.
Connecting B+, B–, and the temperature sensor
The Acuity’s B+, B–, and temperature sensor connections are made via 5/16"ring
terminals. Simply place the ring terminal over the battery stud/terminal and
then replace the washer and nut.
Installing the current sensor
The current sensor is polarity sensitive and must be properly oriented for the
Acuity to work correctly.
NEGATIVE
TERMINAL
– +
– +
–«+
– +
CURRENT
SENSOR
POSITIVE
TERMINAL
Either B+ or B– can be selected to pass through the current sensor, depending on the battery configuration and location of the current sensor.
Pass the end of the battery cable through the opening of the current
sensor, making sure that the marking on the current sensor is pointing in the
correct direction.
Insert a tie wrap into each of the slots in the current sensor and pull the
battery cable tight against the side of the current sensor in which the slots are
located.
4
Curtis 1030 Acuity Manual, Rev. B
2 — INSTALLATION & WIRING
CAN connections
The CAN connector is either a 2-pin Deutsch or two bullet-style connectors.
Note that the Deutsch connector is not acid resistant, and therefore if used
should be located at least one meter away from the battery.
The termination resistors on a cable should match the nominal impedance
of the cable. ISO 11898 requires a cable with a nominal impedance of 120 Ω;
therefore, you should use 120 Ω resistors for termination. If you place multiple
devices along the cable, only devices at the ends of the cable need termination.
You can specify whether the Acuity will include the 120 Ω termination resistor
(see Specifications, page 28).
Curtis 1030 Acuity Manual, Rev. B
5
3 — Acu-Set Software
3 acu-set software
Acu-Set software is license-based and will only run on the PC on which it is
originally installed. After the software is purchased, instructions will be emailed
from Curtis to define the download and activation procedure. Acu-Set is not
transferrable. If it is required that Acu-Set be loaded on a different computer,
a new license is required.
Connecting the Acuity to the computer
Make sure the Acuity is powered on before making the connections, then
follow these steps.
• Using the Peak USB-to-CAN dongle (Curtis p/n 17697USBCANI-01) and
mating harness (Curtis p/n 17668357):
Connect bullet connectors on Acuity to mating bullet connectors on harness
Connect sub-D connector on harness to mating sub-D
connector on Peak dongle.
• Install the dongle USB driver by inserting the CD into the computer and
following the instructions.
• Copy the PCANBasic.dll file for the Peak dongle from the dongle CD to
the folder where the Acu-Set software is executable (the folder where the .exe
file is located). The process is the same for the other brands of dongle: i.e., the
driver needs to be downloaded and the .dll file must be in the same folder as
the Acu-Set executable.
• Plug the dongle’s USB connector into the USB slot on the computer.
• From within the folder in which the Acu-Set files were saved, double-click
on the Acu-Set .exe file.
6
Curtis 1030 Acuity Manual, Rev. B
3 — Acu-Set Software
Establishing communication between Acuity and computer
Follow these steps to establish communication.
• Click on the COMM tab at the top of the Acu-Set screen.
”
• From the drop-down menu, select your CAN dongle:
Kvaser BlackBird WiFi
SYS TEC USB-CAN
Peak USB-CAN [default selection]
CANBlue II.
Note: If you are using the CANBlue Bluetooth dongle, select CANBlue
# Comm Port in the field below the dongle selection field.
• When the default Peak dongle is chosen and the baud rate and node ID match
the Acuity, Acu-Set will automatically display the Power Prover tab. If this did
not happen, review the Baud Rate and CAN Node ID settings.
The default baud rate is 125 kbps. If it is necessary to change this setting
to match your system, select the proper baud rate from the drop down menu: 100 kbps
125 kbps [default setting]
250 kbps
500 kbps
1000 kbps.
The default Node ID is 42. If it is necessary to change this value, enter
a value between 1 and 127 that is not already in use. The Node ID List shows
the Node IDs of all devices that are transmitting in that network at the selected
baud rate.
Curtis 1030 Acuity Manual, Rev. B
7
3 — Acu-Set Software
Configuring the Acuity
The Acuity needs to be configured to match the battery on which it is installed.
Begin by clicking on the Config tab at the top of the screen.
”
There are three methods of configuration.
1Click on the pull-down menu entitled Batt Type and select the
battery type that matches your battery. Enter ID (Batt ID),
voltage (Batt Rated Volt), capacity (Batt Rated Ah) and empty
point (Depth of Disch). Click Configure, then click Reset State of
Charge. Note: For depth of discharge, if desired empty point is
20% state-of-charge, enter 80. See explanation on page 21.
A dialog box will open to indicate that the Acuity has been
configured successfully. Click OK and the parameters of that
configuration will be loaded into the column on the left.
Note: The table on the right side of the screen is used for
internal purposes only.
2A configuration file that has been previously stored on the
computer can be retrieved and programmed into the Acuity.
Click on Load from File, select the appropriate configuration
file, and click Open. Configuration files use the extension .Acfg.
The parameters of that configuration will be loaded into
the right-hand column of the table on the left side of the
screen.
A dialog box will open to indicate that the Acuity has been
configured successfully. Click OK.
3Use the other fields in the Config tab.
Read Parameters Reads all parameters from the Acuity and
displays them into the column on the left of the table. This
feature allows the user to determine how an existing Acuity is
configured when newly connected to the computer.
Copy Values This function is used when copying parameters
from an Acuity to a computer. After the parameters are read
from the Acuity, the Copy Values button activates the copying of
8
Curtis 1030 Acuity Manual, Rev. B
3 — Acu-Set Software
the values on the left to the editable list on the right. The user
can then make any necessary changes before Save to File.
Clear Values This function removes all the values that were
entered by the user.
Save to File Saves the parameters that have been entered into
the editable list on the right.
Reset State-of-Charge Resets that value in the Acuity.
Update Time & Date Allows the user to set the time and date
of the real-time clock in the Acuity.
Power Prover (viewing & recording instantaneous data)
The Power Prover screen allows the user to view live data being transmitted
from the Acuity and to record that data on the host computer.
”
The Power Prover screen contains the following functions.
Select Scale Two pull-down menus allow you to select the voltage scale
and the current scale to be displayed on the computer.
Select Data Logging Rate The rate at which data is recorded to a file on the
computer can be selected using the drop-down menu. It is set in multiples of
PDO1 messages. The PDO1 transmission rate is 100 ms by default. It can be
reset using a CAN object.
Start Data Logging Begins storing data that is received from the Acuity’s measurements into a file on the computer, at the rate set by Select Data Logging Rate.
Reset AHr Counters Resets the Ampere Hour counters to zero. “D” represents
Ampere Hours Discharged, and “C” represents Ampere Hours Charged.
Battery ID This is an identifier unique to that Acuity and therefore to that
battery.
Time-of-Day Time of day as reported by the host computer.
Curtis 1030 Acuity Manual, Rev. B
9
3 — Acu-Set Software
Handling historical data
The Historical Data screen allows the user to retrieve historical data from the
Acuity.
”
Four buttons near the top allow the user to handle the historical data.
Load History From Acuity This
function retrieves data records from the memory
of the Acuity. The number of records and the unique identifier of the Acuity
(and this battery) are displayed. There are three ways to view the data, each
with its own subscreen.
1 View Historical Data Displays the raw data for each Acuity parameter in
tabular form. The battery parameters plotted using Select Parameters to Plot are:
State of Charge
Temperature
Ah Delivered / Returned
Percent Ah Returned
Estimated Ah Capacity.
2 Battery Cycles History Displays a graphical representation of the battery
history data. Slide bars help select specific ranges of data to view and simplify
the identification of measurements of particular interest, such as when the state
of charge has fallen below 20%.
3 Battery Current Profile Displays a bargraph showing the ranges over which
the ampere hours were consumed.
Examples of these three data displays are shown on the next page.
10
Curtis 1030 Acuity Manual, Rev. B
1 View Historical Data
2 Battery Cycles History
3 Battery Current Profile
Curtis 1030 Acuity Manual, Rev. B
11
Here are the remaining buttons on the Historical Data screen.
Load History From File Retrieves data records previously stored in the computer
and displays the data in tabular form. The file format extension is .*AHR.
Save History To File Stores
data records from Acuity’s memory to a file on the
computer in .ahr format.
Update History File Updates
stored history file with new data. This function also
provides an option for creating a backup for the stored history file before updating.
Programming the Acuity
The Program screen is used to re-program the Acuity with updated firmware.
”
Open Hex File Retrieves
Program Downloads
12
the hex file from the computer’s folder.
the file to the Acuity.
Curtis 1030 Acuity Manual, Rev. B
4 — CANopen COMMUNICATIONS
4 canopen communicationS
The Acuity adheres to the industry standard CANopen communication protocol and thus will easily connect into many CAN systems, including those
using the Curtis AC and Vehicle System controllers (1234/36/38, 1298, 1310,
and enGage VII). Any CANopen-compatible master can be programmed to
control the Acuity.
Minimum state machine
The Acuity will run the CANopen minimum state machine as defined by CiA.
The CANopen minimum state machine has four defined states: Initialization,
Pre-Operational, Operational, and Stopped.
Power-On
Reset
Reset
Module
Initialization
Reset
Communication
Transmit
Boot-up
Pre-Operational
Stopped
Operational
When the Acuity powers up, it goes to the Initialization state; this is also
known as the Boot-up state. No CAN communications from the Acuity are
transmitted in this state although the Acuity listens to the CANbus. When the
Acuity has completed its startup and self-tests, it issues an initialization heartbeat message and automatically goes to the Pre-Operational state and the to the
Operational state.
In the Operational state, the Acuity will start sending PDOs and process
all other necessary CANopen messages.
Baud rates
The Acuity will run at one of five selectable baud rates: 125 kbps, 250 kbps,
500 kbps, 800 kbps, and 1 Mbps. Rates below 125 kbps are not supported.
The baud rate can be changed by an SDO. Changes in the baud rate
require an NMT reset to make the new rate active.
Node addresses
The node address of the kbps can be 1 to 127 and is used by CANopen to
route messages to the Acuity and to denote messages from the Acuity. The node
Curtis 1030 Acuity Manual, Rev. B
13
4 — CANopen COMMUNICATIONS
address is part of the COB-ID and therefore also plays a part in message priority
and bus arbitration.
Changes to the node address require an NMT reset or power-cycle.
Standard message identifiers
The Acuity will produce—and respond to—the standard message types with
the following CANopen identifiers.
Message Type
Message Identifier
NMT
EMERGENCY
PDO-MISO
PDO-MOSI
SDO-MISO
SDO-MOSI
HEARTBEAT
0000 – 00hXx
0001 – 01hXx
0011 – 03hXx
0100 – 04hXx
1011 – 0BhXx
1100 – 0ChXx
1110 – 0EhXx
The 11-bit identification field is a fixed part of the CANopen specification
called the Communication OBject IDentification (COB-ID). This field is used
for arbitration on the bus. The COB-ID with the lowest value gets priority and
wins arbitration. Consequently, NMT messages have the highest priority of the
standard message types, and the heartbeat has the lowest priority.
The standard organization of the COB-ID puts the message type in the
upper four bits, and the Node ID in the bottom seven bits:
11
10
9
8
Message Type
7
6
5
4
3
2
1
Node ID
NMT messages
NMT (Network Management Transmission) messages are the highest priority
message available. The NMT message puts the Acuity into one of the four defined
states. These messages have 1 byte of data sent by the master; the slave does
not respond with any data to an NMT. The Acuity state value is transmitted
with each heartbeat message.
Value
00h
04h
05h
7Fh
14
State
Initialization (or “boot-up”)
StoppedXx
OperationalXx
Pre-OperationalXx
Curtis 1030 Acuity Manual, Rev. B
4 — CANopen COMMUNICATIONS
The NMT message identifier consists of the standard message type (NMT)
in the top four bits; the bottom seven bits must be set to zero.
The first data byte of the NMT command is the command specifier:
Value
01h
02h
80h
81h
82h
Command Specifier
Enter the Operational state
Enter the Stopped stateXx
Enter the Pre-Operational stateXx
Reset Acuity (warm boot)Xx
Reset the CANbusXx
The second byte of the NMT command defines whether this NMT is for
all slaves on the bus (data byte = 00h) or for a specific node (data byte = Node
ID of the Acuity).
Heartbeat messages
The heartbeat message is a very low priority message, periodically sent by each
slave device on the bus. The heartbeat message has a single byte of data and
requires no response. Once the Acuity is in the Pre-Operational state, the next
heartbeat will be issued and will continue until communication is stopped.
The heartbeat message has only one data byte. The top bit is reserved and
should be set to zero. The bottom 7 bits hold the current NMT device state as
defined previously.
Curtis 1030 Acuity Manual, Rev. B
15
5 — PDO COMMUNICATIONS
5 PDO communicationS
The Curtis Acuity is easily controlled and monitored through two fixed communication packets. Each data packet contains 8 bytes. CANopen calls these
packets Process Data Objects (PDOs). PDO messages have a medium priority.
The PDO communication packets conserve bus bandwidth by bundling
the values of a group of objects into a single message. The content of these
PDOs is fixed, thus simplifying the interface.
The Acuity transmits PDO1, PDO2, and PDO4 continuously. By default, PDO1 is sent every 100 ms, PDO2 is sent every 5 seconds, and PDO4 is
sent every second. PDO1 and PDO2 transmit periods are configurable using
a CAN object.
PDO1
Byte 1
Byte 2
Byte 3
Byte 4
Byte 5
Byte 6
Byte 7
Byte 8
BatteryBatteryBatteryBatteryTemper-Temper-
Not Used SoC
VoltageVoltageCurrentCurrent ature ature
LSBMSBLSBMSBLSBMSB
Battery Voltage Unsigned
16-bit integer. Resolution is hundredths of volts.
Example: A value of 30000 equals 300.00 V.
Battery Current Signed
16-bit integer. Positive value represents current coming
out of battery (discharge). Units are in tenths of amperes.
Example: A value of +3456 equals 345.6 A of discharge current.
Temperature Signed
16-bit integer. Units are in hundredths of degrees Celcius.
Example: A value of 5500 equals 55.00°C.
SoC (State of Charge) Unsigned
8-bit integer. Range is 0 –100%.
PDO2
Byte 1
Byte 2
Byte 3
Byte 4
Byte 5
Byte 6
Byte 7
Byte 8
HistoricalHistoricalHistoricalHistoricalHistoricalHistoricalHistorical Historical
DischargeDischargeDischargeDischarge Charge Charge Charge Charge
Ah LSB
Ah
Ah
Ah MSB Ah LSB
Ah
Ah
Ah MSB
PDO4
16
Byte 1
Byte 2
Seconds Minutes
Byte 3
Hours
Byte 4
Day
Byte 5
Byte 6
Byte 7
Byte 8
Month
Year [Reserved][Reserved]
Curtis 1030 Acuity Manual, Rev. B
6 — SDO COMMUNICATIONS
6 SDO communicationS
CANopen uses Service Data Objects (SDOs) to change and view all internal
parameters, or “objects.” The SDO is an 8-byte packet that contains the address
and sub-address of the parameter in question, whether to read or write that
parameter, and the parameter data (if it is a write command). SDOs are sent
infrequently and have a low priority on the CANbus.
SDOs are designed for sporadic and occasional use during normal runtime operation. There are two types of SDOs: expedited and block transfer.
The Acuity does not support large file uploads or downloads (using the block
transfer), so all SDOs in this specification are expedited SDOs.
The SDOs in the Acuity are used to set up and input battery-specific
parameters. They are also used to retrieve basic information (such as version
or battery-specific data).
SDO Master Request (SDO-MOSI)
An SDO transfer always starts with a request message from the master. Each
SDO request message consists of one control byte, a two-byte CAN Object
index, a one-byte CAN Object sub-index, and up to 4 bytes of valid data. This
format is CANopen compliant.
SDO-MOSI (received from the system master)
Byte 1
Byte 2
Byte 3
Byte 4
Byte 5
Byte 6
Byte 7
Byte 8
Control CAN ObjectSub-index
DataDataData Data
Index
The first data byte contains R/W message control information.
Action
Read
Write
Byte 1
Value
42h
22h
The next two data bytes hold the CAN Object index. The least significant byte
of the index appears first, in byte 2, and the most significant byte appears in byte 3.
For example, if the index is 3021h, byte 2 holds the 21h and byte 3 holds the 30h.
Data byte 4 holds the CAN Object sub-index. When there is only one instance
of a parameter or value type, this value is 0. If there are several related parameters
or values, the sub-index is used.
The last four data bytes hold the data that is to be transferred. In the case of a
single-byte transfer, the data is placed into data byte 5, with bytes 6 through 8 being
undefined (set to 0). In the case of a 16-bit transfer, the lower 8 bits appear in data
byte 5 and the upper 8 bits appear in data byte 6; bytes 7 and 8 are undefined (set
to 0). The case of a 32-bit transfer follows the same strategy, with the least significant byte placed in data byte 5 and the most significant byte placed in data byte 8.
Curtis 1030 Acuity Manual, Rev. B
17
6 — SDO COMMUNICATIONS
SDO Response (SDO-MISO)
An SDO request is always acknowledged with a response message from the
Acuity. The Acuity can issue two kinds of response messages: a normal response
or, in case of an error in the request SDO, an Abort SDO Transfer message.
SDO-MISO (sent by the Acuity in response to the system master)
Byte 1
Control
Byte 2
Byte 3
Byte 4
CAN Object
Sub-index
Index
Byte 5
Byte 6
Byte 7
Byte 8
Data: either the requested Read values,
or the actual Write values, or an error code
The first data byte of the response contains an acknowledge code, which
depends on the type of transfer that was initially requested.
Action
Read Response
Write Acknowledge
Abort SDO
Byte 1
Value
40h
60h
80h
Data bytes 2, 3, and 4 hold the CAN Object index and sub-index of the
request SDO.
If the SDO was a read command (a request for data from the Acuity),
data bytes 5 through 8 will be filled with the requested values, with the least
significant byte is data byte 5 and the next least significant in byte 6 and so
forth. All unused bytes are set to 0.
If the SDO was a write command, data bytes 5 through 8 will return back
the actual value written in bytes 5 – 8. In this way, if the Acuity needs to limit or
round-down the SDO write request, the master will know—because the return
value will be different than the sent value.
If the SDO-MOSI did not properly read or tried to access a parameter
improperly, an Abort SDO Transfer will be sent. Data bytes 5 through 8 will
be filled with a 32-bit error code:
06020000h = Object does not exist
06010002h = Attempt to write to a read only object.
Types of SDO objects
There are three types of SDO objects: Communications Profile Objects (address
range 1000h), Device Parameter Objects (address range 5100h), and Device
Monitor Objects (address range 5200h). Communications Profile Objects are
described in this section; Device Parameter Objects and Device Monitor Objects
have sections of their own. The following definitions apply to all the objects.
Access RO = Read Only access. RW = Read/Write access.
Index The CAN address that is used to access this object.
Sub-index Some objects have several associated values. In these
a sub-index is used to access each component of the object.
18
cases,
Curtis 1030 Acuity Manual, Rev. B
6 — SDO COMMUNICATIONS
COMMUNICATION PROFILE OBJECTS
The objects found in the 1000h CAN Object address range are shown below
in Table 1.
Table 1 Communication Profile Objects
indexsub-indexaccess
byte 5 byte 6byte 7byte 8description
1000h00hRO00 00Device Type.
1001h
00h RO
0
0
0
0
Error Register.
1008h00hRO10 30Model Number.
Four ascii characters; = 1030.
1009h00hRO00 01Hardware Version.
Four ascii characters.
100Ah00hRO00 01Software Version.
Four ascii characters.
101Bh00hRO50 00Identity Object.
Number of entries = 5.
01h RO 49h43h 00h00h Identity Object.
Vendor ID = 00004349h.
02hRO10 30Identity Object.
Model Number; four ascii characters.
03hRO00 01Identity Object.
Model Number sequential code;
Four ascii characters.
04hRO00 00Identity Object.
Serial Number.
Curtis 1030 Acuity Manual, Rev. B
19
7 — Device Parameter Objects
7 DEVICE PARAMETER OBJECTS
SDOs can be used to set up battery-specific parameters such as battery system
voltage and rated capacity. They can also be used to set up battery operation
related parameters such battery depth of discharge, charge full voltage, etc.
The objects found in the 5100h CAN Object address range are shown in
Table 2. Definitions follow the table.
Table 2 Device Parameter Objects
indexsub-indexaccess
5100h
byte 5 byte 6byte 7byte 8description
00h
RW
LSB
MSB
‘B’
‘V’
Battery Voltage. 16-bit value. Keyword: BV
5101h
00h RW
LSB
MSB
‘A’
‘h’
Manufacturer Ah Rating, at 5hr or 6hr.
Keyword: Ah.
5102h
00h
RW
LSB
MSB
‘T’
‘y’
Battery Profile parameters.
Keyword: Ty.
5103h
00h
RW
#
#
#
#
#### = Battery ID bytes 12..9.
01h
RW
#
#
#
#
#### = Battery ID bytes 8..5.
02h
RW
#
#
#
#
#### = Battery ID bytes 4..1.
5105h
00h
RW
value
‘D’
‘O’
‘D’
Depth of Discharge.
5106h
00h
RW
#1
#2
‘C’
‘E’
#1 = Charge Efficiency at high rates.
#2 = Charge Efficiency at low rates.
5107h
00h
RW
LSB
MSB
‘C’
‘F’
Charge Full, in mVPC.
5108h
00h
RW
LSB
MSB
‘S’
‘O’
Current Sensor Offset, in mA.
5109h
00..11h
RW
Custom discharge parameters; see Definitions.
510Ah
00h
RW BC_LthBC_Hth ‘B’
‘C’
Battery Cycle Thresholds, low and high.
Range 0 –100.
510Bh
00h
RW
HRint
‘H’
‘R’
‘I’
Historical Record store interval; range 0 –3.
0=1/8C, 1=1/16C, 2=1/24C, 3=1/32C.
510Ch
00h
RW
CAN
‘C’
‘P’
‘L’
CAN protocol for V.I.T. time; range 0 –2.
Prcl
0=CANopen PDO. 1=J1939 proprietary.
2=3100R.
5111h
00..15
RW
0
0
0
0
Customer notes. Total of 64 bytes.
Addressable 4 bytes at a time, using
sub-indexes 1–15.
20
5112h
00h
RW
pdo1 pdo2 heartB ‘F’
PDO1, PDO2, and Heartbeat Tx frequency.
Resolution 100 ms. Value of 0 disables PDO.
5113h
00h
RW
‘R’
‘n’
‘g’
#
Sets binned Ah range. For low range, set
Byte8 to 0h. For high range, set Byte8 to 1h.
5114h
00h
RW
sec
min
hour
‘T’
Time of day.
01h
RW
day
month year
‘D’
Date.
02h
RW
DoW
‘W’
Day of week. (Sunday = 1)
0
0
Curtis 1030 Acuity Manual, Rev. B
7 — Device Parameter Objects
Table 2 Device Parameter Objects, cont’d
indexsub-indexaccess
5115h
00h
RW
byte 5 byte 6byte 7byte 8description
CAL
‘C’
‘T’
‘D’
5116h
00h
RW CapTC CapTC Chg
‘c’
_H
_C
TC
Calibrate time of day.
Capacity Temp Coefficient, hot and cold.
Resolution 0.1% per °C.
Charger Full Temp Coefficient,
resolution 0.1 mV per °C.
Definitions
Battery Voltage (5100h) Battery
system voltage for the application.
Battery Profile Parameters (5102h) Selects
a battery discharge profile from
the existing battery discharge profiles, including:
0:
1:
2:
3:
4:
5:
6:
7:
256:
257:
512:
65534:
Flooded, Enersys E85
Flooded, Enersys E100
Flooded, Enersys E110
Flooded, Enersys E125
Flooded, Enersys E140
Flooded, Enersys E155
Flooded, Trojan T105
Flooded, Trojan T890
AGM, US Battery AGM-185
AGM, Discovery EVGC8A-A
Gel, MK Batteries M24
Custom parameters.
Battery ID (5103h) Battery
can be assigned an identification number
consisting of up 12 characters.
Depth of Discharge (DoD) (5105h) The DoD value scales the SoC displayed.
Example 1: When DoD=80, the unit will report 0% SoC when 20% is left.
Example 2: When DoD=100, the unit will report 0% SoC when 0% is left.
The factory default is 80.
Charge Efficiency (5106h) The
range for this parameter is 0 –100.
A setting of 100 means 100% of the energy put in goes into charging,
and none is wasted.
Byte 5 Charge efficiency at higher charge rates; factory default=95.
Byte 6 Charge efficiency at lower charge rates; factory default=100.
High and low rates are determined by the Ampere-Hour Law.
Custom discharge parameters (5109h) If the battery discharge profile for the
battery used in the application is not available, enter 65534 (Custom
parameters) in 5102h and then create a custom discharge profile in 5109h.
Curtis 1030 Acuity Manual, Rev. B
21
7 — Device Parameter Objects
Battery Cycle Low and High Thresholds (BC_LTh, BC_HTh) (510Ah) Battery discharge
cycles in any application are irregular. BC_LTh and BC_HTh set thresholds
to define a battery cycle. The Acuity increments the battery cycle if the
battery’s SoC drops below BC_LTh and then rises about BC_HTh.
Historical Record Store Interval (HRint) (510Bh) This
parameter defines the fraction
of the rated capacity (discharged or charged) at which the historical record
is stored. Historical record storage can be set at 1/8th, 1/16th, 1/24th, or
1/32nd of rated capacity C.
Configuring parameters
The Device Parameter Objects can be used to configure the Acuity parameters
for the application battery.
Most configurable parameters require a keyword to be sent along with
the value to be changed. Keywords consist of one or more ASCII characters.
Letters are case sensitive. To permanently store configurable parameters into
non-volatile memory, a Store command (keyword STOR) needs to be sent.
The timeout between setting the parameters and sending the Store command
is 15 seconds.
indexsub-indexaccess
51FFh
00h
WO
byte 5 byte 6byte 7byte 8description
‘S’
‘T’
‘O’
‘R’
Store configuration parameters.
Example:
indexsub-indexaccess
byte 5 byte 6byte 7byte 8description
5100h
00h
RW
0x30
0
‘B’
‘V’
Configures the unit for a 48V battery.
5101h
00h
RW
00h
02h
‘A’
‘h’
Configures the unit to 512 Ahr.
51FFh
00h
WO
‘S’
‘T’
‘O’
‘R’
Causes these new parameters to
be permanently stored in non-volatile
memory.
Resetting the SoC
The following object is used to reset the SoC of the battery to 100%.
indexsub-indexaccess
byte 5 byte 6byte 7byte 8description
4000h
00h
WO
‘R’
‘S’
‘T’
0
22
Resets state of charge to 100%.
Byte 8 is a zero.
Curtis 1030 Acuity Manual, Rev. B
8 — Device Monitor Objects
8 DEVICE MONITOR OBJECTS
The Device Monitor Objects are found in the 5200h CAN Object address
range, as shown in Table 3.
The Acuity monitors and records various battery parameters. To retrieve
battery data from the Acuity, you can use either PDOs or the objects in Table 3.
Table 3 Device Monitor Objects
indexsub-indexaccess
byte 5
byte 6byte 7byte 8description
5200h00hRO Voltage.
5201h
00h RO
Current.
5202h
00h
RO
Temperature.
5203h
00h
RO
SoC.
5204h
00h
RO
Historical Ah Discharge.
5205h
00h
RO
Historical Ah Charge.
5209h
00...9h
RO
Binned Ah.
520Ah
00h
RO RmAh_lsbRmAh_msb RAh_LSB RAh_MSB
Resettable Ah counter, Discharge.
520Bh
00h
RO RmAh_lsbRmAh_msb RAh_LSB RAh_MSB
Resettable Ah counter, Charge.
5214h
00h
RO EBC_LSB EBC_MSB
Estimated battery capacity.
Binned Ah (5209h) There
are ten ranges of discharge rates. Each sub-index
(00–09h) holds the number of Ah discharged at that rate.
Historical records
A historical record is generated when one of these four events occurs:
• A given number of Ampere-hours have been drawn from the battery
• A battery cycle has completed
• The battery charger has been removed
• The unit has been disconnected from the battery.
In a typical application, the Acuity will generate 15 to 20 historical records per
day. The historical records are stored in the Acuity’s non-volatile memory and
can be read through the CAN interface.
The following three objects are used to read historical record data.
indexsub-indexaccess byte 5 byte 6byte 7byte 8description
5300h
00..15h
RO
LSB MSB
0
0
HIstorical record request.
Bytes 6+5 = record number.
Sub-index = index to 4 bytes within record.
5301h
Number of records saved; 16-bit number.
00h RO
LSB
MSB
0
0
5302h
00h
RO
LSB MSB
0
0
Bytes 6–5 battery cycle number. Returns
historical record index.
Curtis 1030 Acuity Manual, Rev. B
23
8 — Device Monitor Objects
The Acuity can store up to 64,000 historical records. Each record in 64
bytes long. Record data is retrieved 4 bytes at a time. Allocation of parameter
bytes within each historical record is as follows.
sub-indexbyte
24
description
00h
byte 0
Runtime counter LSB (seconds).
00h
byte 1 Runtime counter LSB.
00h
byte 2
Runtime counter Byte 3.
00h
byte 3
Runtime counter MSB.
01h
byte 4
Historical Ah discharge LSB.
01h
byte 5
Historical Ah discharge Byte 2.
01h
byte 6
Historical Ah discharge MSB.
01h
byte 7
Historical Ah charge LSB.
02h
byte 8
Historical Ah charge Byte 2.
02h
byte 9
Historical Ah charge MSB.
02h
byte 10 Highest battery voltage measured during this interval (LSB).
02h
byte 11 Highest battery voltage measured during this interval (MSB).
03h
byte 12 Lowest battery voltage measured during this interval (LSB).
03h
byte 13 Lowest battery voltage measured during this interval (MSB).
03h
byte 14 Current measured at highest voltage (signed byte, units of 10 A).
03h
byte 15 Current measured at lowest voltage (signed byte, units of 10 A).
04h
byte 16 Highest temperature measured (signed byte, -40°C to 85°C).
04h
byte 17 Lowest temperature measured (signed byte, -40°C to 85°C).
04h
byte 18 Highest SoC during this interval.
04h
byte 19 Lowest SoC during this interval.
06h
byte 24 Estimated remaining Ampere Hours at the 6 hour rate.
06h
byte 25 Flags_1. See explanation in chart below.
06h
byte 26 Highest 1 second Avg Battery Voltage (LSB).
06h
byte 27 Highest 1 second Avg Battery Voltage (MSB).
07h
byte 28 Lowest 1 second Avg Battery Voltage (LSB).
07h
byte 29 Lowest 1 second Avg Battery Voltage (MSB).
07h
byte 30 1 second Avg Current measured at highest Avg Voltage.
07h
byte 31 1 second Avg Current measured at lowest Avg Voltage.
08h
byte 32 Activity_TimerD (LSB).
08h
byte 33 Activity_TimerD.
Curtis 1030 Acuity Manual, Rev. B
8 — Device Monitor Objects
sub-indexbyte
description
08h
byte 34 Activity_TimerD.
08h
byte 35 Activity_TimerD (MSB).
09h
byte 36 Seconds (time and date historical record was stored).
09h
byte 37 Minutes.
09h
byte 38 Hours.
09h
byte 39 Day.
10h
byte 40 Month.
10h
byte 41 Year.
10h
byte 42 Event dependent; see Byte 42–51 chart below.
10h
byte 43 Event dependent; see Byte 42–51 chart below.
11h
byte 44 Event dependent; see Byte 42–51 chart below.
11h
byte 45 Event dependent; see Byte 42–51 chart below.
11h
byte 46 Event dependent; see Byte 42–51 chart below.
11h
byte 47 Event dependent; see Byte 42–51 chart below.
12h
byte 48 Event dependent; see Byte 42–51 chart below.
12h
byte 49 Event dependent; see Byte 42–51 chart below.
12h
byte 50 Event dependent; see Byte 42–51 chart below.
12h
byte 51 Event dependent; see Byte 42–51 chart below.
byte 52– [not used]
64.
The type of event is recorded in historical record Byte 25 Flags_1. The bit
assignment for the flag is as follows.
bytebit
assignment
byte 25
bit 0
0 = lowest SoC occurred before highest SoC.
bit 1
0 = current resolution in 10 A units. 1 = current resolution in 1 A units.
bit 2
0 = lowest temperature occurred before highest temperature.
bit 3
0 = lowest Avg temperature occurred before highest Avg temperature.
bit 4
0 = lowest voltage occurred before highest voltage.
bit 5
1 = end of charge event.
bit 6
1 = power up event.
bit 7
0 = battery cycle event.
Curtis 1030 Acuity Manual, Rev. B
25
8 — Device Monitor Objects
The data recorded per the events in Bytes 42 – 51 is as follows.
battery cycle event
bytedescription
byte 42
end of charge
power down
Battery cycle number (LSB).
EoC_V_LSB PowerDown_sec
byte 43
Battery cycle number (MSB).
EoC_V_MSB
_min
byte 44
Total Ah charge for battery cycle (LSB).
EoC_I_LSB
_hour
byte 45
Total Ah charge for battery cycle (MSB).
EoC_I_MSB PowerDown_Day
byte 46
Total Ah discharge for battery cycle (LSB).
[not used]
_Month
byte 47
Total Ah discharge for battery cycle (MSB).
[not used]
_Year
byte 48
Max temperature for battery cycle.
[not used]
[not used]
byte 49
Min temperature for battery cycle.
[not used]
[not used]
byte 50
5Hr rate capacity available (LSB).
[not used]
[not used]
byte 51
5Hr rate capacity available (MSB).
[not used]
[not used]
Retrieving historical records
Historical records are generated for four different events (see page 23). To find
the precise historical data location where the data cycle has been recorded, use
the following steps. This way data for any cycle number can be retrieved without
a search through all the historical records. The retrieval starts with a request
to 5302h to find the record number. (See also, chart at bottom of page 23.)
indexsub-indexaccess
5302h
00h
RO
byte 5
Cycle number
(LSB)
byte 6byte 7byte 8description
Cycle number
(MSB)
0
0
Read historical record.
The Acuity response to this request is as follows.
Byte 1
Byte 2
Byte 3
Byte 4
Byte 5
Byte 6
Byte 7
40h02h53h00h
Historical
Historical
0
Record
Record
Number
Number
(LSB)
(MSB)
Byte 8
0
After the historic record number is received, specific details for that record can
be retrieved, using the SDO object Historic Record Request (5300h), along
with the appropriate sub-index.
indexsub-indexaccess
5300h 00..15h
26
RO
byte 5
byte 6byte 7byte 8description
Record number Record number
(LSB)
(MSB)
0
0
Read historical record.
Curtis 1030 Acuity Manual, Rev. B
8 — Device Monitor Objects
The data is retrieved 4 bytes at a time. The sub-index points to a 4-byte
block within the record. Sub-index 0h to 15h can be used to retrieve all 64
bytes of data.
Example:
The following SDO command will read historical record number 0104h.
Sub-index 02h points to Bytes 8 –11 of that record.
indexsub-indexaccess byte 5 byte 6byte 7byte 8description
5300h
02h
RO
04h
01h
0
0
Read historical record at 0104h.
The Acuity response to this request is as follows.
Byte 1
Byte 2
Byte 3
Byte 4
Byte 5
Byte 6
Byte 7
Byte 8
40h00h53h02h
Historical
Historical
Historical
Historical
Record
Record
Record
Record
Byte 8
Byte 9
Byte 10 Byte 11
Curtis 1030 Acuity Manual, Rev. B
27
9 — SPECIFICATIONS
9 specifications
The specifications for the Curtis Model 1030 Acuity are presented in Table 4.
Table 4 Specifications: 1030 Acuity
Electrical
Operating voltage range
24 – 48 VDC; 72 –144 VDC
Electrical isolation
500 VAC, per UL 583
Transients
IEC 6100-4-4, test level 2
Reverse voltage
protection
Acuity will not be damaged if connected to the battery
with inverted polarity.
Short circuit
protection
All inputs and outputs (except CANbus) shall withstand
continous short circuit to B– or B+.
CANbus Isolation
Eliminates ground loops that can cause component
damage as well as data errors due to differences in ground
potentials among the nodes on the CANbus.
Environmental
Operating/storage
temperature range
–30°C to 55°C
Humidity
100% condensing, per IEC 60068-2-30, Db
Protection
IP67, per EN60529
Vibration
IEC 60068-2-6, Fc
Shock
IEC 60068-2-29, Eb
Chemical resistance
Immune to the effects of contact with battery electrolyte,
hydraulic fluid, water, baking soda.
EMC
Emission
EN55022 Class B (component test): EN12895 (vehicle test)
Immunity
EN61000-4-3 (component test): EN12895 (vehicle test)
ESD
EN61000-4-2 (component test): EN12895 (vehicle test)
Regulatory Approvals
UL (pending)
Recognition or component listing (UL 583)
MODEL NUMBER
VOLTAGE RANGE
28
CAN TERMINATION
RESISTOR 120Ω
CAN
CONNECTOR
1030-304
1030-310
24 – 48 VDC
24 – 48 VDC
noBullet
noDeutsch
1030-306
1030-308
24 – 48 VDC
24 – 48 VDC
yesDeutsch
yesBullet
1030-305
72 –144 VDC
1030-311
72 –144 VDC
noBullet
noDeutsch
1030-307
72 –144 VDC
1030-309
72 –144 VDC
yesDeutsch
yesBullet
Curtis 1030 Acuity Manual, Rev. B
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement