Topics created by selva_tvi

@selva_tvi ahhhh I'll need to think on this. On closer inspection of the Gcode file, your machine follows this logic

T0 prints at Z=0.2

T1 is called, tfree0.g is run
Per tfree0.g, you move Z: G1 Z3 F500 ; up 3mm
T1 nozzle moves to the next printing location: G1 X270.6 Y259.2 F4800

What this means is Z is still equal to Z3, and doesn't go to the proper location until the start of 2, when G1 Z0.4 F1000 moves the T1 nozzle back to the correct height.

I use Cura for my IDEX machine, and on the move following a tool change Cura re-writes the current Z position, so I don't see this issue (I have my tfree set up in a similar way as you, where I move the print head in it). What we should be doing (I think) is using the G1 command with a R2 and Z0 in your tpost0.g and tpost1.g
https://docs.duet3d.com/User_manual/Reference/Gcodes#g1-controlled-linear-move
Example: G1 R2 Z0. This will move the tool head back to the printing Z height.

@chrishamm Thank you. Sorry to ask, what will be the timeline for this?

Actually we have installed a printer to an institute and they dont prefer Wifi. So we are using Panel due.

@selva_tvi is the movement towards the endstops for each axis? If so, I expect the move that the XY move from home back to the resume point is too fast, and it is skipping steps.

Ian

@Phaedrux Board -

Duet 3 MB 6HC V1.02 with RPI 3B.
DSF Version: 3.4.5
Firmware: RepRapFirmware for Duet 3 MB6HC 3.4.5 (2022-11-30)
Duet Web Control 3.4.5

Panel Due 5i - Firmware - 3.4.x

I needed the fan control in the front screen. Is it possible?

Also, if I connect the Pen drive (USB drive) to SBC, how to show in Panel due (It is showing in DWC).

When i clicked the Print icon, it is showing the Sd card option only. It is showing two partitions - one is gcodes and other is firmware files folder

@selva_tvi Would you mind sharing a ZIP of your macro files? Then @mfs12 could have a look.

@dc42 Thank you. Previously with Duet 3 Mini 5, the Filament runout works flawlessly. Even at the start of the print, if the filament is not there, it wont start the print. (Without any special codes). It was with
firmware 3.4.0

I tried the following code in start.g (Got from a thread):

if sensors.filamentMonitors[0].status = "sensorError"
echo "SensorError-0 Continuing to Print"

if sensors.filamentMonitors[0].status != "sensorError"
M25
set global.beepbeep1 = 1
M591 D0
M118 P0 S"filament error" L2```

It worked. When there is no filament at the start, it paused the print.
But when i resumed it without loading the filament, it continues (it means it is not continuously checking).

I kept the same code in resume.g, but it didnt work.

@selva_tvi I am quite sure this is caused by your router then. You could try to assign a different MAC address to the affected board via M540 and check if that makes a difference - maybe there is still an odd rule somewhere in your router's firewall.

If it doesn't work, I'd consider a factory reset of that router although I understand that's easier said than done.

@o_lampe @jay_s_uk thank you. will check and update.

@dc42

@dc42 said in Mirror Mode with IDEX:

@selva_tvi is the problem that you normally home the printer before you select the mirror tool, but when resuming after power fail it homes after selecting the tool?

If so then that should be fixable in the homing files, by running M579 U1 before homing U, then running M579 U-1 afterwards if the mirror tool is current.

I created a new macro Pwrresumehome.g in that I added M579 U1.

Not the Mirror mode power failure resume is working flawlessly.

Mirror printing starts perfectly. After power failure, if we resume, it heats up and then homes smoothly. After that it comes to the resume position and starts printing normally.

But as I mentioned above, I am unable understand the G10 for mirror. I have to give U-625.

"For Mirror Mode:
It was very strange that I got some odd values of U-625. (After did a lot of tests)
M563 P3 D0:1 H1:2 X0:3 F0:2 X3 S"Mirror" ; tool 3 uses both extruders and hot end heaters, maps X to both X and U, and uses both print cooling fans
G10 P3 X125 Y0 U-625 S0 R0 ; set tool offsets and temperatures for tool 3

@selva_tvi I think the problem is that you are trying to send tool 1 below Z0. The left tool, which I assume is Tool 0, has G10 P0 Z0. When applying offsets:

Tool offsets are given as the offset of the nozzle relative to the print head reference point, so the signs are opposite to what you might expect because tool offsets are subtracted from the required printing locations during printing.

You are using Tool 0 nozzle tip as your 'print head reference point', with Z0 at the tip, but you need to go -0.3 below this for Tool1, which takes it below Z0. I think there are a couple of options:

Set M208 to allow for some negative Z movement, or Set Tool 0 to G10 P0 Z-0.3, and adjust the Z probe trigger height/homing height, and set Tool 1 to G10 P1 Z0

See also https://docs.duet3d.com/User_manual/Tuning/Defining_tool_and_Z_probe_offsets for a better explanation of using tool offsets.

Realistically if you are printing in duplicate and mirror mode, you will achieve better results by getting both nozzle to the same height.

Ian

@selva_tvi said in Filament Monitor Disbaled for First layer only:

@OwenD said in Filament Monitor Disbaled for First layer only:

start.g will be run once before the print starts so it makes sense to disable your filament sensors there.

I disabled daemon.g and kept the below contents in start.g

if job.layer = 1 & state.status = "processing"
M591 D0 S0
M591 D1 S0
else
M591 D0 S1
M591 D1 S1

But it didnt work. Even at layer 1, it was enabled only.

Any change to be made?

start.g is run before printing starts, so the layer number will be zero
Therefore your code would enable the sensor as the layer does not equal one.
In start.g just disable the sensors without any if conditions.
If you use the slicer layer change code I gave then it puts the enabling commands in the print gcode.
Otherwise use daemon.g to do the enabling if you can't use the slicer layer change section

To help trace it down you can add M117 message commands between the lines in your homeall and slicer start gcode to see where it's getting thrown. That may help narrow it down.

@selva_tvi have you looked at the manual for the driver?

10. Software Configuration The CS-D508 is designed for simple setup and implementation. For most applications no software configuration or tuning is needed especially when driving Leadshine stepper motors with encoders (see Appendix A). If you want to define tuning or custom configurations such as micro-step, current percentage change…, you can use Leadshine’s freeProTuner software to make

You can't use RRF to change anything, you have to hook the driver up to a PC. All RRF does is tell the driver when to move, by how much and in which direction

@selva_tvi I remember vaguely, I'd set bed limits differently for my two tools. But that only works, when one tool is parked.
Both tools working simultaneously is a different story.

Well I was suggesting that you place the switch such that if the bltouch fails and the z axis continues to move the switch would trigger before the nozzle hits the bed.

@jay_s_uk I always respect your support. As mentioned that you have supported me lot of times. I know that.

Sorry, that my words have hurt you. My apologies for that.

I know that you are supporting from outside, not from Duet Team.

@Phaedrux Thanks for the support.

The below issue came up repeatedly.
'M997: File DuetWiFiServer.bin not found'

Then we read another topic in which it is suggested to use 'M21 to remount the SD card'.

After that, it updated the firmware. Now it is connected to the Wifi

@selva_tvi 1000ppr is fairly standard. The Duet3D EXP1HCL driver can get 4000 cpr out of them, although the accuracy of the intermediate steps is reduced. I can't vouch for the StepperOnline driver because I have no experience of it. If you read the manuals, they may say whether or not you can set the steps/rev to 2x or 4x the cpr.

@dc42 said in Step Servo motors on Duet 3 boards:

Duet 3 MB6XD

Thanks for the reply. Will start working on that

@phaedrux ok. understood. But I just wanted to hear from the experienced users of IDEX. How the power failure resume happens?