Topics created by goldentuna

Thank you very much .. that will help a lot .. hopefully someday we'll be able to use the DueX5 endstops as well.

This will give me enough as I've read the GCodes on the wiki several times to at least give some points to experiment with.

Thank you so much … that will be a big help!

thank you for that clairification.

It turns out - and hence my OP question - that one of my Titan extruders was in fact skipping. I thought at first the motor wasn't strong enough .. or that there was a clog in the nozzle - or that .. well.. 1/2 a dozen other reasons I was checking.

As it was .. I just didn't have the current set correctly. It was set at 400mA (it probably came from a copy/paste doing the config) .. and it really should have been 850mA

Once I made that adjustment - so far, it's been working great.

Thanks for everyone's input and help.

That makes total sense now where S3D comes up with the .27 - I apologize for my ignorance.

It appears then, that I have some issues I need to re-calabrate for my nozzle and bed leveling to reset my z height in the config file.

Thanks.

@T3P3Tony:

Hi Ian

You can do what you describe using one more thermistor input.

As the DuetWifi reports the CPU temperature there is an aspiration to make this a temperature channel that can be used for fan control.

Ah… Ok. Makes sense.

@dc42:

You could arrange your starting gcode to have this at the start, before your other G10 commands:

G10 P0 S0 R195
G10 P1 S0 R195
T0
T1
T-1

This will start both tools heating to standby temperatures.

Thank you!

I got this issue solved by upgrading the firmware to 1.16 … errors all went away and heaters are working fine.

Thanks again to both of you .. I now have my beast working .. at least all the homing and I can 'dry' print a file.

I still need to tune my heaters - and work on the IR Z-probe distance and Z offset .. so I'll be doing some more research/reading before I come back and bug you guys for help again.

thanks for pointing that out … I tested, and I see now that when I trigger the x or y endstop the led does come on. They were probably on before because the enstops were shorted.

I have an IR mini Z-probe ... can I also use the z-endstop as a 'fail-safe', I don't see the z-motor led come on when the IR z-probe is triggerd.

Sorry for all the newbie questions .. moving from arduino/marlin to Duet has been more of a learning curve than I anticipated - but I'm sure with everyone's patience I'll make it...