RRF 3.01-RC10, DWC 2.1.5 and DSF 2.1.1 released

[A Former User]

https://forum.duet3d.com/topic/15848/dsf-2-1-1-hangs-on-apt-upgrade-with-no-duet-connected (sort of case closed)

[Silrocco]

Hello.

I'm getting an error when uploading the DuetMaestroFirmware.bin to a Maestro.

M997 S0
Error: M997: In-application programming binary "DuetMaestroIAP.bin" not found

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 Maestro FIRMWARE_VERSION: 3.01-RC8 ELECTRONICS: Duet Maestro 1.0 FIRMWARE_DATE: 2020-04-17b4

I can upload the Duet2CombinedFirmware successfully, NOT the DuetMaestroFirmware.

[chrishamm]

@Silrocco The file you are looking for (DuetMaestroIAP.bin) is available here: https://github.com/dc42/RepRapFirmware/releases/tag/3.0 Please upload that before you upload the firmware file.

[Silrocco]

@chrishamm

Thanks. I'm currently printing a part so when done I'll attempt uploading it.

[gloomyandy]

Hi,
is the github repo fully up to date? It is tagged as RC10, but the Version.h file claims to be RC9+1 (and this is the version reported by DWC when using an LPC build).

https://github.com/dc42/RepRapFirmware/blob/3.01-RC10/src/Version.h

Thanks!

[dc42]

I'm sorry, it looks like I may have failed to commit that file before I did the release. That was the very last change I made. All other changes were in previous commits.

[gloomyandy]

If that is the only file I wouldn't worry about it David.

[Silrocco]

@chrishamm

Uploading DuetMaestroAP.bin didn't work either, getting an infinite upload status for minutes that I have to cancel out.

[dc42]

@gloomyandy said in RRF 3.01-R10, DWC 2.1.5 and DSF 2.1.1 released:

If that is the only file I wouldn't worry about it David.

I'm not worried - I just need to avoid making the same mistake when I do the 3.01 stable release

[dc42]

@Silrocco said in RRF 3.01-R10, DWC 2.1.5 and DSF 2.1.1 released:

@chrishamm

Uploading DuetMaestroAP.bin didn't work either, getting an infinite upload status for minutes that I have to cancel out.

Is that repeatable? What is the file size of the DuetMaestroAP.bin file on your PC?

[arhi]

Duet WiFi, Ethernet and Maestro: a default bed heater is no longer created, so you need to use M140 H0 in config.g if you want to replicate the prevous behaviour. The online configurator already generates this command automatically when you configure a bed heater. Any M143 H0 command must come later in config.g than the M140 H0 command, because M140 resets the temperature limit for the heater to the default for bed heaters.

This is confusing to me so need to check. M140 is used to set the bed temp? What is new, to set the bed temp we now need to do M140 H0 S100 in g-code for the job or ? Why would that ever be in config.g ? Shouldn't config.g only be M308 S0 to define bed temp sensor and M950 H0 to create bed heater?

Am I missing something or ?

M140

RepRapFirmware also provides an optional 'H' parameter to set the hot bed heater number(s). If no heated bed is present, a negative value may be specified to disable it. M140 commands with H parameters would normally be used only in the config.g file.

So maybe M140 H0 P0 does what's required? if it does, I have to say it's not clear from the documentation few more words would have to be added both for M950 and M140

[c310]

i am not able to get heat bed configured:

M308 S0 P"bed_temp" Y"thermistor" T100000 B4250 R4700  	; define bed termistor sensor
M950 H0 C"bed_heat" T0 					; heater 0 uses the bed_heat pin, sensor 0

once i issue M140 S40
Error: M140: No bed heater has been configured for slot 0
and i do no see heat bed on DWC

what is wrong? please advice how to treat it

[dc42]

In response to the last 2 posts: READ THE UPGRADE NOTES!!!!

Why do I bother to write them?

[arhi]

@c310 add

M140 H0 P0

after M950

[Phaedrux]

@arhi https://duet3d.dozuki.com/Wiki/Gcode#Section_M140_Set_Bed_Temperature_Fast

RepRapFirmware also provides an optional 'H' parameter to set the hot bed heater number(s). If no heated bed is present, a negative value may be specified to disable it. M140 commands with H parameters would normally be used only in the config.g file.

It's basically just telling the firmware that heater is a bed so that it uses appropriate values for a bed heater by default. There have been many people with issues where their bed would give heater faults for heating too slowly because the firmware was expecting it to act like a hotend by default. This change just informs the firmware that it is a bed again.

At least I think that's what's going on.

[arhi]

@dc42 I did, and I got it working but is very unclear

a default bed heater is no longer created, so you need to use M140 H0 in config.g

I created a heater already so "no longer created", but I just did .. I just added the code and it works but ... maybe

"default bed heater is no longer auto assigned, so you need to assign it using M140; use M140 H0 in config.g ..."

I know I'm nitpicking and you have more important things to do but looking at M140 amd M950 there's nothing about assigning heater to this or that

[dc42]

@arhi said in RRF 3.01-R10, DWC 2.1.5 and DSF 2.1.1 released:

@dc42 I did, and I got it working but is very unclear

a default bed heater is no longer created, so you need to use M140 H0 in config.g

I created a heater already so "no longer created", but I just did .. I just added the code and it works but ... maybe

"default bed heater is no longer auto assigned, so you need to assign it using M140; use M140 H0 in config.g ..."

I know I'm nitpicking and you have more important things to do but looking at M140 amd M950 there's nothing about assigning heater to this or that

The upgrade notes are:

Upgrade notes:

Duet WiFi, Ethernet and Maestro: a default bed heater is no longer created, so you need to use M140 H0 in config.g if you want to replicate the prevous behaviour. The online configurator already generates this command automatically when you configure a bed heater. Any M143 H0 command must come later in config.g than the M140 H0 command, because M140 resets the temperature limit for the heater to the default for bed heaters.

If you tell me what you didn't find clear, I will try to improve the text.

[arhi]

@Phaedrux said in RRF 3.01-R10, DWC 2.1.5 and DSF 2.1.1 released:

It's basically just telling the firmware that heater is a bed

If you look my question I c/p both related paragraphs from the documentation.

1st issue - heater is already created with M950 so what's being "created again". reading your comment it looks like heater is being assigned .... ok, makes sense that's required, just needs to be properly documented

2nd issue - M140 is "set bed temp fast" .. there is zero chance a normal person will look there to find how to assign a heater to be a bed heater ... like negative infinite

again, nitpicking but maybe, just maybe someone find it useful, if not well sorry for wasting everyone's minute

[arhi]

@dc42 said in RRF 3.01-R10, DWC 2.1.5 and DSF 2.1.1 released:

Duet WiFi, Ethernet and Maestro: a default bed heater is no longer created, so you need to use M140 H0 in config.g if you want to replicate the prevous behaviour. The online configurator already generates this command automatically when you configure a bed heater. Any M143 H0 command must come later in config.g than the M140 H0 command, because M140 resets the temperature limit for the heater to the default for bed heaters.

If you tell me what you didn't find clear, I will try to improve the text.

I really don't want to waste your time nitpicking so apologies but .. sometimes stronger then me ... so ..

this part:

default bed heater is no longer created,

this makes no sense to me, I created the heater already and there is nowhere in the g-code documentation about other way of creating a heater.

Now using something like "is no longer assigned to bed" or some wording like that with updating M140 to explain H is assigning heater id to bed heater id would imo solve the problem

[dc42]

I've changed the M140 (and M141) headings and text in the GCodes wiki page, and changed "created" to "assigned" in the upgrade notes. I hope this will help make it clearer.