SeeDiph
-
Posts
8 -
Joined
-
Last visited
Content Type
Forums
Events
3D Prints
Posts posted by SeeDiph
-
-
I don't remember seeing those files but will give it another try.
-
Sorry for the delay. All your insight is appreciated. Here is what I have from this week's efforts.
cap_NJF-UMS3_2021-02-18_22.24.30_X195.0Y155.0_sensor_reset.log cap_NJF-UMS3_2021-02-18_22.24.46_N1_X173.0Y155.0.log cap_NJF-UMS3_2021-02-18_22.25.03_N0_X195.0Y155.0.log cap_NJF-UMS3_2021-02-18_22.25.12_N0_X215.0Y175.0.log cap_NJF-UMS3_2021-02-18_22.25.14_N0_X215.0Y135.0.log cap_NJF-UMS3_2021-02-18_22.25.16_N0_X215.0Y95.0.log cap_NJF-UMS3_2021-02-18_22.25.19_N0_X175.0Y15.0.log cap_NJF-UMS3_2021-02-18_22.25.21_N0_X175.0Y55.0.log cap_NJF-UMS3_2021-02-18_22.25.23_N0_X175.0Y95.0.log cap_NJF-UMS3_2021-02-18_22.25.25_N0_X175.0Y135.0.log cap_NJF-UMS3_2021-02-18_22.25.27_N0_X175.0Y175.0.log cap_NJF-UMS3_2021-02-18_22.25.30_N0_X135.0Y175.0.log cap_NJF-UMS3_2021-02-18_22.25.32_N0_X135.0Y135.0.log cap_NJF-UMS3_2021-02-18_22.25.34_N0_X135.0Y95.0.log cap_NJF-UMS3_2021-02-18_22.25.36_N0_X135.0Y55.0.log cap_NJF-UMS3_2021-02-18_22.25.38_N0_X135.0Y15.0.log cap_NJF-UMS3_2021-02-18_22.25.40_N0_X95.0Y15.0.log cap_NJF-UMS3_2021-02-18_22.25.42_N0_X95.0Y55.0.log cap_NJF-UMS3_2021-02-18_22.25.44_N0_X95.0Y95.0.log cap_NJF-UMS3_2021-02-18_22.25.47_N0_X95.0Y135.0.log cap_NJF-UMS3_2021-02-18_22.25.49_N0_X95.0Y175.0.log cap_NJF-UMS3_2021-02-18_22.25.51_N0_X55.0Y175.0.log cap_NJF-UMS3_2021-02-18_22.25.53_N0_X55.0Y135.0.log cap_NJF-UMS3_2021-02-18_22.25.55_N0_X55.0Y95.0.log cap_NJF-UMS3_2021-02-18_22.25.57_N0_X55.0Y55.0.log cap_NJF-UMS3_2021-02-18_22.25.59_N0_X55.0Y15.0.log cap_NJF-UMS3_2021-02-18_22.26.09_N1_X215.0Y95.0.log cap_NJF-UMS3_2021-02-18_22.26.12_N1_X55.0Y175.0.log cap_NJF-UMS3_2021-02-18_22.26.14_N1_X55.0Y15.0.log cap_NJF-UMS3_2021-02-19_03.10.30_X195.0Y155.0_sensor_reset.log cap_NJF-UMS3_2021-02-19_03.10.47_N1_X173.0Y155.0.log cap_NJF-UMS3_2021-02-19_03.11.04_N0_X195.0Y155.0.log cap_NJF-UMS3_2021-02-19_03.11.12_N0_X215.0Y175.0.log cap_NJF-UMS3_2021-02-19_03.11.14_N0_X215.0Y135.0.log cap_NJF-UMS3_2021-02-19_03.11.17_N0_X215.0Y95.0.log cap_NJF-UMS3_2021-02-19_03.11.19_N0_X175.0Y15.0.log cap_NJF-UMS3_2021-02-19_03.11.21_N0_X175.0Y55.0.log cap_NJF-UMS3_2021-02-19_03.11.24_N0_X175.0Y95.0.log cap_NJF-UMS3_2021-02-19_03.11.26_N0_X175.0Y135.0.log cap_NJF-UMS3_2021-02-19_03.11.28_N0_X175.0Y175.0.log cap_NJF-UMS3_2021-02-19_03.11.30_N0_X135.0Y175.0.log cap_NJF-UMS3_2021-02-19_03.11.32_N0_X135.0Y135.0.log cap_NJF-UMS3_2021-02-19_03.11.34_N0_X135.0Y95.0.log cap_NJF-UMS3_2021-02-19_03.11.36_N0_X135.0Y55.0.log cap_NJF-UMS3_2021-02-19_03.11.39_N0_X135.0Y15.0.log cap_NJF-UMS3_2021-02-19_03.11.41_N0_X95.0Y15.0.log cap_NJF-UMS3_2021-02-19_03.11.43_N0_X95.0Y55.0.log cap_NJF-UMS3_2021-02-19_03.11.45_N0_X95.0Y95.0.log cap_NJF-UMS3_2021-02-19_03.11.47_N0_X95.0Y135.0.log cap_NJF-UMS3_2021-02-19_03.11.49_N0_X95.0Y175.0.log cap_NJF-UMS3_2021-02-19_03.11.51_N0_X55.0Y175.0.log cap_NJF-UMS3_2021-02-19_03.11.53_N0_X55.0Y135.0.log cap_NJF-UMS3_2021-02-19_03.11.56_N0_X55.0Y95.0.log cap_NJF-UMS3_2021-02-19_03.11.58_N0_X55.0Y55.0.log cap_NJF-UMS3_2021-02-19_03.12.00_N0_X55.0Y15.0.log cap_NJF-UMS3_2021-02-19_03.12.09_N1_X215.0Y95.0.log cap_NJF-UMS3_2021-02-19_03.12.12_N1_X55.0Y175.0.log cap_NJF-UMS3_2021-02-19_03.12.15_N1_X55.0Y15.0.log dmesg.log flow_NJF-UMS3.log process_data.log sensor_data.log
-
I'll definitely grab the log files when I get back home.
Interestingly, if I slice the same files with Simplify3D and then load that Gcode into Cura and send it to the printer it works just fine. Must be an error introduced with cura slicing? I went so far as to install a legacy version of cura on a different computer and the error persisted.
-
Alright here we go again... This fails with a line error = 64
-
I will post the next time I get the error. It seems like if I manipulate anything on the build plate it seems to happen
-
Still getting the error even with the usb removed. Supposedly they swapped out the board when I sent it in. So bizarre...
-
I seem to be having a recurrent and persistent error which has severely limited the utility of my S3. I continue to get "line errors" on simple geometries I'm trying to print. I have been in contact with service and have really seemed to have tried everything without finding a solution. I have designed using different programs (tinkercad, MOI), updated firmware, used print over network, used local printing with two different USB drives, redesigned the object from scratch, etc etc. Finally I sent the machine into service for an overhaul last month despite it being less than a year old. It worked as expected for a couple prints and now is back to the same errors. I haven't found any solutions I haven't tried elsewhere apart from returning it for a replacement. I was hoping for a little insight into what might be worth trying. I'm very frustrated.
I've included two of the files I've tried without success.
Nathan
Recurrent Issue with "Line Error" on S3
in UltiMaker 3D printers
Posted
So I think I have the issue figured out. Filleting was introducing very small errors in the models, thus making them non-manifold but for whatever reason, cura was not detecting it. Repaired in mesh maker, all the problem files print without issue.