@infiniteloop
Ok, problem appears to be solved.
All carriages removed, cleaned and reinstated. Belt tensions checked and stepper motor current reduced by 80%.
Added always on 40x40 cooling fan to underside of board.
Thanks for all the comments!

@droftarts
I can try put my Flea-Scope on it and see if it can see any differences.

Although, with all of these boards being brand new and only in operation a week or so, I wouldn't expect it to have a failed part already unless defective from the start.

@Phaedrux ,,,Thank you I'll check out the link and try the file in a dif location help is appreciated

@dc42 this is what I have for my tpost0.g

What are the coordinates for the state?  Machine based or tool based?

; called after tool 0 has been selected ;Drop the bed var zRestore = state.restorePoints[0].coords[2] var zTool = move.axes[2].userPosition var newPos = var.zRestore + 5 ; in case it's needed if {!exists(var.zRestore)} G91 G1 Z20 G90 elif { var.zRestore > var.zTool } var message = "zRestore higher at: " ^ {var.zRestore} ^", zTool: " ^ {var.zTool} ^ " need to adjust Z, moving to " ^ {var.newPos} M118 S{var.message} P0 G1 Z{var.newPos} elif { var.zRestore < var.zTool } var message = "zRestore lower at: " ^ {var.zRestore} ^", zTool: " ^ {var.zTool} ^ " no need to adjust Z" M118 S{var.message} P0 if heat.heaters[1].current > 170 ; Checking for safe clearances then wiping M98 P"/macros/tools/safeX" M98 P"/macros/tools/safeY" M98 P"/macros/tools/safeZ" M98 P"/macros/tools/wipe_tall" else G91 G1 X-60 F1800 G1 X-40 F6000 G90 ; enable fan if it was running M106 R2

Thanks. Works great. Was not working for me as I was on version 3.1
Works great on 3.5.1

Video of it working: https://www.youtube.com/watch?v=hMWtKxBUGBE

Thanks. Works great. Was not working for me as I was on version 3.1
Works great on 3.5.1

@gloomyandy

Correction, I had it backwards... I am using M203 to gradually increase speed. As I increase the speed, the resonant frequency increases on the X axis on a single X axis move. The Y resonant frequency remains the same at all speeds on y axis moves. amplitude varies with speed for both.

I also do not understand the entire logic behind the option of capturing data during or after the move. I have been mostly capturing during the move. If I capture data after the move, I only get significant peaks in the Y axis, with a minimal amount on X. It would be great if there were a more in-depth explanation of this feature.

I am also confused as to why the motion profile only allows input for negative to positive axis movement for each move, but not the reverse of that.

I have both a 1LC and a Scanning Probe board on my printhead, and both accelerometer readings are similar and consistent on all tests.

One of my main print resonance issues seems to stem mostly from stepper vibration (big AWD corexy). I am primarily concerned with finding an outer wall print speed that will minimize this resonance. My theory behind this was to find an axis feed rate that evokes the lowest amplitude of resonance on the accelerometer at a practical printing axis feed rate, and then also apply IS to the frequency as well. My printer evokes very little resonance at higher axis feed rates, but these speeds are not practical speeds for printing under all circumstances. This is where I found the resonant frequency on the X axis varying based on axis feed rate. Trying to utilize a practical axis feed rate to read accelerometer amplitude and compare with what I see visually seems like it could be of some benefit.

Perhaps I'm off in that thought process, but until the developers provide a more comprehensive explanation of how Duet IS and motion profiles work and how it can be practically applied... I have scoured the internet for weeks for any answers I can find and I am good at figuring things out. There are still many great unanswered IS questions in this forum and I find the explanation given on the Duet website not sufficient enough to fully understand it.

What would also be phenomenal is some sort of implementation for using accelerometer data to compare and check belt tension on corexy printers, similar to what Klipper uses.

@bernardomattiucci first problem is that your measurement tape is not a reliable reference. I had some with an error of up to 10% per centimeter. Get a high quality set of calipers.

@deckingman said in X and U axis move in when homing Y-axis:

e first move will set the homing flag, then you can use H0 or simply omit the H parameter for the second step where you move away from the endstop. So either G1 H0 Y-5 F3600 or

Thanks, done that and now it works

@gloomyandy thanks.
I waas hoping for a little better option, but if it is all that can be done this will have to do it 🙂

@T3P3Tony thx, this seems to work even when set to 40 hours, thx

M208 defines the length of the axis.

Your 0,0 point should be the front left corner of the bed where the nozzle can actually print. The M208 maximum is the farthest point from 0,0 that the axis can safely move the nozzle tip.

According to your config,g your endstops are on the low end of travel, so they should be on the left and front side of the plate.
-x moves should move to the left, +x to the right
-y moves should move to the front, +y to the back

If this is not the case, you need to sort that out first as that may be the root of the problem.

If this is accurate for your setup, and you want to measure the M208 min and max accurately, try this:

Send M564 H0 S0 to allow you to move the print head anywhere ignoring any limits. Be careful now as you can crash your print head.

Jog your nozzle to where you want 0,0 to be.
Send G92 X0 Y0 to set that point as 0,0
Send G1 H3 X-50 F300 to set the endstop trigger point as the m208 x axis minimum
Send G1 H3 Y-50 F300 to set the Y minimum

Now you can jog your print head to the maximum side of each axis until the nozzle is at the farthest usable point. Make note of the X and Y position.

Send M208 X### where ### is the position you noted for X
Do the same for Y with M208 Y###

Now send M208 by itself and the firmware will report the actual minimum and maximum positions of your bed size. Compare that to what you have in your config,g for M208.

; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X230 Y230 Z250 S0 ; set axis maxima

How does it compare?

My first thoughts would be mechanical, but please update to 3.5.1 as there were some issues with skipped steps occasionally, but this doesn't sound applicable to me.

Can you share some more information if the firmware update doesn't help? config.g and a sample gcode of your moves. Maybe some more detail of the hardware? Is 1A current sufficient for the motors?

When you solve this. please be sure to post what it was that worked.

@dc42 I see, and M30 as it is is probably originating from Marlin, right? Then i I guess they will stay both and it is up to the user to use them. Thank you!

@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

@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.

@Jered No problem! You could likely use the same technique, combined with the bed scanner, to get an even quicker read of just the print area before each print.

@usinjin

First off, I am no expert with tuning the 1HCLs. That being said I have been using them since they first came out.

I would drop your D value down to D0.1. That will immediately quiet them down, and I found it to have little impact on the performance.

I would also increase your P value. The auto tuning function tried setting my P value down in the 20-ish range like yours and I noticed very poor performance. Just for testing sake I would try a higher number like R100.

The other thing that might help is to post a picture of your tuning graph.