Seed Hawk Raven 2010 - Manual (Page 32)

Chapter 3
22 Seed Hawk™ Viper Pro™ Installation & Operation Manual
Detecting CANbus Nodes
The Viper Pro console must be able to communicate with the CANbus system to make sure product is being
applied correctly. Viper Pro should automatically establish communication with the switch box node, product 1,
2, and 3 nodes, and drill node.
FIGURE 1. CAN Initialization Results Screen
Seed Hawk ® Viper Pro systems with Sectional Control Technology (SCT™) will also detect up to two SCT
nodes depending upon the number of bins in the air cart. SCT Ready systems will not have any SCT nodes on
the CANbus. Up to two additional product control nodes (Product 4 and 5 nodes) may be installed to control
optional products during seeding operations.
Note:
If the Viper Pro console establishes communication with a node, it displays as ‘Found’ on the CAN
Initialization Results screen. Nodes not detected during startup will not be displayed on this
screen.
If a node is not found by the Viper Pro console, determine why Viper cannot communicate with the
node. See Chapter 11, Troubleshooting the Viper Pro System, for more information about
communication failures.
CAN Initialization Results
1.
If you have not done so already, power up your Viper Pro console.
2.
The CAN Initialization Results screen displays. If the CAN system found all of your nodes, press Start
Viper
. If not, press Retry CAN Init.
Note:
If the product nodes are not found and this is a new installation, skip to the Re-Addressing Product
Nodes section on page 23 and follow the instructions for addressing the product nodes.
3.
If product nodes which had been ‘Found’ during previous Viper Pro applications, but are still not displayed
after step 2, you will need to troubleshoot the CANbus system to determine why the node is not
communicating with the CAN system (i.e. No logic power, ground issues, faulty CAN connection, etc.).