Raise3D UI on Duet



  • Hello,

    Does anyone has already build or does the Duet (& PanelDue) has the possibility to change the web interface (easily…)?
    I found the Raise3D UI very user friendly and nice. So I wonder if we can port it to our Duet systems.
    What do you think ?



  • is the source released as open source or an open source compatible license?



  • The firmware on the board and the existing web interface are open source. Several people have written alternatives.

    Do be aware that the protocol between board<>web is changing between Duet2 firwmare vs. Duet3 firmware running on a Duet 3 hardware board. The former uses HTTP polling and the latter uses websockets. Still, all open source. You just need to make a decision as to which you support, or both.

    Also, all the payloads are JSON, so they are almost self documenting. For example:

    {"status":"I","heaters":[20.1,19.8],"active":[0.0,0.0],"standby":[0.0,0.0],"hstat":[2,2],"pos":[0.000,0.000,615.910],"machine":[0.000,0.000,615.910],"sfactor":100.00,"efactor":[100.00],"babystep":0.000,"tool":0,"probe":"0","fanPercent":[0.0,0.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0],"fanRPM":0,"homed":[1,1,1],"msgBox.mode":-1,"seq":6,"resp":""}

    I don't really need a document to figure out that machine has two heaters, their sensors currently reading 20.1C and 19.8C, and all active and standby settings are zero. I can also see that all three towers (it is a delta) have been homed. And on and on.

    Summary: It is as easy or hard as you make it.



  • I would love the PanelDue UI to looke something like the one on Raise3D's newer machines, with the model preview, progress visualization and all that.

    Without having any idea of how it's coded etc. is it any direct reason (harware or software side) that would make it hard or impossible to achieve this?



  • The pane due has very limited resources and doesn't have dynamic configuration capability. You'd have to write/modify the firmware.

    If you have a tablet, even a cheap one, check out https://github.com/gtjoseph/DueUI
    I wrote it specifically to provide customizable user interface that could be optimized for tablets. I'm in the process if updating it for RRF3 and should have the first beta of the update ready on Monday.



  • @Exerqtor said in Raise3D UI on Duet:

    I would love the PanelDue UI...

    How about a Pi, or other single-board-computer, with a touchscreen, running full DWC? That takes only minutes to setup.



  • @Danal

    Uhm what? I think you totally missunderstood what i said in my last post.


  • administrators

    @Exerqtor said in Raise3D UI on Duet:

    I would love the PanelDue UI to looke something like the one on Raise3D's newer machines, with the model preview, progress visualization and all that.

    Without having any idea of how it's coded etc. is it any direct reason (harware or software side) that would make it hard or impossible to achieve this?

    Yes it's impossible on PanelDue because it has very limited resources. But we will provide those things on Duet 3 via the attached RPi.



  • @dc42 said in Raise3D UI on Duet:

    @Exerqtor said in Raise3D UI on Duet:

    I would love the PanelDue UI to looke something like the one on Raise3D's newer machines, with the model preview, progress visualization and all that.

    Without having any idea of how it's coded etc. is it any direct reason (harware or software side) that would make it hard or impossible to achieve this?

    Yes it's impossible on PanelDue because it has very limited resources. But we will provide those things on Duet 3 via the attached RPi.

    I thought that was the case since it haven't been done yet.

    But that will only be avalible with the Duet3 and not as a retrofit for the Duet2?



  • @Danal said in Raise3D UI on Duet:

    @Exerqtor said in Raise3D UI on Duet:

    I would love the PanelDue UI...

    How about a Pi, or other single-board-computer, with a touchscreen, running full DWC? That takes only minutes to setup.

    A cheap tablet works for DWC as well.



  • This has become sort of spread out across a bunch of posts. Let me summarize, (I realize that probably a lot of people already know this... but for anyone trying to figure it all out):

    Duet 2 can be on a WiFi or Ethernet network (depending on hardware model). Duet 3 can be on WiFi or Ethernet or anything else supported by the ribbon-cable-attached Single Board Computer (i.e. Pi) that is part of the Duet 3 architecture. (It is also possible to run a D3 'stand alone', meaning with no attached SBC. I'm going to ignore that for right now).

    Once your Duet 2 or 3 is on a network, then anything that can run a browser can present DWC (the Duet Web Control) interface. This could be a PC, a Tablet, a Phone, etc, etc. This can be on a desktop, or attached to the frame of the printer, or wherever. With appropriate security and proxy setup, this could transit the internet and be anywhere on the planet.

    A PanelDue can be plugged into a Duet 2 or 3; this is a "TTL Serial" connection and does not use any form of WiFi or Ethernet. As such, it can run on a few meters of cable, but not hundreds of meters. The PanelDue itself can have any of several sizes of touchscreen. The UI on a PanelDue is designed to operate the printer, and has several limitations as compared to 'full' DWC.

    All above is the same (or very close) for D2 or D3.

    A Duet 3 with attached Single Board Computer (that is, a Pi) offers one more option: The Pi will be running DWC on its HDMI terminal session. Therefore, any combination of mouse/pad, keyboard, display will present a 'full' DWC interface. This includes any of the many touchscreens already made for Pi that emulate mouse/keyboard via touch. Given that the Pi must be ribbon cabled to the Duet 3, and that the Touchscreen must be HDMI cabled + USB (typically) to the Pi, it makes most sense for this setup to be physically on the printer.

    As long as the above is, it is still very summarized. Hopefully it is reasonably accurate; corrections are certainly welcome.


Log in to reply