alexjx

I am.

The model has a lot incorrect normals. Even one that on the same face. I recall reading somewhere that cura doens't affect by normals, but I guess I read wrong. Here is the model after fixing the normals.

Plus one for this. I tried to implement this. But could not get the "angle" mark work properly... Cura didn't tracking the expansion state, but just tracking the "click".. See that "Quality" and "Material" collapsed, but the "arrow" is still downwards.

This is really cool feature! I would like to use this. Thank you for bring another great feature. Have you pushed to your github? :)

Actually, I think the video had made an incorrect claim against nylon. It will absorb water, but for a printed part, moisturization might be the wanted result. Nylon demostrates different properties after absobe water, it will be more flexible and "tough". And actually, some nylon parts manufactures demands certain degree of moisture. So I would put the printed parts into water to make it more "stronger".

I'm not sure about the "nozzle 1" offset you are referring... The "regular" bed leveling wizzard will guide you to level the bed, and set the "active"nozzle" offset. So I normally do that with nozzle 1. After this the bed should be leveled relative to the nozzle. All you have to do is the set the offset of the other nozzle, and that is what the function in the "dual" manual does. Jia

By connecting via USB, you actually gain access to the serial port. And printers are controlled via GCODEs. there are a lot you could find on the net. UM firmware implemented a subset of the GCODEs and some might not well comformant to the standard if there is one. I think reprap wiki would be a good start point. Regarding to your goal, assumming you would like to print via SD card. There are GCODE tells you what's the current bytes offset starting from the begin of the file. But the catch is that there is no GCODE to tell you how long it's been printing so far (as far as I know). So you have to track that from beginning. Jia

Did you still have the gcode? you could inspect if there are M0/M1/M25 command to pause the print. If not, it might be firmware. Jia

Here you are. But actually mine's 2*4*1.5, with 0.5 thicker for better insolation.

Yes. It does. Same as mark2, firmware will adjust the Z height accordingly. After install this mod, you will have calibrate X, Y aligment and as well as Z. Similar to you leveling your bed. The difference is that, you have to manually do that (with GUI guided you through it of cause). Jia

Assuming you're printing it as the STL...if you want it smooth. The only thing I could think of is to use quite small layer height. But since we are talking about FDM... I guess 0.05 will be the limtation?

If there is no referrence to those temperatures, cura will insert them before the start gcode. At least this was the logic in the 4.1.

Thanks. This is very helpful. Especially for those who print different high temperature materials, like PC. BTW, how does it work with the existing z-offset plugin? I see, it gives the option to include what option, not providing options directly.

I think this is a good idea. Though I agree that the root cause is the leveling. But for beginners to do a good leveling is difficult. Because it is not really a measurable thing. It requires quite a lot experience. So why not make the tool do more that we could get started. Instead of being frustrated and leave.

Do you do regularly updated build? Or github I could get the latest. I also like the extra control. 🙂

For one, I think you have to choose "marlin" when you use host software like RepetierServer. marlin, reprap and ultimaker 2 here, are something like dialects of a language. They are all gcodes but, there are a few differences. As you have figured out, when you choose ultimaker 2, the start procedure is handled by the firmware. The same behavior could not be achieved when using host software since it's now the host sending gcode one by one to the printer. While there is no "start", so the firmware doesn't know when to do the start procedure. Therefore the start has to be done by the slicing software or host software. When changed to Marlin, Cura has a default start script. You could use that as a base and tweak to the behavior as your liking.

Aha, I see it now. so "within infill" will only consider the start and end point if it's "infill" but not in between. That's why once I was printing a spring, it travels across the whole spring only if I set to "within infill". Thank you again for explaining this. 🙂

Thanks!

@smartavionics Thank you very much for the infill tip. 🙂 I tried "not in skin" too. but there is also a similar issue. I'm not sure if they are related.

@smartavionics Thanks for helping. The gcode is attached. And the issue happens in layer 8 of a corner. mcstnd_base.zip

@smartavionics Here it is. Let me know if I'm doing it right... Should I use "save" or "export"? mcstnd_base.3mf

Right... Then, CuraEngine itself doesn't have a hard limit in the code, so it will take whatever the Cura GUI provided. Setting it to 9999 then the upper limit is 9999. This is from reading the code. And for a practical example, The "bird in the cage" as a lot of small features need retractions. In the first picture, max is set to 99 and the second with 9999, and no other change. Notice the dark blue lines indicating none-retraction travel since retraction count exceeded the limit, while the second doesn't.

I think it only warns you. I've set this to 9999, and didn't observe any slicing problem. But of cause, setting retraction count so high will risking chewing your filament if the window is very small.

Hi all, I'm trying to understand a travel path that causing blob on the surface. I've enabled both "retract at layer change" and "retract before outer wall". The travel is to the skin wall with retraction. Combing is set to "within infill". What makes the print bad is that the path generated seems a bit off the skin before it could start print. (see the picture). Is there any option I could tweak to get rid of this? Thanks. Jia

I think this behavior started at 3.6. I had a hard time understanding it too. But it makes sense after you realize if two material interleaving with each other, the adhesion tendency will not as strong as one. So Cura chooses to use one material always printing a shell for the tower, so it will not break during print. For support materials like PVA, this makes sense, and for dual color prints, for most of the time, each layer will have two colors so it also makes sense. The only problem is where things like a traffic cone, which different colors printed in different layers. I think this is a small price to pay...since the original behavior is to print different colors alternatively in each layer. And in this case, it will make the tower even weaker.