CURA question. Vase settings. I’m printing a continuous vase for the first time and it is “glitching” roughly at the same location around the perimeter. Looking at the g-code, I see a G0 on every new layer that is ever so slightly a different position than the continous path would suggest. What setting(s) do I need to change to fix this?
So, I think I’m limited to 15.04.4 or something like that for OctoPrint. But looking at the g-code, I’m wondering if there is a regex to delete any line containing ‘G0’ & ‘Z’ that is PREceded by a line containing ‘LAYER’.
This explains it. Always wondered about it. I applaud Daid’s honest answer to some ranter “you guys just don’t care?”… he said. “No.”
Ha! Asked and answered. I’ve got no problem w honesty. Instead of trying to hack around the hack, why not just use slicer for spiral vases. That’s what I do. For everything else, I like cura. Going from cura to slicer feels like going back in time on the UI though. But grain of salt here- I’m riddled w inconsistent practices… I still use pronterface from time to time. No it’s not a slicer, but the UI is so plain, it’s a wonder. It’s hilarious to me that the interface was an option in cura 1.5. I used it too.
I love the joke: your not happy w (insert open source software here)?! You should ask for your money back.
Not trying to stir up flame wars, I love open source software and I’m happy to live w idiosyncrasies. But My business is also a benefactor so I have no grounds to complain at all.
@Alex_Wiebe no I don’t think it’s that simple, although I’ve never actually tried, the slicer engine is actually causing the printer to stop where the “seam” is (and it IS creating a seam, even in spiral mode) and then dipping down, then back up again. At least that’s what happened to me with this being the result: http://i.imgur.com/ck2ZpMf.jpg
I did have some luck by setting that outer wall wipe distance thing to 0 but it still didn’t seem to be a perfect solution / workaround.
@Brook_Drumm exactly, the vase mode was always a quick hack. Some might spend some time on improving it, but don’t expect wonders from it. As the engine was never designed to do this.
Note that BeagleOrb is our dedicated engine developer these days, I’m no longer directly involved.
@Daid_Braam good know, that actually explains a lot. Specifically, the comments I’ve seen from you. So what do YOU do for a living? Just curious. Were you a formal part of the company that owned cura previously? Not that it is that important, but I’ve never understood the relationship of the software company to the hardware company (ultimaker). I’ve always wondered how the software company makes money.
@Brook_Drumm still working at Ultimaker. We are not just making hardware, we are making hardware and software. Selling it as one solution. (Actually, the full solution is hardware+software+materials+profiles) So, one company.
But, I went back to what I love most, embedded software. Cura always was a run-away side project. So the Ultimaker 3 firmware has taking a lot of my time the last year. I wanted to make sure that the Ultimaker 3 feels as 1 product, unlike a printer with octoprint placed on top of it. (no hard feelings for Octoprint. Just a different method)
Almost had a burnout trying to do both Cura and the Ultimaker 3 in an exploding growing company. So it took some effort to leave Cura “behind” me in the hands of a whole team at Ultimaker. That has been a bumpy ride with the Cura 2.x version. But they are getting there.
I’m also very busy with just spreading information within the company. With the amount of engineers we have, the amount of details printing knowledge is less on average.
@Daid_Braam I hear you! That’s hard work. We finally got to market with our cloud service, new electronics : teensy, touch screen, ESP wifi, dedicated power board and new tinyg Printrboard G2 running on 33 bit arm chip. The firmware for the G2 (adding 3d printing stuff to their cnc platform) and the hand coded from scratch printrhub firmware (the touch screen, teensy and ESP) was soooo hard. So. Unbelievably. Hard. Thank God for super smart coders! Then we added marlin emulator to the G2 so cura and other open source host software works.
I wanted the same: an integrated system end to end. The files can be imported from Thingiverse and myminifactory. It turned out pretty cool.
Sounds like a big team. We are small. One programmer doing cloud, touch screen UI and helping w touchscreen teensy/ESP firmware, one guy, rob from tinyg, wrote the G2 electronics and one guy designed touch screen electronics and did the from-scratch firmware. All of us feel like we worked 10 years in the last year or so.
@Brook_Drumm I have 5 guys on just the UM3 firmware here. Of which one is a full time tester. On average the output is lower per person then with just 1 person. But the quality is higher. Which is something we need seeing the numbers we output.
The Cura team is 8 people I think.
Our new leveling method is one of the things we underestimated. It has more then a man-year of development effort in it, just from the software side.
I personally would stay away from the ESP in a product. I’ve played around with it, and it didn’t feel like a stable platform to develop on. Certainly not something I would trust a 4 day print on (which is something common for us now, “I’m having a week off, don’t touch my printer, it should be finished by the time I get back”)
It’s a shame we didn’t go for a better screen in the UM3, it’s what you get when the project grows organically with a shifting deadline. As this small screen estate is still causing headache.
I am however, very happy with the firmware we have for the UM3 now. Single firmware that runs on a whole bunch of machines (including prototypes) without a single recompile. We can deploy the same update on all our machines. Dynamic configuration takes care of the rest. Clear separation of concerns instead of a single master blob, allows for better working in a team, and potential upgrades without breaking everything else.
Took a while to get to this point, but now we can start making speed…
@Daid_Braam fun to hear about your process and work. We don’t stream anything, so ESP has been great. It just downloads the file and we’re good. It’s always a balance with all these complicated systems connected to each other. It’s going well. I wouldn’t describe us as “blowing up”, I’ve always take a very metered approach… no investors, just me doing what I enjoy
