New firmware 2.0RC5 available



  • @dc42 In that case the append is working as intended! Very useful with the network drops. There are issues I know I need to wirk on at som point for the latter.



  • If you choose "Change Filament" via DWC, this error occurs:
    Error: M701: Unload the current filament before you attempt to load another one
    Filament loading is then no longer possible via DWC.

    @dc42 said in New firmware 2.0RC5 available:

    Where are you running M502, and why?

    for example loading the filament, I set the acceleration smaller here.

    And I was hoping that I can do this with M502 resets without deposit anywhere fixed values.


  • administrators

    @zerspaner_gerd said in New firmware 2.0RC5 available:

    If you choose "Change Filament" via DWC, this error occurs:
    Error: M701: Unload the current filament before you attempt to load another one
    Filament loading is then no longer possible via DWC.

    Just to be clear: you are getting that error only if you run M502. Correct?

    When you create a tool (for example because you run M502, which will recreate all the tools), if the tool uses exactly one extruder, the code looks to see if there is already a filament assigned to that extruder, and if so then it flags the tool as using that filament. That appears to me to be sensible behaviour. If you disagree, please explain why.



  • @dc42 said in New firmware 2.0RC5 available:

    @bmmal said in New firmware 2.0RC5 available:

    I do have simple switch filament monitors. The machine disables/deconfigures the filament monitors at the start of each print to make sure there are not any from a previous print, see start.g.

    Thanks. I found a possible problem with configuring/deconfiguring filament monitors while a print is active. I believe I have fixed it. However, I advise against deleting filament monitors (or changing their type in other ways) once they have been configured. Instead, I suggest you use the M591 S parameter to enable or disable the filament monitor.

    Can you explain what problems you were getting before, i.e. what you mean by "to make sure there are not any from a previous print" ?

    @dc42 For some reason I didn't realize the S parameter enabled or disabled them. I'll switch things over. I was basically trying to disable them all at the beginning so that only the ones needed for a print would be enabled and I didn't have to have material loaded in an unused extruder.



  • I have strange heater erros with RC5. But I have brand new 24V heater unit so it could be that too. The heater is calibrated, and after the calibration it have had problems maintaining the temperature.

    But in any case these heater errors look strange, there might be some bug there. See that decreasing expected temperature raise limit after each fault.

    0_1527614037216_heater-error.png


  • administrators

    @bmmal said in New firmware 2.0RC5 available:

    @dc42 For some reason I didn't realize the S parameter enabled or disabled them. I'll switch things over. I was basically trying to disable them all at the beginning so that only the ones needed for a print would be enabled and I didn't have to have material loaded in an unused extruder.

    The S parameter wasn't supported on filament monitor types 0 and 1, but in 2.0RC6 it is.


  • administrators

    @nuffe said in New firmware 2.0RC5 available:

    I have strange heater erros with RC5. But I have brand new 24V heater unit so it could be that too. The heater is calibrated, and after the calibration it have had problems maintaining the temperature.

    That error message normally means that the heater hasn't been tuned. Did you save the calibration values from tuning:

    • Either by sending M500, if your config.g file is set up to invoke config-override.g using M501;
    • Or by editing the results of tuning into a M307 command in config.g and making sure there isn't another M307 command for that heater in config-override.g?

  • administrators

    I have just released firmware 2.0RC6 so I am closing this thread and starting a new one. Those of you who have outstanding issues with RC5, please test again using RC6 and report any issues that are still present in that thread.


Locked
 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.