@tomasl

I had issues trying to set a static IP as well. I finally got it to work with some suggestions. The steps seems to be very picky. See this thread,

https://forum.duet3d.com/topic/22703/duet-3d-wifi-set-ip-address/7?_=1621469740585

@phaedrux that worked. Thanks again.

Thank you that fixed it, I must have missed I needed to move my M350 and M92 commands after my M584.
I will look at my M593 and fix that, I am at least printing again and that is the important part.

@psyblue the main change between bootloader 2.2 and 2.3 is that in 2.2 if it didn't get a satisfactory frequency reading within a certain time, its reset the processor to start again. In 2.3 it just keeps on taking readings, in effect allowing the crystal oscillator as long as it needs to stabilise.

Now working!. I think the problem was this: mapping the y-steppers to drive 2 and z stepper to drive 1. In addition, the z motor is bigger and needs more amps to move.
The drive 0 was hotter than it´s neighbours allthough not in use. Maybe some damage?

@engikeneer Thank you so much. I will check the guide!!!

Guys , next beer i will spend.

@phaedrux will do, thank you for your help I appreciate it!

@lbi thoss cables are overkill. For power I suggest something like https://www.conrad.com/p/tru-components-1565746-speaker-cable-2-x-080-mm-red-black-100-m-1565746. For CAN you can use unshielded twisted pair, either single pair if you have just one tool board (so it can be at the end of the CAN bus), otherwise 2-pair such as Lapp 0035101.

@stephen6309
Thanks!

Yes, no problem.

@tecno you can start a new thread in this category. I will mark this as solved.

@phaedrux Here is mine in io.4 of a mini5+ btt.jpg

Black supplied wires reading "up" v3.3, signal, gnd.

On the sensor side I left it the way it comes from BTT. Which looking at it from the label side is a 4 pin plug only populated in 3 |V _ S G|
Where v is ~3.3-5v

in config.g
M591 D0 P7 C"io4.in" L7 R50:200 E15 S1

"M591 D0
Pulse-type filament monitor on pin io4.in, enabled, sensitivity 7.000mm/pulse, allowed movement 50% to 200%, check every 15.0mm, no data received"

I need to tweek the setting but its working fine.

@kotuo, you lucked out 🙂

with my pause, the first step I do is move z all the way to the top of the z travel to get it out the way and then move the spindle away from the workpiece. On resume, I do the opposite

@phaedrux Thank you!

@fma said in Using stepper currrent to detect a tool is loaded:

@rzi said in Using stepper currrent to detect a tool is loaded:

@dc42 CNC user here. Is it possible to add. I'm using two free drivers for a motorised vise. Would be super to have a mean of applying same force on each part I'm machining.

You could set the current of the vise motor to set the wanted force (torque). Then, just turn the motor until it stalls (using stallGuard feature, through a homing procedure, for example), and you should get roughly the same force each time.

Ah yes, going to test that. A much more straight forward approach. Thanx

@flex12

This is the code from 122
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later + DueX2
Board ID: 08DLM-996RU-N85T0-6J9FL-3SD6R-1SS3N
Used output buffers: 3 of 24 (15 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 73900 of which 24 recycled
Never used RAM 14696, free system stack 204 words
Tasks: NETWORK(ready,186) LASER(blocked,67) HEAT(blocked,308) DUEX(blocked,31) MAIN(running,625) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:13:33 ago, cause: software
Last software reset at 2021-05-02 21:56, reason: User, GCodes spinning, available RAM 14452, slot 1
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
MCU temperature: min 36.3, current 36.8, max 37.8
Supply voltage: min 0.2, current 0.4, max 2.0, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: position 0, ok, SG min/max not available
Driver 1: position 0, ok, SG min/max not available
Driver 2: position 0, ok, SG min/max not available
Driver 3: position 0, ok, SG min/max not available
Driver 4: position 0, ok, SG min/max not available
Driver 5: position 0, ok, SG min/max not available
Driver 6: position 0, ok, SG min/max not available
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-05-02 22:09:51
Cache data hit count 1135360814
Slowest loop: 7.13ms; fastest: 0.13ms
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.9ms, 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 = -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== 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: 15.76ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
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.25
WiFi MAC address 84:0d:8e:b2:f6:52
WiFi Vcc 3.33, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25600
WiFi IP address 192.168.0.102
WiFi signal strength -43dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
=== DueX ===
Read count 1, 0.07 reads/min

@droftarts I can confirm the miswiring causes the z probe to not report back to the main board. I tried many times and while the probe would deploy it would not show any value in the UI but 0 when manually touched.

My 4th was just delivered and after swapping it out it worked perfectly instantly. With the wrong wires going to ground and the Z probe acting as the 5V had fired something for sure.

With the 2nd one I did 100% hear a pop when I issued the M401 command.