Thanks for the quick reply/support - yes, i renamed the .db file and the program opened right up - i didn't even realize i had a sync account, but after resetting the password- got in and it recovered my printer settings, all is back to normal. How the .db got corrupt is concerning.... be nice if MatterControl could recognize the db is corrupt and tell you and ask to restore the settings, etc, rather than simply refusing to launch.
I updated to ver 1.7.3 on the 9th. Worked fine after install. But, last night I shut down my PC (normally I only put it to sleep, so this is first time windows rebooted since the last Windows update, about 3 weeks ago)
After Windows restarted MatterControl will no longer launch. I press the icon, and windows cursor shows busy for sec, but, program never launches. I opened Task Manager - Detail view, and when i launch MatterControl it never shows up under Apps, But when i look under Background Processes, MatterControl pops up for 1 sec, then disappears - but the program is not launching.
I uninstalled MatterControl and reinstalled, same issue. I rebooted Windows again, same thing. MatterControl simply will no longer launch.... What happened? ? ?
Well, I just answered my own question... When I tried to run the edited Salvage file and the extruder went into convulsons, i would hit CANCEL immediately. But, when i did, it took some seconds before it canceled. As a One Last time try, i ran the file and this time i didn't hit cancel, after about 15 sec of spewing out filament, the printer jumped to the location and resumed the print. YEAH, I was too fast at hitting cancel before. Anyway, it has resumed the print and looks great so far. So, this print will be salvaged. I guess my method works - just waists a little filament. But, better then have to restart the print all over again.
I have issue with MC hardwired to use Absolute length values for Extruder. Previously I used to use Slic3r and never had issue with how i salvaged bad prints. So, Slic3r/repetier host must have used Relative Extruder values.
Here's how i used to Salvage a bad print. For example today I am printing a large piece (10.75" diameter on my Rostock Max bed) and 4+ hours into the print the tube popped out of the bowden extruder and filament when everywhere - but the piece... Here's what i used to do with Slicer - I would measure the printed height of the piece and then load the Gcode file into an editor (Notepad++) and 'find' the layer (by z height) where the print left off - I would then remove all the code for the already printed layers from the end of the header to the layer where i need to RE-start printing. Then load the edited file in and resume printing from that layer.
It always worked and I've salvaged countless bad prints using that method. (Sometimes the print can stop due to printer malfunction, PC crashing, running out of filament, etc,, etc.)
For some months I've been using MatterControl both as the host software and for slicing. Generally i like it, especially the 13 point bed leveling feature with the Rostock Max, makes it print LEVEL all the way around... out to the edges.
I have had to modify the method for Salvaging bad prints due to the bed leveling feature in MC. I could no longer use the measured height of the piece where it stopped printing and find it in the saved gcode file, because the autho leveling would print to the compensated height. So, what i have been doing in MC is use the Layer View and so far I have been able to find the last printed layer with pinpoint accuracy by combination of looking at the print, and often time finding a where a feature starts or stops at a layer and count the layers since that feature to where it stopped. Anyway, that is a bit of an explanation, but the gist is I have always found the last printed layer, can modify the Gcode and save it and ReStart printing at that layer - And, up until today, even with MC that has worked.
But, today it didn't - the part is large - and i printed it with 50% infill. And, it had printed a considerable number of layers so far. So, when i tried to run the modified file, i noticed the Extruder went into convulsions, vibrating and spewing out as much filament as it could - all at once. But, i didn't know what was going on at first, because up until this file, this has worked for me in the past and i was able to salvage bad prints.
After some frustration, i finally found the issue. The first line of the layer i was trying to restart the print from was this:
G1 F6600 E1971.46079
E1971 - that is what? I would assume that is mm, but, not sure because it would seem by that layer it would have used more than just 2 meters of filament. Anyway, however long it is, the first layers of the file were deleted so i could salvage the print and print from this layer... so now this line is instructing the extruder to immediately extrude a whole bunch of filament all at once before proceeding. As a result the extruder can't run that fast and the stepper goes into convulsion while a whole bunch of filament pours out.
I was using Carbon-Fiber filled PETG (from 3DXTech) which is a little expensive, plus the print was already over 4 hours done, and i wanted to save it Sadly, it looks like it can't be done, and I don't have enough of that filament to print another from scratch. I will have to use plain ole PETG and start a new print.
But, in the future does anyone know of any workaround for what I am trying to do? I mean, I can't be the only one out here who tries to salvage bad prints am I? Like i said, i've done it in the past many times. And, it is something I would like to know how to do with MC in future. (other than writing some hack program that will read my Salvage GCode file in, and subtract the first E value from all the E values, making the salvaged file start with Extruder length of 0 rather then some large number - but i haven't written C utility programs in ages, so that would take me too long to set up a compiler and all)
I know how the calibration works, or is supposed to work, I've ran it many times before i did this upgrade. I know that it moves Z in 1mm .1 and .01 mm What I mean, is what i hinted at in my first post, it will start with location X140 Y0 and after setting that location - with all three depths 1mm .1 and .01 it should go to the next location, but, it doesn't - the head stays in the same location and starts over with the 1mm .1 and .01 it does this for 3x then it jumps not to the next or 2nd location, but to the 4th location as i showed in my first post
1 X140 Y0
2 X140 Y0
3 X140 Y0
4 X0 Y140
5 X0 Y140
6 X0 Y140
where position 1 is correct, x140 y0 but position 2 should be
2 X121.24 Y70
3 X70 Y121.24
4 X0 Y140
So, instead it stays at location 1 for 3 times, then jumps to 4th position. Again, i am speaking of counting the 1mm .1 and .01 settings as being one location setting.
I have tried setting the leveling to 7 positions and 3 and back to 13 but it doesn't change the way it is working.
Previously, after i first did the upgrade, when i pull up the Leveling Settings window (using the edit pencil button next to the Software Print Leveling under Calibration in the Options menu - it actually displayed those incorrect position values, where it shows
1 140 0
2 140 0
3 140 0
4 0 140
But, after doing what you told me as long as i don't try to run the Calibration Configuration... it now will display in the Leveling Settings window the correct locations, and when i print it is doing the leveling OK
But, if i try to run the Configuration then it goes to the wrong locations, staying 3x at the first location, then jumps to the 4th location... etc. When i hit cancel of the configuration and try to view the positions again by opening the Level Settings window, that window will now be blank, not listing any positions at all. And, when you cancel the configuration the program turns leveling off, so if i try to turn it back on, after having tried to run the configuration the program crashes with the index out of range error
Definitately, something is wrong
Build is 220.127.116.1167
additional note: When i reboot the program and turn on Leveling - it is working now and prints ok i guess the other time i tried to print leveling wasn't turned on
But when i try to run Calibration it still is not going to the 13 points, it still is stuck on 3x at same location. Then I cancel Calibration and it turns leveling off - at that point when i hit button to turn leveling back on - it crashes w/ the out of range index. BTW I have uninstalled MatterControl and reinstalled it already
Sorry took so long -
Nope - I did what you said, renamed the Profile dir re-launched Mattercontrol 1.6.1 it ran a wizard, I think for setting up the cloud accnt, which was already set up, but i didn't see a profile import wizard.
When I first viewed the Level Settings window, it showed what looked like older Level settings But, when i printed it was off, so I ran the Calibration to redo the values, and it did the same thing,
moves to the first location, set the height, then instead of going to a different location, it stays in same location for 3x, etc. When i exited the Calibration I viewed the location settings again, and now it was blank like before.
I noticed that Leveling was turned off, so I went to turn it on and it crashed, giving an error box unhandled exception saying that the Index was out of range - must be non-negative number
So, now I am unable to print anything...
Followers 0 Following 0 Joined Last Online