It's out! Firmware 1.21 released

dc42 · 21 Mar 2018, 10:35

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.

paboman · 21 Mar 2018, 11:00

last touch ups to the pulse filament detector are also included ?

JohnOCFII · 21 Mar 2018, 14:25

@paboman:

last touch ups to the pulse filament detector are also included ?

Looks like it:

New features and changed behaviour since 1.21RC5:

The rr_status and M408 reports now include the spindle speed
M106 now also reports the current fan PWM for thermostatically-controlled fans
Machine coordinates are always used when running system macros automatically.
Bug fixes since 1.21RC5:

Pulse-type filament monitors are now working
WiFi sockets whose connections abort are now terminated to make them available for re-use
DWC Machine Properties page shows the correct state of active low endstops

paboman · 21 Mar 2018, 14:49

great! thank you

paboman · 21 Mar 2018, 14:49

great! thank you

Phaedrux · 21 Mar 2018, 20:07

Not sure if this is intended or not, but when trying to simulate a file I get various error messages if the axes are not homed first.

[c]2:02:49 PMM37 P"z-motors_fixed.gcode"
Simulating print of file z-motors_fixed.gcode
Cancelled simulating file z-motors_fixed.gcode after 0h 0m simulated time
Error: G0/G1: insufficient axes homed
2:02:16 PMWarning: Tool 0 was not driven because its heater temperatures were not high enough or it has a heater fault
Error: G0/G1: insufficient axes homed
2:02:16 PMM37 P"lm2596_case_fixed.gcode"
Simulating print of file lm2596_case_fixed.gcode
Error: SetPositions called when DDA ring not empty
Cancelled simulating file lm2596_case_fixed.gcode after 0h 0m simulated time[/c]

dc42 · 21 Mar 2018, 20:30

That's a known issue.

Nengerman · 22 Mar 2018, 12:44

I have updated the firmware from 1.20 to 1.21. Now the printer does not work anymore.
When I upload a print file, the bed and the extruder are heated, then the printer stops as if it is ready.
At Home All I get the error message G0 / G1: insufficient axes homed.

resam · 22 Mar 2018, 12:50

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

Doc_Pengu · 22 Mar 2018, 12:52

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 · 22 Mar 2018, 22:58

@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 · 22 Mar 2018, 23:29

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

appjaws · 26 Mar 2018, 13:24

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 · 26 Mar 2018, 13:49

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 · 26 Mar 2018, 13:57

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 · 27 Mar 2018, 10:30

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

DunstonUK · 29 Mar 2018, 05:34

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 · 29 Mar 2018, 06:10

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 · 29 Mar 2018, 15:40

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 · 29 Mar 2018, 16:51

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.