Posts made by sinnedwrong

@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

@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

@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?

@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

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

@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.**

@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?

@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

@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)

@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?

Good spot, haven't had to CTRL F5 for a long time, now works correctly. Thanks

Unfortunately the URL I have for the configuration tool, given in my first post, comes up with version 3.2.0. Is there a different URL to access the latest version?

I'm attempting to put a second hot end onto an Ormerod 2 and used the reprapfirmware configuration tool https://configtool.reprapfirmware.org/Start however I must be doing something wrong. The original config.g supplied by when I bought the machine has:
M563 P0 D0 H1 ; Define tool 0
G10 P0 S-273 R-273 ; Set tool 0 operating and standby temperatures
;M563 P1 D1 H2 ; Define tool 1, uncomment if you have a dual colour upgrade
;G10 P1 X19 S-273 R-273 ; Set tool 1 operating and standby temperatures, uncomment if you have a dual colour upgrade

implying that the second nozzle is 19mm from the first. However using the configuration tool (Firmware for Duet 2 maestro 2.05.1) produces :

; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
M563 P1 D1 H2 F0 ; define tool 1
G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets
G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C

despite having entered 19 into the box on the XYZ Offset box and clicked apply the offset does not appear in the generated config.g file. Clearly I can edit the config.g file but am I missing something?

Doing the commissioning sequence from DC42 website but with a piece of white paper under the sensor and nozzle the Z axis reads 1.38 so within the range 0.5 to 2.5mm as required. I presume that even with the black paper under the glass there is not enough reflection from the klapton tape. Suggestions as I can't find a solution to this un the website. Thanks Dennis

The setup is as described on DC42 website

Glass (with or without coatings such as hairspray, PVA or Kapton tape): works as-is if placed directly on a PCB bed heater or other surface that does not reflect strongly. If there is an aluminium heat spreader or bed plate underneath the glass, then either paint the aluminium surface matt black (see below), or put a sheet of matt black paper between the glass and the aluminium. Coatings on the glass affect the trigger height slightly.

Dennis

Glass with Klapton tape on top and black paper under the glass which is supported on aluminum plate

What's a buildplate and how would I ascertain, purchased fromThink3DPrint3D in November 2018 Invoice #4873

As the title says following the instructions on DC42 website the probe goes from a reading of 468 to 540 (and red LED) but the reported Z height at triggering is negative not 0.5-2.0mm.
RepRapfirmware 2.05.1 Ormerod 2. Its raining here so no excessive radiation (IR, vis or UV!)
If I put the -0.62 value in config.g will it work otherwise what's going wrong?

Hi,

Having been appropriately admonished by Phaedrux for attempting to get a machine going using an old version of the firmware I thought I ought to update my maestro from 2.02RC3 to 2.05.1 which I found on the github page and downloaded(DuetFirmware-2.05.1). On unzipping I discovered the zip included .bin for Duet2, Duetmaestro and Duet wifi. I assume that install process knows which one to install.

My questions are in the readme on github it implies that all one needs to do is upload the zip file using the upload button and then let it do its business. This would appear to be at variance with https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware. Am I correct in the belief that the Github instructions are the most recent and correct?

I wasn't clear if the config.g file needed changing so I did a creation of .g files using the configuration tool and that generated an identical config.g file except for an additional line M584 X0 Y1 Z2 E3. While I can understand how that is constructed, and despite having read the g code wiki, why do I need this line?

If I'm not to be admonished again I will in the future need to look to version 3... Clearly there are massive changes to the g files and as far as I can see this wasn't available in the configuration tool. Is that correct?

Finally if I decide to get very brave is DuetWebControl-1.22.6 the correct firmware for a Duet 0.6?

Hi, Thanks all for the input. DCs answer has stopped me putting an M117 "Random message" into tpost0.g to see if it was run. I think this thread has just about run its course now. I'm presuming having read the wiki regarding T gcodes that there is a typo in DC42 last post and that it should read T-1 P0 followed by T0.

Thanks again for the input, will be starting a new post re upgrading firmware after more reading.

Dennis