DSF 1.3.2 (unstable) released


  • administrators

    I'm happy to announce the release of DSF 1.3.2 for testers. It is now available on the unstable Duet3D package feed. For a list of changes, see https://github.com/chrishamm/DuetSoftwareFramework/releases/tag/1.3.2

    At this point many thanks again to @gtj0 for his extensive testing before this release was officially published.

    If you want to give this release a try and you were not on DSF 1.3.1 before, have a look at this article. Again, please be aware that this build contains lots of changes since DSF 1.2.x and some things may not work as expected. That being said, here some notes:

    • If you see messages like "DCS is shutting down" or "DCS is stopped" this means that DuetControlServer, the main application doing G-code coordination and file management, is no longer running. To figure out why it isn't, connect to your Raspberry Pi using SSH or open a terminal and run sudo journalctl -u duetcontrolserver -en 100 --no-pager and post the output here
    • If some parts of the web interface do not seem to be regularly updated, it indicates that there is an incompatibility between RRF's and DSF's internal object model. Likewise, connect to your board or open a terminal, run sudo journalctl -u duetcontrolserver -f and look for error messages
    • If this does not reveal any error messages or if anything gets stuck, please open a terminal and send sudo systemctl stop duetcontrolserver followed by sudo /opt/dsf/bin/DuetControlServer -l debug. This will generate extra debug messages that may show what is going on. Please note that you must not close the terminal as long as you are printing, else the print job will fail.

    If you get any error messages, please share them here and I will fix them in the next build.



  • @chrishamm said in DSF 1.3.2 (unstable) released:

    If this does not reveal any error messages or if anything gets stuck, please open a terminal and send sudo systemctl stop duetcontrolserver followed by sudo /opt/dsf/bin/DuetControlServer -l debug. This will generate extra debug messages that may show what is going on. Please note that you must not close the terminal as long as you are printing, else the print job will fail.

    if running over ssh this is especially important; a network glitch will terminate the session and its running processes.

    use screen or nohup to work around this.



  • FYI...The two pause/resume issues I reported on Github are still issues.


Log in to reply