TGSS Ground-Speed Radar Interface Guide: Pulse, CAN & RS-485 Comparison

Introduction

In modern agricultural vehicles, mobile machines and advanced equipment, accurate measurement of ground speed is increasingly critical. The TGSS (True Ground Speed Sensor) is a radar-based system designed to detect true ground velocity—unaffected by wheel slip or wheel circumference variations. In this article, we’ll dive deep into the interface options available for TGSS: Pulse output, CAN Bus, and RS-485 serial, comparing their characteristics, pros/cons, integration considerations, and typical use-cases.

What is TGSS? A quick overview

Before we look at interfaces, it helps to have the TGSS functionality in mind. TGSS uses a continuous-wave (CW) Doppler radar at ~24 GHz (K-band) to measure ground velocity by reflecting a radar beam off the terrain and analysing the Doppler shift.

Key performance specs (for typical versions):

• Minimum detectable speed down to ~0.1 m/s (~0.36 km/h) in some models.
• Speed measurement error less than ±1 km/h in typical agricultural vehicle conditions.
• Supports multiple output modes which makes it suitable for both legacy systems (pulse) and modern digital ECUs (CAN, RS­-485) in one unit.

Given this flexibility, the choice of interface becomes important—it affects integration complexity, system compatibility, durability, real-time responsiveness, and diagnostic possibilities.

Interface #1: Pulse Output

How it works

The pulse output mode of TGSS essentially converts the measured ground speed into a frequency (pulse-rate) signal, similar to how traditional mechanical or magnetic wheel-speed sensors output pulses. For example, TGSS may output something like 36.6 Hz = 1 km/h or 58.9 Hz = 1 mph in a specified mounting angle and configuration.

In simple terms:

The TGSS counts the Doppler return and converts it into a square-wave or pulse stream whose frequency is proportional to vehicle ground speed.

The downstream system (e.g., planter control module, yield monitor, hydraulic rate controller) reads these pulses and computes speed.

Because many legacy agricultural systems already accept a pulse speed input (often from wheel-mounted sensors or axle sensors), the TGSS pulse mode offers “drop-in replacement” capability. For example, the TGSS datasheet notes “Pulse interface compatible with conventional pulse speed sensors.”

Advantages

• Compatibility: Many older machines and monitors expect a pulse input; TGSS pulse mode means you don’t need to redesign electronics or add extra converters.
• Simplicity: The wiring and logic are straightforward—the sensor supplies a pulse output referenced to ground and power, and the receiving unit just counts pulses.
• Low overhead: No complex data parsing; minimal processing needed on the receiving side.

Disadvantages / Limits

• Lower data richness: Pulse output gives speed only; there is no built-in capability for richer data like direction, quality flags, error codes, or diagnostics.
• Speed quantization/latency: Pulse signals may have coarser resolution or slower update depending on frequency scaling; for ultra-low-speed (<1 km/h) or very dynamic manoeuvres, performance may degrade.
• Harder to integrate into modern digital systems: Newer ECUs or ISOBUS devices may expect CAN or serial data rather than simple pulses.

Integration Tips

Ensure the scaling of pulses matches the receiving system’s expectations: e.g., if the monitor expects 100 pulses per km/h, but TGSS outputs 36.6 Hz = 1 km/h, you may need to configure or scale accordingly. TGSS documentation notes default 36.6 Hz = 1 km/h.

Signal noise/vibration: Because pulse counting expects clean transitions, any jitter, false pulses (due to vibration) or reflective ground anomalies must be filtered or anchored.

Confirm power supply and output voltage levels: Some pulse outputs may be +12 V square waves, which must be compatible with the counting electronics. For example, TGSS specification: “Pulse_OUT_12V Pulse speed data … 36.6 Hz means 1 km/h” for a certain output.

Typical Use-Cases

Retrofitting older agricultural vehicles where the OEM monitor uses pulse input.

Applications where only speed is required (not direction, diagnostics), and simplicity and cost matter more than advanced data link.

Machines where digital bus infrastructure isn’t available or where simplicity and field-serviceability are key.

Interface #2: RS-485 Serial Output

How it works

RS-485 is a common industrial serial-communication standard that supports differential signalling over twisted-pair wiring, enabling robust communication in harsh environments and over longer cable lengths. TGSS supports an “UART + 485” interface mode, outputting speed (in m/s) at a given baud rate (for example 9600 baud) via RS-485.

In this mode:

The TGSS outputs a data packet via RS-485, which may include speed in real-units (m/s or km/h), quality flags, possibly direction, error codes.

The downstream device (PLC, ECU, ISOBUS terminal) acts as RS-485 master/slave or reads the serial messages.

The differential nature of RS-485 helps to mitigate noise, ground-loops, and long-cable issues typical in mobile machinery.

Advantages

• Rich data: Unlike pulse mode, RS-485 can transmit multiple data fields: speed, direction, timestamp, status bits.
• Robust in harsh environments: Differential signalling, long cable support, better noise immunity compared with single-ended signals.
• Flexible integration: Many modern agricultural control systems or PLCs support serial communication; using RS-485 allows for future expansion (firmware updates, diagnostics).
• Better for networked systems: If the sensor is integrated into a broader telemetry or IoT architecture, serial output is often more suitable.

Disadvantages / Limits

• Requires more electronics/firmware: The receiving side must parse the serial protocol, handle error checking, possibly implement modbus or vendor-specific protocol.
• Higher complexity: Wiring must consider proper termination, biasing, ground reference, and correct connector pin-outs.
• Longer latency/delay: Serial packets might have slightly longer latency compared to simple pulses, depending on baud rate and processing.

Integration Tips

Match the baud rate: TGSS lists 9600 baud typical for RS-485.

Ensure correct wiring: differential pair (A/B) plus ground reference; consider twisted pair shielded cable if long run.

Use proper termination resistors at the ends of the RS-485 line, ensure no stub wiring causing reflections.

Plan for protocol details: Determine message frame format, whether speed is transmitted in m/s, km/h, or pulses, whether direction is encoded, and whether CRC or checksum is used. TGSS documentation may need to be consulted for the exact message.

Ground-loop mitigation: Because mobile machines have large power systems, ensure the RS-485 ground is properly referenced and doesn’t float.

Firmware compatibility: If integrating into an ISOBUS or CAN-to-RS-485 gateway, ensure the mapping of speed data is correct.

Typical Use-Cases

• Agricultural machines with central PLCs or ISOBUS terminals that expect real-value speed data, not simple pulses.
• Systems where diagnostics, data logging, or advanced control (e.g., closed-loop speed control) is required.
• Situations where long wiring or multiple sensors share a network, and robust communication is necessary.

Interface #3: CAN Bus Output

How it works

CAN (Controller Area Network) is a widely used vehicle-bus standard in automotive and mobile equipment for real-time control and data exchange. Some versions of TGSS support CAN output mode (though exact message definitions may depend on version and OEM). For example, ZLY’s TGSS states “RS485, CAN, and pulse communication modes are available.”

In CAN mode:

The TGSS acts as a CAN node/producer sending defined CAN frames containing ground speed data (and possibly status) on the machine’s CAN bus.

Other ECUs, displays or telemetry modules subscribe to the speed messages.

Messages follow standard or proprietary CAN identifiers, and may be configured for agricultural equipment standards (e.g., ISOBUS/ISO 11783) or OEM custom.

Advantages

• Real-time, robust bus: CAN is designed for the harsh automotive/mobile environment, with error detection, arbitration, and robustness.
• Scalable system integration: You can attach multiple sensors and ECUs to the same bus, and speed data can be used in broader vehicle functions (traction control, slip monitoring, automation).
• Standardization: Many agricultural machines already use CAN or ISOBUS; TGSS integrating via CAN fits naturally into modern machine architectures.
• High reliability and networked architecture: With CAN, speed values can be distributed to multiple modules (display, telemetry, control).

Disadvantages / Limits

• Complexity: Requires understanding of CAN architecture, message mapping, IDs, baud rate (e.g., 250 kbit/s or 500 kbit/s), potentially higher cost wiring/connectors.
• Sensor/node configuration: If the TGSS supports multiple output modes, you may need to configure it to CAN output, which could involve firmware or DIP-switch settings.
• Dependency on system bus: If the machine’s CAN bus is already loaded or has other priorities, adding another node may require bus planning or load management.
• Less drop-in for very old systems: Legacy machines without CAN will not benefit from this mode unless a gateway is added.

Integration Tips

• Confirm CAN parameters: baud rate (typically 250k or 500k), termination (120 Ω resistors at each end of bus), node addressing, message IDs and data format.
• Map messages: Ensure the TGSS’s CAN message for ground speed is correctly interpreted by the machine controller or display (units, scaling, offsets).
• BUS loading: Check how many nodes, message frequency, and bus utilization to avoid CAN congestion.
• Confirm sensor configuration: Many TGSS units might ship default to pulse; switching to CAN may require configuration or ordering the correct variant.
• Electro-mechanical considerations: Use shielded twisted pair cable, proper termination, keep wiring away from high-current or high-voltage lines to avoid EMI.

Typical Use-Cases

• Newer agricultural machines with full digital architectures and CAN/ISOBUS networks.
• Mobile equipment requiring integration of speed data into broader functions (traction control, autopilot, telematics).
• OEM systems where sensor nodes need to be connected to the central vehicle bus and multiple modules will consume speed data.

Practical Integration Workflow

Here are the recommended steps when integrating TGSS via any of the three interface options:

1. Select the correct TGSS variant

When ordering, specify which interface you intend to use (Pulse, RS-485, CAN) to ensure the sensor is configured accordingly. TGSS spec notes selectable interfaces.

Check all mechanical and environmental specs: operating voltage (9-16 V typical for TGSS), cable/wiring harness, mounting height and angle.

2. Mechanic & mounting setup

Install at recommended height and angle: for example, the TGSS manual gives 0.3–1 m above ground as typical height, and ~35° mounting angle relative to ground.

Ensure a clear line of sight to the ground (i.e., no brushes, debris, or pipework in the radar beam path), as interference can cause erratic speed readings.

3. Wiring & power supply

• Confirm the vehicle’s supply voltage matches sensor requirement (TGSS: 9-16 V typical) and that the wiring harness is sized for the current draw.
• For pulse output: connect power, ground, and pulse output line; ensure the receiving system expects the correct voltage level and pulse polarity.
• For RS-485: connect A/B lines (differential pair), ground reference, ensure proper termination at bus ends, use twisted-pair cable, configure baud rate (e.g., 9600).
• For CAN: connect CAN High, CAN Low, ground (and possibly a shield), ensure bus termination, verify bus topology, set baud rate and node ID as per vehicle bus design.

4. Sensor configuration & scaling

• For pulse mode, validate scaling (e.g., 36.6 Hz = 1 km/h) and adjust downstream system or TGSS scaling setting if required.
• For serial modes (RS-485 or CAN), obtain message definitions, scaling factors, units (m/s vs km/h), and set up the receiving ECU accordingly.
• Perform calibration test: with vehicle stationary and engine idle, verify no ghost speed; then drive at known speed and validate reading matches actual ground speed. Check for mounting angle error or sensor misalignment.

5. System integration & validation

• For pulse: count pulses over a known time and calculate expected speed; compare to vehicle telemetry or GPS.
• For RS-485 or CAN: capture message data, log speed values, confirm values correspond to actual motion, check for latency or drop-outs.
• In all cases, test under the actual vehicle operating conditions: different ground textures (stubble, gravel, wet/dry field), low speed (<1 km/h) manoeuvres, reversing (if relevant), and higher speed (if the vehicle will operate beyond very low speeds). TGSS claims minimum detectable speed ~0.1 m/s.
• Check for diagnostic flags or error codes (especially for serial/CAN modes) and ensure the system handles sensor fault conditions gracefully (e.g., no signal, obstruction, extreme vibration).

6. Documentation & maintenance

• Keep wiring and installation diagrams.
• Note the interface mode selected (Pulse, RS-485, CAN) and any scaling factor or mapping used.
• Periodically inspect the mounting path for debris, ensure the sensor’s line of sight is clear, check for wear/loose fasteners, review whether firmware updates (if applicable) or bus configuration changes are needed.

Which Interface Should You Choose?

Here are some decision-guidance points:

• If you are retrofitting older agronomy equipment that expects a simple pulse speed signal and you want minimal changes: go with Pulse interface.
• If you have a machine with a modern control system but no CAN bus (or you prefer serial simplicity): RS-485 is a strong choice—provides more data and robustness than pulse, but less complexity than CAN.
• If you are designing a new vehicle or machine with a CAN/ISOBUS architecture, and you want full integration (speed + status + diagnostics + networked data): go for CAN output interface.
• If budget is a major constraint and you only need speed (no extra data): pulse may suffice, but be aware of its limitations at ultra-low speeds and for advanced control.
• If cable length, electromagnetic noise or long-haul vehicle wiring is a concern (e.g., long field tractors, trailers): RS-485 or CAN (both differential signalling) are more robust than simple pulse wiring.
• If you foresee future upgrades (e.g., telematics, automation, slip-control, safety alerts): selecting RS-485 or CAN now will future-proof the integration.

Common Pitfalls & How to Avoid Them

• Incorrect mounting angle or height: As noted above, a 1° angular error can introduce ~1% speed error in some cases.
• Obstructed radar beam: Mud, grime, brush guards, or other parts blocking the radar’s view to the ground can cause false readings or instability. Clean line of sight is critical.
• Mismatch in pulse scaling/logic: If the receiving system expects a different pulse frequency per km/h (e.g., 50 Hz vs 36.6 Hz), the speed reading will be wrong—always verify the scaling factor.
• Wiring noise and ground loops (especially for pulse or serial): Use shielded cable where possible, avoid parallel routing with high-power lines, ensure proper grounding.
• Unterminated RS-485 or CAN bus: Reflective signals or bus errors will compromise data; always ensure proper termination.
• Ignoring diagnostics/invalid readings: Especially in serial or CAN modes, incorporate logic to detect when the speed reading is invalid or when the sensor is disconnected.
• Neglecting environment conditions: TGSS models list environmental ranges such as –45 °C to +85 °C in agricultural implementations.
• Assuming speed accuracy without field validation: Always validate the actual speed output under your machine’s real conditions (ground texture, speed range, direction, moisture) rather than relying purely on spec sheet.

Case Study: Agricultural Vehicle Integration

Let’s walk through a hypothetical case: an OEM tractor manufacturer wants to integrate TGSS into a new model to provide accurate ground speed for seed-planting rate control, wheel slip feedback, and ISOBUS network distribution.

Scenario:

Vehicle has an ISOBUS terminal (CAN bus) already, and uses a CAN network at 250 kbps.

The seed-planting system needs real-time speed data (update at least 10 Hz) to adjust seed meter rate precisely during low-speed operations, turn rows, and reverse.

The vehicle also has telemetry: ground speed must be logged and transmitted for fleet management.

The machine will operate on varying ground surfaces: soft soil, stubble, gravel, slopes.

Implementation Steps:

• Select TGSS variant configured for CAN output (confirm part number/config).
• Mount TGSS on underside of the tractor, at ~0.6 m above ground, pitched at ~35° to the forward direction per manufacturer’s recommendation.
• Connect to CAN bus: twisted-pair (shielded) cable, ensure proper termination at bus ends, set node ID and message IDs per OEM standard.
• Map TGSS speed message to the ISOBUS data dictionary: e.g., PGN 0xFEEE (hypothetical) with parameter ground speed in km/h, scaled by 0.01 km/h.
• Validate under operating conditions: drive at slow speed (0.5 km/h to 40 km/h), verify speed matches GPS or known distance/time, test reversing, test on stubble, ensure no false speed when stationary.
• Use speed data for downstream systems: seed meter rate control, slip monitoring (compare TGSS speed vs wheel/axle speed), telemetry upload (vehicle speed logs), diagnostic display (if speed reading invalid, flag sensor fault).
• Maintain installation: inspect sensor face for debris, verify radar beam unobstructed, log any instances of speed dropouts or anomalous readings and adjust mounting or shielding as needed.

Outcome: The tractor gains reliable true-ground-speed data, not dependent on wheel slip, improving planting accuracy, reducing seed waste, enabling slip control and better field data logging—justifying TGSS integration via CAN bus.

Conclusion

Choosing the right interface for the TGSS True Ground Speed Sensor is a critical decision that affects system compatibility, integration complexity, data richness and future-proofing.

Pulse output is ideal for simplicity and legacy systems.

RS-485 serial offers better data, robust wiring and suitability for modern but non-CAN systems.

CAN bus output enables full integration into vehicle networks and advanced functions, albeit at higher complexity.

By understanding the trade-offs and planning the integration carefully—mounting, wiring, configuration, validation—you can ensure reliable, accurate ground-speed measurement that enhances machine control, precision agriculture operations, and telematics.