UltiMaker uses functional, analytical and tracking cookies. Tracking cookies enhance your experience on our website and may also collect your personal data outside of Ultimaker websites. If you agree with the use of tracking cookies, click “I agree, continue browsing”. You can withdraw your consent at any time. If you do not consent with the use of tracking cookies, click “Refuse”. You can find more information about cookies on our Privacy and Cookie Policy page.
Printcore in head slot X is taking too long to warm up - Ultimainboard reboot happening in the background
Posted
· Printcore in head slot X is taking too long to warm up - Ultimainboard reboot happening in the background
Did you manage to solve this issue?
Our Atmel board also started rebooting during a print.
I also put the printer into dev mode to get logs, and as you see below it seems like the same issue. However, I never got the error "Printcore in head slot X is taking too long to warm up", as you did.
The error occurred in a PETG print, with relatively high temps. I was thinking it might be the powersupply having issues, so I will test with lower bed temp and lower print core temp, to see if I still get the error.
Snippet from logs:
Feb 16 08:25:42 ultimakersystem-ccbdd30032e5 python3[874]: 2021-02-16 08:25:42,221 INFO timeEstimator getTimeRemaining() total_time 20:20:12 scaling_factor 0.9526796062937224 compensated_total_time 19:22:27.579336 time remaining 18:02:26.854937 pure_cura_time_remaining 19:00:11.275388
Feb 16 08:26:44 ultimakersystem-ccbdd30032e5 python3[874]: 2021-02-16 08:26:44,481 INFO transportLayer BUILD:Jan 27 2019 22:52:07
Feb 16 08:26:44 ultimakersystem-ccbdd30032e5 python3[874]: 2021-02-16 08:26:44,486 INFO transportLayer Detected board with id #2
Feb 16 08:26:44 ultimakersystem-ccbdd30032e5 python3[874]: 2021-02-16 08:26:44,492 INFO transportLayer ADS1015 #0x48 ref.voltage=958
Feb 16 08:26:44 ultimakersystem-ccbdd30032e5 python3[874]: 2021-02-16 08:26:44,495 INFO transportLayer Marlin started
Feb 16 08:27:04 ultimakersystem-ccbdd30032e5 python3[874]: 2021-02-16 08:27:04,508 WARNING transportLayer ProtoError:Sequence number is unexpected (received, expected): 189,0
Feb 16 08:27:04 ultimakersystem-ccbdd30032e5 python3[874]: 2021-02-16 08:27:04,510 WARNING transportLayer Protocol error from Marlin received, send buffer: [MessageTuple(sequence_number=189, message='M105', callback_function=<function ApplicationLayer.__getIdleCommand.<locals>.<lambda> at 0x9ed12d68>, in_planner_buffer=False), MessageTuple(sequence_number=190, message='M105', callback_function=<function ApplicationLayer.__getIdleCommand.<locals>.<lambda> at 0x9ed12e88>, in_planner_buffer=False), MessageTuple(sequence_number=191, message='M105', callback_function=<function ApplicationLayer.__getIdleCommand.<locals>.<lambda> at 0x9ed12db0>, in_planner_buffer=False), MessageTuple(sequence_number=192, message='M105', callback_function=<function ApplicationLayer.__getIdleCommand.<locals>.<lambda> at 0x9ed12e40>, in_planner_buffer=False), MessageTuple(sequence_number=193, message='M105', callback_function=<function ApplicationLayer.__getIdleCommand.<locals>.<lambda> at 0x9ed12930>, in_planner_buffer=False)]
Feb 16 08:27:04 ultimakersystem-ccbdd30032e5 python3[874]: 2021-02-16 08:27:04,617 WARNING transportLayer Resend data request for sequence 0, but not found, before adjusting: [MessageTuple(sequence_number=189, message='M105', callback_function=<function ApplicationLayer.__getIdleCommand.<locals>.<lambda> at 0x9ed12d68>, in_planner_buffer=False), MessageTuple(sequence_number=190, message='M105', callback_function=<function ApplicationLayer.__getIdleCommand.<locals>.<lambda> at 0x9ed12e88>, in_planner_buffer=False), MessageTuple(sequence_number=191, message='M105', callback_function=<function ApplicationLayer.__getIdleCommand.<locals>.<lambda> at 0x9ed12db0>, in_planner_buffer=False), MessageTuple(sequence_number=192, message='M105', callback_function=<function ApplicationLayer.__getIdleCommand.<locals>.<lambda> at 0x9ed12e40>, in_planner_buffer=False), MessageTuple(sequence_number=193, message='M105', callback_function=<function ApplicationLayer.__getIdleCommand.<locals>.<lambda> at 0x9ed12930>, in_planner_buffer=False)]
Feb 16 08:27:04 ultimakersystem-ccbdd30032e5 python3[874]: 2021-02-16 08:27:04,619 WARNING transportLayer Resend data request for sequence 0, but not found, after adjusting: [MessageTuple(sequence_number=0, message='M105', callback_function=<function ApplicationLayer.__getIdleCommand.<locals>.<lambda> at 0x9ed12d68>, in_planner_buffer=False), MessageTuple(sequence_number=1, message='M105', callback_function=<function ApplicationLayer.__getIdleCommand.<locals>.<lambda> at 0x9ed12e88>, in_planner_buffer=False), MessageTuple(sequence_number=2, message='M105', callback_function=<function ApplicationLayer.__getIdleCommand.<locals>.<lambda> at 0x9ed12db0>, in_planner_buffer=False), MessageTuple(sequence_number=3, message='M105', callback_function=<function ApplicationLayer.__getIdleCommand.<locals>.<lambda> at 0x9ed12e40>, in_planner_buffer=False), MessageTuple(sequence_number=4, message='M105', callback_function=<function ApplicationLayer.__getIdleCommand.<locals>.<lambda> at 0x9ed12930>, in_planner_buffer=False)]
Feb 16 08:27:04 ultimakersystem-ccbdd30032e5 python3[874]: 2021-02-16 08:27:04,737 INFO transportLayer too long extrusion prevented
Feb 16 08:27:46 ultimakersystem-ccbdd30032e5 python3[874]: 2021-02-16 08:27:46,092 INFO transportLayer cold extrusion prevented
Feb 16 08:27:46 ultimakersystem-ccbdd30032e5 python3[874]: 2021-02-16 08:27:46,257 INFO transportLayer cold extrusion prevented
Link to post
Share on other sites
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
🚀 Help Shape the Future of Cura and Digital Factory – Join Our Power User Research Program!
We’re looking for active users of Cura and Digital Factory — across professional and educational use cases — to help us improve the next generation of our tools.
Our Power User Research Program kicks off with a quick 15-minute interview to learn about your setup and workflows. If selected, you’ll be invited into a small group of users who get early access to features and help us shape the future of 3D printing software.
🧪 What to Expect:
A short 15-minute kickoff interview to help us get to know you If selected, bi-monthly research sessions (15–30 minutes) where we’ll test features, review workflows, or gather feedback Occasional invites to try out early prototypes or vote on upcoming improvements
🎁 What You’ll Get:
Selected participants receive a free 1-year Studio or Classroom license Early access to new features and tools A direct voice in what we build next
👉 Interested? Please fill out this quick form
Your feedback helps us make Cura Cloud more powerful, more intuitive, and more aligned with how you actually print and manage your workflow.
Thanks for being part of the community,
The full stable release of Cura 5.10 has arrived, and it brings support for the new Ultimaker S8, as well as new materials and profiles for previously supported UltiMaker printers. Additionally, you can now control your models in Cura using a 3D SpaceMouse and more!
Recommended Posts
ndu 0
Did you manage to solve this issue?
Our Atmel board also started rebooting during a print.
I also put the printer into dev mode to get logs, and as you see below it seems like the same issue. However, I never got the error "Printcore in head slot X is taking too long to warm up", as you did.
The error occurred in a PETG print, with relatively high temps. I was thinking it might be the powersupply having issues, so I will test with lower bed temp and lower print core temp, to see if I still get the error.
Snippet from logs:
Link to post
Share on other sites