Categories

  • Discuss setting up and using the DuetWifi and compatible hardware

    9.4k
    Topics
    88.9k
    Posts

    tasundefined

    Hi,

    The forum is getting spammed big time this evening. Offering to sell everything from CBD to counterfeit money.

    It is a bit tedious to flag so many posts using the existing reporting method. I know, I know, it's pretty easy as it is but I found it annoying this evening.

    Maybe the ability to right click in the post subject listing and report without having to open the message, go to the bottom, then select the option to report.

    Just a suggestion.

    Thanks,

    Tony.

    P.S.

    Also being able to report user and post at the same time as spam would be very helpful.

  • Using Duet Controllers

    831
    Topics
    7.5k
    Posts

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

    8.5k
    Topics
    76.8k
    Posts

    oozeBotundefined

    Thank you both! I'll have an engineer do some testing on it. We've never seen one have this kind of issue before and would like to understand if we (really, myself since it's been on my desk) caused it damage or if it was just a faulty board. I'll go ahead and remove the "Unsolved" tag.

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

    584
    Topics
    5.1k
    Posts

    NineMileundefined

    @Firky_CNC said in Modbus CNC Spindle Control (3.6 RC2) Shihlin SL3:

    Just an update to say, using the MillenniumMachines ArborCTL release 0.0.5, I am able to control a SL3 VFD using the RJ45 connector using a TLL to RS845 converter connected to UART (OI_1) on the mini 5+

    Unable to post a link. But it is on GitHub.

    https://github.com/MillenniumMachines/ArborCTL/releases/tag/v0.0.5

    <- Author

    It's a RRF addon written in a similar vein to MillenniumOS, the idea is to provide a framework around which Modbus spindle control implementations can be written for particular VFD types.

    Currently it configures and runs the Shihlin SL3 and has untested support for the HY02 VFDs. It is alpha quality so if you do use it, be careful and it is at your own risk.

    Help supporting more VFD types appreciated.

  • Prototype hardware issues.

    27
    Topics
    808
    Posts

    dwuk3dundefined

    @dc42 Sounds great thanks.

    I don't think the number of overridden GCODEs is likely ever to be a very long list - so maybe a lookup list could work too - perhaps with some sort of extra M command in the config.g or start gcode in the slicer to register the overrides.

    In the meantime I think I will alter my post processor to be more generic and do more or less the same thing.
    i.e. Look for some sort of override registration M command (M802 for example) in the gcode stream, and then use that info to then override any relevant G/M/T commands later in the stream into .x equivalents.

  • Discuss Duet on laser cutters and engravers.

    183
    Topics
    1.5k
    Posts

    jay_s_ukundefined

    @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

    droftartsundefined

    @rodneysramosj Is the X endstop a max endstop or min endstop? Currently your G1 H1 X... homing moves are positive, so should be moving to the right, towards a max endstop. If this is wrong, you probably need to check the direction the motors are moving is correct, see https://docs.duet3d.com/en/How_to_guides/Commissioning#h-10-check-stepper-motors

    Your printer origin X0 Y0 Z0 should be in the front left corner. Positive X moves should move the nozzle to the right, positive Y moves should move the nozzle towards the back.

    Ian

  • 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

    Notepadundefined

    @Pat Thats interesting as PA has been changed quite heavily between 3.5.4 and 3.6.x

  • Discuss using conditionals, loops and variables in gcode

    795
    Topics
    5.6k
    Posts

    mikeabuilderundefined

    Thanks. I'll see if @dc42 has some trick... but I've also been thinking about the relative effort of

    Adding my trace code to existing M291 S3 commands, plus adding whatever trick might exist. Swapping M291 S2 for M291 S4 and using my existing bread crumbs.

    The M291 swap replaces 1 line of code with three lines (the M291, plus an if statement, and an M99 (to cancel).

    Any trickiness to retain the M291S3 would almost certainly require more than that.

    In both cases, there is the search for M291 in multiple files and add the breadcrumb code (two lines). And this is maybe the biggest effort.

    So I'll amend my request for a tricky solution to include - "only if it's dead-simple"

  • Ask questions about the official web interface here

    1.6k
    Topics
    13.1k
    Posts

    jay_s_ukundefined

    @Paski BtnCmd can be used to change the header colour fba9d235-0007-4a74-b22d-20b6227418f1-image.png

  • Feedback for docs.duet3d.com

    116
    Topics
    558
    Posts

    droftartsundefined

    @oliof @gloomyandy After discussing this with @dc42, I think I've misunderstood how extruder acceleration is limited under PA. The jerk / PA limit on acceleration is applied automatically by RRF, so the user doesn't need to set jerk or acceleration manually to take account of PA. The user sets extruder speed, jerk and acceleration at whatever the extruder can achieve in extruder-only moves (like retraction). The user only needs to know that acceleration is limited when PA is applied, to jerk / PA, so may have consequences such as slowing down or stuttering during printing moves, or skipping steps. This, at least, makes the documentation simpler! Which I'll now update, again...

    Ian

  • 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
    804
    Topics
    9.8k
    Posts

    dwuk3dundefined

    Updated my CAD for INDX a bit based on latest pictures, plus created a Voron Zero version.

    1B0231A7-B1F5-481A-8386-FCEAD3449398.png 58815C02-0CE3-4734-8CDB-FBF0890AD9B1.png 65FF815E-3CEB-4AFA-8E1B-34207ADA202C.png 0E70E13C-4DF6-4146-ABB2-7E401FD69030.png 3E31B6EA-689E-4633-8407-24BAB982BA2E.png 9E38F91F-1FA7-4F7D-A0D4-A842A64DD5F7.png

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

    116
    Topics
    793
    Posts

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

    DueUI
    178
    Topics
    2.5k
    Posts

    stuartofmtundefined

    @guywinslow
    Ok - that's good news but a mystery as to why it did not work the first time, as I assume you, effectively, just reinstalled from github.

    If you had used the version I posted yesterday - there would have been a duetBackup ONLY log created (along with additional debug information) that you could access directly using the DWC UI.

    The version that I sent to you yesterday will be the version posted in github soon. I do not use github for "in progress" builds - just for version bumps, once they are tested.

    While I have tested on my 3.6 beta build - It would be very helpful if you could validate it against your 3.5 build.

    Can you do that for me? I.e. Try the version I posted yesterday.

    P.S. The permissions dsf:dsf from the ls -l look correct - so there may have been some other issue.

  • Accessories and Add-ons

    66
    Topics
    601
    Posts

    jay_s_ukundefined

    @dwuk3d yes, it'll work with that

  • 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.

    411
    Topics
    4.1k
    Posts

    elmoretundefined

    @patterson6 They're in stock, I think for a couple days stock ran out, but nearly immediately restocked. Could have signed up for restock emails?

    Most, nearly all Volcano nozzles are in stock. Which materials/sizes are you wanting?

  • No decsciption available

    232
    Topics
    1.9k
    Posts

    dl6lrundefined

    I tested and had no consistent results with a structured PEI coated steel sheet. Moving the head just 1or 2mm sideways produced deviations of up to 0.2mm in either direction. I am back to BL-Touch with more consistent overall results whereas the IR-probe was more consistent on the same spot.

  • 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

    JC42undefined

    @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

    127
    Topics
    1.3k
    Posts

    jonsteinmetzundefined

    @stuartofmt
    Great, thanks for the reply. I might wait for the release since I had some weirdness when I tried 3.6.0 rc2. I was messing with several things at the time so maybe it was unrelated. In the meantime I have been manually checking my config into github. 🙂

    Thanks again and I look forward to trying this out.

  • RepRapFirmware on other controllers

    30
    Topics
    352
    Posts

    jay_s_ukundefined

    @CrazyCreator yes, that's right

  • STM based control boards

    48
    Topics
    384
    Posts

    sankafolaundefined

    @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

    Shadi_Polarundefined

    @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.2k
    Posts

    ironhydroxideundefined

    @dc42
    Loaded rc2+4, error is still present

    Console output here from uploading firmware, updating config.g back to the previous U axis definition, then G28 A

    4/17/2025, 7:17:00 AM: : Board 50 starting firmware update 4/17/2025, 7:17:24 AM: Connection established 4/17/2025, 7:18:19 AM: Upload of config.g successful after 0s 4/17/2025, 7:18:33 AM: Connection interrupted, attempting to reconnect...: Network error: Request timed out 4/17/2025, 7:18:35 AM: Connection established 4/17/2025, 7:18:46 AM: G28 A: homea.g Call Error: Code 7 move error: info=-2.147e+9, seg: s=16775844 t=2147483647 d=-2147483648.00 u=-1.0000e+0 a=0.0000e+0 f=0f 4/17/2025, 7:18:55 AM: M122: === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.6.0-rc.2+4 (2025-04-17 08:23:50) running on Duet 3 Mini5plus Ethernet (standalone mode) Board ID: G5729-TU8LU-F65J0-409NU-3F03Z-7U6T6 Used output buffers: 1 of 40 (19 max) === RTOS === Static ram: 94764 Dynamic ram: 116336 of which 16 recycled Never used RAM 30280, free system stack 110 words Tasks: NETWORK(1,ready,21.1%,178) ETHERNET(5,nWait 7,0.1%,578) HEAT(3,nWait 6,0.0%,371) TMC(4,nWait 6,0.8%,99) CanReceiv(6,nWait 1,0.0%,818) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,337) MAIN(1,running,75.5%,675) IDLE(0,ready,1.6%,29) USBD(3,blocked,0.0%,147) AIN(4,delaying,0.8%,261), total 99.8% Owned mutexes: === Platform === Last reset 00:00:31 ago, cause: software Last software reset at 2025-04-17 07:18, reason: User, Gcodes spinning, available RAM 30280, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0400f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 MCU temperature: min 30.2, current 31.2, max 31.2 Supply voltage: min 23.9, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/37, heap memory allocated/used/recyclable 2048/696/0, gc cycles 0 Events: 0 queued, 0 completed Date/time: 2025-04-17 07:19:27 Slowest loop: 56.79ms; fastest: 0.16ms === Storage === Free file entries: 18 SD card 0 detected, requested/actual speed: 25.0/24.0MBytes/sec SD card longest read time 3.4ms, write time 6.0ms, max retries 0 === Move === Segments created 3, maxWait 22309ms, bed comp in use: none, height map offset 0.000, hiccups added 0/0 (0.00/0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00 Pos req/act/dcf: 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00 No step interrupt scheduled Driver 0: standstill, SG min 0, r/w errs 0/1, ifcnt 43, reads/writes 1603/15, timeouts 0, DMA errs 0, CC errs 0 Driver 1: standstill, SG min 0, r/w errs 0/1, ifcnt 41, reads/writes 1605/13, timeouts 0, DMA errs 0, CC errs 0 Driver 2: standstill, SG min 0, r/w errs 0/1, ifcnt 41, reads/writes 1604/13, timeouts 0, DMA errs 0, CC errs 0 Driver 3: standstill, SG min 0, r/w errs 0/1, ifcnt 32, reads/writes 1607/10, timeouts 0, DMA errs 0, CC errs 0 Driver 4: standstill, SG min 0, r/w errs 0/1, ifcnt 32, reads/writes 1608/10, timeouts 0, DMA errs 0, CC errs 0 Driver 5: not present Driver 6: not present === DDARing 0 === Scheduled moves 1, completed 1, LaErrors 0, Underruns [0, 0, 0] Segments left 1, axes/extruders owned 0x00000013, drives owned 0x00000013 Code queue is empty === DDARing 1 === Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0] Segments left 0, axes/extruders owned 0x00000000, drives owned 0x00000000 Code queue is empty === Heat === Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === GCodes === Movement locks held by HTTP, null HTTP is idle in state(s) 2 5, running macro Telnet 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 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 === CAN === Messages queued 156, received 249, lost 0, ignored 0, errs 2680, boc 0 Longest wait 277ms for reply type 6041, peak Tx sync delay 10687, free buffers 26 (min 25), ts 148/145/0 Tx timeouts 0,0,2,0,0,0 last cancelled message type 30 dest 127 === Network === Slowest loop: 14.42ms; fastest: 0.03ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 = Ethernet = Interface state: active Error counts: 0 0 0 0 0 0 Socket states: 6 6 2 2 2 0 0 0 0

  • Discuss and contribute to the Duet Software Framework

    132
    Topics
    1.1k
    Posts

    chrishammundefined

    @oozeBot Thanks for pointing it out, I just removed the section about gpiochip4. The automatic change in config.json to gpiochip4 was removed last year and that change is already in the latest DuetPi version, so no further changes should be needed at this point if the stock image is used.

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

    406
    Topics
    3.2k
    Posts

    umutdumanundefined

    @dc42 that is PsoC which is supplying by 3.3v

  • Prototype hardware issues.

    50
    Topics
    675
    Posts

    dc42undefined

    @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

    -SF-undefined

    Good evening,

    Would it be possible to operate an extruder in closed loop mode?

    For instance with:

    Duet3D magnetic encoder on the extruder's stepper (commutation) Duet3D magnetic filament monitor near the hotend (close the loop) Duet3D 1HCL

    If this would be possible, it could improve:

    Estep calibration, material independent Retraction Backlash in the bowden tube VFA due to excentric hobs VFA due to speed variations caused by poorly meshed (dual) extruder gears Possibly pressure advance Non linear extrusion Extruder feed forward

    Thanks in advance!

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

    331
    Topics
    2.1k
    Posts

    fcwiltundefined

    @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

    Oben221undefined

    @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