@siam said in How to run PID for BED:

M303 H0 S80

Ok 😄 ... thx

@jbourns trying a different slicer and then testing 2000% let's you decide whether the problem is in the slicer region or in the config/dwc region.

@fcwilt Thank you very much. I've got a 15 hour print going, but once it's done. I will play with those settings.

Thanks.

Michael

@sigourosandreas please send a picture for how its connected to the Duex4

You do not need the M950 command in the deploy and retract probe macro please remove those, it should just be in your config.g

Please run M98 P"0:/sys/config.g" and post the output here to see if there are any issues with the config.

Finally if you can please test the functionality with the old settings and without the Duex 5 to see if it makes a difference.

@lui2004 the prusa calculator is good, and there is also a calculator build into our config tool when you set the steps/mm
Screenshot_20211010-111433.png

@klotz420 said in Nothing but trouble with Nozzle as Probe and Mesh Bed Comp:

I kept using the RRF Configurator instead of changing the .g files directly. Not anymore so.

You got it correct. The configurator is good for a baseline configuration on a new machine/board, but you need to tweak it later manually.

One way to manage the gcode changes is to use a version system such as github and backing up the /sys and /macros directories periodically. This way you can track changes and go back in time when needed and the rfm utility makes it much easier https://github.com/wilriker/rfm/releases

@messiahman ok great news.

@adamfilip can it be that something is wrong in the wiring of the fan?Perhaps a defect fan-cable which has a little conductivity to GND?

@icy_snake I show those opto endstops as currently unavailable, but there are other suppliers who make the same thing. Look for the LM393 comparator chip on whatever devices you use. That chip switches the output between logic 0 and 1 very quickly and I think that is responsible for the high precision of the endstops.

This one uses the LM393 comparator

@jay_s_uk That seems to have done the trick! Thank you so much!

@toddel Da musst Du Dir vieles zusammensuchen. Im dozuki steht schon mal ziemlich viel. Z.B. über PA.
Im Forum nach Stichworten suchen ist die beste Möglichkeit.

Beim Motorstrom würde ich nicht über 85% des max. Stroms vom Schrittmotor gehen (muss natürlich im Range des max. Stroms vom Board sein). Ich persönlich fahre mit 75% des Maximalwerts. Den max. Strom des Schrittmotors kann man seitlich am Schrittmotor ablesen. Im Betrieb zeigt sich dann ja ziemlich schnell ob der Strom passt. Werden die Motoren sehr heiss, ist der Strom sicher zu hoch. Hast Du Schrittverluste, eher etwas höher gehen. Da sollte dann aber auch kontrolliert werden ob die Mechanik leichtgängig ist!

Für Input shaping brauchst Du ein Accelerometer... da bin ich mir jetzt aber nocht ganz sicher. Hab mich noch nicht damit beschäftigt.

@dc42 said in Usage of g-code T-1:

@jens55 said in Usage of g-code T-1:

This is where my confusion is happening - we have no extruder selected but the next commands, M104 and M109 actually work on tool 0 ..... Why????

when RRF receives M104 or M109 with no tool selected and no T parameter, it applies it to the lowest numbered tool.

Ahhhhhhh ....... now that makes sense (and saves me some time trying to figure things out)
Thank you !

@col_clucks said in Issues with mesh leveling.:

@fcwilt so I took that out and it is changing the z height now so great success there. However it doesn’t seem like it is correcting enough. That may be an issue with the pinda 2 I’m using so I’ll start looking there

It sometimes seems to be that mesh bed compensation is changing Z enough - though I can see the Z steppers moving tiny amounts.

Perhaps it is a speed issue and that some setting is preventing the Z steppers from changing fast enough to be at the correct height where the actual filament is being laid down?

I have no idea.

Frederick

@tom33 Have a look at M505 https://duet3d.dozuki.com/Wiki/M505

@modest-orange thanks for letting us know what it was.

@the_gibson if you can get a existing config then use the config tool here:
https://configtool.reprapfirmware.org/
and the existing information from (e.g. Marlin configuration.h) od the documentation to get dimensions, correct currents etc.

@thedragonlord you probably have M116 or similar in your tool change files