- No category
advertisement
Transportation
Products
CBT mVEC User Manual
REV 1.2
Table of Contents
1. mVEC Introduction Section
................................................................................................... 4
2. Quick Start Section
................................................................................................................... 5
2.1. Working with the mVEC .............................................................................................................. 5
2.1.1. mVEC Electrical Grid ........................................................................................................... 6
2.1.2. mVEC Components ............................................................................................................. 6
2.1.3. Component Descriptions ...................................................................................................... 6
2.1.4. mVEC Software ................................................................................................................... 7
3. Configuring the mVEC Options
............................................................................................ 8
3.1. Hardware Options ...................................................................................................................... 8
3.1.1. mVEC Electrical Grid Configuration Options ........................................................................ 8
3.1.2. External High-Side Output Option ........................................................................................ 9
3.1.3. Grid Output Connector Options............................................................................................ 9
3.1.4. Grid Input Power Connection Options .................................................................................. 9
3.1.5. Grid Label Options ............................................................................................................... 9
3.1.6. Cover Options .................................................................................................................... 10
3.1.7. Fuse Puller and Spare Fuse Options ................................................................................. 10
3.2. Software options ....................................................................................................................... 10
3.2.1. Fault Detection Options ..................................................................................................... 10
4
. External Connections
............................................................................................................. 11
4.1. Control Header Connection ...................................................................................................... 11
4.1.1. Overview ............................................................................................................................ 11
Figure 8: CAN (mating) connector ................................................................................. 12
4.1.2. CAN Connector Part Numbers ........................................................................................... 12
4.1.3. CAN Connector Pin Descriptions ....................................................................................... 12
4.1.4. Ignition Connections .......................................................................................................... 13
Figure 9: Active-low ignition connections ....................................................................... 14
Figure 10: Active-high ignition connections ................................................................... 15
Figure 11. CAN harness address pin connections with power reference to offset ........ 16
4.2. Bussman 32006 Series Output Connections ............................................................................ 16
4.2.1. Part Numbers ..................................................................................................................... 16
4.2.2. Output Connector Drawing ................................................................................................ 17
4.3. mVEC Power Input Connection Options ................................................................................... 18
4.3.1. Bladed Power .................................................................................................................... 19
4.3.2. Studded Power .................................................................................................................. 19
Figure 14. Studded power (mating) connector.............................................................. 19
4.3.3. Input Connector Part Numbers .......................................................................................... 20
Figure 15. Bussmann 32004 VEC Input connector ....................................................... 20
5. Vehicle Installation
................................................................................................................. 21
5.1. Mechanical Information ............................................................................................................ 21
5.1.1. Dimensions ........................................................................................................................ 21
Figure 18. mVEC height with cover open ..................................................................... 22
1
5.1.2. Mounting Location Selection .............................................................................................. 22
5.1.3. Electrical Connections to the Vehicle ................................................................................. 23
5.1.4. Power Connections to the mVEC: Connector Details ........................................................ 24
5.1.5. High-Side Drive (Optional) ................................................................................................. 25
5.1.6. CAN Connection ................................................................................................................ 25
Figure 21. CAN connection .......................................................................................... 26
6. Application Examples
............................................................................................................ 27
6.1. Switched Fuse Load ................................................................................................................. 27
6.2. Inductive Load Protection ......................................................................................................... 27
6.3. Controlling a Motor using an H-Bridge ...................................................................................... 28
Table 4. H-Bridge States for Motor Control .................................................................. 28
Figure 24. H-bridge ....................................................................................................... 29
6.4. Controlling Flashers using Relays ............................................................................................ 29
6.5. High-Side Output Power Master ............................................................................................... 30
7. PROGRAMMING the mVEC (Using J1939 Messages to Set, Control, and
Monitor the mVEC)
...................................................................................................................... 32
7.1. CAN Software Settings ............................................................................................................. 32
7.1.1. Proprietary A Messages ..................................................................................................... 32
7.1.2. CAN Source Address ......................................................................................................... 32
Table 5. CAN Harness Address Pin States and Offsets ............................................... 34
7.1.3. Parameter Group Number (PGN) Base for Proprietary B Messages ................................. 34
7.1.4. Population Table ................................................................................................................ 35
7.1.5. Default Relay States .......................................................................................................... 36
7.1.6. Start-up Delay Time ........................................................................................................... 36
7.1.7. CAN Message Count Threshold ........................................................................................ 37
7.1.8. Software Version Number .................................................................................................. 38
7.1.9. Controlling Relays .............................................................................................................. 38
7.2. Monitoring Fuse, Relay, and System Fault States .................................................................... 39
7.2.1. Proprietary B Messages ..................................................................................................... 39
7.2.2. Fuse Status Messages ...................................................................................................... 40
7.2.3. Relay Status Messages ..................................................................................................... 40
7.2.4. System Error Status Messages.......................................................................................... 40
7.3. CAN Message Definitions ......................................................................................................... 41
7.3.1. Proprietary A Messages ..................................................................................................... 41
7.3.1.1 Command Messages .................................................................................................. 39
Table 6. Message ID 0x12 (Command) ........................................................................ 41
Table 7. Message ID 0x80 (Command) ........................................................................ 42
Table 8. Relay State Values ......................................................................................... 42
Table 9. Message ID 0x88 (Command) ........................................................................ 43
Table 10. Message ID 0x90 (Command) ...................................................................... 43
Table 11. Message ID 0x92 (Command) ...................................................................... 41
Table 12. Message ID 0x94 (Command) ...................................................................... 44
Table 13. Message ID 0x95 (Command) ...................................................................... 46
Table 14. Message ID 0x96 (Command) ...................................................................... 46
Table 15. Message ID 0x98 (Command) ...................................................................... 44
Table 16. Message ID 0x98 (Command) ...................................................................... 47
2
Table 17. Message ID 0x99 (Command) ...................................................................... 47
7.3.1.2. Reply Messages ......................................................................................................... 45
Table 18. Message ID 0x01 (Reply) ............................................................................. 48
Table 19. Relay State Change Failure Message .......................................................... 48
Table 20. Message ID 0x13 (Reply) ............................................................................. 49
Table 21. Message ID 0x94 (Reply) ............................................................................. 48
Table 22. Message ID 0x96 (Reply) ............................................................................. 51
Table 23. Message ID 0x97 (Reply) ............................................................................. 51
7.3.2. Proprietary B Messages ............................................................................................................ 52
7.3.2.1. Fuse Status ..................................................................................................................... 52
Table 24. Fuse Status Message ................................................................................... 53
Table 25. Fuse Status Values ....................................................................................... 54
7.3.2.2. Relay Status ................................................................................................................... 54
Table 26. Relay Status Message .................................................................................. 54
Table 27. Relay Status Values ..................................................................................... 55
7.3.2.3. System Error Status ........................................................................................................ 56
Table 28. Error Messages ............................................................................................ 56
8. Hardware Specifications
....................................................................................................... 59
Environmental Specification ............................................................................................................ 59
Electrical Specifications ................................................................................................................... 59
9. Troubleshooting
...................................................................................................................... 62
10. FAQ
............................................................................................................................................ 64
11. Glossary of Terms
................................................................................................................ 66
3
1. mVEC Introduction Section
The multiplexed Vehicle Electrical Center (mVEC), shown in Figure 1, is an enhanced version of the Bussmann
Vehicle Electrical Center (VEC) as it has a Controller Area Network (CAN) interface. The mVEC has VEC-like features (accepts plug-in components common to power distribution such as fuses, relays, circuit breakers, diodes, etc.) and is IP66 compliant. The mVEC incorporates the VEC ‘power grid’, an electrical component grid for power distribution functions, and the grid is electronically interfaced with a CAN control board that monitors the state of components and controls relays that are plugged into the grid of the mVEC.
Figure 1. Multiplexed Vehicle Electrical Center
The mVEC is a power distribution slave module that distributes power to other devices in a vehicle, and communicates over a CAN bus. Because it is a slave module, the mVEC relies on a master CAN module to control its relays and monitor component status messages.
The mVEC is ideal for applications across numerous markets, including heavy truck, construction, agriculture, military, transit bus/coach, marine, recreational vehicle, and specialty vehicle applications. The mVEC is an excellent solution for power distribution systems that require the ability to control relays and monitor fuses and relays; and a cost effective replacement for complex, fully electronic (solid state) power distribution modules.
The mVEC’s grid can be populated with industry standard plug-in components which use “280 series” terminals, including relays, fuses, circuit breakers, diodes, transorbs, resistors, and flasher modules. These components can be configured in many different ways to meet your system requirements.
The mVEC can be connected to 12 V or 24 V systems, or to vehicles with both voltages. The mVEC is based off the
Bussmann VEC technology and it is possible to customize the mVEC (create a new variant) so that it is capable of functioning with varying electrical architectures. The mVEC can be enabled (turned-on) by battery voltage through an active-high ignition input or by ground through an active-low ignition input.
The mVEC’s CAN control board is protected against over-voltage transients and reverse-voltage conditions and its relay coil drivers are protected from short-circuits.
4
The mVEC communicates with other devices on the vehicle’s CAN bus using the SAE J1939 protocol, and can be part of a multiplexing system that eliminates the need for individual connections between switches and loads. The mVEC works by receiving messages to turn its relays “on” and “off”, and by sending messages indicating the state of its grid components.
Figure 2 shows how an mVEC can be integrated into a vehicle.
Figure 2. mVEC Integration Diagram
2. Quick Start Section
2.1. Working with the mVEC
The mVEC is a power distribution slave module that distributes power to other modules in a vehicle over a Controller Area Network (CAN) bus. Because it is a slave module, the mVEC relies on other modules to monitor and control its components and software.
5
2.1.1. mVEC Electrical Grid
The mVEC features the VEC ‘power grid’ (shown in Figure 3) internal to the unit. This VEC grid provides the electrical circuit to various components with 64 connection points, which can be utilized within the design.
Figure 3: mVEC Grid Area
2.1.2. mVEC Components
The mVEC electrical grid can be populated with components that have 2.8 mm blades on 8.1 mm centerlines (280-series components). mVEC components are used for controlling and/or fusing highcurrent loads on a vehicle, like relays and fuses. The mVEC components can be configured per the customer’s requirements.
These various types of components can be placed on the mVEC electrical grid, including (but not limited to) relays, fuses, circuit breakers, diodes, transorbs, resistors, and flasher modules. The mVEC can only control and monitor relays; fuses and circuit breakers (type I & III) can only be monitored. Because of this, most of the manual is dedicated to using fuses and relays. Relays that are not controlled via the internal CAN board cannot be monitored as normal since the relay control signals are unknown.
2.1.2.1. Relays
The mVEC can be populated with 4-terminal and 5-terminal relays that can switch power to loads.
These relays can be controlled via CAN commands, which signal the internal driver to energize the relay coils by pulling one side of the coil low. (See Grid Coil Current Limit in Section 8). The mVEC has the ability to control and monitor relays.
• For information on how the mVEC controls relays, refer to section 7.1.9. Controlling Relays
• For information on how the mVEC monitors relays, refer to section 7.2. Monitoring Fuse, Relay,
and System Fault Status.
6
2.1.2.2. Circuit Protection – Fuses & Circuit Breakers
Fuses and Circuit Breakers limit excessive current going to loads. The mVEC determines the state of each fuse / breaker by monitoring the fuse voltage through two internal digital inputs.
The mVEC has the ability to monitor fuses / breakers (it cannot control them). Note Type II circuit breakers may not show open status due to the internal resistive component and should not be used in the mVEC.
• For information on how the mVEC monitors fuses / breakers, refer to section 7.2. Monitoring
Fuse, Relay, and System Fault Status.
2.1.3. mVEC Software
The mVEC is a slave module, meaning it is controlled by a master CAN module over a Controller Area
Network (CAN), using CAN messaging.
OEMs / Integrators / operators are not able to create custom software for the mVEC. However, you can change some of the mVEC’s software settings.
• For information on changing software settings, refer to section 7.1. CAN Software Settings.
• For information on how the mVEC controls and monitors components, refer to section 7, Programming the mVEC.
7
3. Configuring the mVEC Options
There are many elements of the mVEC that can be configured. Configuration options for the mVEC fall into two major categories, as follows:
• Hardware configuration options. All hardware configuration options must be selected early in the design process and implemented before production.
• Software configuration options. Most software configuration options do not need to be selected until production, and can be modified after production if needed.
Contact your Cooper Bussmann Account Representative for more details about creating a custom configuration for your product.
3.1. Hardware Options
3.1.1. mVEC Electrical Grid Configuration Options
The mVEC’s electrical grid has 64 connection points that are used for connecting components to the grid.
The components you choose for the grid determine the hardware configuration of your mVEC. Once your configuration is created, you will receive a custom overlay for the grid that has cutouts for each component you selected. See Figure 4.
Figure 4. Grid Component and Connector Location Diagram
8
onnector, and can be used
Option put Conn ector Op tions
T he configurat connectors ar re as follows:
• You can have ut connectors
• Total current for each con nector is 100 amps.
• Output conne nsealed (seal ed required fo
• Output conne configured in
( (useful for ens tput connecto in #11 on the
VEC such as igure 5). rent keying
Figu
re 5. Grid Co m
T he “Power Gr ut amperage f for an mVEC is 200 amps regardless of f the input con s. The
s
T he mVEC inte with cut outs t to allow insert o be filled per the design. els, etc.) For r each unique r, the label is umbers, relay ustomer’s numbering, ci rcuit identifier rs, etc.
9
3.1.6. Cover Options
Additional marking is available on the mVEC cover. Custom laser etching may be made either on the mVEC interior of the cover (underside) or on the exterior (outside) or both.
3.1.7. Fuse Puller and Spare Fuse Options
A fuse puller and up to 4 spare fuses can be included with your mVEC. If included, these items would be stored on the electrical grid as shown in Figure 6.
Figure 6. Spare Fuse and Puller Locations
3.2. Software options
The mVEC software configuration options are primarily in the area of base addressing, default states for relays, and population tables for components (whether to detect if they are present and to be monitored or ignored due to an empty plug in position). Some of the options must be configured at the factory before the mVEC is manufactured, and the rest can be configured by the user at anytime.
3.2.1. Fault Detection Options
The mVEC is capable of detecting various faults. However, some faults may need to go unreported, and would need to be disabled in the factory at an early stage of development. An example would be a fuse that is supplied power through a relay contact. When the relay contact is open the fuse will not have power, causing the mVEC to detect a non-powered fuse fault. It is assumed that fuses always have power; therefore, the non-powered fuse fault should be disabled for this particular fuse. mVEC fault detection capabilities are detailed in the software section of this manual. See section 7 for more information.
10
4. al Conn
o the mVEC c an be classifi ed into three groups:
• Power nectors
• Power ectors
T here is one C
T he CAN conn gr round signals C. eceptacle con tacts on the C nnector is mat ted to the har
T he following s ferent parts o cations
11
Figure 8: CAN (mating) connector Top view of mVEC pin out
4.1.2. CAN Connector Part Numbers
The following table shows the mating connector part numbers for the mVEC’s CAN connector:
Table 1. CAN connector Part Numbers
Component
Plug housing
Receptacle contact
Part Number
Tyco (AMP) - 184115-1
20-14 AWG, Gold: Tyco (AMP) - 184030-1
Double lock plate
Wire seal
Cavity plug
Tyco (AMP) - 184058-1
Tyco (AMP) - 184140-1
Tyco (AMP) - 172748-1 or 172748-2
4.1.3. CAN Connector Pin Descriptions
The following table shows the pin-out for the CAN connector:
Table 2. 12-Pin Connector Pin-Out
Pin Number Name
1 VBATT
24V capable.
Function
2 PWR_REF source address.
Ground connection for the mVEC control circuitry and relay coil return path. Wire size must handle all the relay’s coil current.
Base address offset bit #1. Internally pull low (logic 0). Connect
4 ADDR_1 to PWR_REF to change the offset address to logic 1.
5
6
CAN_SHIELD
CAN_HI
This is the connection point to the CAN shield.
CAN bus high signal connection (CAN_H).
Input enable pin. Pull this input to ground to enable the control pin or pin 8 for enable control.
12
Pin Number Name Function
Input enable pin. Pull this input to battery level to enable the either this pin or pin 7 for enable control.
Base address offset bit #2. Internally pull low (logic 0). Connect
9 ADDR_2 to PWR_REF to change the offset address to logic 1.
10 ADDR_0 to PWR_REF to change the offset address to logic 1.
11
12
HS_OUTPUT
CAN_LO
Optional high-side drive output, controlled via CAN command.
CAN bus low signal connection (CAN_L).
4.1.4. Ignition Connections
The mVEC offers two power-enable inputs pins within the CAN connector.
• One is active high, called IGNITION_HIGH
• One is active low, called IGNITION_LOW
The mVEC will remain powered on when either signal is active. Once deactivated, the mVEC will power off, delaying shortly if internal memory requires updating.
Note: Only one of the enable lines should to be used for normal operation. If both are enabled simultaneously, the mVEC will enter a recovery mode application (factory use only).
4.1.4.1. Active-Low Ignition Input Connection
The active-low ignition input (IGNITION_LOW) enables power to the mVEC when the voltage is
lower than ½ battery voltage on Pin 1.
A shut-down procedure is activated when the voltage on the active-low input is higher than ½
battery voltage on Pin 1, or when the input has an open circuit condition.
mA. This protection is only needed for the harnessing to the mVEC.
The following shows a typical active-low ignition input connection:
13
connections
4.2. Active-High Ignit ion Input C
mVEC when t the input is
tery voltage
on Pin 1. A s rocedure is ac on the active-high in on. ut has an
mA. T his protection he mVEC. ctive-high ignit nnection: n input is 200
14
s
4.3. CAN H arness Ad dress Pin ons
There are three pin provid ed by the mV a power refer rence (called PWR_REF) t that is e used for an y other purpo ns.
• ollowing shoul ld be taken in tion when con
:
The power connector. reference ca n be spliced i into the CAN harness addr he CAN
• eed to be pull led high shou cuit. ered by confi guring the so ns.
. The source gh the mVEC’ ’s CAN
15
ctions with vo ce.
eries Out nnection
B ussman sells tion. The out tput connecto g 30 A ontinuous cur rrent per term inal (maximu connector)l.
• Wh en a sealed o d to IP66. n. ector has a d g feature. color (8 can be up to f onnectors on
B ecause there n options for t the output co he part numb f different
M
ALE
O
UTPUT
C
ONN
(280 S
ERIES
)
S
EALING
C
ONNEC
C
AVITY
C
1 = For Use
ON
P
ART
C
O
O
PTIONS
2 = For Use
A = Black
B = Gray
C = Green
D = Blue
F = Red aled minals inals utral (only
avai JP2 tion.)
16
4.2.1.1. Terminal Position Assurance (TPA)
mVEC connectors feature terminal position assurance. Here are the part numbers depending on your sealing configuration.
O
UTPUT
C
ONNECTOR
– T
ERMINAL
P
OSITION
A
SSURANCE
(TPA)
32006-TPX
S
EALING
O
PTION
4.2.1.2. Connector Position Assurance (CPA)
The connector position assurance part number is 32006-CP.
4.2.2. Output Connector Drawing
The output connector pinouts are configuration-specific. Refer to the procurement drawing for your specific mVEC configuration for more details.
Figure 12. 32006 VEC Connector
17
Table 3. 32006 Mating Terminal Reference
The chart below is for reference only, and is subject to changes by Delphi Packard. Delphi Packard part numbers are shown.
PART NUMBERS
12110843
12110844
12129424
12110842
12129663
12129425
12110846
12110847
12129409
12110845
12110853
12052217
12034046
12066214
12129494
12059284
TERMINALS DESCRIPTION
280 ser. Metri-Pack Unsealed Female Terminal - Tangless
280 ser. Metri-Pack Unsealed Female Terminal - Tangless
280 ser. Metri-Pack Unsealed Female Terminal - Tangless
280 ser. Metri-Pack Unsealed Female Terminal - Tangless
280 ser. Metri-Pack Unsealed Female Terminal - Tangless
280 ser. Metri-Pack Unsealed Female Terminal - Tangless
280 ser. Metri-Pack Sealed Female Terminal - Tangless
280 ser. Metri-Pack Sealed Female Terminal - Tangless
280 ser. Metri-Pack Sealed Female Terminal - Tangless
280 ser. Metri-Pack Sealed Female Terminal - Tangless
280 ser. Metri-Pack Sealed Female Terminal - Tangless
280 ser. Metri-Pack Unsealed Female Terminal - w/Tang
280 ser. Metri-Pack Unsealed Female Terminal - w/Tang
280 ser. Metri-Pack Unsealed Female Terminal - w/Tang
280 ser. Metri-Pack Unsealed Female Terminal - w/Tang
280 ser. Metri-Pack Unsealed Female Terminal - w/Tang
CABLE RANGE (mm sq)
.35-.50
.80-1.0
1.0-2.0
2.0-3.0
3.0
5.0
.35-.50
.80-1.0
1.0-2.0
2.0-3.0
3.0-5.0
.35-.50
.50-.80
1.0-2.0
2.0-3.0
3.0
12015858
12084201
12077411
12077412
12129493
12077413
280 ser. Metri-Pack Unsealed Female Terminal - w/Tang
280 ser. Metri-Pack Sealed Female Terminal - w/Tang
280 ser. Metri-Pack Sealed Female Terminal - w/Tang
280 ser. Metri-Pack Sealed Female Terminal - w/Tang
280 ser. Metri-Pack Sealed Female Terminal - w/Tang
280 ser. Metri-Pack Sealed Female Terminal - w/Tang
3.0-5.0
.35-.50
.50-.80
1.0-2.0
2.0-3.0
3.0
12-10
22-20
20-18
16-14
14-12
12
PART NUMBERS SEALS DESCRIPTION/COLOR/TYPE
12015193
CABLE DIA.
280 ser. Metri-Pack cable seal/Blue/Straight 3.45-4.30
12010293
12015323
12041351
280 ser. Metri-Pack cable seal/Light Gray/Straight
280 ser. Metri-Pack cable seal/Green/Ribbed
2.81-3.49
2.03-2.85
280 ser. Metri-Pack cable seal/Tan/Straight 2.03-2.42
16-14
14-12
12-10
22-20
20-18
16-14
14-12
12
GAUGE
22-20
18-16
16-14
14-12
12
10
22-20
18-16
12089679
12015899
12129381
280 ser. Metri-Pack cable seal/Purple/Ribbed 1.60-2.15
280 ser. Metri-Pack cable seal/Dark Red/Ribbed
800 ser. Metri-Pack cable seal
PART NUMBERS CAVITY PLUGS
12010300 280 Metri-Pack Cavity plug for 32006-XX Connector
1.29-1.70
4.54-4.70
PART NUMBER TERMINAL REMOVAL TOOL
12094429 280 & 800 Ser. Metri-Pack Female Terminal Removal Tool
4.3. mVEC Power Input Connection Options
There are two types of power input connectors that can be used with the mVEC (depending on your grid configuration):
• Bladed (using sealed dual-blade connectors)
• Studded (using ring terminals)
18
T he Bussmann t connector is bl laded connec your configur ration. rent input. It wo input conn he duale mVEC, nput connect tor is capable of providing 60 A of contin t per blade, to amps per connecto
2004 is readil y available th
T he two bladed ts within a sin
T he second co superior prot tection for the ed inputs. St tudded inputs puts. are alled in an be unused). ector
Studded Power
T he studded in ted to the har g terminals. connector is
10-12
ft/lbs. The m . vehicle could be exposed t d to the input area includin ctions:
input stud, the plate of th e ring terminal l
T he following s power inpu t stud, the pla alts, that ‘after er the power r
re 14. Studde d power (mati ing) connecto
19
4.3.3. Input Connector Part Numbers
Male input connector (800 Series)
M
ALE
I
NPUT
C
ONNECTOR
(800 S
ERIES
)
32004–X X
S
EALING
O
PTION
P
ART
C
OLOR
A = Black B = Gray
The following drawing shows a 32004 Input Connector.
Figure 15. Bussmann 32004 VEC Input connector
4.3.3.1. Terminal Position Assurance (TPA)
mVEC Connectors feature terminal position assurance. Here are the part number depends on your sealing configuration.
Input Connector - TPA
32004-TPX
S
EALING
O
PTION
4.3.3.2. Connector Position Assurance (CPA)
Input connector – CPA
32004-CP
20
e Install lation
vary depend ing on the sy stem. Theref fore, mechan mental, and e lectrical the product h ovided.
chanical ation
It is important t that the mVE d so that all of f the mechan y accessible.
mensions of t the mVEC in millimeters: and depth
C height with d
21
Fig
h cover open
5.1.2. Mounting on Select ion
ndent on you wever, you m ust take the f following unting. mounting opti ions with a Co ntative.
2.1. Enviro nmental R equiremen
environments.
.
mVEC locati ion, ensure th
• o
Sa ure range for t the mVEC is –
• o
Re nents. o
To
• l requirement ts are respect ted: entual failure of the module to moisture o ctice dictates placement of f the mVEC in
. hat allows ser rvicing of the s
Cauti on: Bussma d mounting t he mVEC in
has b een tested ag water pressu
dule may be
n exceed the ns the mVEC
Under certai n conditions, n.
22
5.1.2.2. Mechanical Requirements
When selecting an mVEC mounting location, ensure the following mechanical requirements are respected:
• It is highly recommended that it be mounted in locations that are not routinely exposed to direct and routine water sprays. Wherever possible, the mVEC should be placed in covered, shielded, interior locations on a vehicle.
• The mVEC and its connectors are shielded from harsh impact, debris, etc, and is not designed for other mechanical purposes other than that of a power distribution module. It should not be placed where someone could step on it.
• Mount the mVEC harnesses with sufficient strain relief and adequate bend radius.
• The mVEC cover can be fully opened.
• The mVEC mounting location / orientation should facilitate easy servicing of the plug-in power distribution components (fuses, relays, etc.)
• Consider operator’s view of the mVEC labels when mounting unit.
• The mVEC should not be mounted upside-down. Best position is horizontal, but the mVEC is capable of being mounted up to a 90 degree angle from the horizontal.
5.1.3. Electrical Connections to the Vehicle
Depending on the design of the mVEC you plan to use, a number of vehicle-to-mVEC connections will be made that may include the following:
•
•
CAN harness address pin connections
Relay output connections
•
•
Fuse and breaker connections
External high-side output connections (optional)
The following shows an overview of how to connect the mVEC to a vehicle:
23
electrical
5.1.4. Power Co e mVEC: C
T he mVEC is a operation (rel lay dependen y changes. Its
V for 5
T he mVEC has s: grid power des power to the VEC pow ng via output pins on the m
• Logic
CAN power
deliver red through th ector. connectors / studs) with herals, and is
nd Logic P ower Conn equirement ts
power:
•
The mVEC harnesses a e fused. o
Log ould be fused to protect the between the battery and
• o
Pow o
Co nnect logic po ic ground dire r and ground connections f from the logic
VEC.
•
• ads do not aff fect the logic g grid power dir rectly to the c grid grounds into the har s or battery g round.
and the igni ition input to while a non-functi onal unit.
24
omponent on to Load
The gr rid componen as per r the wiring sc ses, circuit br reaker, etc.) c
5.1.5. High-Sid Optional) )
T he mVEC pro controlled ou
T his output is p
L s.
T he following d put terminals und the to 500 mA. ut is used for nal loads like n to an LED:
gure 20. High-side output dri iving an LED
CAN Con nection
T he mVEC is d d. vehicle Contr rol Area Netw o the SAE
F or a list of J19 tions, refer to
S ociety for Aut tomotive Eng ineers. SAE J
the SAE J19 e through the us including nnector type, ngths.
T his section de on. ry to create a 1939-11 indu ness.
T he following l o
connection: modules to the CAN bus for the J1939 bus has thre
25
Low, and CAN Shield (which connect to the corresponding CAN_HI, CAN_LO, and
CAN_SHIELD pins on the CAN connector). o
The CAN cable is very susceptible to system noise, and therefore, the CAN Shield wire must be connected according to the following: a) Connect CAN Shield to the point of least electrical noise on the CAN bus. It is recommended to connect CAN Shield to the vehicle chassis. b) Use the lowest impedance connection possible. c) Connect CAN Shield as close to the center of the CAN bus as possible to multiple points, a ground-loop may occur.
• CAN Connectors: Industry approved CAN connectors are manufactured by ITT, Canon, and
Deutsch, and come in either “T” or “Y” configuration.
• CAN Harness: The CAN harness is the “main backbone” cable that is used to connect the CAN network. This cable cannot be longer than 40 meters, and must have a 120
Ω terminator resistor at each end. The 120
Ω terminator resistors eliminate CAN bus reflections and ensure proper idle-state voltage levels.
• CAN Stubs: The CAN stubs cannot be longer than 1 meter, and each stub should vary in length to eliminate CAN bus reflections and ensure proper idle-state voltage levels.
• Maximum Number of Modules in a System: The CAN bus can handle a maximum of 30 modules in a system at one time.
The following diagram shows a typical CAN connection using the J1939 standard:
Figure 21. CAN connection
26
functions.
Many of thes in new cu variants.
Note: It i is the system ustrative purp oses only.
6.1. Swit tched Fu
e mVEC to pr rovide power et tc.).
T he following s ntroller provi ides the logic pical connecti ons for a swit ation under a ll conditions. s, solenoids,
Figure 22. sed load
oad Pro tection
T he following s
“off”.
27
as diodes ctive load is
nductive load pr rotection.
ntrolling a Motor an H-Bri idge
T he mVEC can lay logic. typically use DC motor.
The customer can use a on the mVEC to do this.
T he relays can ways (off-off, on-off, off-on , on-on), and are possible, as illustrated in Table 4. to control the d n a relay-by-r relay basis.
T able 4. H-Br ridge States f ontrol
Relay 1 Relay 2 Motor 1 M
G GROUND
Motor State
28
Relay 1 Relay 2 Motor 1 M Motor State
G VBATT
T he following s n H-bridge to otor:
ntrolling rs using
es telling the r on” and “off”.
T he following s ntrolled by an external cont
29
F
sher function us
Power M aster
T he high-side ms, including t the grid powe ot ther vehicle s minimize the wn by the syst em when ign
Caution:
If the master r power relay feeds the circ dr rops can occu tion cranking.
wer relay will turn “off”.
T he following s the mVEC, output will tu rn “on” when the mVEC is roller to send a command t to the mVEC to turn it “on” ”. master power r:
30
Fi
h-side output m
31
7. PROGRAMMING the mVEC (Using J1939 Messages to Set,
Control, and Monitor the mVEC)
7.1. CAN Software Settings
A number of mVEC software settings can be viewed and changed using J1939 Proprietary A messages
(refer to section 7.1.1. Proprietary A Messages).
The software settings that can be changed include the following:
• CAN Source Address
• Parameter Group Number (PGN) for Proprietary B messages
• Default Relay states
• CAN message count threshold and source address
Note: It is recommended that the mVEC be set-up in a stand-alone environment when working with software settings.
7.1.1. Proprietary A Messages
Proprietary A messages (PGN EF00) are used for viewing and changing various mVEC software settings.
These messages allow you to define which module in a system is going to receive the message.
• Proprietary A messages sent to the mVEC from external devices are called command
messages.
• Proprietary A messages sent from the mVEC in response to command messages are called
reply messages.
When the mVEC receives a Proprietary A command message, it responds with a Proprietary A reply message. The reply is sent to the CAN node that sent the command message.
The first data byte of a Proprietary A message is the message ID. For messages that have less than 8 bytes, the unused bytes can be filled in with 0x00 or 0xFF without interfering with mVEC performance.
The second data byte of a Proprietary A message may be used as a grid address if the message is grid specific. The parameter called grid address identifies a particular grid within the mVEC (for mVECs with more than one grid). An mVEC with one 8x8 grid would use 0x00 as its grid address.
For a summary of all Proprietary A messages, refer to section 7.3.1. Proprietary A Messages.
7.1.2. CAN Source Address
If multiple mVECs are being used in a vehicle, each must have a unique CAN source address so that other modules can identify which mVEC is sending and receiving messages.
The source address on an mVEC is determined with the following equation:
CAN Source Address = Source Address Base + Source Address Offset
If your system uses 8 mVECs or less, you can assign CAN source addresses using one of the following methods:
32
• Method 1 - Give each mVEC in your vehicle a unique source address base by changing the source address base value in software, and leave the source address offset (harness address pins) the same for each. Refer to section 7.1.2.2. Changing the Source Address Base for more information.
• Method 2 - Give each mVEC in your vehicle a unique source address offset by configuring the
CAN harness address pins in the CAN connector, and leave the source address base the same for each. Refer to section 7.1.2.3. Changing the Source Address Offset for more information.
If your system uses more than 8 mVECs, you can combine different source address bases with different source address offsets to create more than 8 unique CAN source addresses.
7.1.2.1. Viewing the Source Address Base and Source Address Offset
To view an mVEC’s source address base and source address offset about the message.
The mVEC responds with message ID 0x97, which displays the current values for the mVECs source address offset in byte 2.0 and source address base in byte 3.0. See
Message ID 0x97 (Reply).
7.1.2.2. Changing the Source Address Base
•
To set the source address base, set the desired source address base value in byte 1.0 of
message ID 0x90, and send the message to the mVEC. See Message ID 0x90 (Command).
The mVEC responds with message ID 0x01, which indicates if the change was a success or failure in byte 2.0. See
Message ID 0x01 (Reply)
.
Changes made to the source address base will not take effect until the ignition power to the mVEC is cycled. base value as is, then use 0xFF.
7.1.2.3. Changing the Source Address Offset
The mVEC’s source address offset is assigned by configuring the CAN harness address pins
(called ADDR_0, ADDR_1 and ADDR_2) in the mVEC’s CAN connector. Refer to section 5.1.6.
CAN Connection for more information about connecting and configuring the CAN harness address pins.
Up to 8 different source address offsets can be created using different combinations of CAN harness address pin states. There are two CAN harness address pin states: open and
PWR_REF.
• PWR_REF indicates the CAN harness address pin is connected to the PWR_REF pin on the
CAN connector.
• Open indicates the CAN harness address pin is open circuit (not connected).
Changes made to the source address offset when the mVEC is powered will not take effect until the ignition power to the mVEC is cycled.
33
The following table shows all the possible address pin states and the resulting offsets they produce:
Table 5. CAN Harness Address Pin States and Offsets
ADDR_2 ADDR_1 ADDR_0
Open Open Open 0
Open Open
PWR_REF
Open
PWR_REF
1
Open 2
Open PWR_REF PWR_REF
Offset
3
PWR_REF
PWR_REF
Open Open 4
Open
PWR_REF PWR_REF
PWR_REF
5
Open 6
PWR_REF PWR_REF PWR_REF 7
7.1.3. Parameter Group Number (PGN) Base for Proprietary B Messages
The PGN Base identifies which type of Proprietary B message is being sent by the mVEC. The mVEC uses Proprietary B messages to send three types of information: fuse status, relay status, and error status.
It may be necessary to change the PGN Base for Proprietary B messages to avoid conflicts with
Proprietary B messages from other modules. The Proprietary B PGN has an upper byte and a lower byte.
• The upper byte of the PGN is always 0xFF
• The lower byte of the PGN is determined by adding the PGN base value and PGN offset value.
The PGN base value defaults to 0xA0 (160 DEC). To change the PGN you must change the PGN base value. The PGN base can be set to any value between 0x00 and 0xF1.
The PGN offset values are not configurable, and are set as follows:
• Fuse status offset – 0x00
• Relay status offset – 0x01
• Error status offset – 0x02
For example, if you are using the default PGN base value of 0xA0, the PGN values would be 0xFFA0
(fuse status), 0xFFA1 (relay status), and 0xFFA2 (error status).
7.1.3.1. Viewing the PGN Base Value
To view an mVEC’s PGN base value about the message.
The mVEC responds with message ID 0x97, which displays the current value for the PGN base in byte 7.0. See Message ID 0x97 (Reply).
34
7.1.3.2. Changing the PGN Base Value
To change the status PGN base value
•
Set the desired PGN base value in byte 2.0 of message ID 0x90, and send the message to the mVEC. See Message ID 0x90 (Command) for more details about the message.
•
The mVEC responds with message ID 0x01, which indicates if the change was a success or failure in byte 2.0. See
Message ID 0x01 (Reply)
. the source address base value as is, then use 0xFF.
7.1.4. Population Table
The hardware configuration of your mVEC defines which components belong on the mVEC’s electrical grid, and where each component must be connected. For the mVEC to work properly, all components configured to be connected to the electrical grid must actually be connected. of the mVEC’s electrical grid.
A population table (stored in Flash memory) indicates whether or not the components are actually connected to the electrical grid. If a component is not connected (but should be according to the population table), the mVEC will generate an error in the corresponding status message, indicating the component is missing (refer to section 7.2. Monitoring Fuse, Relay, and System Fault Status for more details about status messages).
To avoid errors from a missing component, you must send the mVEC a message telling it to stop controlling or monitoring the component, which is done through the population table using message
ID 0x94.
7.1.4.1. Viewing the Population Table
To view the population table about the message.
The mVEC responds with message ID 0x94, which diplays the current population values for each component: o
0 indicates the component is not controlled and monitored. o
1 indicates the component is controlled and monitored.
See Message ID 0x94 (Reply).
message ID 0x01, and displays a value of 0 (failure) in byte 2.0.
35
7.1.4.2. Changing the Population Table
To change the population table setting for a component
•
Set the desired population value(s) in the appropriate byte(s) of message ID 0x94, and send the message to the mVEC. See Message ID 0x94 (Command) for more details about the message.
• The following population values can be used: o
0 indicates the component is not populated and does not need to be controlled and monitored o
1 indicates the component is populated and must be controlled and monitored.
The mVEC responds with message ID 0x01, which indicates if the operation was a success or failure in byte 2.0. See
Message ID 0x01 (Reply)
.
Note: You cannot ‘populate’ a device that was not in the original factory configuration. You may only alter the population settings of factory-installed devices.
7.1.5. Default Relay States
The default relay states are the “safe” relay states the mVEC assumes when it powers-up, and when the
CAN message count threshold is breached. When the mVEC is shipped, all of the default relay states are set to “off” (0). The following sections show how to view and change the default relay states.
7.1.5.1. Viewing the Default Relay States
To view the default relay states of the mVEC
•
Send the message ID 0x96 to the mVEC. See Message ID 0x96 (Command) for more details about the message.
If the grid address is valid, the mVEC responds with message ID 0x96, which shows the default relay states in byte 4.0 to byte 5.4. See Message ID 0x96 (Reply).
If the grid address is invalid, the mVEC responds with message ID 0x01, and displays a value of 0 (failure) in byte 2.0. See
Message ID 0x01 (Reply)
.
7.1.5.2. Changing the Default Relay States
To change the default relay states
•
Set the desired default relay states in the appropriate bytes of message ID 0x95, and send the message to the mVEC. See Message ID 0x95 (Command) for more details about the message.
• The following default relay state values can be used: o
0 sets the default state to “off” o
1 sets the default state to “on”
The mVEC responds with the message message ID 0x01, which indicates if the operation was a success or failure in byte 2.0. See
Message ID 0x01 (Reply)
.
7.1.6. Start-up Delay Time
The start-up delay is the number of milliseconds the mVEC waits after start-up before receiving commands, or sending messages.
The start-up delay range is 0 milliseconds to 65,534 milliseconds (65.5 seconds), which is 0x0000 to 0xFFFE.
36
7.1.6.1. Viewing the Start-up Delay Time
To view the current start-up delay time
•
Send message ID 0x96 to the mVEC, see Message ID 0x96 (Command) for more details about the message.
If the grid address is valid, the mVEC responds with message ID 0x96, which shows the values for the start-up delay in bytes 6.0 and 7.0. See Message ID 0x96 (Reply).
If the grid address is invalid, the mVEC responds with message ID 0x01, and displays a value of 0 (failure) in byte 2.0. See
Message ID 0x01 (Reply)
.
7.1.6.2. Changing the Start-up Delay Time
To set the delay time
• Set the desired start-up delay time values in byte 1.0 and 2.0 of message ID 0x99, and send the message to the mVEC. See Message ID 0x99 (Command) for more details about the message.
The mVEC responds with message ID 0x01, which indicates success or failure in byte 2.0.
See
Message ID 0x01 (Reply)
.
7.1.7. CAN Message Count Threshold
The CAN message count threshold refers to the minimum number of messages that must be received by the mVEC every two seconds. If the mVEC does not receive enough messages over two seconds, it switches all relays to their default state. The relays will remain in the default state until the mVEC receives a message ID 0x80 or message ID 0x88 with different relay state information, or until ignition power is cycled (for more details on default relay states, see 7.4.2. Relay Status).
There are two ways you can use the CAN message count threshold:
• The same CAN message count threshold can be applied to all modules communicating with the mVEC by not setting a specific CAN timeout source address.
• A specific CAN message count threshold can be applied to one module communicating with the mVEC by using a specific CAN timeout source address. If this is used, the mVEC will only count messages from the indicated module.
7.1.7.1. Viewing the CAN Message Count Threshold
To view the CAN message count threshold
•
Send message ID 0x97 to the mVEC. See Message ID 0x97 (Command) for more details about the message.
The mVEC responds with message ID 0x97, which displays the values for the CAN message
count threshold in byte 4.0 (LSB) and byte 5.0 (MSB), and the CAN timeout source address in byte 6.0. See Message ID 0x97 (Reply).
37
7.1.7.2. Changing the CAN Message Count Threshold
To change the CAN message count threshold
•
Set the desired CAN message count threshold in byte 1.0 (LSB) and byte 2.0 (MSB), and
CAN timeout source address in byte 3.0 of message ID 0x98, and send the message to the mVEC, see Message ID 0x98 (Command) for more details about the message.
The following are things to consider when setting the CAN message count threshold:
• Setting the CAN message count threshold to a value of “0” will disable the CAN timeout feature. Any value other than “0” will be the actual CAN message count threshold.
• Setting the CAN timeout source address to 0xFF will apply the same CAN message count threshold to all modules communicating with the mVEC. If you only want the mVEC to count messages received from one module, you must provide the CAN timeout source address for that specific module.
The mVEC responds with message ID 0x01, which indicates success or failure in byte 2.0.
See
Message ID 0x01 (Reply)
.
7.1.8. Software Version Number
It may be necessary to indicate the software version number for your mVEC when corresponding with
Cooper Bussmann.
7.1.8.1. Viewing the Software Version Number
To determine the mVEC’s software version number
• Send the message message ID 0x12 to the mVEC. See Message ID 0x12 (Command) for more details about the message.
The mVEC responds with the message message ID 0x13. See Message ID 0x13 (Reply).
The values that are returned depend on the operating mode of the mVEC. The operating mode is indicated in byte 1.0 of message ID 0x13. o
If the operating mode is 0 (Run), the software version number will be shown in byte 2.0 and 3.0, and the bootloader version number will be shown in byte 4.0 and 5.0. o
Operating mode is 1 is reserved. o
If the operating mode is 2 (Test Mode), the software version number will be the same as that in mode 0 (Run).
7.1.9. Controlling Relays
The mVEC’s relays are controlled by CAN messages received from external devices that tell the mVEC to turn the relays “on” or “off”. The following sections describe how to view and change the state of a relay.
7.1.9.1. Viewing Relay States
To determine the state of the mVEC’s relays
•
Send message ID 0x96 to the mVEC. See Message ID 0x96 (Command) for more details about the message.
If the grid address is valid, the mVEC responds with message ID 0x96, which shows the state of the mVECs relays (and high-side drive, if installed) in bytes 2.0 to 3.4. See Message ID
0x96 (Reply).
38
If the grid address is invalid, the mVEC responds with message ID 0x01, and displays a value of 0 (failure) in byte 2.0. See
Message ID 0x01 (Reply)
.
7.1.9.2. Changing Relay States
There are two messages that can be used when changing the state of a relay, as follows:
• Message ID 0x80 - does not provide a diagnostic reply message from the mVEC indicating if the message was a success or failure.
• Message ID 0x88 – does provide a diagnostic reply message from the mVEC indicating if the message was a success or failure.
7.1.9.3. Changing Relay States Using Message ID 0x80
To change the state of a relay and not receive a diagnostic reply, set the desired relay states in the appropriate bytes of message ID 0x80, and send the message to the mVEC, see Message
ID 0x80 (Command) for more details about the message.
Each relay state value will have one of the bit settings described in Table 7 listed for message ID
0x80. See Message ID 0x80 (Command) for more details about the message.
If the message fails because it is too short, contains an invalid grid address, or is trying to control a relay that is not in a controlled and monitored component location, message ID 0x80 will be ignored.
7.1.9.4. Changing Relay States Using Message ID 0x88
To change the state of a relay and receive a diagnostic reply set the desired relay states in the appropriate bytes of message ID 0x88, and send the message to the mVEC, see Message ID
0x88 (Command) for more details about the messageEach relay state value will have one of the bit settings described in Table 7 listed for message ID 0x80, see Message ID 0x80 (Command) for more details about the message.
The mVEC responds with message ID 0x01, which indicates success or failure in byte 2.0, see
Message ID 0x01 (Reply)
.
If the message fails because it is short, contains an invalid grid address, or is trying to control a relay that is not in a controlled and monitored location on the grid, message ID 0x01 will have additional bytes explaining the failure, as detailed in the description for Message ID 0x01
(Reply).
7.2. Monitoring Fuse, Relay, and System Fault States
Fuses, relays and errors are monitored by the mVEC, and the state of each is communicated periodically to other modules on the CAN bus using Proprietary B status messages.
7.2.1. Proprietary B Messages
All Proprietary B messages start at PGN FF00. These messages do not allow you to define which module receives the message; they are broadcast to all modules on the CAN bus at the same time.
The mVEC uses Proprietary B messages to communicate three types of information: fuse status, relay
status, and error status. These messages are sent by the mVEC once every 1000 ms, or every time the status of a relay or fuse is changed (up to once every 25 ms).
39
specific J1939 request from another module to obtain error information (they are not sent once every
1000 ms). Once an error is detected, the error message is sent once every 1000 ms until it is corrected.
Each type of Proprietary B message is identified by a Parameter Group Number (PGN) that may need to be changed to avoid message conflicts with other modules. Refer to section 7.3.2. Proprietary B
Messages for more information on changing the PGN Base for Proprietary B messages.
7.2.2. Fuse Status Messages
The mVEC automatically sends Proprietary B message 0xFF00 + PGN base (defaults to 0xFFAO) indicating the fault state of its fuses once every 1000 ms, or every time the state of a fuse is changed (up to once every 25 ms). Refer to section 7.3.2.1. Fuse Status for more details about this message.
•
The state of each fuse on the mVEC is represented by a two-bit value. See Table 25.
downstream from a relay from generating error messages when the relay is “off” (because they are not receiving power). Disabling the “Not Powered” fuse fault must be done during production at the factory, and cannot be implemented once the product is shipped.
7.2.3. Relay Status Messages
The mVEC automatically sends Proprietary B message 0xFF01 + PGN base (defaults to 0xFFA1) indicating the fault state of its relays once every 1000 ms, or every time the state of a relay is changed
(no more than once every 25 ms). Refer to section 7.3.2.2. Relay Status for more information about this message.
•
The state of each relay on the mVEC is represented by a four-bit value. See Table 27.
•
Some of the faults shown in the table can be disabled at the factory during production. These cannot be disabled after your mVEC is shipped.
detected will be reported by the mVEC. coil driver “off” to protect the circuit and reports the “coil shorted” error. The relay will remain “off” until the mVEC receives a command to turn it “off” and then back “on”.
7.2.4. System Error Status Messages
System error messages are Proprietary B messages; however, they are not sent by the mVEC on a regular basis like other Proprietary B messages. Instead, they are sent every time a system error occurs, or when there is a specific J1939 Request message from an external module to obtain System Error
Status information.
40
When a system error occurs, the message 0xFF02 + PGN base (defaults to 0xFFA2) is transmitted once every 1000 ms until either the power is cycled, or CAN communication is restored, see 7.3.2.3.
System Error Status for more details about the message.
7.3. CAN Message Definitions
The mVEC uses two kinds of messages when communicating with other modules:
The sections that follow show the settings and values for the various Proprietary A and Proprietary B messages.
• Settings enclosed by round brackets (xxx) are actual values.
• Settings enclosed by square brackets [xxx] are default values.
7.3.1. Proprietary A Messages
When the mVEC receives a Proprietary A message from an external device, it sends a reply message back to that device using a Proprietary A message.
• Messages sent from the external device to the mVEC are called command messages.
• Messages sent from the mVEC back to the external device are called reply messages.
7.3.1.1. Command Messages
Command messages are sent to the mVEC by external modules. The mVEC replies to every command message except message ID 0x80. All command messages have the following message format:
pgn61184 – Proprietary A
Transmission Repetition Rate: N/A, received message only
Data Length: As defined below, no more than 8 bytes
Parameter Group Number: 61184 ( 00EF00 16 )
The data bytes of each command message are formatted as described in the following sections.
7.3.1.1.1. Message ID 0x12 (Command)
Message ID 0x12 is used for viewing the mVEC’s software version number. The mVEC responds to this message with reply message ID 0x13.
The following table shows the format of the data bytes of message ID 0x12:
Table 6. Message ID 0x12 (Command)
Byte Description Value
41
Byte Description
0 Message ID
1-7 Reserved
Value
Message ID (0x12)
7.3.1.1.2. Message ID 0x80 (Command)
Message ID 0x80 is used to change the state of relays or the high-side drive (if installed).
The mVEC does not respond to this message. Refer to section 7.3.2.2. Relay Status for the different relay state values.
The following table shows the format of the data bytes of message ID 0x80:
Table 7. Message ID 0x80 (Command)
Byte Size (Bits)
0.0 8
3.6
4.0
4.2
4.4
4.6
5.0
5.2
1.0
2.0
2.2
2.4
2.6
3.0
3.2
3.4
2
2
2
2
8
2
2
2
2
2
2
2
2
2
6
Total: 6 bytes
Meaning
Message ID (0x80)
Grid address (0x00)
Relay 1 state
Relay 2 state
Relay 3 state
Relay 4 state
Relay 5 state
Relay 6 state
Relay 7 state
Relay 8 state
Relay 9 state
Relay 10 state
Relay 11 state
Relay 12 state
High-side output state
Reserved
Each relay state value will have one of the following bit settings:
Table 8. Relay State Values
Bit Value Hex Value
00
01
0
1
Turn relay off
Turn relay on
10
11
2
3
Action
Do not change relay state
Do not change relay state
The “Do not change” values shown above are used when multiple modules are controlling the same mVEC to enable you to leave the state of some relays unchanged while changing the state of others with the same message.
42
7.3.1.1.3. Message ID 0x88 (Command)
Message ID 0x88 is used to change the active state of relays or the high-side drive (if installed). The mVEC responds to this message with reply message ID 0x01. Refer to section 7.3.2.2. Relay Status for the different relay state values.
The following table shows the format of the data bytes of message ID 0x88:
3.6
4.0
4.2
4.4
4.6
5.0
5.2
Table 9. Message ID 0x88 (Command)
Byte Size (Bits)
0.0 8
1.0
2.0
2.2
2.4
2.6
3.0
3.2
3.4
2
2
2
2
8
2
2
2
Relay 2 state
Relay 3 state
Relay 4 state
Relay 5 state
Relay 6 state
Meaning
Message ID (0x88)
Grid address (0x00)
Relay 1 state
Relay 7 state
2
2
2
2
2
2
6
Total: 6 bytes
Relay 8 state
Relay 9 state
Relay 10 state
Relay 11 state
Relay 12 state
High-side output state
Reserved
Each relay state value will have one of the bit settings described in Table 8. Relay State
Values listed for message ID 0x80.
7.3.1.1.4. Message ID 0x90 (Command)
Message ID 0x90 is used to set:
• the CAN source address base value
• the PGN base value
The mVEC responds to this message with reply message ID 0x01. The new setting for the CAN source address takes effect on the next power cycle. The new setting for the
PGN base value takes effect immediately.
The following table shows the format of the data bytes of message ID 0x90:
Table 10. Message ID 0x90 (Command)
Byte Size (Bits) Value
0.0 8 Message ID (0x90)
43
Byte Size (Bits)
1.0 8
Value
Source address base. Use 0xFF to indicate no change.
2.0 8
Total: 3 bytes
Status PGN base. Use 0xFF to indicate no change.
7.3.1.1.5. Message ID 0x92 (Command)
Message ID 0x92 is used to view the population table. The mVEC responds to this message with reply message ID 0x94 (or reply message ID 0x01 if the grid address is invalid).
The following table shows the format of the data bytes of message ID 0x92:
Table 11. Message ID 0x92 (Command)
Byte Size (Bits) Meaning
0
1
1
1
Total: 2 bytes
Message ID (0x92)
Grid address (0x00)
7.3.1.1.6. Message ID 0x94 (Command)
Message ID 0x94 is used to change the population table settings.
The mVEC responds to this message with reply message ID 0x01.
The following table shows the format of the data bytes of message ID 0x94:
Table 12. Message ID 0x94 (Command)
Byte Size (Bits) Meaning
0.0
1.0
2.0
2.1
2.2
2.3
2.4
2.5
2.6
2.7
8
8
1
1
1
1
1
1
1
1
Message ID (0x94)
Grid Address (0x00)
Fuse 1 populated
Fuse 2 populated
Fuse 3 populated
Fuse 4 populated
Fuse 5 populated
Fuse 6 populated
Fuse 7 populated
Fuse 8 populated
44
Byte Size (Bits)
7.0
7.1
7.2
7.3
7.4
7.5
5.0
6.0
6.1
6.2
6.3
6.4
6.5
6.6
6.7
4.1
4.2
4.3
4.4
4.5
4.6
4.7
3.0
3.1
3.2
3.3
3.4
3.5
3.6
3.7
4.0
1
1
1
1
8
1
1
1
1
1
1
1
1
1
3
Total: 8 bytes
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
Meaning
Fuse 9 populated
Fuse 10 populated
Fuse 11 populated
Fuse 12 populated
Fuse 13 populated
Fuse 14 populated
Fuse 15 populated
Fuse 16 populated
Fuse 17 populated
Fuse 18 populated
Fuse 19 populated
Fuse 20 populated
Fuse 21 populated
Fuse 22 populated
Fuse 23 populated
Fuse 24 populated
Reserved
Relay 1 populated
Relay 2 populated
Relay 3 populated
Relay 4 populated
Relay 5 populated
Relay 6 populated
Relay 7 populated
Relay 8 populated
Relay 9 populated
Relay 10 populated
Relay 11 populated
Relay 12 populated
High-side output
Reserved
7.3.1.1.7. Message ID 0x95 (Command)
Message ID 0x95 is used to change the default relay states. The mVEC responds to this message with reply message ID 0x01.
The following table shows the format of the data bytes of message ID 0x95:
45
2.2
2.3
2.4
2.5
2.6
2.7
Table 13. Message ID 0x95 (Command)
Byte Size (Bits) Meaning
0.0 8 Message ID (0x95)
1.0
2.0
2.1
8
1
1
Grid Address (0x00)
Relay 1 default state
Relay 2 default state
1
1
1
1
1
1
Relay 3 default state
Relay 4 default state
Relay 5 default state
Relay 6 default state
Relay 7 default state
Relay 8 default state
3.0
3.1
3.2
3.3
1
1
1
1
Relay 9 default state
Relay 10 default state
Relay 11 default state
Relay 12 default state
3.4 1 High-side output default state
3.5 3
Total: 4 bytes
Reserved
7.3.1.1.8. Message ID 0x96 (Command)
Message ID 0x96 is used to view:
• The start-up delay time
• The default relay states
• The current relay states
The mVEC responds to this message with reply message ID 0x96 (or reply message ID
0x01 if the grid address is invalid).
The following table shows the format of the data bytes of message ID 0x96 (command):
Table 14. Message ID 0x96 (Command)
Byte Size (Bits) Meaning
0 1 Message ID (0x96)
1 1
Total: 2 bytes
Grid address (0x00)
7.3.1.1.9. Message ID 0x97 (Command)
Message ID 0x97 is used to view:
46
• The mapping board configuration
• The CAN source address offset
• The CAN source address base
• The PGN base value
• The CAN message count threshold
• The CAN timeout source address
The mVEC responds to this message with reply message ID 0x97.
The following table shows the format of the data bytes of message ID 0x97 (command):
Table 15. Message ID 0x97 (Command)
Byte Size (Bits) Meaning
0 1 Message ID (0x97)
Total: 1 byte
7.3.1.1.10. Message ID 0x98 (Command)
Message ID 0x98 is used to change:
• The CAN message count threshold (set both bytes to zero to disable)
• The CAN timeout source address
The mVEC responds to this message with reply message ID 0x01.
The following table shows the format of the data bytes of message ID 0x98 (command):
Table 16. Message ID 0x98 (Command)
Byte Size (Bits)
0.0 8 Message ID (0x98)
1.0 8
Value
CAN message count threshold (LSB)
2.0
3.0
8
8
Total: 4 bytes
CAN message count threshold (MSB)
CAN timeout source address [0xFF = count all messages from all addresses]
7.3.1.1.11. Message ID 0x99 (Command)
Message ID 0x99 is used for setting the start-up delay time. The mVEC responds to this message with reply message ID 0x01.
The following shows the format of the data bytes of message ID 0x99:
Table 17. Message ID 0x99 (Command)
Byte Size (Bits)
0.0 8 Message ID (0x99)
1.0
2.0
8
8
Total: 3 bytes
Start-up delay (LSB)
Start-up delay (MSB)
Value
47
7.3.1.2. Reply Messages
Reply messages are sent by the mVEC after it receives command messages from external modules.
All reply messages have the following message format:
pgn61184 – Proprietary A
Transmission Repetition Rate: As required, in response to command messages
Data bytes
Data 0
Parameter Group Number: 61184 ( 00EF00 16 )
The data bytes of the reply messages are formatted as described in the following sections.
7.3.1.2.1. Message ID 0x01 (Reply)
Message ID 0x01 is a diagnostic message that indicates success or failure.
The following table shows the format of the data bytes of message ID 0x01:
Table 18. Message ID 0x01 (Reply)
Byte Size (Bits)
0.0 8
Value
Message ID (0x01)
1.0 8 Message ID being responded to
2.0 8 0 = failure
1 = success
Reserved 3.0-
7.0
8
If the diagnostic reply message is in response to a Message ID 0x88, and that message failed because it was short, contained an invalid grid address, or was trying to control a relay that is not in a controlled and monitored location on the grid, message ID 0x01 will have additional bytes explaining the failure, as detailed in the following table:
Table 19. Relay State Change Failure Message
Byte
3.0
4.0
8
1
Size (Bits) Value
Default: Grid Address requested
Or
0xE0 = Message is too short
0xE1 = Invalid offset
Relay 1 unable to change state as requested
4.1 1 Relay 2 unable to change state as requested
4.2
4.3
4.4
4.5
4.6
1
1
1
1
1
Relay 3 unable to change state as requested
Relay 4 unable to change state as requested
Relay 5 unable to change state as requested
Relay 6 unable to change state as requested
Relay 7 unable to change state as requested
48
5.4
5.5
6.0-
7.0
Byte
4.7
5.0
5.1
5.2
5.3
1
1
1
Size (Bits) Value
Relay 8 unable to change state as requested
Relay 9 unable to change state as requested
1
1
1
3
Relay 10 unable to change state as requested
Relay 11 unable to change state as requested
Relay 12 unable to change state as requested
High-Side Output unable to change state as requested
Reserved
8 Reserved
Total: 8 bytes
7.3.1.2.2. Message ID 0x13 (Reply)
Message ID 0x13 is sent by the mVEC after receiving the command message ID 0x12.
The following table shows the format of the data bytes of message ID 0x13:
Table 20. Message ID 0x13 (Reply)
Byte Description
0
1
2-3
Response
Operating Mode w a r e
S t of
V e rs io n
Value
Message ID (0x13)
0 = Run (application)
1 = Reserved
2 = Test Mode (bootloader)
Software version
4-5 Alternate
Version
6-7 Reserved
Bootloader version.
7.3.1.2.3. Message ID 0x94 (Reply)
Message ID 0x94 is sent by the mVEC after receiving command message ID 0x92.
The following table shows the format of the data bytes of message ID 0x94:
Table 21. Message ID 0x94 (Reply)
Byte Size (Bits)
49
Meaning
4.2
4.3
4.4
4.5
4.6
4.7
5.0
6.0
6.1
3.2
3.3
3.4
3.5
3.6
3.7
4.0
4.1
6.2
6.3
6.4
6.5
6.6
6.7
7.0
7.1
2.3
2.4
2.5
2.6
2.7
3.0
3.1
Byte Size (Bits)
0.0 8
1.0 8
2.0
2.1
2.2
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
8
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
Meaning
Message ID (0x94)
Grid address (0x00)
Fuse 1 populated
Fuse 2 populated
Fuse 3 populated
Fuse 4 populated
Fuse 5 populated
Fuse 6 populated
Fuse 7 populated
Fuse 8 populated
Fuse 9 populated
Fuse 10 populated
Fuse 11 populated
Fuse 12 populated
Fuse 13 populated
Fuse 14 populated
Fuse 15 populated
Fuse 16 populated
Fuse 17 populated
Fuse 18 populated
Fuse 19 populated
Fuse 20 populated
Fuse 21 populated
Fuse 22 populated
Fuse 23 populated
Fuse 24 populated
Reserved
Relay 1 populated
Relay 2 populated
Relay 3 populated
Relay 4 populated
Relay 5 populated
Relay 6 populated
Relay 7 populated
Relay 8 populated
Relay 9 populated
Relay 10 populated
50
Byte Size (Bits)
7.2 1
7.3 1
7.4
7.5
1
3
Total: 8 bytes
Meaning
Relay 11 populated
Relay 12 populated
High-side output
Reserved
7.3.1.2.4. Message ID 0x96 (Reply)
Message ID 0x96 is sent by the mVEC after receiving command message ID 0x96.
The following table shows the format of the data bytes of message ID 0x96:
3.4
3.5
4.0
4.1
4.2
4.3
4.4
4.5
4.6
4.7
5.0
2.5
2.6
2.7
3.0
3.1
3.2
3.3
Table 22. Message ID 0x96 (Reply)
Byte
0.0 8
Size (Bits)
1.0 8
2.0
2.1
2.2
2.3
2.4
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
3
1
1
1
1
1
Value
Message ID (0x96)
Grid address (0x00)
Relay 1 state (on / off)
Relay 2 state (on / off)
Relay 3 state (on / off)
Relay 4 state (on / off)
Relay 5 state (on / off)
Relay 6 state (on / off)
Relay 7 state (on / off)
Relay 8 state (on / off)
Relay 9 state (on / off)
Relay 10 state (on / off)
Relay 11 state (on / off)
Relay 12 state (on / off)
High-side output on / off
Reserved
Relay 1 default state
Relay 2 default state
Relay 3 default state
Relay 4 default state
Relay 5 default state
Relay 6 default state
Relay 7 default state
Relay 8 default state
Relay 9 default state
51
Byte
5.1
5.2
5.3
5.4
1
Size (Bits)
1
1
1
5.5
6.0
7.0
3
8
8
Total: 8 bytes
Value
Relay 10 default state
Relay 11 default state
Relay 12 default state
High-side output default state
Reserved
Start-up delay (LSB)
Start-up delay (MSB)
7.3.1.2.5. Message ID 0x97 (Reply)
Message ID 0x97 is sent by the mVEC after receiving command message ID 0x97.
The following table shows the format of the data bytes of message ID 0x97:
Table 23. Message ID 0x97 (Reply)
0.0
1.0
2.0
Byte Size (Bits)
8
8
8
Value
Message ID (0x97)
Detected circuit board configuration
(Read from mapping board)
CAN source address offset
(cable select)
3.0
4.0
8
5.0 8
CAN source address base
CAN message count threshold
(LSB)
CAN message count threshold
(MSB)
6.0 8
7.0
Total: 8 bytes
8
CAN timeout source address
Status PGN base
7.3.2. Proprietary B Messages
Proprietary B messages are sent by the mVEC (to every module in the system) once every 1000 ms, or every time the state of a relay, fuse, or error is changed (up to once every 25 ms).
7.3.2.1. Fuse Status
The status of the mVEC’s fuses is transmitted in message 0xFF00 + PGN base (defaults to 0xFFAO).
52
pgn65283 – Proprietary B – Fuse Status –
Transmission Repetition Rate: 1000ms
Parameter Group Number: 65280 ( 00FF00 16 ) (depends on PGN Base setting)
The following table shows the format of the data bytes of Fuse Status message:
5.6
6.0
6.2
6.4
6.6
7.0
4.0
4.2
4.4
4.6
5.0
5.2
5.4
2.0
2.2
2.4
2.6
3.0
3.2
3.4
3.6
Table 24. Fuse Status Message
Byte Size (Bits)
0.0 8
1.0 2
1.2
1.4
1.6
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
8
Total: 8 bytes
Value
Grid address (0x00)
Fuse 1 status
Fuse 2 status
Fuse 3 status
Fuse 4 status
Fuse 5 status
Fuse 6 status
Fuse 7 status
Fuse 8 status
Fuse 9 status
Fuse 10 status
Fuse 11 status
Fuse 12 status
Fuse 13 status
Fuse 14 status
Fuse 15 status
Fuse 16 status
Fuse 17 status
Fuse 18 status
Fuse 19 status
Fuse 20 status
Fuse 21 status
Fuse 22 status
Fuse 23 status
Fuse 24 status
Reserved
53
Each fuse status value will have one of the following bit settings:
Table 25. Fuse Status Values
Bit Value Hex Value Meaning
00 0
F a
N o ul t
01 1
10
11
2
3 r e d
P o
N ot w e
B lo w n
N ot
U s e d
Option to Disable?
No
No
Yes
No
7.3.2.2. Relay Status
The status of the mVEC’s relays is transmitted in message 0xFF01 + PGN base (defaults to 0xFFA1).
pgn65283 – Proprietary B – Relay Status –
Transmission Repetition Rate: 1000ms
Parameter Group Number: 65281 ( 00FF01 16 ) (depends on PGN Base setting)
The following table shows the format of the data bytes of Relay Status message:
Table 26. Relay Status Message
Byte Size (Bits)
0.0 8
Value
Grid address (0x00)
54
5.4
6.0
6.4
7.0
7.4
Byte
1.0
1.4
2.0
2.4
3.0
3.4
4.0
4.4
5.0
4
4
4
4
4
4
Size (Bits)
4
4
4
4
4
4
4
4
Total: 8 bytes
Value
Relay 1 status
Relay 2 status
Relay 3 status
Relay 4 status
Relay 5 status
Relay 6 status
Relay 7 status
Relay 8 status
Relay 9 status
Relay 10 status
Relay 11 status
Relay 12 status
High-side output status
Reserved
Each relay status value will have one of the following bit settings:
Table 27. Relay Status Values
Bit
Value
Hex
Value
0000 0
Meaning
Okay
0001 1
0010 2
0011 3
0100
0101
4
5
Relay coil open or relay not present
Coil shorted or failed relay driver
Normally Open (N.O) contact is open (when a N.O contact is not connected to the Common (C) terminal, but should be).
Normally Closed (N.C) contact is open (when a N.C contact is not connected to the Common
(C) terminal, but should be).
The coil is not receiving power
Option to
Disable
55
Bit
Value
Hex
Value
0110 6
0111 7
1000 8
1001 9
1010 A
1011 B
1100 C
1101 D
1110 E
1111 F
Meaning
Normally Open (N.O) contact is shorted (when a N.O contact is connected to the Common (C) terminal, but should not be).
Normally Closed (N.C) contact is shorted (when a N.C contact is connected to the Common
(C) terminal, but should not be)
Reserved
Option to
Disable
Reserved
Reserved
High-side driver is reporting a fault condition.
High-side driver has an openload
High-side driver is over voltage
Reserved
Relay location not used
7.3.2.3. System Error Status
System error status messages are sent in message 0xFF02 + PGN base (defaults to 0xFFA2).
pgn65283 – Proprietary B – System Error Status –
Transmission Repetition Rate: 1000ms
Parameter Group Number: 65282 ( 00FF02 16 ) (depends on PGN Base setting)
The following table shows the format of the data bytes of System Error Status message:
Table 28. Error Messages
Byte Size
(Bits)
Meaning Corrective Action
56
Byte Size
(Bits)
0.0 8
1.0
1.1
1.2
1.3
1
1
1
1
Meaning
Grid address
(0x00) mVEC contains invalid configuration information.
Internal electrical grid identifier values have changed since power-up.
Note: Initial error may have no effect, but functionality may change on next power-up.
CAN Harness address input pin values have changed during operation.
CAN Rx communication error.
This happens when the mVEC receives an insufficient number of messages.
1.4
1.6
1.7
2.0
2.1
1
1.5 1
1
1
1
1
2.2 1
2.3 1
CAN Tx communication error.
This happens when a message sent by the mVEC is not received by an external module.
Unexpected reset, or watchdog timer reset.
Over voltage
SPI error
Short message received
Bad FLASH address
Invalid
Checksum
Corrective Action
mVEC must be re-configured by
Cooper
Bussmann. mVEC must be serviced by
Cooper
Bussmann.
Check harness connections. If no result, contact Cooper
Bussmann.
Adjust CAN message count threshold.
Check module harnesses in the system that are sending the mVEC messages.
Cycle vehicle power.
Check terminators in the harness.
If no result, contact Cooper
Bussmann.
Check power and ground connections on the CAN connector. Refer to Section 11.
Troubleshooting
for more details.
Batt+ is greater than about 43v.
Reduce input voltage.
Internal error.
Erase Region command incomplete. Check host application.
Invalid address specified for
Erase Region or Write Memory command.
Invalid data length specified for
Write Memory command.
Invalid checksum for received data for Write Memory command.
57
Byte Size
(Bits)
Meaning
2.4 1 FLASH
Corrective Action
FLASH data doesn’t match received data after Write
Memory command.
2.5 1 Reserved
2.6 1 Reserved
2.7 1 Reserved
Reserved
58
8. Hardware Specifications
Environmental Specification
Operating Temperature
Storage Temperature
Thermal Shock
Temperature Life
Vibration
Mechanical Shock
Temperature/Humidity
Salt Fog
Chemical Resistance
Ingress Protection
Bombardment Test
Label Test
-40 to +85
-40 to +125
-40 to +85
+85
-40 to +85
IP66
°C
°C
°C
°C
°C
EP455 (R2008), Section 5.1.1
EP455 (R2008), Section 5.1.2
SAE J1455 (RJUN2006), Sec. 4.1.3.2
100 hour at temperature, CEI IEC 68-2-2
SAE J1455 (R2006), Section 4.10.4.2
SAE J2030 (RDEC2002), Section 6.16
SAE J1455 (RJUN2006), Sec. 4.2.3
Subject the mVEC to a ninety-six (96) hour period of salt fog per ASTM B117-94, Salt Fog Test
Brake Fluid, AT Fluid, Antifreeze, Windshield Wash
Fluid, PS Fluid, Oil
Low and High Pressure Spray, Splash
24 Hour of Dust, Sand, and Gravel
24 Hour Temperature/Humidity
Electrical Specifications
Maximum Ratings
Maximum ratings establish the maximum electrical rating to which the unit may be subjected.
Standoff Voltage
Time at Standoff
External High-Side Drive
Current
Grid Coil Current Limit
48
15
500
350
V
Sec mA mA
Voltage applied to battery terminal.
Maximum continuous load on this drive output.
General
Unless otherwise stated, conditions apply to full temperature range and full input voltage range.
Battery Voltage
Battery Quiescent Current
9 32
1.5
Power Enable High Voltage
Power
Enable Low
Voltage
> ½ BAT_PWR
< ½ BAT_PWR
59
V mA
V
V
The mVEC control will operate normally within this range of battery voltage.
For the control board only when both ignition inputs are inactive. Less for 12V systems.
Enable voltage must be above this level for normal operaton.
Enable voltage must be below this level for normal operaton.
Grid
Ratings apply to all grid configurations.
Dielectric Voltage
Withstand
Low Voltage
Resistance
No evidence of insulation breakdown or arc over applied are intended to be electrically isolated from each other.
190 output wire just beyond the crimp connection at 10A loading.
200 A
Total amperage limit is 200 amps. Each input stud is limited to
100 amps.
60 connector.
30 terminals
100 A Total amps per output connector.
Electrical Ratings
10M
135 breaker device without evidence of damage or distortion
Temperature rise due to electrical loading at any input, output, or grid component terminal when individually
60 °C dependent upon each circuit application.
Ω
With 80VDC bewteen input and output grid terminals Insulation Resistance
Abnormal Conditions
Ratings apply to the external 12-pin connector. Grid connections subject to application conditions.
Notes:
Reverse Battery
Short Circuit Protection
Power Up Operational
- 24
Short to ground, 5 min.
Short to 16VDC, 5 min.
Ramp battery voltage from 0 to minimum operating voltage at
1V/ms.
V SAE J1455 (RJUN2006), duration of 5 min.
EP455 (R2008) Section 5.10.4
EP455 (R2008) Section 5.10.7
Transient Tests
Ratings apply to the control board and its external 12-pin connector. Grid connections subject to application conditions.
Characteristic Parameter Notes:
Accesory Noise
Alternator Field Decay
Batteryless Operation
Inductive Load Switching
Load Dump
14 + 1.5 sin(2
πf·t)
14 – 90 e
-t/0.038
V
6+|12.6sin(2
πf·t)|
14±600e(-t/0.001)
28+122e(–t/0.4s)
V
V
V
V
V
EP455 (R2008), Section 5.11.1
EP455 (R2008), Section 5.11.2
EP455 (R2008), Section 5.11.3
J1455 (2003), Section 4.11.2.2.2
J1455 (2003)
60
Mutual Coupling Power
Line
Mutual Coupling
Signal Line
ESD Package and
Handling
ESD Powered Mode
14 + 200e
-t/(14x10-6)
±200e
-t/(14x10-6)
±15kV
±15kV
Electro-Magnetism Compliance
Ratings apply to the control board.
Radiated Emissions
Susceptibility
0.01MHz to 1GHz, Narrow band 1MHz normalized
Level 1
CW 14kHz to 1GHz, VPol
CW 30MHz to 1GHz, HPol
100V/m
V
V
V
V
EP455 (R2008), Section 5.11.6.1
EP455 (R2008), Section 5.11.6.2
SAE J1113-13 (RNOV2004), Sec. 5.0
SAE J1113-13 (RNOV2004), Sec. 4.0
EP455 (R2008), Section 5.16.3.1 and
SO 14982
EP455 (R2008), Section 5.16.1
61
9. Troubleshooting
Problem
Everything is connected but there is no communication
The mVEC is communicating, but the relays will not turn
“on”.
Possible Causes
The mVEC is not powered
The relays do not have power.
• Verify the address lines are configured correctly.
Possible Solutions
IGNITION_HIGH
connected to power or
IGNITION_LOW
connected to ground?
The voltage on the address lines is not what it should be.
The CAN bus is marginal or not functional.
The mVEC software is configured differently than it should be.
The relay message is being rejected.
The destination address is incorrect.
• Use a PC-based CAN tool to verify that messages can be sent and received on the
CAN bus.
CAN_HI
&
CAN_LO
reversed?
CAN_HI
or
CAN_LO
shorted to ground or to
CAN_SHIELD
?
CAN_HI
or
CAN_LO
open?
• Is the CAN bus terminated properly?
• Is there “mVEC-like” communication from an unexpected source address and/or PGN?
These are configurable, and if they are not what you expect, the mVEC will be broadcasting on different source addresses and PGNs.
• Make sure the relay message is the version that requests a diagnostic response
(message 0x88).
• Check the codes returned by the mVEC against the responses listed in section
7.3.2.2.
• Check for lack of grid power connection, blown fuse, improperly seated relay, and improperly seated fuse.
• Make sure the relay message is the version that requests a diagnostic response
(message 0x88).
• Check the codes returned by the mVEC against the responses listed in section
7.3.2.2.
• Check message length, offset value, and whether the component location is populated with a relay.
• Confirm the destination address of the relay message matches the source address that is sending fuse and relay status messages.
62
Problem
The mVEC resets when the loads are turned “on”.
Possible Causes
You are trying to drive 24V relays from a
12V supply.
Insufficient transient response from the desktop power supply.
Power drop or ground lift at a high-current connection point.
Possible Solutions
• Make sure the power supply matches the relays. A 24V mVEC will communicate when powered by 12V, but the 24V relays will not engage.
• Desktop power supplies, even if they are rated for the current requested, can sag substantially when large loads are switched
“on”, a phenomenon that can be confirmed with an oscilloscope.
• Make sure the CAN connector power and ground are not tied to the high-current power and ground studs. When large loads are enabled, the voltage drop (or lift at the ground) could be significant.
63
10. FAQ
What does mVEC stand for?
Multiplexed Vehicle Electrical Center.
Will the mVEC still function if I remove components from its electrical grid?
You must change the population table setting for components that are removed from the grid; otherwise, the mVEC will report errors for the missing component. Refer to section 7.1.4.
Population Table for more details.
How does a system of modules identify which message is being sent by which mVEC?
Using a unique PGN base in combination with a unique CAN source address enables a system to identify which messages are being sent by which mVEC.
How is the source address of the mVEC changed?
Refer to section 7.1.2. CAN Source Address.
What is a grid address?
The grid address identifies the component grid. At present, there are no multiple-grid mVECs, so this is a reserved byte for future expansion. For mVECs with 1 grid, the grid address value should be set to 0.
Do I need to fuse power going to the mVEC power studs?
Though extra fusing is not required to protect the mVEC, heavy gauge wire that is not fused running through a vehicle is not a safe design practice.
Does the power going to the CAN connector have to be fused?
Yes; a 5 A fuse should be used.
What are the recommended mounting practices for the mVEC?
For recommended mounting practices see section 5.1.2 Mounting Location Selection.
Can the mVEC be pressure washed or immersed in water?
An unsealed mVEC should not be pressure washed or immersed in water.
A sealed mVEC can handle pressure washing, but cannot be immersed in water.
What is the maximum torque that can be applied to the studded power connector?
The maximum torque that can be applied to the power lugs is 18 ft./lbs.
Can the mVEC drive relays that aren’t actually on the mVEC’s electrical grid?
The mVEC can be configured with an external high-side output, so it is possible to drive a single external relay from an mVEC. Additionally the mVEC relays could be used to drive other highercurrent relays or solenoids.
What is the current capacity of the mVEC?
The maximum current capacity of the mVEC is 200 A, but that is dependent on the application, type of load, etc.
Can the relay outputs be pulse-width modulated (PWM’d)?
Relays are mechanical devices and cannot be PWM’d at the high frequencies possible with solid state outputs; however, low frequency applications such as turn signals can be run by the mVEC.
Can the external high-side output be used to control something other than a relay?
Yes, as long as the load does not exceed 500 mA.
64
What are the low-side outputs protected against?
Low-side outputs are protected against short-circuits and designed to withstand electrical transient pulse levels likely to be encountered on vehicles.
Can the grid connection inputs for fuses be used to monitor things other than fuses?
Yes, these inputs can be wired directly to output pins through the grid and can monitor active-high digital states (all inputs are tied to weak pull-down resistors). This is not the intended use of the mVEC, so care should be taken to ensure faults reported by the software will be interpreted correctly.
Does the mVEC need a master module on the CAN bus to control it, or can it control itself?
The mVEC is designed as a slave module, meaning it is controlled by master modules.
Can the mVEC be used as an H-bridge?
The mVEC can be used in an H-bridge configuration if two 5-pin relays are used.
Will the mVEC work on a 42 V electrical system?
No. The mVEC is designed for 12 V and 24 V systems. It is not intended for use on 42 V electrical systems.
How far can the mVEC be from the controller sending it commands?
The mVEC is designed to communicate on a J1939 compliant CAN bus. Refer to section 5.1.6.
CAN Connection for more details about connection limitations.
How many mVECs can be in a vehicle?
30 mVEC modules can be in the same system on the same vehicle.
Is black the only mVEC color?
Yes.
Should the mVEC be disconnected when welding it to a vehicle (if welding is necessary)?
Cooper Bussmann recommends that all electrical devices be disconnected during welding to avoid potential damage to them.
The mVEC should not be subjected to environmental conditions that exceed the mVEC’s design limitations.
65
11. Glossary of Terms
CAN
Controller Area Network. A communication network designed for heavy equipment and automotive environments.
CAN High
One of the wires used in the shielded twisted-pair cable. It provides the positive signal that, when connected with CAN Low, provides a complete CAN differential signal.
CAN Low
One of the wires used in the shielded twisted-pair cable. It provides the negative signal that, when connected with CAN High, provides a complete CAN differential signal.
CAN message count threshold
The minimum number of messages that must be received by the mVEC every two seconds.
CAN Shield
A shielding that wraps around the CAN High and CAN Low “twisted pair,” which completes the shielded twisted-pair cable.
CAN source address
An address that identifies which mVEC on the CAN bus has sent a message.
command message
Messages sent to the mVEC from other modules.
component
A device that can be plugged into the mVEC electrical grid. Components include fuses, relays, breakers, diodes, etc.
Connector Position Assurance
A device that prevents you from accidentally pulling-out a connector from the mVEC.
electrical grid
A grid with 64 connection points that is used as the interface for plugging components into the mVEC.
H-bridge
A combination of two half-bridge circuits. H-bridges are used to provide current flow in both directions on a load, which allows the direction of a load to be reversed.
load
A load is any item that draws current from the module, and is typically switched “on” and “off” with outputs.
Examples include but are not limited to bulbs, solenoids, motors, etc.
multiplexing
Simultaneously transmitting multiple messages over one communication channel in a local area network, which dramatically reduces the number of wires needed for switch and load connections.
mVEC
Multiplexed Vehicle Electrical Center.
open load
A fault state that occurs when a load that should be connected to an output becomes disconnected, which typically occurs because of a broken/worn wire in the wire harness or connector pin.
66
PGN
Parameter Group Number. In the mVEC, the PGN is used to identify which type of Proprietary B message is being sent by the mVEC.
population table
Indicates which components are connected to the electrical grid.
Proprietary A message
A J1939 CAN message that allows you to define which module in a system is going to receive the message.
Proprietary B message
A range of J1939 CAN messages that are broadcast to all modules on the CAN bus at the same time.
PWM
Pulse Width Modulation. A type of square wave frequency signal where the ratio of “on” time vs. “off” time is determined by the duty cycle of the signal. The duty cycle refers to the percent of time the square wave is “on” vs. “off”. PWM signals are typically used to drive varying amounts of current to loads, or to transmit data.
reply message
Messages sent by the mVEC to other modules.
shielded twisted-pair cable
A type of cable that consists of two wires twisted together, and covered with a shield material to improve immunity against electrical noise. This cable is used when connecting the CAN bus.
slave module
A module that relies on other devices to monitor and control it. The mVEC is a slave module.
start-up delay
The number of milliseconds the mVEC waits after start-up before receiving commands, or sending messages.
status messages
Messages sent by the mVEC to other modules once every 1000 ms indicating the status of its relays, fuses and (if active) errors.
Terminal Position Assurance
A device that prevents you from accidentally pulling-out wire terminals from the male input and/or output connectors.
67
Power Management
Cooper Bussmann
Sure Power
10955 SW Avery St
Tualatin, OR 97062
Tel: 800-845-6269
Fax: 503-692-9091
Power Distribution
Cooper Bussmann
Transportation Products
10955 SW Avery St
Tualatin, OR 97062
Tel: 800-845-6269
Fax: 503-692-9091
Visit us online at www.cooperbussmann.com
Radio Remote Control
Cooper Bussmann
OMNEX Control Systems
74 - 1833 Coast Meridian Road
Port Coquitlam, BC
Canada V3C 6G5
Tel: 800-663-8806
Fax: 604-944-9267
Cooper Bussmann Transportation is a part of the
Cooper Industries world.
Cooper Bussmann Transportation Products Headquarters:
10955 SW Avery St.
Tualatin, OR 97062
Tel: 800-845-6269 www.cooperbussmann.com
31M-XXX-X(X)UM-B 5-13 Printed in USA
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement
Table of contents
- 6 2.1. Working with the mVEC
- 7 2.1.1. mVEC Electrical Grid
- 7 2.1.2. mVEC Components
- 7 2.1.3. Component Descriptions
- 8 2.1.4. mVEC Software
- 9 3.1. Hardware Options
- 9 3.1.1. mVEC Electrical Grid Configuration Options
- 10 3.1.2. External High-Side Output Option
- 10 3.1.3. Grid Output Connector Options
- 10 3.1.4. Grid Input Power Connection Options
- 10 3.1.5. Grid Label Options
- 11 3.1.6. Cover Options
- 11 3.1.7. Fuse Puller and Spare Fuse Options
- 11 3.2. Software options
- 11 3.2.1. Fault Detection Options
- 12 4.1. Control Header Connection
- 12 4.1.1. Overview
- 13 Figure 8: CAN (mating) connector
- 13 4.1.2. CAN Connector Part Numbers
- 13 4.1.3. CAN Connector Pin Descriptions
- 14 4.1.4. Ignition Connections
- 15 Figure 9: Active-low ignition connections
- 16 Figure 10: Active-high ignition connections
- 17 Figure 11. CAN harness address pin connections with power reference to offset
- 17 4.2. Bussman 32006 Series Output Connections
- 17 4.2.1. Part Numbers
- 18 4.2.2. Output Connector Drawing
- 19 4.3. mVEC Power Input Connection Options
- 20 4.3.1. Bladed Power
- 20 4.3.2. Studded Power
- 20 Figure 14. Studded power (mating) connector
- 21 4.3.3. Input Connector Part Numbers
- 21 Figure 15. Bussmann 32004 VEC Input connector
- 22 5.1. Mechanical Information
- 22 5.1.1. Dimensions
- 23 Figure 18. mVEC height with cover open