mbhsict

Hi @AlexBorro You can see in my screen the top and bottom port belonging to printers on v8 firmware, show the CRC errors for a period (until I disabled the camera) The middle ports belong to printers running v7.0.3.0 firmware Yes it looks like FCS as our network support were unable to capture anything due to the packets being dropped at the port before being able to reach further

I've had this logged with support ages ago but have made some more discoveries myself and was wondering if anyone had any similar experiences Ever since upgrading to v8 firmware - all of them including latest channel 8.3.1, we have noticed CRC errors appearing on the network ports that our S5 Pro bundles are attached to. Changing cables, network ports, switches etc had made no difference. I left the remaining machines at 7.0.3 due to the network engineers not being happy with the printers causing these errors. I have been playing around today and upgraded one of the problem machines to 8.3.1 incase by some miracle it was fixed, and then had the thought to remove the device from DigitalFactory as well. Immediately started to see a whole lot less CRC errors on the switch port. I enrolled it to DF again, hoping it was the firmware that fixed the issue, but they came back. After a lot of troubleshooting, it seems to be related to when any user/application views the built in camera - I have confirmed it by all the below spamming CRC errors on the port: DigitalFactory Printer config webpage Direct stream address on the IP address Cura 5.7 3D Printer OS 3rd party cloud slicing I'll log this again with support for some form of resolution, but has anyone seen anything with v8 onwards that changed how the camera stream is presented to users or applications that may cause these packets to be sent out of order, or with errors? Current workaround is now to disable the cameras to the dismay of users...

are future firmware releases planned for the S-Line printers or has all support moved to the Factor 4 printers? 8.3.1 was December 2023 and hasn't been moved to Stable channel yet

We have 4 S5 Pro Bundles, 2 exhibit these same symptoms only after upgrading to 8.x firmware No amount of back and forth with Ultimaker has resolved it. They said downgrade to v7 as an option

you can see in the response headers that the api is in GMT timezone Probably best to account for this in your scripts etc and convert it to local time on your end { "connection": "keep-alive", "content-length": "1856", "content-type": "application/json", "date": "Mon, 01 Apr 2024 23:19:04 GMT", "server": "nginx/1.14.2" }

I'm using Grafana to log data from the local API, best suited to v7 firmware. I can then graph and alert on errors, supply levels, hours remaining on filters etc

We trialed the FormFutura BVOH which worked really well, but have gone with the Ultimaker Breakaway support as a good tradeoff to cut down the time and mess of the soluble support.

yep understand all that, perhaps I should use the material empty flag on the api as the trigger for my alert email. The printers will sit there for days until someone tells us that it is out of material, if thats mid print it can be an issue. I have a dashboard that shows us the amount remaining on all the slots across the fleet of printers, but without an accurate measure on the tag, its not very reliable.

The material remaining on the spool tag is only read for display purposes then I guess. If there is an end of roll sensor in the material station, the remaining field on the tag could be whatever you like, its only going to affect the display bar. As it is now I have a printer which when queried via the api is showing remaining amount of 0 yet is happily printing away. I guess the empty flag gets set when the end sensor is tripped. { "slot_index": 2, "material_guid": "44a029e6-e31b-4c9e-a12f-9282e29a92ff", "direction": 0, "material_selection_source": "RFID", "material_insertion_datetime": "2024-03-25T00:41:23", "status": "loaded", "material_empty": 0, "material_remaining": 0, "material_remaining_mm": 0 }, Kind of makes it hard to try and report when machines are empty.

thanks, I've taken some readings and found below. New full spool - NFC reads 750000 New full spool - scale weight 1019g Empty spool - scale weight - 229g That leaves 790g of material, yet the tag is programmed with 750g of material. Is this an extra 40g that can't be printed because of the length to feed up the bowden tubes? I'll measure a few more semi-used spools and compare scale weights to nfc readings and see if there if the 40g difference is consistent. On more than one occurrence, we have had the printers say material is empty, when there looks to be quire a few loops of the spool left.

I had no end of trouble with PVA material and how it goes so brittle even with the material station. Ended up using some 3rd party BVOH material for disolvable support which was so much better.

I'm using an Elatec TWN4, and it works with the Director software it comes with. I can read the tags to some degree, just not sure of which pages etc to look at for the material remaining. Was hoping the SpoolMaker program would make it a lot easier. I am reporting on how much material is remaining in our Material Stations to save treking around campus all the time for replacement material. I have found that the amount remaining is not very accurate so would like to weigh it, update it and see if if the values drift.

I'm getting the error below, any workaround? Have Cura 5.6 and 5.0 installed Edit: Have tried manually starting the few 'Smart Card' windows services without any resolution

We have been running BVOH after a rather large investment and failure of the Ultimaker PVA. I was able to print with the generic PVA profile without too much hassle, until we were able to load in the specific settings from the material manufacturer. Yes you will need a BB print head for soluble material. We have now been testing the Ultimaker Breakaway support which has been performing very well, as we have students printing for school work, having them to deal with water and the time taken to dissolve the supports was not really feasible.

Are there any plans in the works to bring in some form of slicing to the Digital Factory system? As a Google Reference School, we have 1:1 Chromebooks for staff and students. We currently use 3DPrinterOS to do all the slicing, job management, print costing etc, but would be great to be able to keep this in the one banner as we can't use Cura on a Chromebook. Thanks