RPI are supporting docker containers and there is a general trend towards containerization.
Wouldn't it be nice if DCS DWC and DWS are running in on a docker container?
Did somebody tried something similar?
What is your opinion about that? Do you see more advantages or disadvantages?
@Phaedrux It's just that often I am not finding what I am searchingt for.
Probably I am using the wrong search terms, but to give you example search for term like,
"5v power supply problem"
"Changing ports of DWS"
"Wiring neopixel"
and 95% of the posts which will be shown are not really correlated to what I am searching for.
My personal experience is that the search function in this forum is very limited. Most of the time I find the right forum post rather when I go back to Google and search there.
Does anyone have any idea what the technological problem is? Would something like "tagging" be useful?
And the STEP fieles ofat least 1.0
here https://github.com/Duet3D/Duet3-Mainboard-6HC/tree/master/Duet3_Mainboard_v1.0
@TLAS Thanks fo the hint.
I found the schematics in https://github.com/Duet3D/Duet3-Mainboard-6HC/blob/master/
Does a free CAM/CAD model of the Duet3 MB6HC exist anywhere?
and second question:
Does somebody has created a fusion 360 electronic library block for the Duet? I would like to use it for my circuit plan.
@chrishamm Ok? That's interesting. I used http://192.168.1.7:1000/ and checked that it was http and it did not work.
Changed my config back by removing the port. Restarted Server -> worked again.
@chrishamm recommended me for another problem to change my DWC port.
I changed
/opt/dsf/conf/http.json
into
...
"Kestrel": {
"Endpoints": {
"Http": {
"Url": "http://*:1000"
}
}
...
but after an restart, even if I was able to connect to //my:1000 and DWC was responding, the DWC is not able to connect to the Duetboard.
Is there a second config file which I have to change?
Setup:
SW 3.2 Duet3
not standalone mode
@Matthieu Hey Matthieu,
I am doing something similar, I am running NodeJs frontend on the RPI and then I use the PythonApi from @wilriker https://github.com/Duet3D/DSF-APIs
in a FLASK based (Python) backend to communicate with the Duet.
Would this be a way that would work for you?
@Phaedrux I thought that it helped to reinstall everything. First everthing worked well, but after configuring my RPI in the way I typically use it, i got the same problem again.
But I was able to find the point where something is going wrong.
What I have done:
Completly new image on SD card (v3.2). Everything worked correctly: DWS webpage is shown correctly in my network.
I want to run another Singlepage-Application an the RPI therefor I install nodejs with the following command
sudo apt-get install -y nodejs npm
and after finishing the installation, something is wrong with the Appache-Server (?).
Results:
And I get my old error message: "Apache2 default message"
Question:
Is there an Apache expert who has an idea?
How is it possible that the installation of nodejs is changing something that leads to my problem with the Apache?
Thanks for the hint. I have done a reinstall with a new SD-card - it worked
Hey guys,
since 3.2 i got a strange problem with DWC. The "website" is not accessable.
The RPI4 is in my network and accessible via SSH.
If i try to access over DNS (e.g. http://duet3/) or directly over the IP address the Apache server on the RPI is showing me the following message.
pi@duet3:~ $ sudo journalctl -u duetcontrolserver -f
-- Logs begin at Tue 2021-01-12 13:17:01 GMT. --
Jan 12 13:26:51 duet3 DuetControlServer[427]: Written by Christian Hammacher for Duet3D
Jan 12 13:26:51 duet3 DuetControlServer[427]: Licensed under the terms of the GNU Public License Version 3
Jan 12 13:26:52 duet3 DuetControlServer[427]: [info] Settings loaded
Jan 12 13:26:52 duet3 DuetControlServer[427]: [info] Environment initialized
Jan 12 13:26:52 duet3 DuetControlServer[427]: [info] Connection to Duet established
Jan 12 13:26:52 duet3 DuetControlServer[427]: [info] IPC socket created at /var/run/dsf/dcs.sock
Jan 12 13:26:52 duet3 systemd[1]: Started Duet Control Server.
Jan 12 13:26:52 duet3 DuetControlServer[427]: [info] Starting macro file config.g on channel Trigger
Jan 12 13:26:53 duet3 DuetControlServer[427]: [info] Finished macro file config.g
Jan 12 13:29:57 duet3 DuetControlServer[427]: [info] System time has been changed
Setup
RPI4 via USB and ribbon cable connected to Duet3_MB6HC
hostname: duet3
browser: chrome
Software:
pi@duet3:~ $ apt list 2>/dev/null | grep duet
duetcontrolserver/stable,now 3.2.0 armhf [installed]
duetruntime/stable,now 3.2.0 armhf [installed]
duetsd/stable,now 1.1.0 all [installed]
duetsoftwareframework/stable,now 3.2.0 armhf [installed]
duettools/stable,now 3.2.0 armhf [installed]
duetwebcontrol/stable,now 3.2.0 all [installed]
duetwebserver/stable,now 3.2.0 armhf [installed]
Any Ideas?
@NexxCat Exactly! I just want to test the REST API of the Duet Web Control without having a physical RPI.
@NexxCat thanks for the hint! I don't want to interact with the printer or the board, I just want to want to interact with Duet Web control which rans on the PI
Did somebody tried to run die Duet SBC Software (the SBC software Image from https://duet3d.dozuki.com/Wiki/SBC_Setup_for_Duet_3) in a VM?
I tried Virtualbox but didn't get it work. Does somebody knows a tutorial?
Best regards Jan
@dc42 on SD-Card/RPI (Duet 3)
I found my error, and I think its Bug from the firmware. But, the firmware experts can probably tell me if this is intended....
If i call
; first step
M42 P4 S0.0
G4 P1
M42 P4 S1.0
G4 P1
; second step
M42 P4 S0.0
G4 P1
M42 P4 S1.0
G4 P1
....
everything is fine and required only a few miliseconds. But if call macros with exactly the same content (eg. M42 P4 S1.0), the programm needs several 100ms to perform a step.
M98 P"/macros/LOW.g"
G4 P1
M98 P"/macros/HIGH.g"
G4 P1
M98 P"/macros/LOW.g"
G4 P1
M98 P"/macros/HIGH.g"
G4 P1