@dc42 Thank you! On to the next round of troubleshooting.

@singhm29 said in Thermal runaway not active by default?:

No problem! The issue however is that I get a reading of 2000 instead of fault and no error in DWC making me wonder what I've done wrong in the setup to have the safeguards disabled

If you are getting readings of 2000, the heater will go into the fault state as soon as you try to heat it up. It will not go into the fault state or report any other error as long as you leave it turned off.

Thanks. Currently the command line entry on PanelDue does not scroll horizontally. I suspect that the command was being truncated.

Morning gremlings made my reply into an edit:/

In any case I think we can call it case closed if the configurator will be changed to exclude the deploy commands for BLTouch. 👍

Thank you gents

@sinned6915 said in Help- Marlin convert: Dual endstops & LCD Menus:

.........................I am leaning towards wiring the other 3 switches in series, NC, so that if one of them trips, the condition is set. I really want this for stopping the printer from crashing the carriage out of bounds resulting from missed steps/layer shifts-hangs-hiccups-whatever................

That's how I have my machine configured. As @Phaedrux says, once homed any moves will respect the axes maxima but I tend to do stupid things from time to time, so having additional switches can be useful. In my case I use a spare end stop on the Duex5 (E4) and connect the 3 switches wired in series to that. So any one opening will cause the trigger to happen using this command in config.g M581 E4 S1 T0 C0. The E4 is the end stop number, S1 means detect rising edge, T0 means do an emergency stop like M122 (but you can take other action or call your own macro), and C0 means any time (using C1 means only when printing from SD card).

That did not seem to affect it when I did it. I intentionally changed the homing speed in that section and while it did affect the homdelta.g file it did not change the T parameter in M558

Though it seems to be doing it now, odd.

@dc42 Yeah, I guess that makes sense. I did get a build done after I downloaded CoreNG-dev3 yesterday.

just tried a different card. worked. thanks

It is with great pleasure that I can inform fellow forum members that the printer is now functioning as expected. Setting the endstops to active high at the low end did indeed do the trick.

For reference the endstop LED’s are on and go off when the switches are activated.

Many thanks one and all for your input.

I think your wifi server is a little out of date. Should be running 1.23. Not sure if that will help or not, but worth a shot.

I've never seen that error message before. It could also be related to DWC2.0 RC4. I think it's up to RC6 now, so you may want to also update that.

The problem is that the name of your GCode file contains space characters, and the current stable firmware omits the quote characters around the filename in the M23 command. This is fixed in the most recent beta. Meanwhile, if you edit the resurrect.g file inserting double quote marks around the filename, you will be able to resume it.

Thanks for your report, this problem has been fixed.

Thanks, I'm discussing this with Tim and my colleagues.

Thanks a lot.