Topics created by JohnOCFII

Shit happens, John 😉

Btw: New Version is out and working
https://github.com/chrishamm/DuetWebControl/blob/dev/DuetWebControl-1.21.2-b2.zip

To close this out, I decided to create a new two-wire connection that bypassed the 12-pin connector. I started by replacing the thermistor connection. It works fine. So - I didn't find the true source of the problem, but I did isolate it to the thermistor pair of wires and not the heater wires.

This workaround is acceptable to me, and less hassle than replacing the 12-pin connector and likely having to patch in additional wire length. 🙂

Looks awesome!

@dc42:

How long is the Bowden tube on your printer; and what was the printing speed?

The bowden tube is about 470mm between Titan extruder and E3D-v6.
Print speed was was 60mm/sec with outline at 48mm/sec.

@dc42:

Your M201 acceleration settings are quite low, which means that you probably have little need for pressure advance. Pressure advance is more important when you use high printing speeds and high accelerations.

I chose to start my testing at this speed as a "known" speed, and expected to ramp up from there. Because I had seen positive impact with Linear Advance at similar speeds on my MK2, I started with the same speeds here on the Delta. I'd agree that my starting position on the MK2 had worse looking corners at 60mm/sec than I do on the Delta. The process I had used on the MK2 was to try to get my 80mm/sec prints look as good as my 40mm/sec prints. I was thinking along the same lines for the Delta.

I had also selected this model since it was closer to my "real world" prints than some of the simpler tests.

Thanks for the insight.

John

After seeing your reply I decided to reload the wifi firmware only and that seems to have done the trick. Tried a few restarts and all good. Thanks!

@dintid:

@JohnOCFII:

@burtoogle:

Settings -> Machine Control -> Half Z Movements

The state of this is probably stored in the browser, not the Duet.

That was it! Thanks.

In this day and age when it is common (for me anyway) to interact with two to three web browsers on multiple devices (laptop, tablet, phone), even across the duration of a single print, I wonder if this information could be saved and loaded from the Duet itself. It feels like DWC was not designed with the multiple simultaneous browser environment in mind.

John

Correct, it is only designed for 1 consecutive connection at a time. It’s so fast that it’s normally irrelevant, but it does raise questions like these.
If everything were set on Duet you wouldn’t be able to do custom things or client basis, so guess it’s a trade off as always ?

It would be possible by adding a username to the initial login.
Then the settings could be saved on a per user basis.

Thanks, I've just updated it.

@deckingman:

You can now set a temperature range and the Duet will attempt to control the fan over that range using PWM. I've recently started using T60:140 instead of a fixed "T45" value. What this does is start the fan when the temperature reaches 60 deg C and ramps it up to full speed when the temperature reaches 140 deg C, maintaining full speed at any temperature above 140 deg C.

Very Interesting! I'll keep a note of that. I'm commissioning a new effector, new fans, new carriages and Haydn's Magball arms in my T3P3 Kossel Mini, so I'm already throwing a lot of change in at this time. If it all works properly, I will certainly consider that option.

@Dougal1957:

https://www.ebay.co.uk/itm/Mini-Round-Bullseye-Spirit-Level-Bubble-12mm/322198500470?hash=item4b0486f476Ⓜmt_o3et2cj8-H9SRpAaTEug

Ordered - Thanks!

This morning was the first chance I had to try this again.

I realized that I could run G32 from the DWC many times without issue. I ONLY had issues when running it as part of the pre-print calibration as part of a particular print I was trying to do. I regenerated the GCODE from S3D, and that GCODE ran fine, including the G32. I've done a couple of other small prints since then that also worked.

So - either this problem occurred with a bad GCODE file, or gremlins. 🙂

I'll consider this resolved.

What would be the optimal cable to use to make a wiring harness?
I think I'll try to make it myself 🙂

-Jannis

@number40fan:

http://www.ebay.com/itm/Lot-2pcs-Ball-Bearing-4cm-40mm-x-10mm-Blower-Fan-12V-Brushless-Cooling-fan-2pin/263060496493?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2060353.m2749.l2649

Grab a set of these. Saves a lot of room and they push some air. With my fan and nozzle, it is right at 50mm tall and fits under my effector mounted vertically. Working on a new mount to put both fans on there.

I ordered the set of two. Thanks for the link!

That layout also takes up a lot more space, i.e. 9 rows of layout instead of just 3. This isn't so much of a problem on a PC, but would be an issue on a smartphone or small tablet. Some machines have additional axes U, V W which would also need to be included. The Extrude functionality also needs buttons to set the extrusion rate.

Perhaps someone can come up with another layout that is better than both the existing one and the one used by Pronterface, Repetier etc. and that most users can agree is better than both of those?

@JohnOCFII:

One of the nice plug-ins for OctoPrint keeps a list of printed jobs with their details (time printed, time to print, filament used, etc.) This also keeps a cumulative total of print time and filament used.

http://plugins.octoprint.org/plugins/printhistory/

Thanks for the consideration,

John

+1 😉

I re-did the G31 calibrations with hot-end and bed heated. New G31 Z parameter is now 0.17, and on the first two test prints, the first layer height was excellent. Adhesion on glass is good, and bottom was appropriately smooth.

Thank you for the guidance, David.

John

Great, glad it's working for you now. My story on this is that I am using a wifi module in a product (not the same module as the Duet uses) and I found that after a while the mdns queries to it failed even though you could still access it using the ip address. After a lot of investigation that involved changing both the AP and the DHCP server I never got to the bottom of it. To this day I remain convinced that it is a bug in the wifi module. But then I got a duet and noticed the same thing could occur with the duet. So now I just access the duets using their ip addresses and the connections never drop out. Could still be something else that's causing the problem but I've wasted enough time already so I'm not chasing it any more. Cheers, Mark.

Thanks for the explanation, David.

I will make the suggested changes.

John