[FR] Support for 4Max Pro 2.0 (and original 4MP) #65

New Issue

2021-01-24T03:01:46-06:00

alfrankgit commented

2021-01-24 03:01:46 -06:00

(Migrated from github.com)

Hi! I really appreciate the effort you put into the Anycubic Mega Firmwares, since Anycubic doesn't do anything.

How about supporting the 4Max Pro (2.0 and original version) also? They have the same boards and displays.

For the 4Max Pro 2.0 I already patched your V1.1.9 in the Mega P TMC sections, see the attached Configuration.h and Configuration_adv.h. It has a BMG clone extruder, TMCs for X and Y, other thermistors. I had to disable the Anycubic Filament Sensor option.

I commented all my changes with //AFR.

But I am no programmer so I can't add a new environment to your project. But that would be nice to have, wouldn't it?

I also have three of the original 4Max Pro but none still in the original configuration, so I'm not sure what that was. IIRC it doesn't have TMCs and it definitely has the original DWIN display. But it has the Titan clone extruder. And hotend thermistor type 11. But I can test a configuration for that one too, if you can create an env for it.

PS: My native language is German.

Edit, 26.01.2021: made a few changes in speed and acceleration settings, reuploaded changed files...

4MP_2.0_KW1.1.9.zip

Hi! I really appreciate the effort you put into the Anycubic Mega Firmwares, since Anycubic doesn't do anything. How about supporting the 4Max Pro (2.0 and original version) also? They have the same boards and displays. For the 4Max Pro 2.0 I already patched your V1.1.9 in the Mega P TMC sections, see the attached Configuration.h and Configuration_adv.h. It has a BMG clone extruder, TMCs for X and Y, other thermistors. I had to disable the Anycubic Filament Sensor option. I commented all my changes with //AFR. But I am no programmer so I can't add a new environment to your project. But that would be nice to have, wouldn't it? I also have three of the original 4Max Pro but none still in the original configuration, so I'm not sure what that was. IIRC it doesn't have TMCs and it definitely has the original DWIN display. But it has the Titan clone extruder. And hotend thermistor type 11. But I can test a configuration for that one too, if you can create an env for it. PS: My native language is German. Edit, 26.01.2021: made a few changes in speed and acceleration settings, reuploaded changed files... [4MP_2.0_KW1.1.9.zip](https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/files/5875815/4MP_2.0_KW1.1.9.zip)

👍 1 ❤️ 1

knutwurst commented

2021-02-06 04:49:09 -06:00

(Migrated from github.com)

Hello,
so since the hardware seems to be the same, that wouldn't be a problem and I think it's great that you have already done the preparatory work :)

But I'm currently working on support for the Chiron - and by that I also mean support for all display functions, including leveling. There is also very strong demand for support for the Mega Pro Laser.

I'll see how quickly it goes with the 4MAX Pro, but I can't promise that I can take care of it right away. But I'll write it on my agenda :)

Hello, so since the hardware seems to be the same, that wouldn't be a problem and I think it's great that you have already done the preparatory work :) But I'm currently working on support for the Chiron - and by that I also mean support for all display functions, including leveling. There is also very strong demand for support for the Mega Pro Laser. I'll see how quickly it goes with the 4MAX Pro, but I can't promise that I can take care of it right away. But I'll write it on my agenda :)

❤️ 1

alfrankgit commented

2021-02-08 13:10:29 -06:00

(Migrated from github.com)

Hi,
and thanks a lot for your reply and infos.

As a moderator on drucktipps3d.de I'd gladly welcome you to our forum where I already recommended your excellent firmware quite a few times.

Hi, and thanks a lot for your reply and infos. As a moderator on drucktipps3d.de I'd gladly welcome you to our forum where I already recommended your excellent firmware quite a few times.

❤️ 1

github-actions[bot] commented

2021-03-10 20:07:39 -06:00

(Migrated from github.com)

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] commented

2021-05-14 21:14:39 -05:00

(Migrated from github.com)

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.

knutwurst commented

2021-10-30 04:28:59 -05:00

(Migrated from github.com)

I've included the 4MAX pro 2.0 build environment for stock and TMC. I actually don't know if all motor directions are correct, so please give me some feedback, what's not working correctly
KW-131-4MAXPRO2.zip
.

I've included the 4MAX pro 2.0 build environment for stock and TMC. I actually don't know if all motor directions are correct, so please give me some feedback, what's not working correctly [KW-131-4MAXPRO2.zip](https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/files/7446174/KW-131-4MAXPRO2.zip) .

❤️ 4

alfrankgit commented

2021-10-30 07:57:44 -05:00

(Migrated from github.com)

Thanks for including the 4Max Pro 2.0 now, but I can't test it myself anymore because I don't own the 4Max Pro 2.0 anymore. But there are users on drucktipps3d.de who do and are aware of your firmware and my "hacks".
https://drucktipps3d.de/forum/topic/anycubic-4max-pro-2-0/?part=23#postid-180447

Thanks for including the 4Max Pro 2.0 now, but I can't test it myself anymore because I don't own the 4Max Pro 2.0 anymore. But there are users on drucktipps3d.de who do and are aware of your firmware and my "hacks". https://drucktipps3d.de/forum/topic/anycubic-4max-pro-2-0/?part=23#postid-180447

👍 2

knutwurst commented

2021-10-30 08:05:12 -05:00

(Migrated from github.com)

@alfrankgit Maybe you can shed light on the darkness. I saw in your config that you are using the Build Environment of the MEGA_P and activate both MEGA_P, TMC and DGUS2 for it.

Are these settings for the stick 4MAX or for one in which all drivers have been substituted for TMC2208?

If you built MEGA_P_TMC for the 4MAX stock, I had a mistake in thinking and maybe the directions of the two versions (TMC and non-TMC) are now reversed :D

I'm looking forward for some "testers" ;)

@alfrankgit Maybe you can shed light on the darkness. I saw in your config that you are using the Build Environment of the MEGA_P and activate both MEGA_P, TMC and DGUS2 for it. Are these settings for the stick 4MAX or for one in which all drivers have been substituted for TMC2208? If you built MEGA_P_TMC for the 4MAX stock, I had a mistake in thinking and maybe the directions of the two versions (TMC and non-TMC) are now reversed :D I'm looking forward for some "testers" ;)

alfrankgit commented

2021-10-30 08:12:05 -05:00

(Migrated from github.com)

I didn't change any physical stepper drivers on the 4Max Pro 2.0.
All my changes in the configuration files are marked with //AFR, either as a new comment to disable a line or as a comment with the original content of the line followed by a line with the changes I made.

I didn't change any physical stepper drivers on the 4Max Pro 2.0. All my changes in the configuration files are marked with //AFR, either as a new comment to disable a line or as a comment with the original content of the line followed by a line with the changes I made.

knutwurst commented

2021-10-30 08:17:18 -05:00

(Migrated from github.com)

...then... the 4MAX_TMC version should work on stock. Let's wait for feedback.

And thank you again for your provided config!

...then... the 4MAX_TMC version should work on stock. Let's wait for feedback. And thank you again for your provided config!

👍 1

JonnyHaystack commented

2021-10-30 08:51:10 -05:00

(Migrated from github.com)

I've been using alfrank's config with MEGA_P_TMC environment. I can test with the new environment at some point 😄

I've been using alfrank's config with MEGA_P_TMC environment. I can test with the new environment at some point :smile:

knutwurst commented

2021-10-30 18:09:16 -05:00

(Migrated from github.com)

After getting some feedback I added configurations for both, Stock and full TMC Versions. Now also for the original 4MAX Metal.
The case light (controllable via touchscreen) should also work. Please let me know if there are any other issues. If not, I'll release the version in the upcoming days.

KW_4MAX_4MAXPRO2_v1.3.1.zip

After getting some feedback I added configurations for both, Stock and full TMC Versions. Now also for the original 4MAX Metal. The case light (controllable via touchscreen) should also work. Please let me know if there are any other issues. If not, I'll release the version in the upcoming days. [KW_4MAX_4MAXPRO2_v1.3.1.zip](https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/files/7447746/KW_4MAX_4MAXPRO2_v1.3.1.zip)

❤️ 1

q4wey commented

2021-10-31 00:46:38 -05:00

(Migrated from github.com)

After getting some feedback I added configurations for both, Stock and full TMC Versions. Now also for the original 4MAX Metal. The case light (controllable via touchscreen) should also work. Please let me know if there are any other issues. If not, I'll release the version in the upcoming days.

KW_4MAX_4MAXPRO2_v1.3.1.zip

I'm new to this thread and have limited experience with marlin but I tested your hex files currently I have found the file titled (4MAXP2_v1.3.1-4MP2) to work but with 2 glitches. I don't know if these glitches are unique to my machine 4maxv2
or in the firmware itself. The display will run two intro cycles on startup and the stop print button will flicker until the tool head is parked.

I hope this info is of anyhelp.

> After getting some feedback I added configurations for both, Stock and full TMC Versions. Now also for the original 4MAX Metal. The case light (controllable via touchscreen) should also work. Please let me know if there are any other issues. If not, I'll release the version in the upcoming days. > > [KW_4MAX_4MAXPRO2_v1.3.1.zip](https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/files/7447746/KW_4MAX_4MAXPRO2_v1.3.1.zip) I'm new to this thread and have limited experience with marlin but I tested your hex files currently I have found the file titled (4MAXP2_v1.3.1-4MP2) to work but with 2 glitches. I don't know if these glitches are unique to my machine 4maxv2 or in the firmware itself. The display will run two intro cycles on startup and the stop print button will flicker until the tool head is parked. I hope this info is of anyhelp.

MasterYod4 commented

2021-10-31 10:51:02 -05:00

(Migrated from github.com)

Hello first of all, I would like to thank you very much for your work!
I tested version 4MAXP2_v1.3.1-4MP2 on my 4Max Pro 2.0. What I noticed is that the light button now works but the normal 4 point leveling in Anycubic Menu doesn't work.
As described by q4wey, the intro runs twice but I couldn't detect the stop button flickering.

Hello first of all, I would like to thank you very much for your work! I tested version 4MAXP2_v1.3.1-4MP2 on my 4Max Pro 2.0. What I noticed is that the light button now works but the normal 4 point leveling in Anycubic Menu doesn't work. As described by q4wey, the intro runs twice but I couldn't detect the stop button flickering.

IrieRainer commented

2021-10-31 12:36:26 -05:00

(Migrated from github.com)

Hello first of all, I would like to thank you very much for your work! I tested version 4MAXP2_v1.3.1-4MP2 on my 4Max Pro 2.0. What I noticed is that the light button now works but the normal 4 point leveling in Anycubic Menu doesn't work. As described by q4wey, the intro runs twice but I couldn't detect the stop button flickering.

Yes, same for me (tested 4MP2 stock version). The original "Leveling"-Button isn't working (like in the self compiled versions before).

@MasterYod4
You can go to "print" -> "Special Menu" to get 4 point or even Mesh bed leveling.

> > > Hello first of all, I would like to thank you very much for your work! I tested version 4MAXP2_v1.3.1-4MP2 on my 4Max Pro 2.0. What I noticed is that the light button now works but the normal 4 point leveling in Anycubic Menu doesn't work. As described by q4wey, the intro runs twice but I couldn't detect the stop button flickering. Yes, same for me (tested 4MP2 stock version). The original "Leveling"-Button isn't working (like in the self compiled versions before). @MasterYod4 You can go to "print" -> "Special Menu" to get 4 point or even Mesh bed leveling.

MasterYod4 commented

2021-10-31 12:47:08 -05:00

(Migrated from github.com)

@CruisenRainerWahnsinn Thanks for the hint.

knutwurst commented

2021-10-31 12:49:29 -05:00

(Migrated from github.com)

The original "Leveling"-Button isn't working

I know... that's because it's not implemented at all. I just included the build paths and ne configurations and "hacked" the light control in. This isn't final at all. It's just a milestone. I'll take a look at anycubic's implementation of the leveling menu. If it's straight forward, i'll implement it also.

In the meantime, you can use the specialmenu like @CruisenRainerWahnsinn mentioned :)

> The original "Leveling"-Button isn't working I know... that's because it's not implemented at all. I just included the build paths and ne configurations and "hacked" the light control in. This isn't final at all. It's just a milestone. I'll take a look at anycubic's implementation of the leveling menu. If it's straight forward, i'll implement it also. In the meantime, you can use the specialmenu like @CruisenRainerWahnsinn mentioned :)

JonnyHaystack commented

2021-10-31 13:40:25 -05:00

(Migrated from github.com)

Is the filament runout sensor working? I think some other people may have got it working in forks that I've seen

knutwurst commented

2021-10-31 13:49:33 -05:00

(Migrated from github.com)

@JonnyHaystack it's currently disabled until I figured out the correct pin.

hanebuechenes commented

2021-11-01 01:29:08 -05:00

(Migrated from github.com)

Tested the version KW_4MAX_4MAXPRO2_v1.3.1.zip on stock 4max V1. seems to work nice, only the Y axis is wrong direction. Can i change this somewhere, or have it to be compiled again?

IrieRainer commented

2021-11-01 04:23:15 -05:00

(Migrated from github.com)

Tested the version KW_4MAX_4MAXPRO2_v1.3.1.zip on stock 4max V1. seems to work nice, only the Y axis is wrong direction. Can i change this somewhere, or have it to be compiled again?

Which hex file did you chose of the zip? There are 4 files.

I'm not sure if it is true for the 4max (1), but if you use TMC Version of 4MP2 the direction is switched. So the TMC version of it might fix this issue.

> > > Tested the version KW_4MAX_4MAXPRO2_v1.3.1.zip on stock 4max V1. seems to work nice, only the Y axis is wrong direction. Can i change this somewhere, or have it to be compiled again? Which hex file did you chose of the zip? There are 4 files. I'm not sure if it is true for the 4max (1), but if you use TMC Version of 4MP2 the direction is switched. So the TMC version of it might fix this issue.

MasterYod4 commented

2021-11-02 13:20:50 -05:00

(Migrated from github.com)

I played around a bit today and noticed the following:

Set flow rate - works
Preheat Ultrabase - works
4 Point Leveling - only drives up to point A, all other points are not approached
Mesh leverling - works
PID Tune Hotend - does not work
PID Tune Ultrabase - works

I played around a bit today and noticed the following: Set flow rate - works Preheat Ultrabase - works 4 Point Leveling - only drives up to point A, all other points are not approached Mesh leverling - works PID Tune Hotend - does not work PID Tune Ultrabase - works

Yury-MonZon commented

2021-11-03 01:57:20 -05:00

(Migrated from github.com)

I second what MasterYod4 said.

Also, I've tried both TMC and non-TMC version on 4Max Pro 2.0(which has TMC installed by default). TMC version has Z axis reversed.

On both versions I can't read/send commands via USB, I've tried 57.6k, 115.2k and 250k baudrate - got corrupted data. The cable and drivers are fine - I can successfully flash the board. And I can connect to the stock firmware with 250k baudrate.

Stopping the printing process from the touchscreen shows me like a thousand of popup screens that stop is done. It doesn't happen if I pause the print and then stop it.

I'm able to test multiple times, if it could be useful to developer - let me know.

I second what MasterYod4 said. Also, I've tried both TMC and non-TMC version on 4Max Pro 2.0(which has TMC installed by default). TMC version has Z axis reversed. On both versions I can't read/send commands via USB, I've tried 57.6k, 115.2k and 250k baudrate - got corrupted data. The cable and drivers are fine - I can successfully flash the board. And I can connect to the stock firmware with 250k baudrate. Stopping the printing process from the touchscreen shows me like a thousand of popup screens that stop is done. It doesn't happen if I pause the print and then stop it. I'm able to test multiple times, if it could be useful to developer - let me know.

Daventrik commented

2021-11-03 08:26:54 -05:00

(Migrated from github.com)

i would be glad to help with testing but i didn't flashed my printer with these versions yet, still on stock but i have the "round corners" on a square and i hope that the new firmware can solve that issue since the profile tuning is not solving this. How can i help?

knutwurst commented

2021-11-03 15:59:51 -05:00

(Migrated from github.com)

1.4.0 Beta 2 is out now.

👍 4

IrieRainer commented

2021-11-03 17:27:47 -05:00

(Migrated from github.com)

i would be glad to help with testing but i didn't flashed my printer with these versions yet, still on stock but i have the "round corners" on a square and i hope that the new firmware can solve that issue since the profile tuning is not solving this. How can i help?

Try setting K factor to 0.2

Send "M900 K0.20" and safe with M500
Try 190°C (if PLA)
Get a e3d V6 nozzle (fits on stock hotend)
=> big improvement

> > > i would be glad to help with testing but i didn't flashed my printer with these versions yet, still on stock but i have the "round corners" on a square and i hope that the new firmware can solve that issue since the profile tuning is not solving this. How can i help? Try setting K factor to 0.2 Send "M900 K0.20" and safe with M500 Try 190°C (if PLA) Get a e3d V6 nozzle (fits on stock hotend) => big improvement

q4wey commented

2021-11-03 19:54:44 -05:00

(Migrated from github.com)

1.4.0 Beta 2 is out now.

Tested 1.3.0 beta 2, didn't make any changes just complied and uploaded. No menu pops up in the print menu for mesh leveling etc. Motors are all in the correct direction and homes/ heats up.

> 1.4.0 Beta 2 is out now. Tested 1.3.0 beta 2, didn't make any changes just complied and uploaded. No menu pops up in the print menu for mesh leveling etc. Motors are all in the correct direction and homes/ heats up.

Daventrik commented

2021-11-04 05:32:23 -05:00

(Migrated from github.com)

i would be glad to help with testing but i didn't flashed my printer with these versions yet, still on stock but i have the "round corners" on a square and i hope that the new firmware can solve that issue since the profile tuning is not solving this. How can i help?

Try setting K factor to 0.2

Send "M900 K0.20" and safe with M500 Try 190°C (if PLA) Get a e3d V6 nozzle (fits on stock hotend) => big improvement

I will buy a e3d v6 nozzle but what would be recommended? Brass? copper plated, stainless steel? Thank you!

> > > > i would be glad to help with testing but i didn't flashed my printer with these versions yet, still on stock but i have the "round corners" on a square and i hope that the new firmware can solve that issue since the profile tuning is not solving this. How can i help? > > Try setting K factor to 0.2 > > Send "M900 K0.20" and safe with M500 Try 190°C (if PLA) Get a e3d V6 nozzle (fits on stock hotend) => big improvement I will buy a e3d v6 nozzle but what would be recommended? Brass? copper plated, stainless steel? Thank you!

Yury-MonZon commented

2021-11-04 10:34:28 -05:00

(Migrated from github.com)

Version 1.4.0.-b2 doesn't have linear advance support on 4Max Pro 2:
Unknown command: M900
What about thermistor type, is it correct? I had to raise the nozzle temp to 230 for PLA to get proper layer adhesion (with 70% part fan as mentioned in the guide). Is it wrong or it is happening because of the stock steel nozzle?
Thanks a lot!

Version 1.4.0.-b2 doesn't have linear advance support on 4Max Pro 2: `Unknown command: M900` What about thermistor type, is it correct? I had to raise the nozzle temp to 230 for PLA to get proper layer adhesion (with 70% part fan as mentioned in the guide). Is it wrong or it is happening because of the stock steel nozzle? Thanks a lot!

knutwurst commented

2021-11-05 05:03:34 -05:00

(Migrated from github.com)

4 Point level fixed in b6a11d2
PID Tune fixed in 9cbf70c
Linear advance fixed in dd169b7

Thanks for your feedback!

4 Point level fixed in b6a11d2 PID Tune fixed in 9cbf70c Linear advance fixed in dd169b7 Thanks for your feedback!

👍 2

Yury-MonZon commented

2021-11-05 05:16:01 -05:00

(Migrated from github.com)

You are the man! That was quick! Thanks a lot!
Are you planning to release 1.4.0-beta.3 with those fixes any time soon?

You are the man! That was quick! Thanks a lot! Are you planning to release 1.4.0-beta.3 with those fixes any time soon?

q4wey commented

2021-11-06 01:04:44 -05:00

(Migrated from github.com)

@knutwurst

Tested the new release 1.4.0.beta 2 today. When using the built in remove filament tool while a print is paused the filament will begin to remove but then the printer reboots so you cant resume the print.

Your doing great work on this mate, many thanks.

@knutwurst Tested the new release 1.4.0.beta 2 today. When using the built in remove filament tool while a print is paused the filament will begin to remove but then the printer reboots so you cant resume the print. Your doing great work on this mate, many thanks.

knutwurst commented

2021-11-06 04:33:47 -05:00

(Migrated from github.com)

@Yury-MonZon dunno... I have to fix some more things as you can see ;) In the upcoming days I think. But you can check out the master branch and compile it by yourself :)

@q4wey Does this only apply to the 4MAX Pro v2?

@Yury-MonZon dunno... I have to fix some more things as you can see ;) In the upcoming days I think. But you can check out the master branch and compile it by yourself :) @q4wey Does this only apply to the 4MAX Pro v2?

IrieRainer commented

2021-11-06 10:20:53 -05:00

(Migrated from github.com)

Didn't test the latest alphas yet. Still very happy about 1.3.1 :) already

Concerning ENV and 4max types:
There are several 4max out. Just wondering if env "4max" is meant to be "4max pro (1)". There should be 4max, 4max pro, and 4 max pro 2 (afaik)

Concerning acceleation/jerk parameters that are working very nice for me:

Recv: echo:; Steps per unit:
Recv: echo: M92 X100.00 Y80.00 Z800.00 E423.50
Recv: echo:; Maximum feedrates (units/s):
Recv: echo:  M203 X150.00 Y150.00 Z25.00 E30.00
Recv: echo:; Maximum Acceleration (units/s2):
Recv: echo:  M201 X2000.00 Y2000.00 Z60.00 E10000.00
Recv: echo:; Acceleration (units/s2): P<print_accel> R<retract_accel> T<travel_accel>
Recv: echo:  M204 P1500.00 R1500.00 T1500.00
Recv: echo:; Advanced: B<min_segment_time_us> S<min_feedrate> T<min_travel_feedrate> J<junc_dev>
Recv: echo:  M205 B20000.00 S0.00 T0.00 J0.02

Recv: echo:  M900 K0.20

:
(changes on the printer: e3d V6 nozzle and adapted fan duct)

Didn't test the latest alphas yet. Still very happy about 1.3.1 :) already **Concerning ENV and 4max types:** There are several 4max out. Just wondering if env "4max" is meant to be "4max pro (1)". There should be 4max, 4max pro, and 4 max pro 2 (afaik) **Concerning acceleation/jerk parameters that are working very nice for me:** ``` Recv: echo:; Steps per unit: Recv: echo: M92 X100.00 Y80.00 Z800.00 E423.50 Recv: echo:; Maximum feedrates (units/s): Recv: echo: M203 X150.00 Y150.00 Z25.00 E30.00 Recv: echo:; Maximum Acceleration (units/s2): Recv: echo: M201 X2000.00 Y2000.00 Z60.00 E10000.00 Recv: echo:; Acceleration (units/s2): P<print_accel> R<retract_accel> T<travel_accel> Recv: echo: M204 P1500.00 R1500.00 T1500.00 Recv: echo:; Advanced: B<min_segment_time_us> S<min_feedrate> T<min_travel_feedrate> J<junc_dev> Recv: echo: M205 B20000.00 S0.00 T0.00 J0.02 Recv: echo: M900 K0.20 ``` ![20211103_085654](https://user-images.githubusercontent.com/73447431/140614715-55b6a35f-832a-422b-8c5d-87d81d310fe1.jpg) : (changes on the printer: e3d V6 nozzle and adapted fan duct)

knutwurst commented

2021-11-06 10:22:56 -05:00

(Migrated from github.com)

@CruisenRainerWahnsinn take a look at the Beta (not alpha). ;) All 4MAX variants should be covered. Beta 3 is on the way with more improvements.

👍 1

IrieRainer commented

2021-11-06 10:28:49 -05:00

(Migrated from github.com)

@CruisenRainerWahnsinn take a look at the Beta (not alpha). ;) All 4MAX variants should be covered. Beta 3 is on the way with more improvements.

I'll check them out 100%. Thank's a lot for your work!

> > > @CruisenRainerWahnsinn take a look at the Beta (not alpha). ;) All 4MAX variants should be covered. Beta 3 is on the way with more improvements. I'll check them out 100%. Thank's a lot for your work!

Yury-MonZon commented

2021-11-06 12:55:21 -05:00

(Migrated from github.com)

@CruisenRainerWahnsinn Print acceleration 1500? Looks a bit high to me, how did you get rid of the ringing? What are your print speeds with these settings? Also, how did you manage to install e3d v6 nozzle? It is longer, isn't it?

IrieRainer commented

2021-11-06 15:03:43 -05:00

(Migrated from github.com)

@CruisenRainerWahnsinn Print acceleration 1500? Looks a bit high to me, how did you get rid of the ringing? What are your print speeds with these settings? Also, how did you manage to install e3d v6 nozzle? It is longer, isn't it?

It's working great for me with these setting.

This is the latest Cura Profile I'm using (from the print you see):
https://www.dropbox.com/s/qxn14x4ppobsnq3/4MaxPro2.0_PLA_0.2mm_192C.curaprofile?dl=0

The only thing you need to adapt to the e3d v6 nozzle, is the height of the fan duct (needs little sanding or reconstruction). The e3d v6 nozzle fits the stock hotend perfectly. + I prefere capricorn tube.

There is still a tiny tiny bit of ghosting going on, but it's very hard to see and ok for me.

I got trouble on Z-Axis at 180mm. I put some grease on the z-axis, went up and down and made 2 test prints (2 towers 5*190mm). First one was better than prints i did before. Second test print worked fine - no more rough layers on the top of the prints.

> > > @CruisenRainerWahnsinn Print acceleration 1500? Looks a bit high to me, how did you get rid of the ringing? What are your print speeds with these settings? Also, how did you manage to install e3d v6 nozzle? It is longer, isn't it? It's working great for me with these setting. This is the latest Cura Profile I'm using (from the print you see): https://www.dropbox.com/s/qxn14x4ppobsnq3/4MaxPro2.0_PLA_0.2mm_192C.curaprofile?dl=0 ![grafik](https://user-images.githubusercontent.com/73447431/140624094-ec869faa-4ea5-4966-8222-dfe8abd46c94.png) The only thing you need to adapt to the e3d v6 nozzle, is the height of the fan duct (needs little sanding or reconstruction). The e3d v6 nozzle fits the stock hotend perfectly. + I prefere capricorn tube. There is still a tiny tiny bit of ghosting going on, but it's very hard to see and ok for me. I got trouble on Z-Axis at 180mm. I put some grease on the z-axis, went up and down and made 2 test prints (2 towers 5*190mm). First one was better than prints i did before. Second test print worked fine - no more rough layers on the top of the prints.

q4wey commented

2021-11-06 17:52:22 -05:00

(Migrated from github.com)

@Yury-MonZon dunno... I have to fix some more things as you can see ;) In the upcoming days I think. But you can check out the master branch and compile it by yourself :)

@q4wey Does this only apply to the 4MAX Pro v2?

yes my apologies this was tested on the 4max pro 2.0 i should have specified

> @Yury-MonZon dunno... I have to fix some more things as you can see ;) In the upcoming days I think. But you can check out the master branch and compile it by yourself :) > > @q4wey Does this only apply to the 4MAX Pro v2? yes my apologies this was tested on the 4max pro 2.0 i should have specified

q4wey commented

2021-11-13 18:36:03 -06:00

(Migrated from github.com)

Tested 4MAXP2_DGUS_v1.4.0-b3.hex on the 4max pro 2.0. When printing and the pause button it pressed a message of SD pullout will pop on the screen until the printer head it parked. after the head is parked 3 beeps are made but when you try to resume the print it just wont resume.

Yury-MonZon commented

2021-11-14 00:28:54 -06:00

(Migrated from github.com)

it just wont resume

I also have this sometimes. Wondering why is this not a constant thing?

> it just wont resume I also have this sometimes. Wondering why is this not a constant thing?

knutwurst commented

2021-11-14 05:34:50 -06:00

(Migrated from github.com)

@q4wey and @Yury-MonZon are you sure that you have the DGUS variant with Anycubic 0.0.2 Display? There is a Pause/Resume bug in the original DGUS II.

Yury-MonZon commented

2021-11-14 07:39:02 -06:00

(Migrated from github.com)

I'm sorry, didn't know that they are different. How do I get the model of the screen?

IrieRainer commented

2021-11-14 18:15:14 -06:00

(Migrated from github.com)

@Yury-MonZon

I'm sorry, didn't know that they are different. How do I get the model of the screen?

There are some sources here:

https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/wiki/Beginner's-Guide-(English)#2-identification-of-the-display

&

https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/wiki/Types-of-Anycubic-Touchscreens

@Yury-MonZon > > I'm sorry, didn't know that they are different. How do I get the model of the screen? There are some sources here: https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/wiki/Beginner's-Guide-(English)#2-identification-of-the-display & https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/wiki/Types-of-Anycubic-Touchscreens

👍 1

Yury-MonZon commented

2021-11-15 04:41:33 -06:00

(Migrated from github.com)

@knutwurst Yeah, I have Anycubic 0.0.2 display (DGUS clone) - the text 'Ready' is sharp and small.

There are some sources here:

Thanks a lot.

@knutwurst Yeah, I have Anycubic 0.0.2 display (DGUS clone) - the text 'Ready' is sharp and small. > There are some sources here: Thanks a lot.

luknz commented

2021-11-16 09:25:13 -06:00

(Migrated from github.com)

Hi, first of all thank you very much for your effort! Knutwurst has been running flawlessly on my i3 Mega for months. Today I also flashed my Anycubic 4Max Pro 2.0 with V 1.4.0-beta.3. Since then he has been making strange whistling noises when printing, like an old Internet modem. Does anyone know what could be causing this?

Update:
I have since found out that the beeps and whistles are triggered by the start code from github.
The noises only appear when I print with the suggested start code (https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/wiki/Cura-Start--and-Endcode-with-preheat-and-purge-line).
If I use the standard Cura start code, the printer prints quietly as usual.

Hi, first of all thank you very much for your effort! Knutwurst has been running flawlessly on my i3 Mega for months. Today I also flashed my Anycubic 4Max Pro 2.0 with V 1.4.0-beta.3. Since then he has been making strange whistling noises when printing, like an old Internet modem. Does anyone know what could be causing this? Update: I have since found out that the beeps and whistles are triggered by the start code from github. The noises only appear when I print with the suggested start code (https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/wiki/Cura-Start--and-Endcode-with-preheat-and-purge-line). If I use the standard Cura start code, the printer prints quietly as usual.

Truggy commented

2021-11-19 23:02:27 -06:00

(Migrated from github.com)

Not sure what I did wrong. I have v002 board 4mp v2.

when I stop a print the system crashes and is ina continuous reboot until hard switch is switched off.

I have the clone screen as well - same behavior with stock steppers or all tmc 2208. Did reset and load defaults in eprom.

thanks,
John

Not sure what I did wrong. I have v002 board 4mp v2. when I stop a print the system crashes and is ina continuous reboot until hard switch is switched off. I have the clone screen as well - same behavior with stock steppers or all tmc 2208. Did reset and load defaults in eprom. thanks, John

Yury-MonZon commented

2021-11-28 05:26:50 -06:00

(Migrated from github.com)

continuous reboot until hard switch is switched off

When I do this I have multiple messages on the screen. So I use pause and then stop. And after that printer doesn't print when you start a new print.

> continuous reboot until hard switch is switched off When I do this I have multiple messages on the screen. So I use pause and then stop. And after that printer doesn't print when you start a new print.

Truggy commented

2021-11-28 06:48:44 -06:00

(Migrated from github.com)

That the same as I have. Ok. Wasnt sure if something was up with the mainboard.

dspitzer commented

2021-11-30 17:33:15 -06:00

(Migrated from github.com)

After a lot of fiddling I managed to install a BLTouch in the 4Max Pro 2 and with the latest master the auto levelling works perfectly - thanks a lot @knutwurst !

I'm using the 4MAXP2_DGUS_BLT_10 and the only parameter that I changed was the NOZZLE_TO_PROBE_OFFSET.

A few quirks that I noticed so far: After booting, the display immediately reboots (it basically shows the startup animation twice). Also, stopping a print results in a boot loop - I have to turn the printer off every time I stop a print.

After a lot of fiddling I managed to install a BLTouch in the 4Max Pro 2 and with the latest master the auto levelling works perfectly - thanks a lot @knutwurst ! I'm using the 4MAXP2_DGUS_BLT_10 and the only parameter that I changed was the NOZZLE_TO_PROBE_OFFSET. A few quirks that I noticed so far: After booting, the display immediately reboots (it basically shows the startup animation twice). Also, stopping a print results in a boot loop - I have to turn the printer off every time I stop a print.

Truggy commented

2021-11-30 18:29:43 -06:00

(Migrated from github.com)

I get the same but I used the non blt firmware.

SchimmelSepp commented

2021-12-01 03:25:46 -06:00

(Migrated from github.com)

Hey good morning,
Is it just recommended to use CURA or do i must use CURA with the Firmware from Knutwurst. Because i think Prusa works better for details & corners.

Hey good morning, Is it just recommended to use CURA or do i must use CURA with the Firmware from Knutwurst. Because i think Prusa works better for details & corners.

IrieRainer commented

2021-12-04 03:26:44 -06:00

(Migrated from github.com)

@SchimmelSepp
Most users I crossed, were using cura, some prusa. I saw good results on both.

Concerning display and crashes:
I recently found out that my octoprint server is solving the bugs you're describing (but the double starting animation)
My machine don't crash and i can navigate through the whole menu (on the display) the whole time - while printing and always can access the special menu, which isn't the case for non-print-server-users.

@SchimmelSepp Most users I crossed, were using cura, some prusa. I saw good results on both. Concerning display and crashes: I recently found out that my octoprint server is solving the bugs you're describing (but the double starting animation) My machine don't crash and i can navigate through the whole menu (on the display) the whole time - while printing and always can access the special menu, which isn't the case for non-print-server-users.

SchimmelSepp commented

2021-12-04 05:10:32 -06:00

(Migrated from github.com)

@SchimmelSepp Most users I crossed, were using cura, some prusa. I saw good results on both.

Concerning display and crashes: I recently found out that my octoprint server is solving the bugs you're describing (but the double starting animation) My machine don't crash and i can navigate through the whole menu (on the display) the whole time - while printing and always can access the special menu, which isn't the case for non-print-server-users.

Yeah, i use prusa and the result with KW-Firmware is amazing instead of the Standard. Me either had just the Problem when i hit Stop the Printer reboots it selfs 2-6 times (idk why it does sometime 2 times and sometime up to 6) but yesterday i printed for 9 Hours and it stopped and didnt finished the printing, but the printer gived me via the Display the text „Print is finished“. And the Layerd looked good and didnt hat print fails.

> @SchimmelSepp Most users I crossed, were using cura, some prusa. I saw good results on both. > > Concerning display and crashes: I recently found out that my octoprint server is solving the bugs you're describing (but the double starting animation) My machine don't crash and i can navigate through the whole menu (on the display) the whole time - while printing and always can access the special menu, which isn't the case for non-print-server-users. Yeah, i use prusa and the result with KW-Firmware is amazing instead of the Standard. Me either had just the Problem when i hit Stop the Printer reboots it selfs 2-6 times (idk why it does sometime 2 times and sometime up to 6) but yesterday i printed for 9 Hours and it stopped and didnt finished the printing, but the printer gived me via the Display the text „Print is finished“. And the Layerd looked good and didnt hat print fails.

github-actions[bot] commented

2022-01-03 20:15:11 -06:00

(Migrated from github.com)

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.

Truggy commented

2022-01-03 21:28:50 -06:00

(Migrated from github.com)

Do we think a release 4 will happen?

IrieRainer commented

2022-01-17 12:06:42 -06:00

(Migrated from github.com)

@knutwurst

Just compiled and installed the beta 4 from today on my totally stock 4MP2.

Needed to chose DGUS-Version as env, because the stock 4MP2-env had no "special menu".
Maybe it got mixed up.

I wil run this vversion now and report all i find here.

@knutwurst Just compiled and installed the beta 4 from today on my totally stock 4MP2. Needed to chose DGUS-Version as env, because the stock 4MP2-env had no "special menu". Maybe it got mixed up. I wil run this vversion now and report all i find here.

IrieRainer commented

2022-01-20 03:57:04 -06:00

(Migrated from github.com)

@knutwurst

The DGUS-Version is working fine for the 100% stock printer!
No issues so far (with octoprint involved)

> @knutwurst The DGUS-Version is working fine for the 100% stock printer! No issues so far (with octoprint involved)

knutwurst commented

2022-01-21 10:56:35 -06:00

(Migrated from github.com)

There is nothing mixed up afaik. There are (older) 4MP2 printers that have an original DWIN/DGUS II display. They need the firmware without DGUS in the name. The newer printers with Anycubic 0.0.2 "DGUS Clone" need the _DGUS firmware.

That was already the case with the Mega X.

There is nothing mixed up afaik. There are (older) 4MP2 printers that have an original DWIN/DGUS II display. They need the firmware without DGUS in the name. The newer printers with Anycubic 0.0.2 "DGUS Clone" need the _DGUS firmware. That was already the case with the Mega X.

JonnyHaystack commented

2022-01-21 11:23:06 -06:00

(Migrated from github.com)

That does sound like a somewhat confusing naming convention 😛

That does sound like a somewhat confusing naming convention :stuck_out_tongue:

knutwurst commented

2022-01-21 11:28:35 -06:00

(Migrated from github.com)

I know. This is because the firmware was originally only intended for the Mega S. And at some point a display was built into it, which looks very similar to the DGUS II.

To support this display, I called the new firmware "DGUS" and somehow kept it.

Unfortunately, "real" DGUS II displays were actually installed in the Mega X and 4MAX, which can be controlled in a similar way to the Anycubic 1.0 display. But I didn't know that until then.

Maybe I'll change the naming scheme soon too. I also plan to mark the stock firmware as "stock" because the Mega Pro owners in particular always think they have to get the TMC version just because they have 2 TMC drivers.

All very confusing, I know :D

I know. This is because the firmware was originally only intended for the Mega S. And at some point a display was built into it, which looks very similar to the DGUS II. To support this display, I called the new firmware "DGUS" and somehow kept it. Unfortunately, "real" DGUS II displays were actually installed in the Mega X and 4MAX, which can be controlled in a similar way to the Anycubic 1.0 display. But I didn't know that until then. Maybe I'll change the naming scheme soon too. I also plan to mark the stock firmware as "stock" because the Mega Pro owners in particular always think they have to get the TMC version just because they have 2 TMC drivers. All very confusing, I know :D

❤️ 1

IrieRainer commented

2022-01-21 11:49:36 -06:00

(Migrated from github.com)

Haha, yes!

Thanks for your work!

I'm 100% sure i have the clone screen:
https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/wiki/Beginner's-Guide-(English)#23-the-anycubic-002-display-dgus-clone

Special menu looked like this since 1.3.0 (self compiled)
https://raw.githubusercontent.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/master/images/manual_dgus_specialmenu.jpg

Since 1.4.0b4 i have to chose DGUS to get the special menu back and it is still looking like before (not like original DWIN)
(I have a stock printer - no changes made on drivers or display)

I think this is what was confusing me.

Haha, yes! Thanks for your work! I'm 100% sure i have the clone screen: https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/wiki/Beginner's-Guide-(English)#23-the-anycubic-002-display-dgus-clone Special menu looked like this since 1.3.0 (self compiled) https://raw.githubusercontent.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/master/images/manual_dgus_specialmenu.jpg Since 1.4.0b4 i have to chose DGUS to get the special menu back and it is still looking like before (not like original DWIN) (I have a stock printer - no changes made on drivers or display) I think this is what was confusing me.

IrieRainer commented

2022-01-22 14:41:53 -06:00

(Migrated from github.com)

Otoprint error message which cause "promptly stop" on 4MP2-DGUS, when using mesh bed leveling with M420 S1 in the start gcode. without the command it has no error message and prints.

Fehler vom Drucker gemeldet
Die Firmware Deines Druckers hat einen Fehler gemeldet. Darum hat OctoPrint die Verbindung geschlossen. Gemeldeter Fehler: Failed to enable Bed Leveling

Otoprint error message which cause "promptly stop" on 4MP2-DGUS, when using mesh bed leveling with M420 S1 in the start gcode. without the command it has no error message and prints. ``` Fehler vom Drucker gemeldet Die Firmware Deines Druckers hat einen Fehler gemeldet. Darum hat OctoPrint die Verbindung geschlossen. Gemeldeter Fehler: Failed to enable Bed Leveling ```

IrieRainer commented

2022-01-22 14:46:30 -06:00

(Migrated from github.com)

Failed to enable Bed Leveling
#https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/issues/234

solved

(empty mesh was causing the problem)

Failed to enable Bed Leveling #https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/issues/234 solved (empty mesh was causing the problem)

knutwurst commented

2022-01-24 01:33:04 -06:00

(Migrated from github.com)

@CruisenRainerWahnsinn can you provide further information? And can you test it with 1.4.0 Beta 5?

VegaMyssil commented

2022-01-25 12:42:14 -06:00

(Migrated from github.com)

First of all thank you the printer is now working properly !

I have some issue with the LED strip. When I start a print the strip goes off. Also, had to change polarity on the Extruder Motor and Z axis since there is only two TMC driver (X and Y).

(Using the compiled firmware)

First of all thank you the printer is now working properly ! I have some issue with the LED strip. When I start a print the strip goes off. Also, had to change polarity on the Extruder Motor and Z axis since there is only two TMC driver (X and Y). (Using the compiled firmware)

Yury-MonZon commented

2022-01-26 01:19:17 -06:00

(Migrated from github.com)

First of all thank you the printer is now working properly !

I have some issue with the LED strip. When I start a print the strip goes off. Also, had to change polarity on the Extruder Motor and Z axis since there is only two TMC driver (X and Y).

(Using the compiled firmware)

You have to send a command to enable it in your start g-code:
M355 S1 P255

> First of all thank you the printer is now working properly ! > > I have some issue with the LED strip. When I start a print the strip goes off. Also, had to change polarity on the Extruder Motor and Z axis since there is only two TMC driver (X and Y). > > (Using the compiled firmware) You have to send a command to enable it in your start g-code: M355 S1 P255

VegaMyssil commented

2022-01-26 07:43:40 -06:00

(Migrated from github.com)

You have to send a command to enable it in your start g-code: M355 S1 P255

Will try ! Thanks !

> You have to send a command to enable it in your start g-code: M355 S1 P255 Will try ! Thanks !

iankds05 commented

2022-01-29 05:00:29 -06:00

(Migrated from github.com)

Well I have tried all variations of the firmware including Beta 5 and none work flawlessly. The Pause/Resume is broken and if Stop print is pressed the screen goes into a loop and the whole machine has to be shut off. Corner levelling can only be done from Special menu so to be honest I have given up on the outdated Trigrollia board. I intend to strip out the electronics and install a decent 32bit controller and screen so future updates of Marlin can be installed without having to hack the firmware every single time. Why Anycubic insist on using outdated control boards when the 3D world has moved on from Mega 2560 chips beats me. The 4Max Pro could have been an awesome machine if not let down by poor support and antique electronics.

knutwurst commented

2022-01-29 05:06:53 -06:00

(Migrated from github.com)

@iankds05 can you try to repruduce every issue (regarding pause/resume) on Beta 5 and create a bugticket? Maybe with a video or photos. The problem is, that I don't own a 4MAX Pro so I have to "code blindly" and listen to what people (like you) say to make it better.

The leveling function is currently not implemented yet, so the only way to level the bed is the internal 4 point and mesh leveling, which should also work... until I fugured out the internal tft functions to reverse engineer the functionality and provide full support.

Please be aware, that this firmware is still in beta state, so bugs always might occur.

@iankds05 can you try to repruduce every issue (regarding pause/resume) on Beta 5 and create a bugticket? Maybe with a video or photos. The problem is, that I don't own a 4MAX Pro so I have to "code blindly" and listen to what people (like you) say to make it better. The leveling function is currently not implemented yet, so the only way to level the bed is the internal 4 point and mesh leveling, which should also work... until I fugured out the internal tft functions to reverse engineer the functionality and provide full support. Please be aware, that this firmware is still in beta state, so bugs always might occur.

iankds05 commented

2022-01-29 17:41:42 -06:00

(Migrated from github.com)

So thanks for the reply Oliver, but at this stage I have already started to rip out all the electronics from my 4Max Pro v2 and replace with completely new 32 bit control board and dual function TFT screen. I need a reliable "Daily Go To" enclosed printer and continually having to tinker with the firmware is not an option anymore.
I commend you work so far, especially not having the actual hardware to soak test on. I did not use any of the binary files but compiled my own from your source code as I had replaced all the stepper drivers with TMC2209 standalone. At least with my new setup I can use UART and sensorless homing
I will post a progress report with pictures in case other tinkers want to be brave and do the same modifications.

So thanks for the reply Oliver, but at this stage I have already started to rip out all the electronics from my 4Max Pro v2 and replace with completely new 32 bit control board and dual function TFT screen. I need a reliable "Daily Go To" enclosed printer and continually having to tinker with the firmware is not an option anymore. I commend you work so far, especially not having the actual hardware to soak test on. I did not use any of the binary files but compiled my own from your source code as I had replaced all the stepper drivers with TMC2209 standalone. At least with my new setup I can use UART and sensorless homing I will post a progress report with pictures in case other tinkers want to be brave and do the same modifications.

ausdai commented

2022-01-31 22:38:32 -06:00

(Migrated from github.com)

@knutwurst Thank you so much for this. I have had a lot of trouble finding information about the 4Mac Pro v2.0. Could you please clarify which version of the firmware should be used. I have a recent model that says it includes the TMC2208 stepper drivers as stock. Does this mean I need to flash this with the _TCM using 4MAXP2_TMC_v1.4.0-b5.hex or 4MAXP2_DGUS_TMC_v1.4.0-b5.hex depending on the screen? Or should I be using the none _TCM versions?

mjaschen commented

2022-01-31 23:59:27 -06:00

(Migrated from github.com)

You can just try it ;-)

Center the printhead in the X, Y and Z directions so that it has enough space to move around it.
Move the printhead little distances in X, Y and Z with the built-in control screen or with OctoPrint an take notes which direction it moves when pressing the + or - keys.
Install the firmware.
Use the built-in control screen again to move the printhead. You will then see if the directions are the same or if you need to install the _TCM firmware to reverse the moving directions.

You can just try it ;-) 1. Center the printhead in the X, Y and Z directions so that it has enough space to move around it. 2. Move the printhead little distances in X, Y and Z with the built-in control screen or with OctoPrint an take notes which direction it moves when pressing the + or - keys. 3. Install the firmware. 4. Use the built-in control screen again to move the printhead. You will then see if the directions are the same or if you need to install the `_TCM` firmware to reverse the moving directions.

👍 1

knutwurst commented

2022-02-01 01:48:12 -06:00

(Migrated from github.com)

@ausdai : As mentioned in the FAQ ;)

But @mjaschen is also right! That's the way if you want to be absolutely sure.

@ausdai : As mentioned in the [FAQ](https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/wiki/FAQ-(english)) ;) But @mjaschen is also right! That's the way if you want to be absolutely sure.

ausdai commented

2022-02-01 02:40:15 -06:00

(Migrated from github.com)

@ausdai : As mentioned in the FAQ ;)

But @mjaschen is also right! That's the way if you want to be absolutely sure.

Thanks for letting me know. I did read the FAQ but I couldn't see anything that really answered that question specifically. Maybe I'm going blind! Thanks again, I will follow the instructions and test.

> @ausdai : As mentioned in the [FAQ](https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/wiki/FAQ-(english)) ;) > > But @mjaschen is also right! That's the way if you want to be absolutely sure. Thanks for letting me know. I did read the FAQ but I couldn't see anything that really answered that question specifically. Maybe I'm going blind! Thanks again, I will follow the instructions and test.

AKharytonchyk commented

2022-02-01 08:43:45 -06:00

(Migrated from github.com)

Hi Gents,

I am trying to connect RPI to a 4Max Pro 2. Though, it looks like UART3 is disabled on the motherboard. I am using the latest beta build for 4max. Might be someone has an idea how to turn it on?

Hi Gents, I am trying to connect RPI to a 4Max Pro 2. Though, it looks like UART3 is disabled on the motherboard. I am using the latest beta build for 4max. Might be someone has an idea how to turn it on?

IrieRainer commented

2022-02-10 16:32:48 -06:00

(Migrated from github.com)

After installing 1.4.0 my print bed is heating when the printer gets turned on. It is set to 0° and it's showing 0° as set, but the tempreature is increasing and never stopping. The bed is getting very hot and the display is showing the increasing temperature. (Same behavour on 1.4.1..now)

Where to start??? Replacing cables that are attached to the bed?
Ordered a mosfet too.

After installing 1.4.0 my print bed is heating when the printer gets turned on. It is set to 0° and it's showing 0° as set, but the tempreature is increasing and never stopping. The bed is getting very hot and the display is showing the increasing temperature. (Same behavour on 1.4.1..now) Where to start??? Replacing cables that are attached to the bed? Ordered a mosfet too. ![grafik](https://user-images.githubusercontent.com/73447431/153507461-3360ab7c-6271-47e2-b527-575ed4025f89.png) ![grafik](https://user-images.githubusercontent.com/73447431/153507495-e5ea1c20-730c-4755-861a-4156747302bb.png) ![grafik](https://user-images.githubusercontent.com/73447431/153507529-4598f3f3-196c-48b4-9a35-f5090604b38e.png) ![grafik](https://user-images.githubusercontent.com/73447431/153507584-2c0af57f-675d-4f69-8276-1c0c62f38f60.png)

knutwurst commented

2022-02-11 01:25:03 -06:00

(Migrated from github.com)

I can't explain it either, but it seems as if the power supply generates short-term voltage spikes when the PWM frequency is too low. This "could" lead to a defect in the MOSFET, but in my opinion it is very unlikely. After all, hundreds of printers work without any problems.

It's probably a coincidence. :(

The cables do not need to be swapped. The temperature is read correctly and the bed heats up. So all cables are still fine.

The MOSFET (second photo) is probably defective and is now switching through completely.

I hope you can solve the problem. Please continue to use 1.4.1. Just to be safe.

I can't explain it either, but it seems as if the power supply generates short-term voltage spikes when the PWM frequency is too low. This "could" lead to a defect in the MOSFET, but in my opinion it is very unlikely. After all, hundreds of printers work without any problems. It's probably a coincidence. :( The cables do not need to be swapped. The temperature is read correctly and the bed heats up. So all cables are still fine. The MOSFET (second photo) is probably defective and is now switching through completely. I hope you can solve the problem. Please continue to use 1.4.1. Just to be safe.

IrieRainer commented

2022-02-11 04:39:29 -06:00

(Migrated from github.com)

The MOSFET (second photo) is probably defective and is now switching through completely.

I hope you can solve the problem. Please continue to use 1.4.1. Just to be safe.

mosfet is ordred and 1.4.1 installed. still thanks for your work and keep on going!

> The MOSFET (second photo) is probably defective and is now switching through completely. > > I hope you can solve the problem. Please continue to use 1.4.1. Just to be safe. mosfet is ordred and 1.4.1 installed. still thanks for your work and keep on going!

❤️ 1

IrieRainer commented

2022-03-01 07:08:31 -06:00

(Migrated from github.com)

@knutwurst Can I use 1.4.3 or should i stay on 1.4.0b5, which im using now again, since my mosfet died? Feel like asking this time, before changing again :)

knutwurst commented

2022-03-01 07:10:03 -06:00

(Migrated from github.com)

@CruisenRainerWahnsinn it's safe to update ;)

❤️ 1

github-actions[bot] commented

2022-04-23 20:59:24 -05:00

(Migrated from github.com)

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] commented

2022-06-28 09:03:28 -05:00

(Migrated from github.com)

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.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wp/Marlin-2-0-x-Anycubic-i3-MEGA-S#65