Categories

• General Discussion

  Discuss setting up and using the DuetWifi and compatible hardware

  8490
  Topics
  82887
  Posts

  

  @johny said in G32 doesnt save after True Bed Leveling:

  I set the M208 Z-1

  My mistake. I've checked with @dc42, and this isn't necessary. Bed mesh compensation is applied after the limits have been checked, so the nozzle is capable of going below Z0 when bed mesh compensation is enabled.

  Are you sure bed mesh compensation was enabled? Was the first layer exactly as it was before?

  Have you confirmed with a straight edge that your bed is actually the same shape as the mesh is showing? It is still possible this is a measurement error of the Z probe; for example if the weight of the extruder is causing the X axis to deflect, and either bend in the middle or rotate around the X axis. That would also give a bed mesh of this shape, though it would be an extreme example.

  Perhaps you could post a picture of the X axis setup of your printer.

  Another option, though slightly tedious, is to do a manual bed mesh. Set the probe to type 0, and choose a 4x4 bed mesh, then run a new bed mesh (save the old one with a name first, with G29 S3 P"mesh_name.csv"). This will probe the bed, but for each point it will ask you to jog the nozzle down until it touches the bed (or grips a piece of paper). This should help confirm if the bed shape is the same or different from what the Z probe sees. Something like:

  M561 ; clear any bed transform G28 ; home as normal M558 K1 P0 H5 F300 T8000 ; create a new manual probe M557 X25:275 Y90:320 P4 ; define a 4x4 bed mesh G29 K1 S0 ; probe the bed with the manual probe and enable compensation G28 ; home to adjust bed mesh to Z0

  Ian

• Using Duet Controllers
  789
  Topics
  7224
  Posts

  

  @Exerqtor Looks interesting! I've always wanted a plasma CNC...
  This video shows the inside quite well https://youtu.be/qIk-UxMZ0U4?si=gMgWM8EIeHTX0FW0&t=191. I like how both motors are in the base, and it uses a linkage for the distal arm movement. I'm not sure if that makes it a SCARA or some other kinematic; @JoergS5 would know!
  I'd think a Duet and 2x M23CL motors would work well. You would have to ask @dc42 if we could plot the position with the motors.
  There's another thread about building a plasma cutter, and possible problems with EMI: https://forum.duet3d.com/topic/34164/pantograph-help-against-emi-from-plasma-cutter-or-arc-welder
  @o_lampe might be interested in this too.

  Ian

• Duet Hardware and wiring

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

  7905
  Topics
  72666
  Posts

  

  @dc42 Thank you for the heads up. I will continue to post crash logs as I receive them. I suspect mine is related to a hardware issue and static. I was on 3.4.5 and it was crashing with the same type of error.

  Initial testing after moving the chamber thermistor is promising. I was able to do 2 successful prints that were 3 hours long.

  Is there a way to ground the thermistors on the Duet side in order to protect the board? I'd rather wire something in if it all possible to eliminate that as an issue. the hotend thermistor has a metal enclosure and is grounded by the hotend. The other thermistor is bare with just the two leads going to it. I am not sure if it is acting as an antenna for static when it is near parts interacting with filament or what. I am really just shooting in the dark as this point.

• CNC

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

  484
  Topics
  4484
  Posts

  

  @MaxGyver said in CNC Duet3 6XD Omron MX2 VFD forward and reverse:

  Unfortunately I did not find any information concerning the use of the obove discribed 3-wire interface that works with my VFD.

  What do you mean by that?
  It is described in your manual on page 103
  https://www.hitachi-da.com/files/pdfs/produkte/Frequenzumrichter/WJ200/WJ200.pdf

  You need to assign the STA, STP and F/R to three different multifunction inputs of your VFD.

  duet VFD OnOff ---------------- STA |___STP FW/RV ---------------- F/R

  You can read more about it in the Omron MX2 manual on page 203.
  https://assets.omron.eu/downloads/latest/manual/de/i570_mx2_users_manual_de.pdf?v=8

• MultiAxis Printing

  Prototype hardware issues.

  4
  Topics
  402
  Posts

  

  Maybe I reference my hashPrinter here, just in case someone wants to have 4 printheads and needs inspiration...

• Laser Cutters

  Discuss Duet on laser cutters and engravers.

  164
  Topics
  1398
  Posts

  

  @o_lampe Thank you

• Firmware installation

  Ask questions about installing the firmwares here

  1979
  Topics
  22496
  Posts

  

  config.g

  I'm getting extruder 0 reported sensor error.

  Hi again, I installed a tool board and attached filament sensor, and extruder driver to it.

  Not tested filament sensor other than with t with board.

  But I think the error is in the config.

  It will print for a while then pause
  Then fail 2 3 times just after resuming print.

  Also new maybe related it won't load the tools unless I emergency stop on start up

  Tools are one extruder
  And 3 heated beds

  Cheers Darrell

• Tuning and tweaking

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

  5020
  Topics
  53102
  Posts

  

  @droftarts Thanks!

• Gcode meta commands

  Discuss using conditionals, loops and variables in gcode

  642
  Topics
  4765
  Posts

  

  @azs123 You need to call EvaluateExpression in your custom code handler to get the actual value of that parameter if it is an expression. Afair there is another code parameter property to flag this.

• Duet Web Control

  Ask questions about the official web interface here

  1404
  Topics
  12191
  Posts

  

  @Stan said in DWC 3.5.0-rc.1 disconnects after a while:

  Y is 3400mA (dual Y motors)

  If you're using a Duet 2, the motor current is probably just set to max, ie 2.5A.

  Are your motors wired in parallel? I'd guess they are if you have doubled the motor current. However, due to the current limit of the Duet 2 drivers, they are only getting 1.25A each. If they are wired in series, the voltage is doubled rather than the current, which the stepper driver can do itself. You would potentially lose top speed, but the controller would run a lot cooler.

  Ian

• Documentation

  Feedback for docs.duet3d.com

  71
  Topics
  365
  Posts

  

  @Otso @fcwilt @gloomyandy Thanks to this thread, I have updated various parts of the documentation:

  G1 S parameter section is updated to include that max laser power is set by M452.
  G1 S parameter range has been updated, which was 0..254, to 0-255.
  G1 S parameter section now describes 'laser clustering', which was added in RRF 3.5.0-beta3.

  M42 and M106, where the range of values for PWM and fan settings is referred to, is now worded as follows:

  The S field may be in the range 0.0-1.0 or >1.0-255. 0 is off in both cases.

  I investigated M3 and M5 support (M4 has never been supported) in laser mode. M3 and M5 are still supported in laser mode, but in 'non-sticky' mode (M452 S0), they are redundant, as all G1 commands need an S parameter to fire the laser, otherwise it just defaults to S0. In 'sticky' mode (M452 S1), you can set the laser with, for example, M3 S255, then subsequent G1 moves will use that setting without needing an S parameter. M5 effectively sets G1 S0. M3/M5 can't be used to fire the laser on their own; the laser will only fire with a G1 movement command.

  I will update M3, M4, M5, M452 in the Gcode dictionary, and https://docs.duet3d.com/User_manual/Machine_configuration/Configuration_laser, with the above information.

  Ian

• My Duet controlled machine

  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
  756
  Topics
  9281
  Posts

  

  I can see it being a real hard guess 😁
  The dies to form the springs were finish machined on the mill with a .5mm ball endmill, too.
  https://youtu.be/27zb8gcqGPA?si=suV_zfw9h41iTjDT
  I posted this above already but this is what the part was for https://youtu.be/27_E8RawCyQ?si=GDXWU7Ujmx36qK8a

• Config Tool

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

  94
  Topics
  663
  Posts

  

  @developeralgo222

  i tried homing with the above config file and it failed on X-axis & Y-axis with

  G28: failed homing

  and other axes did not home correctly

• Third-party software

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

  DueUI
  156
  Topics
  2314
  Posts

  

  @NeueKlasse Thank you for making this tool. I gave it a try on my windows machine. The splash screen appears plain white for about 1/2 second and I don't see the BMP image. Files are attached. Can you give it a shot and see if it works on your machine?

  I'm loading this to a paneldue 7i. I'm using PanelDueFirmware-3.4.1-7.0i and splash.bmp as the input in the attached zip folder. PanelDueFirmware3.bin is the output.

  @dc42 Can we please add .bmp as a valid file type for attachments in this forum? I see .bmb listed below. Maybe it's a typo. I tried uploading a .bmp file and it gave me the error below.

  [files.zip](Invalid file type. Allowed types are: .png, .jpg, .gif, .bmb, .pdf, .svg, .dxf, .cad, .txt, .doc, .xls, .docx, .xlsx, .stl, .csv, .g, .gcode, .stp, .step, .cps, .cbpp, .odt, .ods, .json, .scad, .heic, .cpp, .c, .h, .py, .fcstd, .elf, .bin, .mp4, .jpeg, .hpp, .webp, .heic, .js, .qoi, .gc, .pcapng, .3mf) splash screen.png PanelDueFirmware3.bin PanelDueFirmware-3.4.1-7.0i.bin

• Accessories and Add-ons
  62
  Topics
  578
  Posts

  

  @Tuma thanks, I'll mark this as solved then.

• Filament Monitor

  Forum for discussing the Duet3d Filament Monitor

  368
  Topics
  3807
  Posts

  

  @Cawfee It depends what version you have. Files for the enclosures are here: https://github.com/Duet3D/FilamentMonitors/tree/master/Filament_Monitor_Magnetic
  Drawings of the hobbed assemblies here: https://docs.duet3d.com/en/Duet3D_hardware/Accessories/Rotating_Magnet_Filament_Monitor#hobbed-assembly
  User @Lo-Fi has also produced some new housings for the older version (v1 and v2) in OnShape, see https://forum.duet3d.com/topic/27780/redesigned-the-mfm-housing/31

  Let me know if you need anything else.

  Ian

• Smart effector for delta printers

  Discuss the smart PCB effector for delta printers here.

  391
  Topics
  3898
  Posts

  

  @Phaedrux
  thanks for the reply

  I am grateful for any suggestion and also from o_lampe.
  i am away in the countryside for the weekend but will check again re the operating system but am pretty sure am running 2.03. I have looked at RRF3.4 and will probably upgrade but know changes to the gcodes need to be done too with this. I have not needed to upgrade with the previous effector version 2.

  My connundrum is that there is also a clear misfit of the heatsink and the effector: the fit is too tight and the effector may be tilted as a result of this, even after tightening (it was very difficult to remove when I diassembled it all). Reaming the hole in the effector would help but I don't want to do this in a new device.
  Hence I have at least one hardware issue, maybe more. The hard probing could be from software too... or other.
  Since I have a work around already, using a previous version 1 smart effector modified to work with an IR probe, the printer is working so I am not desperate, just disappointed.

  I have replied to E3d too about this.
  I will change to RRF 3.4 soon.

• IR Height Sensor

  No decsciption available

  226
  Topics
  1892
  Posts

  

  I'd like to note I already use the IR sensor as a mesh and trigger'd zprobe at print start, but this is using a different set of tech that's collecting a lot more data, but used more coarsely.
  Typically, TOF proximity sensors are for a course near/far detection in robotics, but there's some interesting work in applying these sensors for rapid plane geometry detection.
  https://youtu.be/vJdfpmd6OE0
  I can imagine you could poll a sensor like this across a bed at a distance to calculate a bed mesh at near distances or align it rapidly on print start, without the head needing to move across the surface to probe points.
  b6f1bb67-a66a-4b5a-8976-a31c1b4e0557-image.png

  There was a jetting printer that also collected lidar data every layer to improve quality, and a higher resolution TOF sensor could be used for arbitrary surface capture in QC of bridging or distortions as well.

• PanelDue

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

  649
  Topics
  5163
  Posts

  

  @mfs12
  Just did the first print with a M226 pause on this release, and when i pushed the "Resume" button on PanelDue it registered "Cancel" instead of "Resume" and canceled the print.

  I'm 100% sure i didn't fatfinger the "Cancel" button btw.

  This is on a 5" v3 PD.

• Third-party add-ons

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

  188
  Topics
  2095
  Posts

  

  @Paddy That should be okay. For a list of Duet 2 WiFi/Ethernet pins and functions, see https://docs.duet3d.com/Duet3D_hardware/Duet_2_family/Duet_2_WiFi_Ethernet_Hardware_Overview#inputoutput

  See also this thread where the Orbiter filament sensor is discussed: https://forum.duet3d.com/topic/34132/orbiter-filament-sensor-setup

  Ian

• Plugins for DWC and DSF

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

  97
  Topics
  1109
  Posts

  

  @stuartofmt it should be! @yasas any ideas?

• RepRapFirmware on other controllers
  24
  Topics
  210
  Posts

  

  @dc42 it works know
  6f85142d-73f4-4d61-9d87-2724c2f64ddd-image.png

  Thanks for your support

• STM

  STM based control boards

  37
  Topics
  273
  Posts

  

  @gloomyandy awesome thank you.

• LPC

  LPC based control boards

  17
  Topics
  156
  Posts

  

  @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

  Other control boards that are not specifically LPC or STM based

  40
  Topics
  573
  Posts

  

  @KenW and just to add further, GPIO18 and GPIO19 won't be available to use on the latest revision as they will be used by z scanning probe.
  I'm currently looking to see if anything else can be made available

• Future Direction
  12
  Topics
  164
  Posts
  No new posts.
• Beta Firmware

  Categories for specific issues with Beta and Release Candidate (RC) versions of RRF 2 and RRF 3

  998
  Topics
  12690
  Posts

  

  @chrishamm
  thank you for the fast response - that might be - but i guess it is some kind of a software problem.

  I did a print recovery with M916 (without rebooting the SBC or the duet) to resume the print job and the machine was not able to "connect" the DDA segments. It was moving like 0-jerk, every segment with acceleration, steady and deceleration.
  So I did the following:

  pause print checked jerk, acceleration, input shaping and so on ... reapplied the values increased the movment queue
  and the machine was able to move "normal" again. 5.12.2023, 14:02:17 M595 P120 S150 5.12.2023, 14:01:34 M595 DDAs 60, DMs 125, GracePeriod 10 5.12.2023, 14:01:09 M204 P800 T1250 5.12.2023, 14:01:04 M201 X1500.00 Y1500.00 Z70.00 E3500.00 5.12.2023, 14:00:58 M203 X14400.00 Y14400.00 Z1200.00 E3600.00 5.12.2023, 14:00:50 M593 P"zvddd" F40 5.12.2023, 14:00:44 M566 X600.0 Y600.0 Z12.00 E480.00 P1 5.12.2023, 14:00:12 M593 Input shaping 'zvddd' at 40.0Hz damping factor 0.10, min. acceleration 10.0, impulses 0.112 0.438 0.795 0.968 with durations (ms) 12.56 12.56 12.56 12.56 5.12.2023, 13:59:57 M25 Printing paused at X475.6 Y237.3 Z23.2 5.12.2023, 13:59:51 Resume state saved 5.12.2023, 13:58:03 M204 Maximum printing acceleration 800.0, maximum travel acceleration 1250.0 mm/sec^2 5.12.2023, 13:57:48 M201 Accelerations (mm/sec^2): X: 1500.0, Y: 1500.0, Z: 70.0, E: 3500.0 5.12.2023, 13:55:50 M203 Max speeds (mm/min): X: 14400.0, Y: 14400.0, Z: 1200.0, E: 3600.0, min. speed 30.00 5.12.2023, 13:55:34 M566 Maximum jerk rates (mm/min): X: 600.0, Y: 600.0, Z: 12.0, E: 480.0, jerk policy: 1

  M122 output when the segments where not conencted

  5.12.2023, 13:55:54 M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.5.0-rc.1 (2023-08-31 16:19:24) running on Duet 3 MB6HC v1.02 or later (SBC mode) Board ID: 08DJM-9P63L-DJ3T8-6JKD4-3SJ6K-9A77A Used output buffers: 1 of 40 (18 max) === RTOS === Static ram: 154852 Dynamic ram: 89940 of which 1896 recycled Never used RAM 94864, free system stack 117 words Tasks: SBC(2,ready,0.8%,250) HEAT(3,nWait,0.0%,323) Move(4,nWait,0.0%,214) CanReceiv(6,nWait,0.0%,941) CanSender(5,nWait,0.0%,335) CanClock(7,delaying,0.0%,343) TMC(4,nWait,8.6%,61) MAIN(2,running,90.5%,137) IDLE(0,ready,0.0%,30), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 26:21:04 ago, cause: power up Last software reset at 2023-11-30 10:06, reason: User, Platform spinning, available RAM 96472, slot 2 Software reset code 0x6000 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a Error status: 0x00 MCU temperature: min 33.9, current 34.3, max 35.0 Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 11.7, current 12.3, max 12.8, under voltage events: 0 Heap OK, handles allocated/used 99/9, heap memory allocated/used/recyclable 2048/416/240, gc cycles 386 Events: 413 queued, 413 completed Driver 0: ok, SG min 35, mspos 936, reads 11744, writes 2 timeouts 0 Driver 1: ok, SG min 29, mspos 56, reads 11744, writes 2 timeouts 0 Driver 2: standstill, SG min 0, mspos 8, reads 11736, writes 10 timeouts 0 Driver 3: standstill, SG min 0, mspos 504, reads 11736, writes 10 timeouts 0 Driver 4: standstill, SG min 0, mspos 344, reads 11736, writes 10 timeouts 0 Driver 5: ok, SG min 0, mspos 884, reads 11739, writes 8 timeouts 0 Date/time: 2023-12-05 13:55:53 Slowest loop: 490.41ms; fastest: 0.05ms === 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 66, maxWait 2176309ms, bed compensation in use: mesh, height map offset 0.000, ebfmin -0.90, ebfmax 1.00 next step interrupt due in 69 ticks, disabled Moves shaped first try 22, on retry 1, too short 607, wrong shape 5, maybepossible 0 === DDARing 0 === Scheduled moves 680, completed 679, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 4], CDDA state 3 === DDARing 1 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.8 Heater 1 is on, I-accum = 0.3 === GCodes === Movement locks held by File2, null HTTP* is doing "M122" in state(s) 0 Telnet is idle in state(s) 0 File* is doing "G1 X464.493988 Y230.830002 E0.026320" 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 0, running macro Aux2 is idle in state(s) 0 Autopause* is idle in state(s) 0 File2* is doing "M116" in state(s) 0 0, running macro Queue2 is idle in state(s) 0 Q0 segments left 0, axes/extruders owned 0x80000003 Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === Filament sensors === Extruder 0: pos 174.02, errs: frame 143 parity 0 ovrun 0 pol 0 ovdue 0 === CAN === Messages queued 19971, received 0, lost 0, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 11095/0/0 Tx timeouts 0,0,11095,0,0,8876 last cancelled message type 4514 dest 127 === SBC interface === Transfer state: 5, failed transfers: 0, checksum errors: 3 RX/TX seq numbers: 21216/35495 SPI underruns 3, overruns 3 State: 5, disconnects: 1, timeouts: 1 total, 1 by SBC, IAP RAM available 0x25a98 Buffer RX/TX: 2824/400-4080, open files: 0 === Duet Control Server === Duet Control Server version 3.5.0-rc.1 (2023-09-01 07:22:07) File /opt/dsf/sd/gcodes/UCB___-000001_MUSTER-A TEST_31percent_infill_1_0mm_flat_0.25mm_PA_MBL480_1d9h1m.gcode is selected, processing Failed to deserialize the following properties: - MoveSegmentation -> Int32 from 2.0 File: Buffered code: G1 X464.494 Y230.83 E0.02632 Buffered code: G1 X464.708 Y231.006 E0.01245 Buffered code: G1 X464.98 Y231.228 E0.01577 Buffered code: G1 X465.296 Y231.459 E0.01758 Buffered code: G1 X465.539 Y231.621 E0.01313 Buffered code: G1 X465.859 Y231.826 E0.01706 Buffered code: G1 X466.096 Y231.958 E0.01218 Buffered code: G1 X466.505 Y232.18 E0.0209 Buffered code: G1 X466.979 Y232.392 E0.02334 Buffered code: G1 X467.1 Y232.719 E0.01567 Buffered code: G1 X467.404 Y233.38 E0.03268 Buffered code: G1 X467.76 Y234.015 E0.03268 Buffered code: G1 X468.164 Y234.619 E0.03268 Buffered code: G1 X468.615 Y235.191 E0.03268 Buffered code: G1 X469.109 Y235.724 E0.03267 Buffered code: G1 X469.643 Y236.218 E0.03268 Buffered code: G1 X470.214 Y236.668 E0.03267 Buffered code: G1 X470.819 Y237.072 E0.03267 Buffered code: G1 X471.454 Y237.427 E0.03267 Buffered code: G1 X472.114 Y237.731 E0.03267 Buffered code: G1 X472.796 Y237.983 E0.03267 Buffered code: G1 X473.496 Y238.18 E0.03267 Buffered code: G1 X474.209 Y238.322 E0.03266 Buffered code: G1 X474.931 Y238.407 E0.03267 Buffered code: G1 X475.536 Y238.431 E0.02716 Buffered code: G1 X487.005 Y238.431 E0.51523 Buffered code: G1 X487.246 Y238.792 E0.01949 Buffered code: G1 X487.46 Y239.081 E0.01616 Buffered code: G1 X487.708 Y239.395 E0.01798 Buffered code: G1 X487.842 Y239.54 E0.00884 Buffered code: G1 X488.263 Y240.029 E0.02902 Buffered code: G1 X488.758 Y240.453 E0.02927 Buffered codes: 1536 bytes total Daemon: >> Doing macro daemon.g, started by system File2: Buffered code: M116 ; wait for all heaters Buffered codes: 24 bytes total > Suspended code: M107 > Suspended code: G21 ; set units to millimeters > Suspended code: G90 ; use absolute coordinates > Suspended code: M83 ; use relative distances for extrusion > Suspended code: ;LAYER_CHANGE > Suspended code: ;HEIGHT:0.5 > Suspended code: ; custom gcode: before_layer_gcode > Suspended code: ;BEFORE_LAYER_CHANGE > Suspended code: ; custom gcode end: before_layer_gcode > Suspended code: G10 ; retract > Suspended code: G1 Z0.5 F21000 > Suspended code: ; custom gcode: layer_gcode > Suspended code: ;AFTER_LAYER_CHANGE > Suspended code: ; custom gcode end: layer_gcode > Suspended code: G92 E0 > Suspended code: G1 X250.964 Y86.801 > Suspended code: G11 ; unretract >> Doing macro 0:/sys/meltingplot/print_start, started by M98 P"0:/sys/meltingplot/print_start" >> Number of flush requests: 1 Code buffer space: 2424 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0 Full transfers per second: 39.19, max time between full transfers: 44.6ms, max pin wait times: 34.7ms/3.6ms Codes per second: 1.44 Maximum length of RX/TX data transfers: 4712/3328

  M122 after reapplying the values

  5.12.2023, 14:10:43 M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.5.0-rc.1 (2023-08-31 16:19:24) running on Duet 3 MB6HC v1.02 or later (SBC mode) Board ID: 08DJM-9P63L-DJ3T8-6JKD4-3SJ6K-9A77A Used output buffers: 1 of 40 (18 max) === RTOS === Static ram: 154852 Dynamic ram: 89940 of which 1896 recycled Never used RAM 63864, free system stack 117 words Tasks: SBC(2,ready,0.9%,250) HEAT(3,nWait,0.0%,323) Move(4,nWait,1.7%,214) CanReceiv(6,nWait,0.0%,941) CanSender(5,nWait,0.0%,335) CanClock(7,delaying,0.0%,343) TMC(4,nWait,9.0%,61) MAIN(2,running,88.3%,137) IDLE(0,ready,0.0%,30), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 26:35:52 ago, cause: power up Last software reset at 2023-11-30 10:06, reason: User, Platform spinning, available RAM 96472, slot 2 Software reset code 0x6000 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a Error status: 0x00 MCU temperature: min 34.1, current 34.4, max 34.7 Supply voltage: min 23.9, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 11.8, current 12.2, max 12.7, under voltage events: 0 Heap OK, handles allocated/used 99/9, heap memory allocated/used/recyclable 2048/696/520, gc cycles 389 Events: 413 queued, 413 completed Driver 0: ok, SG min 14, mspos 789, reads 31259, writes 0 timeouts 0 Driver 1: ok, SG min 25, mspos 879, reads 31259, writes 0 timeouts 0 Driver 2: standstill, SG min 0, mspos 8, reads 31259, writes 0 timeouts 0 Driver 3: standstill, SG min 0, mspos 504, reads 31259, writes 0 timeouts 0 Driver 4: standstill, SG min 0, mspos 344, reads 31259, writes 0 timeouts 0 Driver 5: ok, SG min 0, mspos 932, reads 31254, writes 4 timeouts 0 Date/time: 2023-12-05 14:10:42 Slowest loop: 42.73ms; fastest: 0.05ms === 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 150, segments created 66, maxWait 155087ms, bed compensation in use: mesh, height map offset 0.000, ebfmin -1.00, ebfmax 1.00 next step interrupt due in 25 ticks, disabled Moves shaped first try 357, on retry 34, too short 2673, wrong shape 12949, maybepossible 256 === DDARing 0 === Scheduled moves 26971, completed 26851, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3 === DDARing 1 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.0 Heater 1 is on, I-accum = 0.3 === GCodes === Movement locks held by null, null HTTP* is doing "M122" in state(s) 0 Telnet is idle in state(s) 0 File* is doing "G1 X502.369995 Y308.734009 E0.013370" 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 1, axes/extruders owned 0x80000007 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === Filament sensors === Extruder 0: pos 203.55, errs: frame 143 parity 0 ovrun 0 pol 0 ovdue 0 === CAN === Messages queued 7995, received 0, lost 0, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 4442/0/0 Tx timeouts 0,0,4442,0,0,3553 last cancelled message type 30 dest 127 === SBC interface === Transfer state: 5, failed transfers: 0, checksum errors: 3 RX/TX seq numbers: 57385/6128 SPI underruns 3, overruns 3 State: 5, disconnects: 1, timeouts: 1 total, 1 by SBC, IAP RAM available 0x25a98 Buffer RX/TX: 3888/984-4080, open files: 0 === Duet Control Server === Duet Control Server version 3.5.0-rc.1 (2023-09-01 07:22:07) File /opt/dsf/sd/gcodes/UCB___-000001_MUSTER-A TEST_31percent_infill_1_0mm_flat_0.25mm_PA_MBL480_1d9h1m.gcode is selected, processing Failed to deserialize the following properties: - MoveSegmentation -> Int32 from 2.0 File: Buffered code: G1 X502.338 Y308.436 E0.01345 Buffered code: G1 X502.26 Y308.139 E0.01382 Buffered code: G1 X502.122 Y307.841 E0.01474 Buffered code: G1 X501.909 Y307.544 E0.01641 Buffered code: G1 X501.622 Y307.246 E0.01858 Buffered code: G1 X500.942 Y306.651 E0.0406 Buffered code: G1 X500.633 Y306.353 E0.01929 Buffered code: G1 X500.373 Y306.056 E0.01774 Buffered code: G1 X500.164 Y305.758 E0.01632 Buffered code: G1 X500.001 Y305.461 E0.01526 Buffered code: G1 X499.782 Y304.866 E0.02848 Buffered code: G1 X499.684 Y304.27 E0.0271 Buffered code: G1 X499.679 Y303.973 E0.01337 Buffered code: G1 X499.711 Y303.675 E0.01345 Buffered code: G1 X499.79 Y303.378 E0.01382 Buffered code: G1 X499.928 Y303.08 E0.01474 Buffered code: G1 X500.14 Y302.783 E0.01641 Buffered code: G1 X500.427 Y302.485 E0.01858 Buffered code: G1 X501.107 Y301.89 E0.0406 Buffered code: G1 X501.417 Y301.592 E0.01929 Buffered code: G1 X501.676 Y301.295 E0.01774 Buffered code: G1 X501.885 Y300.997 E0.01632 Buffered code: G1 X502.048 Y300.699 E0.01526 Buffered code: G1 X502.267 Y300.104 E0.02848 Buffered code: G1 X502.366 Y299.509 E0.0271 Buffered code: G1 X502.37 Y299.212 E0.01337 Buffered code: G1 X502.338 Y298.914 E0.01345 Buffered code: G1 X502.26 Y298.616 E0.01382 Buffered code: G1 X502.122 Y298.319 E0.01474 Buffered code: G1 X501.909 Y298.021 E0.01641 Buffered code: G1 X501.622 Y297.724 E0.01858 Buffered codes: 1488 bytes total File2: >> Finishing macro 0:/sys/meltingplot/print_start, started by M98 P"0:/sys/meltingplot/print_start" Code buffer space: 2616 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0 Full transfers per second: 40.72, max time between full transfers: 41.7ms, max pin wait times: 34.2ms/2.4ms Codes per second: 30.48 Maximum length of RX/TX data transfers: 4712/3328
• DSF Development

  Discuss and contribute to the Duet Software Framework

  90
  Topics
  832
  Posts

  

  @chrishamm @Falcounet Will OP's original ask be implemented in DSF-Python? We are not only interested in updated global variables directly, but other values within the ObjectModel as well. While a bit dangerous, allowing a way to directly interact with the ObjectModel could be extremely powerful.

• Firmware developers

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

  374
  Topics
  3001
  Posts

  

  @Mohammad I suspect that the version of "make" you are using can't handle the very long command lines generated by Eclipse. Please use the MSYS2 version of make instead. If it's not installed already, use pacman (which is part of MSYS2) to install it.

• Hardware dev

  Prototype hardware issues.

  43
  Topics
  585
  Posts

  

  @VoodooBane I don't know, I haven't seen them online for quite some time. It's pretty simple, however, to update and compile the firmware. To be honest it's been a hot minute since I touched it last.

  I was looking around for someone else and either I sold them all or completely lost them in my shop 😄

  I am considering a new order of them, if I get enough interest it would push my decision up a notch.

• Hardware wishlist

  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!)

  125
  Topics
  1240
  Posts

  

  @T3P3Tony Did you guys discuss this any further? Is it feasible to have this option for 1LC boards, perhaps as an alternative version? (something like 1LC-NEMA17?)

• Firmware wishlist

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

  902
  Topics
  7115
  Posts

  

  I put my g-code resolution back to the default value and it started generating arcs. It only does it on external perimeters though. So artifacts from linear segmented inner walls can still print through.

  But again, for the sake of our discussion, until RRF allows true arc support, the quality with G2/G3 is worse than without.

• Duet Web Control wishlist

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

  318
  Topics
  2078
  Posts

  

  We agree the tool panel can get unwieldy.. To combat this, here is what our custom DWC has whittled it down to. Note we removed the label for each heater as it's redundant for our usage. For posterity - most of the padding is coming from the dropdowns - setting the "dense" flag in the v-combobox removes it.

  bbdcae10-a63e-4492-aa02-19127cd3b9ff-image.png

• 3D Printing General Chat

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

  331
  Topics
  3631
  Posts

  

  @Sullivan this forum is for users of Duet3D electronics, using RepRapFirmware. You would be better served posting on the Arduino forums.

  Ian

• Off Topic

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

  94
  Topics
  1010
  Posts

  

  @droftarts Thanks!

• Purchasing
  21
  Topics
  140
  Posts

  

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

• Order discussion

  Help with ordering, announcements etc

  154
  Topics
  927
  Posts

  

  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.