Jump to content
Ultimaker Community of 3D Printing Experts

rachael7

Member
  • Content Count

    18
  • Joined

  • Last visited

Everything posted by rachael7

  1. Ah, that's my problem. I didn't roll the rev to your new scripts at all, except for the exe. My bad. I'll download the new versions and give it another go. Thanks!
  2. All that said, the EXE that you included as release 1.0.0 works great! So much easier without having to install Python! Thank you!!!
  3. 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: 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
  4. 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.
  5. 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 tra
  6. 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 N
  7. 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.
  8. Has anyone been able to make new tags from scratch, rather than reprogramming the UM spools?
  9. 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!
  10. 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!
  11. 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!
  12. Great work! This is another excellent option! Where can I find/download your new files/BOM? Thanks!
  13. 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 ex
  14. 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 t
  15. 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 w
  16. 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!
  17. 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.
  18. 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 drop
×
×
  • Create New...