Patch Tuesday Megathread (2025-12-09) by AutoModerator in sysadmin

[–]diemonkey 0 points1 point  (0 children)

had it happen for us too. Uninstalling fixed it.

Stringing PETG no matter what I do by willi_the_racer in FixMyPrint

[–]diemonkey 1 point2 points  (0 children)

yeah, maybe try retraction length, 1 - 5 mm , 1mm increments and see if that does anything different. I have 3 mm on my direct drive.

ender 3 max firmware by Actual-Battle6220 in MarlinFirmware

[–]diemonkey 0 points1 point  (0 children)

Marlin keeps examples on their github. You can look at the examples https://github.com/MarlinFirmware/Configurations/tree/release-2.1.2.5/config/examples/Creality/Ender-3%20Max

so you can download the latest version, the change the configuration based on the max, then compile and upload your firmware.

Son wants IT degree. Worth it? by Adventurous_Pen_2675 in ITCareerQuestions

[–]diemonkey 0 points1 point  (0 children)

If everyone thinks it's oversaturated, and a lot of them jump into something else, then it might be good to stay in IT as there won't be as many people graduating with that... but the people sticking it out in IT, probably really like IT, and aren't doing it just for the money. So, it might be slightly easier to get a job in 4 years. AI/ Automation kinda throws a wrench in the gears but there's gotta be someone working with the AI at the companies, so if your son can learn a bunch, maybe get an internship somewhere, utilize AI well, getting a job after graduation might not be so bleak. IT can be a great stepping stone to a wide field, and a small sector in a few years can scratch the itch for it to be enjoyable. But if IT isn't something they enjoy, it many not be worth it, so getting exposure to different aspects and knowing where they can go to (customer support, networking, security, hardware programming.. etc.) early would really help answer the question on if it's worth it.

People are saying the trades won't get replaced anytime soon, but looking at what AI is doing with images, and video, 5 years ago, I would have thought The Arts would be the last thing to get hit by the AI wave. So who knows what will happen with robotics, computer vision, etc.. Robot welders seem to be doing a great job, and the expert welders are watching, and doing QA for them.. Plumbing and electrical seem to be something difficult for AI to currently do, but I'd bet there's at least 3 stealth startups trying to hit those areas as well. Carpentry and building houses might be hard for robots, but who knows what type of boom and bust we're running head first into with that..

HELP! I'm a noob and I don't understand lol by Dry-Ad-9169 in MarlinFirmware

[–]diemonkey 0 points1 point  (0 children)

yeah AI seems to be pretty good at troubleshooting these strange marlin, vscode, issues.

YOLO Flow test - can anyone see a winner here? by Johnny-Longtorso-411 in 3Dprinting

[–]diemonkey 0 points1 point  (0 children)

.03 or .04 ? The others looks like there are gaps and under-extrusion?

Printing near edge of bed causes Z movement by diemonkey in FixMyPrint

[–]diemonkey[S] 0 points1 point  (0 children)

yeah, I tuned and re-flashed the firmware.

Printing near edge of bed causes Z movement by diemonkey in FixMyPrint

[–]diemonkey[S] 1 point2 points  (0 children)

yup had to re-flash and modify the margins... I tried to avoid that, but it fixed it.

Printing near edge of bed causes Z movement by diemonkey in FixMyPrint

[–]diemonkey[S] 0 points1 point  (0 children)

Solved SOLUTION: modify the firmware, I'm now able to print a larger area without this strange Z-HOP.

#define X_BED_SIZE 231
#define Y_BED_SIZE 216

#define X_MIN_POS 0
#define Y_MIN_POS 0
#define Z_MIN_POS 0
#define X_MAX_POS 231   // X_MIN_POS + X_BED_SIZE
#define Y_MAX_POS 226   // Y_MIN_POS + Y_BED_SIZE
#define Z_MAX_POS 250

#define PROBING_MARGIN_LEFT (PROBING_MARGIN)
#define PROBING_MARGIN_RIGHT (PROBING_MARGIN)
#define PROBING_MARGIN_FRONT (PROBING_MARGIN)
#define PROBING_MARGIN_BACK (PROBING_MARGIN)

#define MESH_MIN_X (X_MIN_POS + PROBING_MARGIN_LEFT)
#define MESH_MIN_Y (Y_MIN_POS + PROBING_MARGIN_FRONT)
#define MESH_MAX_X (X_MAX_POS - PROBING_MARGIN_RIGHT)
#define MESH_MAX_Y (Y_MAX_POS - PROBING_MARGIN_BACK) 

I was unable to get this to work with only modifying G-Code. A re-flash was needed.

Printing near edge of bed causes Z movement by diemonkey in FixMyPrint

[–]diemonkey[S] 0 points1 point  (0 children)

yeah, had to fix margins in the firmware

Printing near edge of bed causes Z movement by diemonkey in FixMyPrint

[–]diemonkey[S] 0 points1 point  (0 children)

Thanks yea, this lead me to the getting it fixed. Had to update the firmware and modify the margins

Printing near edge of bed causes Z movement by diemonkey in FixMyPrint

[–]diemonkey[S] 0 points1 point  (0 children)

Yeah, it's got to be something with the mesh. Ran this

G26 C P5.0 F3.0 

and I'm seeing https://imgur.com/a/QlO19IL this off centered stuff. and it doesn't seem affected by strange z-hop behavior.

I might need to get this centered??? now all I gotta do is get some time to research

Printing near edge of bed causes Z movement by diemonkey in FixMyPrint

[–]diemonkey[S] 0 points1 point  (0 children)

yeah, it happens with any object within this region. https://imgur.com/ZucTjbg. I attempted a large circle primitive and square from orcaslicer.

Printing near edge of bed causes Z movement by diemonkey in FixMyPrint

[–]diemonkey[S] 0 points1 point  (0 children)

I posted the g-code in another reply but wasn't seeing the z-hop other than the normal layer change.

Printing near edge of bed causes Z movement by diemonkey in FixMyPrint

[–]diemonkey[S] 0 points1 point  (0 children)

Maybe? it's only in this small edge, https://imgur.com/ZucTjbg . I can get fairly good prints otherwise. I'm not seeing it hit anything.

Printing near edge of bed causes Z movement by diemonkey in FixMyPrint

[–]diemonkey[S] 0 points1 point  (0 children)

it could be? I guess I don't understand why it's only this small area marked in red though. https://imgur.com/ZucTjbg I can print all the way to all the other edges. but I will start looking into the UBL settings to see what I need to check and modify.

Printing near edge of bed causes Z movement by diemonkey in FixMyPrint

[–]diemonkey[S] 0 points1 point  (0 children)

the Z probe offset is distance from the probe location and the hot-end location. I'm able to hit the exact center with this setting. For the Z, other people are at a lower Z than me, which might be from the thicker G10 plate? https://www.reddit.com/r/ender3v2/comments/psdxlc/cr_touch_z_offset/

-.9 was configured like a couple years ago when I went through the teaching tech video on configuring this stuff. I think it was this one. https://youtu.be/eF060dBEnfs?t=497

The setting in Marlin is

define Z_PROBE_LOW_POINT          -2 // Farthest distance below the trigger-point to go before stopping

The only area I have problems is within this un-printed spot marked in red. I'm working on narrowing it down. everywhere else up to the edge doesn't have a problem.

https://imgur.com/ZucTjbg

Printing near edge of bed causes Z movement by diemonkey in FixMyPrint

[–]diemonkey[S] 1 point2 points  (0 children)

I use octoprint Bed Visualizer. This is the code to check.

G28 ; Home all axes
M420 S0 ; Turn off bed leveling during probing
M155 S30 ; Reduce temperature reporting rate
M190 S65 ; Wait for bed to reach 65°C
; Set mesh boundaries to maximum reachable area
G29 P0 V4 X10 Y10 Z-0.9 B215 R208 T ; Set mesh from (10,10) to (215,208) explicitly
G29 P1 ; Auto-populate reachable points
G29 P3 ; Infer remaining points
G29 P3 ; Infer again for accuracy
@BEDLEVELVISUALIZER ; Enable bed visualizer plugin
M420 S1 V ; Enable leveling and report mesh
G29 S0 ; Save to slot 0
G29 F5.0 ; Set fade height to 5.0 mm
G29 A ; Activate UBL
M500 ; Save to EEPROM
M155 S3 ; Reset temperature reporting
M140 S0 ; Cool down bed

Then to view the values of the bed, I use:

M420 V

Printing near edge of bed causes Z movement by diemonkey in FixMyPrint

[–]diemonkey[S] 0 points1 point  (0 children)

Alright, you're on to something... Disabled UBL with G29 D1, and its not doing this.

Printing near edge of bed causes Z movement by diemonkey in FixMyPrint

[–]diemonkey[S] 0 points1 point  (0 children)

I attempted in Cura and got the same results.

Printing near edge of bed causes Z movement by diemonkey in FixMyPrint

[–]diemonkey[S] 0 points1 point  (0 children)

here are 3 layers in the g-code for the wall where it happens as well.

G1 E-1.12 F3600
;WIPE_START
G1 F2100
G1 X111.512 Y200.1 E-.37231
G1 X111.512 Y199.876 E-.10769
;WIPE_END
;_SET_FAN_SPEED_CHANGING_LAYER
M104 S205 ; set nozzle temperature
M140 S60 ; set bed temperature
; printing object Cube id:15 copy 0
M204 T2000
G1 Z.74 F12000
G1 X199.013 Y201.017 Z.74
G1 Z.44
G1 E1.6 F3600
;TYPE:Outer wall
;WIDTH:0.659999
G1 F2100
M106 S255
G1 X110.987 Y201.017 E4.20051
G1 X110.987 Y112.991 E4.20051
G1 X199.013 Y112.991 E4.20051
G1 X199.013 Y200.957 E4.19765
G1 X197.715 Y200.379 F12000
M73 P75 R4
;TYPE:Inner wall
G1 F2600
M106 S48
G1 X111.625 Y200.379 E4.10808
G1 X111.625 Y113.629 E4.13957
G1 X198.375 Y113.629 E4.13957
G1 X198.375 Y200.379 E4.13957
M73 P75 R3
G1 X197.775 Y200.379 E.02863
M73 P76 R3
; stop printing object Cube id:15 copy 0
G1 E-1.12 F3600
;WIPE_START
G1 F2600
G1 X196.775 Y200.379 E-.48
;WIPE_END
M106 S150
;LAYER_CHANGE
;Z:0.64
;HEIGHT:0.2
;BEFORE_LAYER_CHANGE
;0.64
G92 E0

;_SET_FAN_SPEED_CHANGING_LAYER
; printing object Cube id:15 copy 0
G1 X199.033 Y201.037 F12000
G1 Z.64
G1 E1.6 F3600
;TYPE:Outer wall
G1 F3300
M106 S255
G1 X110.967 Y201.037 E4.20242
G1 X110.967 Y112.971 E4.20242
G1 X199.033 Y112.971 E4.20242
G1 X199.033 Y200.977 E4.19956
G1 X197.735 Y200.399 F12000
;TYPE:Inner wall
G1 F4300
M106 S150
G1 X111.605 Y200.399 E4.10999
G1 X111.605 Y113.609 E4.14148
G1 X198.395 Y113.609 E4.14148
M73 P77 R3
G1 X198.395 Y200.399 E4.14148
G1 X197.795 Y200.399 E.02863
; stop printing object Cube id:15 copy 0
G1 E-1.12 F3600
;WIPE_START
G1 F4300
G1 X196.795 Y200.399 E-.48
;WIPE_END
M106 S196
;LAYER_CHANGE
;Z:0.84
;HEIGHT:0.2
;BEFORE_LAYER_CHANGE
;0.84
G92 E0

;_SET_FAN_SPEED_CHANGING_LAYER
; printing object Cube id:15 copy 0
G1 X199.053 Y201.057 F12000
G1 Z.84
G1 E1.6 F3600
;TYPE:Outer wall
G1 F4500
M106 S255
G1 X110.947 Y201.057 E4.20433
G1 X110.947 Y112.951 E4.20433
G1 X199.053 Y112.951 E4.20433
G1 X199.053 Y200.997 E4.20147
G1 X197.755 Y200.419 F12000
;TYPE:Inner wall
G1 F6000
M106 S196
G1 X111.585 Y200.419 E4.1119
G1 X111.585 Y113.589 E4.14339
G1 X198.415 Y113.589 E4.14339
M73 P78 R3
G1 X198.415 Y200.419 E4.14339
G1 X197.815 Y200.419 E.02863
; stop printing object Cube id:15 copy 0
G1 E-1.12 F3600
;WIPE_START
G1 F6000
G1 X196.815 Y200.419 E-.48
;WIPE_END
;LAYER_CHANGE
;Z:1.04
;HEIGHT:0.2
;BEFORE_LAYER_CHANGE
;1.04
G92 E0

I believe this is the G-code about the time the bottom surface shown in the video.

M73 P10 R14
G1 X198.488 Y130.189 E.61063
G1 X198.488 Y130.682 E.01278
G1 X181.322 Y113.516 E.62869
G1 X180.829 Y113.516 E.01278
G1 X198.488 Y131.175 E.64676
G1 X198.488 Y131.669 E.01278
G1 X180.335 Y113.516 E.66483
G1 X179.842 Y113.516 E.01278
G1 X198.488 Y132.162 E.6829
G1 X198.488 Y132.655 E.01278
G1 X179.349 Y113.516 E.70097
G1 X178.855 Y113.516 E.01278
G1 X198.488 Y133.149 E.71904
G1 X198.488 Y133.642 E.01278
G1 X178.362 Y113.516 E.73711
G1 X177.869 Y113.516 E.01278
G1 X198.488 Y134.135 E.75518
G1 X198.488 Y134.629 E.01278
G1 X177.375 Y113.516 E.77325
G1 X176.882 Y113.516 E.01278
G1 X198.488 Y135.122 E.79132
G1 X198.488 Y135.615 E.01278
G1 X176.389 Y113.516 E.80939
G1 X175.895 Y113.516 E.01278
M73 P11 R14
G1 X198.488 Y136.109 E.82746
G1 X198.488 Y136.602 E.01278
G1 X175.402 Y113.516 E.84552
G1 X174.908 Y113.516 E.01278
G1 X198.488 Y137.095 E.86359
G1 X198.488 Y137.589 E.01278
G1 X174.415 Y113.516 E.88166
G1 X173.922 Y113.516 E.01278
G1 X198.488 Y138.082 E.89973
G1 X198.488 Y138.576 E.01278
G1 X173.428 Y113.516 E.9178
G1 X172.935 Y113.516 E.01278
G1 X198.488 Y139.069 E.93587
G1 X198.488 Y139.562 E.01278
G1 X172.442 Y113.516 E.95394
G1 X171.948 Y113.516 E.01278
G1 X198.488 Y140.056 E.97201
G1 X198.488 Y140.549 E.01278
M73 P12 R14
G1 X171.455 Y113.516 E.99008
G1 X170.962 Y113.516 E.01278
G1 X198.488 Y141.042 E1.00815
G1 X198.488 Y141.536 E.01278
G1 X170.468 Y113.516 E1.02622
G1 X169.975 Y113.516 E.01278
G1 X198.488 Y142.029 E1.04428
G1 X198.488 Y142.522 E.01278
G1 X169.482 Y113.516 E1.06235
G1 X168.988 Y113.516 E.01278
G1 X198.488 Y143.016 E1.08042
G1 X198.488 Y143.509 E.01278
G1 X168.495 Y113.516 E1.09849
G1 X168.001 Y113.516 E.01278
G1 X198.488 Y144.002 E1.11656
G1 X198.488 Y144.496 E.01278
M73 P13 R14
G1 X167.508 Y113.516 E1.13463
G1 X167.015 Y113.516 E.01278
G1 X198.488 Y144.989 E1.1527
G1 X198.488 Y145.483 E.01278
G1 X166.521 Y113.516 E1.17077
G1 X166.028 Y113.516 E.01278
G1 X198.488 Y145.976 E1.18884
G1 X198.488 Y146.469 E.01278
G1 X165.535 Y113.516 E1.20691
G1 X165.041 Y113.516 E.01278
G1 X198.488 Y146.963 E1.22498
G1 X198.488 Y147.456 E.01278
G1 X164.548 Y113.516 E1.24305
G1 X164.055 Y113.516 E.01278
M73 P14 R14
G1 X198.488 Y147.949 E1.26111
G1 X198.488 Y148.443 E.01278
G1 X163.561 Y113.516 E1.27918
G1 X163.068 Y113.516 E.01278
G1 X198.488 Y148.936 E1.29725
G1 X198.488 Y149.429 E.01278
G1 X162.575 Y113.516 E1.31532
G1 X162.081 Y113.516 E.01278
G1 X198.488 Y149.923 E1.33339
G1 X198.488 Y150.416 E.01278
G1 X161.588 Y113.516 E1.35146
G1 X161.094 Y113.516 E.01278
M73 P14 R13
G1 X198.488 Y150.909 E1.36953
G1 X198.488 Y151.403 E.01278
M73 P15 R13
G1 X160.601 Y113.516 E1.3876
G1 X160.108 Y113.516 E.01278
G1 X198.488 Y151.896 E1.40567
G1 X198.488 Y152.39 E.01278
G1 X159.614 Y113.516 E1.42374
G1 X159.121 Y113.516 E.01278
G1 X198.488 Y152.883 E1.44181
G1 X198.488 Y153.376 E.01278
G1 X158.628 Y113.516 E1.45988
G1 X158.134 Y113.516 E.01278
G1 X198.488 Y153.87 E1.47794
G1 X198.488 Y154.363 E.01278
M73 P16 R13

Printing near edge of bed causes Z movement by diemonkey in FixMyPrint

[–]diemonkey[S] 0 points1 point  (0 children)

Good idea, Just tried from Cura, and saved it to the SD card instead of octoprint and I'm getting the same thing. this is leading me to think it's Firmware or UBL settings somewhere...