Doubt due to passage from 2.05.1 to 3.1.1



  • Hello guys,
    I have a Duet2 wifi with 2.05.1 firmware on a corexy with a 3 motor system for leveling the bed. I would like to understand if there are any advantages (precision, print quality, etc.) using firmware version 3 (today 3.1.1) instead of 2.05.1.

    Many thanks for the reply
    Luc


  • Moderator

    @luc The only reason to move to RRF 3 is if you want to use the extra features. For precision and print quality, I don't think there's any real difference. If you have a dialled in, working printer, and don't need the configuration flexibility RRF 3 offers, it's unnecessary to upgrade. For differences, see https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Overview

    However, official development on RRF 2 has finished and RRF 3 is now the focus, but there may still be maintenance releases to resolve bugs. RRF 2 may still see community development; it is open source (as is RRF3).

    Ian



  • @droftarts First of all thanks for your answer.
    For the features I currently use today 2.05.1 is sufficient but I would like to upgrade to 3.XX. I had some fun simulating the configuration for 3.1.1 using the online configurator and manually modifying / adding parameters. If I attach the config.g of version 2 (working) and version 3 (simulated) do you have time to give me your opinion on any errors?

    (I wish that by installing V3 everything already works)


  • Moderator

    If you have a working RRF2 config already it should be easy to transfer the information to the web configurator and then compare to the RRF3 output.

    Feel free to post post here for a sanity check.

    When you do actually update, ensure that you install 3.0 first, and then 3.1.1. as there are some files in 3.0 required for 3.1.1 to flash properly. Uploading the entire firmware release zip file as is to the /sys folder in DWC is the prefered way to update.



  • Thanks again for your availability.
    Yes, reading I understood that:

    • For duet2wifi I have to install V3.0.0 first and then 3.1.1;
    • For paneldue I installed 1.23.2 and I'm not sure if I necessarily have to install 1.24. Do I need to update? ;

    For the conversion of config.g

    • This is the configuration of the working V2: config V2.g

    • This is a draft of the V3 configuration that I am preparing and on which I ask you for help for verification: config V3.g

    Note: I use 3 Z motors: 1 connected directly to duet2 and 2 motors connected to duex2

    Will I need to make any changes to the homex, homey, homez, homeall, bed .... files?


  • Moderator

    @luc said in Doubt due to passage from 2.05.1 to 3.1.1:

    Note: I use 3 Z motors: 1 connected directly to duet2 and 2 motors connected to duex2

    You may want to move all Z motors to the same board, I don't think it's a requirement, but I would consider it best practice. The extruder would then move to the duex.

    The configurator tool will only show basic axis/motor configuration options. YOu'll need to manually edit the M584 command to add the additional drivers for Z.

    @luc said in Doubt due to passage from 2.05.1 to 3.1.1:

    Will I need to make any changes to the homex, homey, homez, homeall, bed .... files?

    Most likely yes. The configurator will generate new RRF3 compatible files as well. The biggest change would be the homing move parameter has changed from G1 S1 to G1 H1. (due to S being used for laser power when in laser mode)

    Remove the M587 from your config.g it should not be executed at every startup. In more modern firmware versions it's even ignored in order to prevent unnecessary wear to the wifi module. You only need to add the SSID once anyway.

    You'll need to manually add the temp limit for the hotend. There is a bug in the configurator that prevents it from being added.
    M143 H1 S280 ; Set temperature limit for heater 1 to 280C

    You'll also need to manually transfer your custom settings

    ; CPU temp calibration
    M912 P0 S-4.7			                  ; MCU temperature sensor calibration offset (M112 to view current temp. Should match room temp.)
    
    ; Custom settings are not configured
    M572 D0 S0.035                            ; Pressure Advance set K-factor
    
    ; DAA Dinamic acceleration
    M593 F47.3 
    

    And you should add a T0 to the end of config.g to select your first tool at startup.


  • Moderator

    @luc you can also use M505 to switch between configurations easily. I was regularly switching between RRF2 and 3 for testing, though it’s less frequent now as more people switch to RRF 3.x. See my post here: https://forum.duet3d.com/post/125839

    Ian



  • ok .... according to your suggestions I have better checked the draft of the config.g for V3. I also followed the page: https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Summary_of_what_you_need_to_do_to_convert_your_configuration_and_other_files

    This would be a new version: config V3.g

    I would like your opinion on the following points:

    • M584: is it correct on two lines as I wrote or does it all go on one line (M584 X0 Y1 Z2:5:6 E3)?

    • Zprobe section: bltouch use connected to duex2 on pvm1. I'm not sure about the MM950 S0 C"duex.pwm1" and M558 configuration

    • Bed and Hotend heaters: are they ok?

    • Fans: I only have two simple fans. One always on which cools the hotend body and the other for cooling the piece being printed. Is the configuration correct?

    • "And you should add a T0 to the end of config.g to select your first tool at startup." In the RR2 I use T1. Should I change to T0?

    Sorry for too many questions πŸ™„ Any other suggestions are welcome 😘


  • Moderator

    Having M584 on two lines is fine. What I would change, as I said before, would be having all the Z axis motors on the mainboard and the extruders on the duex.
    M584 X0 Y1 Z2:3:4 E5:6

    duex.pwm1 looks ok for the BLtouch. Will need to test first obviously.

    heater and thermistors look ok if you have NTC3950 100K thermistors. Be sure to do a PID tune for the heaters.

    Fan block was correct before, but now they are both set to thermostatic control. The part cooling fan should have H-1 and no T parameter to disable thermostatic.

    Tools start with T0, you only have one tool so T0 is your first tool, you have no T1.



  • @Phaedrux said in Doubt due to passage from 2.05.1 to 3.1.1:

    .....What I would change, as I said before, would be having all the Z axis motors on the mainboard and the extruders on the duex.
    M584 X0 Y1 Z2:3:4 E5:6

    OK...now I got it. I thought you thought I had duex5 and you wanted to tell me to place the 3 Z motors in the duex. I will follow your advice.

    duex.pwm1 looks ok for the BLtouch. Will need to test first obviously.

    ok, of course.

    heater and thermistors look ok if you have NTC3950 100K thermistors. Be sure to do a PID tune for the heaters.

    Yeah ... I have these right now. I will definitely do the PID related to hotend and bed.

    Fan block was correct before, but now they are both set to thermostatic control. The part cooling fan should have H-1 and no T parameter to disable thermostatic.

    Thanks .... I correct (M106 P0 S0 H-1 / M106 P1 S1 H-1)

    Tools start with T0, you only have one tool so T0 is your first tool, you have no T1.

    I seem to remember that I had a problem with the display in the paneldue 5i and had to put T1 in the RR2 as something was not showing but I'm not sure about that.

    Please allow me another question:

    • For paneldue: I installed firmware 1.23.2 and I'm not sure if I necessarily have to install 1.24. Do I need to update?

    Many thanks for your availability .... I don't know if it will happen (I'm in Italy) but you have two paid beers !!!😁


  • administrators

    @luc said in Doubt due to passage from 2.05.1 to 3.1.1:

    For paneldue: I installed firmware 1.23.2 and I'm not sure if I necessarily have to install 1.24. Do I need to update?

    AFAIR, 1.23.2 will is OK with RRF 3.1.1 on a Duet 2. Version 1.24 is necessary on Duet 3 systems with both a PanelDue and an attached single board computer.


  • Moderator

    @luc said in Doubt due to passage from 2.05.1 to 3.1.1:

    M106 P1 S1 H-1

    The hotend fan would stay as you have it fr thermostatic control. M106 P1 S1 H1 T45.



  • @dc42 said in Doubt due to passage from 2.05.1 to 3.1.1:

    @luc said in Doubt due to passage from 2.05.1 to 3.1.1:

    For paneldue: I installed firmware 1.23.2 and I'm not sure if I necessarily have to install 1.24. Do I need to update?

    AFAIR, 1.23.2 will is OK with RRF 3.1.1 on a Duet 2. Version 1.24 is necessary on Duet 3 systems with both a PanelDue and an attached single board computer.

    Thank you very much



  • @Phaedrux said in Doubt due to passage from 2.05.1 to 3.1.1:

    @luc said in Doubt due to passage from 2.05.1 to 3.1.1:

    M106 P1 S1 H-1

    The hotend fan would stay as you have it fr thermostatic control. M106 P1 S1 H1 T45.

    Thank you very much



  • @Phaedrux said in Doubt due to passage from 2.05.1 to 3.1.1:

    Having M584 on two lines is fine. What I would change, as I said before, would be having all the Z axis motors on the mainboard and the extruders on the duex.
    M584 X0 Y1 Z2:3:4 E5:6

    Please @Phaedrux , tell me if the shift from E0 from duet2 (E3) to duex (E5) is correct:

    On duet2
    Hotend:
    M308 S1 P "e0temp" Y "thermistor" T100000 B3950
    M950 H1 C "e0heat" T1
    M307 H1 B0 S1.00
    M143 H1 S280

    Fan cools print:
    M950 F0 C "fan0" Q500
    M106 P0 S0 H-1

    On duex2
    Hotend:
    M308 S1 P "exp.heater3" Y "thermistor" T100000 B3950
    M950 H1 C "e0heat" T1
    M307 H1 B0 S1.00
    M143 H1 S280

    Fan cools print:
    M950 S0 C "duex.fan3"
    M106 P0 S0 H-1

    Okay or did I miss something on the way? 😳
    Thanks again.


  • Moderator

    @luc said in Doubt due to passage from 2.05.1 to 3.1.1:

    Okay or did I miss something on the way?

    You did not need to move the heaters or thermistors at all. Just the motor connections move from duet to duex and use the M584 command I showed above. That's all.



  • @Phaedrux Ok, I get it, just motors. But to learn the command syntax for duex is it correct as I wrote above? How was I supposed to write?


  • Moderator

    Yes that looks correct. The easiest way to check would be to use the configurator to setup a duex and see what it generates.



  • The initial (basic) configuration with the configurator (excluding duex) was very useful for me but I find it much better to use the Gcode guide to make additions and / or changes. It is also easy.
    Only the references to the duex seem to me (for my way of doing but maybe I'm wrong) a bit limited. I have yet to understand its logic.


  • Moderator

    Well the only thing that's really different for the Duex is the pin names. You can see a list of all pin names here: https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Pin_names_for_Duet_2_WiFi_Ethernet

    and when combined with the wiring diagram, it should be fairly simple.

    https://duet3d.dozuki.com/Wiki/Duex_wiring_diagrams
    https://duet3d.dozuki.com/Wiki/Duex2_and_Duex5_Features



  • @Phaedrux Hi, I loaded 3.1.1 and then the new config, home, etc ...... everything worked right at the first try! This is a satisfaction both for me and for you who have patiently supported me. Thank you again!

    The PIDs remain to do and move the 3 Z motors but I will do it later when I have some free time.

    In the meantime I ask what "Mode: FFF" means in DWC (top right)
    Mode FFF.JPG
    I don't know if it was there before but I hadn't noticed.


  • Moderator

    FFF = fused filament fabrication, AKA filament 3D printing mode.


  • administrators

    @luc, if you still have your config file (or config-override.g file if you were using it) from RRF2, then you can use the M307 parameters from that, instead of doing a new PID tune.



  • Unfortunately I agree that I have the following errors:

    5/10/2020, 08:48:48 M98 Pconfig.g
    HTTP is enabled on port 80
    FTP is enabled on port 21
    TELNET is disabled
    Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
    Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 790C
    Error: Heater 2 not found
    Error: Heater 4 not found
    Error: Heater 5 not found
    Error: Heater 6 not found

    On Heater 0 and 1 I think I understand what it is (maybe even PID to be redone) but for Heater 2-4-5 and 6 what should I check?



  • ok ... i solved. It was because of the config.override. I sent an M500, the file updated and the "Heaters x not found" errors disappeared. It remains the "warnig Heater 1 but I should resolve with a new pid.


Log in to reply