@reFlexlab I have some experience with these extruders. I would recommend swapping the motor out for a geared stepper (just to slow it down) and run it like a normal stepper motor in the system. There is a max allowable speed for these that must be adhered to.

@XZY3D

Reading your posts, I’d like to make some annotations.

Most electronic components can take at least up to 80°C, but at the cost of reduced lifetime. So, the cooler they run, the longer they last.

Components who have to control substantial currents like stepper drivers, MOSFETs for fans, heaters and the like, or voltage regulators tend to get hotter than other parts on the PCB. Without thorough tests and measurements, it is quite difficult to determine cooling requirements in advance.

Air flow is essential. If the heat of said components is not moved out of the way, it piles up and results in dangerous hot spots.

In contrast to common belief, most of the heat is dissipated through the back side of the Duets - mounting them flat down horizontally can be less than optimal.

If you intend to put your Duet into a pre-heated environment (say: a heated chamber), you must calculate this as an offset to the cooling requirements of the affected components. Even summer temperatures of more than 30°C may put a passively cooled board at risk.

At an ambient temperature of 60°C, the use of a fan is mandatory. In addition, you also should feed it with fresh air from the outside (to take 5. Into account).

If you are in the design process, you are good advised to provide a fan, anyway - if it turns out to not be required, you can turn it off. If you encounter hot spots, if you need to ramp-up the current for one of the steppers, or if the sun shines bright… well, you’ll be lucky to have a fan ready.

@p8blr What firmware versions are you using, is your mainboard and 1XD on v3.4.5? At maximum X speed you'd generate ~90k steps/s which should be just doable by the 1XD.

@p8blr Okay, thanks for that - it looks like something is wrong with the Duet. Please contact warranty@duet3d.com and CC your reseller with a link to this thread to arrange a replacement.

@dc42 said in 6HC - which temperature input uses which ADC bank?:

@deckingman on the 6HC, temp 0/1/2 are on one bank and temp3 is on the other.

Thanks David.

@jay_s_uk
Oh right, It's more easier.
I've done what you suggest and it work perfectly.
Thank you very much 👍

@dc42 it's printing at the minute, so I don't want to go poking around the wiring. I will take a good look at the wiring later, and if I find an obvious issue, I won't reply to this thread! The fact it is not expected behaviour at least points me in a good enough direction to continue debugging.

Thanks for the assist.

That sorted it - and it now works perfectly. Just had to invert the output.

My crimping tool mashed one of the cables, but not the other two. Shonkly cable, I guess.

@domzduzt I think you should start a new thread and give some more information.

@csoup50 Im printing again, its been two days. Thank you again!

@SetraX said in Duet2 - weak Z Axis:

Changed the belts to steel enforced belts...

Steel core belts are not recommended for the tight bend radius usually used in 3d printer drives. The steel cores will fatigue and break and the belts will then stretch.

Can you try removing and reinstalling the ribbon cable between the Duet and Duex?

@tas Thank you very much.

@CNCModeller said in Hardware advise....:

I was probably going to get to 4 1HCLs and magnetic encoders as I wanted to go "on axes" closed loop on X, Y, Z and a rotary axis.
I was going to use more stepper drivers for a tool changer, but was hoping to control that over CAN to make it easier to maintain and remove if necessary.

The Duet 3 Mini should handle the 4 axes via 1HCLs without difficulty. Any additional stepper drivers for a tool changer would only be used occasionally, so they wouldn't create much extra load whether you drive them directly or over CAN.

If you definitely don't want to drive any axes from the main board then the main board 6XD is another possibility. It has the same high-performance processor and dual CAN interfaces as the 6HC but it costs less, and it doesn't have the 48V VIN option nor the optional WiFi module.

@dc42

@dc42
hello ,

I'm also interested by this same topic.

So what is the easiest solution to integrate today one of these sensors on a 6HC board?

If i understand correctly "current-loop-pyro" was a special dev and it is not supported by 6HC unless why buy the special board.

What about sensors that give a 0-10V signal as output, using them with "linear analog" would work?

What about UART or even thermocouples output ones?

@dc42 even better!

@dc42 said in Problem with escape characters for password for Wi-Fi card.:

Try sending those commands from the console, but:

after the M552 I1 S0 command, wait for the "WiFi module started" message
change M558 "" to M588 S""
wait at least 10 seconds after the M588 command, it has to erase the flash file system
make sure that your terminal emulator doesn't change the straight double quotes to smart quotes

If you want to send them from a GCode file instead, you will need to add G4 delay commands after the M552 and the M588.

Thanks!

I got it to work. Just switched to a PC and dropped using serial tool on Mac and it all started to work.

Thanks for the G4. This will improve the code.

@Zito2485 connect the filament monitor to the toolboard.

@Nxt-1 Thats comforting. That is about the length my wiring is from board/supply to effector. Right now I am just dealing with a strange height map that I cannot diagnose after literally tearing apart my printer and reseating every bolt but thats for another post. I cannot state enough how much I appreciate you guys helping everyone out here. Thank you!

@Schickfus I have not run into this issue but I remember another discussion about this on the forum in the past, can't find it right now.

Personally, if its an emergency and you hit the emergency stop, cutting power, then having the recover requiring rehoming would be acceptable in my view however that may not be the same in your case.

Once you have reconfigured the 1XDs you can send the positions of the axes using G92. the approach of using a trigger to indicate the estop has been pressed, and then either prompting the user to clear the fault and then reset the estop, then running through the reconfiguration of the 1XDs and restoring position should work.