Are they stepstick-type drivers, or large external driver modules with opto isolated inputs? If the latter, then given that those are usually intended for 5V drive and they only get 3.3V if you drive them directly from the expansion connector, it's quite likely that when you drive 2 of them form a single set of pins, the drive voltage drops too much. In which case, do as Tony says. Your interpretation of what he meant is correct.

Here are 2 ways:

1. Set Output On Extrude, M571. This is suitable if you want to open the valve during extruding but not during retraction or on-printing moved.

2. P parameter on G1 commands. This can control the valve however you want, but you need to generate GCode that includes the correct P parameters.

I have fixed this issue. The fix will be in firmware RRF 1.21RC1 and DWS 1.21RC1, both of which which I hope to release soon.

Thanks! Is it calibratable, with a scale and offset?

I have just tried and failed to reproduce that, so I suspect it is fixed in firmware 1.20.

I'm sorry, I don't understand the problem. I typed 100 into the extruder steps/mm box that originally said 420; then when I generate the files, I get E100 in the M92 command, which is correct.

I don't know Lasergrbl so you need to see what GCode it generates.

I am aware of three different schemes for generating GCode files for laser cutters and engravers:

1. Generate GCode commands with E movements to control the laser. This is supported by RRF. You can use M571 to turn a PWM pin on/off with extrusion.

2. Use separate M3 and M5 commands to turn the laser on and off. This is supported by RRF.

3. Generate G1 commands with an extra S parameter to control the laser PWM. This is not currently supported by RRF. That use of the S parameter clashes with the meaning of the S parameter in RRF.

The deployprobe and retractprobe files should not be there if your Duet had firmware 1.19 installed when you received it; but if it had an earlier firmware version, they will have been on the SD card as shipped.

For now it seam it works. I have soldered the cable extension of one z motor (before it used a dupont connector), the other is near the duet so it hasn't an extension cable.

@dc42:

I have taken a look. It appears to have got stuck in the SD card driver because a command failed to complete. I have seen at least one other occurrence of this.

I have it in mind to add a timeout to that function to avoid the reset happening.

Thank you for taking the time to look into it, I forgot to include that I had tried to load the duet web control page to check on the printer's progress when the reset happened.

Thanks

thanks,
I see it I have changed G28 x y to G28 and it works
now adjust the feather with the z height and then make a test print
thank you for the assistance

Thanks.

An hour load time is not a problem for a 80hr build! I doubt that aspect of the project will run that far (the generation of the CAD data would be painful too, slicing even worse!) but if it does it will be after sorting enclosure, risk assessment, automatic extinguisher, and long pauses.

I'll verify (next week) a large file load time for a python generated slice file and respond on this thread with the results.

[solved]

I have a very short ptfe betwee bondtech and e3d heatsink. Turns out I had used the wrong nozzle size.. I installed 0.25mm and when slicing I set it as though it's a 0.3mm nozzle… This result in too much pressure in the ptfe and bondtech never slips so it pushes down the e3d hence giving me false thinking that the z tower on right side appear to struggle...

It's neither. The additional extruder movement is calculated as extrusion_speed * pressure_advance_time.

Folders and files are both enumerated in the same list. So if the list is full, then new folders as well as new files may fail to be displayed.

You can create new subfolders of /gcodes using Duet Web Control. There is a "Make new directory" button on the GCode Files page.

I tried another variation (and the issue still occurred.) Thinking that perhaps something in my homeall.g macro might have been causing a problem, or perhaps selecting the tool was causing a problem, I moved both commands to occur before the initial heating of the HBP. That did not resolve the problem. The "M116 P0" command still did NOT wait for the extruder tool to heat up. Here's the "new" gcode snippet:

[[language]] G90 M83 M106 S0 ; S3D starting gcode for LEFT extruders ; G28 ; homeall T0 ; load left tool M140 S105 ; start heating the bed (no wait) while homing G1 X-145 Y-70 Z30 F6000 ; move to wait position left hand side of table M291 P"Heating Build Plate" S1 T6000 ;M190 S105 ; now wait for the bed to finish heating M116 H0 ; alternate way to wait for the bed to finish heating M292 M300 S600 P600 ; make some noise G10 P0 S240 ; set T1 temp G10 P1 S0 ; set T1 temp M291 P"Heating Tool" S1 T6000 M116 P0 ; wait for everything to get to the designated temp M292 M300 S600 P600 ; make some noise M291 P"Purging and Wiping Left Nozzle" S1 T5 G1 Z0.4 ; Position nozzle G1 X-105 Y-70 E25 F300 ; purge nozzle G1 X-115 Y-70 Z0.15 F1200 ; slow wipe in reverse G1 X-100 Y-70 Z0.5 F1200 ; lift across wipe area

Ok thanks.