Firmware 2.02RC2 released

[dc42]

Thanks for the report!

[DougJones]

I upgraded from 1.21 to 2.02RC2 today and I was successfully using my printer before the upgrade and now I am experiencing loads of over temperature shutdown errors on 4 of my drivers.

When I home some of the axis no longer move.

I have looked on the wiki and forum and cannot seem to figure out what has changed between the firmware versions. i did update my homing files to use H instead of S because I do have a laser as Tool 3.

I assume that everything is conencted properly and it is just a difference in the firmware because the system was running 10 minutes ago.

Here is a section of my config file for reference

; Axis and motor configuration
M584 X0 Y1 Z2 U6 V7 W8 E3:4:5 ; Drive 1 is Y, Drive 0 is X, Drive 6 is U, Drive 2 is Z1/Z2, Drive 3/4/5 is Extruder 1/2/3, Drive 7 is V, Drive 8 is Laser W

M569 P0 S1 ; Drive 0 goes forwards X Axis
M569 P1 S1 ; Drive 1 goes forwards Y Axis
M569 P2 S1 ; Drive 2 goes forwards Z Axis (both in series)
M569 P3 S0 ; Drive 3 goes backwards Extruder 1
M569 P4 S1 ; Drive 4 goes forwards Extruder 2
M569 P5 S1 ; Drive 5 goes forwards Extruder 3
M569 P6 S0 ; Drive 6 goes backwards U Axis
M569 P7 S1 ; Drive 7 goes forwards V Axis
M569 P8 S0 ; Drive 8 goes backwards W Axis
M569 P9 S1 ; Drive 9 goes forwards Not Assigned

M574 X1 Y1 Z1 U2 V1 W2 S1 ; set endstop configuration (all endstops at high end, active high)

;*** The homed height is deliberately set too high in the following - you will adjust it during calibration
M666 X0 Y0 Z0 U0 V0 ; put your endstop adjustments here, or let auto calibration find them
M350 X16 Y16 Z16 U16 V16 W16 E4:4 I1 ; Set 16x microstepping with interpolation
M92 X160 Y80 Z1600 U160 V160 W80 ; Set axis steps/mm
M906 X2400 Y2000 Z2400 U2400 V2400 W2400 E1000 I50 ; Set motor currents (mA) and increase idle current to 60%
M201 X500 Y100 Z100 U500 V500 W500 1000 ; Maximum Acceleration(mm/min)
M203 X5001 Y3000 Z250 U5001 V5001 W5001 ; Maximum Feedrate (mm/min)
M208 S0 X417 Y421 Z375 U505 V421 W510 ; Set Axis Max Travel could be 400
M208 S1 X-76 Y-205 Z0 U0 V-205 W0 ; Set Axis Min Travel
M566 X150 Y25 Z100 U150 V150 W150 E500 ; Maximum instant speed changes mm/minute

[DougJones]

It occurs to me I never cycled power after the firmware updates.

Cycled power, Everything seems to be fine now.

[garyd9]

Just reported in another thread that I got "Error: motor phase A disconnected on drivers 2" on 2.02RC2. Detail and links to config files here: https://forum.duet3d.com/topic/6753/error-motor-phase-a-and-phase-b-disconnected-on-drivers-2/6

[incogizmo]

Can confirm the Maesto with LCD display menu still has a stuttering problem with high detail areas, however the changes in this RC have significantly reduced it. When I rename menu to menu.bak and restart and stuttering stops.
Slic3r Gyroid infil is the perfect way to reproduce it or in Simplify3d small holes eg ~3mm screw holes.

Loving the hybrid stealthchop/spreadcycle and all the LCD menu additions.

Edit: another thing I noticed is the Z possition on the LCD does not have the mesh leveling offsets. eg: while printing one layer, on one side of the bed LCD would show Z: 0.20 the otherside would report Z: 0.25

[Gone2Far]

Everything seems to work well so far on my delta with Duet WiFi+Panel Due.

[wilriker]

@gone2far said in Firmware 2.02RC2 released:

Everything seems to work well so far on my delta with Duet WiFi+Panel Due.

Same here on my i3 style Cartesian.

[genghisnico13]

I got the error "Error: motor phase A disconnected on drivers 1
Error: motor phase B disconnected on drivers 1" when pushing my motors. It doesn't seem to affect anything.

[Phaedrux]

I've done a few prints and things seem ok on my CoreXY.

[dc42]

@genghisnico13 said in Firmware 2.02RC2 released:

I got the error "Error: motor phase A disconnected on drivers 1
Error: motor phase B disconnected on drivers 1" when pushing my motors. It doesn't seem to affect anything.

Do you get that message frequently? Please run M115 to check that you really are running 2.02RC2, not 2.02RC1.

[genghisnico13]

@dc42 I have the RC2:
FIRMWARE_NAME: RepRapFirmware for Duet 2 Maestro FIRMWARE_VERSION: 2.02RC2(RTOS) ELECTRONICS: Duet Maestro 1.0 FIRMWARE_DATE: 2018-09-07b2
I only saw it once (since the update to RC2), but I haven't been printing these past few days, I still have a few tests and calibrations pending before I start printing.
I'll try to see if I can find a way to trigger the error, if I can I will post here.

[genghisnico13]

Well, that didn't take long.
Ive been writing a script to test the limits of my printer travel acceleration, with this Gcode I can trigger the error, it isn't 100% effective, but after running it a few times the error appears.
0_1536974933035_YMax7000mms2 steps200.g
This Gcode was designed for Cartesian printers and needs to have 200mm of movement in the Y direction with a MIN limit switch.

It basically moves the bed to position 200 at a known safe speed(50mm/s I believe), tweaks the acceleration(to the value to test) and moves to position 20 at 300mm/s, then sets the acceleration to a known safe value and goes to position 0, then moves to -0.1mm(at really low speed which could be the trigger based on what I read) to make sure the endstop is triggered and sends an M119 and loops again with a different acceleration.
Since we don't have conditional Gcode(I know that its going to take a lot of work to implement if ever), this is the best semi-automatic way to find the limits of my motors. In the console you can see the acceleration at which steps are lost:
10:13:03 PMY axis Acceleration 6600mm/s2: Endstops - X: at min stop, Y: not stopped, Z: not stopped, Z probe: not stopped
10:12:56 PMY axis Acceleration 6400mm/s2: Endstops - X: at min stop, Y: at min stop, Z: not stopped, Z probe: not stopped
10:12:49 PMY axis Acceleration 6200mm/s2: Endstops - X: at min stop, Y: at min stop, Z: not stopped, Z probe: not stopped
edit: the steps are set low(200mm/s2) specifically to make it long and trigger the error.

[dc42]

Thanks, this is now on my list to investigate. I probably won't have time to look at it until after TCT.

[genghisnico13]

@dc42 no problem, it's not a priority, as far as I can tell there are no adverse effects.

[genghisnico13]

@dc42 I discovered that the error happens more often in stealthchop, I've been testing a silent profile with M569 V0 and the disconnected phase error happens more often, all this tests are made in a CR-10 that has high inductance motors at 14V.

Just in case I reiterate: not a priority, it really doesn't bother me at all, I just wanted to make it easier for you to replicate the error.

[john]

Running dual motor Y-axis on Driver 1 & 2. Received "Error: motor phase B disconnected on drivers 1 2" today.

Duet 2 WiFi/Ethernet version 2.02RC2 (RTOS). It halted my operations because the parent thread received the unexpected message above from the GCode thread.

[dc42]

@sean said in Firmware 2.02RC2 released:

Running dual motor Y-axis on Driver 1 & 2. Received "Error: motor phase B disconnected on drivers 1 2" today.

Duet 2 WiFi/Ethernet version 2.02RC2 (RTOS). It halted my operations because the parent thread received the unexpected message above from the GCode thread.

What parent thread was that? RepRapFirmware takes no action when it detects a motor disconnect other than reporting it.

[kuhnikuehnast]

I get the same error of the "motor phase A disconnected on drivers 

It always happens if I start the auto bed compensation. (Prusa Style Printer, 2 Stepper Drivers for Z to adjust the axis).

Code of Bed.g:
M561 ; clear any bed transform

G30 P0 X20 Y20 H0 Z-99999
G30 P1 X200 Y20 H0 Z-99999 S2

If needed, I could also paste my config.g? (how do you get it to be shown as "source code"?

greetings kuhni

[john]

@dc42 We run things a little different than most users seem to. We have a parent python thread that sends GCommands to the Duet through pyserial(). When an messages is sent back from the Duet that is not "OK" or "Endstop Status: ..." the thread sending GCode stops (because presumably something unexpected happened).

[Catalin_RO]

@dc42 I had a quick look through the latest source files and found this rather strange looking piece of code in GCodes.cpp, in GCodes::DoArcMove

if (!seenXY && seenIJ)		// at least one of XY and IJ must be specified
{
	return  "G2/G3: missing parameter";
}

Some how the condition looks wrong, as G2/G3 with no parameter would pass through instead of being just a NoOperation.