Jump to content

nallath

Team UltiMaker
  • Posts

    4,495
  • Joined

  • Last visited

  • Days Won

    99

Posts posted by nallath

  1. Well, STL's dont have units. So according to the STL, the design isn't in inches, milimeters or "rijnlandse el". This is also one of the things that makes 3MF a vastly superior format as it does have the ability to store what the unit is.

    So if you export the files as 3MF, Cura will recognize the unit and scale them correctly.

  2. A clicking extruder is often a sign of your feeder being unable to push the filament through fast enough. The clicking is the motor missing steps.

    So it could be that some of the behavior of Cura changed that caused it. But as ahoeben mentioned, we will need a bit more info before we can say anything more concrete.

  3. 4 hours ago, Wolffy01 said:

    Two things are still missing in my point of view.

    - klipper flavor

    - mmu support (actually erase all M104 t* manually to avoid error, and add a z-hop and park position for filament switching.

     

    custom Cartesian printer with direct drive and mmu (ERCF VORON), running on klipper

    We don't have a MMU, so we can't test / develop that. We will need to depend on contributions from others for that.

  4. 16 hours ago, geocodyrgia said:

    I would HIGHLY recommend not publishing/advertising that this is out until AFTER Beta.  Just upgraded and all of my material profiles (except one weirdly) are all gone.  If 30 mins of troubleshooting and rolling back to the previous version don't solve it other slicers will get a very strong look.  Didn't have a reason to look outside Cura before now as all of my hard-fought material profiles were here.  Seems strange there wasn't some kind of backup process initiated prior to installing the new version.  Seems like that would be part of "migration 101" in dev school.

    There is a backup. What makes you think there isn't?

    The issue that you ran into is exactly why we release beta's. People find issues and then we fix them 😉 If we thought it was working perfectly, we wouldn't have to bother with a beta at all.

  5. 4 hours ago, Cuq said:

    Could be ...   Lot of message with :

     

    UM.Settings.ContainerRegistry._updateMetadataInDatabase [437]: Removing corrupt database and recreating database. no such column: icon

     

    But stange that I'm the only one with these issues ... And the last Alpha doesn't have any issue ... A little bit frustrating 

    We also got it from some engineers internally, but those were also people that ran it from source / nightly / custom modded versions from Cura. I've not yet checked if it also happens if you use the "official" path.

  6. Quote

    With approach number 01 I can generate GCODEs, but they end up being malformed, a lot bigger in file size and there is also a limitation on the number of  "-s" parameters I can send through command line, thus bringing unsatisfiying results.

    I've never ran into the number of parameters issue. Perhaps this is some issue with windows? I've also not have had them being malformated. The larger size is likely because of different settings.

     

    Quote

    Approach number 02: I could successfully connect to CuraEngine socket through Java and LibArcus, but the only Google Protocol Buffers message I am able to send to CuraEngine is of "Progress" type. Also, I did not find any message types that allow me to load an STL file (as the CuraEngine "-l" argument does) neither to output a GCODE (as "-o").

    I really don't understand what you're doing here. The engine sends progress to the frontend, not the other way around. There is no command that allows you to load an STL as the -i command, you will need to send triangle soup yourself. You can also not let the engine directly save to disk like that. You will get a message with the g-code and you will need to save it yourself.

    • Like 1
  7. I think it might be tripping up on the T0 command, which is really weird. For context; the T command is how the printer is told what extruder to use. So even if your printer only has one extruder, telling it to use the first one (T0) should be a valid command)

    Alternatively, it might also be the G92 E0 E1 command. You could try and see what happens if you change that to G92 E0

  8. On 5/20/2023 at 10:19 PM, Smithy said:

    I never tried it, but I guess when you use Create New, then you also get a new/unkown GUID number for the filament. 

    Yup. If you press "create new" it generates a new GUID. If you duplicate a material it will keep the GUID of the original material

    • Like 1
×
×
  • Create New...