@Crash69 said in Indirect (bearing) laser filament monitor concept:
5x10x4 (mr105)
Hi everyone, I just published my interpretation for a Duet3D laser filament monitor enclosure. Use a rubber band and have moving parts.
https://www.thingiverse.com/thing:4147811
@zerspaner_gerd
No you are wrong, the method has changed. To get the same result as S-1 now you have to assign the trigger on the pin "nil"
feature request
would it be possible to implement the management of multiple states and multiple temperatures for the M568 command?
the idea would be to have
and state An for exemple:
I think they are the most used with a multitool setup.
It would be nice to have similar management for the bed as well.
@arno91
Hi , I use similar solution to load filament with MMU feeder and extruder in sync:
M574 V2 S1 P"duex.e6stop" ;
M400
M18 V E0:1:2:3:4 ; disable the axes/extruder to reassign
M584 V3:8 ; reassign them
M906 V800 ; set the motor currents
M350 V16 I1 ; set the microstepping
G92 V0
echo ">reassigned motor"
M98 P"/sys/SERVO/ON.g" ;engage MMU
G1 H4 V1000 F500 ;load to extruder endstop
M98 P"/sys/SERVO/OFF.g" ;disengage MMU
M400
M18 V0:1 ; disable the axes/extruder to reassign
M584 V8 ;
M906 V1400 E1000 ; set the motor currents
M913 E80
M350 V16 E16 I1
G92 V0
I take this opportunity to ask a question @dc42
in my config.g I have:
M584 X0 Y1 Z2:9 E3:3:3:3:3 U4 V8 P5
[...]
M563 P0 S"E1 " D0 H1 F2 ; Define tool 0 P=tool number, D=driver number, H=heather, F= fan
M563 P1 S"E2 " D1 H1 F2 ; Define tool 1
M563 P2 S"E3 " D2 H1 F2 ; Define tool 2
M563 P3 S"E4 " D3 H1 F2 ; Define tool 3
M563 P4 S"E5 " D4 H1 F2 ; Define tool 4
[...]
and the macro executed in the tool change has the code I posted above, I do not reassign the stepper drives to the E axis (no "M584 Ex" other then the one in config.g). Given that the procedure works right now, there is something wrong that could give me problems perhaps following updates of the firmware?
@pfn
I have three macros:
you could enter in tpostmaster:
M98 P "ercf / lib / load-tool.g" T{state.currentTool}
as far as temperatures are concerned, I manage them with 6 global variables:
global ToolF; first layer temperature tool
global ToolC; temperature toolchange
global ToolT; first layer temperature tool
global ToolS; standby temperature
global bedH; first layer bed temperature
global bedB; temperature bed
these variables are set by "/ filaments / <filament-name> /config.g", where I can possibly also insert pressureadvance and more, the template I use is
0:/filaments/ABS/config.g
;-----------------------------------
var firstlayertemp=240
var layertemp=235
var standbytemp=180
var toolchangetemp=234
var firstlayerbed=103
var layerbed=95
;-----------------------------------
set global.toolF=var.firstlayertemp
set global.toolT=var.layertemp
set global.toolS=var.standbytemp
set global.toolC=var.toolchangetemp
if global.isfirstBedHeat && global.setBed
set global.bedH=var.firstlayerbed
set global.bedB=var.layerbed
set global.isfirstBedHeat=false
i don't need load.g and unload.g of the filament
the temperature of the tool and of the bed is set by a macro that I inserted in the start gicode of the slicer and at the tool change. In superslicer I put this:
;Start G-code
M83
set global.slicer=3
set global.layercount=0
{if wipe_tower}set global.slicerwipe=true{endif}{if !wipe_tower}set global.slicerwipe=false{endif};wipetower
T[current_extruder]
M703
M98 P"/sys/DEFAULTS/heatup.g"
M116
;end start
;BEFORE_LAYER_CHANGE
G92 E0.0
{if layer_num>0}set global.layercount=[layer_num]{endif}
;[layer_z]
;AFTER_LAYER_CHANGE
;SET LAYER COUNT
{if layer_num<2}{if layer_num>0}M98 P"/sys/DEFAULTS/heatup.g"{endif}{endif}
;TOOL CHANGE G-CODE
T[next_extruder]
for CURA I have to initialize the global.layercount to -1 in the start and then pass in post processing script:
set global.layercount = {global.layercount + 1}
of course you have to set ALL the temperatures of ALL the materials to 0 in superslicer to let the printer manage everything!
in this way and setting the tools in config.g with:
M584 X0 Y1 Z2:9 E3:3:3:3:3 U4 V8 P5
M563 P0 S"E1 " D0 H1 F2 ; Define tool 0 P=tool number, D=driver number, H=heather, F= fan
M563 P1 S"E2 " D1 H1 F2 ; Define tool 1
M563 P2 S"E3 " D2 H1 F2 ; Define tool 2
M563 P3 S"E4 " D3 H1 F2 ; Define tool 3
M563 P4 S"E5 " D4 H1 F2 ; Define tool 4
;M563 P99 S"SUPPORT" D5 H2 F2 ; Define tool 99
I can have the materials assigned to each tool and with a flag variable that disables the execution of the tool change macros outside of printing I can change the material from the web interface to any tool (obviously not for the one currently loaded, for that I disable the flag to physically perform the unloading and loading).
in start.g the tool actually loaded is always selected.
the slicer only deals with the management of the fans as they are strictly linked to the gcode and the material, I don't think it can be left to the firmware to manage it ...
my only current problem is that when i change filament with ATX off the printer tries to heat the tool and i have a temp fault, i could not understand where i went wrong as the heater should stay off, as soon as i have time i investigate, for now it is a manageable problem.
I use a similar approach, I scan at varous temp and with different plate(steel and glass),with a complex bed.g called by G32.
I put this control in homez.g and do it after bed temp settled .
in orca start I have M190 followed by G28.
....
if {fileexists(floor(heat.heaters[0].active)^var.plate^".csv")}
var map={(floor(heat.heaters[0].active)^var.plate^".csv")}
if var.verbose
echo "load "^var.map;
G29 S1 P{var.map};
else ;
if var.verbose
echo "no file .csv! load heightmap.csv"
G29 S1;
windows detect a virus in it
@droftarts I have the same behavior, I have RGBW LEDs, set with M950 E1 C"duex.pwm5" T2
@gloomyandy It worked on 3.4.6, could not try downgrade at the moment, too many changes to do
@droftarts Yes, it worked fine. BTW no a great issue, if set blue I have cyan....
@droftarts On duex.pwm5 I should have 5v from external source, I have atx 5v rail connected on "EXT 5v" and "5v AUX" jumper is on "5v ext", while the strip on CONN_LCD have signal on a 74HCT08.
@gloomyandy Nope
I try from 3200000 to 2000000, also 1600000 and 8000, 800 500 just to try, green is always on everytime i send an M150. Maybe an hardware foult of my duet? on
M950 E1 C"duex.pwm5" T2
is same same .
@danzaywer default frequency should be 3000000Hz ?
M950 E0
NeoPixel_RGBW strip on port "(connlcd.np,connlcd.db7,connlcd.5)" uses bit-banging, frequency 2500000Hz, max strip length 3