@o_lampe
It would be extra useful, if the background color changes (like with a zprobe) when the extruder skips steps.

@resam A capital -X works better on the wget command line. But it didn't download all the subfolders until I added -l 0.

@phaedrux In that case I sincerely hope I will never ever have to cope with whomever you label as "beginner" 😆

After deleting /opt/dsf/conf/config.json it works 🙂 Thanks!

FWIW,
'Emergency stop' means just that. Stop NOW.
What I suggested is a confirmation for a non emergency abort which is a totally different kettle of rabbits.

@khenderick said in Show M950 J-inputs:

For a more general overview, another solution could be to implement something more generic where certain entries of the object model could be persisted on the dashboard

I believe, you could poll the sensors in question with M582 in daemon.g and send an echo to your screen with the result?

@phaedrux said in what if Macros appeared in Console?:

Not a bad idea. Moved to the wishlist.

While we are talking about wishlist in macro-context:
I tested a few things in macros and from time to time I made syntax errors or typos in variable names.
A vague warning popped up in the console about these errors, not naming the macro they happened in.
Was it t#free.g, t#pre.g or t#post.g?
Happy searching...

@jameswood It would also be fantastic if the list of filaments that's displayed when clicking "Load Filement" was sorted alphabetically or something. Currently it seems to be sorted by filesize? Custom sorting would be even better, or, if we're wishing really hard, subfolders!

this was exactly what i was looking for! thank you!

I'm not sure what you mean. Are you asking for a gcode that would check if you had the most up to date version and update if available? If so, there is nothing like that at the moment.

It would be problematic because usually the firmware updates contain some changes that may require modifications to your configuration. So at the very least you would need to read the update notes before deciding to update.

Something more automated could be worked into the DWC interface, or at least link back to the github release page and notes.

Will move to the DWC wishlist.

Sorry, yes layer height.

@fcwilt got it, thanks

@OwenD said in Multiple Web Cameras:

@adamj12b
You could put the URL of the first camera in the normal DWC camera configuration and the URL of the second camera in the section that says something like "URL when image clicked"

Thats a good short term work around!

@Martin1454 said in Multiple Web Cameras:

Maybe you can run OBS stream, either on another device - Or if you have a duet 3 with an RPI, then on the RPI it self - That should be able to merge the 2 streams

I have not heard of OBS, but I will look into it and see if it could do this. I dont want to run anything too heavy on the Pi, as it will already be serving the 2 camera streams as well as taking to the 6HC and running NodeRed.

Wish I was that organizer and dedicated.. Im my own worst enemy lol

Interesting idea.

I wonder how many slicers can be configured to provide the needed information.

Frederick

@benkitesurfs I frequently open the video stream in another window. That gives me one browser window dedicated to DWC controls, and another dedicated to just the video feed.

Another option would be send gcodes for jogging directly in the "send code" prompt at the top of the DWC page.

Maybe move "Display" to the end of the list so the order of the standard entries (Files to System) isn't changed for people that have different printers with different setups? Or wholesale move it into the System section as a sub menu entry ...

@chrishamm said in Change Increments for Extrusion Rate +/- Buttons:

@CCS86 I agree, 5% is way too much but I haven't focused on this in a while. I'll reduce the step size to 1% in the next version (3.2).

Thanks!