Categories

• Using Duet Controllers
  699
  Topics
  6435
  Posts

  

  @axiom Moin axiom,

  As „Start G-Code“, this here should be sufficient:

  G28 ; Home M83 ; set extruder to relative mode G92 E0 ; reset extruder’s relative position to 0

  Most other instructions to prepare the printer for a job should better be written into the start.g macro on SD card.

  I don’t quite understand this here:

  However, the start position in the control panel changes.

  With „control panel“, do you mean DWC, PanelDue or something else?

  Generally, it’s quite simple. In your Druckeinstellungen, you told Cura about the size of your printer and the origin of the coordinate system: „Ausgang in Mitte“ (BTW: strange translation of ‚center origin‘) is deselected, so the origin should be front left. At least, that’s what Cura assumes.

  Now, depending on where you place your print object in Cura, this should correspond to its placement on your print bed … as far as you defined the printer’s X/Y origin to be at the front left. If the position doesn’t match, there’s something wrong with either the size values in the Druckereinstellungen of Cura or with the axes-settings of your printer.

• General Discussion

  Discuss setting up and using the DuetWifi and compatible hardware

  7630
  Topics
  75734
  Posts

  

  @Phaedrux
  Thank you very much for the response.
  I think you may be onto something.

  The router type is an ASUS RT-AC88U, and there is a way to disable the maybe not so "Smart Connect" feature. This allows for only the 2.4 or 5 Ghz band. I set it to 2.4, and all three printers connected in short order. Gonna call it quits for tonight, but I will have to do some reset testing very soon here.

  Hopefully, I can call this solved!

  In case anyone wants to know the config...

  ; Network M552 S1 P"mySSID" ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet
• Duet Hardware and wiring

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

  7158
  Topics
  67084
  Posts

  

  this?

  https://us.store.bambulab.com/products/hotend-cooling-fan

  $30 is cheap?

  Anyway.. you need the pinout of the fan, this could be ascertained from someone that has a Bambu printer and measures the pins on the fan header for you.

• CNC

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

  393
  Topics
  3794
  Posts

  

  @o_lampe thanks for the assistance. I tried all combinations of adding pull up resistor and inverting the signal and found no change. I will need to double check wiring, continuity, polarity etc and find out how to test devices such as the PWM converter, as I don't have an oscilloscope. Diving further down the rabbit hole!!!

• Laser Cutters

  Discuss Duet on laser cutters and engravers.

  142
  Topics
  1217
  Posts

  

  What is your M670 command?

• Firmware installation

  Ask questions about installing the firmwares here

  1826
  Topics
  21124
  Posts

  

  @NO1NOKAO I don't think your current setting for Z is correct, you have:

  M913 Z50:50 ; drop motor current to 50%

  But from the docs for M913: https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m913-set-motor-percentage-of-normal-current
  "Example: If you have two motors on your Z axis, physically connected to Z and E0 stepper drivers, configured with M584 Z2:3, set M913 Z50, not M913 Z50:50"

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

  4648
  Topics
  50002
  Posts

  

  @smuellerch acceleration is also limited by M204, so check what M204 values are set. The default is 100000 AFAIR.

• Gcode meta commands

  Discuss using conditionals, loops and variables in gcode

  510
  Topics
  3948
  Posts

  

  @ApTix Thanks for reporting this, it will be fixed in the next version.

• Duet Web Control

  Ask questions about the official web interface here

  1232
  Topics
  10856
  Posts

  

  @Phaedrux, which Duet board do you run and do you run tool boards or is everything connected to the main board?

• Documentation

  Feedback for docs.duet3d.com

  39
  Topics
  181
  Posts

  

  @Steppenleguan said in Independent dual z axis with endstops - z homing not working:

  @knuxvomica no they don´t.
  Current state: G28 homing failed , and nothing happens
  Before with a homez.g: The axis lifts 5mm, moves down then passes! the endstops and hits my frame when I don´t emergency stop...

  As you can see I am using the M564 command to test the axis movements in advance (which works fine) but obviously I don´t have any homing , i.e. no printing possible

  M564 H0 ;move without homing

  @Phaedrux said in Independent dual z axis with endstops - z homing not working:

  Please post your full config.g
  Homing Z should be as simple as a G1 H1 Z move to move the z axis such that the endstops are hit.

  You need G1 H1 Z-700 at the end of your homeall.g to home the Z axis. The same would be needed in homez.g

• 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
  727
  Topics
  8918
  Posts

  

  This is my modified FLSUN Q5.
  It features a Slice Engineering Mosquito hotend and a Duet 2 Wifi.
  Firmware 3.4.4

  For the setup to work I needed to design and print new cooling ducts, new bed level extension and part cooling fan holder. The holder includes an extra piece to keep the bowden tube aligned as it goes into the hot end. The mosquito is using a machined adapter from 713Maker.

  Video:
  https://youtu.be/rswph5SLrJk

  As of right now I have no intentions of using mag balls or a smart effector on this machine. Perhaps in the future.

  NOTE: This machine used to run Klipper with the old board. But that old board, well, lets just say I ran it too hard, too fast, for too long. Hence the need for a new board.

• Config Tool

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

  74
  Topics
  500
  Posts

  

  @fotomas I think it's to do with the Z endstop. For some reason can't select 'Switch'.
  Edit: ... and the I/O mapping page isn't showing up correctly. I think there's an incompatibility in the Fisher config template.

  Ian

• Third-party software

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

  DueUI
  121
  Topics
  1955
  Posts

  

  @dc42 Thanks! I try this:
  ...add command G1 R2 X0 Y0 Z2 Fxxx followed by G1 R2 Z0 Fxxx to the end of your tpost#.g files...
  Looks like it works. Maybe better if the last leg before the new-tool-print-start could travel i mm higher, now it is scratching the print a little. I'm using the rapid change hotends an they can bend easily when touching the print.
  Here I want to ask how to set standby temperatures to tools. I did not find such a feature in Prusa.
  And how to tell the machine to put back the last tool after finishing the job.

• Accessories and Add-ons
  57
  Topics
  550
  Posts

  

  @Exerqtor OK, so nothing fancy about. BTW: for a similar arrangement (but with separate sensor tip), I use an 'even more ordinary' photo-electric barrier, I.e. without amplifier. Works great. Using the whole nozzle assembly as a sensor induces mechanical tolerances I would better like to avoid during print - just my opinion …

• PanelDue

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

  590
  Topics
  4643
  Posts

  

  @oozeBot said in PanelDue IP address display issue (3.3/3.4-pre1):

  @mfs12 @mfs12 @T3P3Tony

  This is surprising now that the PanelDue has been updated to work with the ObjectModel, but you are right.. after some testing, my assumption of what is passed to the PanelDue was incorrect.

  We recently made the decision to build our own version of the PanelDue firmware (that we will keep in parity with the latest official releases). One of the changes was to add in the Global object. So to "fix" the issue, we added a global variable that contains the SBC's IP and are populating the field on the PanelDue with it.. It's not elegant, but it works.

  Where can I find your PanelDue firmware?

• IR Height Sensor

  No decsciption available

  213
  Topics
  1816
  Posts

  

  @jay_s_uk That servo arm is as cute as a button, I like it.

• Smart effector for delta printers

  Discuss the smart PCB effector for delta printers here.

  364
  Topics
  3601
  Posts

  

  @weed2all Yeah, that works for vibration. But when unscrewing nozzle it does not hold.

• Filament Monitor

  Forum for discussing the Duet3d Filament Monitor

  331
  Topics
  3518
  Posts

  

  First off thanks for the great forum I have lurked for ages found 99% of answers I need with out posting

  I am currently using a duet2 wifi with a duex 5 running 3.4.4 firmware
  and everything has just worked for the most part

  I have built this sensor
  https://www.thingiverse.com/thing:3785514 with a 32 tooth encoder wheel
  chosen because I had all the parts on hand. and it is attached to my corexy (sel fsourced railcore) by reverse bowden I would rather not add the sensor to my carriage

  here is my most recent attempt to calibrate it

  2022-11-24, 7:07:42 p.m. M591 D0 Pulse-type filament monitor on pin zstop, disabled, sensitivity 0.250mm/pulse, allowed movement 50% to 200%, check every 5.0mm, measured sensitivity 0.050mm/pulse, measured minimum 27%, maximum 22844% over 5656.8mm 2022-11-24, 7:00:26 p.m. M591 D0 Pulse-type filament monitor on pin zstop, disabled, sensitivity 0.250mm/pulse, allowed movement 50% to 200%, check every 5.0mm, measured sensitivity 0.100mm/pulse, measured minimum 27%, maximum 21655% over 4539.8mm 2022-11-24, 6:59:57 p.m. M591 D0 Pulse-type filament monitor on pin zstop, disabled, sensitivity 0.250mm/pulse, allowed movement 50% to 200%, check every 5.0mm, measured sensitivity 0.108mm/pulse, measured minimum 27%, maximum 21655% over 4465.2mm 2022-11-24, 6:55:37 p.m. M591 D0 Pulse-type filament monitor on pin zstop, disabled, sensitivity 0.250mm/pulse, allowed movement 50% to 200%, check every 5.0mm, measured sensitivity 0.185mm/pulse, measured minimum 27%, maximum 21655% over 4042.0mm 2022-11-24, 6:55:28 p.m. M591 D0 Pulse-type filament monitor on pin zstop, disabled, sensitivity 0.250mm/pulse, allowed movement 50% to 200%, check every 5.0mm, measured sensitivity 0.184mm/pulse, measured minimum 27%, maximum 21655% over 4010.4mm 2022-11-24, 6:55:21 p.m. M591 D0 2022-11-24, 6:45:01 p.m. M591 D0 Pulse-type filament monitor on pin zstop, disabled, sensitivity 0.250mm/pulse, allowed movement 50% to 200%, check every 5.0mm, measured sensitivity 0.241mm/pulse, measured minimum 27%, maximum 2257% over 2132.1mm 2022-11-24, 6:40:29 p.m. M591 D0 Pulse-type filament monitor on pin zstop, disabled, sensitivity 0.250mm/pulse, allowed movement 50% to 200%, check every 5.0mm, measured sensitivity 0.216mm/pulse, measured minimum 27%, maximum 2257% over 1199.8mm 2022-11-24, 6:40:21 p.m. M591 D0 Pulse-type filament monitor on pin zstop, disabled, sensitivity 0.250mm/pulse, allowed movement 50% to 200%, check every 5.0mm, measured sensitivity 0.213mm/pulse, measured minimum 27%, maximum 2257% over 1173.6mm 2022-11-24, 6:36:06 p.m. M591 D0 Pulse-type filament monitor on pin zstop, disabled, sensitivity 0.250mm/pulse, allowed movement 50% to 200%, check every 5.0mm, measured sensitivity 0.237mm/pulse, measured minimum 27%, maximum 2257% over 307.7mm 2022-11-24, 6:35:41 p.m. M591 D0 Pulse-type filament monitor on pin zstop, disabled, sensitivity 0.250mm/pulse, allowed movement 50% to 200%, check every 5.0mm, measured sensitivity 0.182mm/pulse, measured minimum 27%, maximum 2257% over 212.8mm 2022-11-24, 6:35:11 p.m. M591 D0 Pulse-type filament monitor on pin zstop, disabled, sensitivity 0.250mm/pulse, allowed movement 50% to 200%, check every 5.0mm, measured sensitivity 0.739mm/pulse, measured minimum 28%, maximum 51% over 122.6mm 2022-11-24, 6:34:51 p.m. M591 D0 Pulse-type filament monitor on pin zstop, disabled, sensitivity 0.250mm/pulse, allowed movement 50% to 200%, check every 5.0mm, measured sensitivity 0.743mm/pulse, measured minimum 32%, maximum 37% over 48.3mm 2022-11-24, 6:34:37 p.m. M591 D0 P7 C"zstop" S0 R50:200 L0.25 E5 ;rotary optical sensor

  M122

  m122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.4 (2022-10-20 16:17:41) running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DLM-996AL-K65SN-6J9FD-3SN6P-TA16X Used output buffers: 1 of 26 (26 max) === RTOS === Static ram: 23860 Dynamic ram: 76488 of which 40 recycled Never used RAM 8092, free system stack 92 words Tasks: NETWORK(notifyWait,30.8%,211) HEAT(notifyWait,0.1%,303) Move(notifyWait,6.9%,268) DUEX(notifyWait,0.0%,24) MAIN(running,61.8%,421) IDLE(ready,0.3%,30), total 100.0% Owned mutexes: === Platform === Last reset 49:07:06 ago, cause: software Last software reset at 2022-11-22 17:45, reason: User, GCodes spinning, available RAM 9752, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x14 Step timer max interval 0 MCU temperature: min 18.5, current 20.9, max 22.1 Supply voltage: min 0.0, current 0.0, max 12.5, under voltage events: 4, over voltage events: 0, power good: no Heap OK, handles allocated/used 99/4, heap memory allocated/used/recyclable 2048/654/590, gc cycles 0 Events: 5 queued, 5 completed Driver 0: standstill, SG min 0 Driver 1: standstill, SG min 0 Driver 2: standstill, SG min n/a Driver 3: standstill, SG min 0 Driver 4: standstill, SG min n/a Driver 5: standstill, SG min n/a Driver 6: standstill, SG min n/a Driver 7: standstill, SG min n/a Driver 8: standstill, SG min n/a Driver 9: standstill, SG min n/a Driver 10: Driver 11: Date/time: 2022-11-24 20:44:06 Cache data hit count 4294967295 Slowest loop: 159.28ms; fastest: 0.13ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 13.5ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 31, maxWait 1539ms, bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves 95975, completed 95975, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === 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, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.1 Heater 1 is on, I-accum = 0.7 === GCodes === Segments left: 0 Movement lock held by null HTTP is idle 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === Filament sensors === Extruder 0 sensor: ok === DueX === Read count 0, 0.00 reads/min === Network === Slowest loop: 99.82ms; fastest: 0.07ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 = WiFi = Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 49 WiFi firmware version 1.27 WiFi MAC address cc:50:e3:76:3f:a6 WiFi Vcc 3.43, reset reason Software restart WiFi flash size 4194304, free heap 24320 WiFi IP address 10.0.1.27 WiFi signal strength -55dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0

  by my math which is probably wrong it should be about 1.2 mm per tooth on the encoder
  the designer had his set for around 0.83 mm per pulse

  at least this time around the Minimum value seems to be constant now but it is way out there on the max
  and the Measured sensitivity is pretty erratic as well

  this during a PLA print with relatively few retractions and only 0.6mm of retraction

  so any help would greatly be appreciated

• Third-party add-ons

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

  155
  Topics
  1838
  Posts

  

  Looking at the linked documentation from Orbiter it looks like you have things in place. Have you contacted them to see if they have seen this before?

  Can you also send M98 P"config.g" and see if it throws any errors?

• Plugins for DWC and DSF

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

  60
  Topics
  787
  Posts

  

  @falco22 I think, you don't understand correctly what @MintyTrebor means...
  He means, that the job panel in DWC, where you start the job, is not under his control.
  After starting a job it is standard for DWC to jump to status screen. MintyTrebor can only change the BtnCmd plugin.

• RepRapFirmware on other controllers
  20
  Topics
  180
  Posts

  

  If your windows / arduino can generate HTTP you can use https://github.com/Duet3D/RepRapFirmware/wiki/HTTP-requests. This is quite a straightforward interface, e.g. a GET of http://11.22.33.44/rr_gcode?gcode=G28 will execute G28 (ie home all) on the duet machine at 11.22.33.44. It has file operations (upload, download, list, delete etc.), execute arbitarray gcode, and let you get any part of the object model (which lets you check almost every element of the state or status of the machine).

  If you install curl you can do this from pretty much any scripting language (even .bat files).

  If you have a Pi connected to the duet device there's also the DSF: https://github.com/Duet3D/DuetSoftwareFramework This will let you do anything the duet can do, but requires more detailed and particular programming knowledge.

• STM

  STM based control boards

  28
  Topics
  216
  Posts

  

  @jay_s_uk
  overkill of course but i dont use it here at the moment because i dont use this printer

• 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

  35
  Topics
  487
  Posts

  

  @reflexlab it depends on your board:

  If the board uses plug-in drivers then you can usually unplug the driver and connect an external driver to the step, direction and either 5V or ground pins of the driver socket. If it doesn't use plug-in drivers, and doesn't provide access to the step and direction outputs, then you would need a specialise driver that decodes the phase outputs of on-board driver to extract step and direction information from them. I have never come across such a driver, however in this thread https://forum.duet3d.com/topic/28887/weird-signal-from-duet-to-motor it became apparent that the person posting has such a driver.

  The Duet3D MB6HC main board and the EXP3HC and EXP1HCL expansion boards can drive some types of Nema 34 motor directly at up to 6A peak current.

• 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

  792
  Topics
  10544
  Posts

  

  @chrishamm
  Thanks. I'll mark this as solved.

• DSF Development

  Discuss and contribute to the Duet Software Framework

  71
  Topics
  683
  Posts

  

  @dc42 I have too weak power supply so I have to heat chamber only if bed is not heated. Earlier I did it in firmware but it will be nice to do it in Python script.

• Firmware developers

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

  331
  Topics
  3033
  Posts

  

  @dc42 “you could either detect USB disconnection/reconnection in your C# program…” Yes, I was asking how to do that. It is possible but not trivial to get notification for this on a particular device. Further, it needs deeper knowledge of the actual driver providing the serial interface to the application, which I don’t have. So I asked if anyone might have this.
  But my approach was wrong. I don’t have that info, but I don’t need it either: The right way to do it is to hook to the general device event and know that some device dis-/reconnected. That is enough, I can then look at the uptime or a variable to find out if it was the Duet.

• Hardware dev

  Prototype hardware issues.

  35
  Topics
  502
  Posts

  

  @arnold_r_clark I just posted about this:

  https://forum.duet3d.com/topic/28702/toolboard-v1-3-compatible-with-the-hemera-xs

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

  116
  Topics
  1167
  Posts

  

  Hello,

  The 1XD board is a great step towards proper servo drives for CNC usage. With a proper AC servo which has closed loop control between the motor and the driver, end-to-end closed loop control isn't really needed especially if the error/fault output of the servo drive is used. There is however a second use for encoder inputs - Homing.

  Proper servo drives often have buffered encoder outputs, which are the full complement of encoder signals including the index. If a "course" homing switch is included on the axis to get within one motor revolution of the final home location, the final homing can be completed using the encoder by allowing it to continue rotating in a given direction until the index signal is raised. This is far more repeatable than a homing switch (Subject to backlash) and operates with the same resolution of the servo motor.

  Obviously this also puts in the ground-work for end-to-end closed loop control with external drivers if that's implemented.

  So my proposal is to build another version of the 1XD with some more I/O:

  3x differential driver outputs: Step/Direction/Enable [As it currently has] 1x high-current brake output [As it currently has] 3x differential encoder inputs: A/B/I 1x differential error/fault input 2x single-ended endstop inputs (Can be GPIO) [As it currently has]

  See page #57 for an example encoder output from a servo drive:
  https://www.applied-motion.com/sites/default/files/hardware-manuals/SV200_AC_Hardware_Manual_920-0096H.pdf

  The other option of course is something like EtherCat, but that's a whole separate topic.

  Thanks,
  -Andrew.

• Firmware wishlist

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

  797
  Topics
  6392
  Posts

  

  I was wondering if there is a reason why we don't have an option to add a change.g file next to the load.g and unload.g in the filaments menu.

  This way we could make a custom macro for the change.g file without having to add blocking messages to the load and unload macros.

  Unless I missed something and it's already possible to do so?

• Duet Web Control wishlist

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

  298
  Topics
  2009
  Posts

  

  @chrishamm ok, thanks, so I will stay at the current solutions for the moment, as Blazor is C# based.

• 3D Printing General Chat

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

  288
  Topics
  3300
  Posts

  

  @DIY-O-Sphere

  Thanks for the hint of price range. I would like to go for a 500mm so my budget needs to be revised a bit if I read your hint right 😉

• Off Topic

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

  78
  Topics
  951
  Posts

  

  It does, thank you @T3P3Tony

• Purchasing
  16
  Topics
  120
  Posts

  

  Wiring issue still relevant today. Plugged in using instructions, didn't work. I thought I fried my main board by reversing the wiring and seeing a puff of smoke and a flash. Turns out it was a fuse that strangely, was still good? Set up back the way they had wired it originally then moved blue pin to z-stop and it worked fine. Thank you for pointing out that the blue wire, and not the white wire is the sensor. Guess I got lucky, printer still heats up the bed, nozzle and all axis function properly...

• Order discussion

  Help with ordering, announcements etc

  143
  Topics
  871
  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.