Jump to content

Marco_TvM

Dormant
  • Posts

    195
  • Joined

  • Last visited

Everything posted by Marco_TvM

  1. Thanks @fabreax, I will have a look at them and see if I can find anything.
  2. Can you send the log files (using something like wetransfer) please?
  3. Can you tell me which firmware version? And if possible, it would help to get a dump of the log files.
  4. Use the PrintCore heater diagnostics test: System -> Maintenance -> Diagnostics -> Heater Sensor test
  5. What @robinmdh said. Unless Cura does something we (EM) does not know about...
  6. @Tiger91 and @tomnagel : Give me a little time to get some things sorted before I give some answers...
  7. It does detect the kind of printer indeed. And the query helps to see how the printer identifies itself, and in your case, as should be expected as an UM3 Extended. Why it went wrong the first time is still puzzling to me. But am glad it's working well for you now.
  8. As @fbrc8-erin mentioned, this only need to be done once Also I think some collegue has made a sort of "printcore holder" which you can hang onto the UM3, so you can 'store' the cores with the corresponding UM3. I asked him to put it on youmagine and will place a link here when it's done. Added: actually, other people made some as well. Just search for "printcore" on youmagine.com
  9. @smartone Thank you for the feedback. Can you describe exactly what you mean with "my print bed no longer went all the way up? Did you try raise and lowering the bed from the menu? It would help us if you would be so kind and install the new 3.7.7 firmware and try to execute those commands and sending us the log file(s) using wetransfer... For your information, there is only one firmware for the UM3 which serves both the UM3 and UM3 Extended. Why you are having problems with the new firmware is kind of surprising. We have had no other reports of problems with the UM3 Ext. from other people.
  10. What @daid said; However if it's about detecting the materials on the printer, you can use the normal web api to get that information.
  11. @ryandavidson Can you humor me and try to connect to the printer with the app without the NFC material spools placed? If the app works without the material spools placed, you should definitely update the App because there was a bug solved causing this specific issue.
  12. @smartone, could you post the results of the opening this url: http:///api/v1/system/hardware
  13. Actually there is. From the WEB API: http:///docs/api/#!/Printer/get_printer_heads_head_id It shows you the totals. So no print time per material or even more sophisticated.
  14. Have you updated to the latest stable version of the firmware yet? Please check: System -> Maintenance, then move over the choice "Update firmware". At the bottom you will see the current version, which looks something like: X.Y.Z.YYYYMMDD
  15. Have you tried the 2nd AA nozzle? You can also perform a PT100 test using the menu: System -> Maintenance -> Diagnostics -> Heater sensor test.
  16. @EWadsager, @bizzarrini and @sameeryel What @fbrc8-erin and @neotko have been suggesting are the right steps. 1. Check your current firmware. 2. Update to the latest stable. If the problem then still persists. we'd like to receive the log files.
  17. Not sure what you mean with a reboot. If you can't upgrade the firmware for some reason, you might need to use a recovery image. If this is the case, @sandervg might be able to help you with that.
  18. The UM3s come with a Mean Well GST220A24-R7B (as far as I know). Specs: https://www.meanwell-web.com/en/product_info.php?products_id=GST220A24-R7B
  19. I said something, but that was not a good answer. So removed it
  20. Just a small question, which version of the firmware, on the printer, are you using?
  21. Also, if you have just turned on your printer, is the stream accessible / working when using the API directly: http://:8080/?action=stream
  22. Can you send a full log? We'd like to see the kernel messages as well, maybe that will give us a hint of what's going wrong. Thanks in advance.
  23. A heads up to all of you, we think we have identified the cause of the problem and are working on a fix. This still needs to be tested of course. Thank you all for your patience!
×
×
  • Create New...