Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by alexjx

  1. 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
  2. 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
  3. 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
  4. Here you are. But actually mine's 2*4*1.5, with 0.5 thicker for better insolation.
  5. 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
  6. 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?
  7. 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.
  8. 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.
  9. 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.
  10. Do you do regularly updated build? Or github I could get the latest. I also like the extra control. 🙂
  11. 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.
  12. 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. 🙂
  13. @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.
  14. @smartavionics Thanks for helping. The gcode is attached. And the issue happens in layer 8 of a corner. mcstnd_base.zip
  15. @smartavionics Here it is. Let me know if I'm doing it right... Should I use "save" or "export"? mcstnd_base.3mf
  16. 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.
  17. 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.
  18. 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
  19. 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.
  20. Interesting, I've been using DXU for a month, but didn't notice the issue mentioned here. I recognize mark2 is a great design, and what makes other solutions like DXU possible. However, it doesn't make sense to rule out other also good solutions. The heat breaker that DXU uses also works well enough to handle two nozzles. I could use a stronger fan to cool them. I'm using the 2510 variant and observed the cooldown time is much shorter than the original head. I printed regular PC in one head @ 290C, and loaded PLA in another, with an enclosure. Under this situation, the PLA in another head didn't deform enough to jam it. As the leaking, I think Cura's standby temperature did a great job. We are talking about modifications, there is a trade-off. The thing I believe mark2 made is space. The extra head will take up a much larger space than what DXU takes. I think the downside of DXU is really the source of material... It is not so easy to get as mark2.
  21. Doesn't ChangeZ alter the feedrate factor instead of the "speed" itself? So it affects all the "speed" with a ratio. Could you look at if the output gcode has M220 in it? If there is, please check if your firmware has M220 support.
  22. I'm afraid not... since one of the walls is already much less than 1mm thick.
  23. For what it worth, here is what I measured. The diameter of the hole for the heater is 4.05mm and 16mm deep. So maybe for 4mm heater. The diameter of the PT100 hole is 3.3mm also 16mm deep.
  24. Interesting, what firmware r u using? As far as I know G92 will be "reset" once homed.... so unless you print second one without homing.... the z offest will be gone...
  • Create New...

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!