Jump to content
Ultimaker Community of 3D Printing Experts

ER26 and .gz file Extension Troubles


Recommended Posts

Posted · ER26 and .gz file Extension Troubles

I'm getting some problems here. I updated to 3.3.1 today, and did a firmware update for our Ultimaker 3. My old gcode files seem to work fine, but the new files are appended with a '.gz' file extension. If I open the file in notepad, the content is chinese(?) characters and empty blocks.Partial example below

 

謟ꄈ嫴"붜닙읥╱軸좯颵┉ꅞՠ㊂倐櫓荂뀤횚攒兆ᗹ參轲ঝ龢㠒웫뇞濥﮿�ﻯ鯰﾿翃ﵿ埢�וֹ࿷뽯췺鼷鞧�O︯㟱统﹟쟴︿쿩ﶟ쯲濗뽞�ﭼ췲뼗ﵾ㼯羷羇ﵻ￳폺羟ﹼ㾁뺧㱔˩꿻ﺾ῕矅龯钗⿗ﭒﶟ䳲쯧⿫羿췵㶫ﯿﵿ鿫ヌ쟷벿龫矵緟㷻럝籟췵穋꾛﮾诪ᆵ�꿫ǿﻏ�쓳ᅳ忆﫾⾧꾛﾿븟꿫꼾꒵忲�쾫㿓羵懾忇㿃徯羴7t蟹阿쏼匟뇺㾷跾粇鯳￟韗絟㹵㳣곮ﭦ 縫៫뱟ΰ쏼柗⼖뷟蟿쿗퟿ﺿ῰埋

 

 This doesn't seem right.....

 

If I try to start a print it generates an er26 message. If I delete the .gz extension and save with a gcode extension, the file appears empty. If I try to run it, the printer starts but goes directly to 'Print finished' message. Anyone know what might be going on?

 

Same thing seems to be going on in my dump log ('.gz' file and chinese characters)

 

Pete

 

P.S. Sorry if this is a duplicate, I tried to reply in the 'Multiple error codes' thread initially.

  • Link to post
    Share on other sites
    Posted · ER26 and .gz file Extension Troubles

      Update:

     

      Ok, I figured out that the characters are probably just an artifact of the 'gz' compression. (let me know if that is not the case) But if I choose 'save to file' after slicing and save as gcode, I get proper looking gcode. But I still get the ER26 message on the printer when I try to run the file.

     

     Any ideas?

     

    Pete

    UM3_ABSTitanGutsTopMK7.gcode

  • Link to post
    Share on other sites
    Posted · ER26 and .gz file Extension Troubles

    I think I finally have a resolution. After many attempts at fixing Cura, I finally formatted the USB key I was using, downloaded the firmware updates again, and updated the printer firmware again. The files must have been corrupted or something went wrong in the first firmware update, as things seem to be working fine now.

     

    Hope this helps someone else.

     

    Pete

  • 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
    ×
    ×
    • Create New...