@peirof in general you can't use inputs as outputs on Duets because of the protection circuitry. On the Duet 3 MB6HC you can use IO_OUT ports as inputs, but not on the Duet 3 Mini.

@akayoshi you're still on firmware 3.1.1
I highly recommend updating to 3.3.0 and seeing if your problem is sorted

@giostark it was on a aluminum heatsink , it was never hot either has well when i checked it , it was just a cheap bad quality ssr

@philn said in Expanding Duet 2 Wifi with a 6th stepper driver for Triple-Z:

Can I use the 5 on-board drivers for Z-Z-Z+X+Y and use the additional 6th driver for the extruder?

Yes that makes sense.

@philn said in Expanding Duet 2 Wifi with a 6th stepper driver for Triple-Z:

Can I use a TMC2209 as the extruder driver or would you recommend another type, say 2100 or even DRV8825? (I got TMC2209 and a DRV at hand, so would make it simpler)

You can use whichever external driver you wish provided it will interface with your adapter board and will accept a step/dir/enable signal.

This guide may help

https://duet3d.dozuki.com/Guide/Connecting+External+Drivers/22

@wapuraralf Being that this is such an old thread you may have better luck posting some more targeted specific questions as a new thread and we can help you along.

@donstauffer

Yeah i've ditched bloatware slicer long ago lol. That post in the S3D forum is also me 😅

@dc42 Thanks brother!!

@dc42

I have this

; Tools M563 P0 D0 H1

@deckingman said in How to obtain Microstepping:

BMG style extruder

Thank you for the detailed explanation;
Here is some of the details x,y,z: 200,130,150mm
Motors: Nema 17; https://www.amazon.ca/gp/product/B07MDY5RX7/ref=ppx_yo_dt_b_asin_title_o05_s00?ie=UTF8&psc=1
Board: Duet 2 Wifi
Power Supply: 600W, 24 V: https://www.amazon.ca/gp/product/B00DEDB2U2/ref=ppx_yo_dt_b_asin_title_o08_s01?ie=UTF8&psc=1
Heatedbed:
https://www.amazon.ca/gp/product/B07MR59G18/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1

Pleas let me know if you need any other details.

@bubblevisor said in Tool Length Switch:

I want the firmware to ignore any PINDA probe readings for Z offset.

Well the heightmap is created with the probe, so it's a list of values showing the relative difference in height compared to the z0 point established by that probe. As long as your probe Z0 point and the switch Z0 point agree, you don't have an issue. Does that make sense?

@bubblevisor said in Tool Length Switch:

I have now changed the way I home Z using only the tool switch. I am also defining the two sensors via M558 K command. Seems to be working....

If it's working, that's the important thing. Can you also share your homing files?

@ppaukstelis unfortunately there are some commands that must be executed or remembered even when skipping an object, such as tool changes and fan speed settings. Also, I don't think it is guaranteed that after the slicer signals the start of a new object, the first move will be a travel move. Therefore RRF interprets many of the skipped commands and tracks the head position through those commands.

If it was guaranteed that the slicer always started a new object with a travel move, then RRF would not need to track the head position, which would make skipping moves faster.

Alternatively, if the pause while skipping an object is not of itself a problem, but nozzle oozing during the pause is, then we could execute a macro when switching from a printing to a cancelled object, and another when switching back to a printing object. In those macros you cold move the print head to the edge of the build plate, and clean/re-prime the nozzle.

@carlosr it's standard behaviour that after a tool change, all coordinates get restored to the position immediately prior to the tool change. This is because we can't assume that the slicer will send a command to travel to the correct coordinates for all axes after it commands a tool change.

The way it does this is to save the position in restore point 2 at the start of the tool change, and restore the position to the contents of restore point 2 at the end. So you could modify the behaviour by using G60 within your tool change files to change the coordinates stored in restore point 2.

@philipp-r - thanks i will look into this when i get a chance!

@peirof a PT1000 measures as 1000 ohm at 0 degrees. A thermistor typically measures 100000 ohm at 0 degrees

@chrishamm said in How to configure a Mini5+2 in the RRF Configurator?:

this change is rather tricky

Hi @chrishamm, I wonder if it is tricky because the +2 board uses driver numbering of the main board (0.5, 0.6) rather than having its own numbering (1.0, 1.1, etc)?

In this case, maybe it can be modeled as a feature of the Mini5P that can be turned on/off. Or, defining two versions of the mini board, with and without the +2. Just thinking loud.

Thanks @phaedrux. IO0 does work. I guess I should have read the previous posts here more carefully.

@zapta said in How to power the Mini5P from external 5V (no SBC)?:

(40A@110VAC

That's like 4500 watts... If I had something hooked up that could draw 40amps over a 110 line I'd be worried about fire too... and 80@220??? you sure you're not arc welding instead of 3d printing?

@phaedrux, thanks!

The M563 F2 was indeed the problem. I missed that because I haven't actually hooked up a part cooling fan yet....

@pickett Ive got it working under Armbian and Ubunto both being Debian based the Duet packages are easy to install. Had a little issue with finding the right GPIO ready pin unnder the SBC I was using. Odriod C4 rather than a Pi.

https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Duet_Software_Framework_on_Raspberry_Pi

Has the section for setting up the package repo that will work on any Debian based distros.

I haven't tried compiling from source. I can see the top level at https://github.com/Duet3D but not sure what all you;d need to build for a working SBC.