It's out! Firmware 1.21 released

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

zerspaner_gerd

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

Have DuetWifi.
So I only need these files:
[c]DuetWiFiFirmware.bin or Duet2CombinedFirmware.bin (which are the same file), DuetWiFiServer.bin and iap4e.bin[/c]
I do not need these:
[c]RepRapFirmware.bin and iap.bin[/c]
There is no message if G0/G1 is outside the print area?

So it does not come to a collision but my part is dan for the trash can, Mhh????

dc42

1. Correct.

2. In FDM printer mode, that is correct. The reason is that it is quite common for a skirt to exceed the bounds of the bed. In laser and CNC mode the print will be terminated. If you want this changes, please suggest what you would like instead in the Firmware Wishlist section.

rpoltera

I figured out my issue with the IR probe well got it working anyways must have been a bad update I guess formatted my sd card and added all my files back, and now it is working correctly.

alclonky

Hi,
i tried to adjust my homing files for my Cartesian Printer
Homing X and Y works again, but home z just moves the 5 up and then stops with

G28 Z
Error: G0/G1: insufficient axes homed

myhomez.g:
G91
G1 Z5 F6000 S2
; Back to absolute positioning
G90
; Go to first bed probe point and home the Z axis
G1 X0 Y0 F6000
G30

dc42

Read the upgrade notes for firmware 1.21.

alclonky

I did, otherwise i couldn't home X and Y

or did I miss something else?

deckingman

Looking at the above, I'd have thought that your home Z will work but only if you have homed X and Y first. If you haven't, then this line G1 X0 Y0 F6000 will cause the problem. So to be safe, add S2 to it then it won't matter if X and Y have been homed.

alclonky

i tried adding S2 to this line and without that line, but in both cases Z wont home

dc42

Please confirm: are you saying that even if you have homed X and Y first, you get that message if you try to home Z?

If you try to home Z without homing X and Y first, then that message is expected, because the firmware doesn't know where X0 Y0 is.

alclonky

Yes, thats what i am saying

i can home X and Y first and when i home z it failes
if i home all it homes X and Y and failes with z