Lost communication with MCU 'nhk

[Ho-whizzle]

Hi all,

its me again

This has happened 3 times in the past week since I upgraded to LDO Nitehawk. I will printing and the Tirdent will stop printing (no shutdown) and will display a error stating "Lost communicaiton with MCU 'nhk'"

Does anyone knwo what could be casuing and how to prevent it from happening as I cannot trust the printer to do any loong prints now.

 

[NoGuru]

Take a couple pics of your toolhead and how the Nitehawk is connected. My guess is the cable is wiggling near its connection.

 

[Pastafuzool]

Hi all,

its me again

This has happened 3 times in the past week since I upgraded to LDO Nitehawk. I will printing and the Tirdent will stop printing (no shutdown) and will display a error stating "Lost communicaiton with MCU 'nhk'"

Does anyone knwo what could be casuing and how to prevent it from happening as I cannot trust the printer to do any loong prints now.

Did you ever figure this out? I'm having the same issue now. It's not a connection issue. Unless it's on the board or a bad cable. Nitehawk 1 week old. Have about 4 hours on it printing doing calibrations. Set it for a 2hr print, and gave me this issue.

 

[Aeronut]

I had a very similar issue when I first installed my Nitehawk - I finally solved it by cleaning all the connectors with IPA, moved the USB plug on the Pi to a different port and fixed the umbilical cable to the toolhead with a dab of hotmelt glue.

 

[Pastafuzool]

I had a very similar issue when I first installed my Nitehawk - I finally solved it by cleaning all the connectors with IPA, moved the USB plug on the Pi to a different port and fixed the umbilical cable to the toolhead with a dab of hotmelt glue.

I think there is a bigger issue at play here. We all know "cleaning connectors with IPA" did nothing. Unless we all have bad USB slots on our Pi's (mine is brand new) the odds of that happening are slim to none. And my umbilical is in a gland attached to the toolhead, and the back wall exhaust, so it's not that either. I wonder, is everyone with this issue using that short cheapo USB C to A cable that comes in the nitehawk kit? I've just got the MCU error again after thinking I had resolved it. I was previously running a Pi 3 B+ with a C920, nitehawk, and beacon. Once I unplugged the camera, I didn't get the issue again. So I assumed it was because I was using an old underpowered Pi. Bought a new 4b with 4GB ram which is what I have in my other voron 2.4. I'm running hartk board and tap on that with a C920 camera, no issues.

Got the dreaded failure again tonight on a 6 hr print, 2 hrs in. I've gone ahead and swapped the USB C cable that connects the breakout board of the nitehawk to the PI with a reputable cable.
Hoping that fixes it, or it may be time to write off the nitehawk.

 

[Pastafuzool]

It did not. So it's not the cabling. It's not the power to the Pi. I've unplugged the C920 again, and it's printing fine with no MCU errors. Not really sure what is up with this Nitehawk.

 

[Pastafuzool]

And even without the camera it failed, this time after about 4 hrs out of a 6hr job.

 

[leograyc]

I had that a lot before. The root cause is actually the camera. For me it's not able underpower, it actually the camera module being shitty and occasionally send out wrong voltage on the usb line, so the Pi3's entire USB module is rebooted when this happen, which brings down all the connections.

I would say check the kernel log and also dmesg log, see at the time of MUC lost, is the system had any big bug or crashes.

 

[Pastafuzool]

I had that a lot before. The root cause is actually the camera. For me it's not able underpower, it actually the camera module being shitty and occasionally send out wrong voltage on the usb line, so the Pi3's entire USB module is rebooted when this happen, which brings down all the connections.

I would say check the kernel log and also dmesg log, see at the time of MUC lost, is the system had any big bug or crashes.

Even with the camera removed from the equation, it's doing it now. If my print job is under two hours, no sweat. Over two hours? Crash city.

 

[Aeronut]

Even with the camera removed from the equation, it's doing it now. If my print job is under two hours, no sweat. Over two hours? Crash city.

Did you get to the bottom of this issue yet? After a spell of apparently working properly, mine's just started doing it again. Going to remove the camera and change the USB lead and try that, but I'm not too hopeful.

 

[Ho-whizzle]

Apologies for the radio silence.

I have heard that many have a similar and in my case I found out that my e-motor cable was chewed up and exposed cause a short during print. To resolve this, I cut the e-motor and re-crimped it to be short and it has solved the issue! hope this helps.

 

[Aeronut]

No worries - if only mine were that simple! Since your previous post, I've tried all sorts of things, with no resolution. Last week, I removed the Nitehawk and spent two day getting a Canbus setup working. Seemed fine at first, but about 4 hours into a larger print, I got the dreaded 'Lost communication with mcu EBB-Can'. There's now very little that I've not tried, so I've now got a higher Wattage power supply on order - the 200W one which came with my kit seemed a little underspecced , so I have a 350W model on its way to me. I did check Voltage output with the existing supply and it all looked very solid on my meter, but I tweaked the output up to 24.5V just to see if that makes any difference. If the new power supply doesn't fix things, then I don't know what comes next!

 

[Ho-whizzle]

No worries - if only mine were that simple! Since your previous post, I've tried all sorts of things, with no resolution. Last week, I removed the Nitehawk and spent two day getting a Canbus setup working. Seemed fine at first, but about 4 hours into a larger print, I got the dreaded 'Lost communication with mcu EBB-Can'. There's now very little that I've not tried, so I've now got a higher Wattage power supply on order - the 200W one which came with my kit seemed a little underspecced , so I have a 350W model on its way to me. I did check Voltage output with the existing supply and it all looked very solid on my meter, but I tweaked the output up to 24.5V just to see if that makes any difference. If the new power supply doesn't fix things, then I don't know what comes next!

It seems to be a problem for both SB Toolhead board and EBB36 models. My Nitehawk was working great with no issues for 2 months then suddenly it started to lose communication again randomly then the LED on the Stealthburner stopped woking then a week later after that, the Nitehawk just died. There was a LED light showing it was powered but the communication was totally losted. What a shame about this LDO product, I had high hopes for the EBB36 version to not have this issue but looks like it is the same.

 

[thespacecowboy]

Having this problem with a nitehawk randomly. I have spares but has anyone determined what is going on?
Make that both nitehawks, suddenly.... ????

 

[RadioSaebb]

Maybe it is just interferrence (sheath Waves) caused by strong coils(like the hotendheater or the stepdown converters on the mainboard) and other Signals that are near the cables. To manage this, in radiotechnic we Cover the cables with ferrites on the start and the end. Maybe try this with thick ferrites(if the cable is Long enough Torroids) on the camera cable and the usb cable to the nitehawk base usb Adapter and the start of the umbilical too. And for eliminating it from the start, use them on the ac powercable and after the psu to the board too.

 

[NurseKateDeisgn]

I have a have exactly the same problem and there is a few discussion that could be regroup here.
I just change my cable every 2 month This is not a solution.
We have to look at cause of the problem, (The board design or the wrong angle of the connector )
I’m pretty sure about I say because I’m able to trigger the error at will.

In the picture you have the NiteHawk at the top and the SB2240. When say the angle is problem NiteHawk point directly to the back and it’s not protected. When you look at SB2240 Point at the top where they is less chance to be squeeze .

Until LDO change the design of the board we should work together for to design a good mounts That will keep the connected and protect the cable

 

[warpedscale]

Hello all,

I, too, have recently been experiencing a similar issue with the NH-36 and the loss of communication with mcu 'nhk'. I double checked the umbilical cable, all the crimps on the wires plugged into the board, the crimps on the cable plugged into the USB adapter PCB, power supply cable to the PSU, USB cable from the adapter PCB to the Pi, tried different ports on the Pi, etc. I even tried slowing down my prints, double checking my configs, switched out the Pi for another I had on hand, etc.

I was starting to lose hope until I swapped out the USB cable from the adapter board to the Pi with one that I 100% knew was USB 3.1 and into the blue USB ports on the Pi. This seemed to have solve the problem for me so far and I hope it helps some of you (I'll also apologize to those that have already tried/checked this to no avail).

Before, I couldn't go more than about 2-3 hours before my print stopped suddenly (and this was over the course of about a week) with no signs in the log except loss of communication with mcu 'nhk' and then a dump of random stuff and 'b'Got EOF when reading from device' and now I've completed multiple prints over 16-20+ hours.