Vision Miner Wiki

Heater Fault at Print Start

Heater Fault at Print Start

A heater fault during print startup means one of the printer's heaters (bed, chamber, or nozzle) triggered a fault before the actual print began � during the preheat, chamber heating, or heat soak phase in initial.g. The print is cancelled and never starts.

This is different from a heater fault during printing. During print startup the printer runs a specific heating sequence with diagnostic logging that helps pinpoint the cause.

Safety and Warnings

Warning: WARNING: Do not disable heater fault detection to work around this problem. Fault detection is a safety system that protects against fire. Disabling it introduces serious risk. IMPORTANT: If the heater fault occurs repeatedly, do not keep restarting prints. Contact support with the diagnostic files described below.

1. Why This Happens

The firmware monitors all four heaters (H0: left nozzle, H1: right nozzle, H2: bed, H3: chamber) during the entire startup sequence. If any heater cannot reach or maintain its target temperature within the allowed time and tolerance, the firmware triggers a fault, cancels the print, and saves diagnostic files.

Common Causes

HEPA fan cooling the bed (most common)

The Vision Miner 22 IDEX V4 has a powerful HEPA filtration fan that circulates air through the chamber. At high bed target temperatures (above 140 �C), the HEPA fan's airflow can cool the build plate faster than the heater can compensate � causing the bed heater to fault.

This is a known issue. The fix is a firmware update that introduces a three-tier HEPA management strategy during print startup:

Bed TargetHEPA Behavior During Bed Heating
Below 140 �CNormal operation � HEPA ramps to user-set speed
140�165 �CBed lowers to Z350 to reduce airflow impact, gradual HEPA ramp
Above 165 �CHEPA completely off during bed heating, then ramps to 50% for chamber and print

Info: IMPORTANT: If you experience bed heater faults during print startup, update your firmware to the latest version. This fix is included in recent firmware releases.

Other possible causes:

  • Slow heating � Poor bed insulation, damaged heater wiring, or a degraded heater element. The heater cannot raise temperature fast enough to satisfy the fault detection timeout.
  • Temperature sensor issues � Loose or damaged thermistor/PT1000 connection causing erratic readings. The firmware sees sudden temperature drops and faults.
  • PSU voltage drop � Insufficient or unstable power supply voltage. When multiple heaters activate simultaneously, voltage drops can reduce heater output. Check board voltages in the diagnostic TXT file (see below).
  • Incorrect PID parameters � Custom or corrupted PID tuning values can cause temperature oscillations large enough to trigger a fault. Re-run PID tuning from Macros ? System ? Calibration ? Temperature Tuning.

- **Aggressive M570 settings** � If someone manually tightened the fault detection parameters (`M570`), the heater may fault under normal conditions. The defaults are: - Bed (H2): `M570 H2 P60 T50 R5` � 60-second monitoring period, 50 �C tolerance - Chamber (H3): `M570 H3 P600 T70 R5` � 600-second monitoring period, 70 �C tolerance

2. Diagnostic Files

Starting with the latest firmware, the printer automatically logs temperatures and heater parameters during every print startup. If a heater fault occurs, two diagnostic files are saved to the SD card. If heating succeeds, the files are automatically deleted.

File Location

0:/sys/Result/print_start_log.csv
0:/sys/Result/print_start_log.txt

CSV File � Temperature Log

Logged every 10 seconds during bed heating, chamber heating, and heat soak. Each row contains:

ColumnDescription
Elapsed(s)Seconds since heating started
Bed(C)Bed heater temperature
ChamberAir(C)Chamber air sensor temperature
ChamberHeater(C)Chamber heater sensor temperature
LeftNozzle(C), RightNozzle(C)Nozzle temperatures
BedState, ChamberState, H0State, H1StateHeater states (active, standby, off, fault)
HEPA_RPM/100HEPA fan RPM divided by 100
HEPA_ReqHEPA fan requested speed (0�255)
ChamberFan_ReqChamber circulation fan requested speed
Vin_Board0, Vin_Board1Input voltage for mainboard and expansion board

The last line of the CSV indicates when the fault occurred:

  • RESULT: FAILED - Heater fault during bed heating
  • RESULT: FAILED - Heater fault during chamber heating
  • RESULT: FAILED - Heater fault during heat soak

TXT File � Configuration Snapshot

A full snapshot of heater configuration at print start:

  • Target temperatures for all tools, bed, and chamber
  • M307 heater model parameters (heating rate, cooling rate, dead time) for each heater
  • PID values (P, I, D) for each heater
  • M570 fault detection settings (monitoring period, temperature tolerance, max bad readings)
  • Heater monitors (temperature limits, actions)
  • Average PWM for each heater
  • Board voltages (current, min, max) for both boards
  • MCU temperatures for both boards
  • Firmware versions

3. How to Retrieve Diagnostic Files

  1. Open the Web Interface in your browser.

  2. Navigate to System in the file manager.

  3. Open the Result folder.

  4. Download print_start_log.csv and print_start_log.txt.

  5. Send both files to Vision Miner support.

Info: Note: These files only exist when a heater fault occurred during print startup. If the print started successfully, the files are automatically deleted.

4. Running the Heating Test

If the fault is intermittent or you want to test heating performance independently, use the built-in Heating Test macro. This test runs outside of a print job and produces its own detailed log files.

  1. Open the Web Interface.

  2. Navigate to Macros ? System ? Troubleshooting ? Heating Test.

  3. Select which heaters to test: Both (Bed + Chamber) is recommended.

  4. Choose the build plate target temperature (default: 160 �C).

  5. Set the build plate Z position for the test (default: 100 mm).

  6. The test will heat the selected heaters and log temperatures every 10 seconds.

The test creates its own log files in 0:/sys/Result/:

  • heating_test_<timestamp>.csv � temperature log
  • heating_test_<timestamp>.txt � heater configuration snapshot

If a fault occurs during the test, it is reported on screen and logged. Download the files and send them to support.

Info: Note: Hold the X or U endstop to cancel the test at any time.

5. Auto-Shutdown After Heater Fault

The printer can be configured to automatically shut down when a heater fault is detected. This is useful for unattended operation.

To configure auto-shutdown:

  1. Open the Web Interface.

  2. Navigate to Macros ? System ? Settings ? Faults.

  3. Run Action After Heater Fault.

  4. Select an option:

    • Disable � Fault displays a warning, printer stays powered on (default).
    • Immediate (0 s) � Printer shuts down immediately on fault.
    • Delay 30 / 60 / 120 s � Printer shows a countdown, then shuts down. You can cancel during the countdown.
    • Custom Duration � Enter a custom delay in seconds.

When a heater fault occurs:

  • The LEDs flash red.

  • If auto-shutdown is enabled, a countdown dialog appears. Press Keep power on to cancel the shutdown.

  • If the countdown expires or Shut down now is pressed, the printer powers off completely.

FAQ

The fault happens only at high bed temperatures. What should I do?

Update your firmware. The latest firmware includes a fix that manages HEPA fan speed during bed heating to prevent the fan from cooling the build plate. For bed targets above 165 �C, the HEPA fan is completely off during bed heating and then gradually ramps to 50% of its preset speed once the bed is ready.

The diagnostic files are not in the Result folder.

The diagnostic logging feature requires the latest firmware version. If your firmware predates this feature, no files will be created. Update your firmware and try again.

Can I disable bed or chamber fault detection?

Yes � via Macros ? System ? Settings ? Faults ? Bed Fault Detection (or Chamber Fault Detection). However, this is strongly discouraged. Fault detection is a fire safety mechanism. If you must disable it temporarily for testing, re-enable it immediately after.

What does support look for in these files?

  • CSV: Temperature ramp rate (is heating slower than expected?), temperature oscillations, HEPA fan interference, voltage drops on the boards, which heater faulted and when.
  • TXT: Whether PID parameters are correct (factory or custom), M570 settings, heater model parameters, firmware version.

Support

Vision Miner Support

On this page

Your feedback makes it better for everyone.