Downloading and testing your applications..........................................................................................................................4
Important information to reduce risk....................................................................................................................................... 4
Fault checking and error handling.............................................................................................................................................4
Normal CAN structure............................................................................................................................................................... 5
Normal connection mode........................................................................................................................................................6
Link block..........................................................................................................................................................................................10
Link block inputs............................................................................................................................................................................ 10
Link block outputs.........................................................................................................................................................................11
Theory of operation...................................................................................................................................................................... 16
Troubleshooting
Possible error conditions.............................................................................................................................................................21
Table of errors and system reactions......................................................................................................................................21
Once you have created an application, you have the responsibility to download and test the application.
You should only download your application to hardware or change software parameters while the
vehicle is not in operation. After downloading, test application operation under normal and abnormal
operating conditions. You should make sure that:
•
Individual inputs produce expected outputs .
•
Combinations of inputs do not produce unexpected or dangerous outputs
•
Fault handling and error checking work as designed
Important information to reduce risk
The applications that you create with the PLUS+1® GUIDE Service Tool program typically control heavy,
powerful, and mobile off-road equipment such as tractors, cranes, and harvesters.
Fault checking and error handling
The PLUS+1® GUIDE Service Tool program has no automatic protections against these risks. The Service
Tool has no protection against the risks that result from bugs in the Service Tool software, errors in the
Service Tool manual, or incompatibilities between software versions of the Service Tool.
You must design and test your application to reduce these risks.
You have the responsibility when designing a Service Tool application to include the checking and the
error handling needed to reduce risks in normal and abnormal operating conditions.
The following are some items to consider when developing fault checking and error handling for your
application:
•
How the machine is normally used.
•
Possible operator errors and their consequences.
•
Industry safety standards and legal requirements.
•
Input and output failures and their consequences. These failures can include:
•
Joystick, sensor, and other inputs suddenly going to 100 % or to O %.
‒
Outputs that control machinery direction, speed, and force suddenly changing direction or going
‒
to 100 % or to O %.
Decide how likely each failure is. The more likely a failure, the more you need protect against the
consequences of the failure .
•
The sequence of events and consequences of a fault or error.
•
The sequence of events and consequences of an emergency stop.
Warning
Under normal operating conditions, using this type of machinery always involves risk of personal injury
and equipment damage. Abnormal operating conditions increase the risk of personal injury and
equipment damage.
A normal CAN structure is illustrated below. There is one single CAN connection per module. Bus
termination is handled with external resistors.
Normal CAN Structure
Danfoss RedCAN is based on a redundant CAN communication principal. RedCAN uses two CAN
connections per module. The modules are connected in a ring structure to provide a second path for
communication in the event of a segment error.
RedCAN structure
RedCAN Structure
Termination of the bus is handled automatically inside the ECU by the RedCAN connection. No external
resistors are required.
System behavior depends on parameter settings. Incorrect parameters may lead to system malfunction. It
is recommended to disconnect the controller from the system and set parameters before reconnecting it
to the system.
RedCAN uses one standard CAN driver with controller but has the additional connecting circuit logics to
terminate the bus and provide the second communication path in the event of a bus failure.
When using Dynamic RedCAN each node has knowledge about its closest neighbors and with that
information determines if it should act as a master holding the termination and initiating the fault
detection heartbeat or go transparent while waiting for the heartbeat to initiate.
RedCAN inputs
RedCAN function block inuputs
InputTypeRangeDescription
FreezeBOOL—Used to turn off RedCAN
Check AppendixBOOL—Used to turn master relays to look opposite
Def SystemARRAY (128) U8—Array containing predefined system. (Lowest ID
ScanBOOL—Initialize a system scan
Max ExectimeU85–255Maximum execution time during system scan.
Max TimeoutU1675–50000
TimeBaseU1615–10000
CANBus——
Extended_IDBOOL—
CAN_ID_OffsetU320x0-0x1FFFFF00
NodeU80–127
PortPort—CAN port to use
BusOffBOOL—Error on CAN wire
ResetBOOL—
direction.
in position 0, Normal neighbor in position 1,
etc).
This is the execution time of the slowest unit on
the RedCAN loop and, is used for all units
connected to the RedCAN loop. Constant
recommended (default 30 ms).
Sets how long to wait for heartbeat message
before regarded as error. Minimum default
setting is 5 times greater than Time Base (450
ms).
Sets detection timeout and heartbeat rate. (how
often the heartbeat should be sent). Minimum
default setting is 3 times greater than
Max_ExecTime (90 ms).
Use extended CAN message IDs
Offset for CAN ID to put messages in a desirable
range. Messages used are in this range (0x00–
0xFF) + Offset.
Number to distinguish nodes from each other
Output activated -> Reset BusOff (delete
connection in Unit_Config).
RedCAN Outputs
OuputTypeRangeDescription
OS_Out
RedCAN_RelayMode U80–2
StatusBus
0: Transparent
1: Normal
2: Redundant
This signal is either the signal from the RedCAN_
Link block or the signal decided from the
diagnostic tool.
The Extended implementation consists of five separate block parts:
•
Link Block
•
Beat Block
•
Diagnostic Block
•
Freeze Block
•
Relays Block
The blocks could all be used in every controller but it could also be that one controller acts as the
diagnostic interface and is the only one using the Diagnostic block. Other controllers in the system only
need Link and/or Beat blocks.
Link block
The Link Block detects the nodes in the System and their relative positions. It also takes care of bus
termination and disconnects faulty segments to keep the bus intact.
Link block inputs
InputTypeRangeDescription
FreezeBOOL—Use to turn off RedCAN
Check AppendixBOOL—
SystemARRAY (128) U8—
ScanBOOL—Initialize a system scan
InitBOOL—
DelayU160–65535
Max ExectimeU85–255
CANBus——
Extended_IDBOOL—
CAN_ID_OffsetU32
NodeU80–127
Port——CAN port to use
BusOffBOOL—Error on CAN wire
ResetBOOL—
0x00x1FFFFF00
Use to turn master relays to look opposite
direction. Enables detection of some faults that
may otherwise be missed.
Array containing actual system (Lowest ID in
position 0, Normal neighbor in Position 1, etc).
Controls whether a scan should be initiated on
power up.
T: Scan is initiated on power up.
F: No scan, system is regarded as correct.
Sets the delay time before heartbeat is enabled.
This is to handle differences in startup time for
the nodes in the system. Only valid when
init=false.
Maximum execution time during system scan.
Constant recommended (default 30 ms).
Use extended CAN message IDs.
Offset for CAN ID to put messages in a desirable
range. Messages used in the range (0x00–0xFF)
+ offset.
Number to distinguish nodes from each other.
Output activated-> Reset BusOff (delete
connection in Unit_Config.
IStartSprintBOOL—The lowest node in the system that initiates the
ImMasterBOOL—The lowest terminating node. Master.
ImMstrOpsitNeighBOOL—The node on the opposite side of the master.
LowestRandIDU320–4294967295Needed to handle multiples with the same node
Max_ExecTimeU80–255Maximum Max_ExecTime
MyRandomIDU320–4294967295Needed to handle multiples with the same node
NormNeighbNodeID U80–127Node ID of the Normal side neighbor.
NormNeighbRandID U320–4294967295Needed to handle multiples with the same node
OpRandIDU320–4294967295Needed to handle multiples with the same node
OppstNeighbU80–127Node ID of the opposite side neighbor.
RedNeighbNodeIDU80–127Node ID of the redundant side neighbor.
RedNeighbRandIDU320–4294967295Needed to handle multiples with same node
Max TimeoutU1675–50000
TimeBaseU1615–10000
CANBus——
Extended_IDBOOL—Use extended CAN message IDs.
CAN_ID_OffsetU32
NodeU80–127Numbers to distinguish nodes from each other.
Port——CAN port to use
0x00x1FFFFF00
heartbeat. First position in system array.
number.
number.
number.
number.
number.
Sets how long to wait for heartbeat message
before regarded aserror. Minimum default
setting is 5 times greater than Time Base (450
ms).
Sets detection timeout and heartbeat rate. (how
often the heartbeat should be sent).
Minimum default setting is 3 times greater than
Max_ExecTime (90 ms).
Offset for CAN ID to put messages in a desirable
range (0x00–0xFF) + Offset.
-1: Undefined (no mode has been detected after
Startup or Check Appendix)
0: System Ready
1: System Scan
2: Freeze
3: Download
4: Check Appendix
Total number of connected RedCAN nodes in
system.
Holds information about nodes that are not
placed as defined system implies.
Flag that informs that there are nodes with
wrong position in system.
Flag that informs that there are nodes in the
designed system that are not connected.
User Manual
PLUS+1® GUIDE Extended Dynamic RedCAN User Manual
Block Functions
OutputTypeRangeDescription
NodeNvrFndArrayARRAY (128) U8—
FaultBus——
BusErrorBOOL—
Node1U80–127
Node2U80–127
NodeGoneBOOL—
NodeGoneAwayARRAY (128) U8—
Freeze block
The Freeze block listens to CAN message KP0 from the Service Tool to set RedCAN to freeze. Therefore it
will keep its current status and will not react to any faults.
Holds information about nodes that are not
connected.
A wire error has been detected.
There is an error between Node 1 and Node 2.
The error is on the Normal side of this node.
(Only certain if all N–R connections).
There is an error between Node 1 and Node 2.
The error is on the Redundant side of this node.
(only certain if all N–R connections)
Flag that informs that a node has disappeared
from the system after startup.
Holds information about nodes that have been
lost since startup.
Freeze block inputs
Freeze block outputs
Relays block
Relays block inputs
InputTypeRangeDescription
CANBus——
NodeU80–127
Port——CAN port to use
OutputTypeRangeDescription
FreezeBOOL—
Checkpoint———
CP_RedCANFreeze
Number to distinguish nodes from each other
Freeze set from diagnostic tool
Shows current freeze status
The Relays block controls the steering of the RedCAN relays. When the RedCAN block is in freeze, it is
possible to set the relays to either Transparent, Normal or Redundant. The Relays block listens to CAN
message KP136.
The master then sends out a system OK and initiates the heart beat.
Theory of operation: Summary
When the system is connected (Mode = 0), a heartbeat message is transmitted to confirm a healthy
communication path. Each node then listens to the heartbeat messages from its two neighbors and if
one of the messages does not come through an error is declared and a new scan is initiated.
To determine the exact setup of the system, a sequence of messages is sent from the master node to it’s
neighbor in normal direction. The messages are then passed on to the next neighbor until the complete
system is covered. In this way, all nodes will get information about the complete system setup and it can
be compared with the predefined system to detect errors in node order.
It is optional to scan at power up. If init is false, a scan is not triggered and the system input is used as a
predefined system to determine the master node (terminating and starting the heart beat). The entire
ring is always checked at startup by the master asking for opposite neighbors in both directions.
This table identifies errors that could possibly occur:
ProblemPossible Cause
Bus/segment errorsCAN wires shortened, faulty ground connection
Node missing/ not responding or ‘babbling idiot’
behavior
Node misplacedPositions in actual system differ from defined system
Fixing errors
The time to detect an error and fix it depends on the parameter settings. The parameter ‘Time Base’ sets
the timeout for the heartbeat message. This is the error detection time. The parameter ‘Max_ExecTime’ is
used to calculate how long a node will wait for a response before changing direction during a scan. The
theoretical worst case scan time is 112*Max_ExecTime, calculated based on the total timeout. The
theoretical best time is 32*Max_ExecTime, based on the time for communicating only (no waiting time).
The total fix time is the sum of error detection time and scan time:
•
Worst Case fix time: TimeBase + 112*Max_ExecTime
•
Best Case fix time: Time Base + 32*Max_ExecTime
All nodes in defined system are not present in actual
system
Table of errors and system reactions
If several errors appear at once, they are all reported but a functional system cannot be guaranteed if
more than one error occurs at the same time.
RedCAN is able to handle the first error and report where the first error occurs so it can be fixed. But, if
that error is not fixed then there is no guarantee that the system will continue to work if another error is
occurring.
OutputTypeRangeDescription
StatusBus——
ModeS16-1–4
NbrOfNodesU80–128
MisplacedArrayARRAY (128) U8—
NodeMissplacedBOOL—
NodeNvrFndBOOL—
NodeNvrFndArrayARRAY (128) U8—
FaultBus——
BusErrorBOOL—
Node1U80–127
-1: Undefined (no mode has been detected)
0: System Ready
1: System Scan
2: Freeze
3: Download
4: Check Appendix
Total number of connected RedCAN nodes in
system
Holds information about nodes that are not placed
as defined system implies.
Flag that informs that there are nodes with wrong
position in system.
Flag that informs that there are nodes in the
designed system that are not connected.
Holds information about nodes that are not
connected.
A wire error has been detected.
There is an error between Node 1 and Node 2.
The error is on the Normal side of this node. (Only
certain if all N–R connections).
2800 East 13th Street
Ames, IA 50010, USA
Phone: +1 515 239 6000
Danfoss
Power Solutions Trading
(Shanghai) Co., Ltd.
Building #22, No. 1000 Jin Hai Rd
Jin Qiao, Pudong New District
Shanghai, China 201206
Phone: +86 21 2080 6201
Products we offer:
Hydro-Gear
www.hydro-gear.com
Daikin-Sauer-Danfoss
www.daikin-sauer-danfoss.com
DCV directional control
•
valves
Electric converters
•
Electric machines
•
Electric motors
•
Gear motors
•
Gear pumps
•
Hydrostatic motors
•
Hydrostatic pumps
•
Orbital motors
•
PLUS+1® controllers
•
PLUS+1® displays
•
PLUS+1® joysticks and
•
pedals
PLUS+1® operator
•
interfaces
PLUS+1® sensors
•
PLUS+1® software
•
PLUS+1® software services,
•
support and training
Position controls and
•
sensors
PVG proportional valves
•
Steering components and
•
systems
Telematics
•
Danfoss Power Solutions is a global manufacturer and supplier of high-quality hydraulic and
electric components. We specialize in providing state-of-the-art technology and solutions
that excel in the harsh operating conditions of the mobile off-highway market as well as the
marine sector. Building on our extensive applications expertise, we work closely with you to
ensure exceptional performance for a broad range of applications. We help you and other
customers around the world speed up system development, reduce costs and bring vehicles
and vessels to market faster.
Danfoss Power Solutions – your strongest partner in mobile hydraulics and mobile
electrification.
Go to www.danfoss.com for further product information.
We offer you expert worldwide support for ensuring the best possible solutions for
outstanding performance. And with an extensive network of Global Service Partners, we also
provide you with comprehensive global service for all of our components.
Local address:
Danfoss can accept no responsibility for possible errors in catalogues, brochures and other printed material. Danfoss reserves the right to alter its products without notice. This also applies to products
already on order provided that such alterations can be made without subsequent changes being necessary in specifications already agreed.
All trademarks in this material are property of the respective companies. Danfoss and the Danfoss logotype are trademarks of Danfoss A/S. All rights reserved.