@Lexan said in Filament Runout Event:

if !exists(global.filamentDistance)
global filamentDistance = <- is here missing a point after global ?

Another possibility is that daemon.g is starting before the tools & monitors are defined

In your config.g put in a global to stop the daemon code executing
This will also help when you need to edit daemon.g
So at the start of config.g

if !exists(global.runDaemon) global runDaemon = false else set global.runDaemon = false

Then at the start of daemon.g put

while true if global.runDaemon = false M99 ;rest of code

Edit
Forgot to say, at the end of config.g put

set global.runDaemon=true

You will have to rename daemon.g before you can edit and save it, then rename it back again

@achrn said in Rotary axis/spinny thing with no limits:

I think motor steps are in a signed 32 bit variable

Correct (that's motor microsteps, not full steps). Bear in mind that absolute positions are stored as 32-bit floating point numbers, so accuracy will suffer when the number of microsteps doesn't fit in about 24 bits.

@Thalios If it happens again, send M122 after it has skipped steps. This may capture information on the skipping that we can analyse.

Ian

@dc42 said in HSS57 External Driver Controlled by 1XD Exentsion Board:

@Lexan said in HSS57 External Driver Controlled by 1XD Exentsion Board:

@dc42 at the moment i use all 6 wires one by one from the 1xd to the signal port.
so i keep the rest the orientation from pull and dir + to + and - to -. just ena i change + to -.
i understand this correctly ?

Yes, just swap the ENA+ and ENA- connections over.

This was the Solution, Thank You !

@Phaedrux thank you, I got it working I replace the SD card.

@Feynman137 said in Cannot get driver to install on Windows 10:

Great, glad you got it working.

the guides are actually the same so is the link.

I know, I wrote both! The Dozuki wiki is the old wiki and hasn’t been updated for over a year. Use the new wiki.

Ian

@Flynbrd
I have no reference point as you only posted one set of commands, but as long as you have the right driver number (usually 3) then yes.

@droftarts Done!! Thaks a lot!!

@droftarts Thank you both for clarifying. It makes a whole lot more sense now.

@dc42 thanks for confirming, the 3 screw conversion I installed is in the alpha stage so the documentation is a bit sparse

@Dad003 said in Next iteration of gantry.:

Any thing him missing or should be aware of ?

My CoreXY is also supported by a carbon tube. I'm pretty happy with it. Make sure you pick a decent diameter tube and let one side float.
I did that by designing two different carriers, one side clamps the rod, the other is wider to take a 1mm thick PTFE tube, so the rod can slide to compensate thermal expansion.

@dc42

Thank you!

@joefnh said in Getting Started with a Duet Mainboard 6HC:

(rev 1.0 firmware) a raspberry Pi (ver 3.x) and the included 3dDuet rectangular touchscreen

Version 1.0 firmware and an included touchscreen sounds strange. Where was this board purchased from?

@Phaedrux

Correct, it has been a standstill for 2 months due to shipping damage of my new (600x600) magnetic PEI surface from China but got issue solved by Paypal.

Forgot about B parameter I played with with the glass bed.

@dc42 I am breaking the mold a little since this will all end up in a microscope so any LEDs wont be visible anyway and I was hoping to find better encoders but the cnc pendant knobs are a little big. Outside of the cheap ones, it seems that just getting a rotary encoder that had over 400ppr was the next jump but thats a bit excessive for my needs. Maybe i'll regret it, we'll see how long it takes to get this experiment up and running. I really appreciate you filling in the gaps!

@dc42 said in Input Shaping On / Off Switch:

@CCS86 yes I thought of that too. Same problem: we would need to turn on IS a few moves before the perimeter starts. That may be possible if we use the second file reader in RRF3.5 to read a few lines ahead.

Yes. Ideal (if practical to implement) would be to look at the "distance to perimeter" as a trigger to enable IS, with this distance adjustable via IS definition call.

@dc42 Hi using lower current causes more than 1 axis to stall.

ive noticed if i press "emergency stop" in DWC it seems to stall more often, i thought "emergency stop" just runs "cancel.g" but does it do more in the background code .?

;cancel.g echo "Cancel.g " G1 E-2 F200 M98 P"/macros/home_max_Z" M84 ; home_max_Z echo "start home max Z" M122 M569 P0.4 ; Check status in console M569 P0.5 M569 P0.6 G91 ; relative positioning G1 H1 Z-5 F1000 M569 P0.4 S1 D3 V10 ; set to stelth chop M569 P0.5 S0 D3 V10 ; set to stelth chop M569 P0.6 S1 D3 V10 ; set to stelth chop M915 P0.4 S127 F0 R1 H500 ; Configure Z-Axis Stall Detection M915 P0.5 S127 F0 R1 H500 ; Configure Z-Axis Stall Detection M915 P0.6 S127 F0 R1 H500 ; Configure Z-Axis Stall Detection echo "stall detection setup" M17 Z ;energise a motor for stealthChop tuning G4 P400 ; pause to allow the drivers to characterise the motor G1 H1 Z-0.5 F3000 ; move a little for cal of sensorless homing / not stalled echo "after stall detection setup" M569 P0.4 ; Check status in console M569 P0.5 M569 P0.6 M915 P0.4 S10 F0 R1 H300 ; Configure Z-Axis Stall Detection M915 P0.5 S10 F0 R1 H300 ; Configure Z-Axis Stall Detection M915 P0.6 S10 F0 R1 H300 ; Configure Z-Axis Stall Detection echo "diag before stall detection setup" G4 P400 echo "lower motor current" M913 Z50 ; Lower motor current % M566 Z15.00 ;jerk M201 Z50.00 ; set accelerations (mm/s^2) G4 P150 ;wait time ms M574 Z2 S4 ; Configure Z-Axis stall detection homing ;M569 P0.4 ; Check status in console ;M569 P0.5 ; Check status in console ;M569 P0.6 ; Check status in console echo "home max z" G1 H1 Z350 F3000 ; Home Z-Axis actuators independently G92 Z300 ; set a Z height ;M569 P0.4 ; Check status in console ;M569 P0.5 ; Check status in console ;M569 P0.6 ; Check status in console G90 ; absolute positioning G4 P300 ;revert back echo "after revert back" M913 Z100 ; Reset motor current M569 P0.4 S1 D2 ; reset motors back to spread cycle, M569 P0.5 S0 D2 ; reset motors back to spread cycle, M569 P0.6 S1 D2 ; reset motors back to spread cycle, M915 P0.4 S45 F0 R1 H500 ; Configure Z-Axis Stall Detection M915 P0.5 S45 F0 R1 H500 ; Configure Z-Axis Stall Detection M915 P0.6 S45 F0 R1 H500 ; Configure Z-Axis Stall Detection ;M569 P0.4 ; Check status in console ;M569 P0.5 ; Check status in console ;M569 P0.6 ; Check status in console M84 ; turn off motors echo "The bed has landed"

@droftarts Damn. A bug. Bugger!

There is no config.bak file on the SD, and I do not recall if there ever was. There is one on each of my older Duet 2 wifi boards.

It is not possible that I uploaded a default config file, as the events were a shut-down during a print pause (due to a nozzle clog) on one day (I switched the power off, and then when I switched the power on the next day the Panel Due welcomed me to my 'new Duet'.

Here it the M115:
FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.4.4 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2022-10-20 16:18:28