Should I update my Rostock Max 3.2+ to latest RRF3.4?

Stough · 18 Mar 2022, 23:40

I have an original Rostock V3 that I've upgraded a number of times. It is now running a Duet 2 WiFi/Ethernet with a Duet Smart Effector with ED3 hot end. It is working quite well, but I'm always looking to improve things.

Here's what I'm running according to M115:
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.0(RTOS) ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2018-06-05b3

So, should I update my firmware? It looks quite involved. I had been hoping to find a config.g file or config tool.json file as a basis to start my config from but have had very little luck. I've been perplexed in some of the config questions; for example, my thermistor settings for my ED3 don't seem to match the canned ones for ED3 in the config tool.

Thoughts?

What I'd love is for a RRF3.x expert to help me convert my RRF2 config.g. So I'll attach it for reference.

Cheers,
Tim

M550 P"RostockMax V3.2+"                   ; Printer name
M929 P"eventlog.txt" S1                    ; start logging to file eventlog.txt
M555 P2                                    ; Gcode Output Type
M552 S1                                    ; Enable Wifi
M575 P1 B57600 S1                          ; PanelDue Comm Setup
G21                                        ; Work in millimetres
G90                                        ; Send absolute coordinates

; Setup Drive Directions (X,Y,Z,E0,E1)
M569 P0 S0                                 ; Drive 0 goes forwards (X)
M569 P1 S0                                 ; Drive 1 goes forwards (Y)
M569 P2 S0                                 ; Drive 2 goes forwards (Z)
M569 P3 S0                                 ; Drive 3 goes forwards (E0)
M569 P4 S1                                 ; Drive 4 goes backwards(E1)

; Configure Endstops
M574 X2 Y2 Z2 S1                           ; set endstop configuration (all endstops at high end, active high)

; Configure Filament Out Sensor (one input for both E0 and E1)
M591 D0 P2 C3 S1                           ; Sensor for Drive 0 on E0, enable
M591 D1 P2 C3 S1                           ; Sensor for Drive 1 on E0, enable

M665 R144 L291.06 B135 H360 X0 Y0 Z0       ; delta radius, diagonal rod length, printable radius and homed height
                                           ; Y X Z are tower angle offsets
M666 X0 Y0 Z0                              ; endstop offsets in mm

M350 X16 Y16 Z16 E16:16 I1                 ; Set 16x microstepping w/ Interpolation
M92 X160 Y160 Z160                         ; Set axis steps/mm (orig: M92 X200 Y200 Z200)                       
M92 E508.180:508.180                       ; Set extruder steps/mm (orig: M92 E182.0:182.0)

M906 X1200 Y1200 Z1200 E1200:1200 I50      ; Set motor currents (mA) and idle current %
M201 X4200 Y4200 Z4200 E2000               ; Accelerations (mm/s^2) (orig: M201 X4200 Y4200 Z4200 E5000)
M203 X18000 Y18000 Z18000 E6000            ; Maximum speeds (mm/min) (orig: E18000)
M566 X2000 Y2000 Z2000 E900                ; Maximum instant speed changes mm/minute (orig: E2000)

M106 P0 H-1                                ; Part Cooling Fan
M106 P1 S1.0 H-1                           ; Case fan
M106 P2 T50 S1.0 H1                        ; Heat sink fan

M307 H0 B0                                 ; Heated Bed (H2)
M305 P0 T100000 B4388 R4700 H30 L0         ; Bed thermistor

M305 P1 T100000 B4388 R4700 H30 L0         ; Hot end Thermistor
M563 P0 D0 H1                              ; Hot end (T0), drive (E0), heater (H1)
G10 P0 S0 R0                               ; Hot end operating and standby temperatures

;Dual Extrusion Code 
M563 P1 D1 H1                              ; Hot end (T1), drive (E1), heater (H1)
G10 P1 S0 R0                               ; Hot end (1) operating and standby temperatures


; Z-Probe Config                           ; Sensitivity M672 S105:50:205 (aaa:255-aaa, default: 50)
M558 P5 I0 A2 S0.05 R0.4 H20 F1200         ; Strain gauge probe settings (orig: M558 P5 I0 A2 S0.05 R0.4 H20 F2500)
G31 P100 X0 Y0 Z-0.3                       ; Probe trigger and offset values (orig: G31 P100 X0 Y0 Z-0.3, v2: Z-0.15; Z0.4)
M557 R130 S30                              ; defualt bed mapping, radius = 135mm (140mm), spacing = 30mm

; Bed Correction
M376 H7					   ; Distance in mm to taper out correction. Set to ceil(20 * max(abs(bed_correction_dev))

; Final Setup
M501                                       ; Load saved config values
T0                                         ; Select Tool 0
M375                                       ; Load height map
M80                                        ; Make sure power is on

bot · 6 Apr 2022, 01:12

I think you should do three things:

update to firmware 2.05.1. It's the latest RRF2. You might have to make a change to your PID I parameter -- maybe double it or halve it. Check the old release notes. You should be able to dig it up, everything has been well documented but there has been lots of progress since then.
After you update to 2.05.1, figure out the new congfig for RRF3. It shouldn't be too complicated. Maybe use the configurator tool, or start from a known good rostock max config.
Once you have what seems like a safe config.g to use, find what used to be called "fallback procedure #2" (IIRC) in the documentation. It is a set of instructions for erasing the firmware on your board with the erase jumper (or button, if your board is old enough) and then just flashing the latest 3.4 firmware onto it. Make sure you update a Wifi server firmware as well (it might be bundled with 3.4 stable, but was not bundled with 3.4 rc2 when I last did this).

IMO, it will be easier to just flash the firmware with bossac once, rather than going through the stages of uploading different firmware versions to the web interface. But, maybe it's not so bad either way.

Phaedrux · 21 Mar 2022, 03:52

If you still have access to DWC. Upload these 3 zip files, one at a time in the system tab. Don't extract them first. Reboot after each. Use M115 in the gcode console to verify the firmware has been applied.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.0/Duet2and3Firmware-3.4.0.zip
That will get your firmware and DWC up to date.

You can see the change logs here:
https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x

For your config, might be a good idea to run through the configurator tool and generate a fresh set for RRF3.
https://configtool.reprapfirmware.org/Start

Backup your existing config files in the sys folder in case you want to switch back to RRF2. It’s easy to switch back and forth, just upload the zip file for the version you want and then upload your config files.

These documents will come in handy during the conversion.
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview
https://docs.duet3d.com/en/User_manual/RepRapFirmware/Migration_RRF2_to_RRF3
https://docs.duet3d.com/en/User_manual/Reference/Gcodes

Baenwort · 3 Apr 2022, 15:31

If you want to have a example the SeeMeCNC provided version is running 3.2.2 and that should get you a configuration that is good upto firmware 3.3 firmware.

https://forum.seemecnc.com/forum/viewtopic.php?p=111255

For 3.4 there are some more changes needed. I'm using the SE300 hotend setup so I'm not positive on which changes you may need for your modified configuration.

Stough · 3 Apr 2022, 15:31

Thanks to you all for the good information and suggestions.

I haven't done the conversion yet, but I'm torn between Phaedrux and following the SeeMeCNC "official" path from the forums. In any case, I'm going to get back into printing for a couple of months so I can relearn what I've forgotten. If I need to make a fresh config, I'll need to refresh my memory of exactly how my machine differs from the SeeMeCNC v3.2. I really should have kept a better lab notebook.

Thanks again and I'll report back here once I attempt the update.

Cheers,
Tim

elvisprestley · 6 Apr 2022, 01:09

@stough buyer beware
I upgraded my original Rostock V3 to the new RR V3.3 and I have never been able to downgrade again. They changed the folder structure that the Duet uses to look for files. Once you change, I can't figure out how to go back. I wipe and format the SD card, and still the older software "knows" that the file folder structure has changed and it goes looking for things in all the wrong places. Even if you try to fool the older version it doesn't fall for it.

I'd recommend sticking with V2.2 as supported by SeeMe CNC. Steve knows his stuff.
Running V3.3, I have unresolved heater fan issues, and am dead in the water as a result.

Good luck!

elvisprestley · 6 Apr 2022, 01:12

@bot Can you please tell me more about "fallback procedure #2" (IIRC) in the documentation. It is a set of instructions for erasing the firmware on your board with the erase jumper

where do I find these instructions?

bot · 6 Apr 2022, 04:11

@elvisprestley https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_firmware#fallback-procedure-2

dc42 · 6 Apr 2022, 10:15

@elvisprestley to revert frmware 3.3 to an earlier version it should only be necessary to upload the IAP file on the System page of DWC, then upload the earlier firmware binary.