Web Based Configuration Tool
-
Just had a quick go with this, one thin I noticed was in the homeall.g file the z homing appears to be done at the corner (first point) rather than the middle.
-
Just had a quick go with this, one thin I noticed was in the homeall.g file the z homing appears to be done at the corner (first point) rather than the middle.
Under "Endstops", then "Z Probe", there are settings for Probe X offset and Probe Y offset. Put the values you want in here and it'll generate the x and y moves in the homeall.g and home Z files (at least I think it does).
-
The probe offsets are for letting the firmware know the probe and nozzle are not in the same location.
-
I noticed this configuration tool mentions the ability to define a Steinhart-Hart coefficient as term C of the M306 gcode in Firmware 1.16.
Is this supported in the current version 1.15c or do we need to wait for 1.16?
Also, upon entering the appropriate values from the Semitec 104-2GT datasheet I get:
M305 P1 T100000 B4338 C7.034421808033219e-8 R4700 L0 H0Is scientific notation OK or should that be 0.0000000703442181?
As the note says, you'll have to wait for RRF 1.16 because 1.15 doesn't support it yet. You can add already add the optional 'C' parameter though, it just isn't used at the moment. I don't think scientific notation will work, so I suggest you specify the whole number. That's what the config tool does, too.
-
Thanks for the clarification. Unless something's been fixed since Friday, although it displays in decimal form on the website, it does indeed write it out to the config file in scientific notation.
As the note says, you'll have to wait for RRF 1.16 because 1.15 doesn't support it yet. You can add already add the optional 'C' parameter though, it just isn't used at the moment. I don't think scientific notation will work, so I suggest you specify the whole number. That's what the config tool does, too.
-
Very nice!!! I was thinking would it be possible to actually have all these pages embedded in the duet webserver? Is this planned already?
-
W3DRK, thanks for the note. I was expecting JavaScript would display floats without exponent by default, but this doesn't seem to be the case. As a work-around the config tool will now convert the C value to fixed precision with 16 decimal places - I guess that should suffice.
sga, I was thinking about integrating the config tool in DWC so that the template (i.e. config.json) can be loaded and edited using the online configurator at any time. But there are still many more items on my TODO list, so I think this will have to wait a bit longer. If more people are interested in this, I will try to include this feature in my next DWC release.
-
sga, I was thinking about integrating the config tool in DWC so that the template (i.e. config.json) can be loaded and edited using the online configurator at any time. But there are still many more items on my TODO list, so I think this will have to wait a bit longer. If more people are interested in this, I will try to include this feature in my next DWC release.
That would be soooooo cool. Admittedly changing configuration settings is rarely done but when it is necessary, it would be so much easier to use the configurator than try to remember, or have to look up, the requisite M or G code along with all the associated parameters.
-
I beleve RRF does recognize scientific notation. It uses the C library function strtod to parse floats. I've noticed that although you can usually leave out the spaces in gcode commands, you can't leave out the space before E in a command such as M906X800Y800Z800 E800.
-
I've just tested this and I must revise my previous statement: strtod can indeed parse numbers in scientific notation, so it should not matter which format the M305 C-parameter represents. I've just changed the config template to use the native JS float-to-string conversion again.
-
Works for me! Thanks!
-
sga, I was thinking about integrating the config tool in DWC so that the template (i.e. config.json) can be loaded and edited using the online configurator at any time. But there are still many more items on my TODO list, so I think this will have to wait a bit longer. If more people are interested in this, I will try to include this feature in my next DWC release.
That would be soooooo cool. Admittedly changing configuration settings is rarely done but when it is necessary, it would be so much easier to use the configurator than try to remember, or have to look up, the requisite M or G code along with all the associated parameters.
Actually the fact that configuration settings are rarely done depends on your usage I guess, I have exchangeable print heads with dual and single heads and and the Vulcan requires a different Z heights as well… Having a laser head is also part of my plans for the next 3-4 month.
So not only having the web based configuration tool embedded would be a dream but also being able to store, recall and edit multiple config files without uploading would be nice. -
Just noticed something else. In the generated config.g there is this line
M350 X16 X16 X16 X16 X16 X16 I0 ; Configure microstepping without interpolation
Should it not be M350 X16 Y16 Z16 Enn16 etc? At least that is how the wiki seems to read.
-
Yes, also the default should be I1 unless you turned interpolation off in the configurator.
-
@sga:
Actually the fact that configuration settings are rarely done depends on your usage I guess, I have exchangeable print heads with dual and single heads and and the Vulcan requires a different Z heights as well… Having a laser head is also part of my plans for the next 3-4 month.
So not only having the web based configuration tool embedded would be a dream but also being able to store, recall and edit multiple config files without uploading would be nice.sga, is there any reason why you can't use a config.g file for your most common configuration, and then for each additional configuration, create a macro file that you run after starting up? The only commands in config.g that you can't override later are the network configuration commands to set MAC address, IP address etc. (which don't yet work on the Duet WiFi anyway). I even have a macro file to switch my Cartesian printer over to CoreXY mode, so that I can test CoreXY support in the firmware.
-
Yes, also the default should be I1 unless you turned interpolation off in the configurator.
No I didn't turn it off. The configurator has "X16" as the default rather than "X16 (on)".
-
Just noticed something else. In the generated config.g there is this line
M350 X16 X16 X16 X16 X16 X16 I0 ; Configure microstepping without interpolation
Should it not be M350 X16 Y16 Z16 Enn16 etc? At least that is how the wiki seems to read.
No wonder when I change the stepping nothing works! X is always 16!
-
Using the compensation tab, I just noticed for my 300x300 bed, I am receiving an error stating that values must be less than or equal to 210 for probe points. Is this a firmware limit for probe points or something that needs to be fixed in the configurator?
edit: missed a config tab that fixed the issue
-
sga, is there any reason why you can't use a config.g file for your most common configuration, and then for each additional configuration, create a macro file that you run after starting up? The only commands in config.g that you can't override later are the network configuration commands to set MAC address, IP address etc. (which don't yet work on the Duet WiFi anyway). I even have a macro file to switch my Cartesian printer over to CoreXY mode, so that I can test CoreXY support in the firmware.
Sorry, you are certainly right. I do have my effectors on magnet balls. I have the std one working now and all parts ready for a dual vulcan, as well as a ceramic paste extruder. In the future maybe next year I will probably add more (laser) but I have no parts or clear plans yet.
The main differences between the 3 current heads will be in the geometry:
-nozzle height and number and position
-z probe height
-Extruder steps per mm or mm3 for the paste.
-max speed etc…
The only risk is to crash the nozzle by pressing the bed autolevel button before selecting the appropriate config macro.I was naively thinking a different config.h was required for every geometry but a macro library would be just as good.
Following your idea, what would be a good way to change the visual aspect of the webpage as a function of the currently selected configuration macro? ( i am thinking title, color theme, to avoid confusion)
Ideally I would put a different resistor in each effector (toolhead) and use that as a configuration selector. I have used that in the past in different projects and it was good enough up to 20 different calibrated modules.Thank you again for giving us such a nice tool to play with.
sga
-
You can use the M550 command to change the name at the top of the screen to reflect the setup you are using as part of the macro
