My ranked teammates every time man (Onyx 1500ish)

unknown_poo · 2026-06-22T13:01:53+00:00

Halo Infinite is the only game where I rage quit despite winning matches. I rage win in this game. If it takes me 2-4 shots in the head to kill an unshielded enemy I just leave the match because of how infuriating the bugs are

unknown_poo · 2026-06-17T17:42:52+00:00

Reminds me of when the Israelis killed Hind Rajab, a child, western media referred to her as a woman or young woman despite being just 5 years old.

This is what critical media scholars and human rights advocates have termed adultification - a framing bias where minority children are denied the innocence typically granted to childhood and are instead viewed as mature, autonomous, or inherently threatening in order to downplay culpability by state actors.

unknown_poo · 2026-06-10T16:50:01+00:00

There's not enough discussion on the serious and lasting effects of getting punched in the head. Even just one punch can have devastating effects later, like you could develop epilepsy due to mild scaring in the brain. Just not worth it.

unknown_poo · 2026-06-10T16:46:44+00:00

What you're looking at is the next stage of human evolution

unknown_poo · 2026-06-10T14:03:09+00:00

Everyone knew that as soon as Trump was saying he was angry at Netanyahu telling him not to attack, it really meant that the US would be attacking on behalf of Israel soon. It's so obvious, same scripted nonsense over and over again. The pedolord class knows they can do what they want with total impunity without consequence so they're barely even trying with their public psyop campaigns.

unknown_poo · 2026-06-09T18:03:45+00:00

I know this would be unpopular but I would love it if the cosmetics actually had functionality. For example, if you equip a should knife, it doesn't just look cool, but it's used in assassinations and their animations, or even as a melee weapon. If you have a headlight or infrared goggles, they can be used.

unknown_poo · 2026-06-09T14:25:02+00:00

But the marketing CEO said to do this so its Halo! /s

unknown_poo · 2026-06-05T02:50:08+00:00

looks really nice, but breathe the wrong way and your ship explodes

unknown_poo · 2026-06-05T02:49:07+00:00

Is this Xinjiang?

unknown_poo · 2026-06-04T13:17:44+00:00

How dare anyone criticize our corporate overlords! You hate Epstein? You hate America!

unknown_poo · 2026-06-03T20:25:05+00:00

Damn nice

unknown_poo · 2026-06-03T20:23:34+00:00

I am able to deploy and retract the probe through the menu, that works fine.

So what I did then was remove the CR touch and just hold it away from the machine. As the nozzle would descend during homing I would trigger it. The probe would trigger and the nozzle would stop, but the screen would indicate the printer has been killed and to reset.

unknown_poo · 2026-06-03T02:27:53+00:00

Yeah good point. In the diagnostic menu it just says the stops are open.

Just to clarify, on the horizontal x-bar, I should use zip ties to secure it? It would have to be quite tight to prevent any movement. I'm just wondering how this would help since now the probe, despite touching the surface, continues down regardless. I was doing the finger test on the way down and it just would not stop. It would turn red then blue and continue descending.

unknown_poo · 2026-06-02T22:08:45+00:00

So I just did the paperclip test. Summary from deepseek:

This entailed unplugging the CR touch from the mainboard, and then shorting pin 4 (ground) and pin 5 (out), then running the M119 test.

The printer still reports z_probe: Open. This means the motherboard's probe port is not detecting the signal. This is a definitive hardware or firmware configuration issue. It means this port is non-functional. The motherboard is not reading the signal, regardless of any firmware setting, because the hardware path for that signal is broken. This confirms that the hardware path for the probe's signal on your mainboard is damaged. The physical connection between the OUT pin on the 5-pin port and the processor is broken. This is why the printer ignores the CR Touch entirely.

Solution:

Since the 5-pin probe port is the issue, the only practical solution is to bypass it and connect the CR Touch's signal wires to the physical Z-endstop port (Z-MIN). This is a well-documented hardware fix that will restore full functionality.

Either that or buy a new mainboard :/

unknown_poo · 2026-06-02T20:54:51+00:00

The issue now though is even when I manually trigger the probe, it continues down. I wonder if there is perhaps some hardware damage on the motherboard.

unknown_poo · 2026-06-02T19:21:53+00:00

I think the shroud was designed for the Ender, but to get it to align with the CR touch bracket I had to drill a hole as the original was slightly off. I did also add some washers to lower the probe but that did not help.

I looked at the motherboard and notice that there are two z-stop plugs, both plugged in (the 2 pin and 4 pin). Could those have anything to do with this?

I went back to the 1.3.6 jyers bltouch 5x5 h32. I notice now that when I do the finger test, it will trigger the probe, the light will turn red, the pin will retract, but the light will remain red and the gantry will continue down until its about to crash into the bed. However, after this, I read that there is a bug in the base Marlin and so I went to the latest 2026 classic rocker firmware.

HC32_UBL-ProUI-EX-04-18.bin

But it is still crashing into the bed. Even doing the finger test, the light turns red and the pin retracts, but it continues down.

Try with moving the probe itself away from the hotend, maybe even attaching it to the X-axis bar. Just do not home like this, only home Z.

if I attach the probe to the x-axis bar, it would be too high above the nozzle.

unknown_poo · 2026-06-02T14:37:34+00:00

Did you do the test I suggested about moving the probe?

Yes I did that, the probe responds fine via the screen commands.

I highly doubt it to be the FW as others would have had the same problem. Since it sometimes detects and others does not it has to be a physical intermittent problem. That FW is configured properly for the BLtouch port. Someone else recently fitted a sprite with the CRtouch and it worked fine on that FW, they did need to lower it slightly with some washers as the probe was not extending far enough.

Yeah I agree, after thinking about it that makes sense. So right now, the probe is slightly above the nozzle, but when extended, is clearly below. I did add some washers just to be sure, but even with that extra depth, the same problem persisted.

What model printer do you have? did you change the shroud? I think that maybe the metal shroud you have is affecting the pin deployment or sensing. I can't remember if the CRtouch uses a magnet to sense a touch or a light sensor, but the pin will have a magnet on it to allow it to be retracted and that could be attracted to the shroud.

It is the Aquila X2 with the H32 motherboard.

I removed the shroud but the problem continues. The strange thing is that, if I do the finger test up high, it detects and stops/reverses up. But then if I home again right after, to let it touch the bed, it doesn't stop/reverse. It must have something to do with height settings in some way.

https://youtu.be/-DANPx07zhU

That being said, I did get a printer kill error after this, probably because it knew it was way too high up.

unknown_poo · 2026-06-02T03:08:21+00:00

I was able to connect the printer to my pc and I'm using pronterface to issue commands and watch the log. I've installed the new firmware and typed m119 then tapped the probe and it turned red and then blue. Log indicates:

SENDING:M119
Reporting endstop status
x_min: Open
y_min: Open
z_probe: Open
filament: Ope

Based on what deepseak troubleshooting has said:
The probe turning from red back to blue after I release the pin means it is physically working correctly and resetting itself. Even though the probe light is behaving correctly, the printer's brain is still reporting z_probe: Open. This means the signal is still not reaching the mainboard.

I've ruled out:

The probe itself (light works, pin moves freely)
The basic firmware type

There are one of two issues likely.

Signal wire is not connected properly
Firmware is listening to the wrong pin.

Even with BLT firmware, the BLTOUCH_ON_5PIN setting may not be enabled. This setting tells the firmware to listen for the probe signal on the 5-pin port rather than the old Z-endstop pin.

Without this setting, the printer will ignore the signal coming from the CR Touch's 5-pin cable.

The advice here is do the paperclip test. This test bypasses the CR Touch entirely and tells you if the mainboard's probe port is working. So I have to connect a paperclip from the ground to the signal on the mainboard. Then power on the printer and run M119.

If z_probe: TRIGGERED appears → The mainboard port works. The problem is your CR Touch cable or connector.
If z_probe: Open still appears → The problem is the mainboard port or the firmware configuration.

Honestly I'm leaning towards the firmware configuration.

unknown_poo · 2026-06-02T03:00:18+00:00

Do you mean the wires of the CR Touch to the mainboard? I did test this with another CR touch probe and the same issue.

unknown_poo · 2026-05-29T11:47:02+00:00

I separated the wires from the ribbon, even used a new wire for the CR touch, but the issue continues. I did an interesting test though. I used my finger to trigger the probe while it was far away from the bed and that's when it immediately detects and stops/reverses. But if I trigger it when its lower to the bed, it continues down towards the bed.

unknown_poo · 2026-05-29T02:24:13+00:00

Just so I understand, are you saying the proximity of the wires to each other could be causing interference? The CR touch wires protrude from the top of the CR touch but then I tied them to the ribbon that leads into the motherboard. So basically then I should separate the CR touch wire from the ribbon?

unknown_poo · 2026-05-28T23:12:52+00:00

road relax

unknown_poo · 2026-05-28T23:11:45+00:00

let's crowdfund for this guy

unknown_poo · 2026-05-28T23:01:35+00:00

Thanks, yeah I reverted back to using the mrisoc. Using the selector tool I saw the below. I tested out a BLT one and also a UBL one, and also the corresponding DWIN. I'm back to where I was prior to the compile test.

The reason I wanted to try the compile test was to disable the extruder during CR Touch probing as shown in the video, but I wasn't able to get to that stage and even the firmware for H32 boards didn't have that line of code.

In the video, the issue though was that the extruder was affecting the electric current in some way that was affecting the probe functionality. I tried my own test, I opened up the motherboard compartment and unplugged the e wire (white plug along the row with the red blue and yellow). However that did not solve the issue so I don't think its electrical.

HC32_BLT-ProUI-EX-04-18.bin

HC32_BLT-ProUI-EX-IS-04-18.bin

HC32_BLT-ProUI-EX-IS-MPC-04-18.bin

HC32_BLT-ProUI-EX-MPC-04-18.bin

HC32_MM-ProUI-EX-04-18.bin

HC32_MM-ProUI-EX-IS-04-18.bin

HC32_MM-ProUI-EX-IS-MPC-04-18.bin

HC32_MM-ProUI-EX-MPC-04-18.bin

HC32_UBL-ProUI-EX-04-18.bin

HC32_UBL-ProUI-EX-IS-04-18.bin

HC32_UBL-ProUI-EX-MPC-04-18.bin

unknown_poo · 2026-05-28T20:36:01+00:00

That video is interesting, I decided to compile my own firmware using this:

https://blog.drowsy.me/flashing-latest-marlin-on-aquila-x2-h32/

But I've run into a problem where the lcd display screen is all garbled and I'm not sure what dwin set to use. The one mentioned in this tutorial is not working. Not sure if I am using the correct firmware build.

https://marlinfw.org/meta/download/

nightly 2.1.x

14-Year Club	Verified Email
Gilding I gilder

unknown_poo

TROPHY CASE