@kipk
I have reserved one at
https://www.dold-mechatronik.de/
They expect it to be in stock next week.
@kipk
I have reserved one at
https://www.dold-mechatronik.de/
They expect it to be in stock next week.
@jay_s_uk Great tip, thank you. i will look into that.
Both that wiki and the GCode Dictionary explains thing with the term "Z leadscrews" which is correct in some hardware configurations. But it fooled me, maybe reading too quickly and not fully comprehending tings.
I propose a change to the use of "pivot point" or equivalent to make things a bit less likely to misunderstand.
Never used them, can not reach them with my fingers when mounted on my printer.
Final settings (for future use by anyone interested):
config.g
-----------------------------------------
; Drives
M584 X0:3 Y1:4 Z2 U3 V4 P3; Three axis visible
; Tools
M563 P0 D0
; Drive direction
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1
M569 P4 S1
; Steps and Speed
M92 X80.00 Y80.00 U80.00 V80.00 Z4000.00 ; Set steps per mm
M566 X900.00 Y900.00 U900.00 V900.00 Z12.00; Set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 U6000.00 V6000.00; Set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 U500.00 V500.00; Set accelerations (mm/s^2)
M906 X800.00 Y800.00 Z800.00 U800.00 V800.00 I30; motor currents (mA) and motor idle factor
M84 S30 ; Set idle timeout
; Axis Limits
M208 X0 Y0 Z0 U0 V0 S1 ; Set axis minima
M208 X600 Y400 Z100 U600 V600 S0 ; Set axis maxima
; Endstops
M574 X1 Y1 U1 V1 S0 ; Set active low and disabled endstops
homex.g
----------------------------------------
M584 X0 U3 P5; split steppers, 5 axis visible
G91 ; relative moves
G1 X-650 U-650 F450 S1 ; fast homing X and U in parallell
;G92 X0 U0 ; Make adjustments to square axis here
M584 X0:3 P3; join steppers, 3 axis visible
G90
dsmudger
I would say these are major steps
Original connectors can be forced into the Duet board, but I ended up making adapters both for the steppers and the hot end. Pictures below show before the adapters during "proof of concept phase". On the hotend it self I made a new board using experimental circuit board and matching connectors. There was too much interference in the ribbon cable for the signal from the IR board so I added an ethernet (twisted pair) cable for that.
If there are any questions I would be happy to help.
@droftarts I have limited knowledge in this area, but would it be possible by using an arduino converting it to an analog signal and use that signal as a temp sensor on the Duet?
One would then get a curve plotted in the web interface and a neat way to control an extraction fan with "temp" levels in the M106 command.
I want to share may latest project, a detachable Panel Due caring using RJ45 connectors.
I am building a Duet controlled MPCNC and to be able to move my panel due between my printer and the upcoming CNC. I used RJ45 connectors from a server room patch panel.
I have tested with different LAN cable lengths, 3 m works but not 10 m , it communicated but the touch control did not respond. 3 m will be more than enough.
The hole is for an emergency stop button to be used with the CNC. This is a prototype printed printed with a 0.6 nozzle and 0.4 layer height so it is not the prettiest print.
Happy with the solution so far.
I have upgraded my duet-controlled Cetud3d with a Hemera extruder. I have been testing how fast it can print and still have not reached its limits.
Peak speed in the PLA print below is about 250 mm/s , reported by DWC.
This is unnecessary and so much FUN
https://youtu.be/gCN8IdGvwas
@fotomas
Did a test, first layer transparent PLA layed down in a concentric pattern. On top of that black and red PLA and lastlt a black layer. All layers printed with a .4 mm nozzle and layerheight .4 mm. The coaster has a diameter of 80 mm.
There some moiré effects so there are things to improve. But as a first test I think it worked out fine.
(The text translates to "transmission interruption")
Since this is a RC2 it is probably not the time asking for new features. But this is more of an adjustment ...
Move the extrusion window a bit lower so the extruder temp can be seen while manually extruding.
@chrishamm Thank you, it may be possible then, with some luck
I will do some experiments to see how far I get.
@chrishamm Can you explan the issue with having it in stand alone mode? Is it not a just a webserver serving files?
A blazor site can be compleatly clientside. In this case it is my understanding that the only thing the DuetBoard needs to do is serve the files?
I got the idea to white a util in Blazor and put it on the duet board. In a sub or parallel folder to the DWC.
I am thinking a blazor page, without any server side parts, querying the json structure and sending some G-Codes.
Is this possible withe current firmware and are there any limitations I should be aware of?
I am trying to write an application interacting with a DuetBoard.
I have got a Working example, a .Net c# console application using DuetHttpClient.
I have two questions:
How do I get hold of an updated model after connection is established? In my code example a command must be sent ("G31") to get a populated model.
Are there any pattern/thoughts on monitoring changes in the model? Looping with a delay and sending "G31" seems crude...
I have not found any info or code on this, there probably is. So some help pointing me in the right direction would be much appreciated.
/Tomas
using DuetHttpClient;
var options = new DuetHttpOptions
{
ObserveObjectModel = true,
ObserveMessages = true,
};
var session = await DuetHttpSession.ConnectAsync(new Uri("http://192.168.0.117"), options);
await session.SendCode("G31");
var model = session.Model;
foreach (var a in model.Move.Axes)
{
Console.Write(a.Letter);
Console.Write(": ");
Console.WriteLine(a.UserPosition);
}
Console.ReadLine();
@jay_s_uk Great tip, thank you. i will look into that.
Both that wiki and the GCode Dictionary explains thing with the term "Z leadscrews" which is correct in some hardware configurations. But it fooled me, maybe reading too quickly and not fully comprehending tings.
I propose a change to the use of "pivot point" or equivalent to make things a bit less likely to misunderstand.
@dc42 I have made some corrections and tests. A second G32 now results in a much smaller correction compared to before.
And the first layer is so much better than before. Things went a big step away from black magic towards science. Thank you!
I am guessing since the two Z-Motors may be more or less off for each start and the result of correction by G32 varied from each start (due to incorrectly configured M671). This would make the compensation by the mesh bed leveling more or less successful. If so that would explain my intermittent problem with a good first layer, and mostly on the side of the bed making the G32 correction.
During some re-calibration and reading the G-Code dictionary I think the leveling points a defined wrong in my Core-XY printer. (Board: Duet 3 Mini 5+ Firmware: 3.4.0 )
M671 X-19:316 Y146:146 S10.0
(print area is 290 x 290)
I have two independent Z-axis motors (see image) and so far I have set the leveling points to the center of the lead screws. Reading the instructions for M671 I know believe that the M671 should have the coordinates where the yellow lines cross in the picture. This is where height correction screws are positioned and where the bed pivots. Correct?
A a second bed leveling, done after each other, should not result in any correction, right? Can this be used as way to verify correct vales for the M671 command?
Doing a bed mesh leveling after a bed leveling should also result in the same height near the pivot points (see purple circles in heightmap below)?
image url)
@droftarts I think you misunderstood. This is regarding the configtool, in the configuration tool forum.
/Tomas
Went trough all steps wit default settings except these settings:
Start
RepRapPro Fisher
General
Board: Duet2WiFi
Firmware Version: 3.3 or later (stable)
Network
WiFi Access Point Name ...
WiFi Password ...
Finish
Unchecked DWC firmware and latest stable firmware
Error in browser console:
vue.runtime.esm.js:3020
TypeError: Cannot read properties of null (reading 'output_pin')
at Template.js:410:37
at Array.forEach (<anonymous>)
at Object.validatePins (Template.js:409:20)
at a.goToNextPage (App.vue:182:1)
at click (App.vue:1:2431)
at Ln (vue.runtime.esm.js:2988:30)
at n (vue.runtime.esm.js:1786:20)
at link.js:181:19
at Array.forEach (<anonymous>)
at a.onClick (link.js:180:12)
This is my mount for a Hemera on a CoreXY with toolboard and part cooling.
I have a PTFE tube sticking out through the bracket, guiding the filament..
I have threaded brass inserts for mounting the toolboars end the fan shroud.
There is just enough room for my index finger to operate the lever on the hemera.
The fan shroud can be adjusted up/down by oval mounting holes in the shroud.
Lastly my BL-Touch bracket, mounted on the opposite side with the hemera bolts. The long part is a cable guide.
I have some makeshift wiring in place since my toolboard partly gave up on me.
I hope you will find some inspiration by this.