Locked In Print

What is this? I love a good experiment but would love to know what I am getting into haha

 

Yeah I want to give this a try... I have a spare image that was working perfectly that I can swap out to if I have to

 

The only file in the zip was r2rpinew.WfV9HPt7.zip.part

 

nevermind, I have the image

 

Alright, I flash the card and just booted it up... This may take some getting used to haha.

Completely different menu, it's OctoScreen

A few first impressions... The Z offset does not work. It crashes into the bed and the on screen menu to increase or decrease the offset does nothing.

I kind of miss the simplicity of the robo menu but I would love to try and make this work

 

Additionally I cannot SSH into the pi because the default password is not working.

I don't feel like hacking into it so I think I will just go to another image unless you have some insight

 

Well, I am pretty sure my luck ran out....

Swapped to the old image and now the Pi will NOT power up... I am guessing that means this thing is fried

 

Uh oh... this is what I was worried about... the control board shows power, the pi does not when the power switch is on...

I pulled the pi since I have a spare that is identical, but just for Sh*ts and Giggles, I connected the pi to a 5v power supply by itself... it powers up..... Did the 5v power on the board burn out?

 

Yep, swapped the Pi, it does not power up... WTF, not sure how that would have happened...

So, I am not going to bust out the multimeter yet but aside from swapping out the control board with the PartsBuilt one, do I have another option for 5V power on this board?

 

Sorry for all the posts... I did a step by step power up... I am fine and the Pi stays on until the ribbon cable gets plugged in, then it shuts down

If I unplug the ribbon cable, it powers back up. Now the question is whether the screen is shorted and causing it or the cable... I would prefer it be the cable

 

Wow this has become the page of Ben... I figured out the screen issue... I won't say the cause since it was my fault but it is up and running now with a standard R2 image, SSH enabled, and VNC enabled