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.
@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 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.
I have a nimble with pressure advance and the following settings seem to work fine. See attached file (how do I get this to display?).
The pressure advance setting is still a work in progress, but currently:
M207 S0.35 R0.10 F2100 T1800 Z0.00
M572 D0 S0.05.
These are for an E3D Volcano, and the settings vary a bit for nozzle diameter and filament (of course?).
dynamics_H2.g
I liked the previous version, but had left you with some crude code ~20 July, and comments related to my simple needs, but I had abandoned use of DueUI as I thought you had abandoned this project as there had been no response and looked like there would be no support.
I notice babystepping is now included - thanks?
Is there anything critical that is new? Although I can implement and customise this I am not conversant with JSON in general & my brain will take some hours to reboot into this project.
My next step is to have my filament in a low humidity box. I have built one with room for 3 spools.
The plan is to connect it to E1 to control the temperature - choices for PLA or PETG perhaps. (I only have a single extruder on E0). Also with a PWM fan for air flow over the silica gel. A bit of experimenting with the usual features, and the possibility of a heat exchanger to have lower temperature air with higher relative humidity over the silica gel (a theoretical concept they may not be useful in practice - I will find out ).
The likely max power consumption is less than 50 watts and possibly averaging around 20 watts or less, so max current is 2A on my 24V PS. I will install a heater with max 3A to cover uncertainty but well within the capacity of the E heaters. (I have a spare 5 ohm (approx) heater which is too close to the limit of E so will add 3 ohms of resistors for safety as I understand I should not rely on PWM settings.)
It seems I have 2 choices. Configure it as:
I think both can appear in DWC but the Chamber option will be a little more complicated for my evolving minimalist Dueui interface.
It seems both are straightforward in config.g. Is there a reason to prefer one over the other?
@garis I have the sense endstop working now by modifying the widget and the corresponding lines in the json file and also a separate jog widget for E. So far so good and I can now use it.
A babystep widget that works.
A babystep_position widget (a display of complete ignorance).
0_1562725404394_baystep_position.txt
The json code.
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.
A few photos of my Core XY is at https://forum.duet3d.com/topic/10270/my-hypercube-evolution-corexy-variant
I have dual T8 Z screws with 2mm pitch and 2mm lead (ie single start thread), 2 motors and joined by a belt (carefully assembled) to keep them synced when power is off. No problems so far with bed when powered off but I guess there is a slight risk. The 2mm lead is a critical factor where the friction is sufficient to reduce the chance of movement when power is off.
@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.
@claustro I have posted details and photos at "My Hypercube Evolution CoreXY variant" in the category "My Duet controlled machine."
https://forum.duet3d.com/topic/10270/my-hypercube-evolution-corexy-variant
