Jump to content
Ultimaker Community of 3D Printing Experts

zakeen

Member
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

2 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. SOLVED: There is a bug.... In my first post I wrote a list of what I did to try and solves this. It seems they have fixed something in an update half way through my solving because the end result the bug is: With my Gcode, plus Flow Sensor unplugged and Flow Sensor disabled this errors shows. Also, with this exact Gcode on a different S5 with Flow Sensor disabled and unplugged it shows the same error. We have yet to identify what is wrong with my Gcode. With the Distributor's Gcode everything works fine and they were only able to get my Gcodes working if Flow sensor was plugged in
  2. The flow sensor has not been working for the life of the printer. I never worried about it as I cam from the UM 2 and it doesnt have one. I have disabled them both after following: Thanks also for the recommendation Priddy,
  3. Do you mean this? This was done directly after it crashed and only way was to restart it then capture the log files then. cap_Ultimaker-00b763_2019-02-14_10.20.13_N0_X186.5Y213.5.zip
  4. Do this at your own risk. You can extend the printer build plate size in the settings you have posted. I also ran into the same problem as you and increased it just 5mm and that was enough. This worked on the UM 2+ I have never tried on my S5 so I can not say it works for all system.
  5. I have flow sensor disabled but never tried to unplug it and print it. I will try. Thanks.
  6. I did not try to print directly from Cura over wifi. Never done this before. I will try it.
  7. This is the log file: [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.14.32-ultimaker (root@runner-ptzpiGvW-project-11447330-concurrent-0) (gcc version 6.3.0 20170516 (Debian 6.3.0-18)) #3 SMP Tue Jan 21 13:06:10 UTC 2020 [ 0.000000] CPU: ARMv7 Processor [410fc074] revision 4 (ARMv7), cr=10c5387d [ 0.000000] CPU: div instructions available: patching division code [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] OF: fdt: Machine model: Ultimaker UM3-XL (2621) [ 0.000000] bootconsole [ea
  8. From first looks it seems to me just looking at the end product that in your CURA settings the S5 has higher height of layers. Have you checked the CURA settings? - to see if they are the same. S3 looks fine and S5 looks draft quality.
  9. Depending your work environment temp and humanity levels can affect the figment. If it gets too soft sometimes the feeder can not grip it enough. To test the proper way, remove the figment and just check if you have lots of wear at the point just after you feed the figment into the UM. What happens is the figment gets too soft and the feeder can not grip it and it just wears it out at that point. The printer thinks its still feeding through. To fix this in future you can remove about 3 cm at the end of the current figment, that would make the part that was worn a little past the point of pa
  10. Someone please help.... I am desperate ... I have this error message: An unspecified error has occurred in the motion controller. Restored to default settings. This message appears just before its started to print. So after the bed levelling and pre warmup. What I have done so far, not in order and maybe I missed a few things: restored to default settings reset to factory settings calibrated lift switch downgraded firm where from 5.8.2 to 5.8.1 upgraded to 6.1.0 contacted ultimate distributor. was told to clean it. cleaned it again. still same proble
×
×
  • Create New...