RepRapFirmware 3.0 is released!

matej1006

@dc42 i figurit out for homing u axe i stiil have problem with showing temp on graph and extra temp for water and MCU temp

wilriker

@matej1006 If a sensor is not bound to a heater it needs to be given a name to show up in the UI. That's done with the A parameter for M308.

garyd9

@garyd9 said in RepRapFirmware 3.0 is released!:

Duet2 wifi h/w version 1.04
Printer is a normal delta (with 0.9 degree steppers)
Firmware is the first general release of RRF3

After starting my first print with RRF3 on a Duet2 WiFi, I'm seeing a LOT of hiccups using an identical configuration to what I used with RRF2 (where I only rarely saw a hiccup.)

A follow up on this: I wanted to test things in a controlled environment without a print going. So, with no heaters/fans/extrusion going on, I performed the following commands (while in absolute positioning mode):

G1 X0 Y-50 Z50
M122 // just to clear the hiccup count
M122 // just to make sure the hiccups were really at 0
G1 Y+50 F12000
M122

The second M122 showed 188 hiccups.

Is this normal for 0.9 degree steppers, 16 microsteps, and movements of only 100mm across the center of the bed at only 200mm/sec?

Same test, but with a F param of 10000 showed 20 hiccups. Slowing it down to 9000mm/min showed 2 hiccups.

(I didn't see these kinds of hiccups with RRF2 on the same config with moves this slow.)

@dc42? Is RRF3 ready for Duet2 boards controlling deltas?

dc42

@garyd, I'll do some tests on maximum step rates in RRF3. I noticed that on my delta, I had to reduce the max speed to 200mm/sec when it was previously higher.

Hornetrider

@dc42
Updated done for DUET3 Standalone from 3.0RC2 to 3.0 without trouble.
Now going to do some prints to see if everything runs...

Great Job!

appjaws

@dc42 said in RepRapFirmware 3.0 is released!:

M98 P"config.g"

thanks dc42,
I am almost there now but I think you should know that the gcode documentation under M950 has a note "M950 needs to be before M106, M308 etc in config.g file"

appjaws

Nearly there.
My bed isn't heating up at all

RRF 2 old -- worked
M307 H0 A104.6 C986.0 D1.9 ;B0 ; Auto tune PID for bed heater
M305 P0 R4700 B3950 S"Bed Heater" ; bed thermistor R and B values

RRF 3 new -- not working
; Thermistors and heaters
M308 S0 P"bed_temp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bed_heat" T0 ; create bed heater output on bedheat and map it to sensor 0
M143 H0 S70 ; set temperature limit for heater 0 to 70C
M307 H0 A104.6 C986.0 D1.9 B0 S1.00 ; Auto tune PID for bed heater

Thanks for any help

Dougal1957

@appjaws this is how my Heater section is configured on my delta with a Duet2 WiFi only difference is that I Use PT100's for my temp sensors so you will have to allow for that hop it helps.

; Heaters
M143 S300 ; Set maximum heater temperature to 300C
;M305 P0 X201 ; Set thermistor + ADC parameters for heater 0 and remap it to channel 201
;M305 P1 X200 ; Set thermistor + ADC parameters for heater 1 and remap it to channel 200
M308 S0 P"spi.cs2" Y"rtd-max31865" F50
M308 S1 P"spi.cs1" Y"rtd-max31865" F50
M950 H0 C"bed_heat" T0
M950 H1 C"e0_heat" T1
;M307 H0 A199.0 C962.6 D5 B0
;M307 H1 A409.7 C232.2 D4.5 B0
;M307 H0 A161.6 C1109.8 D5.8 S1.00 V24.4 B0
M307 H0 A449.1 C783.3 D9.8 S1.00 V24.4 B0
M307 H1 A544.9 C280.1 D4.2 S1.00 V24.4 B0

Can't see anything wrong in yours mind may be worth just double checking that the Zero's are Zero and not O

Doug

Hornetrider

I found something odd, or it is just to late at night.

This is my heater and fan definition:
M308 S3 Y"mcu-temp" A"MCUTemp" ; configure sensor 3 as MCU Temperature
M308 S4 Y"drivers" A"DriverTemp" ; configure sensor 4 as Dirver Temperature

; Fans
M950 F1 C"out8" Q500 ; create fan 0 on pin out7 and set its frequency
M106 P1 S1 H1 T45 C"Tool Fan" ; set fan 0 value. Thermostatic control is turned on
M950 F0 C"out7" Q500 ; create fan 1 on pin out8 and set its frequency
M106 P0 S0 H-1 C"Part Fan" ; set fan 1 value. Thermostatic control is turned off
M950 F2 C"!out4" ; create fan 2 on pin out4 and set its frequency
M106 P2 H3:H4 T48:60 C"MCU FAN" ; set fan 2 value. Thermostatic control is turned on

I have noticed that in this config the bedtemp drives the MCU fan....like the "drivers" is using the bed temp...and not the drivers temp.
Can somebody please check?

Am I missing something?

Btw. how do I activate the tacho and get and on DWC?

I have a DUET3 6HC with RRF3.0 in use

dc42

To use a 4-wire fan including the tacho, create the fan like this:

M950 F2 C"!out4+out4.tach" Q25000

Check your config by running M98 P"config.g" to see if there are any error messages. You can also send M308 S2, M308 S3 and M106 P2 to check that the settings for the electronics cooling fan and associated sensors are correct.

Hornetrider

@dc42
thx for reacting so fast.
I will check on your input.

Before my last post I run the following check...

Considering that for basic setup:
M950 F2 C"!out4" -> works
M106 P2 H3:H4 T48:60 C"MCU FAN" -> shows strange behaviour as "drivers" is influenced by "bedtemp"

I checked this by changing M106 to:
M106 P2 H4 T48:60 C"MCU FAN"

While MCUTemp stayed at ~40°C I run the bed heating to 50°C and at 48°C the fan started running....
Then I made a recheck for only "mcutemp" like:
M106 P2 H3 T38:60 C"MCU FAN"

And everything worked as supposed: as MCUtemp came below 38°C the fan turned of.

Any clues?

dc42

What temperature does Driver Temp show in DWC while you heat the bed?

Hornetrider

@dc42
0.0°C

dc42

@Hornetrider said in RepRapFirmware 3.0 is released!:

M106 P2 H3:H4 T48:60 C"MCU FAN"

I've just spotted the problem. You are using:

M106 P2 H3:H4 T48:60 C"MCU FAN"

but it should be:

M106 P2 H3:4 T48:60 C"MCU FAN"

Sending M106 P2 would have revealed that it was monitoring sensors 0 and 3.

Hornetrider

@dc42
thx!
I'll give it a try later today and get back to you.

Hornetrider

@dc42
now everything is like it should be... thx a lot!

4lathe

I have several duet 2 wifi’s on deltas and a railcore Zl and have converted the deltas to rrf3. I decided to put a maestro on a Frankenstein Ender 3 Pro that had a bltouch and v6 on it ( I first tested it with a spare duet wifi I had on hand using 2.05 and that worked perfectly). So I installed the maestro and tested using 2.05. No problems. I then upgraded to 3.0. All works perfectly except for deploy and retract probe. I added M950 S0 P”zprobe.mod” before my M558. I then changed the deployprobe.g and retractprobe.g to M280 P0 S10 and M280 P0 S90. When I went to homez, the probe didn't deploy. I tested issuing the commands in the console. Nothing. I searched here and saw that someone said they had to put the M950 command again just before the M280’s in deployprobe and retractprobe. I tried that and it works perfectly. There is no config-override file so nothing is undoing the original M950 in config.g. Any ideas on why this is happening? Thx for any help.

DIY-O-Sphere

That are the lines for my Maestro.
Already on RRF3.01b

M558 P9 C"zprobe.in" H5 F120 T3000
M950 S0 C"zprobe.mod"

dc42

@4lathe said in RepRapFirmware 3.0 is released!:

I have several duet 2 wifi’s on deltas and a railcore Zl and have converted the deltas to rrf3. I decided to put a maestro on a Frankenstein Ender 3 Pro that had a bltouch and v6 on it ( I first tested it with a spare duet wifi I had on hand using 2.05 and that worked perfectly). So I installed the maestro and tested using 2.05. No problems. I then upgraded to 3.0. All works perfectly except for deploy and retract probe. I added M950 S0 P”zprobe.mod” before my M558. I then changed the deployprobe.g and retractprobe.g to M280 P0 S10 and M280 P0 S90. When I went to homez, the probe didn't deploy. I tested issuing the commands in the console. Nothing. I searched here and saw that someone said they had to put the M950 command again just before the M280’s in deployprobe and retractprobe. I tried that and it works perfectly. There is no config-override file so nothing is undoing the original M950 in config.g. Any ideas on why this is happening? Thx for any help.

In 3.0 the Z probe defaults to using probe.in+zprobe.mod. You need to use
M558 to make the Z probe use just zprobe.in. Only then will zprobe.mod be free to use in M950.

4lathe

@dc42 here is my config.g
M950 S0 C”zprobe.mod”
M558 P9 C”zprobe.in” H4 F120 T2400 R0.5
So are you saying I must place the M950 after that M558?