Jump to content
Ultimaker Community of 3D Printing Experts
kmanstudios

Print finished before starting

Recommended Posts

Well, after bazillions of hours of printing with no issues other than self imposed stupidity, I started a print, did the active leveling and as soon as the carriage rode to the front of the buildplate, it went back to the starting position and said print was finished......Now it is active leveling on its own.......And now it appears to be printing. Will get to logs after print is done, but this is a first for me.

Share this post


Link to post
Share on other sites

Just finished printing. I dumped the logs, but did not think to get the file from the USB stick as well.

 

It went into a "start print cycle" for three tries (aborted each time) before I dumped the logs. It was odd. Just for clarity sake, I did abort the print once and abort the cooling sequence as well just to get things moving as it did not have time to heat up that one time.

 

Link to file.

Share this post


Link to post
Share on other sites

I've seen something in the log that caused a problem

Apr 06 10:26:52 ultimakersystem-ccbdd3003e12 python3[459]: 2018-04-06 10:26:52,468 INFO     printerService  Procedure next step: ALIGN_Z_AXIS: HEATUP_HOTEND_WAIT_0
Apr 06 10:26:52 ultimakersystem-ccbdd3003e12 python3[459]: 2018-04-06 10:26:52,473 WARNING  materialManager No maximum temperature for material in hotend 0
Apr 06 10:26:52 ultimakersystem-ccbdd3003e12 python3[459]: 2018-04-06 10:26:52,475 INFO     waitForHeatableObjectsStep Setting target temperature of hotend-0 to 210C
Apr 06 10:26:57 ultimakersystem-ccbdd3003e12 python3[459]: 2018-04-06 10:26:57,490 INFO     waitForHeatableObjectsStep Waiting for hotend-0 heatup: 177.1/210.0 (wait_tolerance: 0.0)
Apr 06 10:27:02 ultimakersystem-ccbdd3003e12 python3[459]: 2018-04-06 10:27:02,504 INFO     waitForHeatableObjectsStep Waiting for hotend-0 heatup: 185.4/210.0 (wait_tolerance: 0.0)
Apr 06 10:27:07 ultimakersystem-ccbdd3003e12 python3[459]: 2018-04-06 10:27:07,520 INFO     waitForHeatableObjectsStep Waiting for hotend-0 heatup: 197.4/210.0 (wait_tolerance: 0.0)
Apr 06 10:27:12 ultimakersystem-ccbdd3003e12 python3[459]: 2018-04-06 10:27:12,043 INFO     procedure       AlignZAxisProcedure(key='ALIGN_Z_AXIS') transitioning from WaitForHotendTemperatureStep(key='HEATUP_HOTEND_WAIT_0') --> GotoPositionAndSetZ0Step(key='MOVE_TO_POS_AND_SET_0')
Apr 06 10:27:12 ultimakersystem-ccbdd3003e12 python3[459]: 2018-04-06 10:27:12,049 INFO     printerService  Procedure next step: ALIGN_Z_AXIS: MOVE_TO_POS_AND_SET_0
Apr 06 10:27:12 ultimakersystem-ccbdd3003e12 python3[459]: 2018-04-06 10:27:12,054 INFO     gotoPositionAndSetZ0Step move to: 'G1 X200.000000 Y105.000000 Z7.143593 F9000' to apply bed level parameters and set Z0 position

Apr 06 10:27:19 ultimakersystem-ccbdd3003e12 python3[459]: 2018-04-06 10:27:19,606 INFO     hotendCartridgeManager setPresentChanged(0 is not present)
Apr 06 10:27:19 ultimakersystem-ccbdd3003e12 python3[459]: 2018-04-06 10:27:19,624 INFO     hotendCartridgeManager _updateHotendGone deleting reference to hotend(0, b'4\xdb]\x1e\x00\x00')
Apr 06 10:27:19 ultimakersystem-ccbdd3003e12 python3[459]: 2018-04-06 10:27:19,679 INFO     heatableHotend  setting default on pid_Kd
Apr 06 10:27:19 ultimakersystem-ccbdd3003e12 python3[459]: 2018-04-06 10:27:19,708 INFO     heatableHotend  setting default on pid_Kp
Apr 06 10:27:19 ultimakersystem-ccbdd3003e12 python3[459]: 2018-04-06 10:27:19,731 INFO     heatableHotend  setting default on pid_Ki
Apr 06 10:27:19 ultimakersystem-ccbdd3003e12 python3[459]: 2018-04-06 10:27:19,795 INFO     hotendCartridgeManager setPresentChanged(0 is present)
Apr 06 10:27:20 ultimakersystem-ccbdd3003e12 python3[459]: 2018-04-06 10:27:20,056 ERROR    procedureStep   Exception caught from step: MOVE_TO_POS_AND_SET_0
Apr 06 10:27:20 ultimakersystem-ccbdd3003e12 python3[459]: Traceback (most recent call last):
Apr 06 10:27:20 ultimakersystem-ccbdd3003e12 python3[459]: File "/usr/share/griffin/griffin/printer/procedures/procedureStep.py", line 82, in _run
Apr 06 10:27:20 ultimakersystem-ccbdd3003e12 python3[459]: outcome = self.run()
Apr 06 10:27:20 ultimakersystem-ccbdd3003e12 python3[459]: File "/usr/share/griffin/griffin/printer/procedures/pre_and_post_print/auto_bed_level_adjust/gotoPositionAndSetZ0Step.py", line 52, in run
Apr 06 10:27:20 ultimakersystem-ccbdd3003e12 python3[459]: controller.sendRawGCode("M218 T%d Z%f" % (hotend_index, z_at_0_0 - z_hotend_0_at_0_0))
Apr 06 10:27:20 ultimakersystem-ccbdd3003e12 python3[459]: TypeError: unsupported operand type(s) for -: 'str' and 'float'

What happened here is that while heating up the left printcore, it suddenly seems to be removed. This happens while the printer is also active trying to move to the correct position based on the left printcore. But now, it can't be found, resulting in an error when calculating the bed z movement.

 

Can you check / clean the printcore contact points, both of the printcore(s) as well as within the head?

Share this post


Link to post
Share on other sites

Actually, I am on my last print with this machine and then it is maintenance time for it. Hot/cold pulls, etc. It was just printing and I was getting things out, so I figured that I would check the core as soon as it either (a) gave me the same issue or (b) finished this round parts for a diorama.Due to be finished in 10 hours.

Share this post


Link to post
Share on other sites

OK, took time to get some maintenance done. Took out the print core 2 and everything is clean  as can be. There was no grit or junk and even did a swab with a Q-tip and 99% Isopropyl and saw nothing on the pristine white cotton swab. Rocked the core before checking it out and it would not budge in the socket. Pulled out very cleanly and went back in with a nice snap and no residual motion once back in. Solid as before I took it out.

 

Doing the basic hot and cold pulls just to clean out any carbonized PVA. Although not really popping or sizzling, you can tell the there is still some carbon build up and getting it all back to working spiffy.

 

So, no idea what happened before.

Share this post


Link to post
Share on other sites

No worries about that. Still wondering what may have caused it.

Mostly it's a mechanical problem causing an electrical failure when the PrintCore suddenly goes missing.

So it's bad connection of PrintCore in the head (dirty copper) or PrintCore too loose within the head.

And you say neither is the case, so at this moment I'm baffled.

Keep us in the loop when this might be happening again.

Share this post


Link to post
Share on other sites

The only odd thing that I did was abort the print a few times trying to get something straight. I wish I could tell you exactly why. Oddly, it kept wanting to return to that print for the same number of aborts. But, so far, all is working splendidly.

Share this post


Link to post
Share on other sites
16 minutes ago, robinmdh said:

We're going to add some de-bouncing to the printcore presence detection.

It will likely be in the first public release of a 5.x.x version.

Please explain 'debouncing'. Also, printer has had no issues since I posted the original notification.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Our picks

    • Taking Advantage of DfAM
      This is a statement that’s often made about AM/3DP. I'll focus on the way DfAM can take advantage of some of the unique capabilities that AM and 3DP have to offer. I personally think that the use of AM/3DP for light-weighting is one of it’s most exciting possibilities and one that could play a key part in the sustainability of design and manufacturing in the future.
        • Like
      • 3 replies
×

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!