Topics created by DocTrucker

@DocTrucker Polycarbonate has good flame retardancy (V-0 and better IIRC) but easy to print grades are often heavily adulterated so you would need to check their data sheets to make sure you're getting what you want.

If it's for a regulated use you should get your parts tested to make sure the part is up to requirement. I say this because some filament manufacturers in the past have used pellet manufacturer's data rather than test actual printed coupons.

@DocTrucker said in Powering 12V_EXT on Duet3 1.01:

@droftarts cheers. Missunderstood your first message as 2A limit when using 12V derived from VIN, rather than 2A limit per output when the jumpers are set to feed V_IN to the outs.

That said I'm surprised the selector-jumpers itself doesn't limit the current more than it aparrently does.

Hmm... actually, I think you are correct, as the selector pins are Molex KK too. Molex KK has a current limit of 2.5A (see the 'product specification' links on this page), and that applies to the voltage selector as well as the actual fan pins. Jumpers are rated at around the same https://www.farnell.com/datasheets/2706775.pdf. So the limit per bank is 2A (to be on the safe side), though if you are supplying power separately, and just using the MOSFET on the GND side, 2A is fine for the header. Also, the MOSFET DMT6018LDR appears to be rated for 8.8A: https://www.diodes.com/part/view/DMT6018LDR

I'll check with the others, and will likely update the documentation.

Edit: we use Wurth pin headers, which are rated at 3A, as are the jumpers, so maximum total current for each group of fans fed from a voltage selector is 3A.

Ian

@droftarts cheers. I'll have a look through that and consider the beta if it's fixed it. I'll need to check out how to force the non-release version onto a SBC setup.

@DocTrucker To elaborate a bit more, in Prusa Slicer, in the custom code section for filaments I have just one macro call - e.g M98 P"prePrintAbs". That macro sets things like retraction, pressure advance, speeds, etc and it resides in the .sys folder. So each machine has it's own .sys folder and therefore it's own "prePrintAbs" macro. So any gcode file becomes machine agnostic and by editing the single macro call at the beginning of the file it becomes filament agnostic too.

@DocTrucker superslicer and orca still use the old M109 commands etc

@DocTrucker That's what I meant with jerky motion. You can use bigger steps than 5 microseconds for more speed, but too much and they get jerky.

@DocTrucker Unfortunately, DWC layout is not user-configurable... yet. You can also use https://github.com/MintyTrebor/BtnCmd/ for custom layouts. I'm not sure if it lets you show the temperature chart, or move the three main dashboard panels.

Ian

@DocTrucker said in "sudo apt dist-upgrade" Doesn't update main board?:

@jay_s_uk that got it, thanks.

Can someone update the documentation to add a note relating to this to step 6?

https://docs.duet3d.com/User_manual/Machine_configuration/SBC_setup

@droftarts Not a bad idea?

@dc42 are there any potential issues if the 24V is on the board before the 5V? Should the SBC Duet systems boot order be: Screen, Raspberry Pi, then Duet?

@droftarts I maybe moving it off the SD card in the near future. I don't believe the RPi's treat SD cards differently to any other storage. I think it means if you run gcode outside of a build/print process the endstops don't work? Perhaps macros are in a bit of no-mans land there?!

@dc42 Raise3D Pro2

@DocTrucker no negatives i can think of

Just confirming endstops work fine on 3.3V. I've wired the fans to a 12V fan socket. All working so far...

@achrn it's a fair point. Any sort of user extras that get a bit too complex for conditional gcode maybe well served by plugins built to run on the Pi. I would have thought it was also less risky as you stand less chance of knackering safety critical stuff - unless of course you send the gcode to do so in error.

Has the duet firmware got to the stage where safety critical gcode instructions are locked mid process? Eg changing temp limits, PID settings etc?

@DocTrucker Sorry, don't know, I'm no Linux guru! How did you have it connected? Maybe both 'Power' and 'Touch' USB ports need to be connected to the RPi.

Ian

@Exerqtor https://github.com/supermerill/SuperSlicer/discussions/3902#discussioncomment-6883183

@dportero morning!

It is in my workshop and stripped of all the original control gear. I've planned what I intend to do, but not actioned it yet because I've had a few paid jobs bunch up.

The screen fits in the old holder with a few mods. I'll mount the Duet3 (doesn't have to be a 3, the motors are low current) on the removable flat panel undervthe machine. I'll likely need to print some cooling ducts to ensure the duet is happy, but other than that I think the biggest mystery will bevthe vslues if the thermistors. I have noticed that one company does upgrade hotends for the machine. That may be an expensive but reliable waybof doing it.

@droftarts Thanks, I had a glimpse at that and thought that looked very interesting. But having worked closely with folk responsible for servo drives from PLC systems I thought I'd try to do my homework with regards to setting up the sizing of the steppers for more than "has enough torque" before I looked at it - perhaps while I got used to one of the mini duet 3s.

Recolection is hazy but I think I chatted over email a fair bit with you while setting up my RepRapPro Ormerod 2 from RS Components around 2014. Didn't come to visit RepRapPro, but did attend a presentation at either Solid Freeform Fabrication Symposium in Texas, or a presentation at an inugural conterence that was run by loughborough by Adrian, but to be fair it was a few more years before I really understood open source. That would have been sometime between 2003 & 2006. A happy accident may have me returning to my roots tinkering with the software running metal laser pricessing machines after a ~10 year break!

@DocTrucker good to see you back