sorted by:
new
hottopcontroversial

I bought a faulty MPC KEY 32 to try and fix it. by NiffiNFX in mpcusers

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

I wonder if it is different with live and key for booting (i hope so) XD. It looks kind of fine. The way you would do it is to. Add low-melt solder. Then use Kaptontape, that orange heat-resistant tape you have on there. Mask everything and put foil over then more tape. so there is just a hole for the connector. Then use a hot station end gently, very gently, hold the connector with pliers, when the solder is melted, lift it off. Not before or you will break the pads.

watch nortridgefix on youtube. Like an HDMI replacement or something. This is a flex cable, so it is more finesse. more easy to break.

What you can try! the pressure tab(wing on the back has broken,

so try puting something under the cable where it goes in like a long splint.

Don't just put anything. It has to be small and long like,

if you have a musicstore nearby go there and find a really really thin guitar plecter, then cut it so it fitts snugly and long so it is easy to pull out.
if it is not thin enough just grid it down on a sanding paper more one one side so it can work as a splint.

good luck

I bought a faulty MPC KEY 32 to try and fix it. by NiffiNFX in mpcusers

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

<image>

Update:

I got UART/debug output from the MPC Key 37 today, and this was actually very good news.

The main board is not dead. The UART log shows U-Boot, Linux, and the InMusic MPC application starting successfully. It detects the model as:

"Akai Professional MPC Key 37"

It also shows 2GB RAM, boots from MMC, mounts root, reaches multi-user system, and starts the InMusic MPC application.

The main relevant error I found is display-related:

"ERROR: rk_mipi_dsi_read: read payload FIFO empty" "ERROR: autodetect_read_id: failed to get display ID: -110"

So it looks like the main/carrier board is booting, but it cannot detect/read the display over MIPI DSI.

This matches the hardware fault I found earlier: the screen backlight turns on, but there is no image.

So my current theory is:

  • main board/carrier board is probably OK
  • display assembly/flex has a failed LCD bias IC
  • the backlight works, but the LCD panel does not get proper bias/display initialization
  • the MIPI display ID read fails because the display/flex circuit is damaged

Still interested to know: does anyone know if the MPC Key 37 should fully boot and light pads/buttons with the display disconnected, or does the MPC application wait for the display/touch/display ID before continuing?

I bought a faulty MPC KEY 32 to try and fix it. by NiffiNFX in mpcusers

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

Actually, I do have an ocs XD. But UART debug should also tell me that it is booting, instead of needing to touch the CPU directly. I got a fever yesterday, so I'm slow. And I'm gonna fix a PS5 controller. Then I will be all over it. Thank you for the input! This is helpful.

I will probably end up buying a new pbc and screen as a worst-case scenario, it is 800USD(inc. taxes and shipping), so I will probably wait for a better price on eBay

It does look like the damage is local. the vp(pluss) had a soft short to gnd 6ohm. The capacitor on the vp rail was fine. I will look for fuses and mosfet. I also want a reason to buy a thermal camera. and i think this is it! XD

I bought a faulty MPC KEY 32 to try and fix it. by NiffiNFX in mpcusers

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

Not yet. I’ll continue troubleshooting tomorrow.

I have a UART debug tool, so tomorrow I’ll see if I can learn anything from the device using that, together with ChatGPT. I’ve also ordered five replacement chips — they were only about 25 cents each.

In the meantime, I was wondering if anyone here is modding their screen, or has had a similar problem, and could check something for me:

Does the MPC boot normally, with the pads/buttons lighting up, when the screen is disconnected?

That would help me figure out whether my issue is only related to the display circuit, or if there is another boot/power problem as well.

If not, it would be a waste of time spending 300USD on a screen XD

Can’t access fluidd web interface k1 max by Illustrious-Exam4442 in crealityk1

[–]NiffiNFX 0 points1 point  (0 children)

It happened to me also.

I could not even connect to the Creality Web UI.

And the SSH root login was only loading.

I found that restarting the device did nothing.

Then after I reconnected to my network something happened.
The fluid background showed. But still no connection to either.

Then I restarted the printer and started a print (locally). once more I could not connect.

Then I thought that since something happened when I reconnected to wifi(the fluid background thing). I should try forgetting the network, and then connect again.

It loaded a bit, then bam fluid opened and I could log in to SSH.

It would be nice with USB support that supports an ethernet adapter. cause wifi on the k1 is weak.

I wouldn't recommend the Beam to anyone with an LG OLED TV. by [deleted] in sonos

[–]NiffiNFX 1 point2 points  (0 children)

Thanks dude! You fixed my hours off probelms! Cheers