Topics created by daninet

@daninet You are unlikely to have anything connected to CONN_LCD (unless you're running a 12864 display), so it won't be a problem using that, it's outputs for drivers are the same as the expansion header. The BTT board will just save you a bit of wiring.

Ian

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

@daninet filament sensor and other errors already raise error events, see https://docs.duet3d.com/en/User_manual/RepRapFirmware/Events -- these can be handled in their own macros.

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

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.

@droftarts
This must be some different issue.
I have ordered a new adafruit accelerometer, soldered the cables and connected it to the board.
Same thing, "accelerometer not found"
Ok, then it might be the cabling, right?
I have cut a set of absolutely short cable, the shortest length that can reach the hotend from the board.
I have connected my original accelerometer to it and the results are the same. As the photo below shows the blue wire is the CS separated away from the rest of the cables and the accelerometer temporary held there with a clamp. The other accelerometer is the adafruit one I have tried earlier.
So for me it seems it is not an issue with the accelerometer, not an issue with the cabling.. so what remains? I have no idea.
For the record: I have continuity tested all cables multiple time, I myself put the dupont connectors on the cable and have verified they make contact and have used the pinout diagram on the docs to verify the cabling order many times.
This is my full config: pastebin
MVIMG_20230527_095026_2.jpg

The X,Y drivers should actually be called A,B, to avoid confusion with Cartesian kinematic.

2b75e0fe-c671-4928-9bca-5bfe0c7fec1e-image.png

@daninet thanks, I'll mark this as solved then.