Is there some function like M48 in Marlin? I’m running RRF 3.4.
Latest posts made by smaaash
-
Probe repeatability.
-
RE: Duet mini issue.
@Phaedrux Sent the Email! thanks for the support!
-
RE: Duet mini issue.
@droftarts from Filastruder Invoice #94794
Jun 4, 2023. Thank you for your guidance in this matter. -
RE: Duet mini issue.
@droftarts thank you for your hrlp with this! This printer was once a TronXY X5S, motors connected currently X0.0 Y0.1 Z0.4:0.3 E121.0 originally the z1 was on 0.2 but the motor wouldn't turn anymore. for troubleshooting I moved it to 0.4 and it turns now. I can't move the motors although the steppers are disabled on the gui. When the unit is off I can move the motors freely. the clicking noise is intermittent once very 5-10 seconds and it seem to be felt in both my x and y . The motor current is so high because my bed is significantly heavier since i replaced it with a MIC6 bed. This printer has worked flawlessly since July 2023 when I installed the new controller and can-bus toolhead board. I run my machine on both whole home surge protection and a power conditioning UPS. Below is MY M122:
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.5 (2022-11-30 19:41:16) running on Duet 3 Mini5plus Ethernet (SBC mode)
Board ID: 807DR-UA67A-G65J0-401GW-K682Z-HQLLU
Used output buffers: 1 of 40 (19 max)
=== RTOS ===
Static ram: 103652
Dynamic ram: 96672 of which 36 recycled
Never used RAM 41352, free system stack 194 words
Tasks: SBC(ready,1.2%,452) HEAT(notifyWait,0.0%,367) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,774) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,348) TMC(notifyWait,0.3%,115) MAIN(running,97.4%,508) IDLE(ready,0.2%,30) AIN(delaying,0.8%,263), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:04:55 ago, cause: power up
Last software reset at 2024-01-25 03:29, reason: User, GCodes spinning, available RAM 41352, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 295932, completed 295932, timed out 0, errs 0
Step timer max interval 1489
MCU temperature: min 19.9, current 30.7, max 30.9
Supply voltage: min 23.8, current 23.9, max 24.0, 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: not present
Driver 1: not present
Driver 2: not present
Driver 3: not present
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 11, reads 7568, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2024-01-27 01:08:41
Cache data hit count 672694472
Slowest loop: 3.59ms; fastest: 0.07ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 0.0MBytes/sec
SD card longest read time 0.0ms, 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 doing "M122" 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 2561, received 5578, lost 0, boc 0
Longest wait 3ms for reply type 6053, peak Tx sync delay 4, free buffers 18 (min 17), ts 1479/1478/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 11390/11390
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x0f6d4
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.6
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 0.07, max time between full transfers: 222.2ms, max pin wait times: 46.9ms/14.6ms
Codes per second: 0.00
Maximum length of RX/TX data transfers: 2944/504 -
RE: Duet mini issue.
@dc42 How do I go about proceeding? ( apologies if the "byname" is out of etiquette)
-
RE: Duet mini issue.
Also I have now noticed that my motors all all engaged at controller bord power on. and they are ticking now as well.
-
Duet mini issue.
Hello I run a duet mini 5+ ethernet in a SBC configuration on a corexy. I have been pretty pleased with the setup. Today however one of my Z motors started ticking and wouldnt move. I relocated the motor from driver from P0.2 to P0.4 and it moved fine. How do I go about troubleshooting further? below is my config:
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 Jun 10 2023 20:57:31 GMT-0400 (Eastern Daylight Time); General preferences
G4 S2 ; wait for expansion boards to start
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Duet 3" ; set printer name
M669 K1 ; select CoreXY mode; Drives
M569 P0.0 S1 ; physical drive 0.0 goes forwards
M569 P0.1 S1 ; physical drive 0.1 goes forwards
M569 P0.2 S0 ; physical drive 0.2 goes forwards
M569 P0.3 S0 ; physical drive 0.3 goes forwards
M569 P121.0 S1 ; physical drive 121.0 goes forwards
M671 X-88:418 Y165:165 S6 ; lead screws at left and right of X axis
M584 X0.0 Y0.1 Z0.2:0.3 E121.0 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E830 ; set steps per mm was E830 X80.00 Y80.00 Z400.00 X80.4829 Y80.44243 Z396.6287 E721.00 will investigate later
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 X1000 Y1000 Z1500 E1000 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X-9 Y0 Z0 S1 ; set axis minima
M208 X340 Y350 Z400 S0 ; set axis maxima; Endstops
M574 X1 S1 P"121.io1.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin 121.io1.in
M574 Y1 S1 P"io1.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io1.in
M574 Z1 S2 ; configure Z-probe endstop for low end on Z; Z-Probe
M950 S0 C"121.io0.out" ; create servo pin 0 for BLTouch
M558 P9 C"121.io0.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-21 Y5 Z1.54 ; set Z probe trigger value, offset and trigger height
M557 X30:320 Y30:320 S80 ; define mesh grid; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp2
M950 H0 C"out0" T0 ; create bed heater output on out2 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
M308 S1 P"121.temp0" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin 121.temp0
M950 H1 C"121.out0" T1 ; create nozzle heater output on 121.out0 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; Fans
M950 F0 C"!121.out1+out1.tach" Q25000 ; create fan 0 on pin 121.out1 and set its frequency -CTS 4 wire
M106 P0 S0 I0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"121.out2" Q500 ; create fan 1 on pin 121.out2 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
M307 H0 A101.4 C1123.0 D10.0 B0 ; PID for Bed
M572 D0 S0.025 ; Set pressure control to 0.025 -
RE: $wire Shenanigans 1LC
@dc42 What setting does the "Q" represent?
-
RE: $wire Shenanigans 1LC
@dc42 in my FW d I need anything mor than :
M950 F0 C"!121.out1+out1.tach" Q500
Do i need to call out the control wire or does tach imply it? My CANBUS address is default BTW.