Topics created by r123

@jay_s_uk Awesome. So it' just 5v/GND and the STEP/DIR inputs. Worst case scenario I can hook up with a handful of female-female breadboard connectors from the Stepper10/11 connector on the Duet Wifi.

Thanks a LOT!

@dc42 Hi, did any work get done on the PTC heater ?

@dc42 now I feel like I'm observing the origins of the universe. (Well, the electrons are a little blurred.) Thank you.

@falkia said in the ground loop thing:

@fcwilt
Without having the 0V connected to ground/earth and the frame of the printer connected to earth/ground, then for example the fuse for the bed heater may not trip if you get a short to the frame in the heater.

I use AC powered heaters and the frame of the printer and the associated parts so a short from heater to frame would blow the fuse.

If I used DC powered heaters a short from the heater to the frame would not be dangerous as the DC outputs of the power supply are floating but there would also be no sign of that condition without a measurement being taken.

Yes, I understand that many folks recommend bonding the "ground" output (whatever that means) of the DC power supply to the "earth" ground.

Over the years (and there are many behind me) I never have done that and it has never caused any problems for me.

Thanks for the feedback.

Frederick

@davidewen said in possible reasons for a "short to ground" error mid print?:

I've swapped the driver for the original Ender 6 and same error.

Please explain exactly what you mean by that.

@r123 Pleasure.

@phaedrux said in what if Macros appeared in Console?:

Not a bad idea. Moved to the wishlist.

While we are talking about wishlist in macro-context:
I tested a few things in macros and from time to time I made syntax errors or typos in variable names.
A vague warning popped up in the console about these errors, not naming the macro they happened in.
Was it t#free.g, t#pre.g or t#post.g?
Happy searching...

@engikeneer good thinking

@o_lampe said in subdirectory /bin to tidy up sys:

@resam
Just to be sure: I still download the .zip file to /sys, but it get's decompressed in /firmware?

Yes, when the firmware is 3.3beta1 or later, and DWC is sufficiently recent.

@dc42 it seems that DWC parses out any ".g" suffix on the filename for display purposes in the Dashboard (though not the macro file list).

As above, I found that if called a macro "my macro" it would not call from a gcode file produced by s3d start script.

(with M98 P"path/my macro" )

But if I called it "my macro.g" then it would call from the gcode file

(with M98 P"path/my macro.g")

@engikeneer Thanks for that, I'm running the 6HC so trying to figure out how to setup the jumpers to run 5V External while also feeding the SBC.

If one has DWC in a regular portrait webpage format then the side bar is hidden and so there's an extra click involved to bring that up. Then one needs to remember that one's trying to click on "Status" to get to where one needs to go to start the print which is not intuitive and anyway it's hard to "find" things in that sidebar where everything looks (at first glance) "similar" and so it needs to be read line by line. At least unless one uses it really every day.

Laborious explanation but that's why I liked the idea of just clicking on the orange "print paused" on the dashboard. Though your idea of bringing job control to the dashboard when jobs are running may indeed be even better!

Perhaps it could be made configurable?

Please don't misunderstand my earlier statement: switching between two "pages" would be great for someone like me who really only uses "status" and "console", but I'm not sure I like the design aspect of it.

@r123 said in smarter 15C heat deviation messages?:

That's neat but I'm sticking with the defaults that have been shown to keep everyone else safe! ; )

Was trying to suggest that Duet might be able to spot Thermistor faults and say "Thermistor fault!" rather than "Heater Error". How? Because (at least in some cases) Thermistor problems can result in changes in "temperature" so rapid that they could not be explained by normal heating or cooling of the hotend.

Failing that maybe as a message:

"Tool Temperature error (X degrees for more than Y seconds): check heater and thermistor"

would be clearer than "Heater Error" ?

More often than not, it's faulty wiring or a badly crimped connector which causes the error. Or in some cases, the temperature can drop due to an overly aggressive part cooling fan blowing directly at nozzle.
Either of those cases might give the same temperature behaviour as a faulty heater or sensor and it's almost impossible to discriminate between them.
You need to be very sure of the cause before giving specific messages, otherwise pendants will start to jump up and down. I can already imagine a post along the lines of "I use a thermocouple but the warning message tells me I have a thermistor fault.". 🙂

thanks @deckingman , sound like a good idea: have added T0 to the "clear heater errors" macro. Wasn't necessary in the past.

If you connect to http://<ip address>/machine/status you get the machine model, and that has an entry 'job' 'lastDuration' which looks to me to be duration in seconds of the last print job. (At least, it does on mine - MB6HX + Pi firmware 3.1.1 - I don't know what combinations of hardware are needed for this to be true.)

One for @chrishamm.