For Europe this is an option for ordering the Mini 2+
https://www.dold-mechatronik.de/Duet-3-Expansion-Mini-2_1

Wonder why any operation with those varaibles results in an error

e.g. {job.filePosition / job.file.size}

i also tried ( same

any hints ?

i was expecting those to be Numerical Value

fwiw this is 3.3 RC3...

@droftarts @dc42

Configuration is :

• Rel 3.3 beta 2+2
• Forced SpreadCycle (D2)
• Mesh active

Still getting layer shifts
(see below at back after couple of layers)
I stopped the print - it produced a sound when that happened

Dumps:

• M569 report
• M122 report
• config.g

no it does not fix the issue

@dc42 good catch !

that might also be the issue behind slicer output .g files not completing the upload when the heater is turned on. They reach 100% but then start over again and again...
thanks

@MikeS the SPI appears to do not support interrupts, yes

@argo was not asking you... 3H+ and update was from 3.3Beta2+

@dc42 Duex ? Ribbon cable ? LOL

I'm on a Mini 5+ / 2+ ....
Actually the Third one as i had to replace them multiple times due to SD card soldering issues....

I'm saying i had no issue before....I install the fw after printer is completely cold at warm temperature
and those (nonsense) alarms came up..
and the steppers started clicking endless like everyting is going to break apart..

Take it or leave it...

TBH i really have enough of the attitudes of yours of all the time i ave spent around this hw and i pretend answers from yourself
not from experts popping up from nowere pretending to become Duet developers overnight (sorry no offence Argo...) i'm really fed up at this point

out

@dc42 ...it's becoming harder to...

I had posted numerous times in the other thread about layers shifts and mesh issues so i assumed you remembered the config i had, but i understand you deal with 100s issues at day...so sorry if my post was not sharp clear from start

Ok understand the explanation now
My intention was to just report factual and that the steppers really click bad and don't stop doing that...
Swtcing off - on appears to solve the issue.
Perhaps it may be worth to mention somewhere...as someone may think things are breaking apart (as i did...)

@gixxerfast said in Neopixel support on 1LC?:

Yep, that would be really great.
The new voron toolhead is coming soon with nozzle lights (and a bling lit logo.)

Would be nice to combine with the 1LC. I need only two max three leds.

Voron Design Stealthburner yet to be public

Yeah as Gixxer said this is the driver (it equips three RGBW discrete neopixel leds)

Also our Klipper "colleagues" (which always are some meters ahead....of us) already have a tool-board with that supported...
@dc42 Thanks for moving this forward and make it a Christmas gift

@gixxerfast said in PINDA leveling sensor:

@thedragonlord said in PINDA leveling sensor:

Volcano heatblock... could be an issue?

Let's see if we can ping one opinion at least @oc_geek What's your thought of the Vinda close to the hotend, OK?

From my short experience with that probe it needs a quite thermal environment for returning reliable reads (temp ~ constant) and i think it struggles above a certain temp too. In all honesty i stepped away from such a probe... and rather quickly
However i have Voron printer which has a closed / heated chamber and so on... so it might be different in your case.
Personally i do not like it and do not like the very short range of action either. I found alternatives based on microswitch (we call Klicky in Voron context) to be infinitely better...

@t3p3tony said in Connecting and reading a pulse generating encoder:

I have moved this to the firmware wishlist to further the discussion about how we might be able to support using filament monitors for no printing extrusion moves such as this.

Hi,
Is there any ETA for this feature being implemented any time soon ?
thanks

@t3p3tony
thanks guys !
would be great to see something like that supported in the fw

@pfn great work !
thanks for all what you did and are doing

@pfn yeah will have to check as you say

Option 1 is not possible as the "encoder wheel" is actually a metal Bondtech gear (as i wrote before below)

Option 2 seems to be the only practical possibility

Also the challenge will be to port the Klipper python module into RRF Marcos...

@pfn as i wrote this came from the Author of the unit itself... it's not that i need something..

The sensor is used ONLY when loading / unloading the chosen (between nine) filament to the tool to make sure it arrives where intended and does not jam the unit and so on...
I think they do that faster than a print feed rate to reduce the overall print time...(e.g. 1000 filament changes in a print would matter..)

that said i did not got any data point from the Duet team on which rates (Hz) are reachable using a trigger... or any other offered solution...

@dan1990 rightly said

in particular the part responsible for the Pulse Generating encoder is a Klipper module written in python

@cncmodeller
Yes i do get disconnects (like in the morning after night prints). See my opened posts on the topic...

mini-5-wifi-connection-unstable

duet-3-mini-5-connection-lost-and-files-missing-again

That said it is a lost battle to get any attention on that topic in here...
Earlier the HW was replaced under warranty (got 2 replacements..) lately it aint the case anymore... and you are left living with the erratic behavior

The best you get back is that your wifi network is unstable or your wifi router has flue... while i'm convinced the bug is in the FW..

@t3p3tony i saw that but it wont be possible to inquire the position nor to reset it (unless i'm reading it wrong)