DueUI Release 3.0.1-beta2 Available

gtj0

@DaBit That could be really interesting. None of the actual UI stuff would need to change at all. It'd be just adding another backend that implements the same contract that the other two do. I'll look into it!

DaBit

I skimmed through the code, and if you add a third backend for serial which emits M408 and reads the response it should work. Don't ask me how to do that; I never did serious Javascript before.

However, I do have the serial line coming from the PanelDue connector connected to the Pi, so I can test. And setting up the build environment would be possible too.

I just set DueUI up on the Pi + 7" Pi screen on the printer.

alt text

Of course I have to configure it. I do get the basic idea of how to do that. However, a few things:

The camera image is not refreshing. DWC reloads the image every X milliseconds, DueUI does not. Not a big issue; having the camera image taking up real estate on the 7" Pi screen while I only have to look up 30cm to have a real view makes no sense.
Current/last file says 'unknown'. Which makes sense if I look at the config, line 355 of dueui_config_default_standalone.json. Isn't the real current filename available somewhere (I am not seeing it in a M408 response either)?

"value": "Current/Last File:  ${state.status == 'P' ? 'unknown' : 'Not printing'}",

Time and times left stay at 0:00:00. In the config the calculated values are commented out, but the referenced values seem OK. Still a beta thing?

A Former User

Maybe I'm missing something, but how would this make the paneldue any more functional than it already is on IO0? I.e. you cannot start jobs from SD. (you could probably execute macros or console commands to start prints, but the paneldue cannot list the fake sd card on the pi)?

gtj0

@DaBit :

How is the webcam sending the stream? As Motion JPEG or something else? If it's just a jpeg that the webcam regenerates, I may have to add a refresh parameter. Also check if the webcam can support other types of output.

The M408 responses and the ones you get by http://<duet>/rr_status?type=3 are actually different. Browse to the rr_status page and you should be able to pick out the fields you want, then you can just substitute them on your config file. I'll look at that again though. At one point I was using the M409 command to get the object model but it's not complete. I might have missed changing it back to rr_status.

gtj0

@bearer said in DueUI Release 3.0.1-beta1 Available:

Maybe I'm missing something, but how would this make the paneldue any more functional than it already is on IO0? I.e. you cannot start jobs from SD. (you could probably execute macros or console commands to start prints, but the paneldue cannot list the fake sd card on the pi)?

Well, it's not ever going to make the panel due more functional and we're talking in a standalone mode for serial connection, not SBC/DSF. There's no real point to DueUI connecting in serial mode in the SBC/DSF environment because you can run DueUI in a browser on the SBC. In a standalone environment though, you could run DueUI (with modifications) on a non-networked laptop and just connect to the Duet via a USB connection or direct serial-to-serial.

gtj0

@DaBit I've added a "refresh_seconds" parameter to the image widget. It'll be in the next beta.

gtj0

Oh, I've also noticed that there's a slight delay before the values are populated from the object models resulting in the expressions appearing in widgets instead of the values for a brief time. That just started happening so it must be something I just did.

DaBit

@gtj0 said in DueUI Release 3.0.1-beta1 Available:

How is the webcam sending the stream? As Motion JPEG or something else? If it's just a jpeg that the webcam regenerates, I may have to add a refresh parameter. Also check if the webcam can support other types of output.

I am using RPi-Cam-Web-Interface. It probably does support output other than a static jpeg frame, but one image every 10 seconds or so is fine for me. On a 3D printer not that much is happening in 10 seconds, and a lower update rate saves bandwidth in case I just want to check if everything still runs fine through a mobile connection when abroad.

@gtj0 said in DueUI Release 3.0.1-beta1 Available:

@DaBit I've added a "refresh_seconds" parameter to the image widget. It'll be in the next beta.

Great!

@gtj0 said in DueUI Release 3.0.1-beta1 Available:

Oh, I've also noticed that there's a slight delay before the values are populated from the object models resulting in the expressions appearing in widgets instead of the values for a brief time. That just started happening so it must be something I just did.

The current beta also does that.

I tried using DueUI running on the Pi yesterday evening, but I had some more issues:

After I pressed 'home all' it took several seconds before the printer reacted.
Jogging Z (after homing) did not work.

I did not dive into it but switched to DWC; I had work to do. Will check more thoroughly soon.

gtj0

What's New in 3.0.1-beta2

Fixed issue with fields showing the format instead of value

When first started or refreshed, the UI could display format
strings like "${state.heat.heaters[1].current.toFixed(1)}" for a
short time instead of the actual value. This was due to the model
not being populated before the UI elements. Now we populate the
model before showing the UI.

Minor backend refactoring

Add refresh_seconds to the Image widget

Some WebCams only provide an image snapshot instead of
a live MJPEG stream. If you have one, you can now set
"refresh_seconds" to control how often the image should
be refreshed.

DaBit

Nice!
I will update, and see how it works.

bastien

hi, i'm error ERROR! ERROR! ERROR!
404 - The requested file could not be found.
i'm install zip and i try to connect to ip-printer/multi.htm

gtj0

@bastien First, I'd try the latest release. Second, I have no idea what "multi.htm" is.

Dr_Ju_Ju

Good day George,

Thanks for your work, and like you I also find the DWC far too overblown\complicated and just require a much simpler interface, more like Octoprints 'cleaner' interface (which isn't ideal by any means), so I thought I'd give your interface a try.....

I downloaded the latest (3.2.0 - standalone) & dropped the zip file into the DWC sys ui, and everything unpacked as expected to the root of the www directory, but, the 2 config json files were not copied over to the www root, is this correct ? I suspect not, as on connecting to dueui.html i can see the config screen but saving any config changes nothing is retained....

If I move the files over to the root of www, I can now see updates to the json files, but all I get after that is the config screen and nothing else, no other displays, any hints on what I've done wrong ??

gtj0

@Dr_Ju_Ju The json files are copied to the sys directory since they're config files that can be edited instead of static files.

Can you paste a screen shot of your settings page? Also, while on the settings page, right click in any blank area and click "Inspect". This should open the debugger window. Then go back to the settings page and do a refresh and see what happens in the debugger.

Dr_Ju_Ju

As requested a picture of settings page (using Firefox)

Screenshot_2021-02-16 DueUI - dbot jules home.png

On selecting a different theme for the page, the theme changes, then subsequently selecting\deselecting any of the 4 'red' buttons, highlights appropriate selections within the inspect window, and the refresh button refreshed the window...

But selecting 'save' appears not to do anything, and 'inspecting' pushing the button also shows no changes.

gtj0

@Dr_Ju_Ju For standalone mode...

Make sure that the dueui_config_default_standalone.json file exists in the /sys directory. That's where it should be, If not, you can unzip the DueUI zip file locally and and can upload the JSON yourself from DWC. The "DueUI config file URL" should then be http://dbot.jules.home/rr_download?name=/sys/dueui_config_default_standalone.json. Then click save and refresh and see what happens. If you have a custom file already, just upload it to /sys and replace dueui_config_default_standalone.json in the URL with your file name.

As a test, you should be able to paste that link in your browser and get the JSON file.

Dr_Ju_Ju

Yes the file is in the /sys directory,,,,, If I enter the URL you posted, I get the config file which I can download\edit and I can also edit the file using the normal DWC sys edit tool....

But clicking on 'save' still does nothing, and looking at the json file I see no changes being applied, even if just for a theme change...

These are the class DuiUisettings in the json file, but one thing I noticed is that there are no settings for the local host and config json, is this correct ??

/*
class DueUISettings {
backend_type = "STANDALONE";
duet_debug_polling_enabled = 0;
duet_password = "";
duet_poll_interval_1 = 500;
duet_poll_interval_2 = 0;
duet_poll_interval_3 = 3000;
duet_polling_enabled = 1;
dueui_settings_dont_send_gcode = 0;
dueui_test_mode = 0;
theme = "Sandstone";
}
*/

gtj0

@Dr_Ju_Ju OK, That DueUISettings class is commented out. It's there as an example only.

Let's start over...

Navigate to http://dbot.jules.home/dueui.html
In your browser settings, clear the cookies and local storage for http://dbot.jules.home
Use your browser's refresh button (F5 on Chrome and Firefox) to reload.
Enter the correct info on the DueUI settings page.
Open the browser's debugger window.
Click Save, then Refresh in the DueUI settings page.

gtj0

@gtj0 OH... You have to turn polling on before you press refresh or you'll just come back to the settings screen.

Sorry, should have mentioned that.

Dr_Ju_Ju

Thank you getting closer, at least turning on polling means I can get past the initial config screen, but only for that session, as nothing is saved back to the json config file, including a change to the theme....

And some things aren't working, e.g. the webcam I have working in the DWC is not showing, how to configure separately ? & the height map isn't showing, and my case lights scripts are displayed but they don't work..

But as nothing is saved to the config file, does that mean I will have to re enter the config url for each browser instance I open, on each computer I try & open the UI on ??