Categories

  • Discuss setting up and using the DuetWifi and compatible hardware

    9.4k
    Topics
    88.8k
    Posts

  • Using Duet Controllers

    830
    Topics
    7.5k
    Posts

    mikeabuilderundefined

    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

    vaike_peeterundefined

    Issue
    I have issue with my DUET SZP canboard. When I start up printer everything is ok. When using SZP(homing/bed leveling/meshing) I get random Can timeout on SZP board. Sometimes it works without errors and it starts printing. Sometimes it errors out and I have to reset printer and try again. Sometimes it logs error in DWC Console but still functions as expected(home/bed level/mesh)

    Console it looks like this:
    12/04/2025, 11:24:29 Error: CAN response timeout: board 120, req type 6061, RID 35
    Error: Expansion board 120 reconnected
    12/04/2025, 11:24:27 Error: CAN response timeout: board 120, req type 6061, RID 35
    Error: Expansion board 120 reconnected

    Setup:
    MB6HC->3HC->Tooldistribution->SZP
    MB6HC - can terminated
    SZP - Can terminated.
    Tooldsitribution - SZP connected to T3, bypass jumpers removed. Also removed tooldistribution termination jumper.

    What I have done already.

    Made new canbus wire recrimped both cable ends Eliminated Tooldistribution board redid ja swapped RJ11 canbuswires between MB6HC->3HC->Tooldistribution board SZP factory reset swapped firmware 3.6.0-rc.2 -> 3.6.0-rc.1

    My current config is in github:
    https://github.com/jurikaur/trident_rrf/tree/SZP/sys

    Logs after timeot error(taken from serial console)

    M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.6.0-rc.1 (2025-02-28 15:00:13) running on Duet 3 MB6HC v1.02 or 1.02a (standalone mode) Board ID: 0JD2M-9P9DA-F0PSJ-6J1FA-3SD6R-T5RR3 Used output buffers: 2 of 40 (35 max) === RTOS === Static ram: 137420 Dynamic ram: 133488 of which 76 recycled Never used RAM 72112, free system stack 150 words Tasks: NETWORK(1,ready,34.8%,180) ETHERNET(5,nWait 7,0.2%,562) ACCEL(6,nWait 6,0 .0%,345) LASER(5,nWait 7,0.1%,235) HEAT(3,nWait 6,0.0%,341) Move(4,nWait 6,0.0%, 250) TMC(4,nWait 6,3.2%,343) CanReceiv(6,nWait 1,0.0%,794) CanSender(5,nWait 7,0 .0%,329) CanClock(7,delaying,0.0%,350) MAIN(1,running,61.1%,103) IDLE(0,ready,0. 4%,29) USBD(3,blocked,0.0%,137), total 100.0% Owned mutex=== Platform === Last reset 00:03:17 ago, cause: power up Last software reset at 2025-04-12 11:18, reason: User, Gcodes spinning, availabl e RAM 72112, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a === Storage === Free file entries: 19 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 2.5ms, write time 0.0ms, max retries 0 === Move === Segments created 40, maxWait 20080ms, 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.0 0 Pos req/act/dcf: 48000.00/48000/0.00 0.00/0/0.00 8000.00/8000/0.00 Next step interrupt due in 101 ticks, disabled Driver 0: standstill, SG min 0, mspos 340, reads 509, writes 23 timeouts 0 Driver 1: standstill, SG min n/a, mspos 8, reads 521, writes 11 timeouts 0 Driver 2: standstill, SG min 0, mspos 420, reads 509, writes 23 timeouts 0 Driver 3: standstill, SG min n/a, mspos 8, reads 521, writes 11 timeouts 0 Driver 4: standstill, SG min n/a, mspos 8, reads 521, writes 11 timeouts 0 Driver 5: standstill, SG min n/a, mspos 8, reads 516, writes 17 timeouts 0 Phase step loop runtime (us): min=0, max=85, frequency (Hz): min=941, max=10135 === Heat === Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters 2 -1 -1 -1 -1 -1 -1 -1, ordering errs 0 Heater 1 is on, I-accum = 0.0 === GCodes === Movement locks held by null, null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is ready with "M122" 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 doing "G4 S10" in state(s) 0 0, running macro 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 1792, received 3353, lost 0, ignored 0, errs 0, boc 0 Longest wait 3ms for reply type 6061, peak Tx sync delay 165, free buffers 50 (m in 49), ts 935/934/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 788.84ms; fastest: 0.03ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 2 of 8 === Multicast handler === Responder is inactive, messages received 0, responses 0 = Ethernet = Interface state: active Error counts: 0 0 0 1 0 0 Socket states: 2 2 2 2 2 2 0 0 0 === WiFi === Interface state: disabled Module is disabled Failed messages: pending 0, notrdy 0, noresp 0 Socket states: 0 0 0 0 0 0 0 0 ok M122 b1 Diagnostics for board 1: Duet EXP3HC rev 1.02 or later firmware version 3.6.0-rc.1 (2025-02-28 15:01:59) Bootloader ID: SAME5x bootloader version 2.11 (2024-08-09) All averaging filters OK Never used RAM 169368, free system stack 172 words Tasks: Move(3,nWait 7,0.0%,144) TMC(2,nWait 6,7.3%,61) HEAT(2,nWait 6,0.0%,130) CanAsync(5,nWait 4,0.0%,70) CanRecv(3,nWait 1,0.0%,74) CanClock(5,nWait 1,0.0%,64) MAIN(1,running,91.5%,413) IDLE(0,ready,0.0%,39) AIN(2,delaying,1.2%,263), total 100.0% Owned mutexes: Last reset 00:03:50 ago, cause: power up Last software reset data not available Moves scheduled 6, hiccups 0 (0.00/0.00ms), segs 33, step errors 0 (types 0x0), maxLate 0 maxPrep 98, ebfmin 0.00 max 0.00 Peak sync jitter -7/5, peak Rx sync delay 186, resyncs 0/0, no timer interrupt scheduled, next step interrupt due in 4155325809 ticks, disabled VIN voltage: min 24.3, current 24.5, max 24.5 V12 voltage: min 12.3, current 12.3, max 12.3 MCU temperature: min 26.3C, current 28.5C, max 28.5C Driver 0: pos -31, 400.0 steps/mm, standstill, SG min 0, mspos 504, reads 41044, writes 29 timeouts 0 Driver 1: pos -31, 400.0 steps/mm, standstill, SG min 0, mspos 504, reads 41044, writes 29 timeouts 0 Driver 2: pos -31, 400.0 steps/mm, standstill, SG min 0, mspos 536, reads 41045, writes 29 timeouts 0 Last sensors broadcast 0x00000000 found 0 207 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 2826, send timeouts 0, received 2205, lost 0, ignored 0, errs 0, boc 0, free buffers 38, min 38, error reg 0 dup 0, oos 0/0/0/0, rxMotionDelay 399, adv 37011/37070 ok M122 b120 Diagnostics for board 120: Duet SZP firmware version 3.6.0-rc.1 (2025-02-28 15:03:22) Bootloader ID: SAMC21 bootloader version 2.10 (2023-11-16) All averaging filters OK Never used RAM 11852, free system stack 112 words Tasks: ScanSens(6,nWait 6,13.6%,50) HEAT(2,nWait 6,0.1%,126) CanAsync(5,nWait 4,0.0%,54) CanRecv(3,nWait 1,0.0%,64) CanClock(5,nWait 1,0.0%,52) ACCEL(3,nWait 6,0.0%,72) MAIN(1,running,54.7%,420) IDLE(0,ready,0.0%,26) AIN(2,nWait 2,31.6%,112), total 100.0% Owned mutexes: Last reset 00:03:36 ago, cause: software Last software reset at 2025-04-12 11:24, reason: HardFault, available RAM 11776, slot 0 Software reset code 0x0060 ICSR 0x00000003 SP 0x200047b0 Task Scan Freestk 110 ok Stack: 00000000 00000001 00000000 00000000 20002fe4 0000e1c5 000065cc 81000000 20002cb0 0000e1c5 00000000 a5a5a5a5 a5a5a5a5 20002cb8 20002c8c 20002cb4 20002c84 20002c9c 20002c88 20002c94 20002c98 20002c90 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 Peak sync jitter 1/5, peak Rx sync delay 277, resyncs 0/0, no timer interrupt scheduled VIN voltage: min 4.8, current 4.8, max 4.9 MCU temperature: min 25.8C, current 26.1C, max 26.1C Last sensors broadcast 0x00000000 found 0 71 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 908, send timeouts 0, received 1914, lost 0, ignored 0, errs 0, boc 0, free buffers 18, min 18, error reg 0 Accelerometer: LIS2DW, status: 00 Inductive sensor: raw value 36560899, frequency 3.40MHz, current setting 16, ok I2C bus errors 0, naks 3, contentions 0, other errors 0

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

    582
    Topics
    5.1k
    Posts

    Tool88undefined

    I seen that this has been brought up once before in a older post, but am wondering if the newer reprap can do canned cycles
    I am in the process of purchasing all the things I need to build a new mill fixed gantry, I not sure what motion controller I want to go with, I would like the options for tapping and boring.

    Also is reprap capable of i-0. J-0. Commands

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

    tcamguilundefined

    @dc42, it is working now. Thank you for the quick update.

    I guess it could be a bad connection.But why does it happens at random points on the buildplate. And why can't I reproduce the issue on RRF 3.6.0-RC.1 or before. Could it be an issue with the debouncer ?

    I switched to a NO sensor and the issue is now flipped the error is now "Error: G29: Probe already triggered before probing move started". and the Z-probe status is stuck in the triggered state until I trigger/un trigger it manually.

  • Discuss using conditionals, loops and variables in gcode

    793
    Topics
    5.6k
    Posts

    dc42undefined

    @mikeabuilder bouncing is not normally a problem with PanelDue so perhaps something is wrong with the touch membrane. Maybe your enclosure is pressing against it enough to increase its sensitivity but it enough to cause a permanent trigger.

    BTW the most precise way to touch the PanelDue buttons is to use the.tip of your fingernail, not the pad of your finger.

    The buttons auto-repeat if you maintain the pressure.

  • Ask questions about the official web interface here

    1.6k
    Topics
    13.1k
    Posts

    Phaedruxundefined

    I see you already have a thread started here. Please keep it limited to one thread per issue.

    https://forum.duet3d.com/topic/37842/printer-not-hitting-any-of-the-endstops

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

    o_lampeundefined

    @dwuk3d In the end we'll see a conveyor belt bed with dozends of tools heads zipping around simultaneously... 😳
    But seriously: you could do the same split_the object_trick in a big scale manner.

    Build two independent printers with 4 heads each place them above the looong conveyor belt with a certain gap print parts 1 + 3 move the belt and print part 2 + 4 move back and repeat

  • 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

    droftartsundefined

    @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

    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

    phoenixundefined

    Encouraged by the post by @cdoe on setting up the Orbiter 2 filament sensor, I gave it a hard try to set up the Smart Orbiter 3. All features are working and I come amazed at the power of RRF 🙂

    The Smart Orbiter 3 has 8 connections at the base, containing a RGB Matrix LED connection, a simple hotend LED and 2 outputs (FS for sensing if filament is present) and FTU (outputs if filament is tangled or filament unload button is pressed). (check the website https://www.orbiterprojects.com/so3/ in section 3.3 Integrated Smart Features for polarity: I spent a day trying to figure out why nothing was working only to discover that blue and red wires are NOT GND and 3V 🙂 )

    Similar to the Orbiter 2 Sensor, the set up is slightly more elaborate than just a sensor since both outputs have 2 functions and logic is not straightforward as well. FS output works as expected as in changing state when filament is present or runs out, FTU output only changes state if filament is already present.

    I am running a e3d toolchanger with Duet 2 Wifi and DueX5. I connected the cables to the pins 1 -6 of the LCD connector. (all works just fine on 3.3V) and reused triggers developed by @cdoe for things to work.

    This is a section in config.g

    ; Filament Sensor & Smart H2 M950 J3 C"^connlcd.enca" ; define logical input for filament auto load M581 P3 T5 S1 R0 ; define trigger for filament auto load triggers trigger5.g M581 P3 T2 S0 R0 ; define trigger for filament sensing triggers trigger2.g M950 J4 C"^connlcd.encb" ; define logical input for filament unload M581 P4 T6 S1 R0 ; define trigger for filament auto unload triggers trigger6.g M950 P5 C"connlcd.rs" ; define logical output for hotend LED M950 E0 C"connlcd.5" T1 U1 ; create a RGB Neopixel LED strip on the LCD Connector 5 port (RRF 3.5 and later) M98 P"0:/macros/h2led" ; Set LED Colour according to state of H2 M42 P5 S0 ; Turn Hotend LED off

    Obviously the most important part is getting the matrix LED to work 😁 with a macro I called h2led.g

    ; Sets MatrixLED according to filament Sensor status if sensors.gpIn[3].value = 1 M150 E0 R000 U255 B000 P255 ; set LEDs to green, full brightness else M150 E0 R255 U000 B000 P128 ; set LEDs to red, half brightness

    Triggers 2, 5 & 6 reuse the macros developed for the smart orbiter

    ; trigger2.g if state.status == "processing" M300 S2000 P100 ; play beep sound M291 P"Ran out of filament while printing" S0 T3 ; display message M25 elif state.status == "pausing" || state.status == "paused" M291 P"Retriggered filament sensor during pause" ; display message else M300 S2000 P100 ; play beep sound M291 P"Ran out of filament" S0 T3 ; display message

    For the load and unload triggers, I am using a single printer macro for all toolheads for loading and unloading. As such, I pass on a parameters representing the toolhead to the macro for addressing the right toolhead. And then obviously triggering the color LED macro at the end of it to adjust LED according to status.

    ; trigger5.g M150 E0 R000 U000 B255 P128 ; set LEDs to blue, half brightness M98 P"0:/macros/filament-load" X2 ; Load Filament for T2 M98 P"0:/macros/h2led" ; Set LED Colour according to state of H2 T-1 ; Park tool ; trigger6.g if state.status = "processing" M300 S2000 P100 ; play beep sound M291 P"Filament is stuck or filament unload button pressed" S0 T3 ; display message M150 E0 R000 U000 B255 P128 ; set LEDs to blue, half brightness M25 else M150 E0 R000 U000 B255 P128 ; set LEDs to blue, half brightness M98 P"0:/macros/filament-unload" X2 ; Call Unload Macro and pass Tool number using X parameter M98 P"0:/macros/h2led" ; Set LED Colour according to state of H2 T-1

    Hope this helps somebody else - it's a nifty little extruder and I'm stoked the electronics are now fully integrated!

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

    127
    Topics
    1.3k
    Posts

    stuartofmtundefined

    @jonsteinmetz

    Also does this return any results?

    sudo find / -name cv2

  • 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

    sebkritikelundefined

    @droftarts and @dc42 , thanks for explaining that!

    Looks like in the "connecting fan documentation" there is a similar note (as what was explained to me above) for the Duet 2.. Perhaps indicating that is also applicable to (at least) the 6HC and 6XD would be sufficient.

  • Discuss and contribute to the Duet Software Framework

    131
    Topics
    1.1k
    Posts

    dc42undefined

    @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

    dc42undefined

    @Triet we do process a lot of segments together, however we need to retain low latency for starting movement and for pausing. If you want to advance feedforward by 6 seconds then that means we would have to delay starting moton for 6 seconds from when you send the first motion command; otherwise how can we apply the correct feedforward to that first move? Similarly we would have to delay responding to a pause command for 6 seconds so that we don't apply incorrect feedforward to moves that have already been queued.

    The compromise we have chosen is to use 50ms latency. So moves already in the queue can be amended up to about 50ms before they are due to start. We could maybe increase it to 100ms without users complaining too much, but certainly not to 6 seconds.

  • 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