HP 625 notebook here, WIN7, not very powerful, but works pretty good,
I don't have an Ulticontroller unfortunately.
That sounds like it should be plenty powerful, though I have heard some posts mention that laptops can cause trouble due to their power saving options and settings. You could try to chase this avenue by searching for laptop related issues in these forums or the ultimaker google group.
Do you have another computer that you could print a test print with? If not Ill clear some space off my desktop's table and see if I can't run a print and see if these errors pop up on it (probably in a day or two).
thanks a lot for good advice my friend.
Hey I tried out the new cura, sadly it didn't help with the weird errors. This might imply that it's not cura or it's slicer, but maybe is more computer issues or (god forbid) hardware? I'd put my money on computer related issues.
Also I made sure the firmware was up to date, so that's not it either.
Ill still try it with another computer.
- 2 weeks later...
I've been running 13.04 for about a month now without any kind of issues. I have a dedicated laptop (running windows xp) connected to my ultimaker solely for the purpose of printing. There is literally nothing else going on in the background. It is a fairly powerful machine, I have no doubt it is up to the task.
I upgraded to 13.06.4 today and tried my first print on it, only to have it fail about 2 hours in. It simply stops mid-print, the hot-end remains heated and continues to happily melt the stuff it is contact with.
I switched to the term tab and noticed a ton of these same strange checksum errors that you are seeing. So I loaded my model back into 13.04, sliced it, and it printed flawlessly. I checked the term tab to see what was going on, and there was only 1 instance of the checksum error right at the beginning of the print.
I've started another print to see how it ends up, and it is already throwing hundreds of these checksum errors (but so far continues to print).
I don't think it is a computer related thing, because it only became an issue when I upgraded Cura.
- UPDATE -
The print has just failed after about 43 minutes. The term tab has hundreds of instances of line number errors.
So, both the prints I have tried with 13.06.4 have failed. I'm quite certain it is not a hardware issue, otherwise I would have come across it some time ago.
I'll see if I can run it again tomorrow, and possibly post the contents of the term tab.
I have moved my printer to another computer and I still get similar errors.
I have been doing some digging though, are your motors hot? Mine were and I read that sometimes the motors will stop if they over heat. I tuned down the amps that go to them (not something I would do without some guidance) and so far I haven't had it stop in mid print. So I not sure that's the issue but Ill make sure to update you if after another 5 prints or so if I run into the same problem.
It's still making those line errors though.
+1. Confirm this too.
I still get the same ERRORS about LINES.
echo:Unknown command: "
Error:Line Number is not Last Line Number+1, Last Line: 3
echo:Active Extruder: 0
Error:Line Number is not Last Line Number+1, Last Line: 3
Error:Line Number is not Last Line Number+1, Last Line: 5
Error:checksum mismatch, Last Line: 27
Error:No Line Number with checksum, Last Line: 27
Error:checksum mismatch, Last Line: 260
Error:Line Number is not Last Line Number+1, Last Line: 260
Error:No Checksum with line number, Last Line: 470
Error:Line Number is not Last Line Number+1, Last Line: 470
Error:No Line Number with checksum, Last Line: 470
Error:checksum mismatch, Last Line: 855
Error:No Line Number with checksum, Last Line: 855
Error:checksum mismatch, Last Line: 931
Error:Line Number is not Last Line Number+1, Last Line: 931
Error:checksum mismatch, Last Line: 1067
Error:checksum mismatch, Last Line: 1171
Error:Line Number is not Last Line Number+1, Last Line: 1171
Error:checksum mismatch, Last Line: 1233
Error:Line Number is not Last Line Number+1, Last Line: 1233
Error:checksum mismatch, Last Line: 1361
Error:checksum mismatch, Last Line: 1577
Error:Line Number is not Last Line Number+1, Last Line: 1577
Error:checksum mismatch, Last Line: 2409
Error:Line Number is not Last Line Number+1, Last Line: 2409
Error:No Line Number with checksum, Last Line: 2409
Error:checksum mismatch, Last Line: 2636
Error:Line Number is not Last Line Number+1, Last Line: 2636
Error:checksum mismatch, Last Line: 2824
Error:Line Number is not Last Line Number+1, Last Line: 2824
Error:checksum mismatch, Last Line: 3128
Error:Line Number is not Last Line Number+1, Last Line: 3128
Error:checksum mismatch, Last Line: 3653
Error:No Line Number with checksum, Last Line: 3653
Error:checksum mismatch, Last Line: 4601
Error:Line Number is not Last Line Number+1, Last Line: 4601
Error:checksum mismatch, Last Line: 4946
Error:No Line Number with checksum, Last Line: 4946
Error:checksum mismatch, Last Line: 5641
Error:Line Number is not Last Line Number+1, Last Line: 5641
Error:checksum mismatch, Last Line: 6549
Error:Line Number is not Last Line Number+1, Last Line: 6549
Error:checksum mismatch, Last Line: 6927
Error:No Line Number with checksum, Last Line: 6927
Error:checksum mismatch, Last Line: 7618
Error:No Line Number with checksum, Last Line: 7618
Error:checksum mismatch, Last Line: 8577
Error:checksum mismatch, Last Line: 9026
Error:Line Number is not Last Line Number+1, Last Line: 9026
Error:checksum mismatch, Last Line: 10189
Error:No Line Number with checksum, Last Line: 10189
Error:checksum mismatch, Last Line: 10682
Error:Line Number is not Last Line Number+1, Last Line: 1
All the time, sometimes my print finishes well, and sometimes IT STOPS in the middle with HOTEND melting my print, too sad, so sad. RESUME <--> PAUSE helps a little and hotends starts to move a little bit, but hardly finishes another layer and stops again, so the print is ruined again.
Anyone? Thanks a lot.
- 2 weeks later...
So I've found a fairly easy workaround. Use Cura to slice, save the gcode, and then download pronterface and use that to actually do the printing. I successfully printed a 4 hour object without having it fail. I'm currently attempting an 8 hour object.
As an added benefit, I've found that pronterface tends to "stutter" less. When I printed direct from Cura I found that it would quite frequently - and randomly - pause during printing for about a second, leaving small little blobs in the print.
I find that the new Cura prints significantly less support material, which is kind of nice. And of course the slice speed is a LOT faster
- 2 months later...
I have the same problem. Haven't found anything on the interwebs so i am pretty much stuck.
Sicyons workaround sounds okay, but this isn't how i wanted to use the Printer. If it stops prints like out ouf the blue then it is not a good host for printing.
On the other hand: I am sharing my printer regularly with newbies who will get confused pretty quickly if I start using one Software for printing and the other one for slicing and an SD-card for printing via Ulticontroller and so on.
Also I like Cura very much and would be really glad if this could get fixed soon.
- 2 months later...
I'm running into the same problem except that none of the prints will complete successfully.
Has anyone found the root cause for the checksum problem?
I'm dead in the water and nothing will print correctly. I was able to print three successful objects before this started.
Are you printing over USB?
The checksum problem isn't the problem - that's just serial comms error correction doin it's thing.
@gr5: I printed the three successful prints via USB cable... When I started having the problem, one of the things that I tried was generating the g-code to SD card and printing directly from SD card. No joy.
The first four or five solid layers seem to lay down smoothly and then the stuttering begins... If, as @illuminarti suggests, the checksum messages are just a product of serial comms error correction then I'm back to thinking that the real issue may be a feed issue... I'll check my filament to see if it is getting scuffed up.
Resolution:
For my particular problem, after @illuminarti ruled out the comms as being the issue I went back in and checked my filament and sure enough it was still gettting scuffed up, which told me it wasn't feeding cleanly.
I swapped out the temporary tube I had used with the Bowden tube I received a couple of days ago and the prints are coming out just fine now.
Thanks for the help illuminarti.
i get same thing both on laptop and desktop.Doesn't bother me, prints are fine
-
Our picks
-
.png.790188cb2d32e3558395d7e5fbc992f3.png)
UltiMaker Cura 5.9 stable released!
ArunC posted a topic in UltiMaker Cura,
Here comes Cura 5.9 and in this stable release we have lots of material and printer profiles for UltiMaker printers, including the newly released Sketch Sprint. Additionally, scarf seams have been introduced alongside even more print settings and improvements. Check out the rest of this article to find out the details on all of that and more-
-
- 5 replies
Picked By
MariMakes, -
-
Introducing the UltiMaker Factor 4
ArunC posted a topic in UltiMaker 3D printers,
We are happy to announce the next evolution in the UltiMaker 3D printer lineup: the UltiMaker Factor 4 industrial-grade 3D printer, designed to take manufacturing to new levels of efficiency and reliability. Factor 4 is an end-to-end 3D printing solution for light industrial applications-
-
- 4 replies
Picked By
MariMakes, -
-
.png.790188cb2d32e3558395d7e5fbc992f3.png)
Recommended Posts
irongland 1
I have run across this type of error code a couple of times in the last month, and similarly to you my print sometimes finishes and sometimes it doesn't.
I thought it was a computer issue, possibly while slicing or when it's feeding the printer the g-code.
As such I thought I had better success at eliminating this issue by cleaning off the computer and removing background processes with spybot and msconfig and such. It seemed to help, but the computer I'm using for printing is from 2001 or so. Still I haven't fixed the problem yet so this might not be of any help
What type of setup are you using? do you have an ulticontroller, if so that would narrow it down. What is your operating system and is the computer outdated or obviously powerful enough?
Either way I'm interested in your response
Link to post
Share on other sites