PID settings.

Hello,

Can I put the M301 command with the PID settings in my config.h file ?

This would be after running M303 to obtain the correct P I and D values.

My printer is the Ormerod 2.

Many thanks,


Brian

Hi,

Yes you can put those statements within a config.h file

Here is a snippet from mine

M301 H1 P20 I0.5 D100				; Set PID Parameters
;M301 P9 I6 D50					; Set PID Parameters
;M301 I2.0						; Set PID Parameters 
;M301 P5.0						; Set PID Parameters
;M301 D50						; Set PID Parameters

The ones with a semicolon in front are not read, just there when I was testing each value, wasn't aware that you could run a M code before to obtain the correct values. As RRP firmware doesn't support auto-tune (M303) in the same way as Marlin firmware

Edited 1 time(s). Last edit at 05/06/2016 07:38AM by orictosh.

---

Supporting 3D Printers with Parts and Build services.
Printer: Ormerod 2 (528.4) Duel extruder set-up with Aluminium X-Rib, RRPro Firmware v1.11-ch (2016-04-08)

Hi Orictosh,

I had assumed I would be able to obtain the correct figures by sending M303 from Printrun.

How did you obtain P I D values without using M303 ?


Many thanks,


Brian

Quote
Europa
How did you obtain P I D values without using M303 ?
Brian

Trial and error. You are looking for rapid heating, minimal overshoot and stable temperature after it settles to its endpoint. You only need to do it once (unless you change your hotend or PSU voltage). Start with the default values.

Look under the "Manual Tuning" heading in this reference:- [en.wikipedia.org]

Dave

M303 is not implemented in RepRap Firmware

Have a look on the page 'RepRap Firmware Heating': [reprap.org]

---

Pierre

- Safety [reprap.org]
- Embedded help system for Duet and RepRap Firmware [forums.reprap.org]
- Enclosed delta printers Lily [rouzeau.net] and Lily Big [rouzeau.net]
- OpenScad delta printer simulator [github.com]
- 3D printing on my site [www.rouzeau.net]

Ok Dave,
I will give it a go.

It is a new E3D V6 hotend from E3D online that I have just fitted.

Many thanks,


Brian