@jay_s_uk Wow I seriously have read over that 10 times I think. sorry for the unnessecary question
Thanks all!
Best posts made by SanderLPFRG
-
RE: On-device start gcode handling
-
RE: How do I use the filament sensor as a trigger for autoloading??
@OwenD I did exactly that yesterday late afternoon. It is working now.
; Custom buttons M950 J1 C"^io2.in" ; define logical input for E1 filamentsensor M581 P1 T2 S0 R2 ; define trigger for filament auto load (trigger2.g) M581 P1 T4 S1 R1 ; define trigger for filament runout (trigger4.g)
Thank you very much both!
-
RE: M291 S4+ commands not working on RRF 3.5beta2
@chrishamm It works!!
It both updated correctly, and now the M291 functions correctly.
Massive thanks Chris and Tony.I'll now work on trying to understand how I can use the input to trigger Gcode commands
-
RE: Cannot use M291 input as variable in loop
@OwenD Damn, this did the trick. Thank you so much owen! also thanks @chrishamm
Latest posts made by SanderLPFRG
-
array not setting correctly from variables.
Hi,
I want to use a macro to set probing boundaries and point spacing with the M557 command.
I am using the param.X function in macro's to create variables for Xmin, Xmax, Ymin and Ymax of the print area and set the point density.
However, if I try to put the parameters in the M557 command, I get the error;
"Error; in file macro line 81: M557: Wrong number of values in array, expected 2"The line I use to put the variables in the M557 command is;
M557 X{var.printxmin}:{var.printxmax} Y{var.printymin}:{var.printymax} P{var.pointsx}:{var.pointsy}
I have checked the variables with "echo var.printxmin" which it reports correctly.
Why doesn't it put the variables correctly in the arrays?
-
RE: On-device start gcode handling
@jay_s_uk Wow I seriously have read over that 10 times I think. sorry for the unnessecary question
Thanks all! -
RE: On-device start gcode handling
@jay_s_uk I have, but I do not see any issues. I have not used G, M, N, or T and I do not see a max specified
what do you mean exactly?
-
On-device start gcode handling
Hi all,
I am trying to handle all of the pre-printing gcode checks as well as starting sequences on-device.
To achieve this, I want to use the parameters sent with M98 which I set in the slicer.
Currently I have;
;Prusaslicer section; ; Define prusaslicer variables { local xmin = (max(print_bed_min[0], first_layer_print_min[0] - 20)); local xmax = (min(print_bed_max[0], first_layer_print_max[0] + 20)); local ymin = (max(print_bed_min[1], first_layer_print_min[1] - 20)); local ymax = (min(print_bed_max[1], first_layer_print_max[1] + 20)); } ; called with M98 P"0:/macros/print-start" M98 P"0:/macros/print-start"A{first_layer_temperature[0]} B{first_layer_temperature[1]} C{first_layer_bed_temperature[0]} D{xmin[0]} E{xmax[0]} F{ymin[0]} H{ymax[0]} I{initial_tool} J"{is_extruder_used[0]}" K"{is_extruder_used[1]}" L"{filament_type[0]}" O"{filament_type[1]}" P{nozzle_diameter[0]} Q{nozzle_diameter[1]}
And the duet macro will start with;
;Duet section ; Retrieve and define variables ; Temperature variables set var.lefttemp = param.A ; Extruder temperature set var.righttemp = param.B ; Extruder temperature set var.bed = param.C ; Bed temperature ; Print variables set var.printxmin = param.D ; Left boundry set var.printxmax = param.E ; Right boundry set var.printymin = param.F ; Front boundry set var.printymax = param.H ; Back boundry set var.purgelength = 15 ; Machine variables set var.initialtool = param.I ; initial tool set var.leftused = param.J ; is right tool used yes/no set var.rightused = param.K ; is right tool used yes/no set var.leftfilament = param.L ; loaded filament type left set var.rightfilament = param.O ; loaded filament type right set var.leftnozzlesize = param.P ; nozzle diameter left set var.rightnozzlesize = param.Q ; nozzle diameter right
After this I can use the variables to move and check the machine
However, if I test the macro by sending;
M98 P"0:/macros/variable-test-printstart" A215 B215 C0 D254.127 E333.118 F221.901 H278.099 I0 J"true" K"false" L"PLA" O"PLA" P0.4 Q0.4
I get the error
Error: in file variable-test-printstart line 34: in file macro line 0: unknown parameter 'P'
While the P parameter is clearly defined in the code.
Can anybody tell me why this is happening?
Testing macro is;
var lefttemp = 0 var righttemp = 0 var bed = 0 var printxmin = 0 var printxmax = 600 var printymin = 0 var printymax = 500 var purgelength = 0 var initialtool = 0 var leftused = "false" var rightused = "false" var leftfilament = "none" var rightfilament = "none" var leftnozzlesize = 0 var rightnozzlesize = 0 ; Temperature variables set var.lefttemp = param.A ; Extruder temperature set var.righttemp = param.B ; Extruder temperature set var.bed = param.C ; Bed temperature ; Print variables set var.printxmin = param.D ; Left boundry set var.printxmax = param.E ; Right boundry set var.printymin = param.F ; Front boundry set var.printymax = param.H ; Back boundry set var.purgelength = 15 ; Machine variables set var.initialtool = param.I ; initial tool set var.leftused = param.J ; is right tool used yes/no set var.rightused = param.K ; is right tool used yes/no set var.leftfilament = param.L ; loaded filament type left set var.rightfilament = param.O ; loaded filament type right set var.leftnozzlesize = param.P ; nozzle diameter left set var.rightnozzlesize = param.Q ; nozzle diameter right echo var.lefttemp echo var.righttemp echo var.bed echo var.printxmin echo var.printxmax echo var.printymin echo var.printymax echo var.purgelength echo var.initialtool echo var.leftused echo var.rightused echo var.leftfilament echo var.rightfilament echo var.leftnozzlesize echo var.rightnozzlesize
-
cutting 24V with Emergency stop in SBC mode
Hi,
I have a machine running Duet3 6HC+2 expansions in SBC mode with a raspberry pi4.
The pi is powered by 5V power supply and the duet runs on meanwell 24V. I now have an emergency stop working via the input button method, but I am afraid it will not surpass testing. Therefore I want the button to cut all 24V systems (motor, heaters and electronics) but I am afraid that it will cause damage to the firmware.
Does anybody know how DWC will react to 24V power cut??
-
RE: X and U axis move in when homing Y-axis
@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
-
RE: X and U axis move in when homing Y-axis
@dc42 Hi, Thank you for your reply. You have stated 2 times "G1 H2". do you mean I need to change it to G1 H1 for the Y to only move??
-
X and U axis move in when homing Y-axis
Hi All,
On a new prototype machine I am building, I am experiencing a weird issue regarding homing.
When homing Y, I first home X and U. Then when the Y axis homes it;
- moves towards the endstop, stops when triggered
- Moves 5mm back
- Moves towards the endstop at slower pace for second time.
Expected behavior is that only Y axis moves, but somehow the X and U axis both move inwards on step 2. In DWC, the positions remain the same however...
Homing macro;
if {move.axes[2].machinePosition < 5 || !move.axes[2].homed} G92 Z0 G0 Z5 ;endif M400 ;home y-axis to max G91 ; relative positioning G1 H1 Y{move.axes[1].max + 25} F3600 ; move quickly to Y axis endstop and stop there (first pass) G1 H2 Y-5 F3600 ; go back a few mm G1 H1 Y300 F600 ; move slowly to Y axis endstop once more (second pass) G90 ; absolute positioning
I am using version 3.5.0-rc.4, markforged kinematics
A second issue I am having is that my X axis sometimes moves past its endstop and keeps moving (thus grinding) instead of stopping. I see on the sensor that the signal changes (NC switch, reports open when triggered) and most of the time it does work flawlessly.. Any idea why this could happen?? (I already tried the pullup trick, no effect)
-
Troubles connecting LIS3DH accelerometer
Hi,
I am trying to connect the ADAfruit LIS3DH triple-axis accelerometer, but am having issues with the graphs.
X;
Y:
The X looks to be connected correctly (x line significantly higer than Y and Z. However, with the Y measurement, it is all over the place.
Have I connected something incorrectly? These graphs look terrible
-
RE: Can I use a USB accelerometer with 6HC mainboard?
@jay_s_uk Ohkee, thanks. Where can I find documentation on how to connect it?