Categories

  • Discuss setting up and using the DuetWifi and compatible hardware

    9.4k
    Topics
    89.2k
    Posts

    dc42undefined

    @JayT :

    Can you confirm that you obtained those prints using firmware 3.6.0-rc.3 ? Does the centre frequency of the ringing reported by the accelerometer and closed loop plugin agree with what you measure? Measure the period of ringing in mm on the print (ignoring the ringing closest to the edge) and divide that into your speed of 60mm/sec to get the ringing frequency. Can you post a print taken with IS disabled so that we can see what different IS is making? There is a checkbox in the IS plugin called "measure over the whole move" or something like that. I believe you have that checked. What does the plot produced by the IS plugin look like oi you un-check that box and take a measurement?

  • Using Duet Controllers

    835
    Topics
    7.5k
    Posts

    gloomyandyundefined

    @droftarts phase disconnection is mentioned here:

    Driver warning (e.g. over temperature warning, or phase disconnected, or closed loop driver position difference warning limit exceeded)

    on this page: https://docs.duet3d.com/User_manual/RepRapFirmware/Events#events

    So it would seem it is indeed a warning that will trigger driver-warning.g

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

    8.6k
    Topics
    77.1k
    Posts

    droftartsundefined

    @kumar22222 See https://docs.duet3d.com/User_manual/Connecting_hardware/Motors_connecting_external

    The Mini 5+ can support two external drivers, connected directly to the mainboard, so long as the external driver can accept 3.3V single-ended signalling. Otherwise, you can connect them to a Duet 3 1XD external driver board, connected to the Mini 5+ via CAN.

    Ian

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

    590
    Topics
    5.2k
    Posts

    droftartsundefined

    @o_lampe said in Closed loop firmware for CNC:

    AFAIK, the current closed loop strategy in RRF is to add the missed steps to the axis involved.

    I don't think that is correct. RRF sends a profile of the move via CAN, not step pulses. In closed loop mode, the 1HCL moves to the position at the speed dictated by the move profile. It doesn't really use steps; it uses the feedback from the encoder to position the motor. If the motor isn't keeping position, it increases current (up to a defined limit) until the motor has enough torque to achieve position. If it still can't keep position, it raises a driver error.

    Ian

  • Prototype hardware issues.

    30
    Topics
    834
    Posts

    dwuk3dundefined

    @dc42 Thanks will switch to that version

  • Discuss Duet on laser cutters and engravers.

    184
    Topics
    1.5k
    Posts

    droftartsundefined

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

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

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

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

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

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

    Ian

  • Ask questions about installing the firmwares here

    2.1k
    Topics
    23.7k
    Posts

  • Speed, acceleration, microstepping etc - post your experiences of and questions about how to get the best out of the Duet WiFi here.

    5.3k
    Topics
    54.9k
    Posts

    Hannahundefined

    My CNC machine has 2 motors on the X axis, they are 1HCL boards.
    Board 51 keeps giving me " warning: position tolerance exceeded" by the dozens. But only when traveling in the positive direction. This happens at pretty much every speed

    I tried:

    setting acceleration verry low reduced the amount of microsteps played with dozens of feedrates

    The machine seems to work great besides spamming my console with warnings.
    Board 50 never gave me a warning, even at ludicrous speeds. And it doesn't happen in the negative direction.

    I am out of ideas. Does anyone have any suggestions?

    Running FW 3.6.0-rc.3
    config.g:

    ; General preferences G90 ; send absolute coordinates... M550 P"RatRig" ; set machine name ; Network M552 P0.0.0.0 S1 ; enable network with DHCP M586 P0 S1 ; enable HTTP M586 P1 S1 ; enable FTP M586 P2 S0 ; disable Telnet ; Internal Serial M575 P1 S7 B57600 M575 P2 S1 B57600 ; -------------------- ; Wait for CAN startup ; -------------------- G4 S1 ; ------------------- ; Define CAN endstops ; ------------------- M574 X1 S1 P"50.io0.in" M574 Y1 S1 P"52.io0.in" M574 Z1 S1 P"53.io0.in" ; ----------------- ; Define CAN motors ; ----------------- ; X0 adress 50 M569.1 P50.0 T2 C1000 R100 ; Quadrature encoder, 1000 steps, 100 Proportional constant M569 P50.0 S0 D0 ; Start in open loop mode ; X1 adress 51 M569.1 P51.0 T2 C1000 R100 ; Quadrature encoder, 1000 steps, 100 Proportional constant M569 P51.0 S0 D0 ; Start in open loop mode ; Y0 adress 52 M569.1 P52.0 T2 C1000 R100 ; Quadrature encoder, 1000 steps, 100 Proportional constant M569 P52.0 S0 D0 ; Start in open loop mode ; Z0 adress 53 M569.1 P53.0 T2 C1000 R100 ; Quadrature encoder, 1000 steps, 100 Proportional constant M569 P53.0 S0 D0 ; Start in open loop mode ; ----------------------- ; Define coordinate sytem ; ----------------------- M584 X50.0:51.0 Y52.0 Z53.0 ; set drive mapping M350 X8 Y8 Z8 I1 ; configure microstepping with interpolation M92 X160 Y160 Z400 ; set steps per mm M566 X0 Y0 Z0 ; set maximum instantaneous speed changes (mm/min) M203 I10 ; set minimum speed to (mm/min) M203 X3200 Y3200 Z600 ; set maximum speeds (mm/min) M201 X300 Y300 Z300 ; set accelerations (mm/s^2) M906 X4000 Y4000 Z4000 I70 ; set motor currents (mA) and motor idle factor in per cent ;M84 S30 ; set idle timeout ; Axis Limits M208 X0 Y0 Z-130 S1 ; set axis minima M208 X1450 Y1000 Z0 S0 ; set axis maxima, Lengte endstop draad Y = 500 ; Z-Probe 3D touch M558 K0 P5 C"!io7.in" H2 A3 S0.01 T3200 F600:150 ; Probe 0, Mode 5, IO7, Dive height, Probe amount, Travel speed, Feedrate ; Z-Probe toolsetter M558 K1 P8 C"io8.in" H2 A3 S0.01 T3200 F800:400 ; Probe 1, Mode 8, IO7, Dive height, Probe amount, Travel speed, Feedrate ; Spindle M950 R0 C"out1" L3000:24000 Q2000 ; Spindle 0, Pin out1, 24k RPM, 2000Hz PWM ; START MACHINE !!! M453 ; Switches to CNC mode. G54 ; Selects coordinate system 1. ; Miscellaneous M501 ; load saved parameters from non-volatile memory M98 P"mos.g"

    homex.g:

    ; homex.g ; called to home the X axis ; M569 P50.0 D0 ; Make sure we are in open loop mode M569 P51.0 D0 ; Make sure we are in open loop mode G91 ; relative positioning G1 H1 X-1500 F2000 ; move quickly to X axis endstop and stop there (first pass) G1 H2 X5 F3200 ; go back a few mm G1 H1 X-10 F300 ; move slowly to X axis endstop once more (second pass) G92 X0 G90 ; absolute positioning G1 X50 F3000 ; Move to a known-safe position M400 ; Wait for the move to complete G4 P200 ; Wait for the motor to settle M569 P50.0 D5 ; Switch to assisted open loop mode M569.6 P50.0 V1 ; Perform the calibration manoeuvre for a quadrature shaft encoder M569 P51.0 D5 ; Switch to assisted open loop mode M569.6 P51.0 V1 ; Perform the calibration manoeuvre for a quadrature shaft encoder G1 X0 ; Move back to X0

  • Discuss using conditionals, loops and variables in gcode

    801
    Topics
    5.7k
    Posts

    dc42undefined

    @mikeabuilder I think what's leading to the stack overflow is that RRF stacks the current state when it executes M291 and then waits for the M292 acknowledgement. If we have RRF discard any input from the same channel apart from M292 while in this state, that should resolve the stack overflow.

    I created https://github.com/Duet3D/RepRapFirmware/issues/1117.

    dc42 created this issue in Duet3D/RepRapFirmware closed RRF incorrectly executes commands while waiting for blocking user input #1117

  • Ask questions about the official web interface here

    1.6k
    Topics
    13.1k
    Posts

    e_cubed99undefined

    @chrishamm - Thanks for the quick response! Bummer on the anomaly, but the file edit workaround is great for now. Really appreciate the help.

    E^3

  • Feedback for docs.duet3d.com

    117
    Topics
    561
    Posts

    crpalmerundefined

    @Macgyver, I also have a hard time keeping the offset meanings (both probes and tools) correct in my brain. As such, I'm not willing to try to turn the contents of my brain into sentences at the risk of getting it backwards and making it harder for you! That said, I have a macro that probes a fixed point with each of my 2 idex nozzles and updates the tool offset based on the results of probing. Here is the macro on the off chance that it helps you visualize the offsets:

    if ! exists(tools[1]) abort "idex-calibration failed, no second tool" if global.probe_block_middle == null || global.probe_block_diameter == null abort "idex-calibration failed, no probe block defined" T0 M98 P"/sys/wipe-for-probing.g" M98 P"/sys/probe-block.g" var p0 = global.last_probe_result var needs_calibration = true while var.needs_calibration && iterations < 3 T1 M98 P"/sys/wipe-for-probing.g" M98 P"/sys/probe-block.g" var p1 = global.last_probe_result var d_u = var.p0[0] - var.p1[0] var d_y = var.p0[1] - var.p1[1] var d_z = var.p0[2] - var.p1[2] if abs(var.d_u) < 0.1 && abs(var.d_y) < 0.1 set var.needs_calibration = false echo "Current offets:", tools[1].offsets[3], ",", tools[1].offsets[1], ",", tools[1].offsets[2] echo "Correction:", var.d_u, ",", var.d_y, ",", var.d_z G10 P1 U{tools[1].offsets[3] + var.d_u} Y{tools[1].offsets[1] + var.d_y} Z{tools[1].offsets[2] + var.d_z} echo "New offets:", tools[1].offsets[3], ",", tools[1].offsets[1], ",", tools[1].offsets[2]

    FYI, var.p0 is the (x,y,z) position of the fixed point as probed by T0 and var.p1 is the (x,y,z) position of the same fixed point as probed by T1 and it computes the delta between the two points as p0 - p1 and then sets the tool offsets as old_offset + delta

  • We'd love to know what your Duet electronics is controlling! When you have your Duet up and running and controlling a 3D printer or other machine, please tell us about it here.

    Example setups and prints
    806
    Topics
    9.9k
    Posts

    dwuk3dundefined

    @droftarts Cool - looks like that 3 colour printer predates the Prusa MMU1 by quite a lot.

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

    117
    Topics
    795
    Posts

    jay_s_ukundefined

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

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

    DueUI
    180
    Topics
    2.5k
    Posts

    stuartofmtundefined

    @chrishamm
    Thanks. Confirmed working with first=0

  • Accessories and Add-ons

    67
    Topics
    603
    Posts

    Inlinebrotherundefined

    @AlexKid Hi, sorry I missed your messages
    Well, it's great that you are working at it.
    My plans changed, I got a bit tired of tinkering so I bought a p1s)

    But my duet printer is still here and when I finish input shaping setup and cooling duct I might think about ercf. But then I will have another problem that I would need to install a cutter somehow. Though for a dual extruder printer multicolor ability would be great)

  • Forum for discussing the Duet3d Filament Monitor

    398
    Topics
    3.9k
    Posts

    bastundefined

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

    Thank you.

  • Discuss the smart PCB effector for delta printers here.

    412
    Topics
    4.1k
    Posts

    droftartsundefined

    @mickeey

    the smart effector is original duet and the problem is there. the card was on another printer and never had problems

    I think the fan0 connector failed because you wired the fan backwards. If you want to fix it, try replacing the MOSFET. See https://docs.duet3d.com/en/User_manual/Troubleshooting/Parts#fan-mosfet

    I think you should also check the plug on the Smart Effector that connects to the Duet 2 board. These pins look like they are not fully inserted into the housing. There also looks like there might be some wires poking out, that may cause a short.

    9178fd43-e865-41a2-a068-e377984f2959-image.png

    you had region on fan 2 everything works. thanks for all the support

    Great, glad you got it working. Please check the above.

    Ian

  • No decsciption available

    233
    Topics
    1.9k
    Posts

    oliofundefined

    @o_lampe if you just want to know whether the filament is loaded, you can try using stall detection on the extruder for that.

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

    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.

    209
    Topics
    2.2k
    Posts

    Adrian52undefined

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

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

    130
    Topics
    1.3k
    Posts

    MJLewundefined

    @oozeBot Thank you, oozeBot. Yes, my explicit Z values are different to the typical slicer output, but they make it easier for me to see what is going on in the gcode. I treat the whole 'layer' idea a bit more loosely than a slicer would...

  • RepRapFirmware on other controllers

    30
    Topics
    364
    Posts

    CrazyCreatorundefined

    @CrazyCreator
    For anyone who has the same problem after me, here's how to connect or insert the ribbon cable.
    You have to flip the small black bracket upwards, then insert the cable, and then flip the bracket back down. This secures the cable.
    Of course, you should have known beforehand that there is a bracket on these mini jacks.

    IMG_0786.jpeg

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

    dc42undefined

    @MaxGyver thanks for your report. Please do some more tests to make suite sure that the disconnect is reproducible, and that it only occurs when IS is set to 12Hz (or lower if you prefer) and not when it is set to 13Hz. Then start a new thread about this disconnect issue. As @gloomyandy suggested, please include the result of M121 B# where # is the CAN address of the 1XD board.

  • Discuss and contribute to the Duet Software Framework

    132
    Topics
    1.1k
    Posts

    davidjryanundefined

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

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

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

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

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

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

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

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

    406
    Topics
    3.2k
    Posts

    timschneiderundefined

    @yoshimitsuspeed said in [feature] Adaptive / Feedforward Temperature setpoint:

    As I suspected I think the biggest evolution from here would be to use a nominal temp and printing speed in the middle somewhere and then run hotter for faster, cooler for slower.

    first find a S value that fits your setup!

    you can already archive this by tuning the algorithm with the lowest possible temperature for the filament T_nom at nominal speed, e.g. F30 ( the speed you use to calibrate the e-steps). Now go to the upper end, set the hotend temp to the highest possible temperature T_max you want to extrude the filament. Now determine the maximal througput for T_max at speed F_max (use the determind maximum flow rate as flow limit in the slicer). Set the temp in the slicer to T_nom. Determine the T parameter for the temp increase from T_nom to T_max with F_nom to F_max - thats it.

    An Example for PETG
    T_nom: 190 °C
    F_nom: 30 mm/min -> 0.5mm/s
    T_max: 275 °C
    F_max: 960 mm/min (40mm³ for 1.75mm FIlament) -> 16mm/s

    T = (T_max - T_nom) /(F_max-F_nom) = 85°C / 15.5 mm/s = 5.48 °C / mm/s

    e.g. for 24 mm³/s (1.75mm filament) it will correspond to around 245°C which is like common sense for petg.
    Bare in mind that you need to tune Non Linear Extrusion after appling heater feed forward! I disable NLE for heater feedforward tuning, and tune NLE after that.

    for calibration, you always have to move one non extruder axis with the extruder axis e.g.
    G1 E100 F30 for e-step calibration (do not apply NLE / or feed forward)
    G90 G1 X0 F2000 G91 G1 E100 X100 F960 for flowrate at F_max (apply feed forward)

    the lookahead from dc42 will take care of the average and will keep the temp high for normal crusing speeds 🙂

  • Prototype hardware issues.

    50
    Topics
    675
    Posts

    dc42undefined

    @ash100 what is your reason for wanting to reduce microstepping to x8?

  • Suggestions for additional hardware to interface with the DuetWifi. Also suggestions for Changes to the DuetWifi hardware (although the hardware design is pretty fixed now!)

    130
    Topics
    1.3k
    Posts

    T3P3Tonyundefined

    @Aurimas the 1HCLs allow you to use a range of stepper motor + encoders

    Yes you could use servos with integrated drivers and then use a 6XD to drive those 4 motors

  • How would you like us to improve the firmware, and which improvements should we make first? Tell us here.

    948
    Topics
    7.5k
    Posts

    dc42undefined

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

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

    331
    Topics
    2.1k
    Posts

    fcwiltundefined

    @T3P3Tony

    If you go to the General section of the DWC there are a number of options/values that can be set/changed.

    So I was thinking that would be a place to have an "on/off" option that would change the behavior.

    As to M568 - I am using that.

    Here is a the relevant code from one of the filament config files:

    set global.print_beg_tool_temp_a [var.index] = 190 set global.print_beg_tool_temp_s [var.index] = 100 set global.print_beg_tool_ext_adj[var.index] = 100 set global.print_beg_tool_spd_adj[var.index] = 100 set global.print_beg_tool_bby_stp[var.index] = 0 set global.print_beg_tool_prime [var.index] = 10 set global.print_beg_tool_retract[var.index] = 0.5 set global.print_end_tool_retract[var.index] = 0.5 set global.print_beg_bed_temp_a [var.index] = 60 set global.print_beg_bed_temp_s [var.index] = 30

    Later on there is this code in another routine that applies these values:

    ; this part is just to make the use of these values down below a bit easier to read by using shorter names var bed_temp_a = global.print_beg_bed_temp_a [var.tool] var bed_temp_s = global.print_beg_bed_temp_s [var.tool] var tool_temp_a = global.print_beg_tool_temp_a [var.tool] var tool_temp_s = global.print_beg_tool_temp_s [var.tool] var ext_adj = global.print_beg_tool_ext_adj[var.tool] var spd_adj = global.print_beg_tool_spd_adj[var.tool] var bby_stp = global.print_beg_tool_bby_stp[var.tool] M568 P{var.tool} S{var.tool_temp_a} R{var.tool_temp_s} ; set extruder heater temps (active and standby) M221 D{var.tool} S{var.ext_adj} ; set extruder extrusion percentage adjust M140 S{var.bed_temp_a} R{var.bed_temp_s} ; set bed heater temps (active and standby) M220 S{var.spd_adj} ; set print speed adjust M290 R0 S{var.bby_stp} ; set initial baby steps

  • General discussion about 3d printing related subjects that are not duet specific.

    352
    Topics
    3.8k
    Posts

    o_lampeundefined

    This smells like ChatGPT BS.
    OTOH, a bit more autotuning in some areas (pressure advance and input shaping) coming from a local PC or SBC would be nice....

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

    109
    Topics
    968
    Posts

    3DPMicroundefined

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

  • Purchasing

    21
    Topics
    140
    Posts

    Exerqtorundefined

    @T3P3Tony tried to send a chat message, but i don't know if it worked. Never done it on this forum platform before.

  • Help with ordering, announcements etc

    160
    Topics
    948
    Posts

    T3P3Tonyundefined

    @TNO_Marc please email sales@duet3d.com. The online shop accounts are currently for OEMs and Resellers purchasing in volume. We also may be able to assist with a reseller near you.

Unless otherwise noted, all forum content is licensed under CC-BY-SA