Posts made by mrwizzard

@oliof

config

; General preferences
M111 S0                 ; Debugging off
G21                     ; Work in millimetres
G90                     ; Send absolute coordinates...
M83                     ; ...but relative extruder moves

M669 K1                 ; Select CoreXY mode
;M575 P1 B57600 S1       ; Comms parameters for PanelDue
M564 S1 H1              ; Forbid axis movements when not homed
;M918 P2 R6 C30 E4 F200000  ; Fysetc 12864 display
;M150 R255 B255 P255 S2 X2

; Network
M550 PVoron V2.4        ; Set machine name
M552 S1                 ; Enable network
M586 P0 S1              ; Enable HTTP (for DWC)
M586 P1 S1              ; Enable FTP (for remote backups)
M586 P2 S0              ; Disable Telnet

; --- Z Drive map ---
;     _______
;    | 8 | 7 |
;    | ----- |
;    | 9 | 6 |
;     -------
;      front
;
; (looking at the printer from the top)

; Drive directions
M569 P0 S0 ; A
M569 P1 S0 ; B
M569 P3 S0 ; Extruder
M569 P9 S1 ; Z0
M569 P8 S0 ; Z1
M569 P7 S1 ; Z2
M569 P6 S0 ; Z3

; Motor mapping and steps per mm
M584 X0 Y1 Z9:8:7:6 E3          ; Z Axis
;M584 U0						; 

M350 X16 Y16 Z16 E16 I1         ; Use 1/16 microstepping with interpolation everywhere
;M92 X80 Y80 Z400               ; Set XYZ steps per mm (1.8deg motors)
M92 X160 Y160 Z400              ; Set XYZ steps per mm (0.9deg motors)
M92 E708.91                     ; Set Extruder steps per mm clockwork 2
;M92 E617.6470588 				; configure steps per mm galileo2

; Drive currents
M906 X1650 Y1650 Z900 E700      ; XYZ and E current
M906 I50                        ; Idle current percentage
M84 S240                        ; Idle timeout

; Endstops
M574 X2 S1 P"xstop" 			; Xmax endstop 
M574 Y2 S1 P"ystop" 			; Ymax endstop
M574 U1 S1 P"e0stop"            ; Probe Docked
M574 Z0 P"nil"					; no Z endstop


; Axis travel limits
M208 X0 Y0 Z-1 S1               ; Set axis minima
M208 X352 Y360 Z275 S0          ; Set axis maxima

; Bed leveling
M671 X-50:-50:400:400 Y0:430:430:0 S20      ; Define Z belts locations (Front_Left, Back_Left, Back_Right, Front_Right)
M557 X5:340 Y5:310 S50                       ; Define bed mesh grid (inductive probe, positions include the Y offset!)

; Accelerations and speed
M98 P"/macros/print_scripts/speed_printing.g"



M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 A"Bed Heater" ; configure sensor 0 as thermistor on pin bedtemp (heater sensor)
M308 S2 P"e1temp" Y"thermistor" T100000 B3950 A"Bed Plate"  ; configure sensor 2 as thermistor on pin e1temp (mic6 sensor)
M950 H0 C"duex.e2heat" T2 Q60                               ; create bed heater output on out0 and map it to sensor 2 (mic6 sensor). Set PWM frequency to 60Hz to prevent flicker
M140 P0 H0                                                  ; Mark heater H0 as bed heater (for DWC)
M143 H0 P1 T0 A2 S120 C0                                    ; Regulate (A2) bed heater (H0) to have pad sensor (T0) below 120°C. Use Heater monitor 1 for it
M143 H0 P2 T0 A1 S125 C0                                    ; Shut off (A1) bed heater (H0) if pad sensor (T0) exceeds 125°C. Use Heater monitor 2 for it
M143 H0 S115                                                ; Set bed heater max temperature to 120°C, use implict monitor 0 which is implicitly configured for heater fault
M307 H0 B1 S0.6 D30                                         ; Enable Bang Bang mode and set PWM to 60% to avoid warping


;M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 A"Bed"  ; configure sensor 0 as thermistor on pin temp0
;M950 H0 C"duex.e2heat" T0 Q60                               ; create bed heater output on out0 and map it to sensor 0
;M143 H0 S115                                               ; set temperature limit for heater 0 to 100C
;M307 H0 B0 R0.748 C121.2 D4.98 S0.60 V24.0				   ; Bed
;M140 P0 H0                                                ; Mark heater h0 as bed heater (for DWC)                        

; Hotend heater
M308 S1 A"Hotend" P"e0temp" Y"thermistor"        ; Hotend is e3d thermistor
M950 H1 C"e0heat" T1							 ;
M307 H1 B0 R2.383 C158.6:132.0 D4.85 S1.00 V24.0 ;
M143 H1 S300                                     ; Set temperature limit for heater 1 to 300C

; MCU sensors
M308 S3 Y"mcu-temp" A"MCU"
M308 S4 Y"drivers" A"Duet Drivers"
M308 S5 Y"drivers-duex" A"Duex Drivers"

;M308 S6 P"e1temp" Y"thermistor" T100000 B3950 A"Bed Plate"  ; configure sensor 0 as thermistor on pin temp0
M308 S7 P"duex.e2temp" Y"thermistor" T100000 B3950 A"Chamber Temp"  ; configure sensor 0 as thermistor on pin temp0



; Chamber temperature sensor via temperature daughterboard pins on Duex
;M305 S"Ambient" P104 X405 T21                   ; Set DHT22 for chamber temp
;M305 S"Humidity [%]" P105 X455 T21              ; Set DHT22 for chamber humidity

; Z probes

global mag_probe_x  = 62
global mag_probe_y  = 358
global bed_is_leveled = false

;M558 K0 P8 C"^e1stop" T18000 F600 H5 A5 S0.01 R0.2
;G31 K0 P500 X0 Y25 Z1.410           				  ; ?
;M558 K1 P8 C"^zstop" T18000 F240:60 H2 A10 S0.005 R0.2
;G31 K1 P500 X0 Y0 Z1.80                				  ; Z switch offset (if positive, greater value = lower nozzle. if negative, more negative = higher nozzle)


; Fans
M950 F0 C"fan0" Q250                ; Create fan 0 (hotend) on pin fan0 and set its frequency
M106 P0 S1 H1 T50                   ; Configure fan 0: Thermostatic control is turned on, based on sensor #1
M950 F1 C"fan1" Q250                ; Create fan 1 (cooling)on pin fan1 and set its frequency
M106 P1 S0 H-1                      ; Configure fan 1: Thermostatic control is turned off
;M950 F2 C"duex.fan3" Q250          ; Create fan 2 (electronics) on Duex pin fan3 (frequency is fixed on Duex)
;M106 P2 S0 H-1                     ; Configure fan 2: Thermostatic control is turned off
;M950 F4 C"fan2" Q30                ; Create fan 4 (electronics bay) on pin fan2 and set its frequency
;M106 P4 S0.25 H1 T50               ; (busted?) Run the fans at 25% if the hotend is over 50C
;M106 P4 S0 H-1 C"Bay Fans"         ; Manual fan triggering... with thermostatic mode they are always at 100%?

; LEDs
M950 H3 C"nil" ; free up e3_heat pin
M950 F3 C"duex.e3_heat"
M106 P3 S255 B0 H-1 C"Top Lights"

M950 H4 C"nil" ; free up e3_heat pin
M950 F4 C"duex.e4_heat"
M106 P4 S0 B0 H-1 C"Nevermore"

; Tools
M563 P0 D0 H1 F1                    ; Define tool 0 using fan 1 for M106
G10 P0 X0 Y0 Z0                     ; Set tool 0 axis offsets
G10 P0 R0 S0                        ; Set initial tool 0 active and standby temperatures to 0C

; Misc
M912 P0 S-4                         ; MCU temperature calibration (yours will be different)
M593 P"zvdd" F33 S0.0				;
;M376 H2                            ; Fade mesh out compensation over 2mm Z


M143
M501                                ; load config-override.g
T0                                  ; select tool 0


;M915 X Y Z S12 R1

;M955 P0 C"spi.cs3+spi.cs4" I50 ;Accelerometer

speed_printing.g

M566 X500 Y500 Z60 E8000        ; Set maximum instantaneous speed changes (mm/min)
M203 X25000 Y25000 Z6000 E15000 ; Set maximum speeds (mm/min)
M201 X10000 Y10000 Z600 E1800     ; Set maximum accelerations (mm/s^2) 
M204 P10000 T10000                ; Set printing acceleration and travel accelerations

@deckingman its 8000mm/min, should it be higher?

@oliof that's what i meant, 5mm/s for X/Y. my E is plenty high. disabling PA fixes it, but also increasing the jerk for XY to at least 10mm/s with PA fixes it at least up to 35mm3/s then problem starts again. either there's something else i'm missing or there's an issue with RRF's PA. i didn't encounter this with klipper (with a low square corner velocity) but that machine has a different extruder and runs a old volcano, however both are 0.6 nozzles.

@deckingman it's 5mm/s per input shaping recommendations. it only seems to happen at higher flow rates, anything from 1mm3/sec to 25mm3/sec seems fine before it starts getting the above.

So i was testing max flow rate, 0.6 CHT, rapido HF and i get this weird under extrusion issue on the rounded corners with PA enabled, value is 0.03 PLA. without PA its fine with the same flow rate range. this is testing 20mm3 to 30mm3. Any ideas what could be causing it? jerk or some other setting?

@Exerqtor IMO, docs should be brought up to par with klipper. things like interpreting the graphs, looking at not just shaping but mechanical issues, loose belts etc.... it would also be nice if the plugin would give suggested freq and accelerations.

I also find the orientation chart confusing as hell for the accelerometer, especially when it's using a 1LC as guide when not everyone uses one of those.

Also, there's no issue collecting the accelerometer data with M956, it creates a CSV with data.

However this also happens in reverse. if i remove the accelerometer setup, home the machine then try to run M955 it will also crash with out of memory. so it's either connect the accelerometer or home the axis, can't have both. lol...

edit: i've disable the display and freed up more memory and it works, for now.

Edit: i thought this happened after upgrading to RRF 3.4.5, please move to right forum.

When using an accelerometer, detected in the input shaping plugin, homing the machine causes it to reset.

Using this, which is correct for my setup i believe. removing this line from the config fixes the issue.

M955 P0 C"spi.cs3+spi.cs4" I10 ;Accelerometer

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-9T6BU-FG3SN-6J9FJ-3SN6L-9SWVG
Used output buffers: 1 of 26 (12 max)
=== RTOS ===
Static ram: 23836
Dynamic ram: 85312 of which 0 recycled
Never used RAM 76, free system stack 184 words
Tasks: NETWORK(ready,10.8%,237) ACCEL(notifyWait,0.0%,348) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) DUEX(notifyWait,0.0%,24) MAIN(running,86.1%,444) IDLE(ready,3.1%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:24 ago, cause: software
Last software reset at 2022-12-29 20:04, reason: OutOfMemory, GCodes spinning, available RAM 4, slot 0
Software reset code 0x41c3 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x20003e38 Task Move Freestk 324 ok
Stack: 2001aa5c 0041009d 00000002 00410273 00000008 00000014 20004038 0042b43f 2001aa78 00425223 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 6c000000 20003eec 2001d540 2000c9e4 20003f18 00000000 00016e35 00425659 3fb504f3
Error status: 0x00
Step timer max interval 0
MCU temperature: min 25.0, current 25.5, max 29.3
Supply voltage: min 24.1, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/3, heap memory allocated/used/recyclable 2048/46/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: 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-12-29 20:05:23
Cache data hit count 901695954
Slowest loop: 6.54ms; fastest: 0.19ms
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 0.7ms, 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
Heater 1 is on, I-accum = 0.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
=== DueX ===
Read count 1, 2.48 reads/min
=== Network ===
Slowest loop: 128.53ms; fastest: 0.00ms
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 0
WiFi firmware version 1.27
WiFi MAC address 84:f3:eb:83:2b:76
WiFi Vcc 3.37, reset reason Power up
WiFi flash size 4194304, free heap 24728
WiFi IP address 192.168.20.49
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

@ctilley79 thanks for this. i have a similar issue with my voron 2.4. mostly the tool head/fan vibrates a ton a specific speed, but i noticed at least two speeds for mine. i don't use the ldo motors either but i have them. just not that excited to change them out...

Had something similar happen a few times, not sure if it's an issue in my config but sounds similar. it just decides to go take a walk in the opposite direction, stop then it runs the next command which is usually homing X/Y then it resumes like normal. sometimes it tries to go too fast and the steppers buzzz like they're stuck but there's nothing in the way.... it works normally in every other scenario. it's glitched but seems hard to reproduce.

@dogma2k I've experienced #3, and gave up. i figure it was the connection even though it does detect it every time. when it doesn't a reboot fixes it. i got data points in some files but at the end of them say something like "failed to read from accelerometer." and locks up the whole board. if it's the cable i'll just have to try another time. too frustrating to deal with and re-crimp wires, lol.

@thepfeiffenator looking at the mesh, i would try some physical leveling too. Either the X is tilted or bed is physically tilted. the less compensation the better. just because it compensates doesn't mean it always should

Seems like just a config issue on my part, crazy right? somehow a e2 heater got uncommented because it was connected to a chamber light so it turned on (was never on before!), then the config-override had 1.0 as the PWM which i never looked at and i did delete but i restored from a backup as i messed something up and completely forgot.... it was a long day. everything appears to work fine now.

However, i did get the panasonic SSR anyway as the omeron is out of stock (probably because people are building vorons). i figured the other one is fine as it's rated for 40A. (probably not but it might at least be 10A).

So i've been building a voron and used an ssr i had used before but different board. i'm using the duet 2 wifi. so when I used this on bed output DC in on the ssr like usual, it works and the bed heats but the average voltage is the full 24v regardless the pwm setting so it's pulling like 700w, lol.

however when i tested it on another heater on the duex, e2 i think...before i finished the config it seems the mosfet poped and it's suck on. while the bed output isn't on the main board i feel like this SSR broke something or is preventing proper pwm.

Any ideas where to look? i have a new mosfet for the duex but perhaps this is an issue with U11? i haven't checked if my hotend has the problem which is probably a good idea. i have some extra replacement chips for U11 but.... i rather not if i don't have too.

Thanks

Not just the duet but the power supply must be able to handle it too if using an SSR. my take is anything bigger than 10-12" and i would use an AC silicone heater with an SSR... it will also heat up just as fast as the hot end to 100c+

i didn't think you would home Z when there is a power loss... you would just run into the print unless you did home to max. setting it to ignore the un-homed z might work so you just home X/Y and Z stays as is.

@fma awesome, this works. I was removing the lines manually for the first two i did but figured i would look it up. Thanks for figuring it out

i've looked, it's a bootup issue. It never event attempts to connect 90% of the time... i have to manually reset a few times in a row before it even tries to connect to get to that point... but 100% of the time when it does TRY to connect it connects fine with zero issues. It's almost like the module isn't getting turned ON when it should. maybe a SD card issue, no idea...

Can't edit? but added note, the 3.3v and 5v power lights come up fine..... USB or 24v powered seems the same either way.

So i got a new Duet wifi, but 9/10 when it boots either after reset, power off the wifi module fails to come online. My definition for online is the blue light flashes while connecting to the AP, it either stays solid or stops which is fine if it cannot connect.... But in this case it doesn't come up until multiple-resets. Rarely it comes online first reset/startup from power off. So when saving configuration to emergency stop i have to constantly reset it again... and sometimes i have to do it up to 5-10 times before it decides to start trying to connect.

When it connects, it works fine though.

In addition to that, all end stops from Z to E0 seem to always report a single state dependant on the configuration, Hit or Not Hit. no response/action from the endstop, they never appear to work. Far as i know mine are NC with ground as the signal.

Aside from that, i configured sensorless homing and a BLTouch on it and works flawless and everything else seems fine but the Wifi issue and endstops bug me since this is a new new board. if i'm away from the machine and it needs a reset, there is maybe a 90% chance it won't come up.

It's still on the shipped firmware which is the V2.0 RTOS version.

the Config.g seems pretty typical from the configuration generator and has the Enable Network command and usual setup at the start of the file so not sure what it could be unless i need to re-flash the Esp8266. it might very well boot if i retried from the serial/USB console but issue is having it work on a reset or power up.... it's just unstable.

I'm trying to determine if it's a known issue or if i should just return it for another one since the endstops appear DOA.... i still have to check if there is indeed voltage on the endstops. maybe a fuse is popped?

Thanks.