Categories

  • Discuss setting up and using the DuetWifi and compatible hardware

    9.4k
    Topics
    89.1k
    Posts

    undefined

    Hello everyone,

    I'll keep it simple and quick.

    I've already read the different threads that talk about sending data in GCode from an Arduino but I want to be absolutely sure to understand everything, especially wiring and a little code.

    A thread presents this schematic https://forum.duet3d.com/assets/uploads/files/1697735659312-duet3d-cnc-pendant-wiring.png

    Does it allow you to connect the 6XD, its Panel I7 and the Arduino without an additional board and send it GCode?

    In my case (large multi-axis CNC) I won't be able to slide an SD card onto the motherboard. So I need the second method of connecting the Panel with the “panel duet” port. (The only difference is that the Arduino is directly connected to the io_0 pin).

    Another related question. About the code (I'm not the strongest on this side).
    Arduino

    void setup() { Serial.begin(57600); void loop() { // Send Gcode exemple Serial.print(g_code);

    Will it be enough to send the information? (gcode is a text variable)

    Duet 6XD Config.g

    M575 P1 S0 B57600

    Will it be enough to understand the information received?

    Thank you in advance for your response.

    To give more details: The goal is to create an ultra functional machine in “free access” of this fact to be able via a screen 10 inch touch connected to the Arduino to make a simple program for a fast and simple machining for all people. For example, you want to make 4 holes with 40mm and 110mm centres on a 500x500 plate, starting from the center. All you have to do is enter this information via a graphical interface, click on “ok” and you'll have your part back.

  • Using Duet Controllers

    832
    Topics
    7.5k
    Posts

    Phaedruxundefined

    @R006 said in Stall Detection on Duet 2 WiFi and Duet 3 MB6HC:

    RepRapFirmware 3.5.0-rc2

    The old unsupported 3.5 rc2 or the new in testing 3.6 rc2?

  • Ask questions about the hardware capabilities, compatibility, wiring etc. here.

    8.6k
    Topics
    76.9k
    Posts

    undefined

    @elmoret Can confirm, E3D testing is always a "worst case" recommendation. The max motor amperage is only if they are pushing ultra high flow high pressure, in a 50+C heated chamber, for extreme lengths of time.
    You may want to raise your amperage as that would give you more force available.

  • Discuss Duet on CNC machines other than 3d printers and laser cutters

    586
    Topics
    5.1k
    Posts

    undefined

    @o_lampe Are you planning to put the sand and ball between the two glass sheets? That's going to be a problem for spreading the sand. Also with narrow spacing, you can expect some of the sand to stick to the top glass from static charges. You really want to be able to clean the top glass, by lifting it up or removing it completely. Also, if you put LED strips in a narrow space at the level of the ball/sand, the sand will end up blocking the light. I think you really want to have 50 mm or so between the two sheets of glass, and the LED strips should sit about 10-20 mm above the level of the bottom glass.

    I use RGB LED strips that allow color changes, and typically operate with two different colors because I like the contrast, but white all around also looks pretty good and long as the illumination angle is low so the ridges in the sand cast shadows. A lot of people use addressable LEDs and create all sorts of light shows, but I find I want to watch the ball drawing in the sand and flashing lights quickly become hard to look at.

    Humidity isn't usually a problem with baking soda. I find that if I don't run the table for a couple weeks, small lumps will start to form, but they crumble to dust the instant the ball runs again.

  • Prototype hardware issues.

    29
    Topics
    829
    Posts

    undefined

    @JoergS5 Hi, yeah I think it is AC. Gantry (and rotary axes) looks something like this (not final design):
    ffc40a57-c651-42e2-b26f-2834dc8bb70f-image.png
    I was not aware of your work on this, is it possible to do this configuration without modification, or would I need to change something for it to work?
    And from what I see my configuration would be described Z_corexy(XY)AC or Z_corexy(XY)CA or something else?

  • Discuss Duet on laser cutters and engravers.

    183
    Topics
    1.5k
    Posts

    undefined

    @Macwolf ok then. so you just need to connect the "L" connection to the duet. You will need to connect a ground connection, like on PSU type 2, to your power supply powering your duet

  • Ask questions about installing the firmwares here

    2.1k
    Topics
    23.7k
    Posts

    undefined

    Many of the past upgrades (3.6 series) on SBC failed to fully complete with the Mini 5+ firmware still on the previous version.

    This has been easily corrected by running sudo dpkg --configure -a

    Reporting this in case something needs to be addressed.

  • Speed, acceleration, microstepping etc - post your experiences of and questions about how to get the best out of the Duet WiFi here.

    5.3k
    Topics
    54.9k
    Posts

    undefined

    @Phaedrux

    While there is nothing wrong with doing that it is not needed, in my experience.

    Here is the start code from Cura 5.10.0:

    T0 M104 S0 M109 S0 M98 P"print_begin.g" M82 ;absolute extrusion mode M82 ;absolute extrusion mode M98 P"print_extrude_begin.g" M83 ;relative extrusion mode M83 ;relative extrusion mode G1 F1500 E-6.5 ;LAYER_COUNT:259 ;LAYER:0 M107

    Note that the M104 and M109 are harmless as the call to user code follows them and there is no unwanted code that follows the call to the user code.

    Here is the start code from Prusa 2.9.2:

    M98 P"print_begin.g" G21 ; set units to millimeters G90 ; use absolute coordinates M83 ; use relative distances for extrusion M98 P"print_filament_begin.g" M107

    Again there is no unwanted code that follows the calls to user code.

    Not big deal, just thought I would mention it.

    Frederick

  • Discuss using conditionals, loops and variables in gcode

    798
    Topics
    5.7k
    Posts

  • Ask questions about the official web interface here

    1.6k
    Topics
    13.1k
    Posts

  • Feedback for docs.duet3d.com

    117
    Topics
    561
    Posts

    undefined

    @Macgyver, I also have a hard time keeping the offset meanings (both probes and tools) correct in my brain. As such, I'm not willing to try to turn the contents of my brain into sentences at the risk of getting it backwards and making it harder for you! That said, I have a macro that probes a fixed point with each of my 2 idex nozzles and updates the tool offset based on the results of probing. Here is the macro on the off chance that it helps you visualize the offsets:

    if ! exists(tools[1]) abort "idex-calibration failed, no second tool" if global.probe_block_middle == null || global.probe_block_diameter == null abort "idex-calibration failed, no probe block defined" T0 M98 P"/sys/wipe-for-probing.g" M98 P"/sys/probe-block.g" var p0 = global.last_probe_result var needs_calibration = true while var.needs_calibration && iterations < 3 T1 M98 P"/sys/wipe-for-probing.g" M98 P"/sys/probe-block.g" var p1 = global.last_probe_result var d_u = var.p0[0] - var.p1[0] var d_y = var.p0[1] - var.p1[1] var d_z = var.p0[2] - var.p1[2] if abs(var.d_u) < 0.1 && abs(var.d_y) < 0.1 set var.needs_calibration = false echo "Current offets:", tools[1].offsets[3], ",", tools[1].offsets[1], ",", tools[1].offsets[2] echo "Correction:", var.d_u, ",", var.d_y, ",", var.d_z G10 P1 U{tools[1].offsets[3] + var.d_u} Y{tools[1].offsets[1] + var.d_y} Z{tools[1].offsets[2] + var.d_z} echo "New offets:", tools[1].offsets[3], ",", tools[1].offsets[1], ",", tools[1].offsets[2]

    FYI, var.p0 is the (x,y,z) position of the fixed point as probed by T0 and var.p1 is the (x,y,z) position of the same fixed point as probed by T1 and it computes the delta between the two points as p0 - p1 and then sets the tool offsets as old_offset + delta

  • We'd love to know what your Duet electronics is controlling! When you have your Duet up and running and controlling a 3D printer or other machine, please tell us about it here.

    Example setups and prints
    805
    Topics
    9.8k
    Posts

    dwuk3dundefined

    @o_lampe thanks good idea about doubling up - that slip ring has 6 connections and I only need 4 - so I can double up the heater ones - 20A 230v would be masses more than I need.

    I haven't done enough actual printing on the SV08 to find any heat bed issues - but it seems to maintain temps ok - although I did get a failure with the PID tuning,

    Point taken about the project approach.

    One of the advantages of not having a sponsor is not being restricted to specific goals, dates or budgets.

    But you might be right that there is a risk of me losing interest in the project - especially as I've just booked a QM2 cruise - so really want to do a model of that ship before I go - so that I can get some comparison photos.

    So far all of my changes are just reordering things that were already in the plan (or when better technology like INDX vs Stealthchanger comes along).

    On this subject though I am about to change around my bed slinger approach a fair bit to not have a longer bed - but instead just move about 150mm - and add the ability to link multiple SV08's with this ability together - to get 350x700 or 350x1050 for example - with the build plates slightly overlapping the heated beds.

    Will probably do dual gantry - but only single heads on the second SV08.

    That will then deliver my original plan (and most popular video so far) - see Prusa Multi Mini.

    My immediate plans (which I may change)

    Get 3 headed build working well - with fully parallel, faster printing Rotating bed Angled extruder on rotating bed 150mm bed slinging 2nd linked or independent SV08 with 150mm bed slinging 4th print head - probably on stealthchanger to allow for offloading. iNDX - which may slot in earlier if previous steps go past December.

  • Report issues or feature request for the online RepRapFirmware config tool (https://configtool.reprapfirmware.org)

    117
    Topics
    795
    Posts

    undefined

    @Akhteh no good asking here, no one uses marlin...

  • Discuss software & plugins that work with the Duet/RepRapFirmware ecosystem.

    DueUI
    179
    Topics
    2.5k
    Posts

    undefined

    @chrishamm said in http /machine/connect session timeout:

    @stuartofmt ..... If you have a password set, there is no alternative, though. .....

    In addition to that, the session timeout is configurable via /opt/dsf/conf/http.json - see SessionTimeout in there.

    As a practical matter then, if a password is set and when the time between calls is not known: It looks like every call ought to disconnect, connect, make the desired call. An alternative would be to keep track of how long its been since the last connect call and if >= 8 seconds: connect , make the desired call

    I'd be loath to "hijak" a system wide variable for the sake of a plugin 🙂

    Thanks for the clarity. The documentation does not make it entirely clear that there is a different behavior between the no-password vs password scenario.

  • Accessories and Add-ons

    67
    Topics
    603
    Posts

    undefined

    @AlexKid Hi, sorry I missed your messages
    Well, it's great that you are working at it.
    My plans changed, I got a bit tired of tinkering so I bought a p1s)

    But my duet printer is still here and when I finish input shaping setup and cooling duct I might think about ercf. But then I will have another problem that I would need to install a cutter somehow. Though for a dual extruder printer multicolor ability would be great)

  • Forum for discussing the Duet3d Filament Monitor

    397
    Topics
    3.9k
    Posts

    T3P3Tonyundefined

    @adrien_tobeca more recent firmware reports the raw angle:

    M591 D0 Duet3D Roto magnetic filament monitor, enabled always, 25.20mm/rev, allow 10% to 190%, check printing moves every 2.0mm, agc 45, raw angle 354, no calibration data

    Also you can use the "S" parameter in M591 to monitor movement all the time if you prefer:

    Sn 0 = disable filament monitoring (default), 1 = enable filament monitoring when printing from SD card, 2 = enable filament monitoring all the time (S2 is supported RRF 3.5.0 and later ). Filament monitors accumulate calibration data (where applicable) even when filament monitoring is disabled

    https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m591-configure-filament-sensing

  • Discuss the smart PCB effector for delta printers here.

    412
    Topics
    4.1k
    Posts

    droftartsundefined

    @mickeey

    the smart effector is original duet and the problem is there. the card was on another printer and never had problems

    I think the fan0 connector failed because you wired the fan backwards. If you want to fix it, try replacing the MOSFET. See https://docs.duet3d.com/en/User_manual/Troubleshooting/Parts#fan-mosfet

    I think you should also check the plug on the Smart Effector that connects to the Duet 2 board. These pins look like they are not fully inserted into the housing. There also looks like there might be some wires poking out, that may cause a short.

    9178fd43-e865-41a2-a068-e377984f2959-image.png

    you had region on fan 2 everything works. thanks for all the support

    Great, glad you got it working. Please check the above.

    Ian

  • No decsciption available

    233
    Topics
    1.9k
    Posts

    oliofundefined

    @o_lampe if you just want to know whether the filament is loaded, you can try using stall detection on the extruder for that.

  • Discuss PanelDue connection, operation, firmware, enclosures and usage here.

    686
    Topics
    5.4k
    Posts

    Phaedruxundefined

    Are they displaying correct on the web control?

    What exactly are you seeing on the PanelDue? Photo?

    Can you describe the heater layout for the printer?

  • Discuss how to use third-party Z probes, filament sensors, endstop switches and other hardware with Duet electronics here.

    208
    Topics
    2.2k
    Posts

    undefined

    @phoenix

    Hello, thank you for sharing this. I have a question — I own a ToolChanger controlled by a Duet 3 MB6HC board, and there are 4 tools installed. Tool “T4” is a Smart Orbiter V3.0, which is connected to a ToolBoard 1LC V1.3. I was wondering whether it is possible to use the functionalities of the Smart Orbiter V3.0 by connecting them directly to the ToolBoard 1LC V1.3. Thank you in advance for your reply, it would be a great help.

  • Third-party plugins for DuetWebControl and DuetSoftwareFramework (SBC) can be found in here

    129
    Topics
    1.3k
    Posts

    oozeBotundefined

    I decided to finally take the time to learn how to create plugins within the framework and thought this would be a good challenge for a first project. Yes, it's really being designed for use within our machines, but we'll likely release a "lite" version (if there is enough interest) as an external plugins outside of the "full" version that's baked into our framework. The only caveat is that this is tied to an SBC implementation (which all our machines use), so converting it to stand-alone might be further than we will want to take it.

    We already have @Sindarius excellent gCode viewer - and this is not to take away from that!

    A few key features that have been implemented so far:

    Segmentation based gCode rendering (it splits each G1/G2/G3 into microsegments that are rendered at a precise delay so the overall move completes at the exact time expected by the associated feedrate) Actual extrusion width instead of approximated (still working on perfecting this) Feature type color rendering Loads local files, files saved within DWC, and can sync with the current job Tons of memory optimizations to keep resource utilization as small as possible Play, Pause, Speed controls, and Forward / Reverse functionality

    I'm all ears for feedback on this. It is just a side-project I thought of early last week. However, I've already grown quite fond of zoning out while watching it. 🙂

    Here are some videos and a screenshot of where I currently am with it.

    gCode Plugin - recording 1.mp4
    gCode Plugin - recording 2.mp4

    Screenshot 2025-05-04 211629.png

  • RepRapFirmware on other controllers

    30
    Topics
    364
    Posts

    CrazyCreatorundefined

    @CrazyCreator
    For anyone who has the same problem after me, here's how to connect or insert the ribbon cable.
    You have to flip the small black bracket upwards, then insert the cable, and then flip the bracket back down. This secures the cable.
    Of course, you should have known beforehand that there is a bracket on these mini jacks.

    IMG_0786.jpeg

  • STM based control boards

    48
    Topics
    384
    Posts

    undefined

    @dc42 @gloomyandy @achrn

    found the issue the 8 pin connector was the issue thanks to all of you

  • LPC based control boards

    17
    Topics
    156
    Posts

    undefined

    @gloomyandy said in RepRap Firmware Issue in behavior:

    M98 P"config.g"

    Hi @gloomyandy I appreciate your help on this below the outcome of M98P "Config.g", I agree with you some information might be strange in my Config.g file like the S because I added it without exact knowledge of the functionality so I thought that might Improve the result. but i do not know the actual value I should add :).

    Actually this is an old project i never finish as not dedicated to however since i am working on again i would like to know how should i move on below is a picture of the machine as i was not able to upload video due to the size

    I uploaded while the machine in action however if you notice that the circle is not exactly circle it looks like defected circle you can tell however in the square it is more clearer

    9/26/2022, 12:21:35 AM M98 P"config.g"
    HTTP is enabled on port 80
    FTP is enabled on port 21
    TELNET is disabled
    Error: bad grid definition: Too many grid points; suggest increase spacing to 58.4mm
    9/26/2022, 12:17:55 AM M122
    === Diagnostics ===
    RepRapFirmware for LPC176x based Boards (biquskr_1.4) version 3.2_4 running on LPC176x at 100Mhz
    Used output buffers: 1 of 16 (11 max)
    === RTOS ===
    Static ram: 4956
    Dynamic Memory (RTOS Heap 5): 7896 free, 7856 never used
    Allocations: 178 Frees: 21
    Never used RAM 256, free system stack 14 words
    Tasks: NETWORK(ready,187) HEAT(blocked,243) MAIN(running,354) IDLE(ready,21)
    Owned mutexes: WiFi(NETWORK)
    === Platform ===
    Last reset 00:01:25 ago, cause: [software]
    Last software reset at 2022-09-26 00:16, reason: User, GCodes spinning, available RAM 256, slot 0
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0042a000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
    Error status: 0x00
    Aux0 errors 0,0,0
    Supply voltage: under voltage events: 0
    Driver 0: position 0, standstill, SG min/max 0/10, error r/w 0/1, ifcnt 73, cnt r/w 7165/15, timeout 0, failedOp 0xff
    Driver 1: position 0, standstill, SG min/max 0/0, error r/w 0/1, ifcnt 68, cnt r/w 7168/12, timeout 0, failedOp 0xff
    Driver 2: position 0, standstill, SG min/max 0/18, error r/w 0/1, ifcnt 73, cnt r/w 7165/15, timeout 0, failedOp 0xff
    Driver 3: position 0, standstill, SG min/max 0/0, error r/w 0/1, ifcnt 63, cnt r/w 7169/11, timeout 0, failedOp 0xff
    Driver 4: position 0
    Driver 5: position 0
    Driver 6: position 0
    Date/time: 2022-09-26 00:17:51
    Slowest loop: 20.93ms; fastest: 0.13ms
    Step timer: target 34955404 count 84948299 delta -49992896 late 0
    USBSerial connected 0
    ADC not ready 2 ADC error threshold 10 ADC Init 1
    Ints: 51516; Calls 51516; fast: 3uS; slow 20uS adj 0 bad 0 big delta 0
    PWM Channels
    Delta -822796941 Start -1 End -1
    === Storage ===
    Free file entries: 6
    SD card 0 detected
    SD card longest read time 2.3ms, write time 0.0ms, max retries 0
    === Move ===
    DMs created 40, maxWait 20302ms, bed compensation in use: none, comp offset 0.000
    === DDARing ===
    Scheduled moves 7, completed moves 7, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === Heat ===
    Bed heaters = 0, chamberHeaters = -1
    Heater 1 is on, I-accum = 0.0
    === GCodes ===
    Segments left: 0
    Movement lock held by null
    HTTP is idle in state(s) 0
    File is idle in state(s) 0
    USB is idle in state(s) 0
    Aux is idle in state(s) 0
    Trigger is idle in state(s) 0
    Queue is idle in state(s) 0
    Daemon is idle in state(s) 0
    Autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 42.51ms; fastest: 0.00ms
    Responder states: HTTP(0) HTTP(0)
    HTTP sessions: 1 of 2

    WiFi -
    Network state is active
    WiFi module is connected to access point
    Failed messages: pending 0, notready 0, noresp 0
    WiFi firmware version 1.25-01LE-D
    WiFi MAC address c0:56:27:45:b2:f9
    WiFi Vcc 3.37, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 35944
    WiFi IP address 192.168.1.134
    WiFi signal strength -68dBm, mode 802.11n, reconnections 0, sleep mode modem
    Clock register 00181001
    Socket states: 0 0
    Untitled.jpg20220926_230657.mp4

  • Other control boards that are not specifically LPC or STM based

    42
    Topics
    602
    Posts

    T3P3Tonyundefined

    @Rat-Rig-CS thanks for your response and for how this had been handled.

    From our side part of the issue was between how warranty issues are handled when a product is supplied from a reseller, vs a board supplied with a complete product (be it a kit or an assembled machine):

    For a reseller supplied product, referral to the forum is the correct procedure. For a product incorporated in kit or complete machine we expect the manufacturer to handle the warranty process (and communicate with us directly, if there is a fault with the board).

    The basic idea being a machine sold as a complete product, which the manufacturer has control over would not be expected to have configuration or wiring issues that we want to debug here on the forum before confirming a hardware fault.

    We will update our T&Cs to make this clearer.

  • Future Direction

    14
    Topics
    196
    Posts
    No new posts.

  • Categories for specific issues with Beta and Release Candidate (RC) versions of RRF 2 and RRF 3

    1.2k
    Topics
    15.3k
    Posts

    undefined

    @jltx you should add X0 Y0 to your two G1 R1 commands in resume.g. Also add Z0 to the second one.

  • Discuss and contribute to the Duet Software Framework

    132
    Topics
    1.1k
    Posts

    davidjryanundefined

    @chrishamm

    I've created a function to subscribe to the OM. It sees some of the error messages but not all of them.

    From the DWC Dashboard:

    When I try to overtravel an axis, the message comes through to my app and the DWC console. If I try to set a global variable that doesn't exist, the message does not come through to my app but it does show up in the DWC console. If I try to run a macro that doesn't exist with M98, the message does not come through to my app but it does show up in the DWC console.

    The terminal screen on the right shows just the 'message' portion of the OM patch once I receive the full OM on the first call, I didn't want to dump the whole patch on each patch iteration, just when a new message shows up.

    The DWC console "sees" everything, my app only saw the target position error.

    9c0bcc0d-ec44-403a-9c8b-bcbc783ffaed-image.png

    Does the source of the command call to the DSF matter (my app or DWC) in determining where the message goes?

  • If you are adding features to the firmware yourself, discuss what you are doing here.

    406
    Topics
    3.2k
    Posts

    undefined

    Out of curiosity if I started playing with this is there an easy way to make the target temp the middle of the range with heating for faster and cooling for slower than x rate? Or is there no easy way to do that?

  • Prototype hardware issues.

    50
    Topics
    675
    Posts

    undefined

    @ash100 what is your reason for wanting to reduce microstepping to x8?

  • Suggestions for additional hardware to interface with the DuetWifi. Also suggestions for Changes to the DuetWifi hardware (although the hardware design is pretty fixed now!)

    130
    Topics
    1.3k
    Posts

    T3P3Tonyundefined

    @Aurimas the 1HCLs allow you to use a range of stepper motor + encoders

    Yes you could use servos with integrated drivers and then use a 6XD to drive those 4 motors

  • How would you like us to improve the firmware, and which improvements should we make first? Tell us here.

    948
    Topics
    7.5k
    Posts

    Phaedruxundefined

    @wieman01 The post above yours describes a way to do it.

  • Do you have an idea for a cool new feature in Duet Web Control? Post it here!

    331
    Topics
    2.1k
    Posts

    undefined

    @T3P3Tony

    If you go to the General section of the DWC there are a number of options/values that can be set/changed.

    So I was thinking that would be a place to have an "on/off" option that would change the behavior.

    As to M568 - I am using that.

    Here is a the relevant code from one of the filament config files:

    set global.print_beg_tool_temp_a [var.index] = 190 set global.print_beg_tool_temp_s [var.index] = 100 set global.print_beg_tool_ext_adj[var.index] = 100 set global.print_beg_tool_spd_adj[var.index] = 100 set global.print_beg_tool_bby_stp[var.index] = 0 set global.print_beg_tool_prime [var.index] = 10 set global.print_beg_tool_retract[var.index] = 0.5 set global.print_end_tool_retract[var.index] = 0.5 set global.print_beg_bed_temp_a [var.index] = 60 set global.print_beg_bed_temp_s [var.index] = 30

    Later on there is this code in another routine that applies these values:

    ; this part is just to make the use of these values down below a bit easier to read by using shorter names var bed_temp_a = global.print_beg_bed_temp_a [var.tool] var bed_temp_s = global.print_beg_bed_temp_s [var.tool] var tool_temp_a = global.print_beg_tool_temp_a [var.tool] var tool_temp_s = global.print_beg_tool_temp_s [var.tool] var ext_adj = global.print_beg_tool_ext_adj[var.tool] var spd_adj = global.print_beg_tool_spd_adj[var.tool] var bby_stp = global.print_beg_tool_bby_stp[var.tool] M568 P{var.tool} S{var.tool_temp_a} R{var.tool_temp_s} ; set extruder heater temps (active and standby) M221 D{var.tool} S{var.ext_adj} ; set extruder extrusion percentage adjust M140 S{var.bed_temp_a} R{var.bed_temp_s} ; set bed heater temps (active and standby) M220 S{var.spd_adj} ; set print speed adjust M290 R0 S{var.bby_stp} ; set initial baby steps

  • General discussion about 3d printing related subjects that are not duet specific.

    349
    Topics
    3.8k
    Posts

    undefined

    @dc42 I dont know why i didn't think about backlash. commented out the extra z movments and perfect!
    Thank you.

  • Off topic technical discussion area. Keep it clean please! Not for Duet related discussion (use the appropriate Duet forum)

    108
    Topics
    967
    Posts

    Phaedruxundefined

    Maybe some more details about the project.

  • Purchasing

    21
    Topics
    140
    Posts

    Exerqtorundefined

    @T3P3Tony tried to send a chat message, but i don't know if it worked. Never done it on this forum platform before.

  • Help with ordering, announcements etc

    160
    Topics
    948
    Posts

    T3P3Tonyundefined

    @TNO_Marc please email sales@duet3d.com. The online shop accounts are currently for OEMs and Resellers purchasing in volume. We also may be able to assist with a reseller near you.

Unless otherwise noted, all forum content is licensed under CC-BY-SA