Troubleshooting

The most common cause of a motor that sounds louder or seems to struggle is belt tension loosening over time. When the belt is too loose, the motor works harder to overcome slippage, which creates more noise and reduces effective power transfer.

Signs of loose belt tension:

• Motor sounds louder or more strained during operation
• Reduced thrust force compared to initial setup
• Clicking or ratcheting sounds at stroke endpoints
• Belt visibly deflects more than 5mm when pressed

Solution: Follow the belt tension guide to verify and adjust your belt tension. Even small amounts of slack can significantly affect performance.

Over time, the linear rail's factory lubrication can dry out or collect debris, increasing friction. This makes the motor work harder and can produce louder operation.

Signs of rail lubrication issues:

• Scratchy or grinding sensation when moving the carriage by hand
• Motor sounds more strained even at lower speeds
• Inconsistent movement (stuttering or binding)

See the belt tension guide for lubrication instructions.

An aging or failing power supply may deliver less voltage or current than rated, causing the motor to struggle under load.

Signs of power supply issues:

• Motor sounds strained only under load (during strokes, not at idle)
• Performance degrades as the session continues (power supply heating up)
• Visible dimming of motor LED during operation

Solution:

1. If you have a multimeter, measure the voltage at the power input terminals while the OSSM is operating—a healthy 24V supply should deliver close to 24V under load
2. Try a different power supply if available
3. Ensure you're using a supply rated for at least 5A

See insufficient power supply for more details.

Symptoms:

• Green light on motor is dim or flickering
• Motor light is visible but actuator doesn't respond
• Actuator moves weakly or stalls under load

Solution: Ensure you're using a power supply that meets the minimum requirements:

• Voltage: 24V DC
• Current: At least 5A

Symptoms:

• Motor light is completely off
• No response from motor when commands are sent
• Visible loose or disconnected wires

Diagnosis:

1. Inspect the wiring between the controller and motor
2. Check that all connectors are fully seated
3. Look for damaged or frayed wires

Solution: Reconnect any loose wiring following the wiring guide. If wires are damaged, replace them before operating.

Symptoms:

• Motor spins but actuator doesn't move
• Belt slips or makes noise during operation
• Inconsistent or jerky movement

Solution: Adjust the belt tension following the tension adjustment guide. The belt should be tight enough to prevent slipping but not so tight that it strains the motor.

The wired remote draws power from the control board. If you connect the remote before the board is powered, it may not initialize correctly.

Solution:

1. Disconnect the RJ45 cable from the control board
2. Power on the OSSM using the 24V supply
3. Wait for the control board to fully boot (LED indicators stabilize)
4. Connect the wired remote's RJ45 cable firmly until it clicks

A loose or partially seated cable can prevent power from reaching the remote.

Solution:

1. Disconnect the RJ45 cable from both ends
2. Inspect the connectors for bent pins, debris, or damage
3. Reconnect firmly at both the control board and the remote until you hear/feel a click
4. Try a different RJ45 cable if available

If the remote worked previously but stopped, a simple power cycle often resolves the issue.

Solution:

1. Disconnect the 24V power supply from the control board
2. Wait 5–10 seconds
3. Reconnect the 24V power supply
4. Allow the board to boot, then check if the remote display activates

If the remote powers on after cycling, no further action is needed. Intermittent issues may indicate a marginal cable connection—try reseating or replacing the RJ45 cable.

Symptoms:

• Remote display turns on and shows the menu
• Right knob (encoder) works normally for menu navigation
• Left knob (speed control) produces no change regardless of position
• No visible damage to the knob or circuit board

Diagnosis:

1. Power on OSSM and confirm the remote display activates
2. Navigate menus with the right knob to confirm it responds
3. Turn the left knob fully counterclockwise to clockwise—if speed never changes, the potentiometer is likely defective

Before concluding the potentiometer is faulty:

1. Power off and reseat the RJ45 cable at both ends until it clicks
2. Try a different RJ45 cable if available
3. Inspect the cable connectors for bent pins or debris
4. Power on and test again

If the right knob still works but the left knob doesn't respond, the issue is the potentiometer rather than the connection.

A non-responsive potentiometer indicates a hardware fault that cannot be fixed through software or settings. Contact support to request a replacement wired remote under warranty.

Self-repair option: If your remote is out of warranty or you prefer to repair it yourself, the potentiometer part number is:

• Potentiometer: ALPSALPINE RK09D1130C3C

This component is available from electronics suppliers such as Digikey, Mouser, or AliExpress.

Symptoms:

• Remote display turns on and shows the menu
• Left knob (speed control) works normally
• Right encoder responds inconsistently—only some clicks or rotations are registered
• Turning the encoder requires multiple clicks to move through menu items
• Solder joints on the remote board appear intact

Diagnosis:

1. Power on OSSM and navigate to any menu
2. Slowly turn the right encoder one click at a time
3. Count how many physical clicks it takes to move one menu position
4. If it consistently takes 2–3 clicks to register a single movement, the encoder is defective

Before concluding the encoder is faulty:

1. Power off and reseat the RJ45 cable at both ends until it clicks
2. Try a different RJ45 cable if available
3. Inspect the cable connectors for bent pins or debris
4. Power on and test again

If the issue persists after checking the cable, the encoder itself is defective.

A partially responsive encoder indicates a hardware fault that cannot be fixed through software or settings. Some batches of encoder components have been found to have this defect. Contact support to request a replacement wired remote under warranty.

Self-repair option: If your remote is out of warranty or you prefer to repair it yourself, the encoder part number is:

• Encoder: ALPSALPINE EC11E18244AU

This component is available from electronics suppliers such as Digikey, Mouser, or AliExpress.

These menu options are implemented in current firmware:

• Get Help — Displays a QR code linking to documentation
• WiFi Setup — Opens the WiFi configuration portal
• Update — Checks for over-the-air firmware updates

If you see a blank screen instead, your firmware may be outdated. Update using the Web Flasher to get the latest version.

WiFi Setup and Update require the OSSM to connect to a WiFi network. If WiFi has not been configured, these options may not function as expected.

You can configure WiFi using the Web BLE Controller in a browser without relying on the wired remote's WiFi Setup menu. See WiFi Setup for instructions.

To ensure you have the latest features, update your firmware using the Web Flasher.

If the wired remote's menu options aren't working for you, these browser-based tools provide the same functionality:

1. Use the Web BLE Controller to configure WiFi from your browser
2. Use the Web Flasher to update firmware directly via USB

Symptoms:

• Device restarts repeatedly without completing the homing sequence
• Display shows garbled text, flickering, or visual artifacts
• Crashes or reboots occur when using the right knob (encoder)
• Random, uninstructed changes to speed, depth, or stroke parameters
• Motor attempts to exceed position limits (violent movement, belt skipping)
• Problems persist after trying different firmware versions

What to rule out first: Before suspecting a hardware fault, try:

1. Different RJ45 cable — A damaged cable can cause intermittent faults
2. Different power supply — Voltage fluctuations can cause instability (use a quality 24V supply rated for at least 5A)
3. Reflash firmware — Corrupted firmware can cause unexpected behavior. Use the Web Flasher to install the latest stable version.

If basic troubleshooting doesn't help, verify the control board is receiving power correctly:

1. Check the 3.3V LED — The control board has a small blue LED near the ESP32 chip. If this LED is on, the board is receiving power and the voltage regulator is working.
2. Check 24V at the input terminals — Use a multimeter to verify 24V DC at the power input terminals on the control board. A healthy supply should read close to 24V.
3. Check voltage at motor terminals — Measure voltage at the motor output terminals to confirm power is reaching the motor driver.

If the 3.3V LED is off or dim, or if voltage readings are incorrect, the issue may be with your power supply or the control board itself.

Isolate whether the wired remote is causing the issue:

1. Power off the OSSM completely
2. Disconnect the wired remote's RJ45 cable from the control board
3. Power on the OSSM
4. Observe the serial output via USB (optional) or listen for motor movement

Interpreting results:

• If the OSSM boots normally and homes without the remote connected, the wired remote board is likely faulty.
• If the OSSM still fails to boot or crashes without the remote connected, the main control board may be faulty.

Boot loops, display corruption, or erratic parameter changes that persist after troubleshooting indicate a hardware fault. Depending on test results:

• Wired remote at fault — Contact support to request a replacement wired remote board under warranty.
• Control board at fault — Contact support to request a replacement control board under warranty.

The reset button on the OSSM control board performs a power cycle reset. Pressing it restarts the ESP32 microcontroller, similar to unplugging and reconnecting power.

What it does:

• Restarts the ESP32 and reinitializes the firmware
• Clears any temporary runtime state
• Can help recover from a frozen or unresponsive state

What it does not do:

• It does not erase stored settings or calibration data
• It does not wipe the flash memory
• It does not perform a factory reset or clear WiFi credentials
• It does not trigger a new homing sequence automatically (homing occurs on boot as part of normal startup)

The standard OSSM firmware does not include a built-in factory reset function. To completely clear settings and return to defaults:

1. Reflash the firmware using the Web Flasher. This overwrites the existing firmware but may not clear all stored data in flash memory.

2. For a complete flash wipe, you need to use development tools like PlatformIO or esptool to erase the flash before reflashing. See PlatformIO setup for details.

Some community members develop alternative firmware for specialized use cases. If you want to install community firmware:

Before installing community firmware:

• Back up any settings you want to preserve
• Note your current firmware version in case you need to revert
• Read the community project's documentation carefully

If the community firmware requires a clean flash: The reset button does not wipe flash memory. To fully erase flash before installing community firmware, you typically need to:

1. Use PlatformIO with the Erase Flash command
2. Or use esptool.py erase_flash from the command line

Contact the community firmware developer (often via Discord) for specific installation instructions, as requirements vary between projects.

Symptoms:

• The ESP32 chip on the control board becomes uncomfortably hot to touch within seconds of applying power
• Overheating occurs whether powered via the 24V supply or via USB-C connection
• The board may have worked briefly before, or never worked at all

What this indicates:

The ESP32 should be warm during operation but never hot enough to be uncomfortable. Excessive heat indicates a hardware fault—typically a short circuit or damaged component on the board.

Resolution:

An overheating ESP32 indicates a hardware defect that cannot be fixed through firmware updates or configuration changes. Contact support to request a replacement control board.

Symptoms:

• The board is detected on a COM/serial port, but flashing always fails
• Both the Web Flasher and PlatformIO fail to communicate with the board
• Error messages indicate "unable to connect" or "failed to sync" despite the board being detected
• You've already tried: different USB cables, different USB ports, different computers, installing drivers, closing other serial applications

What this indicates:

If the board appears on a COM port but cannot be flashed after exhausting all standard troubleshooting, the ESP32 or its flash memory may be damaged. This can occur from:

• Electrostatic discharge during handling
• A short circuit event
• A manufacturing defect

Resolution:

If you've exhausted all troubleshooting steps and still cannot flash the board, contact support with details of what you've tried. A replacement board may be needed.

Symptoms:

• Motor does not move at all when powered on—no homing attempt, no sound, no vibration
• The 3.3V LED on the board may illuminate, but no other activity occurs
• No purple LED breathing pattern during homing
• Motor's green power LED is on (indicating motor is receiving power)
• ESP32 chip may be abnormally hot

Distinguishing board failure from motor failure:

Resolution:

If the motor shows power (green LED) but the board shows no activity beyond the 3.3V LED, and especially if the ESP32 is overheating, the control board is likely defective. Contact support to arrange a replacement.

Symptoms:

• Unusual sounds on first startup—clicking, buzzing, or electronic tones (not mechanical belt noise)
• 3.3V LED may flash in sync with the sounds
• Sounds stop after a while and the board becomes unresponsive
• Different from the normal homing movement sounds

What this indicates:

Electronic noises accompanied by LED flashing (not the normal purple breathing pattern) can indicate the board is in a fault state or experiencing a hardware issue. If the board subsequently becomes unresponsive or won't flash, the initial noise may have been a symptom of component failure.

Resolution:

If your board made unusual electronic noises on first power-up and is now unresponsive to flashing attempts, contact support with a description of what you observed. This helps identify potential batch issues.

The PCB mount includes a strain reliever on the side to secure the power cable and prevent movement at the barrel jack connection.

Solution:

1. Route the power cable through the strain relief slot on the side of the PCB mount
2. Secure the cable so the barrel jack connector cannot move or wiggle during use
3. Ensure the barrel jack is fully seated before securing the cable

Symptoms:

• Sparks when plugging or unplugging the power supply
• Power cuts out when the cable moves
• Intermittent power during operation

Solution:

1. Unplug the power supply from the wall before disconnecting from the board
2. Inspect the barrel jack connector for damage, bent pins, or debris
3. Ensure the barrel jack is fully inserted until it clicks or seats firmly
4. Use the strain reliever to prevent cable movement during use

Ensure your power supply matches the PCB requirements:

• Barrel jack size: 5.5mm outer diameter × 2.1mm inner diameter
• Polarity: Center-positive
• Voltage: 24V DC (or USB-C PD if using that input)

An incorrectly sized barrel jack may not seat properly, causing loose connections. If using a third-party power supply, verify the connector matches these specifications.