Note that this version was created for Dueui 3.0.2. Because of a change in the way DWC and hence Dueui now report the object model - this version is not compatible with later versions of Dueui.
I have an Ender 5 with Duet2 Wifi. I have a Raspberry Pi with 7" TFT mounted on the Printer.
I used it to serve up a camera and provide some local control with DWS in the browser on the Pi.
This was a fairly clumsy approach because of the small screen and the lack of touch precision. So I decided to give Dueui a go.
I was after a minimal set of control for the occasions when I was standing, mesmerized, in front of the printer.
DWS on my laptop is, of course, used for more complete control.
Other considerations included:
The Screen I am using is only 800 x 600 pixels.
I did not want to have to scroll up/down or left/right.
The browser (chromium) is used in full screen mode.
Attached is the first version of my configuration.json together with some macro's that I use.
I am very happy with the results so far and look forward to improving as I go.
I will explain a little about each of the panes below.
The theme I chose is "Darkly" - other themes may affect the layout.
I trimmed the menu bar at the top to make it fit better.
I placed the log / status just above the menu tabs.
Most everything else fits in between.
In V3 - I added output for M117 Messages (not shown in the screen shots) because I liberally sprinkle messages in my macros and gcode.
This is a really just intended for basic monitoring, stop / start etc.
Because I like to see Nozzle and Bed Temperature that is included.
Babysteps are small i.e. assumed the printer is more-or-less calibrated.
The intent here is to provide simple calibration control and monitoring.
I use a Z-Probe (BLTouch) so bed calibration is automagic. The "Calibrate" button calls a macro () that does all the work.
Since I often change hotends - the Z axis offset can change so I have included a capability to measure the offset.
The "Z Adjust Start" button calls a macro () to setup for adjustment using one of the standard techniques.
It first homes all - so after that has happened you can go ahead and adjust the nozzle to the bed to "paper thickness".
When done - pressing the "Done" button performs a single probe (and another home all just because).
The Z offset is reported in the log / status bar and can then be used to adjust your G31 settings.
No changes here - just copied from the sample config file.
Edit - Made some changes so as not to need keyboard and posted as V2. Removed the need for a keyboard
I mainly use this for filament changes and such. Heat up the nozzle etc.
I personally do not use standby and such. In any case, wanted to "unclutter' the UI for this screen.
The config file comments out a second row of nozzle temps and Fan 0 these can be added back in easily if you want.
There is also a control to reposition the bed (Z axis) to specific positions (useful for getting access to the bed).
More or less the same as the sample config file.
NOTE THE FILENAMES GET CHANGED DURING DOWNLOAD SO YOU WILL NEED TO RENAME THEM BACK TO THE ORIGINAL
@stuartofmt Yeah that's kind of the logic I use but there's a chicken and egg thing going on because you have to find a config file before you can get the settings out of it but you have to have some settings already to know where to look.
I think I have it working now but I'm going to wait until tomorrow and test it again before doing a beta3.
I obviously got side-tracked with polling not being "On" and the non-error error messages.
I went back to the nginx setup on the raspberry pi and "ta-da"
Of course there is always cookies ... and why it would not remember the configuration.
My default browser settings are to delete cookies on exit .... when I realized, I added an exception for localhost. So all is well.
This is a terrific piece of work ! Because the Touch Screen on the Pi (7") is "real estate challenged" and struggles with the example, default layout - I will need to work on my own, config. In any case, I want to make it quite minimal since my intention is just to have an essential "next to printer" experience.
When I have something reasonable - I'll post it in the appropriate discussion.
@hauschka Sure! The website that serves the UI, the website that serves the config file, and the Duet itself can all be configured separately.
The website that serves the UI is the URL you enter in the browser's address window. The website that serves the config file is configured in DueUI's Settings page under "DueUI config file URL". The address of the Duet itself (or the RPi/SBC) is configures in DueUI's Settings page under "Duet hostname or IP address:" or "SBCt hostname or IP address:" depending on whether you're directly connecting to the Duet or the SBC.
So you can certainly have the UI and config file served from the same web server. The path to the config file auto populates with a default if its empty but you can change that and it will be saved.
@CCS86 You probably want the Standalone zip instead of the DSF release unless you are actually running a web server on another computer. Make sure you have Standalone set on the settings page and make sure the URL in "DueUI config file URL" is correct. You can put that URL in any web browser to test. You should also use the DuetWebControl to make sure there's a dueui_config.json file in the /sys directory of the Maestro.