RRF 3.01-RC10, DWC 2.1.5 and DSF 2.1.1 released

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.

c310

based on our discussion here i have updated g-code M140 documentation with the note and sample error.
personally I read release notes and could not figure out what to do with M140...

perhaps we should rename M140 from "Set Bed Temperature (Fast) " to
"Configure Bed Heater or Set Bed Temperature (Fast)"

any thoughts?

dc42

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

based on our discussion here i have updated g-code M140 documentation with the note and sample error.
personally I read release notes and could not figure out what to do with M140...

perhaps we should rename M140 from "Set Bed Temperature (Fast) " to
"Configure Bed Heater or Set Bed Temperature (Fast)"

any thoughts?

I've already done that.

deckingman

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

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

Sorry to butt in on this but I do believe that I can see how the confusion arises. Looking at the wiki for gcode M950 it reads thus:

"M950 is used to create heaters, fans and GPIO ports and to assign pins to them. Each M950 command assigns a pin or pins to a single device. So every M950 command must have exactly one of the H, F, J, P or S parameters."

....and then in the examples it shows

"M950 H1 C"out1" Q100 T1 ; create heater 1"

So I can see how users might be forgiven for thinking that the M950 H0 command is all that is required to create a bed heater.

Perhaps the notes about M950 should include the need to use M140 H0 as well? Might that clarify things?

Silrocco

@dc42

I'm all set now, I directly installed the "DuetMaestroAP.bin file onto the SD Card and then uploaded the update.

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 Maestro FIRMWARE_VERSION: 3.01-RC10 ELECTRONICS: Duet Maestro 1.0 FIRMWARE_DATE: 2020-04-25b3

Thanks for all the support here.

Danal

Install went fine, very smooth, including firmware load of B0. It also appears to operate, although I have not yet done a full print.

WOW the update of B1, etc, messages got MUCH CLEANER. I realize that 3HC boards are still on RC7... but I just thought I'd check, and the "Please wait, updating" style messages are GREAT.

It seems that DWC "Emergency Stop" hangs and never comes back. If I can derive info, I will start a linked thread.

arhi

first short print (2 hours) done, everything working awesome

Garfield

A Noctua Fan that I use to cool the CPU / drivers etc has now become an 'ON/OFF' fan, it used to work fine between the 40 / 45 Deg limits set.

It now is either at 100% or nothing, it comes on at the low end i.e. 40, this used to work just fine so I won't accept that this is a gcode issue unless M950 has changed but not yet been documented.

Up until the update this morning the fan has been fine (although I have skipped a couple of RC versions).

I am now getting

'inconsistent Z' when trying to home Z.

Cancel print results in a 'attempt to extrude with no tool selected' error.

NOTHING has been changed mechanically - was all tickety boo before the update.

Has anyone developed a 'Test plan' that can be executed against new RC's - many people can execute on different hardware and report result - just a thought.

ChrisP

Problem with DCS crashing ungracefully (usually on startup) - DCS Crash with 3.01-R10 / DWC 2.1.5 / DSF 2.1.1

Danal

Bug report: G32 messages work from console, not from DWC.

https://forum.duet3d.com/topic/15894/g32-messages-not-returning-to-console-rrf-3-01-rc10

Garfield

very basic Q to ask - shouldn't the Duet3 boot from the same SD card used by the Pi ?

Because mine doesn't, doesn't make any attempt to get an IP address when hardwired.

gtj0

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

very basic Q to ask - shouldn't the Duet3 boot from the same SD card used by the Pi ?

Because mine doesn't, doesn't make any attempt to get an IP address when hardwired.

Other than the M55x network commands, it should work. Make sure they're not commented out when in standalone mode.

Garfield

Don't have any M55x commands - have never had any ...

Phaedrux

@Garfield I think you'd need at least M552 S1 to enable networking. It should get a DHCP address. You should then be able to reach the printer via the name set in M550 P. Http://printername

Garfield

Gone from bad to worse ... can't even boot the DWC in the Pi now .... Pi boots OK ... sytemctl status reports DWC is running but can't access it.

gtj0

@Garfield I thought you were trying to go standalone to get around the DCS issue, no?

A Former User

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

very basic Q to ask - shouldn't the Duet3 boot from the same SD card used by the Pi ?

Because mine doesn't, doesn't make any attempt to get an IP address when hardwired.

it won't unless you copy the config from /opt/dsf/sd/sys to /boot/sys before removing it from the Pi. (moving the config to /boot/sys/config.g and symlinking it back to /opt/dsf/sd/sys/config.g would be an interesting exercise though (and adding M552 S1))

i.e. duet can only read the first fat32 partition, raspbian uses it for /boot and the duet is unable to read the config file the pi normally uses.

Garfield

I was trying to boot stand alone - couldn't - put it into the Pi and although DWC reports running it can't be accessed, I can access SSH.

Never been a Linux fan ..... never will be until it ceases to a 19th century OS accessible only to those prepared to waste days on a basic config (I am not one of those - I have a life)

gtj0

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

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

very basic Q to ask - shouldn't the Duet3 boot from the same SD card used by the Pi ?

Because mine doesn't, doesn't make any attempt to get an IP address when hardwired.

it won't unless you copy the config from /opt/dsf/sd/sys to /boot/sys before removing it from the Pi. (moving the config to /boot/sys/config.g and symlinking it back to /opt/dsf/sd/sys/config.g would be an interesting exercise though (and adding M552 S1))

i.e. duet can only read the first fat32 partition, raspbian uses it for /boot and the duet is unable to read the config file the pi normally uses.

Can't symlink in that case but yeah, I keep forgetting about people running their SBC from an SD card since I run from SSD. When I need to go standalone, I just copy the /opt/dsf/sd/ directory contents to a freshly formatted SD card.