R2 Connection Interrupted...Reset from LCD, good until next boot up?

Searched forums and attempted all of the recommended fixes. Check cables, Pi, Robo Board etc...

When I first turn it on the unit says Connection Interrupted
Reset from the LCD clears the issue and it will print fine all day.

Power on the next morning and same sequence over again.

Any Ideas why it may be a first boot issue only?

 

Yes, using Wifi and has full signal. Device is about 20 ft from the router.
Out of the box it did not have this issue.

 

Yes, it is running the latest update.

 

You should have more info on the screen that it would help if you mentioned.

Also whether you're trying to print and at what temps when it happens.

 

It happens when I first power on the Robo3D. The screen says Connection Interrupted and has the Reset button and nothing else. If I touch the reset button, it resets and works fine until it is powered off again. Thursday morning did a reset, printed all day Friday and Saturday morning on first boot, same message.

 

I'd check the pogo pins to make sure that they're not damaged.

 

I’m getting same thing except mine won’t reset at all.
What did you figure out? I just put a new hot end on when mine started doing this

 

I wonder if it's a race condition upon the initial power-on and the Robo board isn't ready when the Raspberry Pi starts trying to connect with it. Resetting the Raspi then clears the "problem" since the Robo board is now available. Not sure what to suggest other than possibly adjusting OctoPrint's "connect on startup" option to turn that off. And then in OctoPrint click the Connect button (but that's about the same amount of work, to be honest).

At least, once you're in OctoPrint then check the logs; they might tell you something interesting.

 

I took the wires off the old hot end and put them on the new hot end and it’s working now. Also had to swap out the brass insert at the top of the aluminum cooling block. So I wonder if I got the wrong set up. Regardless it is working now.

 

I never figured mine out, logs were sent to Robo3D but they didn't see anything. I just reset it and move on. Will take more time after the first of the year to work on it.
OutsourcedGuru I think is on the right track, sounds like a timing issue in the communications.

 

More like a bad contact or other issue with heater wiring I'd say, "communication timing" makes no sense at all.

 

Could this be a pogo pin not making contact and delaying the heat-up? Would it show itself this way?

 

Yep.

OP wasn't clear enough to provide good input though. His posts suggests it appears straight after bootling, but I suspect it's the first time he actually tries to print something. Can't explain much if we don't have precise info.