@tekstyle said in force cancel print after a M190 P0 S60 command?:

sometimes, I mess up and forget things the moment i started a print and I need to cancel it altogether. the only problem is it won't let me interrupt the bed heating up to target temperature.

This is already on my list to fix in RRF 3.5.

@dc42 It's working! The sensorless homing does indeed work for the extruders as suggested. Thanks again for the support. 😄

NVM I'm using Macros to set Flags for Nozzle size and Hotendtype and conditional Gcodes in the filament config.
I think it's more intuitive I can rename the Printer with

M550 P"Apex Pedator 0.4 HF PETG"

to make sure the correct settings are loaded

@tristanryerparke we have plans to implement feed hold in a future version of RRF, and that would also facilitate pausing quickly regardless of the jerk. It's pencilled in for release 3.5 but as 3.5 is already late it may have to wait for 3.6.

@MaxGyver
+1
this could also be handy for laser engraving with a rotary tool. I want to try 2.5D-lasercutting once.

@T3P3Tony Thanks, I have run M92 to define step/degree, speed, and acceleration.

On the hardware side i've used following parts:

a Raspberry Pi Pico Waveshare 1.3 inch OLED, https://www.waveshare.com/wiki/Pico-OLED-1.3 two small diodes (1N4148)

Optional parts for the housing:

housing, PicoGehäuse.STL TPU front cover, DeckelFolie4.STL TPU cable outlet, KabeldurchfPicoAssy.STL

TachoMod.jpg
Sorry, the photo is not very sharp! And i know, the "S" on the TPU front cover is "upside down"...

The wiring remains like in my post from 13.9.22 except that i have inserted the 2 diodes in the signal lines. Also there is no need to set the "input bits" because we have a menu for changing the settings.

The TachoMod starts automatically when an input signal is detected. After start, it shows the period duration and the rpm of the incoming(top) and outgoing signals(bottom). see photo above

With the "S" button you can enter the menu (only possible when no input signals are detected), the "+" button increments values in the menu.
The following settings are implemented:

Multiply/Divide Mode: “/” or “x” ; Makes output faster or slower compared to input signal Factor (multiply or divide): 1-16 Delay time: 1-9999ms ; after which time without inputsignal the output will be switched off Pulse per revolution: 1-16 (normally 2) ; for calculating the correct rpm values

All settings will be stored automatically to onboard flash memory after leaving the menu.

And here is the source code of TachoMod_V4.0, written in microPython with ThonnyIDE.
TachoMod_V4_0.py
The code will be far away from "perfect", but it works.
And it was a really nice project for my first steps with a Raspberry Pico and the programming language Python.

I hope this description is more or less understandable and sorry for my bad english...😰

@Wulfsta you can do this already if you configure the slicer to call a layer change macro on every layer change.

@dc42 did you look in to the frame part. ? (bounds)

@dc42 posted as issue #276, thanks for your efforts on support and continued development

@phaedrux would be nice if when you used the define mesh parameters. that you could choose number of points. and not just spacing

59d9546c-972f-410b-84c0-d42f26cc75d3-image.png

@dc42 said in Support for Thumbnails at End of File:

@ccs86 PrusaSlicer generates them at the start of the file, so that's where RRF looks for them.

SuperSlicer allows them at the end:

81fd28e2-2be0-4609-842a-ac8c396e5854-image.png

Example file:
CordEase3 x6.gcode

@jan12345 thanks, should be fixed now.

@niocio01 unfortunately, Neopixel strings don't support setting just some colours. So you need to send the commands for all the LEDs that you want to change. You can either write a macro that computes and writes the correct colours for all 4 tools and call that every time the status of a tool changes, or you could use global variables to record the correct colour for each tool so that you don't need to recompute it each time.

Hey @deckingman,

I don't get why you can't just use a macro [...]

Some examples:

My printers have CPAP blowers+ Motor-valves instead of fans.
In order to control the valves, I would need to change the slicers post processor or use the search and replace function (if the slicer supports it) to add my custom code. While this works for files being printed from SD, I can't adjust the airflow from the web interface using the fan control sliders or just call M106 from the console. So basically the standard Gcode to control the Fans does not work for my setup.

Similar with M3:
Of course, I can write a macro, let's say M3.1.g and change the CNC-Mill-post processor, to call the macro instead of the standard M3 code. But again, If I start the spindle from the web interface the standard code is called instead of my M3.1.g

The proposed logic would be as follows:

if Standard Gcode (like M3) is called
->check if a macro file with the same name (M3.g) is present
--> If yes, call this macro instead.
else
->continue with the standard Gcode (M3)

@deckingman said in Why are "custom GCodes" only for non implemended GCodes?:

You can't call/use M3 from within the macro because you've changed the behaviour such that it will check the door and move the Z axis which will just end up with a recursive call.

And that's where I absolutely agree. My logic only works if the standard Gcode that has called the macro is not included in the macro itself. For me, this would already solve a lot of problems...But Okay.

So we would need to find a way to prevent the recursive calling. One idea would be to execute the standard M3 code directly If it is being called from a macro file, without checking for custom Gcode files beforehand. And If M3 is called from slicer file or web interface or console do the check for a custom Gcode file in sys first and if it is present call it instead.

As an alternative, we could leave the standard codes like M3 untouched but add something like pre.M3.g and post.M3.g where we can add everything that should happen before and/or after the standard M3 call.

I hope this clears things up a little
Cheers
Max