It's out! Firmware 1.21 released

resam

Nengerman: you have to read the release notes! Homing on a Cartesian/CoreXY printer changed.

Doc_Pengu

Does you'r homing script 1st lower/raise bed before it homes X and Y ? If so you need to add S2 parameter to you'r Z axis movement and then X and Y can be homed and Z axis after that

Knaudler

@dc42:

Get it from https://github.com/dc42/RepRapFirmware/releases/tag/1.21 and be sure to read the upgrade notes at https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md. If you want the full list of changes since release 1.20, for now you will have to read all of the 1.21RC release notes too, but in a few days I'll delete the 1.21RC releases and consolidate the change lists.

Hello

there ist webcontrol 1.21 out
https://github.com/chrishamm/DuetWebControl

Ingo

dc42

Thanks, I've updated the release to include it.

appjaws

I was running rc4 and have today updated to 1.21. I expected this to just work.
I uploaded the Duet2CombinedFirmware.bin, DuetWiFiServer.bin, iap4e.bin and DuetWebControl.zip files. When the duet rebooted it could not connect.
The USB printer interface connected to the printer so I tried to run M997 S0 to install the firmware again but this did not work.
I then erased and reset the board and used BOSSA 1.18 to install, so device manager shows Duet 2 WiFi or Duet 2 Ethernet 3D printer control electronics (COM5)
Then reset the board and connected the USB again. The printer is online but when I send M997 S0 I get the error Can't read from printer (disconnected?).
I have followed the Fallback procedure instruction on https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware

I am now stumpted How can I resolve this?

appjaws

This is the result of M122.

SENDING:M122
=== Diagnostics ===
Used output buffers: 1 of 32 (1 max)
=== Platform ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.0 or 1.01 + DueX5
Board ID: 08DAM-999TL-NL5T8-6J1DL-3SJ6P-T65BJ
Static ram used: 16152
Dynamic ram used: 100440
Recycled dynamic ram: 2192
Stack ram used: 3576 current, 4456 maximum
Never used ram: 7832
Last reset 00:00:13 ago, cause: power up
Last software reset at 2018-03-12 17:04, reason: User, spinning module GCodes, available RAM 7768 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 12.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 18.1, current 21.3, max 21.4
Supply voltage: min 0.0, current 0.0, max 0.0, under voltage events: 0, over voltage events: 0
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Driver 5: ok, SG min/max not available
Driver 6: ok, SG min/max not available
Driver 7: ok, SG min/max not available
Driver 8: ok, SG min/max not available
Driver 9: ok, SG min/max not available
Expansion motor(s) stall indication: yes
Date/time: 1970-01-01 00:00:00
Slowest main loop (seconds): 0.000242; fastest: 0.000047
=== Move ===
MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is ready with "M122" in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8

WiFi -
Network state is disabled
WiFi module is disabled
Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485
Socket states: 0 0 0 0 0 0 0 0
=== Expansion ===
DueX I2C errors 0

appjaws

This is after re-enabling M552 S1 in config

=== Network ===
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8

WiFi -
Network state is starting
WiFi module is disabled
Failed messages: pending 0, notready 0, noresp 0
Socket states: 0 0 0 0 0 0 0 0
=== Expansion ===
DueX I2C errors 0

appjaws

resolved
For some reason it appears that the WiFi server had not started.
re-installed and now all OK.

DunstonUK

It is alright changing stuff around, but how do you raise your Z when you have a bed crash, and all you get is

M120
G91
G1 Z5 F6000
M121
Error: G0/G1: insufficient axes homed
Error: Pop(): stack underflow!

and Yes I do have S2 in the files.

dc42

Those messages indicate that the printer was not homed when you ran that command. I guess you powered the machine down when you had the crash and then powered it up again. Possible actions in this situation include;

Home the printer. The homall file for a Cartesian or CoreXY printer normally raises the head a few mm before it does anything else.
Use M564 H0 to allow movement before axes are homed, either in config.g if you want it to be permanent, or temporarily
Use a macro to raise the head by 5mm, using S2 on the G1 Z command

jnolan72

I am getting
Request Timeout

The last HTTP request has timed out. Please make sure the connection between your device and the board is not interrupted.

Anytime I go into G-Code Files then into a Directory with lots of files. I get a spinney icon then
request Timeout

the files has a * infront of them.

Looks like when I go into a directory that I have not gone into after the patch
Some sort of processing is going on change the * to a page icon

Same problem when I upload a large gcode file
when I hit close after uploading
the file show a * and the the Request Timeout

resam

jnolan72: try to reformat your SD card. I have similar issues from time to time. I think the filesystem on my card just gets fragmented or something - or my card is bad in general.

Copy all your files to you PC. Format & wipe the cards. Make a clean FAT32 filesystem, and copy your files back.

Also make sure to keep not too many files in one folder. There is a limit on how many files the Duet can handle. Less than 50 files per folder usually works for me.

dc42

That timeout is triggered when you have a very large gcode file on the SD card and your SD card is formatted with a small cluster size. You can send M39 to find the cluster size if you are running firmware 1.21.

Get a new SD card, format it using FAT16 it is 4Gb or smaller, else FAT32 with 64kb clusters. Then copy all the files and folders over from the old SD card.

Upgrading to firmware 1.21 may also help, if you are running an older version.

zerspaner_gerd

Hello,

three questions:

what is meant by this?

[c]For Duet 06 or 085: RepRapFirmware.bin and iap.bin[/c]

Where do I see my version?
Is the pressure range with nozzle offset checked during simulation?
[c]When beginning a print from SD card, macro /sys/start.g is run if it is present[/c]
Is there such a thing for the printing end?

greeting

dc42

1. The Duet 06 and Duet 085 are older boards that pre-date the Duet WiFi and Duet Ethernet. The PCB revision is printed on the board. For those boards it is 0.6 or 0.8.5. For Duet WiFi or Ethernet it is 1.0, 1.01, 1.02 or 1.03.

2. Please explain what you mean by "pressure range".

3. Yes, stop.g.

rpoltera

Unable to adjust z hight with my IR probe I have raised and lowered over 5mm what worked before is no longer working it doesn't seem to change it is over 2mm of the build pate now
have tried
G31 P500 X0 Y0 Z-5.9
all the way to
G31 P500 X0 Y0 Z5.9

with no change in the hight I have read the notes on the new version but not seeing it am I missing something?

as I mentioned this used to work flawlessly and now I cant use my probe please advise.

dc42

Is there a G31 command in config-override.g that is overriding the one in config.g? Prior to version 1.20, M500 used to save the G31 settings; now it does so only if you provide an extra parameter.

zerspaner_gerd

@dc42:

1. The Duet 06 and Duet 085 are older boards that pre-date the Duet WiFi and Duet Ethernet. The PCB revision is printed on the board. For those boards it is 0.6 or 0.8.5. For Duet WiFi or Ethernet it is 1.0, 1.01, 1.02 or 1.03.

2. Please explain what you mean by "pressure range".

3. Yes, stop.g.

I have version "Duet2 V1.03" that means I would not need these files at all?
Sorry, meant "print area" which was defined with M208.
"Stop.g" not with me executed automatically at the end of the print, like "start.g" at the beginning of the print.

dc42

1. So you need the files listed for the Duet WiFi or Duet Ethernet (whichever board you have).

2. Yes, movement limits are applied during simulation. So G0/G1 moves that would go to outside the bed are modified to remain inside the bed, and G2/G3 moves that would go outside the bed cause the simulation to be aborted.

3. stop.g is only executed if your end gcode finishes with command M0.

rpoltera

no g31 in the config-override.g I added the config-override.g I also checked to make sure there was not a second g31 somehow

; This is a system-generated file - do not edit
; Heater model parameters
M307 H0 A90.0 C700.0 D10.0 S1.00 V0.0 B1
M307 H1 A272.0 C158.9 D3.3 S1.00 V23.7 B0
M307 H2 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H3 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H4 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H5 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H6 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H7 A340.0 C140.0 D5.5 S1.00 V0.0 B0