1047 : PT1000 w/ 4.7k Ohms (E3D) max temp error on boot #242

mendozabrah · 2022-07-23T11:44:15Z

E3D PT1000 thermistor plugged directly into Ender 3 v2 4.2.2 RCT6 board, produces MAX TEMP ERR after switching on printer. Firmware was compiled with TEMP_SENSOR_0 1047

Thermistor functions correctly on other firmware (Jyer's and Unified) with TEMP_SENSOR_0 1047.

To Reproduce

Plug E3D RTD PT1000 temp sensor to 4.2.2 (RCT6) board Ender 3 V2 (no amplifer)
Change TEMP_SENSOR_0 1 to TEMP_SENSOR_0 1047 in Configuration.h
Update firmware
Turn on printer

Expected behavior
After printer boots up, the following errors show in the screenshots

Screenshots

Version
Ender3V2-422-BLT 20220716 Mid year release

The text was updated successfully, but these errors were encountered:

ZipperZ · 2022-07-23T13:01:05Z

Same here with 1010 sensor (PT1000, 1k pull-up), 427 board.

Error is triggered by
(pos && r > temp_range[e].raw_max)
in line 2353 of file "temperature.cpp"

Was not able to track it down even further, but still going deeper.

ghost · 2022-07-23T14:33:36Z

This problem happened to me a couple of times when I was already printing, after I turned it off and on again it started working normally.
I noticed that when this message happens, the temperature of the extruder is oscillating.

ZipperZ · 2022-07-23T17:02:10Z

Ok, I am not yet sure how that works on a standard Marlin, but basically _TEMP_MAX_E(NR) macro functions incorrectly, because temp_range[NR].raw_max is not initialized.

Sorry I am no way near "programmer"...
Very dirty workaround(temperature.cpp line ~2651):

#if _MINMAX_TEST(0, MAX)
_TEMP_MAX_E(0);
#endif

Add line:

#if _MINMAX_TEST(0, MAX)
temp_range[0].raw_max = 65535;
_TEMP_MAX_E(0);
#endif

ZipperZ · 2022-07-23T22:53:04Z

Ok, I am not yet sure how that works on a standard Marlin, but basically _TEMP_MAX_E(NR) macro functions incorrectly, because temp_range[NR].raw_max is not initialized.

Sorry I am no way near "programmer"... Very dirty workaround(temperature.cpp line ~2651):

#if _MINMAX_TEST(0, MAX) _TEMP_MAX_E(0); #endif

Add line:

#if _MINMAX_TEST(0, MAX) temp_range[0].raw_max = 65535; _TEMP_MAX_E(0); #endif

And now after "dirty workaround" M501 triggers MAXTEMP error...

mriscoc · 2022-07-24T00:32:06Z

The thermistor table for the type 1047 is ordered in inverted form with respect to the type 1, that causes some compilation issues with the algorithm of the custom G-code C104.

mriscoc · 2022-07-24T04:36:37Z

Please test with the sources from: https://github.com/mriscoc/Ender3V2S1

ZipperZ · 2022-07-24T07:00:29Z

With sensor 1010 the printer acts the same.
Right after boot error is triggered.

If I initialize temp_range[0].raw_max, then I am able to boot and use the printer until command M501, which also triggers the error.

mendozabrah · 2022-07-24T09:51:02Z

Likewise, the same with sensor 1047. Still throwing MAX TEMP error after boot

mriscoc · 2022-07-24T16:22:02Z

I don't have those sensors to test, I will try to find what's triggering that error message.

Please, disable in configuration.h:

//#define ProUIex 1
//#define HAS_GCODE_PREVIEW 1
//#define HAS_TOOLBAR 1
//#define HAS_PIDPLOT 1

ZipperZ · 2022-07-25T12:01:29Z

With those options disabled the code does not compile

Marlin\src\lcd\e3v2\proui\dwin.cpp: In function 'float Tram(uint8_t)': Marlin\src\lcd\e3v2\proui\dwin.cpp:2452:19: error: 'MESH_MIN_X' was not declared in this scope 2452 | LIMIT(xpos, MESH_MIN_X, MESH_MAX_X); | ^~~~~~~~~~ Marlin\src\lcd\e3v2\proui\dwin.cpp:2452:31: error: 'MESH_MAX_X' was not declared in this scope 2452 | LIMIT(xpos, MESH_MIN_X, MESH_MAX_X); | ^~~~~~~~~~ Marlin\src\lcd\e3v2\proui\dwin.cpp:2453:19: error: 'MESH_MIN_Y' was not declared in this scope 2453 | LIMIT(ypos, MESH_MIN_Y, MESH_MAX_Y); | ^~~~~~~~~~ Marlin\src\lcd\e3v2\proui\dwin.cpp:2453:31: error: 'MESH_MAX_Y' was not declared in this scope 2453 | LIMIT(ypos, MESH_MIN_Y, MESH_MAX_Y); | ^~~~~~~~~~ *** [.pio\build\STM32F103RE_creality\src\src\lcd\e3v2\proui\dwin.cpp.o] Error 1 In file included from Marlin\src\lcd\e3v2\proui\../../../inc/MarlinConfigPre.h:66, from Marlin\src\lcd\e3v2\proui\endstop_diag.cpp:22:

After changing EITHER(MESH_BED_LEVELING, AUTO_BED_LEVELING_UBL) to ANY(MESH_BED_LEVELING, AUTO_BED_LEVELING_UBL, AUTO_BED_LEVELING_BILINEAR)
In Configuration_adv.h in line ~2105 the code compiled.

Now everything seems fine. The board boots, M501 does not cause error either.

Is it memory constraint of STM32F103RC (I assume this uC is used in 427?) If it is, then would it help if I change it to RE? Only I do not know what kind of bootloader is used and where to get it.

mendozabrah · 2022-07-28T12:27:56Z

With those options disabled the code does not compile

Marlin\src\lcd\e3v2\proui\dwin.cpp: In function 'float Tram(uint8_t)': Marlin\src\lcd\e3v2\proui\dwin.cpp:2452:19: error: 'MESH_MIN_X' was not declared in this scope 2452 | LIMIT(xpos, MESH_MIN_X, MESH_MAX_X); | ^~~~~~~~~~ Marlin\src\lcd\e3v2\proui\dwin.cpp:2452:31: error: 'MESH_MAX_X' was not declared in this scope 2452 | LIMIT(xpos, MESH_MIN_X, MESH_MAX_X); | ^~~~~~~~~~ Marlin\src\lcd\e3v2\proui\dwin.cpp:2453:19: error: 'MESH_MIN_Y' was not declared in this scope 2453 | LIMIT(ypos, MESH_MIN_Y, MESH_MAX_Y); | ^~~~~~~~~~ Marlin\src\lcd\e3v2\proui\dwin.cpp:2453:31: error: 'MESH_MAX_Y' was not declared in this scope 2453 | LIMIT(ypos, MESH_MIN_Y, MESH_MAX_Y); | ^~~~~~~~~~ *** [.pio\build\STM32F103RE_creality\src\src\lcd\e3v2\proui\dwin.cpp.o] Error 1 In file included from Marlin\src\lcd\e3v2\proui\../../../inc/MarlinConfigPre.h:66, from Marlin\src\lcd\e3v2\proui\endstop_diag.cpp:22:

After changing EITHER(MESH_BED_LEVELING, AUTO_BED_LEVELING_UBL) to ANY(MESH_BED_LEVELING, AUTO_BED_LEVELING_UBL, AUTO_BED_LEVELING_BILINEAR) In Configuration_adv.h in line ~2105 the code compiled.

Now everything seems fine. The board boots, M501 does not cause error either.

Is it memory constraint of STM32F103RC (I assume this uC is used in 427?) If it is, then would it help if I change it to RE? Only I do not know what kind of bootloader is used and where to get it.

This worked for me too, 1047 thermistor works perfectly ! Appreciate the fix @mriscoc and @ZipperZ

mriscoc · 2022-10-16T07:13:55Z

I want to address this bug disabling the custom G-code C104 for PT1000 thermistor. Anyone to test some experimental builds?

ZipperZ · 2022-10-16T08:01:22Z

I want to address this bug disabling the custom G-code C104 for PT1000 thermistor. Anyone to test some experimental builds?

Hi, I could test it. Do not promise very fast feedback, but I will

NiLMoXiE · 2022-10-16T14:02:49Z

With the options above commented out and ZipperZ's change I still get a compile error (I am using the source from special releases E3V2-422-BLT-UBL):

Marlin\src\lcd\e3v2\proui\dwin.cpp: In function 'void Draw_PrintDone()':
Marlin\src\lcd\e3v2\proui\dwin.cpp:563:5: error: 'Preview_Show' was not declared in this scope
563 | Preview_Show();
| ^~~~~~~~~~~~
Compiling .pio\build\STM32F103RC_creality\src\src\libs\least_squares_fit.cpp.o
Marlin\src\lcd\e3v2\proui\dwin.cpp: In function 'void DWIN_Print_Started()':
Marlin\src\lcd\e3v2\proui\dwin.cpp:1542:24: error: 'Preview_Invalidate' was not declared in this scope
1542 | if (Host_Printing()) Preview_Invalidate();
| ^~~~~~~~~~~~~~~~~~
*** [.pio\build\STM32F103RC_creality\src\src\lcd\e3v2\proui\dwin.cpp.o] Error 1

Commenting out Preview_Show and Preview_Invalidate allowed it to compile but I can't test yet as I am waiting on parts.

mriscoc · 2022-10-16T16:37:32Z

A 422 BLTUBL version could be fine for all of you?

ZipperZ · 2022-10-16T16:45:54Z

A 422 BLTUBL version could be fine for all of you?

I am using 427 and my sensor is 1010 (changed resistor on the board). Also the thermistor table extended from the "original"
Maybe you could create a branch for testing? (we would customize according our setups?)

mriscoc · 2022-10-16T19:28:06Z

EDIT: I think that this issue is now fixed in the main branch

OK, it is ready to test: ~~https://github.com/mriscoc/Ender3V2S1/tree/Ender3V2S1-NO_C104~~
Do not mix with the release branch.

NiLMoXiE · 2022-10-16T20:30:39Z

Getting file not found - Marlin/lib/proui/STM32F1/libproui_ubl.a - is there a reason this was left out?

Can I copy from the release branch or is a different version required?

mriscoc · 2022-10-17T00:28:54Z

Sorry, my mistake, rename Marlin/lib/proui/STM32F1/libproui.a to libproui_ubl.a

These sources are only for compile 4.2.2 or 4.2.7 BLTUBL versions.

mriscoc · 2022-10-17T00:37:34Z

Can I copy from the release branch or is a different version required?

No, please don't mix with files from the release branch.

oddmolecules · 2022-10-17T22:50:23Z

that seems to have it working for me, running a pid test now. I was getting a FileNotFoundError: [Errno 2] No such file or directory: 'Marlin/lib/proui/stm32f1/libproui_mbl.a'
Its the manual mesh version, not the ubl, just had to swap libproui_ubl.a to mbl and then make the ubl changes that i want.

Thank you for taking the time to fix this for us minority of pt1000 users!! definitely appreciated!! will get back after testing further if there are any problems.

mriscoc · 2022-10-17T22:57:57Z

that seems to have it working for me, running a pid test now. I was getting a FileNotFoundError: [Errno 2] No such file or directory: 'Marlin/lib/proui/stm32f1/libproui_mbl.a' It's the manual mesh version, not the ubl, just had to swap libproui_ubl.a to mbl and then make the ubl changes that i want.

Thank you for taking the time to fix this for us minority of pt1000 users!! definitely appreciated!! will get back after testing further if there are any problems.

Manual mesh needs another libproui library. This FIRST test is only to verify that the origin of the bug is in the C104 code. I will prepare others tests to get firmware that can be used by anyone without taking care about the thermistor type.

Thank you for helping me to narrow down where the problem is.

mriscoc · 2022-10-19T07:13:08Z

I think that this issue is now fixed in the main branch.

wwian · 2022-10-20T23:42:43Z

Miguel, will you be making precompiled binary files with this fix?

mriscoc · 2022-10-21T01:11:40Z

Miguel, will you be making precompiled binary files with this fix?

Typically, special configurations such as PT1000 thermistor are compiled by the users themselves, but it is possible to request a sponsored compilation, see the readme at https://github.com/mriscoc/Special_Configurations

ghost · 2022-10-23T03:11:12Z

Getting the same error, I updated the firmware with the newest version today. I only changed the "BED_MAXTEMP" in configuration.h from 110 to 120. It My printer worked great for 3 days now it fails every time unless I use a precompiled marlin version which is so odd. Weird thing is that the printer will work sometimes only if an SD card is inserted. My printer's hardware is completely stock other than this firmware.

mriscoc · 2022-10-23T05:06:06Z

Getting the same error, I updated the firmware with the newest version today. I only changed the "BED_MAXTEMP" in configuration.h from 110 to 120. It My printer worked great for 3 days now it fails every time unless I use a precompiled marlin version which is so odd. Weird thing is that the printer will work sometimes only if an SD card is inserted. My printer's hardware is completely stock other than this firmware.

This page is only for issues with the thermistor PT1000 (type 1047 or 1010)

kiu345 · 2022-10-28T10:04:45Z

I think that this issue is now fixed in the main branch.

Compiled with ZIP Ender3V2S1-20221002, still getting the error. ~~Tried workaround, nothing changed~~. Any idea?

Update: Workaround worked, a "clean all, then build it" did it...

mriscoc · 2022-10-30T06:32:29Z

I think that this issue is now fixed in the main branch.

Compiled with ZIP Ender3V2S1-20221002, still getting the error. ~~Tried workaround, nothing changed~~. Any idea?

Update: Workaround worked, a "clean all, then build it" did it...

Use the main branch, the 20221002 is previous to the fix.

mriscoc · 2022-12-05T15:07:29Z

No more user feedback

github-actions · 2023-04-23T14:06:48Z

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

mriscoc added the bug: Potential? label Jul 24, 2022

mriscoc added bug: Confirmed Something isn't working, the bug was confirmed. and removed bug: Potential? labels Aug 25, 2022

mriscoc closed this as completed Dec 5, 2022

github-actions bot locked and limited conversation to collaborators Apr 23, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

1047 : PT1000 w/ 4.7k Ohms (E3D) max temp error on boot #242

1047 : PT1000 w/ 4.7k Ohms (E3D) max temp error on boot #242

mendozabrah commented Jul 23, 2022

ZipperZ commented Jul 23, 2022

ghost commented Jul 23, 2022

ZipperZ commented Jul 23, 2022

ZipperZ commented Jul 23, 2022

mriscoc commented Jul 24, 2022 •

edited

Loading

mriscoc commented Jul 24, 2022

ZipperZ commented Jul 24, 2022

mendozabrah commented Jul 24, 2022

mriscoc commented Jul 24, 2022 •

edited

Loading

ZipperZ commented Jul 25, 2022 •

edited

Loading

mendozabrah commented Jul 28, 2022

mriscoc commented Oct 16, 2022

ZipperZ commented Oct 16, 2022

NiLMoXiE commented Oct 16, 2022

mriscoc commented Oct 16, 2022

ZipperZ commented Oct 16, 2022

mriscoc commented Oct 16, 2022 •

edited

Loading

NiLMoXiE commented Oct 16, 2022 •

edited

Loading

mriscoc commented Oct 17, 2022 •

edited

Loading

mriscoc commented Oct 17, 2022 •

edited

Loading

oddmolecules commented Oct 17, 2022

mriscoc commented Oct 17, 2022 •

edited

Loading

mriscoc commented Oct 19, 2022

wwian commented Oct 20, 2022

mriscoc commented Oct 21, 2022

ghost commented Oct 23, 2022

mriscoc commented Oct 23, 2022 •

edited

Loading

kiu345 commented Oct 28, 2022 •

edited

Loading

mriscoc commented Oct 30, 2022 •

edited

Loading

mriscoc commented Dec 5, 2022

github-actions bot commented Apr 23, 2023

1047 : PT1000 w/ 4.7k Ohms (E3D) max temp error on boot #242

1047 : PT1000 w/ 4.7k Ohms (E3D) max temp error on boot #242

Comments

mendozabrah commented Jul 23, 2022

ZipperZ commented Jul 23, 2022

ghost commented Jul 23, 2022

ZipperZ commented Jul 23, 2022

ZipperZ commented Jul 23, 2022

mriscoc commented Jul 24, 2022 • edited Loading

mriscoc commented Jul 24, 2022

ZipperZ commented Jul 24, 2022

mendozabrah commented Jul 24, 2022

mriscoc commented Jul 24, 2022 • edited Loading

ZipperZ commented Jul 25, 2022 • edited Loading

mendozabrah commented Jul 28, 2022

mriscoc commented Oct 16, 2022

ZipperZ commented Oct 16, 2022

NiLMoXiE commented Oct 16, 2022

mriscoc commented Oct 16, 2022

ZipperZ commented Oct 16, 2022

mriscoc commented Oct 16, 2022 • edited Loading

NiLMoXiE commented Oct 16, 2022 • edited Loading

mriscoc commented Oct 17, 2022 • edited Loading

mriscoc commented Oct 17, 2022 • edited Loading

oddmolecules commented Oct 17, 2022

mriscoc commented Oct 17, 2022 • edited Loading

mriscoc commented Oct 19, 2022

wwian commented Oct 20, 2022

mriscoc commented Oct 21, 2022

ghost commented Oct 23, 2022

mriscoc commented Oct 23, 2022 • edited Loading

kiu345 commented Oct 28, 2022 • edited Loading

mriscoc commented Oct 30, 2022 • edited Loading

mriscoc commented Dec 5, 2022

github-actions bot commented Apr 23, 2023

mriscoc commented Jul 24, 2022 •

edited

Loading

mriscoc commented Jul 24, 2022 •

edited

Loading

ZipperZ commented Jul 25, 2022 •

edited

Loading

mriscoc commented Oct 16, 2022 •

edited

Loading

NiLMoXiE commented Oct 16, 2022 •

edited

Loading

mriscoc commented Oct 17, 2022 •

edited

Loading

mriscoc commented Oct 17, 2022 •

edited

Loading

mriscoc commented Oct 17, 2022 •

edited

Loading

mriscoc commented Oct 23, 2022 •

edited

Loading

kiu345 commented Oct 28, 2022 •

edited

Loading

mriscoc commented Oct 30, 2022 •

edited

Loading