@gloomyandy Hi.
I just solved the issue. I noticed in Object Model that the Y endstop was not showing "highEnd" and "type" it was for the X, but it was triggering, but not home as mentioned. So I switched over to another io, io5 to io2 and that solved it!
![Fixed]
image url)
One more thing, I switched over to Normally Closed.
Hi all.
I decommissioned a delta and repurposed the Mini 5 on an old TAZ 4, which ran solid with the Maestro board, but I thought I'd give it an upgrade. I feel I'm 99% there, but the y axis has me frustrated.
When I command a "homeall", I notice an odd behavior with the y axis, it starts at the same time as x, but then the y stalls, then tries to move again with hesitation, only after the x has finished it's homing procedure. The y restarts slowly, then accelerates hitting the minimum limit hard (I e-stop it here).
I have tried several things, like reversing the direction of y and changing the endstop to high end, no success. Changed the drive assignment physically and in the config to match, same results. M119, show that the endstops are getting triggered when I actuate them by hand. Nonetheless, x and z axis home fine.
Than you!
; Configuration file for Duet 3 Mini 5+ (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.16 on Sat Sep 30 2023 23:42:55 GMT-0700 (Pacific Daylight Time)
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Old Man TAZ" ; set printer name
; Network
M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet
; Drives
M569 P0.0 S0 ; physical drive 0.1 goes backwards (X Axis)
M569 P0.1 S0 ; physical drive 0.2 goes forwards (Y Axis)
M569 P0.2 S0 ; physical drive 0.3 goes backwards (Z1 Axis)
M569 P0.3 S0 ; physical drive 0.3 goes backwards (Z2 Axis)
M569 P0.4 S0 ; physical drive 0.0 goes backwards (Extruder)
; Movements
M584 X0.0 Y0.1 Z2:3 E0.4 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X100.00 Y100.00 Z1200.00 ; set steps per mm
M92 E420.00 ; set extruder E0 steps/mm
M566 X1000.00 Y1000.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 X800 Y800 Z800 E1000 I60 ; set motor currents (mA) and motor idle factor in per cent
M84 S60 ; Set idle timeout
; Axis Limits
M671 X20:140 Y145:145 S2.0 P0.5 ; lead-screws at left and right of X axis, X270:55:270:55 Y235:235:15:15
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X295 Y295 Z250 S0 ; set axis maxima
; Endstops
M574 X1 S1 P"!io6.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin !io6.in
M574 Y1 S1 P"!io5.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin !io5.in
M574 Z1 S2
; Z-Probe
M950 S0 C"io3.out" ; create servo pin 0 for BLTouch
M558 P9 C"io3.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P10 X0 Y-45 Z1.675 ; set Z probe trigger value, offset and trigger height
M557 X20:275 Y30:240 S40 ; define mesh grid
; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
M307 H0 B0 S1.00 ; 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
M307 H0 R0.130 K0.150:0.000 D10.00 E1.35 S1.00 B1 ; PID Tuning
M308 S1 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C
M307 H1 R2.195 K0.334:0.276 D5.26 E1.35 S1.00 B0 V25.0 ; PID Tuning
; Fans
M950 F0 C"vfd" Q500 ; create fan 0 on pin vfd and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out5" Q500 ; create fan 1 on pin out5 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on
; Tools
M563 P0 S"E3D_E0" 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
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.6 (2023-07-21 14:09:13) running on Duet 3 Mini5plus Ethernet (standalone mode)
Board ID: Z4XQ1-1096U-D65J0-40KMA-2T03Z-RQ92N
Used output buffers: 1 of 40 (26 max)
=== RTOS ===
Static ram: 103712
Dynamic ram: 104764 of which 12 recycled
Never used RAM 33104, free system stack 144 words
Tasks: NETWORK(ready,27.2%,174) ETHERNET(notifyWait,0.2%,560) HEAT(notifyWait,0.0%,342) Move(notifyWait,0.0%,290) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,342) TMC(notifyWait,0.7%,72) MAIN(running,71.0%,423) IDLE(ready,0.0%,30) AIN(delaying,0.8%,263), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 01:08:54 ago, cause: software
Last software reset at 2023-10-01 11:57, reason: User, GCodes spinning, available RAM 33224, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 4134730, completed 4134729, timed out 0, errs 0
Step timer max interval 752
MCU temperature: min 36.4, current 36.6, max 36.9
Supply voltage: min 24.5, current 24.5, max 24.5, 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 4, read errors 0, write errors 0, ifcnt 98, reads 549, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 110, reads 549, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 2, read errors 0, write errors 0, ifcnt 110, reads 548, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 2, read errors 0, write errors 0, ifcnt 110, reads 549, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 89, reads 549, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2023-10-01 13:06:40
Cache data hit count 4294967295
Slowest loop: 1.79ms; fastest: 0.13ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 0.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 5, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 8, completed 8, 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
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
Code queue is empty
=== CAN ===
Messages queued 94, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 52/0/0
Tx timeouts 0,0,52,0,0,42 last cancelled message type 4514 dest 127
=== Network ===
Slowest loop: 3.52ms; fastest: 0.04ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
= Ethernet =
State: active
Error counts: 0 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 0
@o_lampe Yes, I know that. I had the motor removed from the extruder gear housing. What I meant is that I'm using M302 P1 and commanding "Extrude" from the GUI to monitor movement for testing.
@Phaedrux Sorry for getting back late, I was out on a business trip.
For the Duet2 WIFI, the current was set to 1A and ran without issues, but I understand it has different drivers and beside the fact it's older, nonetheless it worked.
No issues with other axis.
I changed the motor drive current to all the axis to 80% of motor mA specs, but that didn't change the behavior, as it the extruder motor still shuddered when commanded to extrude.
Although after enabling StealthChop it is now extruding. To verify, I have power-cycled the printer multiple times and now when I run an M302 P1 it extrudes and printed a 20mm cube without issues.
Issue RESOLVED!
Thank you for the support!
@Phaedrux okay, I didn't want to higher than 1mA risking damage to the driver, ignorance mainly, but I will try going higher as you suggested once I get a chance.
Why does the driver drive the motor in reverse (retract) with the mA current settings?
Thank you.
@OwenD I have already done that. I've explained that on my initial post.
What are the specs of the motor? Wantai - 42BYGHW609P1-X10, 1.8 degree Stepper, 1.7A
Have you tried a different motor? Yes. Same issue.
Have you tried the motor out of the extruder mechanism? Yes, I removed motor from the gear extruder housing, it's how I ran M302 P1.
Is there something mechanically restricting it? No. As I mentioned, I can change the mA values in the Config and restart the config, although I have to repeat the process until I can get it to work.
It sounds like either a problem with the motor or the extruder mechanism. Not likely, If I reinstall the Deut2 WiFi it works perfect.
@o_lampe , Hi. Happy New Year!
Okay, I just tried the M302, allow for cold extrude.
Same results, NO stepper motor movement when commanding to extruding, only movement is when retracting.
Prior to the M302, I was reaching the temperature target, no issue with temp.
Thank you for your support.
After retiring my Duet2 WIFI board and replacing it with a new Mini 5, the board is not driving the extruder stepper motor when trying to extrude. I have verified continuity from the stepper motor connector to the board connector and found no issues and motor phases are correct too. I have switched from stepper driver 3 to 4, and making the necessary changes in the config to reflect driver change and the same issue. Same behavior is encountered, neither stepper driver drives the extruder motor in the direction to extrude, only functions in retract.
I have also changed firmware, from 3.4.4 to 3.4.5, and back down to 3.4.2, no change in function. The only success I have had is changing the value of the mA settings in config. When I changed the value from the default of 800 mA to 1000 mA the printer will function as long as I don't shut the power off. If power-cycled the printer it will cease to function and I will have to play with the config's driving mA until I can get the stepper drive to function again. If I change out the board to my old Duet2 WIFI (switched to old duet config), they're no issues. But when I re-install the Mini 5 again to once again verify operation, the same issue. The reason I switched from the Duet2 board is I prefer LAN to operate all my devices.
When I command to extrude from the UI, and place my fingers on the motor's shaft, it shudders. Although when I select retract, the motor will spin.
What I'm missing here? I'm I missing a line in the config the Duet3's need? Again, no issue with the Duet2 WIFI.
M122>
Duet3-Mini-5_M122_console.txt
Config>
Config.txt
Thanks in advance!
I'm all set now, I directly installed the "DuetMaestroAP.bin file onto the SD Card and then uploaded the update.
M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 Maestro FIRMWARE_VERSION: 3.01-RC10 ELECTRONICS: Duet Maestro 1.0 FIRMWARE_DATE: 2020-04-25b3
Thanks for all the support here.
Uploading DuetMaestroAP.bin didn't work either, getting an infinite upload status for minutes that I have to cancel out. 
Thanks. I'm currently printing a part so when done I'll attempt uploading it.
Hello.
I'm getting an error when uploading the DuetMaestroFirmware.bin to a Maestro.
M997 S0
Error: M997: In-application programming binary "DuetMaestroIAP.bin" not found
M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 Maestro FIRMWARE_VERSION: 3.01-RC8 ELECTRONICS: Duet Maestro 1.0 FIRMWARE_DATE: 2020-04-17b4
I can upload the Duet2CombinedFirmware successfully, NOT the DuetMaestroFirmware.
I managed to fix the issue! Yay!!
Went to the G-Code wiki and made the change by adding the pull up resistor to "C"^zprobe.in"".
"The pullup resistor on the Z probe input is disabled by default. Enable it by prefixing the input pin (C parameter) with the ^ character. Enable pullup resistor with ^ if using Duet 2, running RRF3, using the Z probe input pin, and the probe type is a switch or BLTouch."
-Source: https://duet3d.dozuki.com/Wiki/Gcode
This is my change:
; Z-Probe
M558 P9 C"^zprobe.in" H5 F120 T3000 ; BLTouch connected to Z probe IN pin, free up MOD pin
M950 S0 C"zprobe.mod" ; servo/gpio 0 is Z probe MOD pin
M280 P0 S10 ; send control signal to BLTouch through servo/gpio 0
I appreciate your help! Thank you.
@PaulHew said in Maestro, RRF3, BLTouch Alarm triggered after Homing:
M558 P9 C"zprobe.in" H5 F120 T60000 A10 R0.75 S0.02 ; set Z probe type to bltouch and the dive height + speeds M950 S0 C"^zprobe.mod" ; create servo pin 0 for BLTouch
Hi PualHew,
First off, thank you for your reply.
I made the change you suggested, still getting the same result with this new error:
G28
Error: Z probe already triggered at start of probing move
Hi all,
I updated to RRF3 yesterday and spent a good part of the day reading up on BLT issues and solutions in the forum. With that, I've made the corrections to my config.g file necessary to home, deploy and retract the BLT; all works great for that. But, my issue is when commanding Home All the probe comes in contact with the bed continuing past 20% duty, probe then retracts while Z continues down slowly, BLT deploys once again and the Z continues down into 80% setting off the alarm and the Z stops about 2mm from E0 hitting the bed, by now the probe is fully retracted and Z goes up 5mm.
I clear the arlarm with - M280 P0 S160 with a macro command.
Snippet of config of where changes where made:
; Endstops
M574 X1 S1 P"!^xstop" ; configure active-low endstop for low end on X via pin xstop
M574 Y1 S1 P"!^ystop" ; configure active-low endstop for low end on Y via pin ystop
M574 Z1 S2 ; Set endstops controlled by probe **I've tried without too this line.
; Z-Probe
M950 S0 C"zprobe.mod" ; servo/gpio 0 is Z probe MOD pin
M558 P9 C"zprobe.in" H5 F120 T3000 ; BLTouch connected to Z probe IN pin, free up MOD pin
G31 P25 X-34 Y18 Z2.497 ; Set Z probe trigger value, offset and trigger height **Tried without this line too.
M557 X60:220 Y60:220 S20 ; define mesh grid
**I've commented out the lines out and tried, but same results. I don't know what else to change to get the BLT working as I had it functioned well in RRF 2.05.
Thanks in advance.
@dc42 Hi, after relocation the BL-Touch and adding additional probing points seemed to do the trick. Thank you all for you help> @JamesM @grizewald
New pics...
image url)
image url)
@grizewald Hi, the BL-Touch was skewed slightly. I have relocated the BL-Touch and now it perfectly vertical.
Thanks!
@zapta Hi, I did run the bed comp. at print temp. So what I have done, is relocate the BL probe the left side (my left) and will make changes to the config.g to reflect the change. As JameM mentioned in his post, doing that will give more room for additional probing points and that may be the solution...hoping.
Thanks.
I'll relocate the BL Touch closer and change the probing grid to have more points.
@JamesM, Thanks!