OK, what I’ve done is create a batch of new threads under Feature Request, U1. Anyone interested in commenting or voting, follow the links below. I hope that suits.
It is not uncommon that devices on the home network offer configuration of networking: either “DHCP”, where the device obtains the credentials from a DHCP server on the network (usually provided by the router), or “Manual” where the user sets IP address, netmask, gateway, and DNS directly. Setting DHCP first, and then altering to Manual presets the netmask, gateway, and DNS fields appropriately, the user can then alter the IP address to their liking.
The advantage of this approach is to have th…
If the U1 ran zeroconf, we could address it from our web browsers as (for example) http://u1.local , instead of having to remember what IP address it is on.
Provide an option in Settings > Print Preferences to default Heated Bed Leveling to off. Heated bed levelling is time consuming, and does not need to be done every print (especially if using the same bed plate). It might not seem a long time over the course of a multi-hour print, but I’m sure I am not the only one who is not happy to let a print run unattended until they’ve seen the first layer or two go down!
As of firmware 1.4.1, the U1 defaults heated bed levelling to on, and has to be manua…
Having attempted to copy text from the scrolling Console in the Fluidd interface into a file, I can tell you it is remarkably difficult.
Please provide an option to enable and disable output of console text to a file for later analysis.
At present (1.4.1), system logs can only be exported as an encrypted file for analysis by Snapmaker Support.
The content of these logs is sure to be of interest to experienced users keen to make full use of their U1, maintain it, and perhaps experiment with it. If the data is not human readable, please provide tools to read it.
Being encrypted means users have no visibility of what information they are submitting to Snapmaker, nor what privacy implications there might be.
As of 1.4.1, G-Code files are scanned to check for validity before printing, but the validity criteria are too strict. In particular, it should be possible to omit some or all of the configuration block at the end, and have the printer adopt sensible defaults.
Toolhead Swapping Anomaly counts should be cumulative (user resettable) and accessible on a report screen in Settings > Maintenance (not just at the end of a print). Personally, I would also like to see per-toolhead retry and failed retry counts, and failed retry counts as a percentage of toolhead pick-ups.
This would enable experienced users to monitor the performance of the pogo pins and take preventative measures in a timely fashion.