Only by installing a new driver chip. It's possible that connecting a small signal Schottky diode between the CS and SDO pads for that chip (cathode to CS) might also work, but I haven't tested it.

Comments on this?

I upgraded the firmware to 1.19RC5. Been using the printer for around 5 hours with no disconnects so I'd say this is fixed.

It seems that since I updated to 1.19 RC1 these poor behaviors have greatly improved and possibly disappeared.

I'm glad it's working. I suspect a bad connection.

Also looks like no tool is selected try putting T0 at the end of your Config File

Have you tried RC5, and put the M200 command in the slicer start gcode and nowhere else? I find it surprising that Cura doesn't add the M200 command itself.

Nobody else has reported having to remove M83 from config.g to use absolute extrusion, as long as they included M82 in the start gcode

Ok ….just one little BUG
M291: Display message and optionally wait for response
Supported in firmware version 1.19beta7 and later.

Parameters
P"message" The message to display, which must be enclosed in double quotation marks. if the message itself contains a double quotation mark, use two double quotation marks to represent it.
R"message" Optional title for the message box. Must be enclosed in double quotation marks too.
Sn 0 = no acknowledgement needed (default), 1 = display an OK button and wait for it to be pressed (the user interface then sends M292 to indicate that is has been acknowledged)
Tn Timeout in seconds, ignored if S=1. The message will be cancelled after this amount of time, if the user does not cancel it before then. A zero or negative value means that the message does not time (it may still be cancelled by the user). The default value is 10 seconds
Zn 0 = no special action, 1 = display Z jog buttons alongside the message to allow the user to adjust the height of the print head

if set Z0 appear the jog control ,also is set Z1 😉

Any news on this?

I'm having some quirky and unnerving behavior in 1.19beta11 when I switch tools on my diamond hot end delta. Sometimes the printer will quietly switch without any retraction and sometimes it makes alarming noises while it retracts and extracts back and forth violently and very quickly. I'm not sure why it does one or the other. My tools definitions are as follows:

; Tool definitions

M92 E60.28:60.28:60.28 ; Set extruder steps per mm
M207 S3.75 F3000 ; set firmware retraction
M563 P0 D0:1:2 H1 ; Define tool 0
G10 P0 X0 Y0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
M568 P0 S1 ; Enable mixing for tool 0
M567 P0 E0.90:0.05:0.05 ; Set mixing ratios for tool 0 (90%,5%,5%)
M563 P1 D0:1:2 H1 ; Define tool 1
G10 P1 X0 Y0 ; Set tool 1 axis offsets
G10 P1 R0 S0 ; Set initial tool 1 active and standby temperatures to 0C
M568 P1 S1 ; Enable mixing for tool 1
M567 P1 E0.05:0.90:0.05 ; Set mixing ratios for tool 1 (5%,90%,5%)
M563 P2 D0:1:2 H1 ; Define tool 2
G10 P2 X0 Y0 ; Set tool 2 axis offsets
G10 P2 R0 S0 ; Set initial tool 2 active and standby temperatures to 0C
M568 P2 S1 ; Enable mixing for tool 2
M567 P2 E0.05:0.05:0.90 ; Set mixing ratios for tool 2 (5%,5%,90%)
M563 P3 D0:1:2 H1 ; Define tool 3
G10 P3 X0 Y0 ; Set tool 3 axis offsets
G10 P3 R0 S0 ; Set initial tool 3 active and standby temperatures to 0C
M568 P3 S1 ; Enable mixing for tool 3
M567 P3 E0.34:0.33:0.33 ; Set mixing ratios for tool 3 (34%,33%,33%)

T3 ; select tool 3 (evenly mixed)

I also seem to be having more problems with filaments jamming when I extrude single colors as opposed to evenly mixed which is working without issue.

John

Always read the upgrade notes at https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md before installing new firmware. Had you done so, they would have led you to https://duet3d.com/wiki/DuetWiFiFirmware_1.19beta.

The diag light shares a pin with the Z probe MOD signal, so it is always on when using a type 1 Z probe.

I'm having some quirky and unnerving behavior in 1.19beta11 when I switch tools on my diamond hot end delta. Sometimes the printer will quietly switch and sometimes it makes alarming noises while it retracts and extracts back and forth very quickly. I'm not sure why it does one or the other. My tools definitions are as follows:

; Tool definitions

M92 E60.28:60.28:60.28 ; Set extruder steps per mm
M207 S3.75 F3000 ; set firmware retraction
M563 P0 D0:1:2 H1 ; Define tool 0
G10 P0 X0 Y0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
M568 P0 S1 ; Enable mixing for tool 0
M567 P0 E0.90:0.05:0.05 ; Set mixing ratios for tool 0 (90%,5%,5%)
M563 P1 D0:1:2 H1 ; Define tool 1
G10 P1 X0 Y0 ; Set tool 1 axis offsets
G10 P1 R0 S0 ; Set initial tool 1 active and standby temperatures to 0C
M568 P1 S1 ; Enable mixing for tool 1
M567 P1 E0.05:0.90:0.05 ; Set mixing ratios for tool 1 (5%,90%,5%)
M563 P2 D0:1:2 H1 ; Define tool 2
G10 P2 X0 Y0 ; Set tool 2 axis offsets
G10 P2 R0 S0 ; Set initial tool 2 active and standby temperatures to 0C
M568 P2 S1 ; Enable mixing for tool 2
M567 P2 E0.05:0.05:0.90 ; Set mixing ratios for tool 2 (5%,5%,90%)
M563 P3 D0:1:2 H1 ; Define tool 3
G10 P3 X0 Y0 ; Set tool 3 axis offsets
G10 P3 R0 S0 ; Set initial tool 3 active and standby temperatures to 0C
M568 P3 S1 ; Enable mixing for tool 3
M567 P3 E0.34:0.33:0.33 ; Set mixing ratios for tool 3 (34%,33%,33%)

T3 ; select tool 3 (evenly mixed)

I also seem to be having more problems with filaments jamming when I extrude single colors as opposed to evenly mixed which is working without issue.

John

That's all correct, except I think you meant M92 E90:90:90. The M584 command maps (in this case) extruder drives 0, 1, 2 to driver numbers 5, 6, 7.

Yes, i see your videos last days. Thanks

Have you tried using sam-ba? I find this works well. I'm hosting it somewhere here if you search for it.

Hi David,

Yes that has fixed it.

Ref needing more than 10 - I can't off hand think that I would need more than 10 virtual heaters. I currently use 5 for the 5 individual drive motors that I want to cool to stop the plastic mounts distorting, and 1 for the Duet/Duex which makes 6. I can think of one other possibility and that would be if I need to cool the 5 steppers on the extruder carriage. They are pretty close together and share the same plastic mount. However, compared to the XY motors, they are low current and not doing anything like the work that the main motors do in shifting 4 kgs of mass around. If that was an issue, I've run out of fan connectors in any case and have already had to double up the fans cooling the Duet/Duex by connecting them to a single thermistor/fan connector combination. So I'd say that for now, 10 virtual heaters is enough and more would require more hardware fan connectors (which of course may not be needed either but who knows what the future holds?).

I guess it's fair to say that I'm only using this number of virtual heaters/fans because I can, and if they weren't available, I'd live without them or find some other work around.

Ian

No, nothing has changed in that area.

I'm glad to have been of assistance.

@dc42:

I've run some tests:

DWC 1.17+2 (and probably earlier versions too) displays axes ABC but doesn't handle them correctly. I've asked chrishamm to look at this. The problem with homing using endstops 5-9 is as I suspected. I've done a quick fix and I am about to test it. Until RRF 1.20, endstops 5-9 will have higher latency than endstops 0-5. I hope this won't cause problems for you.

Which Duet do you have: WiFi or Ethernet?

latency wouldn't be an issue as long as they home – I can home slowly if it helps with latency issues. Likely by the time I'm further along in the build -- have the heated bed and all other parts done -- you'll have 1.20 out...I'm moving quick with the build, but the wiring is painfully slow, as there is a lot of them, and getting all the wires neatly out through cable chains to the duet was fairly difficult, it's finally done now, so I hope to connect all the thermistors, fans etc -- I've gone through over 200 feet of wire sleeving and about 8 30m spools of silicone wire. None of the runs are especially long, but just there is a lot of things to wire up.
I'm curious find you where the bug was? I was looking through the firmware source and I'm not seeing it. I'm a programmer by trade, and fact that I couldn't figure it is bugging me.
PS -- my duet is Ethernet -- all my printers are hard wired.

Yakov

Hi lars, is the speed problem still present in beta10? Please respond in the thread on beta10 if is is.