Thanks for the quick answer!
That helped but was not everything I needed. I also had to add crc32appender to my PATH. I did that but eclipse did not add make use of this information so I added the path to the file in the "Properties" of the project (see screenshots). I'm not sure if this is how it's supposed to be done but it worked for me.
Is there a way to adjust the size of the images as they are represented here?
Greetings Daniel
Hey,
I'm trying to compile the RepRap firmware 3.2.2 my self. I've read the build instructions several times and I've gotten less and less error messages but I still can't compile the firmware.
I've downloaded all projects for version 3.2.0 except the firmware which is release 3.2.2.
Does anyone have a pointer?
Greetings Daniel
Hey I upgraded my Duet 6HC + SBC t to the beta firmware because I wasn't able to upgrade.
I did this by
sudo curl https://pkg.duet3d.com/duet3d-unstable.list -o /etc/apt/sources.list.d/duet3d.list
sudo apt-get update
sudo apt-get upgrade
sudo curl https://pkg.duet3d.com/duetcontrolserver.service -o /usr/lib/systemd/system/duetcontrolserver.service
sudo systemctl daemon-reload
Doing so I got the following log and error but it still seemed to work:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
duetcontrolserver duetruntime duetsd duetsoftwareframework duettools duetwebcontrol duetwebserver reprapfirmware
8 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 33.5 MB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://pkg.duet3d.com unstable/armv7 armhf duetsoftwareframework armhf 3.2.0-beta2 [2,030 B]
Get:2 https://pkg.duet3d.com unstable/armv7 armhf duetsd all 1.1.0 [2,102 B]
Get:3 https://pkg.duet3d.com unstable/armv7 armhf duettools armhf 3.2.0-beta2 [61.8 kB]
Get:4 https://pkg.duet3d.com unstable/armv7 armhf duetcontrolserver armhf 3.2.0-beta2 [221 kB]
Get:5 https://pkg.duet3d.com unstable/armv7 armhf duetruntime armhf 3.2.0-beta2 [28.8 MB]
Get:6 https://pkg.duet3d.com unstable/armv7 armhf duetwebserver armhf 3.2.0-beta2 [84.0 kB]
Get:7 https://pkg.duet3d.com unstable/armv7 armhf duetwebcontrol all 3.2.0-beta2 [3,504 kB]
Get:8 https://pkg.duet3d.com unstable/armv7 armhf reprapfirmware all 3.2.0-beta2-1 [875 kB]
Fetched 33.5 MB in 3min 34s (156 kB/s)
Reading changelogs... Done
(Reading database ... 98361 files and directories currently installed.)
Preparing to unpack .../0-duetsoftwareframework_3.2.0-beta2_armhf.deb ...
Unpacking duetsoftwareframework (3.2.0-beta2) over (3.1.1) ...
Preparing to unpack .../1-duetsd_1.1.0_all.deb ...
Unpacking duetsd (1.1.0) over (1.0.6) ...
Preparing to unpack .../2-duettools_3.2.0-beta2_armhf.deb ...
Unpacking duettools (3.2.0-beta2) over (3.1.1) ...
Preparing to unpack .../3-duetcontrolserver_3.2.0-beta2_armhf.deb ...
Unpacking duetcontrolserver (3.2.0-beta2) over (3.1.1) ...
Preparing to unpack .../4-duetruntime_3.2.0-beta2_armhf.deb ...
Unpacking duetruntime (3.2.0-beta2) over (3.1.1) ...
Preparing to unpack .../5-duetwebserver_3.2.0-beta2_armhf.deb ...
Unpacking duetwebserver (3.2.0-beta2) over (3.1.0) ...
Preparing to unpack .../6-duetwebcontrol_3.2.0-beta2_all.deb ...
Unpacking duetwebcontrol (3.2.0-beta2) over (3.1.1) ...
Preparing to unpack .../7-reprapfirmware_3.2.0-beta2-1_all.deb ...
Unpacking reprapfirmware (3.2.0-beta2-1) over (3.1.1-1) ...
Setting up duetruntime (3.2.0-beta2) ...
Setting up duetcontrolserver (3.2.0-beta2) ...
Installing new version of config file /opt/dsf/conf/config.json ...
Creating group dsf with gid 995.
Creating user dsf (n/a) with uid 995 and gid 995.
Setting up duettools (3.2.0-beta2) ...
Setting up duetwebserver (3.2.0-beta2) ...
Setting up duetsoftwareframework (3.2.0-beta2) ...
To modify config files consider adding yourself to the dsf groupd: # usermod -a -G dsf <username>
Setting up duetwebcontrol (3.2.0-beta2) ...
Setting up duetsd (1.1.0) ...
Setting up reprapfirmware (3.2.0-beta2-1) ...
Sending update request to DCS... Error: Failed to send update request
Unhandled exception. DuetAPIClient.InternalServerException: ArgumentNullException in Code: Value cannot be null. (Parameter 'input')
at DuetAPIClient.BaseConnection.PerformCommand[T](BaseCommand command, CancellationToken cancellationToken) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetAPIClient/BaseConnection.cs:line 190
at DuetControlServer.Program.CheckForAnotherInstance() in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/Program.cs:line 305
at DuetControlServer.Program.Main(String[] args) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/Program.cs:line 84
at DuetControlServer.Program.<Main>(String[] args)
After running into some Problems I would like to downgrade back to the stable version.
I tried so by repeating the code from above and changing unstable to stable but Running sudo apt-get update I get the following error
E: Type '<!DOCTYPE' is not known on line 1 in source list /etc/apt/sources.list.d/duet3d.list
E: The list of sources could not be read.
So next I tried to reflash the SD card. This method resulted in me not being able to connect to DWC. I guess due to version incompatibility. Running sudo journalctl -u duetcontrolserver -e leads to the following output.
Oct 29 14:45:23 duet3 DuetControlServer[2630]: Written by Christian Hammacher for Duet3D
Oct 29 14:45:23 duet3 DuetControlServer[2630]: Licensed under the terms of the GNU Public License Version 3
Oct 29 14:45:24 duet3 DuetControlServer[2630]: [info] Settings loaded
Oct 29 14:45:25 duet3 DuetControlServer[2630]: [info] Environment initialized
Oct 29 14:45:25 duet3 DuetControlServer[2630]: [fatal] Could not connect to Duet (Invalid protocol version 3)
Oct 29 14:45:25 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
Oct 29 14:45:30 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=5s expired, scheduling restart.
Oct 29 14:45:30 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 67.
Oct 29 14:45:30 duet3 systemd[1]: Stopped Duet Control Server.
Oct 29 14:45:30 duet3 systemd[1]: Started Duet Control Server.
Oct 29 14:45:31 duet3 DuetControlServer[2644]: Duet Control Server v3.1.1
Oct 29 14:45:31 duet3 DuetControlServer[2644]: Written by Christian Hammacher for Duet3D
Oct 29 14:45:31 duet3 DuetControlServer[2644]: Licensed under the terms of the GNU Public License Version 3
Oct 29 14:45:32 duet3 DuetControlServer[2644]: [info] Settings loaded
Oct 29 14:45:33 duet3 DuetControlServer[2644]: [info] Environment initialized
Oct 29 14:45:33 duet3 DuetControlServer[2644]: [fatal] Could not connect to Duet (Invalid protocol version 3)
Oct 29 14:45:33 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
Oct 29 14:45:38 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=5s expired, scheduling restart.
Oct 29 14:45:38 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 68.
Oct 29 14:45:38 duet3 systemd[1]: Stopped Duet Control Server.
Oct 29 14:45:38 duet3 systemd[1]: Started Duet Control Server.
Oct 29 14:45:39 duet3 DuetControlServer[2659]: Duet Control Server v3.1.1
Oct 29 14:45:39 duet3 DuetControlServer[2659]: Written by Christian Hammacher for Duet3D
Oct 29 14:45:39 duet3 DuetControlServer[2659]: Licensed under the terms of the GNU Public License Version 3
Oct 29 14:45:40 duet3 DuetControlServer[2659]: [info] Settings loaded
Oct 29 14:45:40 duet3 DuetControlServer[2659]: [info] Environment initialized
Oct 29 14:45:40 duet3 DuetControlServer[2659]: [fatal] Could not connect to Duet (Invalid protocol version 3)
Oct 29 14:45:41 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
Oct 29 14:45:46 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=5s expired, scheduling restart.
Oct 29 14:45:46 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 69.
Oct 29 14:45:46 duet3 systemd[1]: Stopped Duet Control Server.
Oct 29 14:45:46 duet3 systemd[1]: Started Duet Control Server.
Oct 29 14:45:46 duet3 DuetControlServer[2670]: Duet Control Server v3.1.1
Oct 29 14:45:46 duet3 DuetControlServer[2670]: Written by Christian Hammacher for Duet3D
Oct 29 14:45:46 duet3 DuetControlServer[2670]: Licensed under the terms of the GNU Public License Version 3
Oct 29 14:45:48 duet3 DuetControlServer[2670]: [info] Settings loaded
Oct 29 14:45:48 duet3 DuetControlServer[2670]: [info] Environment initialized
Oct 29 14:45:48 duet3 DuetControlServer[2670]: [fatal] Could not connect to Duet (Invalid protocol version 3)
Oct 29 14:45:48 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
Oct 29 14:45:53 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=5s expired, scheduling restart.
Oct 29 14:45:53 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 70.
Oct 29 14:45:53 duet3 systemd[1]: Stopped Duet Control Server.
Oct 29 14:45:53 duet3 systemd[1]: Started Duet Control Server.
Oct 29 14:45:54 duet3 DuetControlServer[2685]: Duet Control Server v3.1.1
Oct 29 14:45:54 duet3 DuetControlServer[2685]: Written by Christian Hammacher for Duet3D
Oct 29 14:45:54 duet3 DuetControlServer[2685]: Licensed under the terms of the GNU Public License Version 3
Oct 29 14:45:55 duet3 DuetControlServer[2685]: [info] Settings loaded
Oct 29 14:45:56 duet3 DuetControlServer[2685]: [info] Environment initialized
Oct 29 14:45:56 duet3 DuetControlServer[2685]: [fatal] Could not connect to Duet (Invalid protocol version 3)
Oct 29 14:45:56 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
Oct 29 14:46:01 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=5s expired, scheduling restart.
Oct 29 14:46:01 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 71.
Oct 29 14:46:01 duet3 systemd[1]: Stopped Duet Control Server.
Oct 29 14:46:01 duet3 systemd[1]: Started Duet Control Server.
Oct 29 14:46:02 duet3 DuetControlServer[2699]: Duet Control Server v3.1.1
Oct 29 14:46:02 duet3 DuetControlServer[2699]: Written by Christian Hammacher for Duet3D
Oct 29 14:46:02 duet3 DuetControlServer[2699]: Licensed under the terms of the GNU Public License Version 3
Oct 29 14:46:03 duet3 DuetControlServer[2699]: [info] Settings loaded
Oct 29 14:46:04 duet3 DuetControlServer[2699]: [info] Environment initialized
Oct 29 14:46:04 duet3 DuetControlServer[2699]: [fatal] Could not connect to Duet (Invalid protocol version 3)
Oct 29 14:46:04 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
I've since gone back to the unstable branch and have been able to connect to the web interface again. But I would still like to downgrade to the stable version.
I'm still on 3.1.1 and I'm still having issues with the the M291 command. Here is the macro I'm trying to run:
; ToDo check Temp of bed and nozzle, so both are cold
; Cancel any currently active mesh compensation
M561
; Set z-probe trigger height to 0
G31 Z0
G1 X0 Y0 Z200 F6000
M291 P"Move to point were the z probe shall be calibrated." X1 Y1 S2
M291 P"Get a 0.1 mm thick metal spacer" S2
while iterations <= 5
G1 Z50
M291 P"Remove the z probe sensor if it is already or still attached" S2
G1 Z5
M291 P"Move FFF nozzle down until it just grabs a 0.1 mm thick metal spacer and then remove it." Z1 S2
G92 Z0.1
G1 Z50
M291 P"Attach the z probe" S2
G30 S-1
M291 P"Now calculate the average of the test. The average is the z probe trigger height for that point. Set it the config.g with G31 Z{ave} " S2
After I click OK from the first M291 in line 7 the machine just stays busy and the second window does not open.
Hey, sorry for the late reply.
I tried your code again and changed the axes but it still does not work.
G28V
while iterations < 10
G1 X0 Y0 Z50 F6000
G1 F{6000+iterations*2000}
while iterations <5
G1 V-150
G1 V150
The result in the console is:
Failed to execute G1 in test: [ArgumentException] Cannot convert F parameter to float (value {6000+0*2000})
The problem is no longer relevant to me but there may still be a bug here which needs fixing.
Thanks, I thought I tried that but I my M92 command was missing the V infront of the zero.
Thanks!
Hey, I have a quick question. I have a rotational axis on my printer which does not have any endstops. What can I do to execute "G28" without getting an Error?
I know that I can execute G28 for the individual axes but I would like to solve this problem at the root and not just work around it.
I've set up the endstop with
M574 V0
but that does not help.
Sorry for being no specific enough. Line 4 is not working. Thus the feedrate always stays at F6000 from the command in line 3. I've tried echoing the calculation inn line 4 and it works. But the combination with the G1 command does not seem to work.
Hey, I have a quick question.
I'm trying to write a loop were in each loop iteration the set feedrate increases.
My current approach is the following, but this isn't working. Does anyone have any pointers?
while iterations < 10
G28 U
G1 U180 F6000
G1 F{6000+iterations*2000}
while iterations <5
G1 U56
G1 U304
I've tried replacing the {} with () or [] but did not have any success.
@chrishamm Hmm.. I'm actually on 3.1.1. I did not yet do the update to the beta Version. Might there be something else that I'm doing wrong?
No, think more along the lines of a two individual tools (e.g. normal nozzle and maybe a laser) that rotate around the center of a delta effector.
Hey, I have a quick question,
I have 2 rotational axes which are linked, meaning if I want to turn one I wall also move the other. Both are driven by one stepper. But I will always just "use" one at a time. Yet I need to home both of them individually to account for possible belt slippage (the construction isn't very stiff) and I would also like the position of one to be updated if the other moves.
Is this possible with individual axes as configured by M584? The idea would be to map the same drive to both axes . Then I would home both axes normally. The tricky part would be updating the position of one axis if the other moved. One thought would be to insert a macro before I "switch" between both axes and calculate the position of the axis which will be active next based on the position which is active currently. I'm not sure if I can achieve this with gcode meta commands.
Or do I need to make an individual kinematics file?
What are your thoughts on this?
Thanks for the quick reply, before I do that, I would also like to know what I need to do to go back to the stable branches?
How does one go about updating the Duet 3 with a SBC to beta software? The getting started page does not mention anything about that.
Hey guys,
I'm having trouble using the m291 command.
My setup is a Duet 3 6HC + a Duet 3HC expansion shield and a RPI setup as a SBC.
I'd like to run the following macro, but when the message shows up and I click ok the code after the m291 command is not executed. The message then goes away but the printer says it's busy. The same happens when I click cancel.
if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
G28
G1 Z350 F4000
M291 P"The bed will home next. Remove all object from the bed!" R"Warning" S3
G1 Z 300
M98 P"homew.g"
@bearer Thanks for the answer, I missed that!
Greetings
Daniel
Hi there,
II have a quick question, I was wondering how or if the Duet 3 6HC makes use of the over temperature sensing of the TMC 5160. Based on the data sheet (p.55 and p.78) there is a pre warning if the TMC 5160 senses a chip temperature of more then 120 °C.
Q1: Is this pre warning forwarded to the user interface?
And then the chip goes into thermal shutdown at a selectable temperature of 136°C / 143°C / 150°C.
Q2: At what temperature will the drivers on the Duet 6HC go into thermal shutdown?
Thanks for the help.
Greetings
Daniel