Thanks for the info.

All the hardware-PWM-capable output pins are assigned to heaters and fans. Currently you can't reassign the heater pins without recompiling the firmware, because the associated PIDs are liable to overwrite anything you write to them. I intend to introduce an M code that would let you specify now many heaters you have, thereby allowing the remaining heater pins to be used as GPIO pins.

The Duet WiFi expansion boards we are working on will also provide additional PWM channels.

I will report on that. It definetly doesn't like nozzle crashing into it.
I upped the temperature with edge filament to 240°C and I am doing a print tonight first layer adhesion is actually better ( I used too low temperatures due to some wrong indication on the e3d sticker spool box and also because I was lacking experience)
I still get a lot of goo around the nozzle which I need to babysit clean every 5-10 layer or so… I wonder what is wrong in my slicer settings. The ngen (colorfab) didn't do that.
problem with the goo is that it detaches and hardens always at the worst place and then you get a nozzle crash...

Ahh, blind as a bat..
Firmware 1.15c, webinterface HTML: 1.11, JS: 1.11
Ok updating to 1.12 then…

We have several users wanting to drive dimmable RGB LEDs, which is why we are looking to support additional PWM channels on the DueX5.

Yes that silk screen is the wrong way round.

ah, M569 has moved to M584 and can now map more than one drive to an axis. Pays to read the wiki properly. My bad.

Hi all!
So, I had the right idea how the axis should work, and after the 7:th combination and switched x & y motor connections I finally found the right settings!
Thank you so much for your patience and great answers to me who´s just starting to understand the in´s & out´s of Duet and reprapfirmware!
Best regards
Per

Perfect, working fine thanks

Thank you so much Chrishamm for a beginners question, starting to understand the firmware.
Happy weekend!
Per

These sounds much nicer. Are there any pictures of these by chance?

@peridot:

I'm still not clear about whether RepRapFirmware can turn the stepper motors off when they've been idle for long enough; in fact I'd prefer the firmware to automatically turn the ATX supply off and on when needed, but I realize that "when needed" is a little complicated given that steppers lose microsteps when powered down and hotends can jam if the heatsink is not cooled when it needs it. So for the moment I have G-code to cool the hot end and then shut down ATX power at the end of a successful print; cancelled prints require the user to shut down by hand.

By default, RRF reduces motor current to 30% of normal when all motors have been idle for 30 seconds. The percentage and the timeout can be adjusted using the M906 command.

You can write a macro file to cool the hot end down and then turn the ATX PSU off.

In a future version of RRF, I intend to add the facility to move all motors slightly to a position that corresponds to how they will power up again. That should reduce the risk of the motors jumping steps when you power off and on.

Ah OK. Now it's making sense. Guess I'll have to try and not do anything stupid until you get around to doing the next firmware release. Thanks for the help.

Thanks!!

Some people swear by it (sandblasted glass that is) I'll let you know how I get on. I haven't tried printing on plain glass - it's just that the instructions for my original RRP Mendel recommended Kapton tape and I've become fairly proficient at fitting it, so I've carried on. That's with a 200mm square bed and as the new one is 400mm square, I think I'll need to do something different.

I tried your probe with ground side up and ground side down. The trigger height is different but it works OK for me. Maybe it's the extra thickness (mine is 6mm)??

https://duet3d.com/wiki/Pre-production_hardware_limitations_and_known_firmware_issues

This page, as well as a few other places on the forum/Wiki.

Some suggestions:

1. Switch the bed back to bang-bang control, using the B1 parameter in the M307 command.

2. Try connecting the LED strip directly to your power supply instead of to VIN. That avoids the resistance of the leads from the PSU to the Duet causing voltage drop at the Duet when the bed heater turns on.

3. Use a better-regulated power supply (probably in conjunction with (2) above).

4. If your 12V PSU has sufficient extra power capacity. turn up its voltage to 14V, then use a 12V low dropout regulator to provide a better-regulated 12V supply for the LEDs.

5. Use a separate PSU for the LEDs, or a separate PSU for the bed heater.

6. In a future firmware revision I may make the bed heater PWM configurable, then you will be able to turn it up to 70Hz or greater, high enough for the eye not to see.

As others have said, running two "normal" fans from the same PWM fan channel is fine.

The FET user is the PMV40UN2R is rated to ~4A, however that should be derated significantly to take into account the PWM switching losses and to reduce the max temp the FET gets to so 1A should be safe. Given that most fans that would be used for this are <0.2A your configuration should be fine.

Thank you Tony, I knew something didn't feel right about my numbers! Let's hope I can squeak more than 55% efficiency out of that board..

The LattePanda is definitely interesting - I have not yet played with one, the Kickstarter reviews are so-so, so we'll see how it turns out. I do plan on printing a case for a 7 inch LCD/touchscreen. If the dimensions work out correctly I will mount that and the PanelDue drawer style under the printer and be able to slide them out when needed.. more often than not I'm sure with will be accessing the Windows side of the Panda via RDP if it's powerful enough to run simplify.

Done:

https://github.com/T3P3/Duet/blob/master/DuetWifiv1.0/DuetWifi_Schematic.pdf

For KiCAD you need to use at least version 4.0.2. The custom parts are in the distribution on Github, you might need to point your libraries path at that, I thought it was relative within the project but maybe its not.

edit: added a page to the wiki that links to the source files:
https://duet3d.com/wiki/Source_Files