Categories

  • Discuss setting up and using the DuetWifi and compatible hardware

    9.4k
    Topics
    88.7k
    Posts

    dc42undefined

    @coseng I'm sorry to hear that your project is shutting down. I suggest you post in a new thread with "For sale" in the title and give the machine specifications and your location in that post.

  • 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

    davidjryanundefined

    My setup:
    1 6HC, SBC mode, CNC mode, non-printer application
    3 3HC
    All boards at 3.5.4
    13 stepper motors, 10 Nema17 and 3 Nema23
    Pi5 4GB with DuetPi from Nov. 2024
    Power supply is 24V, 20A split to all 4 boards

    My machine has been running for a year now and just this week, I am suddenly getting resets from the 3HC boards.

    I have expansion-timeout and expansion-reconnect report out the board # when an event occurs, so when the latest reset occurred on board 3, in the DWC, I get :
    d9e8defc-b967-4ebf-81a5-83a66682ebba-image.png

    I then pulled an M122 B3 and M122.

    M122 B3 before the disconnect/reset

    4/9/2025, 12:20:37 PM M122 B3 Diagnostics for board 3: Duet EXP3HC rev 1.02 or later firmware version 3.5.4 (2024-11-24 10:40:29) Bootloader ID: SAME5x bootloader version 2.11 (2024-08-09) All averaging filters OK Never used RAM 156540, free system stack 178 words Tasks: Move(3,nWait 7,0.0%,145) HEAT(2,nWait 6,0.0%,130) CanAsync(5,nWait 4,0.0%,62) CanRecv(3,nWait 1,0.0%,74) CanClock(5,nWait 1,0.0%,63) TMC(2,nWait 6,6.8%,95) MAIN(1,running,92.0%,438) IDLE(0,ready,0.0%,39) AIN(2,delaying,1.1%,259), total 100.0% Owned mutexes: Last reset 00:09:49 ago, cause: power up Last software reset data not available Driver 0: pos 0, 8.9 steps/mm, standstill, SG min 0, mspos 8, reads 61258, writes 16 timeouts 0, steps req 0 done 0 Driver 1: pos 0, 6.7 steps/mm, standstill, SG min 0, mspos 8, reads 61258, writes 16 timeouts 0, steps req 0 done 0 Driver 2: pos 1351998, 1600.0 steps/mm, standstill, SG min 0, mspos 584, reads 61258, writes 17 timeouts 0, steps req 0 done 403620 Moves scheduled 9, completed 9, in progress 0, hiccups 0, segs 6, step errors 0, maxLate 0 maxPrep 16, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 0.00 Peak sync jitter -6/6, peak Rx sync delay 184, resyncs 0/0, no timer interrupt scheduled VIN voltage: min 23.8, current 23.8, max 24.1 V12 voltage: min 12.3, current 12.3, max 12.4 MCU temperature: min 30.5C, current 30.8C, max 33.1C Last sensors broadcast 0x00000000 found 0 73 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 4869, send timeouts 0, received 5311, lost 0, errs 0, boc 0, free buffers 38, min 38, error reg 0 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 403, adv 37023/37086

    M122 B3 after the disconnect/reset

    4/9/2025, 12:57:22 PM M122 B3 Diagnostics for board 3: Duet EXP3HC rev 1.02 or later firmware version 3.5.4 (2024-11-24 10:40:29) Bootloader ID: SAME5x bootloader version 2.11 (2024-08-09) All averaging filters OK Never used RAM 156684, free system stack 180 words Tasks: Move(3,nWait 7,0.0%,128) HEAT(2,nWait 6,0.0%,132) CanAsync(5,nWait 4,0.0%,66) CanRecv(3,nWait 1,0.0%,74) CanClock(5,nWait 1,0.0%,64) TMC(2,nWait 6,7.0%,61) MAIN(1,running,91.8%,387) IDLE(0,ready,0.0%,39) AIN(2,delaying,1.1%,264), total 100.0% Owned mutexes: Last reset 00:04:28 ago, cause: reset button Last software reset data not available Driver 0: pos -17952, 80.0 steps/mm, standstill, SG min 0, mspos 200, reads 56767, writes 16 timeouts 0, steps req 0 done 20268 Driver 1: pos 0, 80.0 steps/mm, standstill, SG min n/a, mspos 840, reads 56770, writes 13 timeouts 0, steps req 0 done 0 Driver 2: pos -994, 80.0 steps/mm, standstill, SG min 0, mspos 712, reads 56770, writes 14 timeouts 0, steps req 0 done 2240 Moves scheduled 13, completed 13, in progress 0, hiccups 0, segs 6, step errors 0, maxLate 0 maxPrep 17, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 0.00 Peak sync jitter -6/6, peak Rx sync delay 180, resyncs 0/0, no timer interrupt scheduled VIN voltage: min 22.2, current 23.8, max 23.9 V12 voltage: min 12.3, current 12.3, max 12.4 MCU temperature: min 34.0C, current 34.2C, max 35.5C Last sensors broadcast 0x00000000 found 0 157 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 2169, send timeouts 0, received 2437, lost 0, errs 0, boc 0, free buffers 38, min 38, error reg 0 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 399, adv 36151/37197

    I can assure you that no one is pressing the reset button on the 3HC board.

    M122 for 6HC after the disconnect/reset

    4/9/2025, 12:59:37 PM M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.5.4 (2024-11-24 10:47:10) running on Duet 3 MB6HC v1.01 (SBC mode) Board ID: 08DJM-9P63L-DJMSS-6J9F0-3SN6N-9UHZA Used output buffers: 1 of 40 (24 max) === RTOS === Static ram: 155464 Dynamic ram: 98656 of which 0 recycled Never used RAM 18360, free system stack 138 words Tasks: SBC(2,ready,2.0%,747) HEAT(3,nWait 6,0.0%,351) Move(4,nWait 6,0.1%,211) CanReceiv(6,nWait 1,0.0%,769) CanSender(5,nWait 7,0.0%,329) CanClock(7,delaying,0.0%,346) TMC(4,nWait 6,9.2%,53) MAIN(2,running,87.5%,444) IDLE(0,ready,1.2%,29), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:48:49 ago, cause: power up Last software reset at 2025-04-09 12:10, reason: User, Expansion spinning, available RAM 19224, slot 0 Software reset code 0x6012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a Error status: 0x00 MCU temperature: min 40.6, current 44.0, max 44.3 Supply voltage: min 21.7, current 23.7, max 23.8, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.2, current 12.3, max 12.3, under voltage events: 0 Heap OK, handles allocated/used 297/281, heap memory allocated/used/recyclable 6144/5008/80, gc cycles 59 Events: 1 queued, 1 completed Driver 0: standstill, SG min 0, mspos 600, reads 60927, writes 6 timeouts 0 Driver 1: standstill, SG min 0, mspos 1016, reads 60927, writes 6 timeouts 0 Driver 2: standstill, SG min n/a, mspos 8, reads 60933, writes 0 timeouts 0 Driver 3: standstill, SG min 0, mspos 280, reads 60927, writes 6 timeouts 0 Driver 4: standstill, SG min 0, mspos 184, reads 60928, writes 6 timeouts 0 Driver 5: standstill, SG min 0, mspos 520, reads 60927, writes 6 timeouts 0 Date/time: 2025-04-09 12:59:37 Slowest loop: 57.87ms; fastest: 0.04ms === Storage === Free file entries: 20 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 125, segments created 6, maxWait 203822ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === Scheduled moves 1659, completed 1659, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 272], CDDA state -1 === DDARing 1 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === GCodes === Movement locks held by null, null HTTP* is doing "M122" in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger* is idle in state(s) 0 Queue* is idle in state(s) 0 LCD is idle in state(s) 0 SBC* is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 0, axes/extruders owned 0x0000000 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 22635, received 58478, lost 0, errs 0, boc 0 Longest wait 3ms for reply type 6024, peak Tx sync delay 274, free buffers 50 (min 48), ts 11735/11735/0 Tx timeouts 0,0,0,0,0,0 === SBC interface === Transfer state: 5, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 20833/20833 SPI underruns 0, overruns 0 State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x24cfc Buffer RX/TX: 0/0-0, open files: 0 === Duet Control Server === Duet Control Server version 3.5.4 (2024-11-25 17:32:26, 64-bit) HTTP+Executed: > Executing M122 Code buffer space: 4096 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 9 Full transfers per second: 53.22, max time between full transfers: 45.8ms, max pin wait times: 32.9ms/6.1ms Codes per second: 3.93 Maximum length of RX/TX data transfers: 6217/944

    config.g

    ; General preferences M453 ; set CNC mode M550 P"A1000-0" ; set name of controller G90 ; set absolute coordinates G4 P1000 ; 1s delay for CAN comms ; Drives ; Motors are wired to Duet A-A, B-B - motor directions are flipped here M569 P0.0 S0 ; physical drive 0.0 goes forwards M569 P0.1 S0 ; physical drive 0.1 goes forwards M569 P0.2 S0 ; physical drive 0.2 goes forwards M569 P0.3 S1 ; physical drive 0.3 goes reverse M569 P0.4 S1 ; physical drive 0.4 goes reverse M569 P0.5 S1 ; physical drive 0.5 goes reverse M569 P1.0 S0 ; physical drive 1.0 goes forwards M569 P1.1 S0 ; physical drive 1.1 goes forwards M569 P1.2 S0 ; physical drive 1.2 goes forwards M569 P2.0 S1 ; physical drive 2.0 goes reverse M569 P2.1 S1 ; physical drive 2.1 goes reverse M569 P2.2 S0 ; physical drive 2.2 goes forwards M569 P3.0 S0 ; physical drive 3.0 goes forwards M569 P3.1 S0 ; physical drive 3.1 goes forwards M569 P3.2 S0 ; physical drive 3.2 goes reverse ; Set motion system queue parameters M595 P100 R50 Q0 ; set motion system queue 0 to 100 steps M595 P100 R50 Q1 ; set motion system queue 1 to 100 steps ; Set drive mapping M584 X0.0 Z0.1 R0 ; set linear drive mapping for gantry M584 A0.2 B0.3 C0.4 D0.5 R0 ; set linear drive mapping for cartridges M584 Y1.2 W3.0 R0 ; set linear drive mapping for slitter and duckbill M584 'A2.0 'B2.1 'D2.2 'E1.0 'F1.1 R1 ; set rotary drive mapping for napkin table and slitter feeding ; Set microstepping interpolation M350 X16 Z16 A16 B16 C16 D16 Y16 W16 I1 ; configure microstepping with interpolation for linear motors M350 'A16 'B16 'D16 'E16 'F16 I1 ; configure microstepping with interpolation for rotary motors ; Set axes scale values M92 X60.00 Z507.00 A1520.50 B1520.50 C1520.50 D1520.50 Y54.00 W53.75 ; set steps per mm M92 'A20.90 'B8.88 'D10.50 'E9.00 'F9.00 ; set steps per degree ; Set max speed change values M566 X400.00 Z400.00 A400.00 B400.00 C400.00 D400.00 Y400.00 W400.00 ; set maximum instantaneous speed changes (mm/min) M566 'A450.00 'B900.00 'D500.00 'E450.00 'F450.00 ; set maximum instantaneous speed changes (mm/min) ; Set max speeds M203 X40000.00 Z20000.00 A5000.00 B5000.00 C5000.00 D5000.00 Y30000.00 W7000.00 ; set maximum speeds (mm/min) M203 'A30000.00 'B35000.00 'D5000.00 'E40000.00 'F40000.00 ; set maximum speeds (mm/min) ; Set accelerations M201 X3000.00 Z1500.00 A500.00 B500.00 C500.00 D500.00 Y2000.00 W1000.00 ; set accelerations (mm/s^2) M201 'A2000.00 'B2000.00 'D1000.00 'E5000.00 'F2000.00 ; set accelerations (mm/s^2) ; Set motors currents and idle factor M906 X2000 Z1400 A3000 B3000 C3000 D3000 Y1500 W1500 I5 ; set motor currents (mA) and motor idle factor in per cent M906 'A3500 'B2800 'D2800 'E1500 'F2800 I5 ; set motor currents (mA) and motor idle factor in per cent ; Set idle timeout M84 S30 ; Set idle timeout ; Axis Limits - minimum M208 X-2 Z-85 A-5 B-5 C-5 D-5 Y-2 W-2 S1 ; set linear axis minimum M208 'A-5 'B-30 'D-5 'E-100 'F-30 S1 ; set rotary axis minimum ; Axis Limits - maximum M208 X601 Z50 A200 B380 C380 D380 Y195 W200 S0 ; set linear axis maximum M208 'A400 'B10000 'D180 'E10000 'F10000 S0 ; set rotary axis maximum ; Endstops M574 X1 S1 P"!^3.io4.in" ; M574 Y1 S1 P"!^2.io4.in" ; M574 Z1 S1 P"!^3.io5.in" ; M574 A1 S1 P"!^3.io0.in" ; M574 B1 S1 P"!^3.io1.in" ; M574 C1 S1 P"!^3.io2.in" ; M574 D1 S1 P"!^3.io3.in" ; M574 W1 S1 P"!^0.io6.in" ; M574 'A1 S1 P"!^2.io0.in" ; M574 'B1 S1 P"!^2.io1.in" ; M574 'D1 S1 P"!^2.io2.in" ; M574 'E2 S1 P"!^0.io8.in" ; ; Inputs - for use with M581/2 commands M950 J0 C"!^0.io0.in" ; M950 J1 C"!^0.io1.in" ; M950 J2 C"!^0.io2.in" ; Spare M950 J3 C"!^0.io3.in" ; M950 J4 C"!^0.io4.in" ; spare M950 J5 C"!^0.io5.in" ; spare M950 J7 C"!^0.io7.in" ; M950 J10 C"!^1.io0.in" ; M950 J11 C"!^1.io1.in" ; M950 J12 C"!^1.io2.in" ; M950 J13 C"!^1.io3.in" ; M950 J14 C"!^1.io4.in" ; M950 J15 C"!^1.io5.in" ; M950 J23 C"!^2.io3.in" ; spare M950 J25 C"!^2.io5.in" ; Napkin Cartridge Present ; Thermister configuration (if installed) M308 S0 P"temp0" Y"thermistor" T100000 B4261 ; sensor 0 M308 S1 P"temp1" Y"thermistor" T100000 B4261 ; sensor 1 ; Outputs - for use with M42 commands ; Board 0 M950 P0 C"0.io0.out" ; M950 P1 C"0.io1.out" ; M950 P2 C"0.io2.out" ; M950 P3 C"0.io3.out" ; M950 P4 C"0.io4.out" ; Spare M950 P5 C"0.io5.out" ; Spare M950 P6 C"0.io6.out" ; M950 P7 C"0.io7.out" ; M950 P8 C"0.io8.out" ; Spare ; Board 1 M950 P9 C"1.io0.out" ; Spare M950 P10 C"1.io1.out" ; Spare M950 P11 C"1.io2.out" ; Spare M950 P12 C"1.io3.out" ; Spare M950 P13 C"1.io4.out" ; Spare M950 P14 C"1.io5.out" ; Spare ; Board 2 M950 P15 C"2.io0.out" ; Spare M950 P16 C"2.io1.out" ; Spare M950 P17 C"2.io2.out" ; Spare M950 P18 C"2.io3.out" ; Spare M950 P19 C"2.io4.out" ; Spare M950 P20 C"2.io5.out" ; Spare ; Board 3 M950 P21 C"3.io0.out" ; Spare M950 P22 C"3.io1.out" ; Spare M950 P23 C"3.io2.out" ; Spare M950 P24 C"3.io3.out" ; Spare M950 P25 C"3.io4.out" ; Spare M950 P26 C"3.io5.out" ; Spare ; Fan configuration (if installed) ; 4 Wire Fan Configuration M950 F0 C"!0.out4+out4.tach" K2 ; 3 Wire Fan Configuration ;M950 F0 C"0.out4+out4.tach" K2 ; Turn on fan to initial setting ;M106 P0 S1 B0.5 ; NeoPixel RGBW LED Strip configuration M950 E0 C"led" T2 Q3000000

    I have 3 boards addressed 1, 2, 3. 2 and 3 seem to do it most of the time. The CAN cable goes from 6HC to B3, then B2, then B1 with B1 terminated. I have switched the cable to 6HC, B1, B2, B3 with B3 terminated, I have swapped/replaced boards and CAN cables, and the issue persists. With 45 minutes of a power up, the problem will happen. I have to power down and back up and the machine can run again.

    I have not made any electrical or software changes in the last week. I even rolled back to an older software change made 3 weeks ago, just in case, to no avail.

    So, other than actually pushing the reset button, what else causes the 3HC to report a push button reset as the cause for the last reset?

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

    581
    Topics
    5.1k
    Posts

    dc42undefined

    @dhusolo yes that should work.

  • 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

    Macgyverundefined

    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

    dc42undefined

    @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

    rodneysramosjundefined

    thanks for all the help on the last post, however... we are running into an issue after successfully homing in which we cannot manually move away from the end stop only towards it. I will attach the home and config files we are currently using. thanks in advance. config.g homeall.g homex.g homey.g homez.g

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

    dwuk3dundefined

    Been dusting off some maths knowledge today to try and more accurately position my print head over the top of the camera after auto aligning with the ball probe.

    A7039D04-80CD-4B60-B53E-3EC8EFAFB59B_1_105_c.jpeg

    Firstly used a few captured nozzle probe and manually aligned readings, plus some measurements of the distance of the probe and camera from the servo pivot point to try and work out the XY coordinates of the servo pivot point.

    With a bit of trial and error I found some numbers that worked

    4C00C0AC-A9BE-48BA-9EE6-26393C501621.png

    Then wrote this macro to calculate the camera position from ball probed UV coordinates - really please to see SIN/COS/ASIN/ACOS functions available...

    ;cameraFromUV.g M98 P"0:/macros/ParkXY.g" ;probe U 251.3187 offset U -13.6500092 probe V 202.1375 offset V 41.20003 ;probe U 251.0562 offset U -14.2998352 probe V 199.4344 offset V 41.00005 ;probe U 250.8687 offset U -14.7497253 probe V 197.4219 offset V 40.84999 ;probe U 250.8938 offset U -14.6997528 probe V 197.5125 offset V 40.85002 ;probe U 250.8000 offset U -15.0500336 probe V 196.2250 offset V 40.80002 ;probe U 250.9875 offset U -14.4999847 probe V 198.0063 offset V 40.89999 ; ;G1 U251.4 V202.8 F10000 var uPos = global.ballProbeU+14.5 var vPos = global.ballProbeV-40.9 var servoX = 427.9 var servoY = 188.3 var probePosRadius = 177 var cameraPosRadius = 165 var cameraOffsetAngle = 14 var probeAngle = degrees(asin((global.ballProbeV-var.servoY)/var.probePosRadius)) if var.probeAngle < 90 set var.probeAngle = 180 - var.probeAngle var cameraX = var.servoX + var.cameraPosRadius * cos(radians(var.probeAngle+var.cameraOffsetAngle)) var cameraY = var.servoY + var.cameraPosRadius * sin(radians(var.probeAngle+var.cameraOffsetAngle)) echo "U",global.ballProbeU,"V",global.ballProbeV,"angle",var.probeAngle,"cX",var.cameraX,"cY",var.cameraY if var.cameraX > 200 && var.cameraX < 300 && var.cameraY > 140 && var.cameraY < 200 set var.uPos = var.cameraX set var.vPos = var.cameraY else abort "cameraFromUV.g - suspect camera calculations" if exists(global.savedU) == false global savedU = -1 global savedV = -1 set global.savedU = var.uPos set global.savedV = var.vPos G1 U{var.uPos} V{var.vPos} F10000 if exists(global.servo5Off) && global.servo5Off > 0 set global.servo5Off = state.upTime + 120 if exists(global.magnetOff) && global.magnetOff > 0 set global.magnetOff = state.upTime + 120

    results pretty good - all photos are auto alignment and direct move to the camera

    Notice the benefits of a camera over a ball probe in first photo - where the ball probe misaligned due to dirty nozzle.

    CD349ED4-4B6A-4E43-B6DE-409E440201D6.png D53B73F8-6BB3-467D-904D-2E66897DA56B.jpeg

    UV
    E80FAC17-028F-4E14-B55C-F5DFA7F070F6.png
    XY after cleaning
    DBF28CF1-BFE1-4B81-9F4D-D7622581E1C7.png

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

    116
    Topics
    793
    Posts

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

    DueUI
    178
    Topics
    2.5k
    Posts

    stuartofmtundefined

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

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

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

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

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

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

  • Accessories and Add-ons

    66
    Topics
    601
    Posts

    jay_s_ukundefined

    @dwuk3d yes, it'll work with that

  • Forum for discussing the Duet3d Filament Monitor

    397
    Topics
    3.9k
    Posts

    T3P3Tonyundefined

    @adrien_tobeca more recent firmware reports the raw angle:

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

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

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

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

  • Discuss the smart PCB effector for delta printers here.

    411
    Topics
    4.1k
    Posts

    elmoretundefined

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

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

  • No decsciption available

    232
    Topics
    1.9k
    Posts

    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.

    206
    Topics
    2.2k
    Posts

    phoenixundefined

    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

    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

    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

    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

    Adrian52undefined

    @dc42 Have been wondering if a post process would be possible, and came across this article
    https://www.nature.com/articles/s41467-025-56140-1#MOESM1
    A rather impeccable source - maybe this is the way things might develop.

  • 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