for future reference, the SSR need more Ma than the IO could provide, I run them now on OUT ports with 0 issues.

@cj19944 it would be helpful to post a copy of the gcode file with the issue along with the firmware version you are running so the stalling can be investigated

Hi, little late but could this be an option for linear motor ?
https://github.com/TkkrLab/LinearMotor
Br
Micael

@jay_s_uk @Hardware_SortingRobotics Yes, this catches me out, too! Pin 3 of the temp_db header is the first numbered spi.cs pin, and on all Duets it is spi.cs1 except the 6HC and 3HC, where it is spi.cs0.

Most of the documentation treats the 6XD as being similar to the 6HC, but in this respect they are different. I'll check and update the documentation for the temperature daughterboards. I've recently gone through this for the accelerometer documentation; I forgot to check the temperature daughterboards section. Apologies for the documentation inaccuracy!

Ian

The 6XD may be the best option for external drivers.

The mini5+ may be best for the normal stepper drivers and you can add a 1XD board for each external stepper

https://docs.duet3d.com/en/Duet3D_hardware/Hardware_overview

@dc42 Gah! I saw those holes in the 6XD board by the drivers and was wondering what one would mount there. I don't know how I didn't put two and two together. Well, there may be a daughterboard version coming in the near future!

This is what it looks like on the milling machine diagram 7aa2ef95-edb5-4b59-984c-41d9593daa4d-image.png

@Herve_Smith said in Duet 3 Mini 5+ no 24v on OUT 1 2 5 6:

@SpeedyDad said in Duet 3 Mini 5+ no 24v on OUT 1 2 5 6:

@Herve_Smith said in Duet 3 Mini 5+ no 24v on OUT 1 2 5 6:

@SpeedyDad said in Duet 3 Mini 5+ no 24v on OUT 1 2 5 6:

OK, sorry for being a noob but how do I "switch" the negative pin on? I've looked through the documentation but must have missed it.

I tried the M950 followed by the M106 but get "Error: Pin 'out5' is not free"

looks like you are attempting to control a fan, if so This documentation should help you

Yes, I know that. That's where I got the info to use M950 and M106 as stated above

then please show the EXACT code you have created from reading that so we can see what you have done.

Pretty much copy/pasted the lines from the connecting a fan page and substituted my fan number and the pin number.

M950 F2 C"out5" Q500 ; create fan 0 on pin out3 and set its frequency
M106 P2 S0 H-1 ; set fan 0 value. Thermostatic control is turned off

@droftarts said in Duet 3 Mini 5+ Dual Z homing not working:

@SpeedyDad

Both on the "out" pin and GND pin. I had them on the "in" pin first but that made the machine think they were homed before trying.

You can use the ‘out’ pin as an input, but be aware that they are only 3.3V tolerant, ie if you short the endstop to higher voltage (entirely possible), you’ll destroy the main processor on the board! Better to use the ‘in’ pins, which are 30V tolerant. If they were marked as already homed, add a '! to the pin name to invert the logic. Though this means your endstops are NO, not NC.

Oh,, and I'm also getting "Error: bad drive number" noted in console. Related?

Probably because you have commented out the extruder drive in M584, but it still has a drive in the tool definition, M563.

Ian

Ah. Thanks for all that. I'll switch the pins and comment out the extruder.

@dc42 Great, thanks for the clarification!

@Hardware_SortingRobotics Note that only out7/out8 switch to GND. V_OUTLCX is always high (+12V). If you have an extra GND connection between your SSRs and V_OUTLCX, the SSRs may be switched on all the time.

Update: the issue has been resolved for now!

It was indeed a power issue, and I figured out what was causing it. I had my 5V hotend fan and 5V tool fan both connected to the toolboard, but they were sharing the 5V input from io_2, since I couldn't get 5V from out1 or out2. Since the part fan turns on after the first couple of layers, I guess it pulled too much current from io2 and caused the toolboard to power cycle. I moved the fan inputs to take 5V from the expansion board instead, and now everything works as intended.

Thanks to everyone who helped!

@droftarts ha ha I was just about to try that when I saw @chrishamm has posted an update 🙂 cheers @droftarts

@ReVeRb I'm glad it's working. To mark as solved, click the Topic Tools button and select Ask As Question. Then click it again and select Mark As Solved.

@Phaedrux Thanks, it seems to solve my issue!

@djthuma Bed heaters are happy to generate heat from AC power, allowing you to use a smaller, cheaper, quieter 24V supply for the rest of the printer. Power to a line-powered bed heater is switched using an SSR connected to the heater pins on the Duet board.

If you already have the 24V heater and power supply, insulating the underside of the bed may allow the low powered heater to eventually get it up to print temperature, but will also extend its cool-down time.

@Thorpydo many flat RJ11 cables are crossover cables. This doesn't matter for telephone or broadband use, but it does matter for CAN. So you should check that there is no overall crossover between each pair of boards.

@droftarts @Phaedrux Thank you, this fixed the issue. For anyone coming here in the future, you will also need to change the z probe point in homez and homeall, and mesh probing will start in a different corner unless changed.

@gcorthey As @dc42 said:

configure the extruder motor as both an extruder and an extra axis, so that you can command it like an axis with an endstop

eg

M584 X0 Y1 Z2 U3 E3 P3

This defines driver 3 as an axis (U) and as an extruder. You need to add values for U to M350, M92 M566, M203, M201 and M906. Probably best to copy the values for the U axis from the E axis. Add an M574 line for the endstop on the U axis, eg M574 U1 S1 P"io5.in" to config.g

When you need to use the U axis, send M584 P4 to show the U axis, home it, then hide it again with M584 P3.

It is probably better to start a new thread than resurrect a thread that is over 2 years old!

Ian

@oozeBot Thanks for the suggestion. That's a nice little adapter but would not have helped in this case. I will have to remember it for the future though. I have my problems solved now. It was all a matter of space available on that side of the board. The issue was that the side of the housing that the RJ11 is on only had about 5mm of space to the side of another housing next to it. I wasn't able to make the mainboard housing any smaller but was able to redesign and print the the second housing so it left more room available.