@dc42 So I can't for the life of me get this thing to read consistently and within any sort of reasonable tolerance. This is the output of ~25 G30 S-1 up 5mm as the commissioning tutorial runs just repeated with a one second delay between movements. Seems all over the place. The sensitivity settings are at the bottom to keep track of what tests I'm running.
5/21/2022, 3:35:51 PM Stopped at height -0.370 mm
5/21/2022, 3:35:48 PM Stopped at height -0.460 mm
5/21/2022, 3:35:45 PM Stopped at height -0.599 mm
5/21/2022, 3:35:42 PM Stopped at height -0.688 mm
5/21/2022, 3:35:38 PM Stopped at height -0.451 mm
5/21/2022, 3:35:36 PM Stopped at height -0.641 mm
5/21/2022, 3:35:32 PM Stopped at height -0.688 mm
5/21/2022, 3:35:29 PM Stopped at height -0.634 mm
5/21/2022, 3:35:26 PM Stopped at height -0.641 mm
5/21/2022, 3:35:23 PM Stopped at height -0.671 mm
5/21/2022, 3:35:20 PM Stopped at height -0.630 mm
5/21/2022, 3:35:17 PM Stopped at height -0.474 mm
5/21/2022, 3:35:14 PM Stopped at height -0.541 mm
5/21/2022, 3:35:11 PM Stopped at height -0.623 mm
5/21/2022, 3:35:08 PM Stopped at height -0.670 mm
5/21/2022, 3:35:05 PM Stopped at height -0.715 mm
5/21/2022, 3:35:02 PM Stopped at height -0.617 mm
5/21/2022, 3:34:58 PM Stopped at height -0.677 mm
5/21/2022, 3:34:56 PM Stopped at height -0.676 mm
5/21/2022, 3:34:52 PM Stopped at height -0.632 mm
5/21/2022, 3:34:49 PM Stopped at height -0.640 mm
5/21/2022, 3:34:46 PM Stopped at height -0.814 mm
5/21/2022, 3:34:43 PM Stopped at height -0.455 mm
5/21/2022, 3:34:40 PM Stopped at height -0.374 mm
5/21/2022, 3:34:37 PM M98 P"0:/macros/Z_Tuning/8_Repeatability"
Stopped at height -0.572 mm
5/21/2022, 3:34:31 PM M672 S105:20:235
5/21/2022, 3:34:30 PM M558 P8 R0.4 F1000 C"zprobe.in+zprobe.mod" H5 A3 S0.15 T10000;
@cossack if its a moving bed, when its at the back and triggering the endstop, that should be set to be the axis minima not the maxima, so your endstop setup wrong in M574 (Y1 not Y2).
When you jog the Y axis in the positive it should come towards you and away from you when jogging negatively.
You'll also need to adjust your homey and homeall to flip the home direction (and probably change your motor direction too)
my bad for not stating things correctly, within a few mm, i had configured the positions of the belts that raise/lower the Z axis as defined at https://docs.duet3d.com/User_manual/Reference/Gcodes, which are outside of the bed coordinates. for a Voron2.4 printer.
T0 at the end of G-config helped. You can control the filament in the Extrusion Control window.
Changing the browser to Edge eliminated the problem with viewing the temperature. Thank you for your help.
using M591manually definitely doesn't realize full potential of MFM
D'accord. The MFM, encased and mounted properly, is a tool I don't want to miss, and yes, putting the data into a chart can help to better spot some problems. But then, I want it to reside in vicinity of the DWC temperature charts, and on top, I would like to see an additional graph with the power consumption of the extruder stepper: this would give us the full picture.
"Homing issue"= going randomly to the incorrect side
S1 current 200mA issue homing
S1 current 400mA issue homing
S1 current 500mA homing ok ( have my doubts on this value being ok)
S1 current 600mA issue homing
S5 current 200mA issue homing
S5 current 400mA homing ok ( have my doubts on this value being ok)
S5 current 500mA issue homing
S10 current 200mA issue homing
S10 current 400mA homing ok ( have my doubts on this value being ok)
S10 current 500mA issue homing
S15 current 200mA issue homing
S15 current 400mA homing ok ( have my doubts on this value being ok)
S15 current 500mA issue homing
s20 current 200mA issue homing
s20 current 400mA homing ok ( have my doubts on this value being ok)
s20 current 500mA issue homing
s20 current 600mA issue homing
s30 current 200mA issue homing
s30 current 400mA homing ok
s30 current 500mA issue homing
s30 current 1000mA homing ok
spent most of the Day testing values above, i still have the issue that the "emergency stop " button seems to toggle the homing direction, also tried changing Jerk to see if that would make any difference (800 and 400)
another observation if i Home X and it goes in the correct direction , then the stepper motors time out, (M84 X Y S20) and i home X again it also goes in the wrong direction.
@Tinchus, you also asked about a repository of useful macros. I believe there is one somewhere, but there are also some in the Cgode meta commands section of this forum.
I can share a couple of things I've been working on.
First is a reference of code snippits I've been building up as I figure things out.
; BUILD A FILENAME
;var outfile = "0:/macros/data/"^+state.time^".csv" ; This is the current time in seconds since the datum, a good unique filename
echo "current time ", state.time ; in readable format
echo "current time ", +state.time, " in seconds since the datum" ; in seconds since the datum
echo "Uptime ", state.upTime, "seconds"
echo "millisecond fraction of up time, in msec = ", state.msUpTime
echo "Uptime to the msec ", mod(+state.upTime,10000) + state.msUpTime/1000 , "sec"
echo "Uptime to the msec ", state.upTime + state.msUpTime/1000 , "sec"
;To time an event less than 2/77 hours (9999sec) long:
var start_time = mod(+state.upTime,10000) + state.msUpTime/1000
G4 P125 ; pause for 125 msec ; This line for testing, replace with your event to be times.
var end_time = mod(+state.upTime,10000) + state.msUpTime/1000
var delta_t = var.end_time - var.start_time
if var.delta_t < 0 ; this IF /ELSE is needed because of the mod function use in capturing the time.
set var.delta_t = 10000+var.delta_t
echo "elapsed time = ", var.delta_t, "sec"
I also have some macros I've written and would be happy to share
Z_probe _evaluation - Evaluate the repeatability of probe measurement in one location after a short move in a random direction and and return to the original place. You can set X and Y location and the number of times to repeat the probing. All data is written to a csv file.
Clear logfile - clears the logfile
line-maker.g - make a move of a specified distance in a specified direction at a specified sped and return to the starting point. repeat a specified number of times. Used to checkout odd behaviors or sounds on particular moves.
OK_CANCEL_checker.g - Collect user input during macro execution. This is a short macro Intended as a macro to be called from another macro. Posts an M291 blocking message. You pass it a parameter that becomes the message posted in the M291. Something like "select OK for option 1, or CANCEL for option 2" When the user responds a global variable called global.OK_CANCEL is set to either "OK" or "CANCEL". Then the calling macro can interpret the global variable and infer the user input. As far as I can tell, this is the best user input there is that works with both DWC and PanelDu.
Lots of other macros that are simple one liners like "move without homing", "clear heater fault", "allow cold extrude". These are useful when interfacing with teh PanelDue and when you can remember those darn gcodes.
@baenwort Awesome! When I downloaded it last week, 4.13 was the latest, but I'll grab this and see what it can do. Sounds like it is exactly what is needed for this issue, thanks!
Now I just have to get this spool feeder working reliably. For some reason the stepper is randomly turning on and I can't trace the problem down. I don't want to come in in the morning and find a 10kg unspooled mess.