Oops, sorry for that.

This is a bug in 3.01beta2. It is fixed in the internal builds at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0.

Oh, @chrishamm This looks like a DSF issue. If I run M0 H1 from the Duet USB Serial port, it runs cancel.g. I'll open an issue on gitgub.

Nevermind, I found the issue in the release notes.

Duet 3 users: there is no longer a default bed heater. To use Heater 0 as the bed heater, put M140 H0 in config.g (later in config.g than your M950 H0 command).

@Danal said in RRF3, find where a pin is used.:

Still curious if there is a way to "dump all pins" or similar.

Currently the pin table records what mode each pin is used in but not which device is using it.

To avoid confusion with variable assignement, but I just saw in the documentation than you will use 'set' for that purpose. Good to have both notations.

Oh one of the most critical things is for @dc42 and @chrishamm to get the PID parameters sorted. Right now issuing an M500 overwrites an existing config-override.g with...

; config-override.g file generated in response to M500 at 2020-01-14 11:04 ; Heater model parameters M307 H0 A C D S V B0 M307 H1 A C D S V B0 ; Workplace coordinates

@dc42 said in Tool Change: Moving in axis without calling them:

@smoki3, I have fixed this in the 3.0 stable release.

I am not planning to do any further 2.x releases, but you have an easy workaround (M400 at the start of the tpre and/or tpost file).

I see. Its working fine now.

For 2.x I don't use it. I just thought about all the tool changer users....

@too, please test again with release 3.0 stable.

Thanks, i will try that later and report back if it worked @Danal

There seems to be an issue with changing (increasing) the hot end temperature during print. Doing so causes a heater fault and a stopped print.

I have not experienced this in previous versions.

Board: Duet 0.85
Firmware: RepRapFirmware for Duet 1.26 (2019-12-13b1)

@bearer said in M300 S and P swapped as played back in RFF3 and/or DWC2 DSF:

Out of interest where would I be able to find that information myself?

https://github.com/dc42/RepRapFirmware/blob/v3-dev/src/Duet3_V05/Pins_Duet3_V05.h#L222

for future reference ☝ 👇

https://github.com/dc42/RepRapFirmware/blob/v3-dev/src/Duet3_V06/Pins_Duet3_V06.h#L230

Just for the sake of completeness: there does not yet exist an official python library to the DuetAPI (but it is on the roadmap - next I think). There exists of course the C#.NET library that e.g. CodeConsole is built upon as well as my Go library (https://github.com/wilriker/goduetapiclient).

And this wraps up that there is no current (full) client library for any scripting language. Thus great job at getting started @Danal! 👍

@chrishamm Tested here - looks good - thanks

@Veti said in Duet 3 Heated Bed Faulting:

you can not. that is just a warning.

I thought that might be the case, no worries.

Please provide your stop.g and cancel.g files.