Categories

  • Discuss setting up and using the DuetWifi and compatible hardware

    9.4k
    Topics
    88.7k
    Posts

    undefined

    What do you want it to do that it isn't doing now? It looks like a passable start to tweak.

  • Using Duet Controllers

    830
    Topics
    7.5k
    Posts

    undefined

    I think you're on the right track with the G60 command. You don't provide any details of the trigger macros, so the rest of this post is just guessing on my part...

    I assume you've read this page on setting up triggers: https://docs.duet3d.com/en/User_manual/Tuning/Triggers, and that you've set up the inputs for the two buttons using M950, and also defined triggers numbered 10 and 11 using M581. Also, you've got these commands in your config.g file so they'll be executed every time you start the machine.

    The trigger10.g macro should need only one command.

    ;trigger10.g G60 S3

    When this macro runs it will save the current machine location into slot #3.

    The trigger11.g macro should looks something like this:

    ;trigger11.g G0 R3 X0 Y0 Z0

    This commands a fast move to the stored S3 location without any offset in the X,Y,or Z positions stored in S3. If you don't have the X0 Y0 Z0 in your command, those axes won't be moved (it will look like nothing has happened when you push the second button).

    An additional thing to consider in your trigger 11.g macro. If your "move to" button is pressed before the "save position" button, the default coordinates stored in slot S3 are 0,0,0 so you'll drive a move you might not want. If you are unlikely to ever save 0,0,0 with your "save location" button, you could write an IF statement into your trigger11.g macro to look at the current values saved in this slot and if they are all 0, you could do something like post a message and not make the move.

    To test your trigger10.g macro without the buttons, you can send M98 P"trigger10.g" in the Web control window, then send echo state.restorePoints[3].coords to see the saved coordinates. You can also look at the object model plugin to see if the location has been stored. It will be in state > restorePoints >3

    You can similarly test trigger11.g. After running trigger10, move the machine using the Web control then send M98 P"trigger11.g" in the Web control window. Your machine should move back to the stored position.

    You can also test the inputs by looking at the inputs section of the object model while you press the buttons.

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

    8.5k
    Topics
    76.8k
    Posts

    undefined

    Hello everyone!

    These days I came across the Duet 3 Magnetic Encoder, and I’m considering using it in my project: a four-wheeled robot. Each wheel is driven by a NEMA17 stepper motor.

    Since I’d prefer not to use a multiplexer (MUX), I was wondering:
    Is this encoder suitable for projects with multiple stepper motors without requiring a MUX?

    Thanks in advance!

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

    581
    Topics
    5.1k
    Posts

    undefined

    @dhusolo yes that should work.

  • Prototype hardware issues.

    27
    Topics
    808
    Posts

    undefined

    @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

    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

    Thanks for the help, Everything is up and running after the update. Now looking to experiment with input shaping.

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

    undefined

    Hi @droftarts

    Thank you for the reply, I have the BLtouch on the T0 toolhead, its why I activate it first using the T0 in the Start Gcode.

    The second toolhead T1 (non-Bltouch) is being called by the slicer. as that is how I have assigned it in my slice.

    If I create a small object (purge line) and print it first the collision does not occure.

    could you take a guess at a work around where I can leave the front tool head not in use to print with the rear one only?

    I am willing to test theorys, just not sure what else to try.

  • Discuss using conditionals, loops and variables in gcode

    792
    Topics
    5.6k
    Posts

    undefined

    @Dlock34 said in dual motor z axis bed leveling not probing by lead screws:

    M574 'z1 S2

    The DWC message is provoked by that line because there is no 'z axis.

  • Ask questions about the official web interface here

    1.6k
    Topics
    13.1k
    Posts

    undefined

    @jltx said in getting blank page for DWC on iPad:

    it says iOS 10 and up in the documentation

    Can you post a link to where it says that, please?

    Ian

  • Feedback for docs.duet3d.com

    116
    Topics
    558
    Posts

    undefined

    @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
    803
    Topics
    9.7k
    Posts

    undefined

    Better demo of parallel colour/material changes - some changes as quick as 2 seconds.

    Still more work to do - but synchronisation getting closer.

    Using preheat G10's to kicking off the Pre Heat, delay, final heat, priming, tool change.

    Demo here.

    https://youtu.be/uk7KTCqrujg
    2F9F385E-12C0-4647-9F90-BBB57768B5B6_1_201_a.jpeg

    Tool change macro getting pretty complicated....

    ;changeFilament.g ;M98 P"0:/macros/changeFilament.g" A{previous_extruder} B{new_filament_temp} L{layer_num} F{first_layer_temperature} N{next_extruder} H{first_layer_height} echo {state.thisInput},"changeFilament" if exists(global.primeLayer) == false global primeLayer = {-2,-2} ;if exists(param.A) && param.A == 0 ; M98.1 A"parkXY.g" ;if exists(param.A) && param.A == 1 ; M98.1 A"parkUV.g" if exists(param.H) G1 Z{param.H} F500 if exists(param.N) && param.N == 0 M596.1 P1 T0 echo {state.thisInput},"step 0 - wait for 200",{sensors.analog[param.N+1].lastReading} while heat.heaters[1].active < 200 G4 P500 ;echo {state.thisInput},"step 0 - wait for 200",{sensors.analog[param.N+1].lastReading} ;echo {state.thisInput},"M116 P1 from ",{sensors.analog[param.N+1].lastReading}," to 200" ;var start = state.upTime ;M116 P{param.N} ;echo {state.thisInput},"step 1 heat up time",{floor(state.upTime-var.start)},"s" ;**** Calculate delay var delayT = global.preHeatT echo {state.thisInput},"delayT initial",var.delayT if exists(param.L) && param.L <= 0 if global.primeLayer[param.N] < param.L set var.delayT = var.delayT - global.primeTime0*2 if exists(param.L) && param.L > 0 && global.primeLayer[param.N] < param.L set var.delayT = var.delayT - global.primeTime0 echo {state.thisInput},"delayT with prime",var.delayT ; post delay heatup var lastR = sensors.analog[param.N+1].lastReading if var.lastR < 200 set var.delayT = var.delayT - ((220-200)/global.degSec) if (200-var.lastR)/global.degSec > var.delayT set var.delayT = var.delayT - ((200-var.lastR)/global.degSec - var.delayT) echo {state.thisInput},"delayT with heatup",var.delayT ;set var.delayT = var.delayT - 1 if var.delayT <= 0 echo {state.thisInput},"SYNC not enough time to parallel tool change",floor(-var.delayT*10+0.5)/10,"secs short" else if heat.heaters[2].active < 200 echo {state.thisInput},"SYNC - other motion system not active - so no need to wait" else echo {state.thisInput},"SYNC - wait for",floor(var.delayT*10+0.5)/10,"secs" G4 P{floor(var.delayT*1000)} M568 P0 S220 R220 ;echo {state.thisInput},"heat up step2" var start = state.upTime+state.msUpTime/1000 var startReading = sensors.analog[param.N+1].lastReading echo {state.thisInput},"M116 P0 from ",{sensors.analog[param.N+1].lastReading}," to 220" M116 P0 var delayFurther = false if heat.heaters[2].active > 199 set var.delayFurther = true while sensors.analog[param.N+1].lastReading < 219 M568 P0 S220 R220 G4 P500 echo {state.thisInput},"step2 heat up time",{(state.upTime+state.msUpTime/1000-var.start)},"s",{sensors.analog[param.N+1].lastReading},"temp",{(sensors.analog[param.N+1].lastReading-var.startReading)/(state.upTime+state.msUpTime/1000-var.start)},"deg/sec" if exists(param.L) && param.L <= 0 if global.primeLayer[param.N] < param.L M98.1 A"clean T0" M801 X40 Y5 T0 S10 ; Prime M801 X40 Y5 T0 S10 ; Prime set global.primeLayer[param.N] = param.L if exists(param.L) && param.L > 0 && global.primeLayer[param.N] < param.L M801 X40 Y5 T0 S10 ; Prime set global.primeLayer[param.N] = param.L set global.T0Clean = false var timeC = state.upTime+state.msUpTime/1000 while global.uvParked = false ; move.axes[4].machinePosition <290 G4 P500 M400 echo {state.thisInput},"Waited for uv to be parked ",{state.upTime+state.msUpTime/1000-var.timeC},"secs" set global.xyParked = false echo {state.thisInput},"finished changeFilament" if exists(param.N) && param.N == 1 M596.1 P0 T1 echo {state.thisInput},"step 0 - wait for 200",{sensors.analog[param.N+1].lastReading} while heat.heaters[2].active < 200 G4 P500 ;echo {state.thisInput},"step 0 - wait for 200",{sensors.analog[param.N+1].lastReading} ;echo {state.thisInput},"M116 P1 from ",{sensors.analog[param.N+1].lastReading}," to 200" ;var start = state.upTime ;M116 P{param.N} ;echo {state.thisInput},"step 1 heat up time",{floor(state.upTime-var.start)},"s" ;**** Calculate delay var delayT = global.preHeatT echo {state.thisInput},"delayT initial",var.delayT if exists(param.L) && param.L <= 0 if global.primeLayer[param.N] < param.L set var.delayT = var.delayT - global.primeTime1*2 if exists(param.L) && param.L > 0 && global.primeLayer[param.N] < param.L set var.delayT = var.delayT - global.primeTime1 echo {state.thisInput},"delayT with prime",var.delayT ; post delay heatup var lastR = sensors.analog[param.N+1].lastReading if var.lastR < 200 set var.delayT = var.delayT - ((220-200)/global.degSec) if (200-var.lastR)/global.degSec > var.delayT set var.delayT = var.delayT - ((200-var.lastR)/global.degSec - var.delayT) echo {state.thisInput},"delayT with heatup",var.delayT ;set var.delayT = var.delayT - 1 if var.delayT <= 0 echo {state.thisInput},"SYNC not enough time to parallel tool change",-var.delayT,"secs short" else if heat.heaters[2].active < 200 echo {state.thisInput},"SYNC - other motion system not active - so no need to wait" else echo {state.thisInput},"SYNC - wait for",var.delayT,"secs" G4 P{floor(var.delayT*1000)} M568 P1 S220 R220 ;echo {state.thisInput},"heat up step2" var start = state.upTime+state.msUpTime/1000 var startReading = sensors.analog[param.N+1].lastReading echo {state.thisInput},"M116 P1 from ",{sensors.analog[param.N+1].lastReading}," to 220" M116 P1 while sensors.analog[param.N+1].lastReading < 220 M568 P1 S220 R220 G4 P500 echo {state.thisInput},"step2 heat up time",{(state.upTime+state.msUpTime/1000-var.start)},"s",{sensors.analog[param.N+1].lastReading},"temp",{(sensors.analog[param.N+1].lastReading-var.startReading)/(state.upTime+state.msUpTime/1000-var.start)},"deg/sec" var delayFurther = false if heat.heaters[1].active > 199 set var.delayFurther = true if exists(param.L) && param.L <= 0 if global.primeLayer[param.N] < param.L M98.1 A"clean T1" T1 M801 U50 V315 T1 S10 ; Prime M801 U50 V315 T1 S10 ; Prime set global.primeLayer[param.N] = param.L if exists(param.L) && param.L > 0 && global.primeLayer[param.N] < param.L M801 U50 V315 T1 S10 ; Prime set global.primeLayer[param.N] = param.L set global.T1Clean = false var timeC = state.upTime+state.msUpTime/1000 ;echo {state.thisInput},"M598 started" ;M598 ;M400 ;echo {state.thisInput},"M598 waited for ",{state.upTime+state.msUpTime/1000-var.timeC},"secs" set var.timeC = state.upTime+state.msUpTime/1000 while global.xyParked = false ; move.axes[1].machinePosition > 25 G4 P500 M400 echo {state.thisInput},"waited for xy to be parked ",{state.upTime+state.msUpTime/1000-var.timeC},"secs" set global.uvParked = false echo {state.thisInput},"finished changeFilament"

  • 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

    undefined

    @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

    undefined

    @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

    undefined

    @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

    undefined

    @andy Sorry you have a broken IR probe. We are happy to replace the board under warranty, but also happy if it's just a soldering issue and you want to fix it yourself.

    If you would like to replace it under warranty, please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.

    Ian

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

    686
    Topics
    5.4k
    Posts

    undefined

    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.

    206
    Topics
    2.2k
    Posts

    undefined

    Just want to say thanks - this works a treat!!

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

    127
    Topics
    1.3k
    Posts

    T3P3Tonyundefined

    @achrn have you considered releasing this as a plugin via plugins.duet3d.com

  • RepRapFirmware on other controllers

    30
    Topics
    352
    Posts

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

    davidjryanundefined

    @droftarts @chrishamm

    I can confirm that the re-racking occurs whenever a G92 is executed. No need for a G28 X or M98 P"homex.g".

    I can send a G92 X0 (or any other axis letter) and watch it occur in the DWC.

  • Discuss and contribute to the Duet Software Framework

    131
    Topics
    1.1k
    Posts

    undefined

    @Gamefanatic3D thanks, I have corrected the persistentGlobal.g example.

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

    405
    Topics
    3.2k
    Posts

    undefined

    @Adrian52 you should be able to reduce the overshoot by increasing the M307 R parameter a little.

    RRF only knows exactly how a move will be performed about 50ms before it is executed, so unfortunately values of advance higher than 50ms are not possible.

  • 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

    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

    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

    undefined

    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