@T3P3Tony Ok outstanding. Thank you!
Posts made by SonnyD1
-
RE: Duet 3 Tool Distribution Board
-
RE: Warning: Driver 1 warning: over temperature warning
@FlyingAspect Yes. I got a 75mm Blower and designed a duct to channel it straight to the back of the drivers. Eliminated the problem. Printer sounds like a jet taking off, but it's not bad. All electronics are underneath so it muffles it some.
-
Duet 3 Tool Distribution Board
Do I need a Duet 3 Tool Distribution board to run two Duet 3 Roto Toolboards from a Duet 3 Mini 5+? For an IDEX using two Rotos for example.
-
RE: SZP Coil Height
@dc42 will the heat from the bed/hot end be an issue? Will I have to stow it during a print? How much heat can it handle?
-
SZP Coil Height
I am building yet another IDEX printer utilizing two E3D Roto Toolheads with the Duet Roto board. I want to run the SZP coil but I have a couple questions that will help me complete the design. What height does the coil need to be from the bed when it runs its scan? I need to know this to design a mount. Also, can the coil withstand the heat from the bed? Do I still need a Z probe IOT establish Z offset or is the SZP a standalone unit capable of all my Z probing needs? Where is there some more documentation? I have read everything I can find and it's not much. I dont think this forum, as great as it is, should be the only source of info in the coil. Lastly, does the Roto tool board come with a coil? I'll stop there. Any info you can provide would be helpful. Sorry if I haven't provided enough info. Please ask if you need to know anything further. TYIA!
-
RE: BLTouch Configuration
I got it now. I have my speed turn up to a point that I like it and it probes Z in the center of the bed like it should too. Thank you @fcwilt and @droftarts.
-
RE: BLTouch Configuration
Ok so I made some adjustments and built up the courage to run a Home All. It touched off to the X/Y and when it went to the Z probe it went to the wrong position (which i can fix). The problem is now that it moved like a snail. I looked at the speeds in the home files and the snail speed doesn't make any sense. I'm gonna continue to tweak but if you see any issues please point them out.
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.3.16 on Sun Oct 15 2023 20:07:59 GMT-0400 (Eastern Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z 5mm relative to current position
G1 H1 X-235 Y-215 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F6000 ; go back a few mm
G1 H1 X-235 Y-215 F360 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 X15 Y15 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed; Uncomment the following lines to lift Z after probing
G91 ; relative positioning
G1 Z5 F100 ; lift Z relative to current position
G90 ; absolute positioning -
RE: BLTouch Configuration
@fcwilt I did not. I didn't even look for them because I figured the configurator would have created them. They are created now and I am conducting further testing.
-
BLTouch Configuration
After hours or reading I am still having issues with setting up a BLTouch on an initial printer setup. I've taken a Lulzbot Workhorse, put a Hemera XS with BLTouch on it, replaced the board and screen with a Duet 2 Wifi and Paneldue. That said, I am running 3.4.6 and am going through the commissioning process. I am on step 11 for the Z Probe. I cant seem to even get it to deploy with an M401 command and I dare not go any further until I do. I have done this a few times before on a Duet2/Duex combo without issue, so I'm kinda baffled. I have verified that it is not the BLTouch itself as I have two brand new ones and have verified functionality on other machines. Here is how I have it wired (board is installed upside down):
And here is how I have it configured:
; Configuration file for Duet WiFi (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.16 on Sun Oct 15 2023 20:07:59 GMT-0400 (Eastern Daylight Time); General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Lulzbot Workhorse" ; set printer name; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S1 ; X physical drive 0 goes forwards
M569 P1 S1 ; Y physical drive 1 goes forwards
M569 P2 S0 ; Z LEFT physical drive 2 goes backwards
M569 P4 S1 ; Z RIGHT pysical drive 3 goes forwards
M569 P3 S0 ; E0 physical drive 4 goes backwards
M584 X0 Y1 Z2:4 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E420.00 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X750 Y750 Z1180 E730 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X230 Y210 Z200 S0 ; set axis maxima; Endstops
M574 X1 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop
M574 Z2 S1 P"zstop" ; configure switch-type (e.g. microswitch) endstop for high end on Z via pin zstop
M574 Z1 S2 ; configure BLTouch for low end on Z; BLTouch
M950 S0 C"exp.heater3" ;create servo/gpio 0 on heater 3 pin on expansion connector
M558 P9 C"^zprobe.in" H5 F120 T6000 ; BLTouch connected to Z probe IN pin and the dive height + speeds
G31 P500 X50 Y-22 Z3.5 ; set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:195 S40 ; define mesh grid
M376 H10 ; taper off bed compensation over 10mm; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 R0.322 K0.239:0.000 D1.69 E1.35 S1.00 B0 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 R5.023 K0.673:0.686 D2.19 E1.35 S1.00 B0 V24.0 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C; Custom settings are not defined
Thank you very much for you help!
-
RE: Firmware error
@br7408 Your the first person outside of work that knows what that symbol means. Nice to meet ya Chief!
-
RE: Firmware error
@Phaedrux OMG...I should have done that to begin with. I definitely will from now on. I spent an entire day fighting with the conventional method and today I spent about 30 minutes and I was up and running. When it comes to starting from scratch, that method is so much easier IMO. Thank you so much! I was afraid to use that method for fear if it didn't work, I'd really be in trouble. Everything worked perfectly IAW the directions. Everything is up to date now and the base config is in and ready for commissioning. You have no idea how happy you made me.
-
RE: Firmware error
Every time I try to send a M997 S0, the terminal closes.
I run the M997 S0 and I don't get a reply. So i run the M552 and you can see the results in the photo. I can manage to get on the DWC now. I still cant get it to update. The best I get is a missing iap error. Would this be easier if I just erase it and load with BOSSA?
-
RE: Firmware error
@jay_s_uk So I did what you said. I went all the way back to 2.0.5. The pic below show the files in the sys folder.
I got this error message from YAT
I also created a new www folder and put the DWC 2.0.7 in it. After I was able to connect to the DWC. I will try to continue up the update ladder and I'll let ya know how it goes. UPDATE It worked for about 3 minutes. Still get the same incompatible error.
-
Firmware error
Please forgive me as I am beyond frustrated. I bought a Duet 2 WiFi some time ago and recently discovered that one of the stepper drivers was bad. Finally got the warranty worked out and I receive my replacement board. Now its on the a plethora of new issues. I cannot connect to the board via WiFi because of "incompatible firmware version" as seen in the image below.
So, IAW the instructions, I move forward to "Fallback procedure #1." The M997 S0 command sends back another error as seen in the next image.
The file is not missing and/or not in the incorrect folder as I have tried it in both the sys and the firmware folders. I put everything in both folders and I get the IAP missing but it is in fact there. The M115 returns: FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.05.1 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-02-09b1<LF>ok<LF>This has become a nightmare. Nothing seems to be working as intended despite my best efforts to follow all directions to the letter.
-
RE: Configure 2nd Z Axis Stepper
@Phaedrux I did as you advised and sent that email. I haven't yet received a reply.
-
RE: Configure 2nd Z Axis Stepper
@Phaedrux I ordered it from Filastruder on June 13 (#95005). I had some life events come up which is why I'm only just now working on it.
-
RE: Configure 2nd Z Axis Stepper
@moth4017 I've isolated the issue to the E1step driver that my right Z stepper is plugged into. Swapping wires and motors the fault stays on the same driver. I do not have another driver that I can try.
-
RE: 12864 LCD on Lulzbot Workhorse
Thank you for the help everybody. What I wanted to accomplish isn't possible with my current hardware. I've decided to go in another direction and replace the 12864 with a paneldue. I really appreciate you taking the time @dc42 and @DIY-O-Sphere.
-
RE: Configure 2nd Z Axis Stepper
@Phaedrux I don't get any error messages when moving the Z axis. One motor (Z Left) moves and the one on the right does nothing. I've confirmed that it's not the motor or the wiring by running both motors with both cables on the Zstep driver. I cant get anything to work on the E1step driver. I removed the duplicate 16 value from the M350 line before running the tests. Here are the results from the M122 taken immediately after tests:
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.6 (2023-07-21 14:08:28) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6M2-NWNS0-7J9D4-3SD6K-1V33L
Used output buffers: 1 of 26 (14 max)
=== RTOS ===
Static ram: 23896
Dynamic ram: 74944 of which 0 recycled
Never used RAM 13240, free system stack 184 words
Tasks: NETWORK(notifyWait,13.3%,242) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) MAIN(running,86.2%,436) IDLE(ready,0.4%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:03:35 ago, cause: software
Last software reset at 2023-10-10 21:49, reason: User, GCodes spinning, available RAM 13168, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 31.5, current 32.3, max 32.8
Supply voltage: min 24.1, current 24.3, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2023-10-10 21:52:41
Cache data hit count 4294967295
Slowest loop: 5.77ms; fastest: 0.18ms
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 3.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, 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
=== 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
=== Network ===
Slowest loop: 12.68ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
= WiFi =
Interface state: active
Module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.27
WiFi MAC address f4:cf:a2:71:b4:05
WiFi Vcc 3.35, reset reason Power up
WiFi flash size 2097152, free heap 19896
WiFi IP address 192.168.1.137
WiFi signal strength -52dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0