DueUI: An Alternate Web Interface

gtj0

I'm writing documentation as we speak. First beta release on Saturday.

thwe

Hello Georg,

first of all many thanks for your extensive documentation and your great work.

I have now installed the DueUI on the DuetWifi and started.
I use it on a Samsung GT-N8010 (Note 10.1 inches) with Chrome as a browser.

I could already initiate the first movements. In the next weeks I will deal with the settings and the customizing of the interface.

As soon as I find my way and acquire a certain competence, I will actively participate in this project with questions and suggestions for improvement as far as my free time permits.

Have a beautiful Sunday!

gtj0

@thwe Thanks!. That's a nice tablet. Makes me sorry I sold my Nexus 10 last year.

gtj0

If no one's noticed...
https://forum.duet3d.com/topic/9257/dueui-1-0-0-alpha-is-available-for-testing

DaveA

I'll assume that I'm doing something wrong but here it is. I've got DueUI installed and it's displaying valid temperature and position information. What I cannot do is initiate any action. If I click on Home All I see a G28 in the upper text window but the printer doesn't home. Same for any other button.
Did I miss a setup step somewhere?

gtj0

@davea Check settings. You probably have "Don't Send GCode. Log Only" checked (green). For normal operation it should be off (red).

thwe

@gtj0 said in [Preview] DueUI: An Alternate Web Interface:

@davea Check settings. You probably have "Don't Send GCode. Log Only" checked (green). For normal operation it should be off (red).

… that it will be - with me all orders are executed first.

Also, I've created ATX ON / OFF buttons -> runs!

Unfortunately, the themes do not seem to be so uniform: after switching between themes, the fields are slightly shifted

Values at the heaters are only displayed as soon as I have switched on my 24V supply (ie ATX ON).

After an ATX-OFF, the status is not updated.

Depending on the theme, the key cross for XY is also shifted, the midpoints are not exactly on top of each other.
But it can also be on my 10.1 inch tablet ... no matter, you can adapt - but you should stay with a theme!

Otherwise, the beginning is really good

gtj0

@thwe said in [Preview] DueUI: An Alternate Web Interface:

@gtj0 said in [Preview] DueUI: An Alternate Web Interface:

@davea Check settings. You probably have "Don't Send GCode. Log Only" checked (green). For normal operation it should be off (red).

… that it will be - with me all orders are executed first.

Also, I've created ATX ON / OFF buttons -> runs!

The next alpha will expose the "checkbox" widget that the buttons in settings use. This way you can have a single button that toggles the ATX power state.

Values at the heaters are only displayed as soon as I have switched on my 24V supply (ie ATX ON).

After an ATX-OFF, the status is not updated.

I'll check on that today.

Unfortunately, the themes do not seem to be so uniform: after switching between themes, the fields are slightly shifted

Depending on the theme, the key cross for XY is also shifted, the midpoints are not exactly on top of each other.
But it can also be on my 10.1 inch tablet ... no matter, you can adapt - but you should stay with a theme!

Unfortunately, I have no control over the themes but I thought all of the themes except for "Base" were consistent. "Base" is basically "no theme" so the contents may shift when you switch between "Base" and any other theme. Does refreshing the browser between theme switches help at all?

For the XY Axis issue, try this for the Y axis position...

"position": {"my": "center center", "at": "center center", "of": "#jog_x" }

and see if it works. That should align the 2 center blank buttons. For me, it works on some devices but not others.

Otherwise, the beginning is really good

Thanks!

DaveA

@gtj0 Yep, that was it. Thanks.

gtj0

@davea The ATX issue is that I forgot to add a status for "O" (off) to the
status map at the bottom of the config file.

Add...

"O": {"label": "Off","style": {"background": "red","color": "black"}},

to the status_map object after the entry for "H".

thwe

@gtj0 said in [Preview] DueUI: An Alternate Web Interface:

Does refreshing the browser between theme switches help at all?

No, there are little differents from hight of Buttons and so on.
Never mind, now I use only theme BASE as my Basic.

Other feedback:
After pressing STOP, the printer stops as expected immediately - but then the DWC asks "The firmware still reports to be stopped after an emergency stop." and must be answered there - unfortunately not on DueUI. Even pressing the "RESTART" button on the DueUI does not help.

Is there a solution here?

gtj0

@thwe said in [Preview] DueUI: An Alternate Web Interface:

@gtj0 said in [Preview] DueUI: An Alternate Web Interface:

Does refreshing the browser between theme switches help at all?

No, there are little differents from hight of Buttons and so on.
Never mind, now I use only theme BASE as my Basic.

Other feedback:
After pressing STOP, the printer stops as expected immediately - but then the DWC asks "The firmware still reports to be stopped after an emergency stop." and must be answered there - unfortunately not on DueUI. Even pressing the "RESTART" button on the DueUI does not help.

Is there a solution here?

Hmmm. On my Duet, when I send M112, the Duet restarts by itself and is ready again in about 15 seconds. Try it with the DWC disconnected and see what happens on DueUI.

thwe

@gtj0 said in [Preview] DueUI: An Alternate Web Interface:

Hmmm. On my Duet, when I send M112, the Duet restarts by itself and is ready again in about 15 seconds. Try it with the DWC disconnected and see what happens on DueUI.

Without a connect from DWC to the Duet every is OK.

Other question:

with

"actions": [{"type": "gcode", "gcode": "M98 Px_macro_test01.g"}]

i can call a file, but how can i call a macro from the macro-subfolder?

... for example "\macros\Tools\Tool bed messuring 5 points"

thwe

Below I want to show you what I have created in the last few days with the DueUI.

DueUI is certainly not a replacement for DWC, but for me the ideal basis as a control panel directly on the printer.
Small netbook (without touch) was ok so far, but the operation with mouse pad was not so comfortable. Also the picture quality was not so sharp.

Desire was as much control panels by touch on little surfaceas as possible and not to lose the overview - so actually a contradiction.
Since my 10 inch tablet only serves once a year as a navigation tool on the boat, it has now got a great job again

Surely everyone has it's own idea of what an ergonomic and clear surface is, but with the DueUI you can quite well realize your own taste.
With a little bit of logical thinking, even a non-programmer like me can do something with it.

Below are a few pictures of my current state in the Chrom-browser:

Display in normal mode, axes homed, ATX ON

ATX OFF

And now in full-screen - and now the status indicator is visible

After a reboot - axes not homed and ATX OFF

Open selection menu

The operation of the axes with the jogging as a cross is closer to reality, but so the place is much better exploited - we are all professionals and come so synonymous with it

If you are interested, I will gladly provide the configuration file, but without any guarantee and with the note that certain details are adapted to MY printer and probably only usable on a 10 inch tablet.

gtj0

@thwe said in [Preview] DueUI: An Alternate Web Interface:

@gtj0 said in [Preview] DueUI: An Alternate Web Interface:

Hmmm. On my Duet, when I send M112, the Duet restarts by itself and is ready again in about 15 seconds. Try it with the DWC disconnected and see what happens on DueUI.

Without a connect from DWC to the Duet every is OK.

Other question:

with
"actions": [{"type": "gcode", "gcode": "M98 Px_macro_test01.g"}]
i can call a file, but how can i call a macro from the macro-subfolder?

... for example "\macros\Tools\Tool bed messuring 5 points"

When a macro is in a subdirectory, you have to use the full path...
M98 P"/macros/Tools/Tool bed messuring 5 points.g"

gtj0

@thwe said in [Preview] DueUI: An Alternate Web Interface:

Below I want to show you what I have created in the last few days with the DueUI.

DueUI is certainly not a replacement for DWC, but for me the ideal basis as a control panel directly on the printer.
Small netbook (without touch) was ok so far, but the operation with mouse pad was not so comfortable. Also the picture quality was not so sharp.

Desire was as much control panels by touch on little surfaceas as possible and not to lose the overview - so actually a contradiction.
Since my 10 inch tablet only serves once a year as a navigation tool on the boat, it has now got a great job again

Surely everyone has it's own idea of what an ergonomic and clear surface is, but with the DueUI you can quite well realize your own taste.
With a little bit of logical thinking, even a non-programmer like me can do something with it.

<snip>

The operation of the axes with the jogging as a cross is closer to reality, but so the place is much better exploited - we are all professionals and come so synonymous with it

If you are interested, I will gladly provide the configuration file, but without any guarantee and with the note that certain details are adapted to MY printer and probably only usable on a 10 inch tablet.

That's fantastic! It's demonstrates perfectly the whole point of DueUI: Creating something that works for YOU. Thanks for sharing it!

I was thinking of enabling the Wiki on GitHub where others could share their designs. Maybe this will be the first.

thwe

@gtj0 said in [Preview] DueUI: An Alternate Web Interface:

I tried

"actions": [{"type": "gcode", "gcode": "P"/macros/Tools/Only_a_test.g""}]

but this would not work (Syntax error of CSS) because of the double quotes

… this

"actions": [{"type": "gcode", "gcode": "P/macros/Tools/Only_a_test.g"}]

is for the CSS correctly, but the Duet can not interpret that because:
--> Error: Bad command: P/macros/Tools/Only_a_test.g

Somehow, the 2 "quotes" must be passed in the Statement within the outer quotation marks

thwe

Another Question:

Is it possible to show the value of the slider?

In my pictures you can see that I have inserted 3x? as a placeholder

gtj0

@thwe said in [Preview] DueUI: An Alternate Web Interface:

@gtj0 said in [Preview] DueUI: An Alternate Web Interface:

I tried
"actions": [{"type": "gcode", "gcode": "P"/macros/Tools/Only_a_test.g""}]

You can either escape the double quotes with backslashes:
"actions": [{"type": "gcode", "gcode": "P\"/macros/Tools/Only_a_test.g\""}]
or in javascript, single and double quotes do the same thing:
"actions": [{"type": "gcode", "gcode": "P'/macros/Tools/Only_a_test.g'"}]
or:
"actions": [{"type": "gcode", "gcode": 'P"/macros/Tools/Only_a_test.g"'}]
or if your macro path doesn't have spaces, you can leave the inner quotes off:
"actions": [{"type": "gcode", "gcode": "P/macros/Tools/Only_a_test.g"}]

BUT see below.

but this would not work (Syntax error of CSS) because of the double quotes

… this
"actions": [{"type": "gcode", "gcode": "P/macros/Tools/Only_a_test.g"}]
is for the CSS correctly, but the Duet can not interpret that because:
--> Error: Bad command: P/macros/Tools/Only_a_test.g

That's because your real issue is that you forgot the M98 GCode command at the beginning.

"actions": [{"type": "gcode", "gcode": "M98 P/macros/Tools/Only_a_test.g"}]

gtj0

@thwe said in [Preview] DueUI: An Alternate Web Interface:

Another Question:

Is it possible to show the value of the slider?

In my pictures you can see that I have inserted 3x? as a placeholder

The best way to do that right now is to have those "???" placeholders be buttons and track the state of the fanPercent values in the status message just as the slider does.

"read_only: true,
"status_level": 1,
"value": "${status.params.fanPercent[0]}",

Change "0" to correspond to each slider's value.

In the next release, I'll add the capability to have labels also track status variables.