ironhydroxide

I had the atom XL for a while, it was ok. Battery life was awesome, but it was hobcobbled together software wise and not actually rugged (both mine and it's warranty replacement broke their screens from a 3' fall out of my pocket stooped over). Their support sucked as well. 3 months after shipping my phone back for warranty they approved the replacement and then shipped out the replacement.

Hardware is a Pi4, 4GB. I've looked through the log, don't know how to upload file here for you to look through it, and it's too long for character limit. It does indicate issues with the serial port, either permission denied in the case i tried tty0 symlink, or no such file or directory when going strait to the serial/by-id.

I've tried many setups. First was following https://www.klipper3d.org/Installation.html#obtain-a-klipper-configuration-file With octopi. Next was another guide that I can't seem to find the link to again. But was a default raspbian lite x32, and installing klipper and mainsail on top with kiauh. next was this guide https://www.obico.io/blog/install-klipper-ender-3/ which I modified for the Ender5+ (what processor to compile for)

I've had varying success, initial try the USB wouldn't show in serial/by-id, I swapped cables and still had no entry. Swapped cables back and tried the next guide/OS, and that gave me the entry in serial/by-id.

also I Tried using the symlink tty0, but that didn't work either.

For the current OS/Setup I think i've messed with too many things, and just need to start over from fresh OS. But I can't think of anything different to try.

Found the port ID by ls /dev/serial/by-id/* I only have one usb device connected, the printer.

I didn't make a new line in the printer.cfg, just edited the [mcu] serial: /dev/serial/by-id/usbXXXXXXXX To match the id I found in the previous command.

Jack and charger ports can be controlled by the phone to turn off if there is low resistance (ie water) between contacts.

A battery is harder, as it's what provides the power to the thing that decides whether to turn off the port. Not that it's impossible to put some smarts into a battery, to decide when to power the output. But it's going to add a lot of complexity and bulk to do it (switching circuit, logic circuits, etc)

Just like the muskrat. If he does, you can bet he will either game the vote, or not actually step down when the vote goes against him.

I see it as a longevity thing.

Sure you can bring another battery pack with you and charge your device from it, but at some point your internal battery will be degraded enough that it essentially needs to be plugged in to function, which is not feasible.

Being able to easily replace the thing in the device that wears out fastest is a good thing.

Granted I expect if this does go through, that mfg will make the battery hard to replace by other means (ie drm locks) making sure they can nickel and dime the consumer all the way.

How does one apprehend confusion?