search

derhopp / Marlin-with-Anycubic-i3-Mega-TFT

Fork Marlin Firmware to support the Anycubic i3 Mega TFT
GNU General Public License v3.0
101 stars 40 forks source link

Any plans to update to newest bugfix branch? #14

Closed Murloc992 closed 5 years ago

Murloc992 commented 6 years ago

Hello, as the issue title states are there any plans to update to the newest 1.1.x bugfix branch of marlin?

derhopp commented 6 years ago

Yes I am planning to do so… but it is quite bunch of work doing that.

On 7. Jul 2018, at 15:01, Andrius Tarasovas notifications@github.com wrote:

Hello, as the issue title states are there any plans to update to the newest 1.1.x bugfix branch of marlin?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

Murloc992 commented 6 years ago

I am trying to setup the newest branch without any support for the TFT and so far everything seems to work. Except homing makes the printer call kill(). Weird. Any way to find out what triggered kill()?

derhopp commented 6 years ago

Hi,

thats unfortunately trial and error. Did you change your drivers? Have overstepped (too high step frequency while moving)? Did you accidentally put a signal to the kill-pin?

Best regards.

On 7. Jul 2018, at 23:37, Andrius Tarasovas notifications@github.com wrote:

I am trying to setup the newest branch without any support for the TFT and so far everything seems to work. Except homing makes the printer call kill(). Weird. Any way to find out what triggered kill()?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

Murloc992 commented 6 years ago

I have TMC2208 in 4 out of 5 driver slots. So far I haven't changed much from defaults. My drivers are not connected by UART. Right now I am just trying to replace all kill() instances with readable output..

Murloc992 commented 6 years ago

Okay, I found it. It's endstop validation. After I removed the kill from it I get: echo:endstops hit: X:-5.00 Y:-3.39 Z:-1.99

I wonder why would it fail?

Murloc992 commented 6 years ago

It's the X axis somehow. I move it to the center, press home and it "homes" in the middle of the bed. Consequent home attempts makes it "wobble" back to the endstop. Weiiiiird.

M119 shows the endstop as open when it homes at a random spot.

When it homes to the endstop it shows up as TRIGGERED.

derhopp commented 5 years ago

What does the end stop status show, when the endstop is physically triggered and when not? Could be inverted in the FW, or is it maybe short?

On 8. Jul 2018, at 00:56, Andrius Tarasovas notifications@github.com wrote:

It's the X axis somehow. I move it to the center, press home and it "homes" in the middle of the bed. Consequent home attempts makes it "wobble" back to the endstop. Weiiiiird.

M119 shows the endstop as open when it homes at a random spot.

When it homes to the endstop it shows up as TRIGGERED.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

Murloc992 commented 5 years ago

Endstop is perfectly normal according to M119. Steps per unit are the same as default: #define DEFAULT_AXIS_STEPS_PER_UNIT { 80, 80, 400, 92.6 }

Murloc992 commented 5 years ago

I think it is related to newest firmware and only X axis. I have opened an issue on Marlin repo itself: https://github.com/MarlinFirmware/Marlin/issues/11224

Whenever I flash back to the firmware on this repo from the bugfix branch everything works just fine.

derhopp commented 5 years ago

Okay, that's why I don’t have that behavior, because I am still on the version of my marlin fork.

On 8. Jul 2018, at 20:56, Andrius Tarasovas notifications@github.com wrote:

I think it is related to newest firmware and only X axis. I have opened an issue on Marlin repo itself: MarlinFirmware#11224

Whenever I flash back to the firmware on this repo from the bugfix branch everything works just fine.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

Murloc992 commented 5 years ago

Seems like making the newest firmware work with Mega will require hardware mods to the endstops themselves. Namely, adding 100nF capacitors in parallel.

derhopp commented 5 years ago

I don’t put any capacitor nowhere on my trigorilla board. I just burned my part fan transistor through with a 22uC tantal capacitor. Fortunately it the transistor is short not open... so the fan still works. (:

On 8. Jul 2018, at 22:46, Andrius Tarasovas notifications@github.com wrote:

Seems like making the newest firmware work with Mega will require hardware mods to the endstops themselves. Namely, adding 100nF capacitors in parallel.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

Murloc992 commented 5 years ago

@derhopp Thanks for doing the update. :)