Blender maybe, since it's more of a modeling program. Meshmixer is about as good as it gets for mesh manipulation though.

@CedricE said in Slicer-adjustment, script or something else?:

Hey,

thank you for your answers!

My next step is using 4 tact welding mode to fill the end crater at an end of the line. I thought to use a dwell time, but I think if I do it with the welding electric, I will get better quality.

And thats why I have to modify the g code 🙂

If you have other ideas, it would be wonderful to hear them!

Cedric

With regards to end craters, if you have a Fronius TPS3200 you can set a start and end current time.
Hold down the store key and press one of the arrows under the trigger selection LEDs.
Use the arrows to scroll through- start current, end current, start time, end time.
It's all in the manual (you've read the manual right? 😉
You should probably leave the trigger made to 2x
If you use then you must issue both a high and low signal at the start and end of each line.
Running 2x trigger mode will simplify things.
You will need to add a delay at the end of each line to ensure the torch stays in place until after both the end time and the post gas flow.
This could be done by a post processing script adding G4 S*

Alternatively you could add a robot interface and insert conditional g-code which checked for the process active signal going low before proceeding to the next line.
You'd still need post processing to do this and whilst you could then adjust settings on the welder without re-slicing, it's much more expensive.

@TurtlePrint
Great idea!
I had a touchscreen with full color running on the ESP32.
(digole was the brand).
Now add a camera to show the nozzles in closeup and some onscreen-buttons for babystepping etc. and we have a remote PanelDue.
I'd buy it, if Ihad several printers to run.

Under the heading of 'weird but makes sense' ....

I actually knew this from a long time ago but had forgotten 😞

I believe what is happening is as follows: Support prints up to and including the roof section (printed at 100% in my case), I then have two layers of a gap to allow separation of support from the print. I then print the first layer of the bottom of the model. This layer, in theory, would be a 100% dense layer if printed in the normal manner of a solid base and then the gap that is 'layer thickness' The nozzle flattens the deposited material to some extent. In my situation though there is a two layer gap in addition to the normal single layer gap the printer has calculated the plastic flow for. Between the support roof and the layer I am currently trying to print there is too big a gap. As a result, there is no flattening, the layer is printed as a round extrusion and loosely lays on the support roof. It can't form a solid surface because there isn't any squashing happening. Not only that, but I find that the next layer is also loosely laid down with maybe a bit of squashing but not sufficient for a 'solid' layer. It looks like the layer is printed at infill density because there are spaces between the round noodles that are laid down and not squashed flat.
The take away of this is that the only way to get a solid layer on top of support is if one uses an actual separation layer of different material that doesn't stick which then results in the model's first layer on top of the separation layer being laid down in a squished manner forming a solid layer.
Whoo, that was difficult to explain. Hopefully it makes sense.

I use a PizeroW with the Pi cam module and MotionOS to turn it into a webcam. It works very well with DWC and makes for a very small and very functional cam.

https://github.com/ccrisan/motioneyeos/wiki

Good guess ! forgot all about that ... let's see, the model is 76 mm by 76 mm. minimum layer time is 20 seconds. A layer is 76 *4 or 304 mm (round to 300) and at 15 mm/sec it is .... tadaaaa .... 20 seconds!

Right on !!!! Where do I send the prize for the right answer ?

Impressive and also most annoying that I must have spent an hour googling things, reading things and staring at the settings !:)

Thank you VERY much !

@PCR Gotcha. I'm printing PETG at modest speeds, but the smaller files are nice.

@MintyTrebor said in Duet to send emails?:

Hi @the_dragonlord, I'm the author of the NodeRed Mobile dashboard. Happy to help with any questions you have etc, but I thought it might be worthwhile explaining how it works, as it may not be the ideal candidate for the scenario you describe.

The NodeRed dashboard pulls information from the DSF http rest api at a pre-defined polling interval (5 secs by default). This is fine for status monitoring (temps etc), but not for event monitoring. If the event you wish to monitor happens in-between the polling interval, there is a significant probability that by the time the next polling is completed the event information has been cleared/overwritten by another event, which could result in missing the required event entirely.

Can I suggest you have a look at MQTT4DSF as an alternative. Amongst other things, it can monitor user specified events and send MQTT msgs when triggered. You can then use any rules engine (including NodeRed) to monitor for those MQTT msgs and trigger another set of actions (ie send an email).

Hope this helps.

Yes it helps! Thanks

how is this simpler or better than using curl and a 2 line script?

KISS PostProcessor command

script contains

RRF does not like spaces or punctualtion in filenames. I have not used DOS batch scripts on a long time, so the variable as filenames is touchy.

I REALLY wish Lonesock gets stuff together and gets 2.0 done soon.

@resam said in Timelapses, are they possible?:

--run-ffmpeg

IT WWWWWWOOOOORRRRKKKKKKSSSSSSSSSSSSSSSS!!!!!!! Great jon my friend, great job!!! Thanks a lot for everything!!!

ok, it works with the example print but not with mine....I've inserted the GCODE in the layer change but it doesn't take the pictures...tha GCODE works because when the layer changes I see the nozzle stopping for a while....I'm using Ideamaker as slicer....any idea?
EDIT:
It started to wokr after about 6-7 layers....they are not so small layers, it take about 30-40 secs each to complete

First try was not successfull. I can connect, commands will be sent due to the logs but no response. Will try to find out what happens.

BTW: I would like to use Octoprint for Mosaic Palette prints as long as there is no plugin for DWC.

@BoA said in Prusa Slicer 2.3alpha2 adds new G CODE flavor for RRF:

Finally G10 support?
I wonder what are the actual changes in this new g code flavor.

Details here: https://github.com/prusa3d/PrusaSlicer/pull/4553

@mendenmh Thanks you very much for your input. Appreciate that.

Regards,
Amit

Thanks for the info. I did not include in the readme all the nodes used in the "example" dashboard, just the nodes in the "Universal" dashboard. I have made it clearer in the readme.

Node-red-contrib-looptimer2 is a node available in palette manager and was used in the "universal" dashboard.

I have also updated the notes to reflect the changes required to use the updated API object model used in the recent beta firmware(s). Its just a simple path change, nothing major.

Edit: I have updated the Duet Dashboard Universal Flow:
Updated to show how to get all three types of status updates from API V1.
Included example of how to process Remaining Job Time
Added alternative Object Model API Paths for Firmwares V3.1+

@BlueDust yes but NO 😄