Yet another problem(Solved)
At least this one is new. After upgrading to firmware 3.3 my printer no waits to reach temperature before printing.
It just starts warming up the heatbed and nozzle and starts calibrating. Then before its each reached temperature it starts printing.
Has anyone else seen this issue?
Is it hardware or software? Is there anyway to fully reload the firmware and completely wipe the nvram etc? In there is bad upgrade settings.
This thing has been nothing but a headache I am starting to wonder if the einsy is faulty.
Re: Yet another problem
I've updated to v3.3 and am not having that issue. The startup sequence is controlled by the gcode. It might be interesting to open up the gcode file in a text editor and confirm that the M190 and M109 commands are present and in the proper sequence.
and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan
Re: Yet another problem
I haven't yet ugraded to the last FW version (shame on me 
), but this clearly seems to be an issue with your start gcode in your slicer.
Re: Yet another problem
Strange, all my research seems to point in that direction as well. I am using simplfy3d, I haven't changed anything in my profile. I have pasted the startup code below. I am not sure why s3d would just stop working. I checked my latest files and I am not seeing the m190 or m109. Going back to older gcodes do have the m190 and m109 codes. So it must be a bug in S3D.
Thanks guys!
Startup Code
G28 W ; home all without mesh bed level
G80 ; mesh bed leveling
G1 Y-3.0 F1000.0 ; go outside print area
G92 E0.0
G1 X60.0 E9.0 F1000.0 ; intro line
G1 X100.0 E12.5 F1000.0 ; intro line
G92 E0.0
M900 K30
Re: Yet another problem
So I was able to solve it.
In S3D under G-Code, Update Firmware Configuration was unchecked. Normally this on by default. All my other profiles had it. Adding that setting back on added back the missing m190 and m109 commands.
In case anyone runs into this issue.
Re: Yet another problem(Solved)
Happy to see that you solved your problem and thanks for sharing the solution!