Posts made by DocTrucker

@Tricep-terry I'm guessing that work may have been to support people that are bulk buying boards for machines they are selling commercially. If the customers (rather than duet) funded the work they may not have wanted to share it. That said, They may just have their hands full!

@Tricep-terry likely stating the obvious but a CE marked board won't make the whole machine CE marked. As a community the best we could do for home brewed machines is to provide example risk assessment and mitigation documents and user manuals which can be adapted by others to suit their machines. This would result in a set of documentation that demonstrates due diligence on making a custom made machine safe for use by employees, but it would still be significant work, and only worth the MBs of storage it is written on if effort is put in.

I've got a small business spec machine that I'm now rebuilding. That could be the start of example docs if they haven't happened already in the long periods of my abscence from this forum!

Edit: I believe the best duet3D could provide with the board is a certificate of incorporation.

@Phaedrux Parsing gcode files to use M201.1 or M204 would help control acceleration on the fly. Not sure why they'd want to change max speed on the fly rather than just use feed rates?

As for variable jerk/instant speed on the fly I'm not sure there is a way to deal with this with the current gcode library?

As there are already slicers in the wild using these gcodes badly perhaps it may be easier to have new gcodes for use in config files that can't be overriden in build files?

Edit: Whats the market share of Duet equipped/reprapfirmware compatible machines like vs Prusa compatible systems now?

Thanks for the comments all. I'll take a better look on Monday, little one got turfed out of nursery with a temp. Nothing serious.

As a side note I am doing what I can to manage fire safety in the usual ways too. My larger system will have relay isolation of the heaters and separate isolation of the fans and other 24DC devices such as the steppers. Latter mostly so I can power up the machine for setup and simulation tasks without the fans running flat out! Most wires will be sized so that a fault current of up to the fuse rating would not cause the wires rating to be exceeded. Some degree of diagnostic coverage on the isolation circuits will be there if I have spare inputs on the Duet, but it is wired so that if there was a fault on the fan PSU it would take out the heater isolation.

A lot of my printers have PLA and PETG near high current (heat bed, 600W PSU, etc) supplies or devices.

In industry these devices may be subjected to glow wire testing to gain reasonable confidence that components near the wiring would have minimal contribution to a fire caused by a fault. From what I understand this is an attempt to prevent a fire taking hold should a component fail catastrophically (e.g. DC motors often die smokey deaths) and reducing the tendancy of a fire to spread through means such as dripping plastic.

So, what printable materials have good flame resistance, and would be likely to pass glow wire tests if they were subjected to them?

Glow wire testing:
https://www.te.com/content/dam/te-com/documents/appliances/global/glow-wire-testing-appliance-industry-white-paper.pdf

It also may be worth checking out "M567: Set tool mix ratios".

https://docs.duet3d.com/en/User_manual/Reference/Gcodes

Does look like there is a Gates Carbon/Volt antistatic range. Guess you have to brush a rotary part at some point to to reliably ground the rotating components. Not looked in to it propoperly yet as you can tell!

@tjhinton is there continuity between the stepper body and ground? Is the negative pole of the printers power supply tied to a mains electricity protective earth?

You mentioned static on the belt as a suspected cause. I will check my steppers to see if there is continuity between the axle and the stepper body. Antistatic belts are probably available if the gates belts aren't already so, although I do note you did check for charge build up.

@India if you want this behaviour on all builds ran on this specific machine add it to your config file. You could also add it to the custom gcode your chosen slicer puts at the beginning of a build file.

Read through the detail for M669 here:

https://docs.duet3d.com/en/User_manual/Reference/Gcodes

@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.

@droftarts it's the full fat main Duet3 board with the steppers on board. Revision 1.01. The docs say 800mA draw when using the onboard 12V supply, but it doesn't say what the individual MOSFETs are rated too if I feed the 12V side of the devices being switched from an external source. I can't see the part codes for the MOSFETs. I think the Q references are simple the components ID on the board rather than it's manufacturer part code.

Morning All.

The advice for the 12V rail on the Duet3 is 800mA and "small fans". The fans on the Raise3D Pro2 dual head seem to be fine for that. Two small part cooling fans and a larger fan (all axial) for the heat break coolers.

The issue is I also have an LED strip for part bed illumination and a larger (rated 400mA, main case diameter ~70mm and ~20mm wide) radial blower that I'm repurposing to blow air under the main board. I think I may be pushing my luck on the 800mA guide.

I had thought about feeding 12V to the permanent fan connector but not sure how current draw would be ballanced between the onboard and external regulator. The former is diode protected against reverse current but if supplying marginally higher voltage it could end up supplying all the current anyway.

Plan b is just to feed the posative legs of the fans from the external source and sink through the board. The MOSFETs on the curcuit diagram are labelled Q25A/Q25B. I couldn't find a spec sheet on these. What is their safe continuous - rather than peak - current draw?

@o_lampe Good spot. Can't see the wood for the trees after a while.

I'll be using whatever the previous F setting was. The other issue that will be choking speed a bit is it will be looking to come to a full stop before executing each change of PWM.

Hello.

Currently in 3.4.6 (Installed by sudo apt-get upgrade/sudo apt-get dist-upgrade on SBC & Duet 3 setup) state.gpOut[].pwm returns a value equal to the original setting divided by 20000. It hat how it will remain? Is the divisor board dependant? Is there a more reliable way to recover the current PWM setting of a port?

Thanks!

@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.

I've spotted a non ideal behaviour with 3.4.6. Before I put much time into seeing ifnit is repeatable what is the best way of finding out if it has already been spotted? Just read release notes of the neta releases since &/or an issues list on github?

@deckingman said in Managing machine & material specific settings.:

@DocTrucker
Can you clarify a bit please? Do you have multiple machines or just use different slicers and computers with a single machine?

Hi Ian. Four printers, two computers both with two slicers. Wasn't too complicated when just using slic3r as I directed the software to use a network share. Alas not so convient with two different slicers. I'll read through what you've discussed tomorrow, thanks.

@jay_s_uk cheers. Missed the obsoletion notice on the old one.

Will be interwsting to see which command Super Slicer & Orca Slicer use.

I had a crack at the conditional gcode this morning and it worked reasonably well, but the movement is sloooow! I will be reading the PWM setting using the object model and developing the code so that it moves from any position. Parking the nozzles to a known position before shut down will also simplify things.

; test
; T0 Nozzle movement = 1.15mm
; T1 Nozzle movement = 1.40mm
; PWM Settings T0 =  M280 P0 S1750
; PWM Settings T1 =  M280 P0 S1250
; PWM range = 500us
var e_range = 1.15
var e_step = 0.10
var num_steps = var.e_range / var.e_step; = 28
var e2_step = -1.40 / var.num_steps
var pwm_start = 1750 ; T0 high
var pwm_end = 1250 ; T0 low.
var pwm_current = var.pwm_start
var pwm_step = (var.pwm_end - var.pwm_start) / var.num_steps

var loop_count = 0

while var.loop_count < var.num_steps
    set var.loop_count = iterations
    set var.pwm_current = var.pwm_start + (var.pwm_step * iterations)
	M280 P0 S{var.pwm_current}
	G1 E{var.e_step}:{var.e2_step}

set var.pwm_current = var.pwm_end
M280 P0 S{var.pwm_current}