@droftarts thanks, this will get me started. If I have a working solution I will post it here for anyone in the future.

@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.

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

@droftarts thanks for the last link I didnt see it. Connecting some break out boards to the expansion header is really viable option for me that is not messing with my existing setup. I will go that way.

@droftarts thank you for your answer. Considering the friendly price of the BTT expansion module it seems like a good option. Am I losing the paneldue on my printer if I choose this?

Hi,
i have built a fully custom core xy machine with duet 2. It is the style of core xy printer where the bed moves down (not like on the voron where the printhead moves up).
This printer is built with a big 350x350mm build plate of thick machined aluminium. Currently I'm using two steppers with lead screws for the Z but it is extremely hard on the screws because of the weight. I need to convert it to a quad Z and I want to do that type of fixture when the bed is just resting on 4 pivot points.
my issue is the additional 2 steppers, the duet2 currently is maxed out. If I buy an expansion board for the duet can I still use the unused pins for things like buttons and other gpio? I have a lot of stuff connected to my expansion header at the moment and I dont fully understand how the expansion board works. I need 2 extra steppers and another 5ish gpio for my trinkets around the printer.

@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.

@Phaedrux you mean mechanically? i didnt notice such a thing. When it gets going it works perfectly

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 wifi

Symptom:
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

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

@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 filament

I think this is clear so far and working in the macro.
However there are two tricky situations need to be covered:

1. Print paused manually for filament change so filament is present but status is paused
2. 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.

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

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: yes

How 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