@neueklasse said in IO*.out Pin Assignment to gpOut with M950:

is it Possible to Change that Command so a "Max Value" can be Programmed?

since M452 allows you to set this power with the R parameter, does that not work, i.e. M452 R100, G1..., do you have a gcode generation tool that uses the E value to specify the laser power? if so which one?

@tonychang Both Powge and Trianglelabs are fine for belts as far as I have heard and seen. Their main supplier for most things is Runice that is the manufacturer of Gates Unitta belts in China. My belts for the Voron 2.4 comes from Powge and they are fine. I think my belts for the V0.1 comes from Powge as well but via Lecktor.com

I think that as long you buy from the bigger stores on Ali you are good. Trianglelabs, Mellow, Powge etc.

If you don't want to buy from China, you can buy the same from for example Lecktor.com and VonWange.com at more or less the same price if you're in EU.

@wdenker what is your M570 command set to?
https://duet3d.dozuki.com/Wiki/M570
You can use the S parameter to set a number of minutes between a heater fault and the subsequent cancellation (and power off)

Snnn Integer timeout in minutes (can be set to 0) for print to be cancelled after heater fault (Firmware 1.20 and later). If the S parameter timeout occurs (which only happens if a SD print is in progress), RRF will also try to turn off power via the PS_ON pin.

@bubblevisor i have heard people using this sort of arrangement when using multiple Z motors, not sure if its actually better than using a single motor and the belt.

@sudodelta what happens when you run G32 a number of times. you should see the error reducing to a "steady state".

@hayden1993 please post your config.g (using the </> tag in the formatting bar so it imports nicely). Also post some information about what endstops you have installed.

@tisdai if you manually move them to the center of the machine so nothing is being triggered. then send M119 what do you get?

then send G92 X150 Y150 and try and jog the axis +/- by 10mm. do they move, doe they move in the direction expected?

@o_lampe I have not looked into the compatibility between older KiCAD and 5.1 yet.
complib.pretty is here:
https://github.com/Duet3D/Duet-2-Hardware/tree/master/complib.pretty
download the directory and then add it as a library (if that works).

@danzaywer I understand, my point is when you go through the while loop its unlikely to actually ever match the condition during the brief point that the stall occurs.

@moe-adams9093 ok then I expect the the processor and possibly more is damaged. its hard to know in advance how much of the 3.3V logic will be damaged in this case.

Hi! Thanks for making this tool, it is very handy.

I'm currently trying to grasp the limitation of accelleration on stepper motor drives. I've used your calculator on a few motors, and i noticed that generally people report running 2-4 times higher accelleration on their printers before running into issues than your calculator says is possible.

I am not sure these printers actually run at the requested speed, but certainly there is some difference between running at the speed your calculator produces and a vastly higher speed, i can see that on my own printer which accellerates more violently.

So i am wondering, what gives? Shouldn't the stepper skip steps if you ask it to go TOO fast? The stepper driver has no feedback loop to tell. I can't notice lost steps below 20.000 mm/s² accelleration using really small NEMA 17 motors with only 1.68 A capability and a rated torque of only 36Ncm, inertia of 54 g/cm² driving a rather heavy gantry at 800gr.

I would really apprechiate if someone could explain this discrepancy to me, i am not very familiar with stepper drives.

For anyone finding this and looking for an answer, this is a part failure in my case. Mine started working again today, but then went out again. Intermittent.

@zakm0n said in Resume from pause doesn't respect previous feederate.:

@fcwilt

The only G1 in this sequence has F75 for 75mm/min (I'm fine tuning feed rate with the speed slider.) That should carry over to the program g-code on resume.

The code in a print file usually has many, many F parameters setting the speed.

It's likely that any speed you set is going to be quickly overridden by those changes.

Frederick

@jrdm EE70F9D6-D0D4-4F20-A5FC-8A0C29D6F56C.jpeg

@siam i think i've found the problem, i just tried stopping the daemon.g from running and it doesn't rebooted in an hour print... i think i'll have to shut it down during printing and reactivate it after.

First print using the modified firmware.

A one layer print ABS 245 C 110 bed 0.2 mm Z and 260 x 260 mm using the bed mesh.

bedmesh.PNG

It's not perfect but it's not bad . I'm quite happy. Since it's all automatic and I just start the print and walk away.

Note, this is the underside not the top side.

IMG_3914.jpg

It's a tad too squished on the outmost of Y edge. Don't know why but that's something for another day.

A cable fault is not impossible; ribbon connectors can be a bit touchy if pulled around.

I'm running a 6HC and Pi setup, it's not given any problem at all; just put the DuetPi SD card in and everything started up, with the Pi powered from the Duet - twice - I did a full reload of the system after experimenting with beta firmware.

I'd suggest you try switching to power from the Duet, in case something is not synchronising properly?

Do you have a keyboard and monitor connected to the Pi & is the web control accessible through that?

@zapta said in A delta with colourful lights:

Very nice build. Don't recall seeing an enclosed delta before. Is this for ABS? What kind of chamber temperature do you get?

It's not really for ABS, though I have a coupel of spools of that I keep meaning to use up. Honestly, there's probably no very good functional reason.

I did find that my Prusa became much more just-print-on-demand and much less aggro and fiddling when I put it in an enclosure, but I suspect that might be because before it was in an enclosure it was just sat out on the side in a family room and got moved around and so on. When it went into an enclosure it did so in a less boisterous room, and never gets moved, so it might be the not getting disturbed that made the real difference. A metre-high 20kg delta doesn't get just moved here and there, so possibly wouldn't suffer the same.

The enclosure kills a bit of the whine from the little E3D fan (I'm looking forward to the Revo hotend, but fear the even smaller fan will be even whinier).

The enclosure has no active heating (just the effect of bed and hotend). I generally set the vent to run its fan from 35C, and I've never tried (yet) to see what it could / would get to. There is an SSR in the base with half a mind to put enclosure heating in it in future, but I'm mostly happy with PLA and PETG!

@zapta I've always turned mine off and on with a wired in switch with no issues so far that's going on 2 years now...but you never know, I'm also using the duet3 6HC not the mini but I don't believe it makes a difference, least I hope not! 🙂

@o_lampe hindsight is a wonderful thing, I should of thought that one through!

@peirof just to clarify, to me its a great advantage that you can find/make the STL's, then slice them and print them all using SBC

@vandermeulen said in heated bed temperature fault:

@engikeneer Okay, I hadn't found the M143 command. Let me try.

While you play with M143, you can loo at the heater's monitors in the DWC object model section. It will show you the internal affect of your M143 on the RRF internal configuration.

@stephen6309 Thank. but I would have prefer something build in the Duet like a external script auto triggered. Because if I use many slicer or config this setting becomes annoying to include in each config

@zapta said in 100C resettable Thermal Cut-Off for 24V heated beat:

BTW, what resettable thermal cut-off do you have in mind?

For now I mounted one exactly like those in a Kettle 100C ;-), after activation the thermo expandable medium while contract and close the circuit again...

@dc42 said in Rotating Magnetic Sensor - Keeps Pausing Printer:

@wouldstain @TheDragonLord please also provide your config.g files, to help us reproduce this.

If it could help I've discovered that the Magnetic sensor "doesn't like" theese two Ideamaker settings (that's the slicer I use). Unchecking both of them the false errors reduces a lot but, of course, this can't be the solution because in this way you get bad prints....

TinyTake17-10-2021-05-49-28.png

@o_lampe said in Curious Motor Phase Errors:

@fcwilt
Knowing the inductance of the motor won't help making it faster.
I'll soon test external TMC2225 drivers which are suitable for 36V and 1.4A. Just right for those geared extruder motors (or my hitchhiker IDEX motor)
Most external driver boards have 35V capacitors and separate Vin...

I understand that. But knowing the inductance and comparing it to other steppers that don't exhibit this problem might teach me something.

I did find some specs of a sort, but being a product out of China you never know how good the specs are.

In any case the stepper is "rated" for 24 volts and I was using it on one of my first printers back when I was using 12 volts and I have never taken the time to update the printer.

Frederick