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!
Strap in for the first Cura release of 2024! This 5.7 beta release brings new material profiles as well as cloud printing for Method series printers, and introduces a powerful new way of sharing print settings using printer-agnostic project files! Also, if you want to download the cute dinosaur card holder featured below, it was specially designed for this release and can be found on Thingiverse!
S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
(Sorry, was out of office when this released)
This update is for...
All UltiMaker S series
New features
Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
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