@julian_wicht said in Problem with PID-Tuning (RRF 3.4.0-b7):

@argo
i try it now with M303 H1 S240 to PID my Left Hotend

It did not make a difference whether i PID via tool or heater, the result are now the Heater are not Starting

I had not used the printer for the last few days and wanted to start it again today for a print job and wondered why the bed heater did not start.
Then I noticed that in the config-override.g file is still the new PID value for the heating bed.

M307 H0 R0.295 K0.200:0.000 D6.01 E1.35 S1.00 B0 ; PID tune for bed at 85c

After I changed this to the old PID as mentioned in the first post, the bed has also worked again.

M307 H0 A137.2 C650.1 D3.2 S1.00 V23.9 B0

@dogma2k in your #3 I had the same issue. Then I cut a USB 3.0 cable and use this Cable, Problem fixed

There is also in the wiki a notice about this trick

@argo

i try it now with M303 H1 S240 to PID my Left Hotend

Auto tuning heater 1 completed after 3 idle and 5 tuning cycles in 341 seconds. This heater needs the following M307 command:
 M307 H1 R2.775 K0.438:0.000 D5.25 E1.35 S1.00 B0 V23.6
Send M500 to save this command in config-override.g

After i Try to Put the New M307 Command in the Console i got this message

M307 H1 R2.775 K0.438:0.000 D5.25 E1.35 S1.00 B0 V23.6
Warning: M307: Heater 1 predicted maximum temperature at full power is 417°C

and now if i try to Heat up Standby or Active Mode the heater not starting

If i put my old PID in the Console the Heater works again great

@phaedrux

• E3D V6 Hotend
• 24V 40W High Precision Heater Cartridges from E3D
• V6 Silicone Socks from E3D
• Fans on the Side are 24V Turbine Fan 40mm * 10mm 4010 DC Radial Cooling Fans
• The Fans on the Front are for T0 30x30x10 and on T1 40x40x10
  -- The Resion is on T0 i have installed a IR Sensor and it takes some Place (See Picture)
• Nozzle on both are Original E3D 0,4 on T0 and 0,6 on T1

Re: New heater tuning algorithm

Hello,

I had last done a PID tuning in RRF3.0 or a bit earlier and by the post that there should be a new algorithm in RRF3.2beta3.2 or newer I did this PID again.

My old values in config-override.g were

; config-override.g file generated in response to M500 at 2020-08-18 09:33
; This is a system-generated file - do not edit
; Heater model parameters
M307 H0 A137.2 C650.1 D3.2 S1.00 V23.9 B0
M307 H1 A477.6 C169.6 D3.6 S1.00 V23.8 B0
M307 H2 A382.6 C148.6 D3.1 S1.00 V23.8 B0

Now I use the firmware version RRF 3.4.0-b7 and have done a PID tuning again with the following results (IDEX system)

M307 H0 R0.295 K0.200:0.000 D6.01 E1.35 S1.00 B0 ; PID tune for bed at 85c
M307 H1 R2.734 K0.423:0.102 D5.00 E1.35 S1.00 B0 V23.6 ; PID Tune for Hotend Left 240c
M307 H2 R2.503 K0.511:0.022 D5.11 E1.35 S1.00 B0 V23.6 ; PID Tune for Hotend Right 240c

On the following picture you can see a yellow line that I have drawn.
On the left of the line is an extreme fluctuation of the temperature with the results of the PID under the beta firmware.
To the right of the line is the old PID value which keeps a stable temperature.

Here is an excerpt from the Config.g for the heating elements

; Heaters
M308 S0 P"bedtemp" Y"thermistor" A"Bett" T100000 B3950             ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0                                              ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B0 S1.00                                                   ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                                            ; map heated bed to heater 0
M143 H0 S121                                                       ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" A"X-Achse" T100000 B4725 C7.06e-8  ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1                                               ; create nozzle heater output on e0heat and map it to sensor 1
M143 H1 S261                                                       ; Temperatur Limit
M307 H1 B0 S1.00                                                   ; disable bang-bang mode for heater  and set PWM limit
M308 S2 P"e1temp" Y"thermistor" A"U-Achse" T100000 B4725 C7.06e-8  ; configure sensor 2 as thermistor on pin e1temp
M950 H2 C"e1heat" T2                                               ; create nozzle heater output on e1heat and map it to sensor 2
M143 H2 S261                                                       ; Temperatur Limit
M307 H2 B0 S1.00  

I don't think I did anything wrong, I used the following codes for the respective tools for the respective tools

M303 T0 S240
M303 T1 S240

Is there an error here with me or is it a firmware error?

best regards
Julian

Thank you for all your help and tips.

The reply email from Roland was very positive, thank you for this tip.

This Threat can be closed.

@phaedrux

Since the accelerometer gave a result on the 1st measurement, and I have checked the wiring several times in the meantime, I can rule out incorrect wiring.

As I said, the 1st measurement it worked, each subsequent measurement was the message in the CSV "Failed to collect data from accelerometer".
What I notice now is, I had the CS cable not spatially separated from the others.
Here should arrive but maximum only no data, that thereby a damage in the 3.3V circle arise I can not imagine, right?

I had bought it July 2020 at Makerdise (dot) com but unfortunately there seems to be this store no longer

@phaedrux

Check the LEDs on the Duet. There should be a red LED illuminated between the USB connector and the Reset button. The red 5V LED at the edge of the board should also be lit, so should the green 3.3V LED. (Note: the Duet 06 doesn't have the 5V or 3.3V LED)

• LED between usb and reset is ON
• 5V LED is ON
• 3.3V LED is OFF

If the red LEDs are lit but not the green 3.3V LED then most likely there is a short between the 3.3V power rail and ground. Disconnect the Duet from USB, then remove all endstop and Z probe connectors from the Duet. If you have a Duex 2 or Duex 5 connected as well, disconnect the ribbon cable joining them too. Then reconnect the USB cable and check the LEDs again.

• everything is disconnected, and the Board is connection with PC, no Change about the LED's

The DIAG LED between the USB connector and the SD card socket may or may not be lit, but can help diagnosis. (Note: the Duet 06/085 doesn't have the DIAG LED.)

• i have a Diag LED but its OFF

• SD Card is not in the Board

Connect to a PC via USB and look for the port

• there is nothing -> No Unknown Device -> No Bossa-Port -> No Windows error
• Erased the firmware several times via the Erase-Pins -> no Change, no Device in Windows

Hello,

I have a Duet2 Wifi in revision 1.04c which was purchased in mid-2020 and a Duex2.

It runs an IDEX system, which worked great until yesterday.

so what has changed?

I have connected a LIS3DH which also worked and provided measurement results.
At least exactly 1 time. Here u can see i got some results

I wanted to repeat the same macro for the test drive, which was carried out, but in the csv file had said that the LIS3DH has brought no results.

Then I checked if the cables were still tight, which they were.
Again I repeated the test without a result but the chip was supplied normally over 3.3V.

Suddenly strange noises came from the printer, where from I could not locate, I can not really describe it, it sounded like when a coil charges up and then suddenly goes out.
From that moment the whole board was dead.

The problem I have now is that since yesterday the board does nothing. I have removed it and connected it via USB.

The 5V+ LED is permanently red as well as the LED between USB and reset button.
the 3.3V is not lit and there are no 3.3V present.

I noticed that the chip U2 gets extremely hot.
See Picture from the Board connectet with USB

How can I find out where exactly the cause of the problem is?

If the Duet2 Wifi is dead and I buy a new one, I would like to make sure that the cause is not on the Duex2, so that when I connect it, I also kill the new Duet2.

best regards
Julian