Jump to content

ninjapigeon

Member
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

Personal Information

  • Field of Work
    Other
  • Country
    CA
  • 3D printer
    Ultimaker 3 Extended
    Ultimaker Original
  1. Isn't there a way to send the GUUID of say "PolyBrand Grey" to the printer before hand, so that it recognizes it? I've tried the steps you linked above, but Cura still responds with "switch unknown to PolyBrand Grey" or whatever, when i try to start the job. I realize the firmware link is a great idea incase you switch filaments and forget to update your Cura job, but this is frustrating me.
  2. Is there a way to override the UM3 "change filament from x to y" prompt, every time (or toggle) sending a project from Cura? example - using non-ultimaker PLA, lets say PolyBrand Grey, setup correctly (recognized as such) in Cura. On the UM3, because it's non-Ultimaker brand, without NFC, i have to choose printer material as "PLA" (assuming it means generic). Despite Cura having verified temps etc... is there no way to get the firmware or Cura to say "yes, i really mean use PolyBrand Grey" instead of the stupid 'override' button in Cura after the job is already posted? Since the override can be done from within Cura, i'm guessing there must be a way to not have to prompt this everytime. Suggestions? plug-in?
  3. Using Cura 4.3, and after slicing any model, sending to print over network, i get an expected 'override needed' (non-UM filament). Overrides fine in the app, then a message pops up stating "no group host", and to click link to resolve. However, the link leads to "print_jobs.com", obviously not by Cura / UM... what is going on here?
  4. I really hope you got an answer years ago, but if not - i found this link recently (for you, and others still looking for this answer): https://ultimaker.com/en/resources/20510-support-3rd-party-printers
  5. https://ultimaker.com/en/resources/20499-reset-cura-2-1 Just found this myself. Guessing you've since found a solution, posting for others who are looking for this.
  6. So, fixed this myself. Seems the programmers on 3.3 took an assumption that didn't fit my profile. I have a smallish SSD to run Windows, and launch my apps from a RAID1 HDD setup. After 3.3 released today, and i removed every config/install/appData file for my previous Cura installs, i had the same error. This time the log said something along the lines of "file not found on expected drive". Uninstall it all again, reinstall on the default 😄 drive.. lo and behold it works, and i'm printing now from 3.3. 😞 TL;DR - fixed, only if i installed on my default 😄 drive. Lame Ultimaker, lame. Edit: Apologies for the rash judgments! Fixed in 3.4 and later, haven't had similar issues since!
  7. Help appreciated! -launch Cura 3.3 Beta after installing. Agree to license. Can see a pop-up for "allow" of something behind a "select/name your printer" window. -select my printer (UM3, named "Ultimaker 3" or even "BldrBot") -window disappears as does all of Cura 3.3. (auto-quit) Ideas? Suggestions? incidentally, 15mb log for first launch? wow. cura.log
×
×
  • 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!