Jump to content
Ultimaker Community of 3D Printing Experts


  • Content Count

  • Joined

  • Last visited

Posts posted by rachael7

  1. I am also getting this error at widely spaced and apparently random times.  In 780 hours of running, I've gotten the ER80 two or three times.  Most recently, I got the error at hour 24 of a 26 hour print, very disappointing.  I've checked my connections and they're solid.  My bowden tubes are not attached to the air manager cable and the cable is properly secured to the back of the machine, so it does not appear to be an electrical connection issue.  The error occurred in the middle of the night, when the machine was entirely undisturbed (and unobserved).  It's such a rare failure, that there isn't much I can do to diagnose it, so after checking and rechecking the cable, I'm pretty much at a loss.

  2. Thanks so much, Bunnyman! Couple issues to report, at least on my end. Compiling the exe seemed to work, but then it wouldn't actually run. It gave an error about module failed to start or something. So I tried to run the uncompiled script again. It had been working before, so I was surprised it errored out. It returned:



    Traceback (most recent call last):
      File "C:\Users\rachael.katz\Downloads\Engineering\Spool-Maker-main\SpoolMaker.py", line 36, in <module>
        import CuraMaterial as c
      File "C:\Users\rachael.katz\Downloads\Engineering\Spool-Maker-main\CuraMaterial.py", line 49, in <module>
        curaSysDir = OpenKey(HKEY_LOCAL_MACHINE, 'SOFTWARE\\WOW6432Node\\Ultimaker B.V.\\Ultimaker Cura 4.7')
    FileNotFoundError: [WinError 2] The system cannot find the file specified


    I had originally set this up when I was running Cura 4.7. I've since upgrade to Cura 4.8.0. Oddly, the reference to Cura 4.7 seems to be hard-coded into CuraMaterial.py.  How did I get myself into this mess?! LOL

  3. Yeah, I don't think it was any change with the format of the tags.  I'm hoping that they fixed what I think was a bug regarding new materials. As it stands now, if your new material has a material type field that matches an existing material, like PLA, ABS, etc, your custom material will not download to the material handler.  In order to get it to go into the material handler you have to give it a unique material type, like PLA1 or whatever. I really don't think that was their intention and the release notes sound like they may have addressed it. I'll have to test it soon.

  4. Thanks, Bunnyman!  I can't even imagine being without a computer for a week, let alone 2 months! Good to see you back. I think the tags are going to work fine, at least the ones I got from Amazon. The pickup in the machine is inside the plastic divider between the bays. It's just a flex circuit, like you'd find in a keyboard or something (accidentally took one of those dividers out, so I've seen it). The tags I bought seemed to pick up at least as well as the UM ones. My UM spools only actually read if I rotate them until the tag is in the bottom half of the machine - I think they kept the transmit power low on purpose, to prevent cross-talk between bays. The purchased tags seemed to have similar response, so I'm comfortable with them. My biggest worry is that on non-UM spools, you may not have a recessed area for the tag and the tag could get damaged as the spool turns. Might be best to put a mailing label or some other sort of sticker over the tag to make sure there is no abrasion. Otherwise, I think we can turn any spool that fits into an NFC spool.


    On another matter, have you had a chance to play with the new 6.1 firmware yet? The release notes made it sound like they changed something relative to custom materials, so I'm wondering if it has any effect on what we're doing here.

  5. 14 hours ago, gmeardi said:

    Thanks, Rachel et al.

    I’ve found the NFC reader/writer ACR122U based on Amazon, as well as the tags (NTAG216).

    I’ll try it in MacOS (BigSur) asap...


    Question: but having a latest iPhone (nfc write capable), with app like “NFC Tools” that can write NTAG216, might you simply program each tag with the correct ID (copy & paste from Cura) to have a similar solution?




    I can't say for sure, but maybe? The issue is that most NFC stuff seems to only use the ID of the chip, and not the actual data storing capacity of the tag, so most of the NFC apps I found couldn't do anything with the data portion at all.  I could manually edit some of the data fields with NFC Tools on PC, but I feel like I read somewhere that IOS doesn't actually let you do what you need to do with the phone.  Also, you have to figure out which fields store the data you need to change and edit it in hex.  For example, the total material weight on the roll was in 2E when I looked at it with NFCTools (I don't think the apps all number the memory fields the same) and the remaining weight was in 2F.  I didn't track down where the material ID was, though I'm sure it wouldn't be too difficult.  In the end, I gave up on that approach, since even with the challenges in setting up Python, it was still easier to just use the tool in this thread.

  6. Well, I was able to answer one question myself. This script is perfectly capable of writing new tags on blanks, in addition to changing existing spool tags. The trick is finding the right tag to use.  After some trial, error, and research, it appears the tags you need are Mifare Ultralight NTAG216.  The NTAG216 part really is the essential bit and what you should search on. I can confirm that these ones, from Amazon, work: https://www.amazon.com/gp/product/B07BF8MSN9/. Just select your material from the list, put the blank on the reader, and click "Write Tag". Couldn't be easier.         

    • Like 2
  7. Finally got this to work, once I got all the right Python modules installed. The one that really got me stuck was that I installed ndef instead of ndeflib. Also took me a while to figure out SWIG so I could install the pyscard module. Anyway, got it sorted, but I'm sure others following would still appreciate a handy executable. Thanks!
  8. On 10/21/2020 at 12:07 AM, Bunnyman21 said:

    @gandy @jomeier No problem, I put the link below. Still had some things I wanted to fix before uploading which are done now. Note it doesn't detect directories automatically for Mac or Linux yet, but can detect Cura for Windows just fine. For Mac/Linux, just give it the file paths. The script should work on a Pi too, but better to use command line for that rather than GUI.



    I really hate to ask, since you've done so much awesome work on this already, but I'm not much of a coder (dabbler, only) and I'm really not up to speed on Visual Studio Code. I keep getting errors about missing module PyQt5. Could I possibly impose on you to give us programming noobs either a step-by-step or a compiled executable? Thank you so much!

  9. 20 hours ago, Benleo888 said:

    Let me consolidate all related files and upload to Thingiverse, however, apart from those plastic parts (you can print by yourself with ABS), some metal parts also need to be modified and which may not easy for everyone, you can refer to the photos I attached below, I also upload more photos of my mod for reference.

    Thank you again!  It would be great to be able to get all the files from Thingiverse!  Please post back when you've had the opportunity to do that work. Thanks again for making this available to the community!

    • Like 1
  10. On 11/10/2020 at 2:08 AM, Benleo888 said:

    I finally converted my printer to DXU, but I am not using the original DXU print head, instead, I make use of the original head with modification, so that I can keep using the metal parts.  I found this modification design from Chat room, however, the author only released the STL files and some them seems not work well.  Therefore, I based on the original head dimension and reference to the STL file, I redraw all of them with Solidwork, modified some key area, attached the photos of my build as well as the parts photo exported from Solidwork. 

    Great work!  This is another excellent option!  Where can I find/download your new files/BOM?  Thanks!

  11. I guess I didn't do a good enough job of explaining the problem.  Let me try to outline it more clearly.


    - There is no issue with the generic materials. I can select them fine, but using the generic option doesn't allow one to use the full capabilities of the machine or Cura. There are many handicaps to using the generic material, including that you can only effectively use one at a time and you can't save their material parameters, so a custom material really is necessary to fully utilize the machine.


    - Creating new profiles is not difficult. I know how to do it, in exactly the way you said, by duplicating an existing profile, unlinking, and changing what is necessary. I know about the risk with handler-specific parameters, but in my experience it isn't a big problem if you start with a material that is close to the one you want to add.


    The issue is that, as but one example, you cannot add a new brand of PLA.  If you wanted to use say Colorfabb Build Series PLA, you could duplicate the Generic PLA material, unlink it, change the necessary fields in the material definition, and save it.  Next time you start Cura, it will download that new profile to the printer. The problem is that the new material will not appear as an option to select on the material handler when you load the material in the printer. However, if the material type field in the material settings, is set to 'PLA1' or 'PLA-A', instead of just 'PLA', the material WILL show up as an option to select on the material handler. Further experimentation will show that any new material you make, if it shares a material type with one of the generic materials, will not be available for selection on the material handler. Any new profiles with material types different from those available in the generics will be available for selection on the material handler. What I want to know is if this behavior was intentional or if this is a bug that needs to be addressed.

  12. So after watching the Cura masterclass webinar, I followed the instructions and defined some new materials for use with my S5/Material Station. Some of the materials showed up on the material station and some didn't. After some experimentation I was able to determine that the ones that showed up have material types (PLA/ABS/etc) that were different from any of the generic material types and the ones that don't show up use one of the material types that also appear in the generics. So if I want to make a new PLA brand, I have to use a material type such as PLA1 in order to make it usable with the material station. Is this intended behavior or a bug?

  13. Yeah, that's pretty much what happened to me.  I don't know how you defined your printer, if you were using one of the ones built into Cura or if it was totally custom.  My issue happened because I modified the files for one of the ones included with Cura and that caused an issue on the upgrade.  If you are doing your own machine definition files, I strongly recommend you make your own name, unrelated to any that come with Cura, and keep a copy of the definition files outside of Cura in case you need to manually restore them after an update.  I appreciate that this software was meant to work with the Ultimaker machines, but the fact that it doesn't handle updates well is a serious issue.  It doesn't even remove the old version.  It also doesn't handle machines well at all.  If you have saved a workspace and that printer doesn't import properly to the new version, even if you recreate the printer in the new version, you can't open the saved file because it specifies a non-existent printer.  Serious weakness!

    • Like 1
  14. Just to keep it clear for anyone who reads this later, it wasn't an issue with a profile. Those are easy enough to deal with by exporting and importing. This had to do with a custom machine definition, which cannot be exported or saved, and recreating it involves creating/editing JSON files in the program directory. Not trying to dig at you at all - I appreciate the help - it's just that this is a different issue and I don't want anyone to get confused about it. Thanks!

    • Like 1
  15. I resolved this issue. The problem did turn out to be that I modified the machine definition files included with Cura, rather than creating a new set of machine definition files. When I upgraded, part of what I did got overwritten and that created the conflict that was causing me all the trouble. So lesson learned - don't modify the JSON files supplied with Cura. Instead, copy the contents to a new file and define a new printer type. Once I did that, everything worked fine.

  16. I'm trying to upgrade from 4.5 to 4.6.1.  In addition to my UM2+, I also have a custom machine based on a Wanhao I3 Plus.  I modified the physical machine with an all-metal hotend that has multiple nozzle choices, so I modified the Wanhao I3 Plus machine and extruder definitions to give me the nozzle size dropdown.  I also had to add the nozzle variant files to make that work.  It's working as expected in 4.5.  When I upgraded to 4.6.1, on first run, I got the attached error messages about my extruder and variant definitions, and it went back to the basic machine definition with no nozzle dropdown.  I attempted a second upgrade method, by uninstalling, reinstalling, and manually copying over my machine definition, extruder definition, and variants, before starting Cura.  This caused Cura to crash when I tried to run it.  What is the proper procedure to migrate a custom machine from Cura 4.5 to 4.6.1?  Has something in the machine definitions changed between versions that is preventing the import of my custom machine?  Could the problem be that I modified the original 4.5 definition files for the Wanhao I3 Plus, rather than duplicating them to a new machine?  Thanks for any assistance!


  • Create New...