Marlin: [BUG] (Mesh bed doesn't work with dual-x. )

[Ziyayildizz3]

Mesh bed doesn't work with dual-x. I have this question for a long time. Could you help?

This marlin error. With Marlin 1.1.6, mesh-Bed works smoothly. When I say table level in the new version, the axes go home and do nothing. I have been using the prayer-x system for a long time.

There are two independent x-axes. The two nozzle levels are the same. After X1 prints, it parks and X2 exits. Works seamlessly with Marlin 1.1.6 Mesh-bed.

[Ziyayildizz3]

The settings I use are;

Dualx-Mesh Eror.zip

[AnHardt]

There is absolutely no way how this could work.
If one nozzle is in a valley and the other on a hill - what should the system do? Ram one nozzle into the hill?

[Ziyayildizz3]

This marlin error. With Marlin 1.1.6, mesh-Bed works smoothly. When I say table level in the new version, the axes go home and do nothing. I have been using the prayer-x system for a long time.

[Ziyayildizz3]

Bunun nasıl çalışabileceğinin kesinlikle bir yolu yok.
Bir meme bir vadide, diğeri bir tepede ise - sistem ne yapmalıdır? Tepeye bir meme mi koydun?

There are two independent x-axes. The two nozzle levels are the same. After X1 prints, it parks and X2 exits. Works seamlessly with Marlin 1.1.6 Mesh-bed.

[boelle]

dont use marlin 1.1.6 use bugfix-2.0.x branch

[qwewer0]

@boelle The configuration files that @Ziyayildizz3 provided shows that the problem is with the Bugfix-2.0.x, but it worked/works fine on Marlin 1.1.6.

CONFIGURATION_H_VERSION 020006
CONFIGURATION_ADV_H_VERSION 020006

[Ziyayildizz3]

@qwewer0 Absolutely. This problem has existed for a long time. I have forwarded several times but the error raparu has been removed.

[thinkyhead]

Whenever there are homing or leveling issues, we now ask everyone to follow a standard procedure to gather more information so that we're not just taking stabs in the dark. Here is the boilerplate:

• Download Marlin bugfix-2.0.x to test with the latest code.
• Enable DEBUG_LEVELING_FEATURE and M114_DETAIL and re-flash the firmware.
• Connect to your printer from host software such as Cura, Printrun or Repetier Host.
• Send M502 and M500 to ensure your Configurations are applied.
• Issue the command M111 S247 to enable maximum logging.
• Perform a G28 to do your standard homing procedure.
• Do a G29 S1 followed by G29 S2 to probe the bed. This will also enable bed leveling.
• Do some of the moves that revealed problems before. Take notes.
• Copy the log output into a .TXT file and attach it to your next reply.

Repeat this procedure, if needed, to demonstrate inconsistencies. From these logs we should hopefully get a better idea of what's going on with your machine.

[thinkyhead]

In addition to the above, please move the nozzle to some spots around the bed and send M114 D to get a report of how leveling is being applied at that position. That should give some idea how Marlin is calculating offsets at different positions.

[thinkyhead]

And a note to Triage people: Pay attention to the issue and don't just post automatic responses. I'm a bit embarrassed how poorly this issue has been addressed. Watch me carefully for the right way to follow up on issues.

[thinkyhead]

While I'm waiting for Ziya to come back with some logs, I will be looking through the mesh leveling code to see if anything obvious jumps out at me, and to see where I might want to add logging or ask new questions to fill in our knowledge gaps.

[thinkyhead]

One of the steps needs more detail for MESH_BED_LEVELING…

• Do a G29 S1 followed by G29 S2 to probe the bed. This will also enable bed leveling.

[Ziyayildizz3]

@thinkyhead Thankyou. I tried to shoot the problem with the video. I will try what you say and give feedback.
https://www.dosya.tc/server29/eds4yg/IMG_3357.zip.html

[thinkyhead]

I don't need video, thanks. I already believe the problem exists.

[Ziyayildizz3]

Thank you for your kind reply and interest. I will collect the data following the instructions and forward them to you.

[InsanityAutomation]

Ive got an idex machine with a probe, I can run a test on it this weekend if nothing comes back before then.

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.