Jump to content

Link

Member
  • Posts

    360
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Link

  1. 4 hours ago, smartavionics said:

     

    Not sure what you mean there. I'm not aware of there being an open issue on github related to the sharpest corner z-seam method.

     

    It's probably working as intended and the real issue is that the sharpest corner on each layer of your model does not occur in the same x/y position. It only really works satisfactorily when the model is suitable (no tiny jagged edges and a uniquely identifiable corner). Perhaps it would work better if the outline was smoothed?

     

    I have been experimenting with the 'sharpest corner' function and it doesn't work consistently on all models as you would expect, despite the corner not changing in the model the location for the seam moves (as seen in the original problem). Also when you manual set the location of the seam it results in much improved travel moves, Cura seems to be able to much more efficiently calculate its paths when you set the seam location. Using sharpest corning seems to make the whole model way more complicated for Cura to handle (or it would appear so)

  2. As usual you nailed !, thank you Sir !

     

    it seems to be a combination of the extra infil wall count and the seam not locking as you said when you pick sharpest corner. Removing the extra wall and setting the seam to user specified (even with grid infil) sorts the issue.

     

    When you set the seam to user specified do you leave it to the default location it picks, rather than actually type co ordinates in ?

     

    Thanks again

  3. Hi,

     

    I am printing a basic cylinder and as can be seen from the image at a point near the top the z seam moves and the travels change despite the model being exactly the same over its length. I have tried every option of layer start position and z seam alignment and still at the same point on the model the the travels change and the seam moves. As said the model is the same the whole way up, just a simple cylinder with one flat side and infil.

     

    I have also tried all versions of combing and again no change

     

    any ideas @smartavionics or anyone else ?

     

    thanks !

    Screenshot 2019-02-13 at 10.44.17.png

    Screenshot 2019-02-13 at 10.50.50.png

    Screenshot 2019-02-13 at 10.50.37.png

  4. hi @smartavionics,

     

    I am using your new 'not in skin' combing but getting blobs on the outside of the wall at these points (shown below), as mentioned a while back (and the reason i asked you to keep 'only in infil') Cura treats walls as skin rather than just the top and bottom layers and therefore doesn't retract in the walls, hence the material from the non-retract travel is getting deposited in the wall which is often too thin to hide it. In the screen shot below there is a strange 'kick' in the travel at which point the blob appears. Any ideas ?. could the travel be made to not perform this kick, or stick more to the inside of the wall ? i can switch back to 'within infil' and will get retracts in the walls which fixes the problem, but think you mentioned that Cura has issues deciding where infil is and hence the 'only in infil' can sometimes result in travls without retract actually in the top or bottom layers (skin) ?

     

    Many thanks !

     

     

    1620757370_Screenshot2019-01-09at15_09_16.thumb.png.d4db8987b96fe5436e4a5d2ee3c8114b.png

  5. 13 hours ago, CarloK said:

    We only want to do an UM2(+) release when it is thoroughly tested, for the same reason that you don't want to run a beta version.

     

    Internally testing the UM2(+) software turns out to be a practical problem since we don't have a lot of those machines in the office, every developer has a UM3 or S5, so these machines are not tested in normal work. Also the System Test department did the last UM2 test a year ago.

     

    The Cura beta cycles are too short to get a good feedback on the firmware quality. I'll start a topic for a public beta test and see if that gives good response.

     

    interesting, I would have assumed that the 2+ was the biggest seller still for UM, but guess the other two models are considered newer and maybe need more tuning as the 2+ could be considered optimised.

     

    I managed to get the Tinker build working as it was rebased and have managed to change the few things I wanted (heater PID, default retraction etc for the 2+), so I am really happy  with what I have now. I am looking to add a cold pull feature and maybe look into how your 2+ code reads retraction from the SD card and include that into the Tinker branch. 

     

    Thanks for your help, I will obviously help with the Beta when I can (when I can supervise the print), let me know if I can assist in anyway.

     

    Cheers

  6. 1 hour ago, ahoeben said:

    Unless you want to do lots of development on Marlin, there's no need to install sdl, mingw or codeblocks. You can just install Arduino and load Marlin.ino (from the Marlin folder). Select the board that best resembles your controller board (Atmega 2560 is fairly common) and go to Sketch -> Export compiled binary. Two new hex files will be created in the same folder as Marlin.ino.

     

     

    I get this list of errors if it try to do that, I am using the latest Arduino IDE and TinkerFirmware 

     

    Arduino: 1.8.6 (Mac OS X), Board: "Arduino/Genuino Mega or Mega 2560, ATmega2560 (Mega 2560)"

    In file included from sketch/Marlin.h:21:0,
                     from sketch/Marlin_main.cpp:30:
    pins.h:1248:41: error: pasting "/* PG2*/" and "_RPORT" does not give a valid preprocessing token
     #define SDCARDDETECT                39  // PG2
     

  7. [gr5 removed massive quote of first post of this topic]

     

    could you help with this issue ?

     

    just about there, I have a compilation error related to the Arduino.h defining the max and min macro. It shouldn't really define those, but has, how did you get around that ?

     

    Thanks

     

     

    c:\mingw\lib\gcc\mingw32\6.3.0\include\c++\bits\stl_algobase.h|243|error: macro "min" passed 3 arguments, but takes just 2|

  8. thanks, just about there, I have a compilation error related to the Arduino.h defining the max and min macro. It shouldn't really define those, but has, how did you get around that ?

     

    Thanks

     

     

    c:\mingw\lib\gcc\mingw32\6.3.0\include\c++\bits\stl_algobase.h|243|error: macro "min" passed 3 arguments, but takes just 2|

  9. @3rdpig interesting, I recently went from 0.35 (the default in Cura for a Ultimaker 2+) to 0.4 and have to admit the parts look way way better, the top surface looks so much better not to mention the walls etc. All this would indicate that Cura seems to work better with line widths at least the size of the nozzle. My parts never  looked as good with a 0.35 line even without actual gaps issue, the top layer looked very rough compared to a 0.4 nozzle. 

  10. looking at the model it would be worth trying changing the 'Seam Corner Preference', I am not clear if setting this to 'hide seam' for instance is having some odd affect in some scenarios, however setting this to 'none' certainly seems to move the seam point and worth a go

×
×
  • Create New...