How to Troubleshoot ISV57 Servo Drive Modbus Communication in DIY Sim-Racing FFB Pedals

To troubleshoot ISV57 servo drive Modbus communication, verify the TX/RX pin mapping in Main.h, ensure UART is initialized at 38400 baud with the correct polarity inversion, validate CRC-16 (0xA001 polynomial) calculations in Modbus.cpp, and test register reads using the documented addresses in ServoParameterization.md.

The chrgri/diy-sim-racing-ffb-pedal project utilizes a Leadshine iSV57 servo drive controlled via a Modbus-RTU-like protocol over hardware UART. When communication fails between the ESP32 and the servo, systematic debugging of the physical layer, serial configuration, and packet integrity is required to restore force feedback functionality. This guide references the exact source code locations and diagnostic procedures from the repository to isolate and resolve Modbus errors.

Verify Physical Wiring and Pin Configuration

Start by confirming the hardware connections match the firmware definitions in Firmware_for_V3/PedalFirmware/include/Main.h. The ESP32 uses specific GPIO pins for the servo interface:

#define ISV57_TXPIN 27   // ESP32 TX → Servo RX
#define ISV57_RXPIN 26   // ESP32 RX ← Servo TX

Ensure your PCB version uses the correct pin assignments, as they vary between V1.2, V1.3, and V1.4 revisions. The iSV57 requires inverted RS-485 signaling; verify your level-shifter polarity, ensure the ground reference is common between the ESP32 and servo drive, and use a short (≤30 cm) twisted pair cable to minimize noise.

Configure UART Parameters

The serial initialization occurs in Firmware_for_V3/PedalFirmware/src/isv57communication.cpp. The constructor sets the baud rate, frame format, and inversion flag based on the PCB version:

#if PCB_VERSION == 10 || PCB_VERSION == 9 || PCB_VERSION == 12 || PCB_VERSION == 13
  Serial1.begin(38400, SERIAL_8N1, ISV57_RXPIN, ISV57_TXPIN, false);
#else
  Serial1.begin(38400, SERIAL_8N1, ISV57_RXPIN, ISV57_TXPIN, true);
#endif

Critical parameters to verify:

• Baud rate: 38400
• Data bits: 8
• Parity: None
• Stop bits: 1 (or 2 on legacy boards)
• Inverted: true for most boards; false only for PCB versions 9, 10, 12, and 13

If the inversion flag or baud rate mismatch the servo configuration, Modbus::requestFrom will return -1, indicating a communication timeout.

Validate Modbus Packet Structure and CRC

The Modbus implementation in ESP32/src/Modbus.cpp handles packet framing and CRC validation. A standard request frame follows this byte structure:

[0] Slave ID (0x3F = 63)
[1] Function code
[2] Address high byte
[3] Address low byte
[4] Quantity high byte
[5] Quantity low byte
[6] CRC low byte
[7] CRC high byte

The CRC-16 calculation uses the 0xA001 polynomial as implemented in Modbus::CheckCRC:

int Modbus::CheckCRC(uint8_t* buf, int len){
    int nominal = 0xA001;
    int crc = 0xFFFF;
    // Iterate bytes and bits...
    return crc;
}

Validate your implementation by calculating the CRC for the test packet 0x3F 0x03 0x01 0xF3 0x00 0x03, which should yield 0xF0 0xDA as documented in StepperParameterization/ServoParameterization.md.

Test Communication with Diagnostic Registers

Use the coilRead method to perform a "lifeline" check on coil 0x0000 using slave ID 63 (0x3F):

int alive = modbus.coilRead(63, 0x0000);

This calls Modbus::requestFrom, which returns -1 on timeout or CRC error. If successful, it returns the coil state (0 or 1).

For functional testing, read holding register 0x0191 to retrieve the position percentage:

long position = modbus.holdingRegisterRead(0x0191);

Refer to StepperParameterization/ServoParameterization.md for the complete register map, including coil registers (0x01-0x03) for status flags and holding registers for parameters like PR0.01 and PR1.00.

Common Symptoms and Fixes

Symptom	Root Cause	Solution
All reads return -1	Incorrect pin mapping or UART inversion	Verify ISV57_TXPIN/ISV57_RXPIN in Main.h and match the Serial1.begin inversion flag to your PCB version
CRC errors in debug output	Signal noise or polarity mismatch	Shorten cable to ≤30cm, verify TX/RX polarity, ensure common ground
Coil reads work, holding registers fail	Invalid register address	Use valid addresses from ServoParameterization.md (e.g., 0x0191-0x0194 for cyclic data)
No response to lifeline packet	Wrong slave ID	Confirm servo ID is 0x3F (63) or update slaveId constant in isv57communication.cpp
Intermittent timeouts	Buffer overflow or timing issues	Increase timeout_ in Modbus::requestFrom (default 10ms) or add delay(1) between requests

Example Diagnostic Sketch

Upload the following sketch to isolate communication issues. It tests the lifeline coil, position register, and fault status:

#include "Modbus.h"
#include "Main.h"

Modbus modbus(Serial1);

void setup() {
  Serial.begin(115200);
  
  // Initialize servo UART per Main.h specifications
  Serial1.begin(38400, SERIAL_8N1, ISV57_RXPIN, ISV57_TXPIN, true);
  modbus.init(true);  // Enable debug logging
  delay(100);
}

void loop() {
  // Test 1: Lifeline check
  int lifeline = modbus.coilRead(63, 0x0000);
  Serial.print("Lifeline (0x0000): "); Serial.println(lifeline);
  
  // Test 2: Position feedback
  long pos = modbus.holdingRegisterRead(0x0191);
  Serial.print("Position %: "); Serial.println(pos);
  
  // Test 3: Fault status coil
  int fault = modbus.ReadCoilReg(63, 0x01F3, 1);
  Serial.print("Fault status: "); Serial.println(fault);
  
  delay(1000);
}

This sketch uses the same Serial1 configuration as the production firmware and prints results to the USB serial monitor for immediate verification.

Summary

• Physical Layer: Confirm ISV57_TXPIN and ISV57_RXPIN definitions in Main.h match your wiring, and verify the RS-485 inversion setting matches your PCB hardware.
• UART Config: Initialize Serial1 at 38400 baud with SERIAL_8N1 and the correct inversion flag for your PCB revision.
• Protocol Integrity: Ensure CRC-16 calculation uses the 0xA001 polynomial; validate against known-good packets from ServoParameterization.md.
• Register Access: Use slave ID 63 (0x3F) and documented register addresses; handle -1 return values as timeout indicators.
• Timing: Increase timeout_ values or add inter-message delays if the servo response is slower than the default 10ms expectation.

Frequently Asked Questions

Why does modbus.coilRead return -1 consistently?

A return value of -1 indicates either a UART timeout or CRC mismatch. Verify that Serial1.begin in isv57communication.cpp uses the correct baud rate of 38400, that the inversion flag matches your PCB hardware (true for most, false for versions 9, 10, 12, 13), and that the physical TX/RX pins defined in Main.h are correctly wired to the servo drive.

How do I verify the CRC calculation is correct?

Use the test vector from ServoParameterization.md: the packet 0x3F 0x03 0x01 0xF3 0x00 0x03 should generate CRC bytes 0xF0 0xDA. Compare the output of Modbus::CheckCRC in ESP32/src/Modbus.cpp against an online Modbus CRC calculator to ensure the 0xA001 polynomial implementation matches the specification.

What is the default Modbus slave ID for the iSV57?

The default slave ID is 63 (hexadecimal 0x3F), defined as const uint8_t slaveId = 0x3F in isv57communication.cpp. If the servo has been reprogrammed to a different ID, update this constant in the firmware or reset the servo to factory defaults to restore ID 63.

Can I use a different baud rate than 38400?

The firmware hardcodes 38400 baud in the Serial1.begin call within isv57communication.cpp. While the iSV57 supports other baud rates, changing this requires updating both the servo drive parameterization (via Leadshine software) and the Serial1.begin initialization in the firmware to maintain communication.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}