Recent content by Aeronut

I encountered a similar problem yesterday - today, I found a broken wire at one of the umbilical connectors - broke right at the solder joint - why they can't use a crimped connector, I don't know!

You need to look in 'Stepper Z' section and not in the probe section which you posted.

If you don't feel comfortable with mains wiring, install the parts and then find a qualified electrician to do the connecting up.

Pleased that you managed to find the problem. The cable chains seem to be an almost endless cause of problems. Some of the problems are surely caused by unsuitable wire types being used, but I'm very glad that I changed to CANbus and umbilical, only the Z chain to worry about now!

If your setup uses cable chains, my first suspect would be a broken wire somewhere.

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...

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.

AFAIK, the umbilical setup is only designed to operate the printhead, with no faciility to drive the two steppers and anything else associated with the gantry. My own recent Nitehawk setup uses a Z chain between chassis and gantry, then umbilical to the toolhead. It's set up for sensorless...

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.

Are your X/Y belts identical lengths? If they're different, you'll have gantry squaring problems for sure.

I've run into the same problem on occasion. My solution is to manually perform a QGL just before starting a print. You can also change the number of retries in the CFG file,

FWIW, I've also had a couple of shutdowns with the same message. I've noticed that the reported Nitehawk temperature is around 67C whilst it's printing, which seems rather high to me. What sort of temperatures does yours report? I'm next going to try running the printhead without that hinged...

I spent more than two complete days trying to get two different CAN setups to work - always failed at the software DFU mode install. Abandoned that and fitted the LDO Nitehawk USB setup, had it up and running in a couple of hours, ignoring time taken to print parts. I've encountered two...

What LEDs are you using?

Finally twigged! In Mainsail, when you edit, save and restart the 'printer.cfg' file, the newly modified file is saved with a filename that reflects date, time etc., so that the restart still uses the OLD 'printer.cfg' file. The solution is to use 'save and close', which saves the file as...