Posts made by shaunppl

@eranglr Would be beneficial to see what you have built and what you use it for, perhaps then people could suggest alternate paths for you to follow or help investigate.

Sounds like you are after variable speed control ? on the fly ?

@Manrhpg1 Do you mean Ivan Miranda ?
which printer model did you follow, and what files did you download from his website.

Duets need to have the end switches to be homed before any other movements are normally recognised, you can get around this by M commands used in the console area of DWC control panel.

You can if you wish contact me directly and we can have a video chat and you can show me what you have got, I would be happy to try and help you and advise accordingly.

Where are you based in the world and we can arrange a meet on WhatsApp.

Contact me on WhatsApp Shaun Richards

@zecreton How are the AXIS homed ?, you have no end stops wired to the motherboard unless you are using the override g-code command in the console, you need to show us the start-up DWC panel Dashboard after booting that verify and show all the end stops have been triggered and are homed properly, as before it will allow manual movement of the motors these have to be triggered. Without this its very difficult to ascertain what the problem is and how to help you further, Unless anyone else has an ideas.

@agmeadows have you double checked the power supply feed and or the power supply output, where is the printer situated ?.
power spikes are another source of electrical interference that could be effecting the boards as a fluctuating input or ground can trip the boards to reset.

@jay_s_uk Yeah i am trialing the revo hotend with the upgraded smart efficator board (a lot more accurate and less prone to the vibration issues when bed levelling) and using a fixed mounted hemera extruder not the flying spring mounts, seems to be more stable and prints faster.

@jay_s_uk How are you getting on with your predator, I revamped mine with a rail conversion along with a meastro board and smart efficator made a hell of a difference.

@jay_s_uk Yeah i think so, but now worried as my other prototype are all on the maestro boards and 2 failures means i will have to probably move them all to duet 3 boards.

@jay_s_uk Had to upgrade to the Mini 5+ as my maestro board keeps wiping the sd cards ? and making them unreadable.

So took all my settings with it, so scraching head to sort 3 axis homing and other issues etc, talk about having a bad day. lol

@jay_s_uk Yep you are very right, have just uploaded the later firmware 3.4.0 and it worked, many thanks for your help.

@jay_s_uk Duet web control 3.4.0, FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.2.2 ELECTRONICS: Duet 3 Mini5plus Ethernet FIRMWARE_DATE: 2021-02-11

@jay_s_uk Just found them.

; tpost0.g
; called after tool 0 has been selected
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon May 23 2022 12:52:37 GMT+0100 (British Summer Time)
; Wait for set temperatures to be reached
M116 P0

; tpre0.g
; called before tool 0 is selected
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon May 23 2022 12:52:37 GMT+0100 (British Summer Time)

@jay_s_uk Where do i find that ??

When i click on heater 1 in the Dashboard screen to make it active i keep getting the following error and it will not activate the heater??

M568 P0 A1, The M568 command is no longer needed

This appears to be a javascript script ??

2, 11:23:46 M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus Ethernet (standalone mode)
Board ID: 577A8-6096U-D65J0-40KMD-MH03Z-R8DWU
Used output buffers: 3 of 40 (23 max)
=== RTOS ===
Static ram: 98732
Dynamic ram: 102484 of which 72 recycled
Never used RAM 43928, free system stack 138 words
Tasks: NETWORK(ready,172) ETHERNET(blocked,560) HEAT(blocked,295) CanReceiv(blocked,947) CanSender(blocked,358) CanClock(blocked,362) TMC(blocked,97) MAIN(running,440) IDLE(ready,20) AIN(blocked,260)
Owned mutexes:
=== Platform ===
Last reset 00:34:38 ago, cause: software
Last software reset at 2022-05-24 10:47, reason: User, GCodes spinning, available RAM 44172, slot 0
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
Aux1 errors 0,0,0
Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 10000, standstill, SG min/max 0/4, read errors 0, write errors 0, ifcnt 32, reads 42406, writes 3, timeouts 0, DMA errors 0
Driver 1: position -6000, standstill, SG min/max 0/4, read errors 0, write errors 0, ifcnt 32, reads 42406, writes 3, timeouts 0, DMA errors 0
Driver 2: position 6000, standstill, SG min/max 0/6, read errors 0, write errors 0, ifcnt 32, reads 42406, writes 3, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 29, reads 42409, writes 0, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 29, reads 42409, writes 0, timeouts 0, DMA errors 0
Driver 5: position 0, standstill, SG min/max 0/6, read errors 0, write errors 0, ifcnt 32, reads 42406, writes 3, timeouts 0, DMA errors 0
Driver 6: position 0, standstill, SG min/max 0/6, read errors 0, write errors 0, ifcnt 32, reads 42405, writes 3, timeouts 0, DMA errors 0
Date/time: 2022-05-24 11:22:08
Cache data hit count 3719245232
Slowest loop: 8.65ms; fastest: 0.11ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.7ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 341151ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 10, completed moves 10, 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 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.
=== Network ===
Slowest loop: 9.11ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 2 of 8

• Ethernet -
  State: active
  Error counts: 0 0 0 0 0
  Socket states: 5 2 2 2 2 0 0 0
  === CAN ===
  Messages queued 16659, send timeouts 16658, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16
  24/05/2022, 11:20:32 M568 P0 A1
  The M568 command is no longer needed

Congif.g File:
; 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.10 on Mon May 23 2022 12:52:37 GMT+0100 (British Summer Time)

; General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Uni3D 001" ; set printer name
M669 K1 ; select CoreXY mode

; Network
M552 P0.0.0.0 S1 ; enable network and set IP address
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable 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 S0 ; physical drive 0.2 goes backwards
M569 P0.3 S1 ; physical drive 0.3 goes forwards
M569 P0.5 S0 ; physical drive 0.5 goes backwards
M569 P0.6 S0 ; physical drive 0.6 goes backwards
M584 X0.0 Y0.1 Z0.2:0.5:0.6 E0.3 ; set drive mapping
M350 X32 Y32 Z32 E16 I1 ; configure microstepping with interpolation
M92 X400.00 Y400.00 Z800.00 E424.41 ; set steps per mm
M566 X600.00 Y600.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X1000.00 Y1000.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 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X330 Y330 Z600 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"io5.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io0.in
M574 Y1 S1 P"io6.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io2.in
M574 Z1 S2 ; configure Z-probe endstop for low end on Z

; Z-Probe
M950 S0 C"io3.out" ; create servo pin 0 for BLTouch
M558 P9 C"io3.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X0 Y40 Z2.5 ; set Z probe trigger value, offset and trigger height
M556 S50 X0 Y0 Z0 ; set orthogonal axis compensation parameters
M557 X15:330 Y15:330 S20 ; define mesh grid

; Heaters
M308 S0 P"temp2" Y"thermistor" T100000 B4725 C7.06e-8 ; 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 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 B4725 C7.06e-8 ; 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"out5" Q500 ; create fan 0 on pin out3 and set its frequency
M106 P0 S0 H1 T45 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out3" Q500 ; create fan 1 on pin out4 and set its frequency
M106 P1 S1 H-1 ; 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

@Phaedrux Completed yesterday, but forgot to include link, so edited the form just now and resubmitted with link.
Thanks for your help, sorry if I came over a wee bit arrogant over the M221 etc but really did not need this issue at the mo under the present pandemic as been hit really hard to keep sales going.

The board was purchased in the UK direct from Duet3d on the 15/07/2020.

The config.g is irrelevant as the config.g was used on the spare stock board and that worked 100% correct, the issue is with the stepper drivers circuitry or some part of the mainboard has some components that are failing when the system powers up.
The power supply has been tested and found without fault and the stepper motors independently tested on alternate build system also without fault, all units are brand new, when I build printers or upgrades all component's are tested before a complete assembly where as I can be confident that the components dont have faults.

The components did not fail under the config.g they failed under the test motors macro provided in the firmware accessed from the dashboard that is automatically loaded into the build.

The test programs are always used when first test is required, this is the first board that has failed a self motors test.

Here is the test macro for the motor test.

; Motor Test Routine for Duet 2 Maestro August 2018

;Start logging
M929 P"test1log.txt" S1

; Test motors
;----setup motors for test----

;The printer dimensions are deliberately set very high to allow a lot of moves during testing
M584 X0 Y1 Z2 U3 V4 ;Set all motors up as Axis
M906 X1400 Y1400 Z1400 U1400 V1400 I100 ; Set all motors to 2A with no idle current reduction
M201 X10000 Y10000 Z10000 U10000 V10000 ; Acceleration limits (mm/s^2)
M203 X100000 Y100000 Z100000 U10000 V10000 ; Maximum speeds (mm/min)

G92 X0 Y0 Z0 U0 V0 ;Set them all to 0

; Test motors

M291 P"The motors will start to move. Press all 5 endstops, 1 at a time to confirm the motors stop moving" R"Homing Test" S2
G91 ; use relative positioning
G1 S1 X3200 Y3200 Z3200 U3200 V3200 F1000 ; move XYZUV motors, stopping when endstops are triggered
;----end homing lines----

M291 P"The motors will start to move backwards and forwards together. Check that they all move in both directions" R"Direction Test" S2
G91
G92 X0 Y0 Z0
G1 S2 X400 Y400 Z400 U400 V400 F9000
G1 S2 X-400 Y-400 Z-400 U-400 V-400 F9000
G1 S2 X400 Y400 Z400 U400 V400 F9000
G1 S2 X-400 Y-400 Z-400 U-400 V-400 F9000
G1 S2 X400 Y400 Z400 U400 V400 F9000
G1 S2 X-400 Y-400 Z-400 U-400 V-400 F9000

M18 ; disable motors
G92 X0 Y0 Z0 U0 V0 ;Set them all to 0
M291 P"End Of motor Test" R"Motor Test" S2

M122 Gave no error warnings or messages, all drives were OK all voltages were 24.2v

M98 P Config.g
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled

The test motor test actually passes and gives no errors when the motors jam, so that does not make sense when i would have expected to see an error in the text logs but none ?, this is the first board out of 12 Maestro boards that has shown a failure under the test macros.

I have a Maestro running 24.2v with a new meanwell LRS350 24v power supply, configuring the new board for a new system, copied across the sdcard from an identical build and proceeded to start testing the system, first off had issues with no E0 drive, then could not home the system axis on XYZ, so tried the Test Motors macro, found E0 not turning and on 2nd part of test both Z axis motors stalled and started emitting high vibrational sounds like high pitched squeal and motor spindles locked solid, when the test then reversed the motor direction the spindles unlock and then immediately locked again and this continues until either i cancel the test using shut down button (STOP) or power off the board and supply ?.

Went through all the setting in the config.g files, checked the sdcard for errors, upgraded to 3.11 and reconfigured new config.g, exactly the same errors so went back to original Maestro firmware and started all over again, no difference.

Swapped board out with new spare stock, using the same SDcard and Configuration no issues with the stepper motors all functioning as should be.

Have ran diagnostics on the power supply, no over-voltages detected and steady output of 24.12V on all rails, tested the stepper motors on an alternate system all running normally.

At a loss as to what can cause this, first failure on this board for me, Have requested RMA.

Regards

Shaun

Yet again what a savior, I am making notes now as not to get lost, very new to 3.11 so again many thanks for your help.

OK what a twat should have noticed that, thanks, forgot to make notes before update and lost all my config files,

When it finished the probe (after changing to the correct parameters) it does not adjust the leadscrews to make up the bed being uneven ??, it just displays the warning that there are differences that exceed the limits.

That makes no difference And i have changed it to 0:0, as soon as the P4 starts the process, the motors move the x and y to positions, but on the way the x grinds into the end stop and keeps trying to to move in that direction and not the X30 position, when it goes to the front stepper screw position it then does the same for the Y Endstop until i have to hit the Stop button.

Sorry my fault, I did upgrade to 3.11 thought it was still on 3.01