Categories

  • Discuss setting up and using the DuetWifi and compatible hardware

    9.4k
    Topics
    89.3k
    Posts

    Phaedruxundefined

    The nozzle needs time to build up pressure to begin extruding again. You may need to add a reprime sequence where you command a small amount of extrusion before continuing.

  • Using Duet Controllers

    836
    Topics
    7.5k
    Posts

    R006undefined

    @dc42

    Thank you.

    Could you please provide example files for both driver-warning.g and driver-stall.g, if available?

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

    8.6k
    Topics
    77.1k
    Posts

    droftartsundefined

    @giostark said in End Stop for high temperature coreXY - suggestion/advise:

    I read in other post on this forum that I can place them in series , is this right?

    Yes, so long as you wire and configure them as 'Normally Closed' (which is what we recommend https://docs.duet3d.com/en/User_manual/Connecting_hardware/Sensors_endstops#connecting-different-types-of-endstop-switch). Note that the firmware can't make any distinction between which one is triggered, so set up homing for one end or the other. You can set up triggers to pause or emergency stop if they are triggered at any other time other than homing, see https://docs.duet3d.com/User_manual/Reference/Gcodes#m581-configure-external-trigger

    Ian

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

    594
    Topics
    5.2k
    Posts

    madediundefined

    OK. Thank you very much for your answer. Is it still possible to receive the position signal from the driver via RS485 (or, since the driver has a pulse output, use that) to obtain an absolute position and then communicate this to the Duet as a machine coordinate, so that the Duet can wait until the movement is actually completed? This would have many advantages: 1. It's easier to implement a handwheel (since the jog or speed command can be sent to the driver, as they usually have inputs for these commands). 2. Setting up a custom interface via a display, for example, for a tool changer. In the CNC area, there's a tool library where the tool offsets and, for example, speeds for milling cutters are stored, as well as which tools are actually loaded in the machine. Perhaps this could also be considered for DWC/CNC. 3. If the motors are disabled, the position is still recorded, and you don't have to repeat homing, etc.

  • Prototype hardware issues.

    31
    Topics
    837
    Posts

    SanderLPFRGundefined

    Hey everybody,

    For a side project, I am trying to develop a system to cut at a positive and negative bevel/angle with a CO2 laser by manipulating the beam. I want to do this like in this video. (I need a CO2 laser since fiber cannot cut my material, UV is too heavy to move around, and Diode is too weak)

    Basically, I angle the beam 90deg downwards with mirror 1, then horizontally with mirror2, and then back down with mirror 3.

    Mirror 1 is fixed to the X axis Mirror 2 can be rotated along Z, to manipulate the horizontal direction of the beam Mirror 3 can be rotated along its own Y, manipulating the beam at a -30 to +30 angle

    I have a very rough prototype, but I noticed that as mirror 3 angles side-to-side, the lens-to-workpiece distance varies significantly.
    Current situation;
    30a186df-49ce-4472-ac76-4b96e822ba38-image.png

    To maintain a constant distance, I want to add an actuator to move the lens compared to mirror:

    ed0c7954-66a0-447b-ae53-b4a18d55cb85-image.png

    Now, here comes the question;
    The Y-axis rotates the mirror3, and let's call the actuator for the lens "axis V". They will ALWAYS move in synchronisation, meaning that when Y goes to -30 angle, the V should move to +25mm(-ish), and when the Y is at angle 0, the V should be 0. I understand that there will be challenges with acceleration, and the non-linear movement of V. But, is it possible, in any way, to couple/synchronise the rotational (X) and linear axis (V) always to move in relation

  • Discuss Duet on laser cutters and engravers.

    184
    Topics
    1.5k
    Posts

    droftartsundefined

    @jimakron said in Trouble firing 45 watt TTL Laser on "output6_buff" PMW:

    We are NOT ABLE to fire the laser using the 'output6.buff" pin on the Duet 3 mini 5+when we wire to the IN pin on the MYJG5W.
    The ... 'IN' pin is a analog 0-5vdc analog PMW signal.

    M452 C"!out6" R255 S0 F3000 ; enable Laser mode, on out6 (F3000)

    Have you got a link to the manual for the Cloudray MYJG50W PSU? The product page is quite vague, https://www.cloudraylaser.com/products/cloudray-50w-co2-myjg-series-power-supply-black-shell-myjg-50w

    As far as I can tell 'H' and 'L' are on/off (L being H inverted) inputs. The 'IN' pin is said to support "input 0V to 5V analog signal, can also input PWM signal" (there's no such thing as an "analog PWM" signal). By 'analog signal', it means a signal of 0 to 5V, usually controlled by a potentiometer. The Mini 5+ output6.buff doesn't supply an analogue signal, only a 5V PWM signal.

    I can't find any information on the PWM frequency that the Cloudray MYJG50W accepts, but it's possible that F3000 in the M452 command is too high. The firmware default is 500Hz (F500), have you tied that?

    Ian

  • Ask questions about installing the firmwares here

    2.2k
    Topics
    23.8k
    Posts

    ericlmccormickundefined

    I have the exact same issues. Has a solution been found yet?

  • 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
    55.0k
    Posts

    nick9one1undefined

    @droftarts thanks for the information.

    this is an example of a print that skips with these settings..

    ; Pressure advance M572 D0 S0.051 ; input shaping M593 P"zvd" F40

    I have already printed 3 or 4 of these with input shaping turned off, they all come out fine.

    dd6daba1-1638-4b79-9a17-073b127cfac2-image.png

    I've just started a print with PA off, and input shaping on... I'll update here when it completes (or fails).

    config.g

    Heewing_Motor_mount_Right_pt1_v2 (1)_0.2mm_PETG__1h6m.gcode

  • Discuss using conditionals, loops and variables in gcode

    802
    Topics
    5.7k
    Posts

    dc42undefined

    @mikeabuilder thanks for confirming.

  • Ask questions about the official web interface here

    1.6k
    Topics
    13.1k
    Posts

  • Feedback for docs.duet3d.com

    118
    Topics
    562
    Posts

    jbjhjmundefined

    Hey everyone, I've just finished setting up SZP nozzle probing on my printer.
    Had to figure out some things which were difficult to understand in docs, so I thought I'd write down a full example to help others.
    Don't know if it's the appropriate forum. Feel free to move it somewhere else and/or add the example to documentation.
    (Search terms: beacon contact probe)

    Note that at the time of setting this up, the printhead had TWO probes mounted, so within the code you'll see "K1" everywhere to refer to the SZP instead of the default probe (K0).

    config.g

    sets basic config only. Most configuration is handled dynamically within homing / bed mesh scripts.

    ; Define SZP Scanning Probe ===================================================================== M558 K1 P11 C"120.i2c.ldc1612" F36000 T36000 ; K0 = primary probe, K1 = secondary probe M308 A"SZP coil" S10 Y"thermistor" P"120.temp0" ; configurate coil thermistor G31 K1 X0 Y24 Z2 ; set default XYZ offsets, other params will be set on demand by macros M98 P"szp_mode_normal.g" ; this is optional, just here to calm you down when opening DWC, which would show probe 999999 values otherwise. ...

    nozzle probing and "default" mid-air probing requires different calibrations.
    For that reason, my solution relies on two custom macro files to set up any of the two when needed.

    szp_mode_normal.g M558.3 K1 S0 ; S0 -> enter normal probing mode ; get the S and R values by calling M558.2 K1 S-1 in a good Z distance. 5-10mm from bed worked fine for me. ; manually move Z axis and ensure no 99999 values are being reported ; (when coming super close to bed it may happen, but should be fine as it is not used to probe in super-close distance.) M558.2 K1 S16 R132663 szp_mode_touch.g ; get the S and R values by calling M558.2 K1 S-1 in small Z distance. 2-5mm from bed worked fine for me. M558.2 K1 S16 R133019 ; V=Threshold. Start with V0.1 and increase until it works reliably without misdetections. M558.3 K1 S1 V0.3 homez.g

    a bit more complicated as it needs to handle every situation on the fly.
    As recommended in docs, we first to a mid-air measurement which aims to get the nozzle/probe "kinda close" to the bed.
    Then, a second probing is executed.

    This is not a copy-and-paste script, you'll need to run multiple calibrations to figure out the right values for your printer.
    I recommend to comment out the Step 1/2 seconds and re-add and test them step by step to ensure low risk of damaging your printer due to misconfiguration.
    See the inline comments for explanation as well as instructions on how to calibrate

    ; Step 0: move to a safe probing position M564 H0 ; unlock movement G91 ; relative positioning G1 H0 Z30 F6000 ; lift Z a bit to ensure we arent too close to the bed -- H2 is outdated and not used anymore. H1 respects endstops, H0 ignores them. G90 ; absolute positioning G1 H0 X150 Y140 F10000 ; move probe to bed center M913 Z55 ; 50% Z motor current to reduce damage/intensity of impact ; Step 1: do a rough contact-free measurement to get *kinda close* to bed M98 P"szp_mode_normal.g" ; set a safe Z trigger height to trigger when the bed is coming close but safely not touching. omit XY, these were defined in config.g! ; Z and P values are important here: These relate "Probe value [P] of 8850 relates to [Z] offset of 6mm". ; Get your probe's P value by moving to Z=6 manually after calibrating as described in szp_mode_normal.g, and read the value reported in DWC then. ; if szp_mode_normal.g is modified, these values must be updated too! G31 K1 Z6 P8850 G30 K1 S1 ; execute Z homing to ensure printhead is close to bed ; Step 2: we should now be ~6mm above the bed. TIme to do the fine tuning! M98 P"szp_mode_touch.g" G30 K1 S1 ; execute contact probing and set Z G91 ; relative positioning G1 Z3 ; move up a bit G90 ; absolute positioning ; FInalization M564 H1 ; re-lock movement M913 Z100 ; reset Z motor current to 100%

    You should now be able to successfully home all axes using nozzle touch probing for Z.

    bed.g

    not much special things in here. Call the szp_mode_normal to ensure SZP is using correct configuration.

    M561 ; clear any bed transform M98 P"szp_mode_normal.g" G30 K1 P0 X10 Y25 Z-99999 ; probe near a leadscrew G30 K1 P1 X150 Y280 Z-99999 ; probe near a leadscrew G30 K1 P2 X280 Y25 Z-99999 S3 ; probe near a leadscrew and calibrate 3 motors mesh.g

    pretty much the example found in documentation.
    Only change was I'm calling the homez.g macro.
    Not sure if it makes any difference.

    M557 X10:290 Y25:275 P28:25 ; Define grid for mesh bed compensation, origin in bed centre P=Number of points per axis G29 S2 ; Disable mesh bed compensation M98 P"homez.g" ; Home Z G1 Z6 ; To avoid backlash move to point higher than start of calibration M558.1 K1 S1.7 ; Calibrate probe G1 Z6 ; Move up at end of calibration G29 S0 K1 ; Scan the bed and create mesh

    I think that's it! Took a while but totally worth it. Don't give up if you can't make it work immediately.
    Have fun and good luck!

  • 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
    806
    Topics
    9.9k
    Posts

    Dad003undefined

    fixed a few of my problem now just doing more testing , double the linear rail for the Z axis , one rails wasnt enough , so now platform is sitting on 2 hgr 15 rail with 2 linear block on each side , following that i still had some weird pattern on the Z but found out it was the side panel of the pulley box since they are 3d printed that were flexing , so added an extra support on it and it is now fixed , need to replace those to aluminum at some point. For now i put some aluminum bubble insulation to enclose the heated chamber and top is an acrylic panel , the few test ive done so far it goes from room tmep to about 40c in like 20min , but seem to struggle past that . so i either need more heating power or a better way to dissipate/ propagate the heat in there . so looking into maybe put different heatsink on the silison heater with more fin/ more surface or had another heater

    IMG_20250506_195457837_HDR.jpg IMG_20250518_203417564_HDR.jpg IMG_20250518_203425535_HDR.jpg

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

    117
    Topics
    795
    Posts

    jay_s_ukundefined

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

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

    DueUI
    180
    Topics
    2.5k
    Posts

    stuartofmtundefined

    @chrishamm
    Thanks. Confirmed working with first=0

  • Accessories and Add-ons

    67
    Topics
    603
    Posts

    Inlinebrotherundefined

    @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

    398
    Topics
    3.9k
    Posts

    bastundefined

    I just received my LLL PLUS Buffer from Mellow 3D.
    I'd like to connect it to my Duet to retrieve buffer information. The Duet also has information about filament progress and breakage.
    Here's the device's date sheet:
    https://mellow.klipper.cn/en/docs/ProductDoc/ExtensionBoard/fly-buffer-plus/?persistLocale=true
    It must be connected to 12/24V and has a switch pin and a motion pin.

    Thank you.

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

    687
    Topics
    5.4k
    Posts

    wschadowundefined

    @dc42 Of course it is not a "bug". It shows the "correct" mathematical number. That might be confuing since this ae-b format is used here only. All other number are rounded. Why not display it as 0.001. If it is lower then show 0.000, as it was before. There is is no gain of information from the last digits or that specific number. Besides i doubt that you can achieve that accuracy with a "normal" printer, Formulas will give you that number but an error forward correction will leave you at the 0.01 level I guess.

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

    209
    Topics
    2.2k
    Posts

    Adrian52undefined

    @DocTrucker I approached this problem by clipping a spare thermistor to the cold end, and monitoring it via daemon.g. Might add a belt to your tacho braces.

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

    130
    Topics
    1.3k
    Posts

    MintyTreborundefined

    Updated to V1.3.5 for DWC 3.6

  • RepRapFirmware on other controllers

    30
    Topics
    371
    Posts

    CrazyCreatorundefined

    @jay_s_uk Thank you very much for the quick reply.

  • STM based control boards

    49
    Topics
    396
    Posts

    gloomyandyundefined

    @justGuner I've had my toolchanger which uses 5160 drivers sat in stealthchop with the same settings you use for the last 6 hours and as I suspected no reports of any sort. I'm pretty much out of ideas now.

  • 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.3k
    Posts

    dc42undefined

    @MaxGyver please connect a PC running a terminal emulator to the USB port of the main board, and see whether it prints any debug messages on that terminal when this error occurs.

  • Discuss and contribute to the Duet Software Framework

    132
    Topics
    1.1k
    Posts

    davidjryanundefined

    @chrishamm @T3P3Tony
    Looking at CodeLogger did help me figure a few things, thanks for that push.

    After some testing, the EXECUTED mode is what I need. I was only testing the PRE and POST interception modes previously.

    I am having issues with the sample program https://github.com/Duet3D/dsf-python/blob/v3.6-dev/examples/custom_m_codes.py

    My desire is to capture ALL error messages. Currently I am receiving just those that are generated by G/M/T codes.
    I want to do exactly what the first comment in the sample program is stating, capture the whole G-code stream (no filters).

    It crashes on the non-G/M/T codes being intercepted (the
    cde = intercept_connection.receive_code()
    call) and the reported exceptions are a bit Greek to me.

    If I change the interception mode from EXECUTED to POST, I get the non-G/M/T intercepts but lose the G/M/T intercepts completely, though the program does not crash. So I don't know if what I am facing is an issue the sample script or the binding call itself.

    Who might be the python guru for dealing with the dsf-python bindings? Is it @Falcounet ? I see AndyEveritt is pushing a lot of the contributions for dsf-python on git. Does he have a handle on here?

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

    408
    Topics
    3.2k
    Posts

    sebkritikelundefined

    @dc42 David, really appreciate your time! Wanted to give an update on this, as it may be solved (or at least partially solved for now!).
    7200eeda-501a-4462-8f30-faa2ff2d0e18-image.png

    Because I needed to add the 25Mhz crystal (external to the board), I've been working with a breadboard. The crystal I'm using has a load capacitance of 18pF, and pretty early on I found I had to compensate for solderless breadboard capacitance. I thought I had properly done so, but perhaps the initial setup was marginal, and adding in the oscilloscope and ATMEL-ICE potentially had me seeing ghosts.

    I think I've learned enough here that I can build up an interface PCB to move away from a breadboard!

    Edit: Have the bootloader working as well, so I can do updates via DWC 👍 Guess I was just running in circles the past week or so!

  • 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

    dc42undefined

    @GeneRisi feel free to create a feature request at https://github.com/Duet3D/RepRapFirmware/issues with a link to this thread in it.

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

    354
    Topics
    3.9k
    Posts

    kcressundefined

    @droftarts Ian, Thanks for the link. I've implemented automatic tramming into bed.g

    Thank you!

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

    109
    Topics
    968
    Posts

    3DPMicroundefined

    This is not an advertisment and I won't name any specific sellers on US ebay but if you search for tdk lambda and flex power PSU's there's some great deals. I have been using an $800 Flex for the last couple weeks that I bought for $25. Has 5v 10a, 12v 5a, 2x24v 5a and 48v 8.5a. Purchased a tdk lambda with similar specs also for $45. It's surplus from decomisioned equipment but is in great shape and the seller has dozens of them. Don't buy potentially dangerous junk for the same price when you can get these.

  • 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