@oliof Yes ,you are right, I just had this thought last night....
Best posts made by j3dk
-
RE: Duet 3 mini 5+ network problems
Latest posts made by j3dk
-
Duet 3 mini 5+ out 1&2 conectors
Duet 3 mini 5+ out 1&2 conectors. What is the size of these new connectors, both cable capacity mm2 pls.
and what crimp tool to use for them? -
RE: Duet 3 mini 5+ network problems
@oliof Yes ,you are right, I just had this thought last night....
-
RE: Duet 3 mini 5+ network problems
@dc42 Yes and now it's online again I don't know what and why but now I have found it on a totally different IP that not existed yesterday.
Thanks a lot for your help and fast respond time.Jens Kej
-
RE: Duet 3 mini 5+ network problems
@jay_s_uk Yes, but I still can't find it on the given IP from YAT
-
RE: Duet 3 mini 5+ network problems
@jay_s_uk Yes and I get hte following result:
M552 S1
ok
WiFi module is connected to access point SecureNest, IP address 192.168.87.110
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: RAKRW-A196U-D65J0-40KMW-LU03Z-7FDQQ
Used output buffers: 1 of 40 (2 max)
=== RTOS ===
Static ram: 102724
Dynamic ram: 105696 of which 60 recycled
Never used RAM 35224, free system stack 168 words
Tasks: NETWORK(ready,15.0%,385) HEAT(notifyWait,0.0%,366) Move(notifyWait,0.1%,334) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,340) TMC(notifyWait,0.0%,124) MAIN(running,84.0%,426) IDLE(ready,0.1%,29) AIN(delaying,0.8%,273), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:05:29 ago, cause: reset button
Last software reset at 2021-09-28 16:31, reason: User, GCodes spinning, available RAM 35224, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 329682, completed 329681, timed out 0, errs 0
Step timer max interval 737
MCU temperature: min 28.2, current 29.7, max 29.7
Supply voltage: min 0.5, current 0.6, max 0.6, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 63954, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 1: position 63954, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 2: position 63954, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 3: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 4: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 5: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 6: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 632817408
Slowest loop: 4.95ms; fastest: 0.11ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1, chamberHeaters = -1 -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
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is ready with "M122" 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 2965, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 1648/0/0
Tx timeouts 0,0,1647,0,0,1316 last cancelled message type 4514 dest 127=== Network ===
Slowest loop: 20.99ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 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.25
WiFi MAC address f0:08:d1:02:eb:6b
WiFi Vcc 3.39, reset reason Power up
WiFi flash size 2097152, free heap 25464
WiFi IP address 192.168.87.110
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
ok
- WiFi -
-
Duet 3 mini 5+ network problems
Why is my printer suddenly disapeared from my LAN? One night I turned it off and the next day when I turned it on it was disapeared from the IP-adress it had the day before and the control led for the web server was on.
I scanned my LAN but could not find it. Now I have tried everything described in the documentation, several times. The only thing that happens is the web server led turns om but can't connect to it from the IP, YAT says it have. When I try to connect to it I can't thoug the control Led was on and when I scan my LAN, I get this message
what is going on? -
RE: how to configure magnetic filament sensor on duet 3 mini 5+
@droftarts Hi there thank you for the advise. now I have figured it out putting this line in my config.g it works
M591 D0.3 P3 C"^io5.in" S1 ; filament monitor connected to E0_stop -
how to configure magnetic filament sensor on duet 3 mini 5+
I have conected my rotating magnet sensor to IO_5 on Duet3 mini 5+ but I can't find out how to set up my config.g
; 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.2 on Thu Sep 16 2021 12:55:16 GMT+0200 (Centraleuropæisk sommertid); General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"JK Preddy mod" ; set printer name
M665 R261 L440 B185 H420 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S1 ; enable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0.0 S1 ; physical drive 0.0 goes forwards
M569 P0.1 S1 ; physical drive 0.1 goes forwards
M569 P0.2 S1 ; physical drive 0.2 goes forwards
M569 P0.3 S0 ; physical drive 0.3 goes backwards
M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z80.00 E415.00 ; set steps per mm
M566 X1200.00 Y1200.00 Z1200.00 E1200.00 ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z1000.00 E1000.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 Z0 S1 ; set minimum Z; Endstops
M574 X2 S1 P"^io1.in" ; configure active-high endstop for high end on X via pin ^io1.in
M574 Y2 S1 P"^io2.in" ; configure active-high endstop for high end on Y via pin ^io2.in
M574 Z2 S1 P"^io3.in" ; configure active-high endstop for high end on Z via pin ^io3.in; Z-Probe
M558 P5 R0.4 C"temp2+io4.out" H5 F1200 T6000 ; set Z probe type to effector and the dive height + speeds
M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 R180 S20 ; 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 B1 S1.00 ; enable 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"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; Fans
M950 F0 C"out3" Q500 ; create fan 0 on pin out3 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out4" Q500 ; create fan 1 on pin out4 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"out5" Q500 ; create fan 2 on pin out5 and set its frequency
M106 P2 S0.25 H-1 ; set fan 2 value. Thermostatic control is turned off; 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
M591 P3 C"e0_stop" S1 ; filament monitor connected to E0_stop; Miscellaneous
T0 ; select first toolwhat am I missing?
-
RE: Dual Z-axis endstops
Thanks now Z and U is homing. Back to work…...
-
RE: Dual Z-axis endstops
I have the following software information:
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later + DueX5
Firmware Version: 1.21 (2018-03-21)
WiFi Server Version: 1.21
Web Interface Version: 1.21-RC4