@dc42

Hello!

• Yes, 3 heaters are heating different parts of the same hot end as it is a large-scale pellet machine so they heat the screw in three different parts.

• Yes; I know we can get this heat creep however before the machine was connected to K-type thermocouples, I did not have this problem .

• Fig 3. is a picture that I took when doing the manual calibration so there was the 100K resistor at the input therefore it will show 25°C .However, normally arrangementnot calibration and at ambiance temperaure, all three sensors show the same 22°C . The problem came when I heat above 200°C the middle gets this +3 now +80°C

• I have changed the PT1000 to a new one and that is when I get the +7°C. I have come back to the previous and now it shows +8°C

• I swaped "middle" with "top" now I get this:

@droftarts

Thank you for your response.

Update:

1. Yes, at room temperature all sensors read the same temperature.
2. I measured the resistance in all the PT1000s and all of them indicate 1083 ohm which quite goe according to the datasheet (at 22°C --> 1085.7 ohm)
3. I performed the semi-automatic calibration (fig.1) and retry heating and I encounter the same issue +3°C in the "middle" indication.
4. I performed the manual calibration first with the 100K resistor (fig.2) and the indication was 25.5°C (fig.3). Then with the 220 (fig.4) and the indication was 236.7°C (fig.5). This indications showed that the system is well calibrated. However, when I heat again I still having this +3°C.
5. I changed the sensor for a new one (measured the resistance and gave 1083ohm like the others)
   then heating and now the indication is +7 °C (fig.6)

Fig.1

Fig.2

Fig.3

Fig.4

Fig.5

Fig.6

Hello!!

I've been upgrading a 3D printer and decided to change my thermocouples to PT1000 sensors. The printer has 3 heaters, thus 3 temperature sensors. When I changed and installed the PT1000 sensors, 2 of them are working well, but the one in the middle shows a 3-degree difference from the desired temperature (fig.1) and can't seem to regulate itself. I tried adjusting the R parameter, thinking it might be the issue, but it worsened the reading instead. Also, changing the parameters of the sensor I want to fix affects the other two sensors.

I also attempted to perform the PID tune again in case it would help, but I received a warning: "heater behavior was not consistent during tuning" for H2 and H3 (fig.2).

Could you provide me with an idea of what might be happening?

Fig.1

Fig.2

I'm using RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (standalone mode)

And Config.g

Thank you very much.; General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Gigabot X UWO edition" ; set printer name

; Network
M552 P192.168.100.8 S1 ; enable network and set IP address
M553 P255.255.255.0 ; set netmask
M554 P192.168.100.254 ; set gateway
M586 P0 S1 ; enable HTTP
M586 P1 S1 ; enable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0.0 S2 ; physical drive 0.0 goes forwards X
M569 P0.1 S1 ; physical drive 0.1 goes forwards YR
M569 P0.2 S0 ; physical drive 0.2 goes Backwards YL
M569 P0.3 S0 ; physical drive 0.3 goes forwards ZR n ZL
M569 P0.4 S1 ; physical drive 0.4 goes forwards Crammer
M569 P0.5 S0 ; physical drive 0.5 goes forwards Extruder
M584 X0.0 Y0.1:0.2 Z0.3 E0.4:0.5 ; set drive mapping
M350 X16 Y16:16 Z16 E16:16 I1 ; configure microstepping with interpolation
M92 X53.335 Y59.26:59.26 Z2015.75 E35.00:520.00 ; set steps per mm E crammer : extruder
;M201 X5000.00 Y3000.00:3000.00 Z100.00 E9000.00 ; Save set accelerations (mm/s^2)
M201 X500.00 Y500.00 Z20.00 E900.00 ; TEST set accelerations (mm/s^2)
;M203 X10740.00 Y6810.00:6810.00 Z480.00 E3600.00 ; SAVE set maximum speeds (mm/min)
M203 X10740.00 Y6810.00 Z480.00 E3600.00 ; TEST set maximum speeds (mm/min)
;M566 X5000.00 Y2000.00:2000.00 Z60.00 E500.00 P1 ;SAVE set maximum instantaneous speed changes (mm/min)
M566 X900.00 Y900.00 Z60.00 E500.00 ; TEST set maximum instantaneous speed changes (mm/min)
M204 P5100 T20000 ; set printing and travel accelerations (mm/s^2)
M906 X2800 Y2000:2000 Z2000 E850:2750 I30 ; set motor currents (mA) and motor idle factor in per cent
M572 D1 S0.03 ;Pressure advance
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X570 Y754.5 Z800 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"!io1.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io1.in
M574 Y2 S1 P"!io2.in+!io3.in " ; configure switch-type (e.g. microswitch) endstop for High end on YR and YL via pin io2.in + io3.in
M574 Z1 S1 P"!io4.in+!io5.in" ; configure switch-type (e.g. microswitch) endstop for low end on ZR and ZL via pin io4.in
;M574 A1 S3 ; configure switch-type (sensorless) endstop on Crammer
;M915 A S3 R0 F0 ; configure switch-type (sensorless) endstop on Crammer
;Z-probe
;M950 S0 C"io7.out"
;M558 P9 C"io7.in" H3 R0.5 F220 T6000 A1 B1 ; disable Z probe but set dive height, probe speed and travel speed
G31 P100 X20 Y-10 Z1.6
M557 X50:570 Y50:754.5 S80 ; define mesh grid

; Heaters
M308 S0 P"spi.cs0" Y"thermocouple-max31856" A"Bed" T "k" F 60 ; configure sensor 0 as thermocouple via CS pin spi.cs0
M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
M307 H0 B0 R0.186 C697.8 D3.40 S1.00 V23.9 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M140 S60 R50 ; heated bed "S" active temp "R" standby temp
M140 S-273.1 ; switch off bed heater
M143 H0 S110 ; Heated Bed Max temp
M308 S1 P"temp1" Y"pt1000" A"Bottom" ; configure sensor 1 as PT1000 on pin temp1
M950 H1 C"out1" T1 ; create heater 1 and map sensor 1
M307 H1 B0 R0.255 C1098.9 D15.33 S1.00 V24.1 ; disable bang-bang mode for heater and set PWM limit
;M308 S1 P"spi.cs1" Y"thermocouple-max31856" A"Bottom" ;T "k" F 60 ; configure sensor 1 as thermocouple via CS pin spi.cs1
;M950 H1 C"out1" T1 ; create nozzle heater output on out0 and map it to sensor 1
;M307 H1 R0.227 C1317.237:1317.237 D12.76 S1.00 V23.1 B0 I0 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 300C
M308 S2 P"temp2" Y"pt1000" A"Middle" ; configure sensor 1 as PT1000 on pin temp1
M950 H2 C"out2" T2 ; create heater 1 and map sensor 1
M307 H2 B0 R0.326 C953.9 D12.95 S1.00 V24.1 ; disable bang-bang mode for heater and set PWM limit
;M308 S2 P"spi.cs2" Y"thermocouple-max31856" A"Middle" ;T "k" F 60; configure sensor 2 as thermocouple via CS pin spi.cs2
;M950 H2 C"out2" T2 ; create nozzle heater output on out1 and map it to sensor 2
;M307 H2 R0.387 C763.827:763.827 D8.04 S1.00 V23.1 B0 I0 ; disable bang-bang mode for heater and set PWM limit
M143 H2 S280 ; set temperature limit for heater 1 to 280C
M308 S3 P"temp3" Y"pt1000" A"Top" ; configure sensor 1 as PT1000 on pin temp1
M950 H3 C"out3" T3 ; create heater 1 and map sensor 1
M307 H3 B0 R0.302 C728.2 D15.75 S1.00 V24.1 ; disable bang-bang mode for heater and set PWM limit
;M308 S3 P"spi.cs3" Y"thermocouple-max31856" A"Top" ;T "k" F 60 ; configure sensor 3 as thermocouple via CS pin spi.cs3
;M950 H3 C"out3" T3 ; create nozzle heater output on out2 and map it to sensor 3
;M307 H3 R0.329 C608.587:608.587 D10.43 S1.00 V23.1 B0 I0 ; disable bang-bang mode for heater and set PWM limit
M143 H3 S280 ; set temperature limit for heater 3 to 280C

; Fans
M950 F0 C"out9" Q5 ; create fan 0 on pin out8 and set its frequency
M106 P2 S255 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out8" Q500 ; create fan 1 on pin out9 and set its frequency
M106 P1 S255 H-1 ; set fan 1 value. Thermostatic control is turned off

; Tools
M563 P0 S"Pellet extrudeur" D0:1 H1:2:3 F0 ; define tool 0
M567 P0 E1:1 ; define Mix ratio
M568 P0 S1 ; Activation
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R140,0:140,0:140 S140,0:140,0:140 ; set initial tool 0 active and standby temperatures to 0C

; Miscellaneous
M501 ; load saved parameters from non-volatile memory
;Automatic power saving
M911 S20 R22 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

---

Thank you very much.

@fcwilt
Okay!!

Yes, I used to regularly save the complete configuration by downloading it directly from the DWC.

Is the printer at work just that I upgraded with the duet and is the first time this happen to me.

Thank you so much

@fcwilt

Oh yes, my bad sorry.

Do you have any idea of why that happened and why it restart the config?

Thank you so much for your help

@fcwilt
Hii!!!

By connecting the SD card to my computer and restoring the previous config.g file, I successfully established a connection to the DWC :D.However, I've noticed that I'm currently using the previous IP address instead of the ones you suggested.

Would it be advisable to change it to the recommended IP addresses, or should I leave it as is since the current setup is working fine?"

Thanks a lot!!!

@fcwilt

It sounds like the configuration might be resetting itself when attempting to re-establish the connection or set the IP through YAT. What's odd is that while the macros and configurations for components like the BLtouch remain intact, it's specifically the config/g that seems to be affected.

@fcwilt
This one?

And I already plug the SD card and the config all ready goen

@fcwilt
Okay, thanks!!
Yes, I have a computer where I'm connecting the duet by at ethernet cable.

@droftarts

M122
=== Diagnostics ===<LF>RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (standalone mode)<LF>Board ID: 08DJM-956BA-NA3TN-6JKDD-3SJ6R-KU8UU<LF>Used output buffers: 1 of 40 (1 max)<LF>=== RTOS ===<LF>Static ram: 150904<LF>Dynamic ram: 90544 of which 256 recycled<LF>Never used RAM 109632, free system stack 192 words<LF>Tasks: NETWORK(ready,30.1%,548) ETHERNET(notifyWait,0.0%,212) HEAT(delaying,0.0%,417) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,343) TMC(notifyWait,0.0%,105) MAIN(running,69.8%,1272) IDLE(ready,0.1%,29), total 100.0%<LF>Owned mutexes: USB(MAIN)<LF>=== Platform ===<LF>Last reset 00:01:29 ago, cause: power up<LF>Last software reset details not available<LF>Error status: 0x00<LF>Step timer max interval 91<LF>MCU temperature: min 20.3, current 32.8, max 32.9<LF>Supply voltage: min 0.1, current 0.1, max 0.2, under voltage events: 0, over voltage events: 0, power good: no<LF>12V rail voltage: min 0.1, curre[Warning: Maximal number of characters per line exceeded! Check the line break settings in [Terminal > Settings > Text] or increase the limit in [Terminal > Settings > Advanced].]

---


---

I'm not using any router the connection is made by cable

@fcwilt
Okay, no, unfortunately, I do not have the range :S

I tried to change the network but it did not work either. Now I'm afraid to lose all the configuration :S

@fcwilt said in Duet connection:

Even if I'm not using a wifi board? Im connecting by ethernet and never have this problem before.

Do you have any advice to overcome this issue?

Thank you!!

@fcwilt said in Duet connection:

DHCP

Yes , I have always used a IP address and I don't know how to connect using DHCP.

Yes, all the connections, wall, the ethernet all hahah

Hello!

I've encountered an issue while trying to connect to the Duet via Ethernet.

Here's some context: I've been working smoothly for about 2 months with a Duet 3HB6CH V 3.4, and it was connecting perfectly until today :(. After restarting the interface, it failed to reconnect. I accessed YAT and input the M552 command, which displayed the configured IP address and the actual IP address as 0.0.0.0 (fig 1).

Following that, I attempted to change the IP address by using the command M552 S1 P-IPaddress. Surprisingly, it responded with 'ok' but didn't confirm the complete IP address alteration. When I entered M552 again, it showed the configured IP as the one I inputted, but the actual IP remained 0.0.0.0 (fig 1). Consequently, I'm unable to establish a connection.

Do you have any insights into why this might be happening?

Thank you very much, and I hope you have a great rest of your day!

FIG.1


@gloomyandy
Hello!!

I configurated each heater as a heated chamber and I was able to do the tunning.

Thank you a lot

@gloomyandy

Okay, I'll check on the wiring and the tuning in heater chamber mode :).

Thank you and have a good day :D.

@gloomyandy
Thank you so much!!!
I'll try to do it in that way.

I have another question.

I sent a test print, and although the heaters reached the desired temperature, once the temperature was reached and it was about to start printing, the print job paused, and all temperature indicators suddenly showed 2000 (fig 1). Additionally, an error appeared in the console:

---

Error: Temperature reading fault on heater 1: sensor short to other wiring
Error: Temperature reading fault on heater 2: sensor short to other wiring
Error: Temperature reading fault on heater 3: sensor short to other wiring
Resume state saved

fig1

Is the issue you mentioned related to this error as well?

Thanks.

@gloomyandy

I heated the first heater, and it took approximately 20 minutes to reach the desired temperature.

@gloomyandy

Update:

I simultaneously heated all three heaters, and the following are the results:

Heater 3 displayed an error: "T0 Error: Heater 3 fault: temperature rising much more slowly than the expected 0.5°C/sec" (Fig 1).

While the other heaters continued to heat up, they reached the desired temperature after approximately 14 minutes for heater 1 (Fig 2) and 13 minutes for heater 2 (Fig 3)."

Fig 1

Fig 2
Fig 3

@gloomyandy

Yes, the heaters are capable of reaching the desired temperature as when I heat them they do it without problem. However, I am encountering difficulties with PID tuning. Also, when I attempt to initiate a print, the heaters initially reach the target temperature, but at the moment it start the printing process, they suddenly shut off, and all temperature readings show 2000. I'm uncertain whether this issue is pobably related to incomplete reception of the 24V power supply or if there's interference between the thermocouples and the stepper motors causing this problem.