@dc42 Sorry for bothering you with this too (i know i'm a bit annoying sometimes 😂 ) what do you think about that ?

Still having this issue and I can't seem to find a resolution anywhere, any thoughts anyone?

Thanks a lot to all of you!
PT100 Sensors have the problem of all of them being quite "big", but I am in contact with a manufacturer who might be able to supply a small enough Version of it.

Right now I am using the H and L parameters to finetune my thermistors, but this is a little frustrating to do as you can't just measure the temperature difference and enter it but need to work your way there. At least my thermistors all vary so I'd need to tune all of them.

If the sensor temperature is not the same as at the nozzle it does not matter as the deviation should be the same on every printer if the sensors (probably PT100) don't vary.

@dc42 said in Setting precise temperature for chocolate printer:

Yes, in RRF the G10, M104 and M109 commands accept floating point values for the temperature parameter.

You made my Day! I did not find any documentation this is possible and stupidly did not try.
But this leaves me with one Question: Is there a way to set it at steps 0f .1 of a degree? I dont want my customers to have to use the m104 command all the time.

Do you happen to know if there is a way to set them using a repetier server? (or using PanelDue)

The functionality of the configurator is meant to get you a starting point. Currently, more complicated arrangements will require some implementation by hand. That said, I'll move to the wishlist forum, as work is always being doing to improve the functionality and this may before more easy with RRF3.

Here you can find my tests to talk to the Duet using Python 3 and a Duet 2 running version 3.11 and a Duet 3.
https://github.com/triditive/duet_test/blob/master/duet_python_test.py

@Phaedrux ha, that would be great, but then the first option; just regular wiring. Then a software update would work automatically.

@dc42 said in Object model to report two decimal places for axes:

Although the value is displayed to 1 decimal place, it is stored to a greater precision. You can see this if you enter:

echo move.axes[2].max+0.000001

However, I will increase the number of decimal places reported for axis minima and maxima by M409 to 2 in release 3.1.1.

.

Will the reported accuracy be added across the board?
I noted some rounding when I was doing that macro to add baby steps to the current trigger height.
Trigger height in config.g was to 3 decimals as reported when using G30, but when added to baby steps & saved it was 2 decimals.
Didn’t know you could add how many decimals you want returned, but would be better not to have to.

EDIT: Realized after posting, that your demo was just forcing the return of a string with that level of decimal places, by addition, not a format parameter denoting number of decimals.
Where's the face palm emoji?

@dc42 said in M203: Not Consistent?:

The reason that M203 and M566 are in mm/min is that mm/min is the standard speed unit in GCode, for example it's the units for the F parameter in G1, G2 and G3 commands. GCode was designed originally for CNC machines, which typically use slower feed rates that 3D printers.

M203 has been specified as taking its parameters in mm/min since 2013. There are tens of thousands of machines running RepRapFirmware and specifying M203 machine limits in mm/min, so it would be too disruptive to change the units now. Whereras M205 was added much more recently.

That makes sense.

HA! That's what seqs does!! OK, this becomes much less important then. Thanks @chrishamm.

@dc42 OK interrupt driven endstops make sense in that context.

I hadn't noticed or tried this but M574 does say

Snnn 1 = switch-type (eg microswitch) endstop input, 2 = Z probe (when used to home an axis other than Z),

I'll play with that and see how it works.

@FelixH Sorry, there is no tutorial. What I used is one Box, some pushbutton , one switch, a level shifter and an Arduino Nano with some software. The software you can find in my post above. Inside software you find description what pins to use.

Hello,

Sorry if it's stupid question for you, but I'm not a electronic or software ingeneer...

I need to connect my relay to 1pin for signal and the second wire to ground, then I will have a signal for the relay ?
what will be the exit voltage ? 3.3, 5v or other voltage ?

Can I use every pin on the extension connector or only several pins are usable ?

Thanks for your help.

Bye.

Did anyone get anywhere with this?

@zapta said in Supporting multiple configurations on a single Duet:

I think it feasible to have a seamless upgrade/board-replacement/printer-cloning. E.g. by releasing a single file, having M505 does the work conditionally (seep and Flash wear concerns)

You can probably have RRF choose the correct sys folder already by putting this in config.g (caution: not tested):

M505 P"/sys/RRF3" ; select RRF3 folder if false M505 P"/sys/RRF2" ; select the RRF2 folder M98 P"config.g" M552 S1

RRF2 should ignore the "if false" and execute the second M505 command.

Yeah I mounted enclosure fans on my setup which I leave on at low speed all the time but I was thinking having it thermostatically controlled would be nice.

In Octoprint I was able to have the SBC core temp displayed on the interface

I am running an IDEX printer. I am not so familiar with condition statements. Can someone give me an example of checking if all axis is homed?

Here is my tfree0.g. How can I modify it such that it checks if all axis is homed?

;M106 S0 ; turn off our print cooling fan G91 ; relative axis movement G1 Z3 F500 ; up 3mm G90 ; absolute axis movement G1 H2 X-30 F6000 ; park the X carriage at -30mm

Fair enough.

Regarding the macros, yes, something like this:

if state.status == "idle" remainder of macro commands note the indent

this would be nice to see working again so I can avoid the location of the magnets I have under my PCB bed.