Jump to content
Ultimaker Community of 3D Printing Experts
Sign in to follow this  
ballanux

Corrupted gcode in SD card

Recommended Posts

Hi all!

I finished my ultimaker yesterday and started printing immediately :cool: , the print quality is good, but sometimes the printer head starts doing weird things, like moving to another location outside the object and come back to start printing some layers above the object.

I checked the gcode in my PC and everything was right, but then, I checked the gcode in the SD card (I'm printing from the ulticontroller) and it seems corrupt at some point, which causes a couple of layers to appear in mid air!

pmy5.png

a72s.png

Do you know what can be causing this?? Defective SD card? I'm using the one that came with the ulticontroller...

Thanks!

 

Share this post


Link to post
Share on other sites

If it's specifically just the file on your SD card, I guess it could be a bad card. It might also be file corruption due to you not properly ejecting the card before you remove it from the machine, maybe?

Is the top picture the 'ok on the pc' one... or are they both from the SD card? In both pictures, something looks wrong aside from the missing bits - there's what looks like a skirt and raft floating over the top of your print... those should be at the bottom.

Perhaps if you can post the 'correct' version of the gcode, I can take a look at it, and see if it makes sense. It's also possible that your model is bad somehow, and is confusing Cura into doing odd things.

 

Share this post


Link to post
Share on other sites

The two pictures show the same corrupted file. But what's more intriguing... I have found that this corruption only occurs during the print!

I did the following:

 

  1. Import the STL file in cura
  2. Save the gcode to the SD card and copy this file to the PC
  3. Take the card, insert it again
  4. Read the gcode, it was OK
  5. Print the object, then another error occurred
  6. Stopped the print
  7. Read the gcode in the PC, it was corrupted!

 

This is the gcode file view in cura after the print:

7ebn.png

This is how the object printed:

ko8u.jpg

Unfortunately I formated the card afterwards without saving the gcode, I should have made a comparison to see exactly what went wrong...

I have tried other SD card, but it doesn't get recognized by the ulticontroller (it's a 16Gb card with a partition of only 2Gb), I don't have any other 2Gb SD card...

Now I'm printing another object with the SD card write protected, I'm at 77% and everything is ok, but you never know until the end... :)

After this print I will try to replicate the error and see what changed in the file after printing... maybe a firmware bug?

Thanks

 

Share this post


Link to post
Share on other sites

I doubt it's a firmware bug, because I've never heard of this happening before and surely someone would have run into it by now. So if it's really happening as you suspect, then I'd start by looking for a problem with the card, or the reader hardware... but it's certainly an odd one, so please do keep us posted as you try to track it down.

 

Share this post


Link to post
Share on other sites

Did you always safely remove the card from your computer? Not doing this could irreversibly corrupt the card, it usually only corrupts a file, but it could corrupt the card forever.

(Which is why we didn't go for SD card storage on my previous job, which had very high reliability requirements)

 

Share this post


Link to post
Share on other sites

I doubt it's a firmware bug, because I've never heard of this happening before and surely someone would have run into it by now. So if it's really happening as you suspect, then I'd start by looking for a problem with the card, or the reader hardware... but it's certainly an odd one, so please do keep us posted as you try to track it down.

 

You were right!! One of the SD card reader pins in the ulticontroller is smashed down!! :mad: :mad:

Even more, it's pin 3, which is GND. As there is 2 GND pins (the other one, pin 6 is right) this causes the card to work, but being more susceptible to failure, maybe EMC related...

This will be difficult to repair... and I'm pretty sure this had to came already broken, it's very difficult to bend a single pin in the middle of the reader, so I think I will put a support ticket :-|

5l4n.jpg

v74r.jpg

 

Share this post


Link to post
Share on other sites

The support people replied to me very quickly, they will send me another board. I will print from the PC in the mean time.

If there are problems with this card socket maybe it's time to find another supplier for them.

If any other pin would have been bent instead of GND it would have made the SD card not to work and find the problem immediately, this was a bit unfortunate :???:

 

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
Sign in to follow this  

  • Our picks

    • Ultimaker Cura | a new interface
      We're not only trying to always make Ultimaker Cura better with the usual new features and improvements we build, but we're also trying to make it more pleasant to operate. The interface was the focus for the upcoming release, from which we would already like to present you the first glance. 
        • Like
      • 5 replies
    • "Back To The Future" using Generative Design & Investment Casting
      Designing for light-weight parts is becoming more important, and I’m a firm believer in the need to produce lighter weight, less over-engineered parts for the future. This is for sustainability reasons because we need to be using less raw materials and, in things like transportation, it impacts the energy usage of the product during it’s service life.
        • Like
      • 12 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!