Change extruder button increments in web interface?
-
How can I change the increments on the extruder buttons in the web interface? One of my machines runs 3.0mm filament so 2 of the extruder speed buttons aren't usable, I don't know if 60mm/s is even usable with a 1.75mm extruder. Something like 20mm/s 15mm/s 10mm/s 5mm/s 1mm/s would be more usable for me.
-
How can I change the increments on the extruder buttons in the web interface? One of my machines runs 3.0mm filament so 2 of the extruder speed buttons aren't usable, I don't know if 60mm/s is even usable with a 1.75mm extruder. Something like 20mm/s 15mm/s 10mm/s 5mm/s 1mm/s would be more usable for me.
I agree with this. I think any interface settings should also be in a config file so they are persistent across browsers.
Maybe a json config file?
-
The higher speeds are for loading and unloading filament. I agree, there are too many different high speeds available. The 5mm/sec and 10mm/sec speeds are reasonable if using 1.75mm filament, and possibly also 20mm/sec with a Volcano hot end and large nozzle. For 3mm filament with a regular size nozzle, I can see that you would need lower speeds.
-
Maybe a json config file?
I'm no web dude, but I was curious enough to search for "json config".
This webdude says please don't:
https://arp242.net/weblog/json_as_configuration_files-_please_dontThe rationale seems solid: apparently there's no way of commenting json config files. He does suggest alternatives however.
+1 for the feature though - I used a macro as a workaround while setting up for 2.85mm filament fed at 1mm/s max.
-
Maybe a json config file?
I'm no web dude, but I was curious enough to search for "json config".
This webdude says please don't:
https://arp242.net/weblog/json_as_configuration_files-_please_dontThe rationale seems solid: apparently there's no way of commenting json config files. He does suggest alternatives however.
+1 for the feature though - I used a macro as a workaround while setting up for 2.85mm filament fed at 1mm/s max.
Honestly json is fine for what's needed. No need for the user to manually edit it at all and it's easy to parse locally. In theory it would be called through an Ajax request which means it's the ideal format for delivering the data on request.
-
Thanks for the info
-
Having the Web Config settings persist across browsers is a feature request for Chrishamm