Posts made by Mike 1

Hello everyone,
I had to repace a heater and thermistor due to hardware damage. I use Firmware V3.5.2 and a daughter board (the preowner istalled it).
I replaced it with with one of these:
https://de.aliexpress.com/item/1005005184402518.html?spm=a2g0o.productlist.main.3.6d466f71pClAx0&algo_pvid=6893930b-ce51-4a3b-98a4-3f1ea3fd9b95&algo_exp_id=6893930b-ce51-4a3b-98a4-3f1ea3fd9b95-1&pdp_npi=4%40dis!EUR!35.10!32.29!!!36.65!33.72!%40210307c417196022385586113e4228!12000032636459190!sea!DE!0!AB&curPageLogUid=wke0dKaezosk&utparam-url=scene%3Asearch|query_from%3A
After switching it on, the display showed 2000C. Now I disasseblemd it and used a PT100. Still 2000C
Here is the code from the config file that used to work:

; Heater2
M308 S2 P"spi.cs1" Y"rtd-max31865" A"T1" ; create sensor number 2 as a PT100 sensor in the second position on the Duet 2 daughterboard connector
;M308 S2 P"e1temp" Y"thermistor" A"T1" T100000 B4725 C7.06e-8 ; Set thermistor
M950 H2 C"e1heat" T2 ; Extruder 0 heater
M143 H2 S300

Did I kill the board or is there a fix? I could use the PT100 in the future.

Thanks!
Mike

@stuartofmt Maybee that would be an option. Use the information from the filament sensor and pressure to calculate the real flow in time.

@deckingman That's right. Some special hardware ist needed. Maybee you can gain some information from the motor currents or a more clever filament sensor would be an option. I just love open source and hope it will stay for a long time.

I fond this article and would really appreicate if suche a feature would be implemented to improve print quality and stay cometitive withs B....

https://link.springer.com/article/10.1007/s40192-024-00350-w#Fig5

Happy printing
Mike!

@T3P3Tony said in Muti tool setup:

echo state.currentTool

I am currently away from the printer and made a remote test. Seams to work right now.

Do only have this Warning:
Warning: Obsolete use of S parameter on G1 command. Use H parameter instead.

Will test it with "echo state.currentTool" and come back on eastern.

Thanks!

Mike

Hello,

I do have a E3d Toolchanger with firmware version 3.4x and have the issue that picking up the tool does not work with first job and first tool. This is so because it is missing in the gcode.

I tried to fix it with this custom code:
if state.currentTool = -1 ;check if a tool selected code added because slicer does not select T0 at the very beginning
T0

The second job makes problemes and starts without a tool. scrating the end stop over the printing surface. I end job with the following code:
G91
G1 Z2 F1000 ;Drop Bed
G90
T-1 ;Drop off the tool
G1 X20 Y200 F50000 ;Park
M0 ;turn off all heaters

Thanks for your help!
Mike

That would be great. There is so much to calibrate with different materials etc.. So having something to support it would be great!

@OwenD

I am using a 0.6mm steel nozzle and it has some issues with thermal conductivity (small parts are fine, big parts need a higher temperature 265°C + x for PETG with the risk of burend material) so I am thinking about going back to 0.4mm as these have much less issues and slicers have problems with differernt diameters at the same time. The alternative would be a CHT like nozzle. I have to think about it.

M207 might be a good idea.
I am struggeling with ability to use absolute and relative values for the extruder in the gcode.
I don't know how the gcode interferes with M207. Issue is the time from the wiping station to the printig object. So the correct way to do, would be to bring the prinhead back to its position and then unretract. But one part is driven by the printer and one by the gcode.

Unfortunately I will leave my printer behind for a few weeks on Thuesday again.
If you have a good idea to fix it, I would really appreciate it. But I am short in time and will have to make a break .

Thanks!!!

@OwenD

Now it working fine.
I have a varible in start.g for the used filament.
tpost.g updates the variable for the used filament for each toolchange
wipe.g is executed by gcode
brush.g starts the cleaning process

start.g
tpost0.g
wipe.g
tbrush0.g

But oozing is an issue now. Can I reduce the amont of filament for M101?

if {heat.heaters[1].current > heat.heaters[1].active - 5} && {heat.heaters[1].current > 150};min temperature to work
M103
M400
;brush in
G1 X331.3 Y150 F50000
G1 X331.3 Y100 F50000
G1 X331.3 Y170 F50000
G1 X331.3 Y100 F50000
G1 X331.3 Y170 F50000
G1 X331.3 Y100 F50000
M400
M101
else
echo "temperature too low to brush"

@OwenD

Oh sorry, I was out for a while.

It is working with move.extruders[0].rawPosition. As I do have 4 extruders is there an easy way to replace the 0 by the number of the active extruder?

I am thinking about replacing global.wipesDone by a global.raw position. Then I would give it the current value in the brush.g and check the difference move.extruders[0].rawPosition-global.raw > x and control the process by this.

Brushing works fine Thanks!

@OwenD
Now I added two new files in system folder, but it is not working.

start.g
wipe.g

Wipe is executed and I get "wipe.g finished" as a feedback.

@deckingman
A silicone sock is in use. I made some tests with PTFE coated nozzles. I used them up to 240°C. That did not fix all my issues. Did you test PETG?

@OwenD
That looks fine in my eyes. Maybee some issues when changing the extruder. I will test it on Thuesday. Thanx!

@OwenD said in Wiping an purging control:

I don't really understand why using relative is an issue

Maybee I am wrong with my understanding how it works. I want to to make a wipe operation after x mm of processed filament triggerd by layer change. Adding the extruded filament for each line of gcodes does not seam to be possible for me. So I need some kind of absolute value.

@deckingman
I dislike the relative mode because the infomation about the used filament is lost.

@OwenD
The code is already in a macro. But it should cause issues when printing once relative and once absolut gcode. Is there a command to detect the printers status to return to the same mode after wiping? Then I could use M82 in a condtional case. How can I trigger that x mm filament have been printed in relative mode?

Hello,
I use an E3D toolchanger RFF 3.45 and have issues with filament on the nozzle after printing bigger surfaces and of course ozzing and as a result an empty nozzle after toolchanges.

-A wiping tower is in my eyes the best way to have a perfect start for a new tool. Superslicer requires relative mode for the extruder and does not accept different nozzle diameters.
-Wiping with a brush triggerd by layer change controled by extruded filament fails du to relative extruder mode
-Simple retracts and unretracts cause some issus with ozzing (excat timing)

Has someone a good idea what to do?

@dc42 Thanks! Issue can be closed

Hello,

I am using a E3D toolchanger with 4 individual printheads. FW 3.45

The first line of my macro to brush the nozzel for heater 1 is not working.
I want to make sure, that the printheads temperture is high enough.
I get the attached error message.

if {heat.heater[1].current > heat.heaters[1].active - 5} && {heat.heater[1].current > 150};min temperature to work
M400
;brush in
G1 X331.3 Y150 F50000
G1 X331.3 Y100 F50000
G1 X331.3 Y170 F50000
G1 X331.3 Y100 F50000
G1 X331.3 Y170 F50000
G1 X331.3 Y100 F50000
M400
else
echo "tenmp to low to brush"

T0
Error: in file macro line 1 column 5: meta command: unknown value 'heater^.current'

What is my mistake?
Thanks!

@gloomyandy
Thanx!

Topic can be closed