Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need BLTouch version of 4MAXP2_DGUS_v1.5.4.hex firmare #561

Open
dennislia opened this issue Dec 16, 2024 · 12 comments
Open

Need BLTouch version of 4MAXP2_DGUS_v1.5.4.hex firmare #561

dennislia opened this issue Dec 16, 2024 · 12 comments

Comments

@dennislia
Copy link

Description

My Printer:

  • Model 4Max Pro v2 (BMG direct extruder)
  • Display 0.0.2 display (DGUS clone)
  • Mainboard Trilgorilla 0.0.2 (_DGUS firmware )
  • BLTouch sensor V3.1

There isn't a firmware version with BLT in the name that matches my printer, so I tried 4MAXP2_DGUS_v1.5.4.hex.

Feature Workflow

  1. I successfully installed the 4MAXP2_DGUS_v1.5.4.hex firmware.
  2. I was able to perform manual mesh leveling via the printer's LCD Special Menu and save to EPROM.
  3. I am able to 3D print using the save mesh values.
  4. I was able to install the BLTouch sensor and connect to the control board.
    5)when printer is turned ON the sensor's probe extends several times, retracts and the RED LED stays ON.
  5. using Octoprint gcode terminal sending M280 P0 S60 or any gcode that should be a valid BLTouch code results in an unrecognized command by the marlin firmware
    IMG_2271
    .
  6. This tells me BLtouch isn't supported by this firmware.
    IMG_2270

Additional Information

  • Provide pictures or links that demonstrate a similar feature or concept.
@stklcode
Copy link
Contributor

stklcode commented Dec 16, 2024

Anything wrong with 4MAXP2_DGUS_BLT_10_v1.5.4.hex from the Releases page?

_BLT is self-explaining here and 0.0.2 mainboard "behaves like a Trigorilla 1.0", so should run fine with _10 flavor.
(see
https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/wiki/Beginner's-Guide-(English)#4-download-the-correct-firmware)

@dennislia
Copy link
Author

dennislia commented Dec 16, 2024 via email

@stklcode
Copy link
Contributor

Weird 🤔 Both mages are built from the same source code in the same pipeline, so I’d expect both showing the very same issue or none.

Seems like this config line might not be correct here:

#if BOTH(KNUTWURST_BLTOUCH, KNUTWURST_4MAXP2)
#define Z_MIN_ENDSTOP_INVERTING false // Set to true to invert the logic of the endstop.
#else
#define Z_MIN_ENDSTOP_INVERTING true // Set to true to invert the logic of the endstop.
#endif

Changed back in 1.4.0 (d0219c5).

I could create a custom build and upload it later today, but unfortunately I don’t have a 4MAX and I have no idea whether reverting this might break anything else.

@dennislia
Copy link
Author

dennislia commented Dec 16, 2024 via email

@dennislia
Copy link
Author

dennislia commented Dec 17, 2024 via email

@stklcode
Copy link
Contributor

stklcode commented Dec 17, 2024

I got a question according your wiring: Was there anything connected to the Z+ pin before you connected the BLTouch?

The code indicates that "Z+" (D19) is used for Y endstop and the BLTouch reuses the Z_MIN connector.
That's why Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN, Z_SAFE_HOMING and Z_MIN_ENDSTOP_INVERTING false are defined.


Regarding the VSCode stuff: no idea, didn't use it for years (I typically just open the project in CLion and run PlatformIO from shell)

mega2560 is default in upstream Marlin project, but it does not exist in our config. In this repo it should be all of "our" supported environments

platformio.ini

[platformio]
...
default_envs  =
  MEGA_1G
  ...
  4MAXP2_DGUS_TMC_BLT_11

You can always specify one or more specific targets. This command should do the job: (or replace default_envs = ... with a single target)

pio run --environment 4MAXP2_DGUS_BLT_10

@dennislia
Copy link
Author

dennislia commented Dec 17, 2024 via email

@dennislia
Copy link
Author

dennislia commented Dec 18, 2024 via email

@dennislia
Copy link
Author

dennislia commented Dec 18, 2024 via email

@dennislia
Copy link
Author

dennislia commented Dec 18, 2024 via email

@stklcode
Copy link
Contributor

stklcode commented Dec 19, 2024

HOMING End location: when homing, now the hot end goes to the far left(X=0), then full forward(Y=0) and then to the middle of the bed(X halfway,Y halfway) where it twice exercises the BLTouch probe and stops ...

That’s intentional. When the BLTouch is used for homing, it might not hit the hotbed at X/Y 0. so SAFE_HOMING is enabled and Z homing is performed in the middle of the bed instead.

I would rather find a wiring where the original Z endstops can be used and not use the probe for leveling, bust - as said before - I have no 4Max, so I can’t really figure out how it could/should be done.

(see video)

Which video? Think there’s some issue with mail responses, no formatting at al and no attachments.

I think I read somewhere that the firmware default was around 20mm ... I have the probe lined up with the nozzle on the X axis, so I think that's ok ...- I think Y Offset is a problem, since I think the probe will be out of the print area when running auto bed leveling from the LCD Special Menu ... how to handle this?

Actually it’s X -2 Y -25 Z -0.4

#define NOZZLE_TO_PROBE_OFFSET { -2, -25, -0.4 } // https://www.thingiverse.com/thing:2824005

Can be overwritten via GCode M851 ( https://marlinfw.org/docs/gcode/M851.html )

@dennislia
Copy link
Author

Hi Stefan and Oliver,

I am pretty much finished with getting BLTouch with New Special Menu to work and tested on my 4MAX Pro 2.0.

I have created a branch, off of the Fork that I made off your code, and released builds for just the 4MAX BLT versions at https://github.com/dennislia/Marlin-2-0-x-Anycubic-i3-MEGA-S-Fork/tree/new-special-menu . Wiki at https://github.com/dennislia/Marlin-2-0-x-Anycubic-i3-MEGA-S-Fork/wiki .

If you are interested in reviewing and considering adopting the changes, I’d appreciate your comments and recommendations, on how to proceed.

Note: I think that every line that I touched I added “//dsl” so that all my changes could easily be found by Find-In-Files.
6 files were changed:

  1. platformio.ini (forgot to add "//dsl"),

  2. Configuration_adv.h,

  3. Configuration.h,

  4. Version.h,

  5. anycubic_touchscreen.cpp

  6. anycubic_touchscreen.h.

I changed a lot of the macro definitions to be consistent with the new screen menu selections text.

Thanks for your support.

Denny
PS( I couldn't find any other way to communicate with you about this ... ie...no email or messaging vehicle in Github ... hope this is ok)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants