GENERAL QUESTION

i have a clone prusai3 i have rebuilt its been working just fine i upgraded my control board to a RAMPS1.6 and now nothing, Now I turn the printer on and nothing screen blank, nothing works, power to the board 12.09 VDC a ok, now i hook up to the computer by way of Pronterface power up (still no display screen) but and every things works X,Y,Z all move, bed nothing, hot end nothing, pronterface reads the information and gives me a read out that seams okay but turn the unit on without the computer hookup nothing. any ideas? oh Merlin vs is 1.1.0.

... could be missing +5V from the PC-USB ... check the 5V-regulator on the board

---

Viktor
--------
Aufruf zum Projekt "Müll-freie Meere" - [reprap.org] -- Deutsche Facebook-Gruppe - [www.facebook.com]

Call for the project "garbage-free seas" - [reprap.org]

The ramps 1.6 (like the older 1.4) sends 12v to the mega2560 vin pin via diode D1, the mega2560 board does the 5v generation

So check for 12v on both sides of D1 (with gnd on a gnd pins), if it has 12v on both sides, its likely an issue on your mega2560. To test mega2560 board unplug the ramps from it and power it via 12v dc jack.



as for the screen, what screen does it have? (pictures if your unsure) and what did you enable in firmware?

Edited 2 time(s). Last edit at 05/11/2026 04:02AM by Dust.

thank you for the help, i changed out the mega2560 and it now works, now it's telling "MAXTEMP BED" I'M checking out all of the wires and thermistor now.

#define TEMP_SENSOR_0 1
#define TEMP_SENSOR_1 0
#define TEMP_SENSOR_2 0
#define TEMP_SENSOR_3 0
#define TEMP_SENSOR_BED 5

// This makes temp sensor 1 a redundant sensor for sensor 0. If the temperatures difference between these sensors is to high the print will be aborted.
//#define TEMP_SENSOR_1_AS_REDUNDANT
#define MAX_REDUNDANT_TEMP_SENSOR_DIFF 10

// Actual temperature must be close to target for this long before M109 returns success
#define TEMP_RESIDENCY_TIME 10 // (seconds)
#define TEMP_HYSTERESIS 3 // (degC) range of +/- temperatures considered "close" to the target one
#define TEMP_WINDOW 1 // (degC) Window around target to start the residency timer x degC early.

// The minimal temperature defines the temperature below which the heater will not be enabled It is used
// to check that the wiring to the thermistor is not broken.
// Otherwise this would lead to the heater being powered on all the time.
#define HEATER_0_MINTEMP 5
#define HEATER_1_MINTEMP 5
#define HEATER_2_MINTEMP 5
#define HEATER_3_MINTEMP 5
#define BED_MINTEMP 5

Thermistor type 5 is NTC device

Ie it follows this graph



So for a high temperature it has a low resistance. So your looking for a short.

Unplug the bed thermistor at the motherboard, stick multimeter probes up the two plug pins so you can measure the wires and thermistor resistance.
It should read 100K at 25℃

it reads 92.8k, i plugged a brand new in and still get the same error.

are these setting all okay?
============================ Thermal Settings ============================
//===========================================================================
//
//--NORMAL IS 4.7kohm PULLUP!-- 1kohm pullup can be used on hotend sensor, using correct resistor and table
//
//// Temperature sensor settings:
// -3 is thermocouple with MAX31855 (only for sensor 0)
// -2 is thermocouple with MAX6675 (only for sensor 0)
// -1 is thermocouple with AD595
// 0 is not used
// 1 is 100k thermistor - best choice for EPCOS 100k (4.7k pullup)
// 2 is 200k thermistor - ATC Semitec 204GT-2 (4.7k pullup)
// 3 is Mendel-parts thermistor (4.7k pullup)
// 4 is 10k thermistor !! do not use it for a hotend. It gives bad resolution at high temp. !!
// 5 is 100K thermistor - ATC Semitec 104GT-2 (Used in ParCan & J-Head) (4.7k pullup)
// 6 is 100k EPCOS - Not as accurate as table 1 (created using a fluke thermocouple) (4.7k pullup)
// 7 is 100k Honeywell thermistor 135-104LAG-J01 (4.7k pullup)
// 71 is 100k Honeywell thermistor 135-104LAF-J01 (4.7k pullup)
// 8 is 100k 0603 SMD Vishay NTCS0603E3104FXT (4.7k pullup)
// 9 is 100k GE Sensing AL03006-58.2K-97-G1 (4.7k pullup)
// 10 is 100k RS thermistor 198-961 (4.7k pullup)
// 11 is 100k beta 3950 1% thermistor (4.7k pullup)
// 12 is 100k 0603 SMD Vishay NTCS0603E3104FXT (4.7k pullup) (calibrated for Makibox hot bed)
// 13 is 100k Hisens 3950 1% up to 300°C for hotend "Simple ONE " & "Hotend "All In ONE"
// 20 is the PT100 circuit found in the Ultimainboard V2.x
// 60 is 100k Maker's Tool Works Kapton Bed Thermistor beta=3950
// 70 is the 100K thermistor found in the bq Hephestos 2
//
// 1k ohm pullup tables - This is not normal, you would have to have changed out your 4.7k for 1k
// (but gives greater accuracy and more stable PID)
// 51 is 100k thermistor - EPCOS (1k pullup)
// 52 is 200k thermistor - ATC Semitec 204GT-2 (1k pullup)
// 55 is 100k thermistor - ATC Semitec 104GT-2 (Used in ParCan & J-Head) (1k pullup)
//
// 1047 is Pt1000 with 4k7 pullup
// 1010 is Pt1000 with 1k pullup (non standard)
// 147 is Pt100 with 4k7 pullup
// 110 is Pt100 with 1k pullup (non standard)
// 998 and 999 are Dummy Tables. They will ALWAYS read 25°C or the temperature defined below.
// Use it for Testing or Development purposes. NEVER for production machine.
//#define DUMMY_THERMISTOR_998_VALUE 25
//#define DUMMY_THERMISTOR_999_VALUE 100
// :{ '0': "Not used", '4': "10k !! do not use for a hotend. Bad resolution at high temp. !!", '1': "100k / 4.7k - EPCOS", '51': "100k / 1k - EPCOS", '6': "100k / 4.7k EPCOS - Not as accurate as Table 1", '5': "100K / 4.7k - ATC Semitec 104GT-2 (Used in ParCan & J-Head)", '7': "100k / 4.7k Honeywell 135-104LAG-J01", '71': "100k / 4.7k Honeywell 135-104LAF-J01", '8': "100k / 4.7k 0603 SMD Vishay NTCS0603E3104FXT", '9': "100k / 4.7k GE Sensing AL03006-58.2K-97-G1", '10': "100k / 4.7k RS 198-961", '11': "100k / 4.7k beta 3950 1%", '12': "100k / 4.7k 0603 SMD Vishay NTCS0603E3104FXT (calibrated for Makibox hot bed)", '13': "100k Hisens 3950 1% up to 300°C for hotend 'Simple ONE ' & hotend 'All In ONE'", '60': "100k Maker's Tool Works Kapton Bed Thermistor beta=3950", '55': "100k / 1k - ATC Semitec 104GT-2 (Used in ParCan & J-Head)", '2': "200k / 4.7k - ATC Semitec 204GT-2", '52': "200k / 1k - ATC Semitec 204GT-2", '-3': "Thermocouple + MAX31855 (only for sensor 0)", '-2': "Thermocouple + MAX6675 (only for sensor 0)", '-1': "Thermocouple + AD595", '3': "Mendel-parts / 4.7k", '1047': "Pt1000 / 4.7k", '1010': "Pt1000 / 1k (non standard)", '20': "PT100 (Ultimainboard V2.x)", '147': "Pt100 / 4.7k", '110': "Pt100 / 1k (non-standard)", '998': "Dummy 1", '999': "Dummy 2" }
#define TEMP_SENSOR_0 1
#define TEMP_SENSOR_1 0
#define TEMP_SENSOR_2 0
#define TEMP_SENSOR_3 0
#define TEMP_SENSOR_BED 5

// This makes temp sensor 1 a redundant sensor for sensor 0. If the temperatures difference between these sensors is to high the print will be aborted.
//#define TEMP_SENSOR_1_AS_REDUNDANT
#define MAX_REDUNDANT_TEMP_SENSOR_DIFF 10

// Actual temperature must be close to target for this long before M109 returns success
#define TEMP_RESIDENCY_TIME 10 // (seconds)
#define TEMP_HYSTERESIS 3 // (degC) range of +/- temperatures considered "close" to the target one
#define TEMP_WINDOW 1 // (degC) Window around target to start the residency timer x degC early.

// The minimal temperature defines the temperature below which the heater will not be enabled It is used
// to check that the wiring to the thermistor is not broken.
// Otherwise this would lead to the heater being powered on all the time.
#define HEATER_0_MINTEMP 5
#define HEATER_1_MINTEMP 5
#define HEATER_2_MINTEMP 5
#define HEATER_3_MINTEMP 5
#define BED_MINTEMP 5

// When temperature exceeds max temp, your heater will be switched off.
// This feature exists to protect your hotend from overheating accidentally, but *NOT* from thermistor short/failure!
// You should use MINTEMP for thermistor short/failure protection.
#define HEATER_0_MAXTEMP 275
#define HEATER_1_MAXTEMP 275
#define HEATER_2_MAXTEMP 275
#define HEATER_3_MAXTEMP 275
#define BED_MAXTEMP 150

// If you want the M105 heater power reported in watts, define the BED_WATTS, and (shared for all extruders) EXTRUDER_WATTS
//#define EXTRUDER_WATTS (12.0*12.0/6.7) // P=U^2/R
//#define BED_WATTS (12.0*12.0/1.1) // P=U^2/R

Edited 2 time(s). Last edit at 05/11/2026 11:31PM by yar60.

this is what i get when Pronterface reads it...



Connecting...
start
Printer is now online.
echo:Marlin 1.1.0-RC5
echo: Last Updated: 2016-04-01 12:00 | Author: Ray B
Compiled: Feb 25 2026
echo: Free Memory: 3188 PlannerBufferBytes: 1232
echo:Hardcoded Default Settings Loaded
echoteps per unit:
echo: M92 X80.00 Y80.00 Z2560.00 E83.00
echo:Maximum feedrates (mm/s):
echo: M203 X125.00 Y125.00 Z2.00 E22.00
echo:Maximum Acceleration (mm/s2):
echo: M201 X1000 Y1000 Z5 E500
echo:Accelerations: P=printing, R=retract and T=travel
echo: M204 P3000.00 R3000.00 T3000.00
echo:Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate (mm/s), B=minimum segment time (ms), X=maximum XY jerk (mm/s), Z=maximum Z jerk (mm/s), E=maximum E jerk (mm/s)
echo: M205 S0.00 T0.00 B20000 X20.00 Z0.40 E5.00
echo:Home offset (mm):
echo: M206 X0.00 Y0.00 Z0.00
echo:Material heatup parameters:
echo: M145 S0 H212 B50 F0
echo: M145 S1 H240 B70 F0
echoID settings:
echo: M301 P22.20 I1.08 D114.00 C100.00 L20
echo:Filament settings: Disabled
echo: M200 D3.00
echo: M200 D0
Error:MAXTEMP triggered, system stopped! Heater_ID: bed
[ERROR] Error:MAXTEMP triggered, system stopped! Heater_ID: bed

Errorrinter halted. kill() called!
[ERROR] Errorrinter halted. kill() called!

echoD init fail

Yes those setting are fine

Indicates a hardware fault. potentially a dead ADC pin on the mega


In Configuration.h Find "#define MOTHERBOARD BOARD_RAMPS_14_EFB"

and add this directly under it

#define TEMP_1_PIN                          14  // Analog Input
#define TEMP_BED_PIN                     15  // Analog Input

This swaps the bed thermistor plug from to the unused thermistor plug in firmware.

build and upload this and move the bed thermistor plug to the right most set of thermistor pins and test it

Marlin 1.1.0-RC5 is positively ancient code

thank you for all your help. i'm working on firmware 2.*.*

Well the running firmware says

"Connecting...
start
Printer is now online.
echo:Marlin 1.1.0-RC5
echo: Last Updated: 2016-04-01 12:00 | Author: Ray B
Compiled: Feb 25 2026"

So this doesn't match with "i'm working on firmware 2.*.*"

Hi All.
Has anyone drawn a tree of the files used in compiling Marlin ?
I am trying to come to grips with how the various files relate to each other, and the naming of things primarilly the main processor, in my case an Arduino Due with direct connections between the SAM3X and the level-shifters/sensors, and how to tell whatever module needs it, which configuration.h to load.

@sbkenn

Level shifters have little to do with firmware. They simply translate voltages between devices. Marlin generally doesn't know or care whether a signal passes through a level shifter or not.

The relationship is more like:

Marlin
↓
HAL (SAM3X / Due)
↓
Pin definitions
↓
MCU GPIO pins
↓
Level shifters, drivers, sensors, etc.


Eg

Configuration.h you set MOTHERBOARD, this defines what pins and interfaces are used for what.
It also has a list of valid build environments

eg

#elif MB(RADDS)
  #include "sam/pins_RADDS.h"                       // SAM3X8E                              env: DUE env: DUE_USB

So it uses build env DUE or DUE_USB
This is how code for MPU is selected

[env: DUE]
platform          = atmelsam
#platform_packages = toolchain-gccarmnoneeabi@1.120301.0   # Otherwise it's GCC 7.2.1
board             = due
build_src_filter  = ${common.default_src_filter} +<src/HAL/DUE> +<src/HAL/shared/backtrace>

The +<src/HAL/DUE> tells marlin to build the code in that directory


the platform also sets a defines ARDUINO_ARCH_SAM, which is used in code to select platform-specific code

eg

#elif defined(ARDUINO_ARCH_SAM)
  #define HAL_PATH(PATH, NAME) XSTR(PATH/HAL/DUE/NAME)

Edited 8 time(s). Last edit at 06/21/2026 11:56AM by Dust.

What I meant by mentioning the level shifters is that I'm not using a "motherboard", effectively direct connection to the real world.

Apologies for rather basic questions but : How do I reload the Marlin/DUE project after just closing Visual Studio ? I didn't specifically save it.

The autobuild window shows the right parameters but when I try to build :

PS C:\Users\SBK\Projects\Marlin\Marlin-2.1.2.7> platformio run --silent -e DUE
platformio : The term 'platformio' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is
correct and try again.
At line:1 char:1
+ platformio run --silent -e DUE
+ ~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (platformiotring) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS C:\Users\SBK\Projects\Marlin\Marlin-2.1.2.7> echo "done" >"C:\Users\SBK\AppData\Local\Temp\ipc"

Edited 1 time(s). Last edit at 06/22/2026 10:19AM by sbkenn.

Delete the directory

C:\Users\SBK\.platformio

Then restart VSCode. This will reinstall PlatformIO.

Windows has either lost the path or removed the executable.

What do I need to open to pick up where I stopped, or what do I need to save in order to reopen the project ?