@droftarts thanks, this will get me started. If I have a working solution I will post it here for anyone in the future.
Best posts made by daninet
-
RE: Orbiter filament sensor setup
-
RE: Inconsistent z-offset too high on new prints
@Phaedrux
i took the big gun, took apart the Z and checked manually for any mechanical error, there was none. restarted all the calibration for movement and now it seems to be ok. I have no idea what was the problem tho. I consider it solved. Thank you for your help. -
RE: If statement for macro trigger in RRF
I didnt know about this tool, it's cool. Makes this so much easier. Thanks
I think this is solved lets continue any discussion in the other topic: https://forum.duet3d.com/topic/34132/orbiter-filament-sensor-setup/9
Latest posts made by daninet
-
RE: Inconsistent z-offset too high on new prints
@Phaedrux
i took the big gun, took apart the Z and checked manually for any mechanical error, there was none. restarted all the calibration for movement and now it seems to be ok. I have no idea what was the problem tho. I consider it solved. Thank you for your help. -
RE: Inconsistent z-offset too high on new prints
@Phaedrux you mean mechanically? i didnt notice such a thing. When it gets going it works perfectly
-
Inconsistent z-offset too high on new prints
Hello!
I have a problem since some time. I thought I'm seasoned on 3d printer issues but this one got me.
Printer: blv mgn based custom core xy, I made a lot of part for it myself. It is running on duet2 wifiSymptom:
I'm leveling the bed on the 4 corners manually then starting a print. Even tho I have mesh bed leveling seemingly I still have to do it. Print goes ok. Printer turns off, I don't need the printer for a week.
I turn on the printer, need to print small stuff on the center so I skip the manual leveling. I have mesh leveling anyway. Mesh level goes down, print starts and it prints 2-3mm above the bed after successful mesh leveling. Huge margin of error. It is not the "height is slightly off" it literally prints in the air. The deviation in my 350mmx350mm bed is something like 0.7mm, even if my -i don't know- mesh axes are wrong the height difference is still too much.This is completely beyond me how can it happen because the bltouch measurements are consistent. It is an original one.
Best I can do is share as many settings and data with you as I can and please if anyone has any idea what is happening share it with me.config.g
sample gcode
homeall.g
mesh.g
imgur gallery with images and video -
New pause state
It would be nice if state.status returns different pause state for manual (including gcode pause) and pause initiated by error or filament sensor.
This would enable running special macros, for example unload the remaining filament when the filament sensor triggers during print and print is paused. Something that you might only want to do if you are in an error state. If this can be solved with the current reading of the pause state and I'm just missing something please let me know
-
RE: Orbiter filament sensor setup
@droftarts I need some brainstorming here.
I thought about it a lot and the following scenario is working while the printer is idle:idle && no filament -> press button to start loading filament
idle && filament present -> press button to start unloading filamentI think this is clear so far and working in the macro.
However there are two tricky situations need to be covered:- Print paused manually for filament change so filament is present but status is paused
- Filament runs out and print is paused
For case 1 we can use the original macro as filament is present, but I'm not sure how I could handle when print is paused with error. I have looked up all the available statuses and printer status is same when manually paused and when paused with error. I'm wondering what other parameter we could use this case to determine if the print was halted by error or manually.
-
RE: If statement for macro trigger in RRF
I didnt know about this tool, it's cool. Makes this so much easier. Thanks
I think this is solved lets continue any discussion in the other topic: https://forum.duet3d.com/topic/34132/orbiter-filament-sensor-setup/9
-
If statement for macro trigger in RRF
Hello,
I need help with syntax. I have duet 2 board with RRF.
I have a button that calls trigger2.g
So far this is ok.I have a filament runout sensor switch connected to zstop.
Depending on the state of the sensor I either want to start filament loading or filament unloading on button press triggering trigger2.g
The sensor is right at the extruder so it is a good indication of which gcode to start upon button press.M591 D0 returns this:
Simple filament sensor on pin !zstop, enabled, output low when no filament, filament present: yesHow is my if statement will look like?
if sensors.filamentMonitors[0].filamentPresent = true ;unload gcode else ;load gcode endif
Error: in file macro line 1 column 4: meta command: unknown value 'filamentPresent'
Thank you
-
RE: Orbiter filament sensor setup
@droftarts thanks, this will get me started. If I have a working solution I will post it here for anyone in the future.
-
RE: Orbiter filament sensor setup
@droftarts Ok I never thought of this. So:
I do something like this in a macro and call this in the trigger2.g:; Macro to check printer status and load filament or pause print M408 S0 P"status" ; Retrieve the status information ; Check the status response - I'm just assuming here the reply is printing or idle, needs to be checked IF {[state.status] = "printing"} M98 P"pause.g" ; Execute pause.g to pause print ELSEIF {[state.status] = "idle"} M98 P"loadfil.g" ; Execute loadfil.g to load filament ENDIF
Am I thinking about this the right way?
-
RE: Orbiter filament sensor setup
@droftarts this sounds like a possible workaround. How do I undefine a config entry in my start gcode?