Home › Forums › Announcements and settings experiments › AutoMaker 1.01.00 - RELEASED! This is a huge update!
This topic contains 48 replies, has 21 voices, and was last updated by chanyufei 6 months, 4 weeks ago.
-
AuthorPosts
-
13/01/2015 at 11:46 am #13587
http://www.cel-robox.com/downloads/
The interface has changed, a lot.
- Cura is the default slicer, you can change this default by clicking the COG in the top right corner. Or per profile when you create a custom print profile.
- When using Cura some options are greyed out, Slic3r still has more options than Cura. Cura is not able to slice some models that Slic3r can, or it slices them and makes some strange decisions. You might want to swap back to Slic3r in some instances.
- Calibrations screens and controls have been altered, the new XY calibration will allow users to more easily align the 2 nozzles so gaps between fill and perimeter can be tuned out.
- While we would be very interested in your custom profiles and materials we ask that you use the defaults to start. The results will be dramatically different.
- Older print profiles might have content that is not compatible, we have tried to transfer them over automatically but I would personally start from a new default profile and add my custom settings to that.
- If you have written custom materials onto your reels they will not be automatically overwritten. You might want to write the defaults onto them again.
A reminder:
NEVER switch the power off while fans are still running on Robox. This is vital… If the residual heat of the head is allowed to heat the rear of the head it will cause the filament there to distort and potentially jam. The fans keep this area cool and will automatically run while the head is over 60°C. This transition point has been carefully designed and the heatsink/fan is tuned to maintain the solidity of the filament before it is melted.
Attachments:
You must be logged in to view attached files.
13/01/2015 at 12:25 pm #13593Thanks Pete,
I’ve been privileged to test it in the last couple of weeks and I must say it’s a great improvement, both interface wise and with Cura as the new default slicer!
Congrats on this release and well done CEL team!13/01/2015 at 1:44 pm #13598Hi Pete,
How do I know if I have the latest version?
Thanks
Andy
13/01/2015 at 1:46 pm #13599Sorry, Found the version number at the top of the screen, duhhh!
1.00.17 at the moment
13/01/2015 at 2:29 pm #13600@pete for likes of myself who were testing the beta versions is there any need to upgrade from 1.01.00_RC8 to what is on the download or is it teh same as not getting an update message when i load up AM
13/01/2015 at 2:34 pm #13601@streatsi if you have the RC version you will need to download and install. You can just install over the top of the RC. Your profiles etc will remain as they are.
13/01/2015 at 2:58 pm #1360213/01/2015 at 4:17 pm #13603@dtoo overall better tool paths in most scenario’s creating higher quality models. Slicing is a bit faster as well and you will be able to print models that are buggy when using Slic3r, see for example this post, you can’t print this with Slic3r in a decent fashion: http://www.cel-robox.com/forums/topic/my-gallery-of-mostly-functional-prints/page/4/#post-12420 - Bridging might be better as well, if you had models that failed in the past you should try them again with this new version, if slic3r caused the bug this probably fixes it; It’s nice to have a choice
13/01/2015 at 4:47 pm #13609Well done guys. I’m sure there will be a few inevitable bugs, hopefully not that many. Looking forward to testing the new release soon.
13/01/2015 at 6:16 pm #13613README states:
“Clear indication of why make button is not available”
and yet when printer is not present or switched off, “Make!” button is present and when I press it nothing happens. It definitively seems to be a bug.
Does that mean I should raise a ticket?
If so - wouldn’t raising a ticket be a waste of time for support team that has more important things to do? Wouldn’t some simple issue tracking system (like Jira) be more efficient way of passing software problems back to your development team?
13/01/2015 at 8:32 pm #13614@clicky I guess you can create a ticket or maybe it’s better/faster to send a mail to automaker@… (this domain) to contact Ian directly for these smaller/lower prio issues like we had to do with the beta, this way the other non-software support staff won’t be bothered by it I guess
13/01/2015 at 9:20 pm #13616 -
AuthorPosts
You must be logged in to reply to this topic.
