18 months to get this far. It first worked about 12 months ago but another 12 months to do some surgery to it, and build a second one that is smaller with a single Z screw. Change to E3D volcano, Zesty Nimble, Duet and full redesign of X carriage assembly.

So a fairly basic configuration with print volume of 250 mm cube.

Key features are:
1 the configuration of the dual Z rods rather than 4 rods on the normal Hypercube and they are 16 mm. Y rods are 12 mm and X are hollow 10mm.
2 the X rods were changed from 45 to 90 mm vertical spacing
3 Zesty Nimble with tusk part cooling (hand rolled aluminium) requiring a bit of refinement.
4 Dual 4mm glass beds, 1 fixed & heated and multiple removable print beds, on 3 levelling screws on a 2020 aluminium frame.

Power supply and Duet mounted on the back.

It is mechanically quite accurate requiring no compensation or bed compensation, and at this stage just a Z mechanical Endstop and occasional Babystep variations.

The Z belt arrangement for keeping screws synchronised when power off.

X carriage with 3 10mm bearings, 2 on the lower rod and 1 on the top, with the carriage (not shown) having a bit of complexity to allow in-situ tuning of the bearing separation and alignment with X rods to avoid binding. 2 40mm fans

Thanks for this. Attached is a screenshot of my first draft of a single page version for a 22 in monitor. This is the shot from a windows 10 machine that has moved the elements around a bit compared to the active version. (Both in Firefox). The "production" version is running on another PC running Arch Linux with xampp with 2 virtual servers - one for each of my 2 printers.

I have an idea to also have a minimalist version running on the Duet using an Android Tablet as the client. As long as this doesn't overload the Duet as I also will need the DWC running in the background for other functions.

I have included 2 baby stepping sections which I thought to be useful for me. I wrote 2 widgets added to dueui_widgets.js. The stepping widget works (wonderful for a person that knows no javascript) but the widget for displaying the babystep "position" requires your assistance (see next post). ie display "M290 " z output.

The issues:
... The sense endstops widget doesn't work and this is of course critical.
... The Extruder temp control won't turn the heater off.
... I haven't yet worked out how to style the heater widget as the temperatures are very close to the up/down arrows.
... How do I style the console log to have a larger default height?

So far I haven't used it other than preliminary testing until the sense endstop is fixed.

I have a comprehensive gcode generator - a python script that applies various 'for' loops over user specified geometry (polygons).

It should, hopefully, be useful to others. It includes 20 different routines including many for retraction, jerk and acceleration for XY and E, pressure advance etc.

This image (of translucent PETG 0.6mm nozzle) shows an example with 2 Mcodes incremented in nested 3 x 3 test bands delineated by wider layers, within which a 3rd Mcode is also varied. Each tower can be a different shape and can be printed at different speeds.

This example: 3 polygons - 2 squares and a pentagon, each with 2 sides having grooves to mimic the XY test cubes. Configurable from triangles to circles with and without grooves, and number of walls.

I have been using it successfully for a few weeks and now doing a final check. I will post it here shortly when I have cleaned it up a bit for others (and me) to use.

Now that the structure of the script is working, any combinations of any Mcode can be readily added by request, or the user.

I guess there is an interest in including linear advance? I might do that and delay the posting to this forum.
Question, as I don't yet use linear advance: What is the likely range of parameters for me to start with in order to minimise wild first tests?

Other priorities? maybe wait till you see it. A day or so.

@phaedrux Quite well !! Part of the lengthy build process was lots of redesigning in Fusion360 (every part from the Hypercube Thingiverse site I redesigned so that took time) and of course this X carriage is almost a complete new design for the Nimble and tusk part cooling feature and for the 90m rod spacing etc etc.

The original build was all PLA because I could not successfully use PETG. Now most parts including all critical parts are in PETG with modest print quality. I got there by writing a python script that allows me to optimise 3 Mcodes at 3 different speed and progressively iterate through lots of combinations, which was particularly important because of the Zesty Nimble's sensitivity to acceleration and jerk and because I am using a 0.6 nozzle in a volcano. So now having done many test prints I am "just" able to print PETG. The nimble jerk is 50% higher than recommended and the acceleration is also quite a bit higher. Also dc42 pointed me to driving the zesty stepper at max amps to overcome jerk inertia even though little torque is required otherwise. I will run some more combinations through my python script at some stage.

The volcano also is ok except that at full flow say 20mm3/sec I seem to get too much temperature gradient between the sensor and the filament with the temperature struggling to stay stable. The auto tune Mcode doesn't allow for the heat loss at high filament flow rates. I've fiddled with manual adjustment HE heater settings but have not yet got a good set of parameters. For example if I try to manually test a higher temperature on the fly, say raise the temperature a few degrees, it will not heat sufficiently fast and the Duet will shut down with a heater failure. (its all 24V and all genuine E3D)

The remaining challenge, unsolved, is how to print top layers in PETG. I don't need much infill for strength but it appears I need 33% just to minimise the sag of the first top layer. Also the speed is lowish at 45 otherwise the extrusion bulges a lot as it bridges the infill. Otherwise I can print PETG on perimeters at 70 to 80. Cura did not work for me but the latest KISSlicer alpha with rounded infill seems the best.

The other printer is a single Z screw cantilevered bed X150mm x Y200 with identical upper features except as the X is so short the 8mm X rods are light and so the whole moving mass is close to the lightest possible. Even just using 3 small 8mm linear bearings for weight and reduced friction and potential for binding. The last photo has the two 10mm bearings visible on the lower rod on the bigger printer.

Now I have both printers fully working as of yesterday, I can put my mind to further improvements to my limited knowledge of PETG and perhaps make something useful.

If you understand basic python this script might help you. I posted an earlier version some years ago.

It creates test towers and then test ranges of Mcode from definable start / end / increments.

In essence it can test up to 3 nested for loops of M Code on 3 polygon towers each separately defined (from triangles to near circles eg for jerk !!), each tower at different speeds. Start / end layer locations are definable to control travel paths. (and to change viewing angle during print).

Sides can have 1 or 2 vertical grooves (configurable), and sides can be omitted.

A scan through the code will show more details and parameters.

Wide layers are printing for see where each code is changed, to supplement lots of M117 messages during printing.

I have no skill in creating a user friendly input screen so use the d_settings file that is imported and overrides relevant data in the main script file. Nor do I have skill in automatically creating the location of the output gcode so that needs to be manually set at about line 1008.

Most combinations are possible.

mcopt_p06_2.py d_settings.py

CoreXY has no "knowledge" of X and Y being equal.

My example: I have 2 Core XYs. The small one had a bed 150 x 200.

Recently I heavily tweaked everything on the X axis and now have a print capability of 170 x 210, with enhanced rigidity (ie less deflection than the 150mm) along the X-axis. Ideal for off-the-shelf magnetic print beds of 180 x 180.

If you understand basic python this script might help you. I posted an earlier version some years ago.

It creates test towers and then test ranges of Mcode from definable start / end / increments.

In essence it can test up to 3 nested for loops of M Code on 3 polygon towers each separately defined (from triangles to near circles eg for jerk !!), each tower at different speeds. Start / end layer locations are definable to control travel paths. (and to change viewing angle during print).

Sides can have 1 or 2 vertical grooves (configurable), and sides can be omitted.

A scan through the code will show more details and parameters.

Wide layers are printing for see where each code is changed, to supplement lots of M117 messages during printing.

I have no skill in creating a user friendly input screen so use the d_settings file that is imported and overrides relevant data in the main script file. Nor do I have skill in automatically creating the location of the output gcode so that needs to be manually set at about line 1008.

Most combinations are possible.

mcopt_p06_2.py d_settings.py

@gtj0
url I suspect is the issue, that's where the wiki and this forum get me confused and I could not find the forum post here where "an" example was given and the wiki was silent on the precision of the url if more was needed ??

My settings

M586 P1 S1 C"*"
Using the current default from github - keep it simple at the start, and so no embedded settings in the json
Cookies cleared

Trust this is legible as I don't know a more elegant way to provide this

Thanks

@gtj0 I waited for the dust to settle and have just installed the latest 3.2.5 beta version.

Upload > M586 C* > dueui.html > save > refresh >>> FAIL

Using the default json file.

The settings now look really simple, but apparently not.
It appears the only thing to be done was M586 and reboot the Duet.

I have read the wiki, and wondering what I have missed.

No config file was found at http://nnn.nn.n.nnn/dueui_config_default.json

I can download it using the /rr command given elsewhere - >> its findable. I can see it in the sys directory in DWC.

Stand alone Duet wifi firmware 3.2.2.
iMac with Big Sur Safari or Chrome.

I wonder about the syntax for the url but the dueui.html seems not to need anything just the file name and I tried not to be distracted by the irrelevant complexities for SBC or servers or print farms.

This is frustrating, again. Maybe it is too early in the morning.

It looks like you have been busy - thanks.

What is meant by "reset" the SD card?

Is this different from inserting the card and turning the printer on?

Neither of the cards in my 2 printers have been touched since they were 1st inserted a few years ago.

@gtj0 Always in favour of Simpler.

@gtj0 said in DueUI Release 3.0.1-beta2 Available:

Hmmmm. I'll have to fire up an old Duet2 to test. Sorry about that.

A gentle reminder about this. It would be a shame if Dueui is no longer compatible with Duet2.

I am trying to use dueui again after a long absence, waiting for it to stabilise. Just installed the latest version 3.2.0 to a Duet2 wifi with latest firmware. As the code has been substantially modified I am going to start from scratch again.

Step 1. I used the default config standalone.json file. A continuous string of 'Cannot read property "all of them " undefined'. Problem with dueui-bundle.js. Not reading the machine state file. This is way above my pay grade being a humble mechanical person who only wrote limited Fortran in anger in 1970 onto punchcards.

Step 2. I replaced it with the simple.json file which did work so at least it appears the software and settings are ok - perhaps

I am curious about the syntax in the json file for comments - my online search says no comments are allowed but clearly you have them /* */ and also single lines with // but there are a few value formulae lines with // and also followed by a line with "value" : 0.

I like the idea of putting the settings in the top of the config file but does that make the settings page/file redundant? The settings file is the dueui.html which loads the config.json. I would like access from more than one computer without having the settings in each browser.

@nomukaiki Preference 1 ie Ipad2 which seems not to connect over wifi, on various browsers.

@garyd9 About 18 months ago when I had less understanding of the interaction of all the settings (not that I have enough yet) I wrote a Python Script for generating a print file for 3 highly configurable polygons each at different speeds, with 3 nested loops of any combination of M codes that varied over a range of layer heights - in order to determine sensible starting points for all config settings, and for which setting should go into slicer gcodes. My thought at the time was that the common wisdom on this and other forums may not apply to Nimbles and Volcanos, and with larger nozzles.

I have the same pancake stepper as you have. All my tests at that time were with PETG in a Volcano with 0.6 nozzle. They still appear reasonable with the 0.4 nozzle in one of my printers.

Ejerk~70 and Eacceleration~400 seemed to produce the best quality, although I did not worry about print time, and I would not have focussed on the differences in times you have documented. The Zesty recommended jerk of 40 was too low.

There were some combination of settings that I have not documented and now forgotten where print speeds did drop dramatically. Probably PA settings that were outliers.