Hi,
I'm sorry to hear you're having issues with the latest firmware.
Do you have a USB stick inserted while the problem occurs?
If so, there would be some log dumps on it.
Can you send these to us, using wetransfer?
(Send a PM with the link to wetransfer, so I can take a look)!
I will try to do this tomorrow when I get to work.
But, is it possible to roll back to the previous firmware?
Can you see if the gcode sliced by Cura have the same problem?
Going back to an older firmware might not be the answer to your problem.
As I said, I'm also having problems with Cura. See thread https://ultimaker.com/en/community/51884-cura-doesnt-respond. So I'm pretty much screwed.
Edited by GuestI have fixed the unrelated problem with Cura by rolling back intel graphics drivers https://ultimaker.com/en/community/51884-cura-doesnt-respond?page=1&sort=#reply-192500
I have finally been able to create model with cura to send to the ultimaker. It started printing fine without rebooting, so the issue seems to be with gcode generated by Simplify3D. Sorry I forgot to get a log file before printing. I'll try to get one later.
I hope I can go back to Simplify3D as I prefer it's handling of support structure, in particular it's ability to manually manipulate support. I will contact Simplify3D to see what they say about this issue.
Is it possible to get the sliced gcode you made using slice3d?
It still not a good sign that that would cause a printer rebooting.
I'm glad that Cura now works for you and that you can print again.
I will send it to you in a private message. Thanks.
If you can try slice3d again with the printer and get us the logs that would be helpful.
I've tried the sliced gcode and it just starts printing without rebooting or other issues.
After talking with my colleagues, @daid mentioned something I forgot about.
The printer reboot would normally not happen when trying to print, except when the power consumption gets too high, for example when heating up build plate/cores. In that case, the power brick will reset itself. causing loss of power to the printer.
The second time it will be ok because then less power is required since build plate and PrintCores have been heated up for a bit already.
When you notice the printer rebooting, can you verify if the power brick led is also turned off and on?
Also are you using the original Ultimaker PrintCores?
What you say makes a certain sense, however,
- why would it just appear after the firmware upgrade? Does the new firmware perhaps heat more quickly?
- why would why would it matter if it the gcode were created by Cura or Simplify3D? Or is that just random? Since the firmware upgrade all my files created on Simplyfy3D had the reboot, and the only one I've tried from Cura worked.
I don't know what LED you want me to check. Yes, they are the original Ultimaker print cores.
1. I will have to check later but I think some optimisations have been made for decrease waiting time.
2. I doubt it would have to do with either slicer. Mere coincidence. If you check multiple from Cura, try doing so from a fresh start (ie. a cold printer)
3. The led on the power brick, which emits a blue light when it's on.
Just had another reboot, with a file created on Simplify3D. The blue light around the wheel on the front went out, if that is what you are refering to. I dumped the logs to the usb. They are here:
Ultimaker Logs
Password: VkihEQqA
https://campbellu.egnyte.com/fl/cHi2I7uVCC
The next file, created in Cura started fine.
Regarding the heating hypothesis, the extruders were already warm, since I primed them first. So I really don't know how relevant that is.
So, as this continues to be a problem, is there a way roll back to the previous firmware? I cannot find older firmware posted on-line.
So, as this continues to be a problem, is there a way roll back to the previous firmware?
Sure. Basically use the "Updating via USB" instructions. All releases are listed here:
http://software.ultimaker.com/jedi/releases/
...and please keep us posted if the older release solves this issue for your printer.
Just had another reboot, with a file created on Simplify3D. The blue light around the wheel on the front went out, if that is what you are refering to.
That's not the led I was talking about. The brick that comes with the printer that you put into the power outlet on one side, and on the other side, it will connect to the printer, has a small blue led.
I will check the logs...
@tinkergnome I understand why a rollback could help getting started with printing again. However, I would rather find the cause.
Rolling back, in this case, might not solve the problem.
However, I would rather find the cause.
Rolling back, in this case, might not solve the problem.
I fully agree. But @shassel asked kindly (and it doesn't hurt to rule this out). 
Well now I don't know what to think. I tried a new Simplify3D file today, expecting a reboot and I was watching the LED on the power "brick" -- sorry, new term for me and I didn't know what you were referring to -- to see if it went out. Lo and behold, the print started without rebooting.
Now I don't know if this is random or what. Since upgrading firmware, all S3D files rebooted, and then sometimes restarted. None of the Ultimaker files did. But some of that could be that by the time I tried the Ultimaker files, the heaters were already warmed up.
Or could it be something in my file. I regenerated my stl's and tweaked some of the settings in S3D, so maybe it's something there. I'll send a message with my latest file that printed today.
Additionally, I contacted Simplfy3D about the issue. They said they hadn't seen this problem "in some time." So, they've seen it before? I'm going to send them some files and see what they have to offer.
I do prefer Simplify3D over Cura, primarily due to it's handling of support. And it is a common interface for our multiple printers.
Keep us posted and keep an eye on the brick when starting the print to see if it turns off when you experience the problem.
I'll be here to help.
The folks at Simplify3D have also been working on this problem and have send the following startup gcode for me to try. See copied response to their email below.
My response:
Thank you very much. It came at a convenient time so I tried it right away. It worked from a completely cold start. I must say, however, that recently other files created by Simplify3D have also worked. If I understand the gcode correctly, what you did makes sense, you are heating one element at a time and waiting for it to reach temperature before turning on another. Makes sense, but I can’t guarantee that it’s solved the problem and it won’t come back.
Nor do I understand the interaction with the new firmware, unless Ultimaker is trying to heat to setpoint faster than it used to.
Simplfy3D's Email:
The combined heating could very well be the issue with these prints. Can you please try adjusting the start script and recreating the file? I've adjusted the start script and included it below.
M106 S0 ; fan off
M204 S1500 ; default acceleration
M205 X15.00 ; maximum X Y jerk
T1
G1 X20 Y5 Z5 F15000.0 ; heating location
M140 S[bed0_temperature]
M190 S[bed0_temperature]
M104 S[extruder0_temperature] T0 ; heat left
M109 S[extruder0_temperature] T0 ; stabilize left
M104 S[extruder1_temperature] T1 ; heat right
M109 S[extruder1_temperature] T1 ; stabilize right
G1 Z0.2
G92 E0 ; zero extruder
G1 E30
G92 E0 ; zero extruder
G1 X120 E15 F1000 ; purge right extruder
G92 E0 ; zero extruder
G1 E-12 F900 ; retract prior to tool change
G92 E0 ; zero extruder
T0
G1 Y5.5 F15000.0 ; allow space for left purge
G92 E0 ; zero extruder
G1 E30
G92 E0 ; zero extruder
G1 X2 E15 F1000 ; purge left extruder
Please let me know how well this works for you when starting from an environment where none of the heaters were heated up previously.
However, I would rather find the cause.
Rolling back, in this case, might not solve the problem.
I fully agree. But @shassel asked kindly (and it doesn't hurt to rule this out).
So do I, there has (for a long while) been firmware of past versions available at
https://software.ultimaker.com/jedi/releases
You need to download two files; both the file ending at *.tar.xz and *.tar.xz.sig
Put those files on a usb stick and choose the firmware update function from the printer menu.
More info on the procedure: https://ultimaker.com/...29-updating-firmware
but note that this path is not tested by us!
In the mean time @shassel the gcode header requirements have changed a little bit but I'm sure that @tinkegnome was also using Simplify3D in the beta of this software so I'm quite supprised... but you might need to add the the line ";EXTRUDER_TRAIN.0.NOZZLE.NAME:AA 0.4" to the gcode header...
I'm also missing the header in your start gcode example, shouldn't that be there?
sample valid header:
;START_OF_HEADER ;HEADER_VERSION:0.1 ;FLAVOR:Griffin ;GENERATOR.NAME:Cura_SteamEngine ;GENERATOR.VERSION:3.0.3 ;GENERATOR.BUILD_DATE:2017-10-17 ;TARGET_MACHINE.NAME:Ultimaker 3 ;EXTRUDER_TRAIN.0.INITIAL_TEMPERATURE:210 ;EXTRUDER_TRAIN.0.MATERIAL.VOLUME_USED:3629 ;EXTRUDER_TRAIN.0.MATERIAL.GUID:506c9f0d-e3aa-4bd4-b2d2-23e2425b1aa9 ;EXTRUDER_TRAIN.0.NOZZLE.DIAMETER:0.4 ;EXTRUDER_TRAIN.0.NOZZLE.NAME:AA 0.4 ;BUILD_PLATE.INITIAL_TEMPERATURE:60 ;PRINT.TIME:1626 ;PRINT.SIZE.MIN.X:9 ;PRINT.SIZE.MIN.Y:6 ;PRINT.SIZE.MIN.Z:0.27 ;PRINT.SIZE.MAX.X:129.27 ;PRINT.SIZE.MAX.Y:118.474 ;PRINT.SIZE.MAX.Z:33.87 ;END_OF_HEADEREdited by Guest
Well I still haven't rolled back. The work-around supplied by Simplify3D seems to be working, just staging the heating so everything doesn't draw power at the same time.
Regarding the header, it is not missing. I only pasted here the snippet that S3D calls startup. The full gcode has a header, but some commands are missing, particularly the EXTRUDER_TRAIN... commands. It is pasted here.
;START_OF_HEADER
;HEADER_VERSION:0.1
;TARGET_MACHINE.NAME:Ultimaker 3
;GENERATOR.NAME:Simplify3D
;GENERATOR.VERSION:3.1.0
;GENERATOR.BUILD_DATE:2016-10-03
;FLAVOR:Griffin
;BUILD_PLATE.INITIAL_TEMPERATURE:60
;PRINT.TIME:11836
;PRINT.SIZE.MIN.X:0
;PRINT.SIZE.MIN.Y:0
;PRINT.SIZE.MIN.Z:0
;PRINT.SIZE.MAX.X:215
;PRINT.SIZE.MAX.Y:215
;PRINT.SIZE.MAX.Z:200
;END_OF_HEADER
ArunC posted a topic in UltiMaker Cura,
.thumb.jpeg.0b7a05eafc09add17b8338efde5852e9.jpeg)
Recommended Posts
shassel 2
This keeps happening, on mutiple files. All are created in Simplify3D. I'm trying to create some files to send in Cura for troubleshooting purposes, but that has its's own problems -- see https://ultimaker.com/en/community/51884-cura-doesnt-respond.
So, is it possible to roll back to previous firmware?
Link to post
Share on other sites