Raven Troubleshooting Guide

Start here

How to use this guide

Find your system in the menu (Rate, Sections/AccuBoom, CANbus, AutoBoom, Hawkeye, Injection, NH3, Steering, GPS, Displays, Slingshot, Harvest), then pick the symptom that matches what you're seeing. Each entry tells you what to check first, how to test it with a multimeter or a paper clip, and when the part needs to come in for repair.

Three habits that solve most calls before they start:

  • Check cal numbers and settings before touching cables. Wrong boom widths, meter cal, speed cal, or a section not assigned to a product cause most "it won't spray right" complaints.
  • Test toward the console. When a sensor test fails, move back one connector at a time toward the console or node. Where the test starts working is where the bad cable is.
  • Keep the machine running for anything voltage-related. Node updates, PWM valve tests, and CAN voltage checks all need a steady 12 volts.
Safety: anhydrous ammonia, hydraulics under pressure, and chemical residue are all involved in this guide. Wear the PPE on the product label, relieve pressure before opening lines, and never pressure-wash Raven electronics (water inside a radar, node, or display is the number-one cause of "it worked until I washed the sprayer").

Need parts or help?

Spray Center Electronics carries Raven flow meters, valves, cables, nodes, terminators, NCV poppet kits, and diagnostic cables. Raven Applied Technology Support: +1 (800) 243-5435, ATDSupport@ravenind.com. Raven Slingshot Network Operations Center: NOCsupport@ravenind.com.

When you call, have ready: machine make/model/year, the barcode and part number of the node or display (sticker on the back), software versions of everything on the bus, and what else is connected to the CANbus/ISOBUS.

Pick your system

Rate control

Applies to every Raven rate controller: SCS consoles (440, 450, 460, 660, 4400, 4600, 5000), CANbus product nodes with Envizio Pro / Viper Pro / Viper 4, ISOBUS product controllers, RCM (Rate Control Module), and CR7/CR12.

Rate control

No rate (rate reads zero)

Every Raven system needs three things to show a rate, and they only work in this order: Speed → Boom sense → Flow. Area/hour won't register without speed, and flow won't register without boom sense. Test them in order and skip ahead if you already see one working.

1. Speed.

While moving, the console's distance should count up and speed should show.

  • Speed source mounted correctly and powered? Speed type right? SP1 = wheel/magnet, SP2 = radar or simulated radar from GPS.
  • Speed cal right? New speed cal = (current speed cal × measured distance) ÷ distance shown on the controller. Measure at least 400 ft [122 m].
  • GPS speed over CAN: speed type Radar, speed cal 1000.
  • Speed sensor test: enter a speed cal of 1000 (SP1) or 9999 (SP2). At the speed sensor connector (3-pin, keyway at 12 o'clock: Ground, Power 5 or 12 V, Signal 5 V) short Ground to Signal with a paper clip in a "short – no short" motion. Distance should increase on every touch. If it doesn't, move back one connector toward the console and repeat until it works — the cable you just bypassed is bad. If every cable passes, the speed sensor is bad. Re-enter the correct speed cal when done.

2. Boom sense (area/hour).

A boom width must be entered. With master and boom switches on and speed showing, you should have an area/hour.

  • Where to find area/hour: SCS console — Area/Hour button. Envizio Pro — Product Control > Volume/Area Settings (out of a job). Viper Pro — Product Control (out of a job). Viper 4 — Product Control widget > More (must be in a job).
  • Area/hour test: put an SCS console in Manual. Master and all booms OFF, moving or self-test speed, area/hour should be 0. Master + Boom 1 on → area/hour appears. Boom 2 on → increases. Repeat for every section; each one should add.
  • No area/hour on one or more sections → see "Testing boom sense" below.

3. Flow.

With speed and boom sense present, look at volume/minute. That proves the console is getting flow meter (or granular encoder) pulses.

  • Flow meter mounted correctly, powered, within its flow range for your target rate? Cal number right (liquid = meter cal from the tag; granular = spreader constant)?
  • Flow meter test: enter meter cal 1 (liquid) or density 1 and spreader constant 0 (granular). SCS in Manual. Zero the total volume. Master on and at least one boom on — try several switches in case one is bad. At the flow meter connector (Power 5 or 12 V, Ground, Signal 5 V) short Ground to Signal "short – no short". Total volume should climb by 1 or more each touch. No count → move back toward the console one connector at a time. All cables pass → flow meter/encoder is bad. Re-enter the real cal when done.

Rate present but wrong: recheck every cal number and section width, and confirm area/hour climbs with each switch. Re-calibrate the meter cal with a catch test (formula under "Flow meter facts").

Rate control

Erratic rate (bouncing, or rate rises when speed drops)

  • Cabling first: check voltage at the control valve, flow meter/encoder, and node. Look for pinched or stripped wires, loose connectors, corrosion, damaged pins.
  • Pump and hydraulics: if the pump can't keep up, the controller can't control. Check every filter and strainer for blockage.
  • Manual product control test: set a self-test speed and put the product in Manual. If the rate settles, the valve is the problem (is the rate within the valve's operating range?). If it's still erratic, the flow meter is the problem — take it apart, check the turbine spins freely when you blow through it, confirm the rate is within the meter's range. Still erratic → a bad boom switch: run the area/hour test one switch at a time; the switch that makes area/hour bounce is bad.
  • Low rates on 1993–1998 RoGators (544, 554, 664, 844, 854, 864, 1064): below 15 GPM [56.8 L/min] product can flow backward through the meter. AGCO low-flow kit AG16324; run with the hand valve closed under 15 GPM, open above.
Rate control

Rate is slow to come up at the headland (low-rate tips)

Valve Advance and Valve Delay build boom pressure before the next pass.

  • Valve Advance opens the control valve for 1–9 seconds after the booms turn off. Standard and Fast valves only. Must be 0 for Fast Close, PWM, and PWM Close. Needs product node software 1.5 or newer on field computers, or a recent enough PGM/REV on an SCS console.
  • Valve Delay keeps the control valve from correcting for 1–9 seconds after the booms turn on. Standard, Fast, and PWM valves; must be 0 for Fast Close and PWM Close, or a Standard valve used with injection. Only active if the booms were off less than 30 seconds.
  • Suggested starting point: SCS single-product consoles (440/450/460/660) enter 1020 (hold Speed Cal until DATA flashes; digit 1 = delay, digit 3 = advance, digits 2 and 4 stay 0). SCS multi-product (4400/4600/5000): Data > Product > Valve Delay = 1, Valve Advance = 2. Field computers: Product Control menu, VD = 1, VA = 2.
Rate control

Valve cal number explained

Valve type Digits Raven default Digit meaning
Standard 4 2123 backlash · speed · brake point · deadband
Fast / Fast Close 3 743 speed · brake point · deadband
PWM / PWM Close 2 43 brake point · deadband
  • Backlash (1–9): length of the first correction pulse after the valve changes direction. 1 = short, 9 = long.
  • Valve speed: Standard 1–9 (1 slow, 9 fast). Fast/Fast Close 0–9 (0 fast, 9 slow). PWM 0–9 (0 slow, 9 fast). Too fast makes the system oscillate.
  • Brake point (0–9): how far from target the valve slows down. 0 = 5 %, 1 = 10 %, up to 9 = 90 %.
  • Deadband (1–9): 1–9 % allowable error with no correction.
  • Valve Cal 2 (Fast Close valves, not on every console): milliseconds of 12 V burst to open the valve. Default 200.
Rate control

Valve types and what a meter should read

Measure on the main flow/section cable connector, not the valve's own pigtail.

  • Boom (on/off) valves (single manifold 063-0171-926, 3-section 063-0171-928): 3-pin — A Power 12 V, B Ground, C Signal. 12 V on Signal opens the valve, 0 V closes it. Planters are reversed (0 V open, 12 V closed).
  • Control valves (1" butterfly 063-0172-125, 1" fast 3-way ball 063-0172-172, 15 GPM PWM hydraulic 063-0171-843): green wire = Decrease, yellow = Increase. Opening puts voltage on yellow with green as ground; closing reverses polarity.
  • Standard valve: 12 V only while opening or closing. Fast: up to 12 V, typically 3–4 V while adjusting. Fast Close: same, plus 12 V on Decrease to slam closed. PWM: always 12 V pulsed — must be tested under load, and a voltmeter shows the average (50 % duty ≈ 6 V). PWM Close: same as PWM but voltage removed to close.
  • Single-valve NH3 systems use Fast Close (C-FC).
Rate control

Flow meter facts, cal numbers, and installation

  • Raven flow meters put out a 5 V square wave (10 mA draw, 3–4 % variance). A voltmeter can't test the signal without the node connected.
  • Meter cal = pulses per 10 gallons. 720 = 72 pulses/gal. High-pulse ("dual count") sensors double it (720 → 1440). Swapping sensors: put a 063-0171-669 (standard) in place of a 063-0172-004 (high pulse) → divide the meter cal by 2; the other way → multiply by 2.
  • Lowering the meter cal decreases product output; raising it increases output.
  • Catch test (use water, do it 2–3 times): corrected meter cal = current meter cal × total volume on the tally register ÷ actual measured volume. Write the number on the machine — tags wear off.
  • Frequency check: (meter cal ÷ 10) × GPM ÷ 60 = pulses per second (720 cal at 100 GPM = 120 pps).
  • Starting meter cals (US / metric): RFM 5 5500/1455 · RFM 15 1750/493 · RFM 55 750/198 · RFM 60 P/S 720/190 · RFM 100 700/185 · RFM 200 164/43 · RFM 400 80/21 · 3" Magmeter 157/41 · 4" Magmeter 100/26 · 6" Magmeter 50/13. RFM 60S on anhydrous: Raven suggests a starting cal of 190 (the troubleshooting guide's example uses 168 = 710 ÷ 4.22) — verify with a catch test.
  • Granular encoders: 180-count 1.5–50 RPM, 36-count 7–250 RPM. Spreader constant = encoder count ÷ ((D × gate height × gate width) ÷ 1728), D = belt travel per encoder revolution.
  • The 6-to-8 rule: 6–8 inches of straight pipe per inch of meter diameter ahead of the flow meter, or an elbow's swirl gives bad readings. Mount horizontal or slightly uphill; vertical for low rates. Backwards still pulses, but erratically.
  • Potted sensor has heat shrink at the cable end; molded sensor does not.
Rate control

Flow meter / encoder connector pinouts (cable side, keyway or lock at 12 o'clock)

  • 3-pin Conxall: 1 Ground, 2 Power, 3 Signal.
  • 3-pin flat Deutsch: 1 Signal, 2 Ground, 3 Power.
  • 3-pin triangular Deutsch, Weather Pack, and Metri-Pack: A Power, B Ground, C Signal.
  • Power to Ground: 4.5–16 V (Raven systems usually 5 V, AGCO machines usually 12 V — check the meter's rating). Ground to Signal: 5 V.
Rate control

Testing boom sense

The boom sense/speed node must see 12 V from each section switch when it's on. Three kinds of installation:

  • Traditional boom sense/speed node. Wire colors by section: 1 Black, 2 Brown, 3 Blue, 4 Black/White, 5 Brown/White, 6 Blue/White, 7 White/Black, 8 White/Brown, 9 White/Blue, 10 Pink, 11 Yellow/White, 12 Green/White, 13 Red/White, 14 White/Yellow, 15 White/Green, 16 White/Red. OEM harnesses differ — test at the node connectors instead. Gray connector: pins 1–10 = sections 1–10, 11 logic ground, 12 logic power. Black connector: 1 CAN Lo, 2 CAN Hi, 3 speed signal, 4 speed ground, 6–11 = sections 11–16, 12 speed power.
  • CAN Switch Box or Switch Pro (boom sense built in): swap-map the dead section to a different switch. If the problem stays with the switch, the box needs repair. If it follows the section, the section isn't configured — check its width and product assignment.
  • Product controller node with boom sense unlock: runs on master sense only (remote/foot switch through the 3-pin Deutsch "Remote Switch" on the chassis power cable; NH3 can use the "Remote Proximity Sensor" on the AccuFlow node cable). Master sense is pin P2 at the node. No voltage → make sure every CAN/Power tee has its "Node" connector toward the node cabling and "To Terminator or Extension Tee" toward the next tee or terminator.
Rate control

Speed reads when the machine is parked

  • Inspect speed connections for water, corrosion, loose pins — a short makes distance count up.
  • Radar: vibration or water inside (pressure washing). Let it dry completely; still bad → repair/replace.
  • Simulated radar from GPS: the receiver sends pulses at 0.1–0.2 mph drift. Raise Min Speed: Phoenix 200/300 — Home, right arrow to Utility Options, down to Radar Config, right to Min Speed, set 0.25 mph (don't exceed 1 mph). Invicta 210/310 — Utility Options > MinSpd from 00 to 01.
  • Speed to more than one console: radar/wheel Y-cable 115-0159-472; Dickey-John interface 115-0159-552; simulated radar splitter 115-0171-216; GPS serial Y 115-0171-689.
Rate control

Spinner / fan speed reads zero (CAN & ISO)

  1. Spinner control programmed and at least one section assigned to the spinner product (section shows enabled when switched on).
  2. Unplug the fan RPM sensor (3-pin Weatherpack) on the control cable. Referenced to ground: A Power 12 V, B Ground, C Signal 5 V. No power on the cable ground but power using chassis ground → cable ground is bad.
  3. No voltage at the sensor plug → test at the node: single product node (063-0172-373 / 063-0173-304) pin 9 12 V, 7 ground, 8 5 V signal. Dual product node (063-0172-315) R1 12 V, T2 ground, T3 signal. Multi-product/ISO node (063-0173-236 / 063-0173-006) L3 12 V (with cable 115-0171-945; other cables may use S1 and 5 V), X3 signal (not on the 16-pin liquid cable 115-0171-949). Voltage at node but not at the plug → spinner or product cable bad. None at the node → node bad (on a dual product node, assuming product 1 still works).
  4. Short/no-short: meter cal or density = 1 for the spinner product, Manual, section on, short Ground to Signal at the 3-pin while watching Actual Rate. Number appears → sensor bad. Zero → repeat at the node pins: number → cable bad; zero → node bad.
  5. RPM shows but the valve won't control → test the spinner control valve like any control valve.
Rate control

Spinner / fan speed reads zero (SCS console)

  • Fan Cal in the Data menu = number of bolt heads on the sensor target.
  • At the 3-pin Weatherpack: A 12 V, B ground, C signal 0 V. Console cable pins: 1 ground, 5 signal, 14 12 V.
  • Short/no-short: watch Fan RPM in the Data menu and short Power to Signal. Number → sensor bad. Zero → short pins 5 and 14 on the console cable: number → product/extension cable bad; zero → console or console cable.
Rate control

SCS console: reset to defaults, clear values, "ENTER CODE"

Write down boom cals, valve cal, meter cal, speed cal, and speed type first.

  • SCS 330/340/360/550: switch to OFF, hold CE while switching to AUTO or MAN → "US".
  • SCS 440 old 2-window (063-0159-531): unplug the 16-pin power, pull the 9 V battery (rear panel) and the 15 A fuse, wait 30 s, reconnect → "CAL" / "US". Middle versions: hold SELF TEST 30 s.
  • SCS 440 current 28-character (063-0171-183), 450, 460, 600, 660, 661, 700, 710: power off, hold CE and switch power on. Nothing works → remove power for 30 minutes.
  • SCS 4000/4400/4600/5000: hold CE, press POWER to shut down, keep holding CE, press POWER to turn on, hold CE 5 more seconds.
  • Clearing a total: press the value key, Enter, 0, Enter. "ENTER CODE" means Data Lock — without the code, a full reset is required.
Rate control

RCM (Rate Control Module) notes

  • Master/section sense options: foot switch 063-0173-080 or paddle switch 115-0172-422 (with cable 115-0172-397 12 ft or 115-0172-398 23 ft); ISO Switchbox 063-0173-577 (kits 117-6020-004 Viper 4/4+, -002 GS 2630, -003 Pro 700/Intelliview) — no foot switch needed; or tie into existing switches with ISO Boom Speed ECU 063-0173-635 and cable 115-7300-091.
  • 5 V granular encoders on an RCM (built for 12 V encoders): adapter 115-0159-716, or legacy product cable adapters 115-7347-012 (16-pin), -022 (22-pin), -008 (37-pin).
  • GPS speed over Raven CANbus needs boom/speed node 1.7+, Switch Pro 1.7+, or CAN Switch Box 1.5+; Envizio Pro 3.3+, Viper Pro 3.7+, any Viper 4. Speed type Radar, speed cal 1000.
  • Turning multi-product node channels on/off: enter valve cal 900X (X = number of products) in Valve Cal 1 of the node's first channel; e.g., 9003. Only up to the node's unlocked level. Viper 4: CAN System tab > Product Controller Reset. Re-enter the real valve cal afterward.

Sections & AccuBoom

Sections & AccuBoom

Sections not painting on the map

Most common causes, in order:

  1. Section widths entered wrong.
  2. Sections not associated with the product. Envizio Pro: Tools > Product Control > Section Assignments — every boom checked. Viper Pro: Product Control > Boom Cals — all booms checked, and the Booms button on the Product Setup page at job start must say "All" (not Single or Multiple). Viper 4: Product Control > Section Settings — all sections checked for the product.
  3. AccuBoom not set to control the product/sections, or not enabled for the job. Envizio Pro: Tools > Product Control > AccuBoom > "Apply to all products", and AccuBoom Enabled on the Start Job – Verify Settings screen. Viper Pro: booms section on Home > Next > booms checked and Enable checked; New Job screen: AccuBoom Control checked. Viper 4: AccuBoom applied to products and enabled.
  4. No boom sense from the machine's switches — the node must see 12 V from each switch. See "Testing boom sense" under Rate control.
Sections & AccuBoom

AccuBoom sections won't turn on, or stay on

  • Settings above first. If a combo node is installed, "AccuBoom Combo Node" must be checked; if not installed, it must be unchecked.
  • Switch positions: serial product control (SCS console) — boom switches must be OFF for AccuBoom to run them. CAN product control — switches must be ON or in ACCU.
  • Ground speed: AccuBoom will not turn sections on with a self-test speed. It needs real speed (wheel magnet, radar, or GPS). After stopping, it may be necessary to cycle the master switch.
  • Node lights: Logic and HC Power solid, Micro 1 Hz and CAN Rx/Tx flashing. Diag 1 lights when the node sees master sense — without master sense, AccuBoom will not control sections.
  • Level 1 product controller nodes (063-0173-341) cannot do AccuBoom automatic section control at all, even with the boom sense unlock (AccuBoom on a single-product node is only available in granular modes). A level 2 (063-0173-236) or level 3 (063-0173-367) node, or a level 2 unlock (077-0180-065), is required. Only one product controller node per CANbus.
Sections & AccuBoom

Sections turn on/off too early or too late

  • Machine measurements and antenna offsets are the usual cause, especially when a machine moves between displays. Envizio Pro and Viper Pro measure the fore/aft antenna offset relative to the boom; Viper 4 measures it relative to the rear axle with a separate boom offset.
  • Turn-On Look Ahead normally starts at 1.5–2 seconds; increase it if sections come on late or the system can't build pressure in time. Turn-Off Look Ahead normally 0–0.5 s; increase if sections turn off late. Always keep Turn-On higher than Turn-Off.
  • Outer sections skipping across point rows on big booms: AccuBoom Aggressiveness — Off 0 %, Low 15 %, Medium 35 %, High 60 %, Very High 100 %. Recommended: Envizio Pro Off, Viper Pro Very High.

CANbus & ISOBUS

CANbus & ISOBUS

Node lights — what they mean

  • Logic Power: solid when 12 V logic power is present. HC Power: solid when 12 V high-current power is present.
  • Micro 1 Hz: flashes once per second when the processor is running. (If an AccuBoom master-sense system flashes very fast when the master switch is on, the console isn't sending the CAN "expect master" message — CAN communication problem.)
  • CAN Rx / CAN Tx: flash when messages are coming in / going out.
  • Diag 1: AccuBoom — lit when master or any section switch is on. AutoBoom — a second ultrasonic sensor detected. SmarTrax/SmartSteer — receiving GPS. Product controller/air cart/planter aux — solid = calibration incomplete (missing rate, meter, or valve cal); flashing = receiving meter/encoder pulses.
  • Diag 2: AccuBoom — wireless remote section controller in use. SmarTrax — 3D unlock accepted. Product controller — spinner/fan/pump RPM pulses (Gran 3), or key presses from a remote section controller.
  • No Micro 1 Hz on most nodes after a storm = probable lightning damage. No HC/Logic lights = blown fuses.
CANbus & ISOBUS

Is it a Raven CAN cable or an ISOBUS cable?

The 16-pin round connectors look alike. If all four spade pins (1, 7, 10, 15) are populated, it's Raven Gen II CANbus. If only spade pins 1 and 10 are populated, it's ISOBUS.

CANbus & ISOBUS

CAN cable voltage tests

Gen I (4-pin): 1 CAN Power, 2 CAN High, 3 CAN Ground, 4 CAN Low. Pins 1–3: +12 V. 2–3 and 3–4: 2.5 V (±1 V). 2–4: 75 ohms with two terminators, 150 with one. Terminator 063-0172-369 reads 150 ohms across pins 2 and 4.

Gen II (16-pin): 1 HC Ground 1 · 3 Switched Logic Power · 4 Logic Ground · 5 CAN Power · 6 CAN High · 7 HC Ground 2 · 8 CAN Ground · 9 CAN Low · 10 HC Power 1 · 14 Remote Master Signal · 15 HC Power 2. Tests: 1–10, 7–15, 3–4, 5–8 all +12 V; 6–8 and 8–9 2.5 V (±1); 6–9 75 ohms (two terminators) or 150 (one). Terminator 063-0173-224 reads 150 ohms across 6 and 9.

Rule: a CANbus must have exactly two terminators — one near the display, one at the far end. Hawkeye and SmarTrax MD have their own sub-buses, so a machine may have more than two total.
CANbus & ISOBUS

ISO cable voltage tests

  • ISO 16-pin: 1 HC Ground 1, 3 Switched Logic Power, 4 Logic Ground, 6 CAN High, 9 CAN Low, 10 HC Power 1, 14 Remote Master. 1–10 and 3–4: +12 V. 1–6 and 1–9: 2.5 V (±1). 1–14: +12 V when the switch is active.
  • Terminator adapter (22-pin): 22–1, 3–4, 5–8: +12 V; 6–8 and 8–9: 2.5 V (±1); 14–1: +12 V with switch active.
  • Terminator adapter 6-pin: B Power, D Ground, E CAN High, F CAN Low. D–B 12 V; D–E and D–F 2.5 V (±1).
  • IBBC 9-pin: 1 HC Ground, 2 Logic Ground, 3 HC Power, 4 Logic Power, 6 CAN Power, 7 CAN Ground, 8 CAN High, 9 CAN Low. 1–3, 2–4, 6–7: +12 V; 7–8 and 7–9: 2.5 V (±1).
CANbus & ISOBUS

Losing nodes or losing calibration

  • Field computer updated recently? Update every node too — mixed software versions drop nodes and cals.
  • Machine jump-started with the CAN system connected? The surge usually blows fuses.
  • Voltage dips and spikes from a weak electrical system knock nodes offline intermittently. Check CAN/ISO voltages with the machine running and look for movement.
  • A pinched or broken wire causing sudden voltage drops will make a node lose its calibration. Test each connection.
  • Lightning: Micro 1 Hz dark on most nodes; blown fuses show as no HC/Logic lights.
CANbus & ISOBUS

Node update failed

  • Machine must be running (steady 12 V) and cabling must have a good ground.
  • USB: too large a drive can fail to launch; old drives get slow and fail; never bump or remove the drive mid-update (corrupts the files for next time too).
  • CAN voltages: HC and Logic 12 V; CAN High and Low about 2.5 V (±1). Check for corroded or pinched cable and for exactly two terminators.
  • Wrong program number: check the node's program number (e.g., P144V111 = program 144, version 111) against the update. Loading the wrong one means a repair trip. SmartSteer/SmarTrax nodes use program 269 (SmartSteer can't go past 6.0.17); SmarTrax MD uses 339.
  • Recovery (CAN nodes only): Viper 4 — Administrator Panel > System Manager > Hardware Update > Recovery Mode; pull the node's logic power fuse ~5 s, wait for LEDs to go dark, select the update, Apply. Envizio Pro — after the "node may not be usable" error, cycle logic power 5 s, then go to the node update screen without selecting a node → "Node Recovery Mode" > Accept > pick the correct version > Program Node. Two failures → send the node in. ISO nodes can only be recovered with the Raven Service Tool.
CANbus & ISOBUS

How to update nodes

  • Viper 4: download the CAN or ISO upload package from the Raven portal, extract to the USB root (folder CANUpload or ISOUpload). Administrator Panel > File Manager > USB Manager > file type "Node Update" > select > Copy. Then System Manager > Hardware Update > select node > pick version by program number > Apply Update. Viper 4 software 2.3.0.555+ bundles CAN node updates; 2.7+ can update ISO nodes.
  • CR7/CR12: software 2.0+ for ISO nodes (CAN nodes need the Service Tool). HEX files at USB root. Settings > File Manager > pick USB > check files > Copy. Settings > Software Update > Hardware tab > device > version > Start Update.
  • Raven Service Tool (laptop + CAN adapter): connect, Browse to the USB software, right-click the node > Program. Compatible nodes highlight blue; a gray Program option means wrong software. Failed → disconnect, reconnect, start over.
  • CR7 with SmarTrax or AccuBoom CAN nodes needs minimum node software — see Raven article "CR7 and CAN Node Compatibility".

AutoBoom (UltraGlide / PowerGlide Plus)

AutoBoom

Booms drop when engaging, won't lift, or act strangely

Work in this order: check settings or recalibrate → test electrical → test hydraulics. Base values creep, so a recalibration often fixes it. Calibrate with the target height at 30 in. or higher and the engine at operating RPM.

  • Center rack goes up but won't come back down: many machines need a boom valve and/or master apply switch enabled for center rack control to lower it.
  • Opposite boom reacts when one side hits something: Stability too low (opposite boom raises) or too high (opposite boom drops); inner/outer ultrasonic sensor connections reversed; proportional valve connections reversed or one side unplugged; a sticking proportional valve.
  • Speed setting table: 0–99 for static pressure 900–1800 psi (most machines); 100–199 for heavy booms over 1800 psi (100 % duty to lift); 200–255 for light booms under 900 psi. A machine-database profile can lock you into a narrow range (about ±20); reset defaults and choose Standard0, Standard100, or Standard200 to open it up.
AutoBoom

Fine tuning Sensitivity, Speed, Stability

Tune in that order after a calibration; only Sensitivity should need touching through the season.

  • Sensitivity = how much height change makes the boom react. Raise a hand or cardboard from the ground; adjust until the boom reacts at the height change you want. Low = ignores small changes; high = reacts to grass moving. Lower early season (ground reference), raise with a full canopy (crop reference).
  • Speed = how fast the boom returns to target after reacting. Lift your hand about 1 m/s, then pull it out; the boom should follow at roughly the same speed. Low = booms hang in the air; high = lifts too soon and too high, causing streaks.
  • Stability = keeps the opposite boom from dropping when one side reacts. Pop a hand under one sensor; the other side should rise slightly. Low = opposite boom shoots up; high = opposite boom drops.
AutoBoom

Electrical troubleshooting

  • 2-pin Deutsch "Solenoid" connectors go to the blockers; "Prop" connectors go to the proportional valves. Wire colors: Left Solenoid White+Blue, Left Prop Red+White, Right Solenoid Violet+White, Right Prop Orange+White.
  • From the Diagnostic screen command up/down: blockers should output 12 V; proportional connections show variable voltage. Prop valve reference (control node): manual raise ≈ 8, manual lower ≈ 4, normal 4–8. Blocker: 0 V disengaged, 12 V engaged or trying to raise/lower.
  • Pressure transducer signal vs. pressure: 100 psi 12.65 V · 500 12.12 · 1000 11.45 · 1500 10.78 · 2000 10.11 · 2500 9.39 · 3000 8.74.
  • One side works: swap left and right connections and repeat. If the problem moves, it's electrical; if it stays, it's hydraulic. No control from the Diagnostic screen at all: no voltage = node/cabling; voltage present = hydraulic/valve; also suspect boom sense adapters or sensor connections.
AutoBoom

Hydraulic troubleshooting

Machine running, booms unfolded:

  1. Press the top of the blocker cartridge — booms should lower (old blocks may need a hammer and punch).
  2. Remove the proportional valve cap, screw the adjustment all the way in with an allen wrench.
  3. Press the blocker again — booms should raise.
  4. Back the adjustments all the way out and reinstall the caps.

Suspect a bad valve: swap left and right proportional valves (never a prop with a blocker). Problem follows the valve = valve; stays with the boom = valve block or machine hydraulics. Check hydraulic filters — contaminated oil sticks proportional valves.

  • Pull-type sprayers with a hydraulic product pump: Raven recommends open-center hydraulics to keep pressure and oil temperature down; closed-center at high pressure plus a high-flow pump overheats the oil.
  • RoGators with the add-on HYDAC valve 063-0131-131 that won't calibrate in UltraGlide: needle valves in ports 11 must be turned all the way in (out for PowerGlide Plus); check the orifices in ports 12 are intact and seated.
AutoBoom

UltraGlide sensor test (3- and 5-sensor systems)

First confirm node LEDs: Logic and HC Power lit, Micro 1 Hz, CAN Rx and Tx flashing (Diag 1/2 lit when a second sensor is on either boom).

Unfold and lower the booms fully, open the Diagnostic menu, note every sensor height, then raise both booms. 3-sensor: all three change. 5-sensor: outer sensors change, inner and center don't.

A sensor whose reading doesn't change:

  • Power light lit (yellow-green-yellow) and clicking: bypass the extension cable by plugging the sensor straight into the harness. Works → extension cable bad. Doesn't → check harness voltage/continuity; good harness → replace the node; bad harness → replace the harness. Only one side reads: swap the left and right outer sensor connections.
  • No light or no clicking: swap in a known-good sensor first. Works → sensor bad. Then the extension cable → harness → node sequence above.
AutoBoom

G2 AutoBoom controller (older stand-alone box)

  • "Boot Error": update to the latest G2 software (Raven Tech Service) or reset defaults: Menu > 4 Calibration > 1 OK > 1 confirm > 4 Reset to default > 1 OK > restart.
  • "P" = pressure below the alarm set point, or the pressure transducer not detected. Check the transducer connector orientation on the valve block — the #1 tang aligns with #1 on the plug, white dots aligned.
  • "U" = ultrasonic too low (under 10 in.), too high (over 65 in. for 5 s), or sensor not detected. Check sensor connectors for corrosion.
  • Auto pressure lights don't light when tapping boom down: check interface wiring at the main boom solenoid valves (Left Up White, Left Down Red, Right Up Green, Right Down Black). Left light comes on for right-down: sense lines reversed.
  • Setup: most common mistake is too aggressive — start Up Speed and Down Speed dials at 2–3 and reaction time 5, step up one at a time. Booms only move for a height change over 2 in.
AutoBoom

ISO AutoBoom loses calibration every power cycle

ISO AutoBoom software 4.0 and earlier on nodes 063-0130-016 (rev before C), -022 rev A (John Deere), -024 rev A (XT), -040 (ET). Fix is software 5.01 with a new boot loader — the node must go back to Raven. Do not load it with the Service Tool; that corrupts the node. Already updated: -016 serial 101192 and up, -022 220414 and up, -024 100118 and up.

AutoBoom

AutoBoom XRT sensor pinouts

Radar 4-pin AMP: 1 Red logic power, 2 Yellow CAN Hi, 3 Black logic ground, 4 Green CAN Lo. Boom angle sensor 3-pin Weatherpack: A Red/White 5 V, B Gray signal, C Black ground. Proximity sensor 2-pin: A power, B signal.

Hawkeye & Hawkeye 2 nozzle control

Hawkeye & Hawkeye 2 nozzle control

Nozzle control valve (NCV) light codes

Light Meaning
Green flashing 1 Hz Ready (in actuating mode: ready but needs calibration)
Blue flashing 1 Hz Actuating — Auto
Red flashing 1 Hz Loading new software
Amber flashing 1 Hz Alarm active
Amber flashing 5 Hz No ISOBUS communication
Blue/Green alternating Actuating — Manual
Green/Magenta alternating Not calibrated — switch input high
Red/Magenta alternating Not calibrated — switch input has not changed
Amber/Red alternating No ECU detected or invalid ISO name
Amber/Green alternating Ready, warning alarm active
Amber/Blue alternating Actuating, warning alarm active
Solid any color NCV failure
Dark No power, or NCV failure

1 Hz = once per second, 5 Hz = five times per second.

Hawkeye & Hawkeye 2 nozzle control

How indexing works (and why order matters)

Hawkeye always indexes the left side first, center to tip, then the right side. The ECU sends 8.5 V (±1) to the first left NCV; each NCV that indexes passes 3 V to the next one outward. The right side starts with 11.5 V (±1). After indexing, valves are numbered left tip to right tip.

Hawkeye & Hawkeye 2 nozzle control

Specific nozzles won't index

  • Inspect those NCVs and their connections for damage or a loose plug. Count how many indexed left and right.
  • Read the lights (table above).
  • Reset to defaults: Hawkeye menu > Tools > ISO Info > Reset Defaults.
  • Swap the suspect NCV with a spare from the service kit or a known-good one, re-run the calibration wizard, and see whether the problem follows the NCV or stays with the connection. A faulty NCV can be replaced temporarily with the jumper plug 115-7303-139 (Hawkeye) or 115-2005-070 (Hawkeye 2); the system must be fully re-indexed.
Hawkeye & Hawkeye 2 nozzle control

Random nozzles won't index

  • Likely software on the ECU or display, or a bad terminator/cable. Verify counts, read the lights, clear ISOBUS data (ISOBUS Status > Pool Management > Clear ISOBUS Data > restart machine), disconnect the battery 5–10 minutes and index again, inspect terminators, re-run the calibration wizard, reset defaults, update the Hawkeye ECU and display software.
  • You can spray conventionally until it's fixed (see below).
Hawkeye & Hawkeye 2 nozzle control

Hawkeye 2: "Multiple Nozzle Offline" and two valves blinking blue

Two adjacent NCV2s blinking blue (one at 25 % duty, one at 75 %) with everything beyond them blinking red means the CAN link between those two valves is broken. Do not index, calibrate, or update software in this state.

  1. Run the CAN loopback test to find the pair. Inspect the cable-to-NCV junctions for corrosion or worn contacts.
  2. With the NCV2s removed, check: NCV CAN_HI–CAN_LO and CAN_HI_OUT–CAN_LO_OUT = 120 ohms ±10 %. Harness pin 2 (CAN_LO_OUT, center-rack side drop) to pin 8 (CAN_LO, tip side drop) ≈ 0 ohms; pin 3 (CAN_HI_OUT) to pin 7 (CAN_HI) ≈ 0 ohms. Pins 2 and 3 to pin 4 (HC_GND) and pin 6 (HC_PWR) = open. With only the tip-side NCV2 installed, pin 2–pin 3 on the center drop = 120 ohms ±10 %; with only the center-side NCV2 installed, pin 8–pin 7 on the tip drop = 120 ohms ±10 %.
  3. Any reading out of spec = cable. The NCV bridge cable 115-2005-109 (two drops) or 115-2005-358 (three drops) bypasses a damaged link — it's polarized ("Towards Boom Tip" label faces the tip), never plugs into the faulty drop itself, and only fully repairs a severed trunk on the outermost harness. Re-indexing won't fix a cable.
  4. All readings in spec = swap a replacement NCV2 into the center-rack side; if still blue, put the old one back and try the tip side. Blue clears → index and resume.
Hawkeye & Hawkeye 2 nozzle control

Operating modes and duty cycle

NCVs pulse at 10 Hz. Duty cycle is the percentage of each pulse the valve is open. Never apply below 25 % duty (lateral skips); choose a tip size that puts you around 70 % so turn compensation has room both directions. Wait a few minutes after changing modes for the object pool to load and DTCs to clear (green bell).

  • Standard: controls target rate and target pressure. Best general use in a narrow speed range. Watch tips and strainer with chalky or thick products.
  • Variable Pressure (VP): controls rate and holds 70 % duty by varying pressure. Widest speed range; you set only the rate.
  • High Flow: conventional tip and Hawkeye tip together (stacked nozzles required).
  • On/Off: NCV fully open when applying, closed when not. Air-induction tips OK; better for chalky/thick products.
  • Bypass (conventional): NCV stays closed; sprays through a conventional tip. Requires an alternate flow path at every nozzle body.
Hawkeye & Hawkeye 2 nozzle control

Conventional spraying method (Hawkeye disabled)

Hawkeye menu > Tools > Equipment Settings > uncheck Nozzle Control. Open the manual shut-off on the conventional tip at each nozzle body. Only disable Nozzle Control if the nozzle bodies are set to bypass the NCVs — the NCVs stay closed when disabled. If the ECU sees no NCVs on the bus it unchecks Nozzle Control automatically.

Hawkeye & Hawkeye 2 nozzle control

Diagnostic cables and what to expect on the meter

Hawkeye (kit 117-1007-051). Never let the 2-pin test leads touch — it blows a fuse.

  • 6-pin nozzle diagnostic cable 115-7303-311, between an NCV and its drop: 1 Red HC Power 10.5–16 V · 2 Yellow CAN High 2.0–2.7 V · 3 Gray Switched OUT 2.5–3.2 V · 4 Green CAN Low 2.0–2.7 V · 5 Gray Switched IN 2.5–3.2 V (8–13 V on the first NCV of each left/right primary cable) · 6 Black HC Ground.
  • 19-pin boom harness cable 115-7303-312 (with terminator adapters 115-7300-044/-125 and active terminators 063-0172-964 to isolate boom sections): 4 CAN Low 2.0–2.7 · 5 CAN Power 12–14 · 6 CAN High 2.0–2.7 · 8/12/16 HC Power 1/2/3 10.5–16 · 19 Enable 2.5–3.2 (8–13 on the first 19-pin off the main ECU). HC Power 1 and 3 swap at every 19-pin connection — the cable labels may not show it.
  • Active terminator cable 115-7303-331 at the boom tips: B CAN Power 12–14, D ground, E CAN High and F CAN Low 2.0–2.7.
  • NCV CAN splitter 115-7300-029 (Service Tool port for NCV updates/logs); NCV programming cable 115-7303-157; ECU programming cable 115-0172-230 with CAN power tee kit 117-0159-923.

Hawkeye 2 (kit 117-2005-068):

  • 19-pin jumper 115-2005-069 isolates boom harness sections; 8-pin jumper 115-2005-070 replaces any NCV2 (system indexes normally with it in).
  • 8-pin nozzle diagnostic cable 115-2005-104 at an NCV2: 1 Gray Aux In 0–16 V · 2 Blue CAN Out Lo 1.4–2.5 · 3 Orange CAN Out Hi 1.4–2.5 · 4 Black HC Ground · 5 White Aux Out 0–13.5 · 6 Red HC Power 10.5–16 · 7 Yellow CAN In Hi 1.4–2.5 · 8 Green CAN In Lo 1.4–2.5.
  • 19-pin boom harness cable 115-2005-105: 3 CAN Return Hi, 4 CAN Lo, 6 CAN Hi, 7 CAN Return Lo (all 1.4–2.5 V) · 8/12/16 HC Power 1/2/3 10.5–16 · 17 Fence Row 10.5–16.
  • NCV drop extensions 115-0172-579 (6"), -580 (12"), -581 (36"); connector repair kit 117-2005-054.
Hawkeye & Hawkeye 2 nozzle control

Poppets and seals

Kits of 100 with all seals. Hawkeye NCV1 standard: 117-1005-210 TeeJet, -211 Hypro/Arag, -212 Wilger. Severe duty (both NCV1 and NCV2): 117-1005-216/-217/-218. Hawkeye 2 NCV2 standard: 117-2005-064/-065/-066. Severe duty has a yellow Viton seal (amine/high-pH chemistry), cross-milled backstop (closes faster, fewer stuck-open poppets), and a side hole for flushing and winterizing. NCV2 poppets have 4 flutes (faster response with viscous product) and a blue spring. All are interchangeable if chemically compatible — use one type across the whole boom.

Hawkeye & Hawkeye 2 nozzle control

Flow offset for wheel tracks (RCM-Sprayer / Hawkeye 2)

Home > Flow Offset > Offset Setup > choose Offset 1 or 2 > select up to 4 NCVs (green) > X > enter −50 to +50 % > enable the group > back. The Flow Offset button on the Home screen shows blue with no groups enabled and green when a group is active.

Hawkeye & Hawkeye 2 nozzle control

Hawkeye screen shows on the AGCO C1000 instead of the Viper 4

C1000 software 2.1.3 and older: ISOBUS Terminal Functions OFF. 3.1.2.150512 and newer: Terminal Generation UT 2, Terminal Functions ON, Terminal Number 2 (OFF disables the C1000 on this software). On reboot the C1000 boots first and alarms "No Primary Terminal available — System will reconfigure": ignore it, don't press Esc, and the Viper 4 takes over. Already acknowledged: reboot everything and ignore it, or use Switch Display on Hawkeye ECU 2.1.1.10+.

Direct injection (Sidekick / Sidekick Pro)

Direct injection

Sidekick Pro node lights

Logic Power and High Current Power solid when present. Micro 1 Hz: one flash per second = talking on the CANbus; four flashes per second = cannot communicate on the CANbus. Flow Switch: flashes once per pump revolution. Calibration Switch: flashes when metal passes the internal sensor (only after the console has calibrated the pump once).

Direct injection

Pump times out while priming, or won't calibrate

  • Priming needs the pressure transducer to see 9 psi after the line charges; the usual fix is calibrating the transducer. Also check for air being drawn into the suction side.
  • Transducer calibration: relieve all pressure, unscrew the transducer and let it hang (power connected), then enter a pressure cal of 0. Envizio Pro: Tools > Product Control > Calibration Settings > Press (1-2) Cal. Viper 4: Product Control > Pressure Settings. Viper Pro: Product Control > Pressure Settings. ISO: Tools/Settings icon.
  • The transducer on the Sidekick Pro is mandatory; a second one on the carrier line (422-0000-090) is recommended. The injection line must run at least 10 psi above the carrier line or chemical won't inject.
  • Plunger not rising: lubricate it; run a catch test. "Chasing" the meter cal: plunger sticking — lubricate or catch test.
  • Catch test: 1-gallon container, pump set to recirculate, disconnect the recirculation line at the top of the tank into the container, zero total volume, run until 1 gallon is caught, adjust the meter cal (new = current × controller volume ÷ measured), repeat. Reconnect the line.
Direct injection

Pump won't run

  • Master switch and at least one boom switch must be on.
  • Older Sidekick: unplug the tach feedback generator (2-pin Weatherpack) — the pump should run wide open. If not, the console cable may be connected backwards.
  • Sidekick Pro: calibrate the transducers, check the high-current breaker at the battery, note any error message.
Direct injection

Pump runs wide open

  • Older Sidekick: with the pump running there should be 9 V on the tach generator's 2-pin Weatherpack (thin red and black wires). No voltage = bad tach generator. Check console cable orientation, tach belt not broken or slipped, pulleys tight.
  • SCS Sidekick console: check settings; if correct, the console may be at fault. Sidekick Pro: rare — verify boom associations, especially with more than one pump.
Direct injection

Flow alarm

  • Restriction in the shuttle/piston channel (debris, chemical buildup) — regular maintenance prevents it.
  • Flow sensor out of adjustment: the line should run vertically with the LED on the left. If the LED doesn't flash, adjust the sensor while running at the lowest rate (1 oz/min on a 1–40 oz/min pump, 5 oz/min on a 5–200).
  • Pressure transducer needs calibration. Check valve too tight; bad o-rings or debris in the intake/discharge valves.
Direct injection

Vac alarm

  • Vacuum switch is normally closed. Unplug it from the product cable; on the switch-side female Weather Pack test continuity pin A to pin C: 0 ohms = good, open = bad (pin B unused).
  • Pump inlet no more than 2 ft [0.6 m] above the tank outlet (under 1 ft is best). Suction line under 5 ft [1.5 m] and at least 3/4 in. [1.9 cm] ID, chemically resistant.
  • Clean the pump strainer and check for obstructions between tank and pump; clean any other strainers and valves.
  • Thick chemical: dilute it, or it may not be suitable for injection at all.
Direct injection

Returning a pump or converting it (CAN / ISO / ICD)

Raven requires decontaminated units. Triple-rinse the pump (recirculate ~2 gallons of clean water, then inject at normal rate, three times), flush flow meters and valves with clean water for 2 minutes. Dirty returns get a cleaning fee up to $150 or come back untouched. Conversions: the RMA must say "Conversion Only" or "Conversion and Repair"; the ECU must stay on the motor. ECUs with black cover screws can't be converted (stainless screws can).

Anhydrous ammonia (AccuFlow, HP, HP Plus, Vortex)

Anhydrous ammonia

Bouncing or erratic NH3 rate

Normal erratic-rate troubleshooting applies (valve, flow meter, switches). NH3-specific:

  • Vapor through the flow meter makes the reading jump and the valve chase it. Vapor comes from pressure loss and rising temperature — stay in the non-vapor area of the pressure/temperature chart; on hot days slow down to keep pressure up.
  • Cooler maintenance: clean and inspect regularly so buildup doesn't restrict flow.
  • Flow meter damage: debris (usually a missing strainer) slows or stops the turbine. Running nurse tanks empty spins the turbine at high speed on vapor and wears the bearings — don't run tanks below 5 %.
Anhydrous ammonia

Over-application or uneven application

  • Over-application: the meter cal was entered as the liquid number. The flow meter tag has a separate NH3 cal in pounds of N (an RFM 60S is 710 for liquid but 168 for NH3). No tag: divide the regular meter cal by 4.22. The RFM 60S varies very little meter to meter, so 710 / 168 is a safe starting point; Raven's current flow meter article suggests 190 as an NH3 starting cal for the RFM 60S. Either way, confirm with a catch test.
  • Off-rate otherwise: use the normal rate troubleshooting steps.
  • Uneven application across the bar: hoses pinched or collapsed at the manifolds restrict some sections and push extra flow through others. Replace and re-route them where they can't pinch.
Anhydrous ammonia

NH3 coming out of the vapor tubes with the valves closed, or green streaks in the field

  • Double-check the plumbing, especially on a new install.
  • Internal O-rings and gaskets in the valves may be bad — replace as needed.
  • Multi-section setups need a check valve between the cooler and the flow divider. Without it, pressure left in the lines pushes leftover vapor and eventually liquid out of the vapor tubes when the manifold valves close.
  • Green streaks are liquid coming out of the vapor tubes, usually because there isn't enough restriction in the refrigerant inlet port to let the refrigerant expand. Try a smaller orifice in the refrigerant inlet.
Anhydrous ammonia

Frost buildup on the cooler or valves

Some frost on the cooler is normal; frost on the inlet valve, control valve, or downstream plumbing is not. Causes: pressure loss and restrictions. Clean ports with compressed air or a pipe brush, clean the strainers, and make sure plumbing isn't undersized or full of unnecessary elbows.

Anhydrous ammonia

Valves not opening

  • Master/section valves (1-1/4" 063-0173-203 for AccuFlow/HP; 1-1/2" 063-0173-668 for Vortex/HP Plus): Power 12 V, Ground, Signal, Status (Status not wired on AccuFlow/HP). 12 V on Signal opens the valve.
  • Control valve (1" 063-0172-977; 1-1/2" 063-0173-667): Power 12 V, Ground, Increase, Decrease. Single-valve systems must be set to Fast Close (C-FC).
  • Clean and inspect valves and strainers regularly.
Anhydrous ammonia

Plumbing for capacity (fewer vapor problems)

Big plumbing = less pressure drop = less vapor = more capacity. Nurse tanks with high-flow withdrawal valves and 1-1/2" dip tubes; 1-1/2" ID hoses (1-1/4" minimum) as short as safely possible — at 35 GPM a 1-1/4" hose loses about three times the pressure per foot of a 1-1/2"; high-flow safety disconnects; tandem tanks as the minimum for HP, HP Plus, and Vortex; each tank its own hose or one oversized shared line; no elbows on the supply side. Vapor rows get more nitrogen than liquid rows — use four vapor knives per cooler on non-adjacent rows.

Anhydrous ammonia

NH3 Boost mode (Viper 4)

Product 2 = NH3 Boost. Rate bump 5 psi. Auto-populated: PWM Close, valve cal 31, preset PWM 70, min PWM 70, max PWM 208, PWM frequency 122. With pressure stable, the cooler gauge should match the nurse tank gauge within 5 psi; calibrate the transducer to the cooler gauge. Target for Product 2: 40–80 psi.

Steering (SmarTrax, SmarTrax MD, RS1)

If steering weaves or reacts slowly, check the machine first: play in the steering linkage, hydraulic condition, tire pressure. Auto-steer can't fix a worn machine.

Steering

SmarTrax won't engage

  • GPS must reach the SmarTrax node. External receiver: receiver output → SmarTrax node/control box DGPS input → node output (or control box Lightbar port) → field computer DGPS input. Internal GPS: field computer output → node input → node output → field computer input.
  • GPS source setting: Viper Pro = Generic GPS; Envizio Pro = Internal via Tilt or SmarTrax; Viper 4 = SmarTrax GPS on DGPS.
  • NMEA messages: GGA 10 Hz, VTG 10 Hz, ZDA 0.2 Hz. Baud rates must match: receiver output to SmarTrax 19200 = GPS baud in SmarTrax settings 19200; SmarTrax output to field computer 115200.
  • Watch the switch status change: on the long-box controller "foot swtch / steer swtch" go upper-case when pressed; Envizio Pro and Viper 4 show green vs. red; Viper Pro shows upper vs. lower case. No change = switch or wiring.
  • Engagement speed windows: stand-alone controller 1.5–14 mph; CAN SmarTrax below firmware 7.4 1.5–14 mph, 7.4+ 0–18 mph (SmarTrax MD must engage above 2 mph); RS1, SC1, and TC1 engage from 0 to 18 mph.
  • Too slow: stand-alone and CAN SmarTrax stop steering below 1 mph and disengage after 7 s (stand-alone and CAN below 7.4) or 20 s (CAN 7.4+). RS1/SC1/TC1 disengage after 30 s below 0.34 mph (0.045 mph on RTK).
  • Too fast: 27 mph for CAN SmarTrax and RS1 (22 mph on stand-alone firmware 2.1 and older) — "Too Fast" alarm, disengage after 5 s, and immediate disengage 1 mph over that. RS1 and SC1 cut out at 29 mph; TC1 tops out at 12 mph. NMEA at 5 Hz limits a stand-alone system to about 10 mph.
  • Reverse steering works within those same windows (7/20/30 s to reach minimum speed backwards) but not on articulated machines.
Steering

SmarTrax weaving or line acquire

  • Slow, gradual weave: verify antenna fore/aft; raise PWM values 1–2 % at a time; raise On-Line sensitivity (OL) 1–2 at a time, waiting 30–40 s between changes; inspect the steering sensor; check for mechanical play.
  • Jerky weave: sensitivity or PWM Min too high. PWM Min is normally 20–40 %; above 40 % is suspect — lower it 1–2 % at a time; lower OL 1–2 at a time.
  • Not acquiring the line fast enough: verify antenna fore/aft; Line Acquire (LA) too low — raise 1–2 at a time; point the machine down the line before engaging.
  • Over-steers acquiring the line: LA too high — lower 1–2 at a time.
  • LA works beyond 24–36 in. from the line; OL works inside that. PWM Min/Max affect both. A good calibration on flat, firm ground beats all of this.
Steering

RS1 fine tuning (in this order)

  1. Valve Minimums (Tools > Steering Setup > Wheel Control Settings), typical 0–40: wheels should just barely move, steadily, about 1°/s. Raise if movement starts and stops; lower if it's quick. Tune these after a Quick Calibration; verify after an Auto Calibration.
  2. Valve Maximums, typical 70–100: rarely changed; raise if the machine turns too slowly.
  3. Response Speed (Home), 1–255, typical 100, step 10: raise if the wheels wander slowly; lower if they twitch or saw on the line. Set about 10 below "too much"; lower a little at slower speeds.
  4. Sensitivity (Home), 50–200, typical 100: raise if the machine hangs off the line; lower if it crosses back and forth.
  5. Line Acquire (Home), 10–200, typical 50–100: raise if lazy; lower if it overshoots. Max G-Force (Advanced Tuning), typical 50–70, limits turn sharpness — raise it and lower LA together, or vice versa.
  6. Last Pass Sensitivity (Home), typical 115–145: too high steers inside a curve, too low outside (Last Pass and A-B curves only).
  • Antenna Shift (tractors): flag the hitch pin on a line, turn around, stop on the line; half the offset is the shift (right of the flag = positive).
  • Leave the advanced navigation and wheel PID gains alone unless you know what they do; an Auto Calibration sets them.
Steering

RS1 lights and DTCs

  • LED should always flash. Green 1 Hz = calibrated, no DTCs. Yellow 1 Hz = not calibrated or active DTC. Yellow 10 Hz = no ISO CAN. Red solid = bootloader; red flashing = invalid hardware. Blue solid = reprogramming. Red/green = OS fault; blue/green = hard fault; red/blue = programming.
  • DTC 522250.31 "No Guidance Points" is normal outside a job or before a line is set.
  • 12-pin plug: 1 power in (12–24 V), 2 ground, 3 switched power, 4 logic ground out, 5/6 ISO CAN2 Lo/Hi, 7/8 ISO CAN1 Hi/Lo, 9 GPS/radar out, 10 12 V engage switch, 11/12 modem TX/RX. With the machine running there should be at least 13 V at the batteries and at the RS1 (pins 1–2 and 3–2).
  • Updating RS1 from a Viper 4+ by USB gives "WiFi Invalid Server Config": the RS1's Ethernet is plugged into something other than the Viper 4+/Field Hub, or the RS1 is joined to a Wi-Fi hotspot (so it can't broadcast), or it shipped with 1.5.0.90. Update over the air through Slingshot, or run Ethernet from the RS1 to Viper 4+ port 3; for 1.5.0.90 toggle Wi-Fi mode Raven Auto → Manual-Client → Raven Auto, reboot everything (unplug the 12-pin for 60 s), then update.
Steering

SmarTrax MD error messages

Message Cause What to do
HC Volt H supply over 16 V check battery voltage and connections
HC Volt L supply under 10.6 V check battery voltage and connections
HS Fail / No HC Sync / Torque H mechanical drive hardware (Torque H = over 8 A, check for binding first) Manual Steering screen; toggle master switch — Raven logo goes white to blue; drive the motor and watch Actual Current; no current = replace the drive
HW Wrong software not supported by hardware reprogram with the correct version
MsSw Fail drive hardware toggle master switch; replace drive
MsSw Off master switch off switch under the MDU to ON
Oper Error presence switch disconnected over 7 s check the presence switch connection
OpSW Fail out of seat over 2 s return to the seat; check connections

SmarTrax MD uses program 339 for updates and RTK accuracy is guaranteed only at 5 mph or less.

Steering

Steering sensor voltages (SPS / WAS / yaw)

Find the SPS number: long box — Home, down to "Hold → To Enter Advanced Menu", hold right to Vehicle Setup, right to Status, down once. Cruizer/Envizio Pro — Tools > Steering Settings > SmarTrax Information. Viper 4 — SmarTrax > Sensor Status. Viper Pro — SmarTrax box > STX Setup.

  • SPS/WAS 3-pin triangular: A ground, B signal, C power (5 or 12 V). Power–ground 5 or 12 V; power–signal 4.5–12 V; signal–ground 0 V. Jump power to signal: SPS should go above 1000; unplugged it reads 0. Correct voltage and the jump works = sensor bad. Wrong voltage or no jump = cable or node. Adapters: 063-0181-014 (black rotary sensor 063-0181-013) and 115-4001-232 (linear sensor) — test at the adapter first.
  • Yaw sensor plug (on the valve cable): 1 power 12 V, 2 signal, 3 ground, 4 power 5 V. 12 V–signal 12 V; 12 V–ground 12 V; signal–5 V 4.5–5 V; signal–ground 0; ground–5 V 5 V.
  • Normal yaw: long-box controller Zero Yaw Rate ±1.0 stationary, Yaw Rate ±0.2°, SPS 500–525 parked. SmarTrax/SmartSteer nodes Zero Yaw ±2.0. Out of range or erratic = power, cabling, or the sensor/node.
Steering

Steering valve voltages (use manual steering from the display)

  • Square-connector valves (334-0003-064/-066): single connector — left 12 V between pins 1 and 3, right between 1 and 2; two connectors — pins 1 and 2 on the left or right connector.
  • 2-pin valves (063-0131-129/-130): 12 V on the left connector at full left, right at full right; both blocker 2-pin connectors also read 12 V at full output.
  • Sauer-Danfoss 4-pin (334-0003-089): 1 signal, 2 error, 3 ground, 4 power. Signal = half of machine voltage straight, +3 V full right, −3 V full left (13 V machine: 3.5 / 6.5 / 9.5 V).
Steering

3D calibration warning

Never cancel the 3D compensation step. A cancelled 3D cal is stored as complete, works on flat ground, and goes badly in rough terrain. Envizio Pro/Cruizer II: Tools > Steering > 3D Setup > Calibrate 3D. Viper 4: SmarTrax > 3D Comp > Calibrate. Viper Pro: SmarTrax box > 3D Setup > Calibrate 3D.

GPS

GPS

Line jumps during a job

  • Using SmarTrax? Bypass 3D. If the jump stops, the SmarTrax node needs repair.
  • PRN satellite: Auto is the recommended default. Locking to one PRN gives a consistent source and can stop 3–6 ft jumps on older receivers, but if that satellite goes down the receiver loses differential entirely and won't switch (WAAS PRN 133 was retired in 2017). If you lock, pick the PRN with the best signal-to-noise (over 50 is ideal); time of day matters when set to Auto.
GPS

Line has shifted (same line, new job)

Drift. Lines and boundaries made under WAAS/SBAS move over time as satellites move; only RTK repeats. Use Nudge during the job (Envizio Pro and Viper Pro nudge buttons; Viper 4 nudge widget).

GPS

No GPS at all

  • Inspect antenna and cable for sharp bends or damage; nothing blocking the sky view.
  • Voltage: 12 V to the receiver when the machine is off (10 V or less suggests a weak battery); 5 V to the antenna.
  • SmarTrax settings and baud rates (see "SmarTrax won't engage").
GPS

GPS signal but no differential

  1. Try a different PRN or Auto. 2. Receiver voltage (some receivers show it). 3. 5 V at the antenna. 4. Cycle power and wait 5 minutes. 5. Clear view of the sky. 6. Note settings, re-initialize the receiver, wait 5 minutes. 7. Signal-to-noise for the PRN (over 50 ideal). Still nothing = receiver, antenna, or cable. Differential dropping in and out is usually a bad power or ground — test while it's happening.
GPS

GPS mode / GGA quality numbers

0 no satellites · 1 satellites but no differential · 2 SBAS/WAAS lock (GS converging) · 4 RTK fixed · 5 RTK float, or converged OmniSTAR HP/XP and Satellite GS. Envizio Pro/Cruizer: Tools > GPS > Health. Viper 4: GPS status widget.

GPS

RS1 not finding satellites or not converging

  • 300 ft from bins, silos, sheds, trees, power lines; other roof antennas (Slingshot cellular, two-way radio, RTK radio) at least 3 ft from the RS1; nothing on the roof taller than the RS1; don't key a radio mic; clear view of the southern sky.
  • Unused 7+ days: leave it powered 30 minutes with the right correction source selected so the almanac updates. Should track within 5 minutes with clear sky.
  • 13 V minimum at the RS1 with the engine running.
  • Tracking but not converging: correct source (SBAS, Satellite GS, RTK)? PRN on Auto? GS/RTK won't converge but SBAS will = subscription, unlock, or RTK input.
  • New-profile SBAS convergence stuck past 15 minutes: check the alarm list for 523854.11 (almanac error — wait up to 15 min); set the differential satellite from Auto to a specific PRN (131 or 135 — Raven's article also lists 133, but that satellite was retired in 2017) and wait 10 minutes; if it converges set it back to Auto; otherwise unplug the 12-pin for one minute and repeat. Two power cycles without success — call support with the GNSS serial (RS1 object pool > Diagnostic > Information > GPS Receiver).
GPS

What accuracy to expect

Autonomous GL1DE 12 in. pass-to-pass, no repeatability · SBAS/WAAS 9 in. pass-to-pass, under 1 m repeatability · Satellite GS-Lite 12 in. / under 20 in. · Satellite GS under 2.5 in. / 2–4 in. · Slingshot RTK 1 in. / 1 in. Pass-to-pass is within a 15-minute window; repeatability is coming back weeks or a year later. Solar storms, HDOP above 2.5, and obstructions degrade all of them. RTK base ideal radius 30 miles; accuracy guaranteed at 9 mph or less (SmarTrax RTK hydraulic) or 5 mph (SmarTrax MD).

GPS

Satellite GS corrections not working

Requires GPS engine firmware OEM060730RN0000 or newer, an unlock, and an active subscription bought through the Raven portal (5–30 minutes to process — keep the machine and receiver on so the beam is received). Beam 98W covers North America, or Auto. Working = GGA quality 5 and the differential age counting; stuck at 99 = not converged. Viper 4: Settings > GPS > More > GPS Unlocks and Differential Settings. RS1: Tools > Unlocks and Tools > GPS Setup > Differential Configuration. 600S is configured through a Viper 4 or Envizio Pro with Main GPS Solution "600S on DGPS".

GPS

600S stopped sending NMEA

On a Viper 4: Serial Devices > Re-Detect Devices, then GPS settings > Receiver Defaults. Still dead = repair.

GPS

GPS serial (DB9) pinout

1 simulated radar pulse · 2 TX (GPS out) / RX (GPS in) · 3 RX / TX · 5 ground · 8 external power. Raven-to-Raven never needs a null modem; Raven-to-third-party usually does (115-0171-040 3 ft, 115-0159-822 10 ft).

Field computers (Viper 4, Viper Pro, Envizio Pro, Cruizer, CR7, CR12)

Field computers

Touch screen problems

  • Cursor jumps to one spot: pressure point between the screen layers — needs repair. Don't dig at the screen edge with cards or tools; it breaks the touch-screen wiring.
  • Cursor bounces around: software. Reinstall with a clean/silent install.
  • Cursor doesn't move: try a clean/silent install; if that fails the screen needs repair. A wired USB mouse (not wireless) runs the unit until then.
Field computers

Display won't turn on, or shows white / colored stripes

  • Won't turn on: listen for the fan (machine off); on Envizio Pro/Viper Pro look for the light behind the blue power button; on Cruizer II the lightbar lights normally at startup (try a silent boot). Fan or light present = screen only. Faint image visible = backlight.
  • White screen or stripes: voltage. Envizio Pro/Viper Pro — 12 V between pins 1 and 16 on the console cable (female pins). Cruizer — 12 V at the power plug (center power, outer ground). Good voltage and still white = hardware.
Field computers

Software errors

  • Viper Pro "Zulu" errors: clean install with the latest software (3.8.0.x+): extract the update to USB (creates a "startup" folder), Program Selection Menu > Install Viper Pro > OK at both WARNING prompts. Erases everything — record settings and keys first, and don't clone a profile back in (may copy the corrupt file). Re-import registration keys afterward.
  • Cruizer "MiniZ.exe" / "czmini": silent install with the latest compatible software.
  • Envizio Pro "Missing Skins" / .XML errors: reload software; if that fails, Envizio Pro Recovery (silent install).
  • After an update = files didn't copy (bad download or USB). Out of nowhere = improper shutdown with a job open. Software fixes don't help = hardware, send in.
  • Viper 4/4+ on ROS 21.1 won't change Wi-Fi mode: select the mode, Yes, then Administrator > log out > Demo, restart in demo, repeat to leave demo.
Field computers

Activation keys and unlocks

Registration code (series-specific, from Raven via dealer) + Machine ID + Validation Code → Activation Key generated on the Raven portal ("Activation Key Request"). Only the activation key is typed into the display; everything is case-sensitive.

  • Envizio Pro: Tools > Updates > Special Features Registration (Machine ID and Validation Code at the bottom) > Enter Activation Key > Accept then the green arrow. Unlocks: single VRA 1-077-0180-031, multi-product VRA -067, Multi-VRA -066.
  • Viper Pro: Menu > Setup > Reg Keys (Machine ID, Validation Code; Next shows existing keys) > enter in an empty slot > OK → "Activation Keys Validated". Unlocks: Guidance 1-077-0171-151, Multi-Product -152, Single VRA 1-077-0180-004, WatchDog -030, AgX -059, OmniSeed -070.
  • Viper 4: request with the registration code and the bar code ID; save the downloaded .zip to USB in \Raven\FeatureUnlocks\; insert, restart when prompted, remove the USB before restarting.
  • Cruizer: Tools > Updates > Feature list; enter with the number pad (tap to cycle letters).
  • CR7/CR12: unlocks 1-077-0180-223 Task Controller, -224 Single VRA, -225 Multi VRA (needs single), -226 Combo VRA, -227 UT, -228 UT+TC. UT alone runs an ISO ECU with no mapping or section control; TC adds as-applied maps, rate control, and automatic sections (needed to "mount" the ECU to the profile). Single VRA needs TC for ISO product control but not for an SCS console.
Field computers

CR7 quirks

  • Settings icon missing outside a job (software bug): from inside a job, Settings > Networking, join a 2.4 GHz Wi-Fi (green frog top-right = connected to Slingshot), then update over the air at portal.ravenslingshot.com > Manage > Hardware > barcode > Available Updates > Update > Install.
  • CR7 can't see your hotspot: it's 2.4 GHz only. iPhone: Personal Hotspot > Maximize Compatibility. Android: Mobile Hotspot > Configure > Band 2.4 GHz. CR12 is not affected.
  • CR7 with SmarTrax/AccuBoom CAN nodes needs minimum node software (Raven article "CR7 and CAN Node Compatibility").
Field computers

Prescription (Rx) maps won't load

WGS84 datum; .shp, .shx, and .dbf with the same name; keep names under 25 characters (Envizio Pro's job-name limit; Viper 4 allows 50), no special characters (use _); not zipped; polygons; ESRI standard. Envizio Pro: USB \ePro\ePro\GlobalData\WorkOrders\rxMaps (25-char name limit). Viper Pro: \RDE\viper\jobs\misc\rxMaps. Viper 4: anywhere — search "Rx Maps" in the USB Import Manager. CR7/CR12: USB root. Keep zones no smaller than the boom width.

Slingshot & Field Hubs

Slingshot & Field Hubs

Field Hub not detected by the display

  • Plug the hub's Ethernet into a laptop: internet works = cable good and data plan active.
  • Field Hub (3G): Power on; Signal and WAN on or flashing; 232 on/flashing; GPS on. Field Hub 2.0/2.1: Power solid green (yellow blink every 4 s = GPS fix); Act/232 flashing any color; Signal solid green (yellow acceptable); Network showing green at least occasionally; Ethernet Link (left, green) solid and Activity (right, yellow) flashing.
  • All good: shut down display and hub, power up, they should pair. Otherwise a Slingshot dealer.
Slingshot & Field Hubs

Field Hub 2.0 light colors

Power: green = on (stays on ~60 s after key-off); green with yellow every 4 s = GPS fix; yellow = shutting down; red = not operational. Signal: green strong (better than −85 dBm), yellow marginal, red poor, flashing red none. Network: green = LTE ready, flashing green = LTE roaming, yellow/green = 2G/3G, yellow = connecting, flashing yellow = no service, red = link down, flashing red = authentication failed. Act/232: flashing = data on serial and/or WAN.

Slingshot & Field Hubs

No WAN / no 232 / no corrections

  • No Signal light = no WAN, ever. No Signal usually points to the antenna or antenna cable, or the hub itself.
  • No WAN with Signal: data plan current? Hub provisioned successfully? (Otherwise hub, SIM, or plan.)
  • No 232 with WAN: cabling; hub assigned to a base station or CORS network on the Slingshot website; CORS credentials correct; GPS light on (CORS needs the hub's own GPS — no GPS light means a re-flash, bad GPS antenna, or failed internal GPS module).
  • Receiver side: RTK format matches the correction format on the Slingshot account; baud 115200 to the hub; correct cable, no loose connections.
Slingshot & Field Hubs

Remote support won't connect

Display software must support multi-client remote support (Envizio Pro 3.7.0.56+, Viper 4 2.0.10+, Viper Pro 3.10.1.13+ — older versions need Java 7, which Chrome no longer runs). Keep the browser current. Shop network ports: 17701, 17702, 17712, 18058, and 18059 TCP.

Slingshot & Field Hubs

Passwords and registration

  • Wi-Fi password is on the hub's sticker. Defaults: Field Hub 1.0 "slinshot" + last two digits of the serial (as Raven publishes it); 2.0 "slingshot" + characters 8–10 of the serial; 2.1 on the bottom label; RS1 usually "pinehurst".
  • Registering hardware at portal.ravenslingshot.com: Field Hubs and RS1s with internal modems go through Manage > Subscriptions > New Activation (dealer involved). RS1 without modem: Manage > Hardware Registration, part number without the leading 1, dashes, or trailing letters, plus the barcode. Viper 4/4+ Wi-Fi: same, but keep the leading 1; software 2.8+. Using both Viper 4 Wi-Fi and a modem-less RS1: register both, put the subscription on the Viper 4, and have the NOC (NOCsupport@ravenind.com, 800-243-5435) tie them together.

Harvest (SmartYield / SmartYield Pro)

Harvest

Yield readings wrong

  • Current Tare and Current Darkness (Pro) or % MS (SmartYield) should match at the start of the day; re-tare through the day as crop conditions change. SmartYield: Yield > Set Tare. Pro: Tools > Yield > Harvester Settings > Harvester Tare. Combine level, clean grain elevator empty at full threshing RPM. Numbers don't match: sensors are seeing more than the paddles (chain, bracket) — readjust; or the elevator chain is loose — tighten.
  • Moisture wrong or missing: clean crop buildup off the sensor; check voltage (SmartYield Diag screen, V3 — 0 V = bad wire or sensor; Pro: red/white 12 V, black/white and blue/white 0–5 V); put a hand on the sensor — no change with good voltage = sensor bad.
  • Header height wrong or missing: Tools > Yield > Diagnostics — the voltage should change as the header moves; no change = sensor or cable. Reset the Up/Down values for every crop or coverage won't paint. Most systems use a 360° sensor that reads 0–4.5 V with one deadband point where it rolls over from 4.5 V to 0 V; install it so the head never crosses that point between raised and lowered.
  • Moisture sensor type: 1 = original SmartYield and SmartYield-to-Pro upgrades; 2 = SmartYield Pro systems.
Harvest

Setup tips that fix "the map looks wrong"

  • Smoothing usually defaults to 3 (averages coverage every 3 seconds); set it to 1 — minimal effect on file size.
  • Number of sections: roughly one section per two rows (6 rows = 3 sections). Too many sections skews yield values.
  • Antenna offset is measured from the cutter on the head, not the very front of the head — this matters for Yield Delay.
  • Yield Delay is the time from crop reaching the cutter to passing the optical sensors in the clean grain elevator. Measure it; the map is only as accurate as this number.
  • Envizio Pro shows only 6 yield ranges; use a GIS program (many are free) for finer legends.
  • Set a separate profile for each harvester head — switching crops with the old head's profile (corn vs. beans) gives wrong bushels/acre.

Spray Center Electronics · Spokane / Coeur d'Alene · Compiled September 2026 from Raven's Interactive Troubleshooting Guide (2015 and 2018 editions) plus current Raven Support Center knowledge articles.

This guide summarizes Raven procedures for common problems and does not cover every possible failure. Voltages and part numbers are as published by Raven; confirm against the manual for your specific hardware and software version. Spray Center Electronics is an independent Raven dealer.

Sources

Raven Interactive Troubleshooting Guide (09/02/2015 and 07/19/2018 editions) and the following Raven Support Center knowledge articles (ravenorg.my.site.com/Support, read September 2026): What is needed to get rate? · How to Test for Boom Sense · How to Test Flow Meter and Granular Encoder Cables · How Raven Controls Valves · Flow Meter and Encoder Specifications · Valve Cal Number Explained · Valve Advance and Valve Delay · Why is my field computer reading distance/speed when not moving · How do I get speed to more than one controller · Spinner/Fan Speed troubleshooting (CAN/ISO and SCS) · How to Reset to Default Settings on SCS Consoles · How do I clear values on my SCS console · RCM Master/Section Sense Options · RCM Use with 5-Volt Encoders · GPS speed over the Raven CANbus · Enable/Disable Product Channels · How to Troubleshoot CANbus Cabling · How to Troubleshoot ISO Cabling · How to Update Nodes with the Raven Service Tool · How to Update CAN and ISO Nodes with the Viper 4 · How to Recover a CAN Node on the Envizio Pro · Why won't all boom sections paint · Product controller node AccuBoom capability · G2 AutoBoom Troubleshooting and Calibration · AutoBoom Settings and Fine Tuning Tips · AutoBoom Hydraulic and Electrical Failures · How To Test UltraGlide 3 and 5 Sensor Systems · ISO AutoBoom Node Losing Calibration · XRT Sensor Pinouts · Open vs closed center hydraulics · UltraGlide on a RoGator won't calibrate · Hawkeye NCV Diagnostic Lights · How the Hawkeye Nozzle Indexing Process Works · Hawkeye 2 Boom Cable Drop Troubleshooting · Hawkeye Operating Modes · Duty Cycle Information · Hawkeye and Hawkeye 2 Diagnostic Cables · Hawkeye NCV Poppet Varieties · Setting Flow Offset for RCM-Sprayer/Hawkeye 2 · Hawkeye Object Pool with AGCO C1000 · Sidekick vac alarm · Sidekick Pro pressure transducer calibration · Sidekick Pro diagnostic lights · Proper Cleaning and Chemical Identification · Sidekick Pro Pump Conversions · Why is my AccuFlow rate erratic · Frost Buildup on AccuFlow Cooler · How to Effectively Use the AccuFlow System · AccuFlow Valve Connections and Pinouts · NH3 Boost Mode on a Viper 4 · SmarTrax Settings and Fine Tuning Tips · RS1 Settings and Fine Tuning Tips · ISO Steering Lights and Diagnostic Codes · What are normal yaw values · Voltages for SPS and Yaw Sensors · How to Check Voltages on SmarTrax Steering Valves · Important SmarTrax 3D Calibration Information · Operating speeds for Raven steering · GNSS Troubleshooting for RS1 · RS1 SBAS/WAAS Convergence Issue · RS1 WiFi Invalid Server Config Error · What to Expect from GPS Corrections · Locking on to a PRN Satellite · GPS mode (GGA quality) · 600S Stops Outputting NMEA · How to Get GS Corrections · GPS serial connector pinout · Viper 4 and Wi-Fi Connectivity Issues · Software Feature Unlocks for Raven Field Computers · Viper Pro Clean Install · CR7 Missing Settings Icon Fix · CR7 5GHz Wi-Fi concerns · CRx Unlocks Explained · Prescription (Rx) Map Requirements · Field Hub not detected · Register Hardware on the Slingshot Portal · Slingshot Wi-Fi Password · How to Update Hardware with CRx Devices.