• Tags
  • Documentation
  • Order
  • Register
  • Login
Duet3D Logo Duet3D
  • Tags
  • Documentation
  • Order
  • Register
  • Login
  1. Home
  2. sinnedwrong
  • Profile
  • Following 0
  • Followers 0
  • Topics 6
  • Posts 27
  • Best 1
  • Controversial 0
  • Groups 0

sinnedwrong

@sinnedwrong

1
Reputation
2
Profile views
27
Posts
0
Followers
0
Following
Joined 19 Nov 2018, 16:53 Last Online 24 Apr 2021, 13:48

sinnedwrong Unfollow Follow

Best posts made by sinnedwrong

  • RE: Duet not waiting for hot end to come to temperature

    Thank you all for replying and especially for making me reread the Wiki carefully. The phrase If Tn is used to select tool n but that tool is already active, the command does nothing. Otherwise, the sequence followed is... to me implies that it always calls tpost0.g but now I know!

    To answer specific questions no there isn't a T0 in config.g . As originally delivered by RepRapPro the T0 is put in by the custom Gcode in SlicR from the start GCODE section so I will add an M116 after that. Its interesting that the reprappro supplied SlicR start Gcode for the dual nozzle option doesn't include a T0 and T1. I can only presume that in version 1.09 there was an automatic wait which has gone in the intervening versions. I have looked at the versions in https://github.com/Duet3D/RepRapFirmware/blob/dev/WHATS_NEW.md but that only goes back to 1.12 and I can't see any mention of the change.

    There are 2 reasons why I'm building a second Ormerod, first after 20 years as Clinical Director of a large NHS Pathology service I don't tend to make major changes to software without a fallback machine. My plan is to upgrade my original machine once I have a working spare. I also plan to play with dual nozzle so an understanding of tool changes etc. becomes relevant. The reason I'm on 2.02 RC3 was that was the current firmware when my Maestro was delivered. I got sidetracked into AI resulting in me teaching myself Python, Tensorflow and Linux.

    My current plan is to is to put a M116 in the custom Gcode setting of Slicr after the T0 and when I move on to a second nozzle to also put in a T1 and M116. Looking at the gcode source of a 2 colour slicing that presumably will trigger the relevant tpostN.g macro each time as that will be a tool change.

    Its been interesting and thanks for your input.

    Dennis

    posted in Duet Hardware and wiring
    undefined
    sinnedwrong
    8 Dec 2020, 11:03

Latest posts made by sinnedwrong

  • RE: Upgrading Firmware from 2.02RC3 to 3.2

    @phaedrux Just a quick reply to thank everybody, the TOY is now working successfully on 3.2.

    A couple of points:
    I didn't find in the change log for version 3.2 that BANG-BANG wouldn't work only that there was a new heating algorithm.
    Removing the BANG-BANG option in the configuration tool might be a good idea to avoid confusion
    Also for completeness it might be a good idea to change the title of this thread by adding the phrase "to 3.2". I don't think I'm allowed to do this, I suspect an admin or moderator needs to do this.

    Thanks again for all the help

    Dennis

    posted in Firmware installation
    undefined
    sinnedwrong
    14 Apr 2021, 13:49
  • RE: Upgrading Firmware from 2.02RC3 to 3.2

    @dc42 Clearly more reading and research to do however the RRF config tool was what specified bang/bang and I went with the default recommendation. Clearly I will now have to read https://duet3d.dozuki.com/Wiki/Tuning_the_heater_temperature_control and discover how to use heater tuning. Out of interest what is Z banding and should the config tool be updated?

    Thanks

    posted in Firmware installation
    undefined
    sinnedwrong
    11 Apr 2021, 17:24
  • RE: Upgrading Firmware from 2.02RC3 to 3.2

    @phaedrux I finally got brave enough to attempt the firmware upgrade which was straightforward as I guess you are not surprised. I now have an issue in my config files. The bed which was working perfectly under 2.05 so isn't a wiring fault is coming up with the message "Heater fault rising more slowly than expected 1.8C/sec"
    Settings in the RRF config tool:
    tick for heated bed, bang bang,
    values 120, 100, 10000,3988, 0
    which are the defaults after specifying an Ormerod 2 in the initial screen. M115 gives Firmware 3.2.2 X&Y axes zero OK. That's as far as I've tested.
    Ideas?

    posted in Firmware installation
    undefined
    sinnedwrong
    11 Apr 2021, 12:47
  • RE: Duet Bootloader

    @dc42 Thanks for the prompt reply which has saved me discovering another distraction in lockdown of looking at the source code.
    A lifetime of experiencing major software upgrades in the NHS taught me the importance of a rollback option for when things don't go to plan. Looks like I will have to devise another strategy.
    Thanks for your help
    Dennis

    posted in General Discussion
    undefined
    sinnedwrong
    25 Mar 2021, 11:32
  • Duet Bootloader

    Most of the modern microcontrollers I have used (PIC, Arduino for example) are programmed by uploading the firmware to non volatile memory and on booting up the CPU loads the program from there.
    By contrast what I would call conventional computers (e.g. ICL 1903A, PDP11 or even an IBM PC with its BIOS) have a hardwired bootloader which on reset uploads the main program from some backing store.
    My suspicion is that the latter is the model used on the DUET and that the firmware is read from the SD card at bootup. In which case it should be possible to create an SD card backup then for example upgrade the firmware and have a backout option if the upgrade goes wrong by just changing to the copy of the original SD card. One could even have 3 SD cards and do a grandfather, father and son almost like old fashioned backup policies.
    Am I correct in these thoughts and if so are there any specifications for microSD cards, I see the one in my Maestro is a 4GB.
    Thanks
    Dennis

    posted in General Discussion
    undefined
    sinnedwrong
    25 Mar 2021, 09:13
  • RE: Upgrading Firmware from 2.02RC3 to 3.2

    @sinnedwrong and just discovered this which could be the problem as I hadn't done this. Could be tomorrows challenge EXCEPT how easy is it to go from 3.x back to 2.05?

    **Updating from RRF 2.x to 3.x
    Upgrading ANY Duet 2 from 2.x to 3.0 or later requires installing 3.0 first.

    The version 3.01 and later binaries are too large to be installed by the IAP program supported by version 1.x and 2.x firmware. Therefore you cannot upgrade directly from version 1.x or 2.x firmware to 3.01 or later firmware. This is the procedure:

    Download file Duet2and3Firmware-3.0.zip from https://github.com/Duet3D/RepRapFirmware...
    Upload and install that file on the Duet through Duet Web Control
    Send M115 and check the response to confirm that you are running version 3.0 firmware
    You can then upgrade to version 3.01 or later firmware.
    Important! When upgrading from 1.x or 2.x firmware to 3.x you will need to make substantial changes to your config.g file. See RepRapFirmware 3 overview.**

    posted in Firmware installation
    undefined
    sinnedwrong
    24 Mar 2021, 18:21
  • RE: Upgrading Firmware from 2.02RC3 to 3.2

    @sinnedwrong and to confirm
    M115
    FIRMWARE_NAME: RepRapFirmware for Duet 2 Maestro FIRMWARE_VERSION: 2.05.1 ELECTRONICS: Duet Maestro 1.0 FIRMWARE_DATE: 2020-02-09b1

    What's the way forward?

    posted in Firmware installation
    undefined
    sinnedwrong
    24 Mar 2021, 18:16
  • RE: Upgrading Firmware from 2.02RC3 to 3.2

    @dc42
    I have just recreated firmware and specificallty ensured in the config tool to select V3.0 or later.
    It provides in the zip file DuetMaestroFirmware.bin 470kb compressed size 470kb 5% ratio with a CRC 2144DF1C

    posted in Firmware installation
    undefined
    sinnedwrong
    24 Mar 2021, 18:06
  • RE: Upgrading Firmware from 2.02RC3 to 3.2

    @dc42
    response after uploading 3.2 and power cycling machine

    M98 P"config.g"
    HTTP is enabled on port 80
    FTP is disabled
    TELNET is disabled
    Warning: M308 command is not supported
    Warning: M950 command is not supported
    Warning: M308 command is not supported
    Warning: M950 command is not supported
    Warning: M950 command is not supported

    comments at start of config.g

    ; Configuration file for Duet Maestro (firmware version 3)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 23 2021 17:45:18 GMT+0000 (Greenwich Mean Time)

    posted in Firmware installation
    undefined
    sinnedwrong
    24 Mar 2021, 17:54
  • RE: Upgrading Firmware from 2.02RC3 to 3.2

    @sinnedwrong
    Wanting to avoid being admonished by Phaedrux again I have been attempting to convert my maestro/Ormerod 2 to firmware 3.2. Thhe machine is running succesfully on 2.5 but when I upload 3.2 the machine fails with the error below. Axes X,Y and Z all move and zero correctly. I havent tried heating up the hot end.

    Error. Temperature reading fault on heater 0 unknown temperature sensor channel

    subsequently the following message pops up:

    Reset Heater Fault
    A heater fault has occurred on heater 0. It is strongly advised to turn off your machine now and to check your wiring before you continue. If you are absolutely sure that this is not a physical problem, you can reset the heater fault ON YOUR OWN RISK. Be aware that this is NOT RECOMMENDED and can lead to further problems. How would you like to proceed?

    Reinstalling version 2.5 works normally, installing 3.2 the same error occurs rectified by going back again to 2.5.

    The relevent sections of config.g are:
    2.5
    ; Heaters
    M305 P0 T10000 B3988 R2200 ; set thermistor + ADC parameters for heater 0
    M143 H0 S120 ; set temperature limit for heater 0 to 120C
    M305 P1 T100000 B4138 R2200 ; set thermistor + ADC parameters for heater 1
    M143 H1 S280 ; set temperature limit for heater 1 to 280C

    3.2
    ; Heaters
    M308 S0 P"bedtemp" Y"thermistor" T10000 B3988 ; configure sensor 0 as thermistor on pin bedtemp
    M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
    M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
    M140 H0 ; map heated bed to heater 0
    M143 H0 S120 ; set temperature limit for heater 0 to 120C
    M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
    M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
    M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
    M143 H1 S280 ; set temperature limit for heater 1 to 280C

    The configuration files were created by the RRF Config Tool taking all of the default options for an Ormerod 2 (except for the X direction which should be backwards) What am I doing wrong?

    posted in Firmware installation
    undefined
    sinnedwrong
    24 Mar 2021, 16:20
Unless otherwise noted, all forum content is licensed under CC-BY-SA