@chichirod that worked. Thank you

@ray11
Is the motor louder or the belt/pulley combo? (2GT and GT2 standards are not exactly the same )
Does the belt rub somewhere (against the idler pulleys)?

Good morning @t3p3tony and @gloomyandy

I changed the SD card and the same thing happened, this time it did reboot during a print once.

Maybe something else happened as it says that it was restarted 95h ago but the printing stopped.

I have activated an M929 eventlog to see if it gives me more information.

This was the result of M122:

16/11/2021 15:15:32 M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917NK-F23T0-6JTDJ-3S46L-TDADD
Used output buffers: 3 of 24 (24 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 75504 of which 0 recycled
Never used RAM 12180, free system stack 168 words
Tasks: NETWORK(ready,14.1%,217) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,364) MAIN(running,85.8%,461) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 95:21:31 ago, cause: software
Last software reset at 2021-11-12 15:53, reason: StuckInSpinLoop, GCodes spinning, available RAM 11972, slot 1
Software reset code 0x4083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x200032b4 Task NETW Freestk 403 ok
Stack: 0042ae6f 004545fc 410f0000 3e800000 412586e8 42263771 3edbc06f 3331bb4c 40000000 b5ddd98d 388ab355 bb360b61 3e2aaaab 3f800000 00000000 40951efe 457f5a39 7f7fffff 3e800000 80000010 00000000 00000000 0042ae6f 00000001 0025bc42 00000000 20000818
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 35.1, current 35.6, max 35.6
Supply voltage: min 24.2, current 24.3, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/6, heap memory allocated/used/recyclable 2048/62/0, gc cycles 0
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-11-16 15:15:13
Cache data hit count 4294967295
Slowest loop: 3.60ms; fastest: 0.17ms
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 1.0ms, 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 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.4
=== 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: 201.69ms; fastest: 0.08ms
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 1
WiFi firmware version 1.26
WiFi MAC address 84:0d:8e:b3:06:d4
WiFi Vcc 3.38, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24632
WiFi IP address 192.168.1.230
WiFi signal strength -51dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 4 0 0 0 0 0 0 0

@tecno The M587 I parameter is mentioned here https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7#s50 with a link to M587 in the Gcode dictionary straight after:

If you have a Duet 2 WiFi or Duet 3 Mini 5+ WiFi, this is sufficient to enable networking and let your network router assign an IP address via DHCP. If you need to assign a static IP address, use M587 with the I parameter when setting up the SSID in Step 9. See M587 in the G-code dictionary.

I guess you had set this before with M587 ... I10.0.0.14 ? Sending M587 on it's own lists the saved SSIDs, including any fixed IP address. Unfortunately the Guide format doesn't give much space for a long explanation of this, and it is covered in the Gcode dictionary, so I'm not planning any changes.

Ian

@mathv Thanks for reporting this, I am going to fix it in the next version.

@piranha32 said in Non-pwm cooling fan control:

I'm planning to build the pump controller

if thats the case then it would be the least effort to build one that accepted PWM signal duty cycle to indicate requested speed.

@j-mas1 is the external system (like a robot arm) capable of interpreting the gcode with an E position and sending that to the duet? If you are trying to run the same file on two controllers and have them sync movement based on reported position then that will run into loads of issues from a latency perspective. An alternative could be to pass the required XYZ positions from the Duet to the controller of the external system?

@jrdm this feature is currently experimental in firmware 3.4.0 beta 6. It is only partly functional in RRF 3.3.

@phaedrux
While treveling from Probepoint 1 to P2 (or P2-> P3 or P3->P4) Z moves down simultaniusly.

now I use

; bed.g M150 R145 U40 B0 Y1 S1 F0 G28 XY G1 X10 y10 Z5 F30000 G30 P0 X10 Y40 Z-99999 G1 X325 y10 Z5 F30000 G30 P1 X325 Y40 Z-99999 G1 X325 y300 Z5 F30000 G30 P2 X325 Y330 Z-99999 G1 X10 y300 Z5 F30000 G30 P3 X10 Y330 Z-99999 S4 M150 R0 U255 B0 Y1 S1 F0

it works better, but not as supposed in the tutorials

@aze You can see a bit more about the tool change behaviour here: https://duet3d.dozuki.com/Wiki/Multiple_tools_and_Tool_change_macros#Section_Tool_Change_Macros

@gloomyandy Hello. Your suggestion / solution helped us to resolve the issue. Thank you so much.. Appreciated.

@cando415 great that that is fixed.

@cando415 said in Y Homing on CoreXY:

@gixxerfast & @fcwilt
yes. -5 🤦

@Gixxerfast
checked the Endstopcontroller, rewired it. now it works fine

Glad to hear you got it working.

Frederick

Thanks everyone!

@phaedrux would be great if you could update both docs pages with a simple cross-link and a sentence that explains that they are equal.

@gloomyandy

I should have noticed the difference in the C parameters. I guess I focused too much on the R parameter. The part cooling fan is always off during initial heating which is where the fault occurs. I have made some modifications to the part fan nozzle so I should have redone the auto tune. I will watch carefully to insure the part fan comes on during the tune.

Thanks for the suggestions.

John

@cosmowave said in Duet2 Stepper Driver cooling:

............................I'd like to monitor the temp only for completeness and because we are able to do that!🤠

That's as good a reason as any. 🙂

@marcossf please post your config.g file.

After you run M999 and get those errors on the console, if you then run M98 P"config.g" do you get the same errors again?

@raymonds I have been running the Duet 3 mini 5+ with three different A/B-motor setups now:

LDO-42STH40-2004MAC 0.9 - I could not get these to work without layer shifting with the Duet board. OMC/Stepperonline 17HS19-2004S1 - These are great affordable stepper motors and worked perfectly IMHO. Still got four of them on Z. Ran them at 1200 - 1600 mA LDO-42STH48-2504AC - Had to see what the hype was all about. I run these at 1600 mA and they are OK but quite noisy. Probably for the speed freaks running 48V stepper drivers. As #1 on my list they have the JST connector so I got neater cabling with these than with #2. Nothing wrong with these so far so they'll stay on.

Disclaimer: These are my subjective opinions not based on any calculations and they may work for me but not for anyone else.

I might add that I have two Sanyo high flow 60 mm fans cooling the controller bay which is quite airy. I haven't noticed any temp warnings from the stepper drivers.

@dank0 did you correct that G90 to G91 as @fcwilt pointed out?

Please post your homex.g, homey.g and homeall.g files too.

BTW your Z homing script is incorrect - although I don't think that is the cause of your issue with re-homing X and Y. When using a Z probe for homing, you should home Z using a G30 command, not a G1 H1 command, and you do not need to define a Z endstop using M574. See https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_Homing_Z_using_a_Z_probe.

@rjenkinsgb Appreciate the info, reconsidering my original plan