@gloomyandy said in Inconsistent behavior:

@exerqtor I really don't know, it may be that the second time the filament change macro is run it knows what filament is installed and that makes it do something different. There is also stuff like the toolchange handling that may be slightly different the second time around (your end code deselects all of the tools). I'm just trying to find a way into understanding what the problem may be and identifying it as a problem with absolute/relative mode would at least move things forward a bit. Should be easy to test if you just create a very minimal test print file.

Slow reply with christmas and all what that brings. But I threw a G90 at the verry end of the custom filament gcode in SuperSlicer and it actually seems like it's working now. Still can't see any logical reason for why this should be needes though 🤔

Thanks @dc42, this is very useful. The new schematic after the changes is here https://github.com/zapta/duet_micro_tool/blob/main/kicad/duet_micro_tool.pdf

I still have a couple of questions if it's ok.

Do I need to pull up also the LIS2DH INT1 output?

I was not sure what unused pins to pull up so prepared this list https://github.com/zapta/duet_micro_tool/blob/main/kicad/TODO.txt , is it correct? Also, can I tie together all or groups of inputs to reduce the number of pull up resistors used?

Also, have you considered setting the inputs to have internal pull up/down by default? This may make the firmware more versatile for custom tool boards.

(I am yet to look at ATSAMC21E18A, my current thinking is to stay as close as possible to the Duet toolboard).

@stephen6309 I appreciate the response. I actually made a breakthrough forty minutes ago. A clean homing sequence with no motor grinding. X & Y went first, then Z.

Aloooot of research went into getting that result. I hope any future hurdles are easier to tackle.

I still have more things to test with the printer. But things are looking up now.

@falco22 said in Below 4°:

@deckingman I find a problem with that solution. It only works for 4 degrees. Is there any way to formulate the equation to fit any temperature between room temperature and 0C? Thank you.

I'm not an expert on conditional gcode so someone else might have a better answer. But do you mean if the temperature is within a range from (say) 20 to 0? In which case you could use something like

while {sensors.analog[1].lastReading >0} & {sensors.analog[1].lastReading <20}

or do you mean a fixed temperature but one that you can define? In which case you could use a global variable that you define elsewhere - e.g. in a separate macro or config.g.

so something like

global dispenserTemp = nn (where "nn" is the temperature value)

then the expression would become something like

while sensors.analog[1].lastReading > {global.dispenserTemp}.

But as I said, I'm not expert and may have got something wrong. Suggest you check out the documentation https://duet3d.dozuki.com/Wiki/GCode_Meta_Commands#main

@phaedrux Thanks again for that pointers. I'm going to have to investigate this in the new year now. I'll try commenting out the M574 commands from the config file and placing individual lines into each homing file. It sounds like I should also include M915 in the config file but sensorless homing individual axis has worked without it.

The only other thing I can imagine may be causing an issue is I have the following line in my config file...

M584 X0 Y1:4 Z2 V4 P3; Apply custom drive mapping, P3 hides V(Y2) axis. ***

and I should remove V4 from that as it's not needed. Thanks again, and hope you have a good xmas break. Savvas

PrusaSlicer 2.4.0 is out now! Out of Beta! So that means the -n8 version is out too!

b719b95c-1848-459b-9f0f-c608ef789d47-image.png

https://github.com/n8bot/PrusaSlicer/releases

@damster the maximum number of axes is now 15 on the Duet 3 MB6HC. You can use axis letters XYZUVWABCDabcdefghijkl. To use lowercase letters in GCode commands, prefix the letter with a single quite character, e.g.:

M584 'A2.0 'B2.1

I am using RRF 3.3 and the macro:

; Engage the toolchanger lock. RepRap Firmware V3.3RC3 version. G91 ; Set relative mode G1 U10 F5000 H0 ; Back off the limit switch with a small move G1 U200 F5000 H3 ; Perform up to one rotation looking for the torque limit switch Y0.5 ; H3 will modify axis limits they must be reset with M208 see below (use your axis limits) ;Pickup success detection | Aborts if no Tool picked up M400 ; Make sure moves are complete if {abs(move.axes[3].machinePosition) > 90 || abs(move.axes[3].machinePosition) < 20} ;if tool is not picked up | (Change 20 (half pickup) and 90 (no Pick up) to the value you need) echo move.axes[3].machinePosition ;debug output of the reached position M208 U0:201 ;restore axis limits (see above H3) set global.tool_change_Aborted = true ;send error condition M98 P"/macros/tool_change/tool_unlock.g" ; Unlock the tool G1 Y-20 ;back off M291 P"Werkzeug nicht richtig geladen. Ursache gefunden und behoben? Erneut versuchen!" R"Warnung Werkzeug nicht aufgenommen" S3 T-1 x1 Y1 U1 set global.tool_change_Aborted = false T{state.currentTool} if{job.duration != null} M25 ;pause job echo "Paused" else abort "Aborted" ;Behaviour after successful pick up echo "Picked up Tool",{state.currentTool} ;success message set global.tool_change_Aborted = false ;reset error condition M208 U0:201 ;restore axis limits (see above H3) G90 ; Set absolute mode

I will look into using M0 /M1 .

@nuramori Hello and thank you for your answer, it's possible to explain to me how you did it because if I understood correctly you have 3 axes, is that right?
And you have to talk about kelvin find you where this information please it is possible if you could help me to do the same as you to see if I get a good quality I am ready to do anything to find a solution to my problem.
Thank you to all of you for your help.👍😀

@oliof said in Advantages of Duet Mini + Rasperry Pi:

DWC responsiveness are improved. Th

thx

Use M119 to check the endstop state when triggered and untriggered.

Turns out one of the leads on my endstop came unplugged, should have known to check that.

The automatic checking of the endstop-states is an interesting idea. I'll see if I can implement it.

@fcwilt to answer your question, 3.4b6 fares well on my IDEX setup on a duet 3 mini 5+ with expansion board in standalone mode.

I've been holding off 3.4b7 because the new event system and changed behavior around heater faults, but mostly because I don't have the time to build my own macros to re-implement previous default behavior.

@t3p3tony Thanks Tony working for me now.

@zapta said in Adding a second strips of neo pixels?:

Thans @dc42 , I will give it a try. I presume I need to add a 5v level shifter for the secondary neopixel output I will use.

Yes, you will.

@andersb

Unfortunately that data sheet doesn't show torque vs. speed derating.

I would try @rjenkinsgb suggestions and see if that gets you where you need to be.

@eddygara said in Duet 3 heatsink fan not working with smart effector:

Configuration file for Duet 3 (firmware version 3)

The last config you posted still showed out5 used in two different places - that cannot work as intended.

This is the heat & fan section from my config for a delta with smart effector, using a Duet3 6HC board.

I have no problems with heaters or fans; the heatsink fan turns on at 45'C and the part fan runs as set by the slicer G code.

; Heaters M308 S0 P"temp0" Y"thermistor" A"Bed" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C ; M308 S1 P"temp1" Y"PT1000" A"Tool" ; configure sensor 1 as a PT1000 on pin temp1 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Fans ; Part cooling M950 F0 C"out4" Q500 ; create fan 0 on pin out5 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off ; ; Hotend heatsink M950 F1 C"out5" Q500 ; create fan 1 on pin out6 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on

The tool sensor type is different to yours and will need changing back to the 100K thermistor rather than the PT1000.

If you are still not sure, post a photo of the Duet board showing what's connected where??

@danzaywer I did it. Powered the board with adjustable power supply to see the current it draws. 0.18A at idle and 1.80A when hotend is on.
Ac outlet 230volt stable. PSU output 24.2volt stable. Board power input connector 24.0 v stable.

@percar It is in a PiD mode. I'm using two PSU. The 24V psu is for the board, 12V psu is for leds and 12v fans around enclosure. Filament spool made by a turntable. It is a free spinning bearing.

@rjenkinsgb I understood what you mean. I tried it. Nothing seem works really right now.

I don't know if this macro shows a layer height change or over extruded layer? I think layer height is different than others.
Anyway I'm tired. Don't shut off the heater bed and problem is solved.

WhatsApp Image 2021-12-18 at 17.31.48.jpeg

@phaedrux
Know ok
Thank you again for helping me

I performed temp tests using known resistors and the Duet itself seems to give very close results for one of the two Semitec 100K thermistor models so I presume this is the one that E3D sells. This validates the Duet's recommended configuration for the E3D thermistor. It says nothing though about the specific thermistor I am using.

For example, 210.4 ohms gave 239.9C where the expected value is 240C.

b91fc00c-0c59-4a31-a94b-ee64c4d9ee47-image.png

7991d78c-d4c7-4296-9869-993fab4bad99-image.png