- User Since
- May 11 2019, 6:56 AM (27 w, 2 d)
Oct 8 2019
Oct 1 2019
Sep 30 2019
Okay, sounds good and will check myself as well the next time I updated the firmware.
Sep 26 2019
@karrad, not sure this is the best way to communicate this :-), but since my original reason for changing the startup gcode was to improve leveling, I thought I would mention something I just noticed ...
@anolen, okay I just did some testing.
Sep 25 2019
@anolen, I apologize I have not had time to replace my version of the code with yours yet. I should be able to do an external test for you on Thu though.
Sep 21 2019
@anolen , I am so excited that you were able to take time to work on this - thank you. I like all your "WHY" logic and appreciate your detailed explanations. On the wipe temps, like I said, after more testing I'm not so sure raising those - at least not as high as I suggested - is a good idea, but maybe some testing to do there. Very interesting on your logic on the fans and the different materials - that would have never crossed my mind. I'll give your updates a whirl this weekend and report back. Thanks again. Oh, can you link me to the newer wiper mount - I'd like to see which I have. If I have the older one, I assume there must be some value in switching to the new one?
Sep 16 2019
@anolen, a couple things I've noted in subsequent testing:
@karrad, I did not notate that, however, I will see if I can re-create it and get that info back to you.
Aug 31 2019
Aug 27 2019
@victor_larchenko, thank you for fixing this. :-)
Aug 26 2019
Any chance of this getting fixed in an upcoming release? I know it's not an emergency thing, it's just annoying when things like this don't work :-) :-).
Aug 25 2019
Aug 23 2019
Aug 22 2019
@karrad, thank you, much appreciated.
Jul 30 2019
@Steven well hallelujah, let's celebrate!!!!!!!!!!!!!! It works :-) ... I tested it both starting out NOT connected and being connected and no failures, worked like a champ. Thank you guys for fixing this.
Jul 29 2019
@karrad yes, here is what I do each time before installing a new version:
Testing under 3.6.17, Windows 10:
YES YES YES that is awesome!!!!!!!!!!!!!!!!!!!! :-)
Jul 26 2019
Jul 25 2019
Jul 22 2019
Jul 19 2019
See T8014 for more details ... this needs fixed!! :-) :-) :-)
Cura LE 3.6.13
I know this doesn't mention what toolhead, but in T8768 I mentioned that I had this problem on a TAZ 6 with Aerostruder and Inova 1800 specifically and that in other forums others experienced thermal runaway too with higher temp materials (with Aerostruder). The solution was to put an E3D silicone sock over the hotend and all problems went away. From what I recall heat deflecting off the bed and I guess getting trapped against the hotend and increasing it's temp for high temp materials was the root cause. Just FYI if it helps.
Jul 18 2019
@victor_larchenko that's awesome!! :-)
Jul 15 2019
I had this problem with TAZ 6 and Aerostruder and the solution was to put a E3D silicone sock on the hotend. I assumed the heat reflecting off the build plate and the higher temp of the Inova 1800 was causing the hotend to overheat (I found others with similar issues in other forums) - the sock 100% fixed this with all higher temp material.
Look at T8014 under the heading "Test 1 (3.6.10)". I have this problem all the time, but my notes under that section indicate how I am able to get it to work.
Jul 11 2019
I might be repeating part of what I said in an earlier comment, but for me it has happened on all versions from 3.2.32 all the way up to 3.6.14. I am running Windows 10.
Jul 9 2019
This happened to me last night. I thought maybe there was just a timeout and it purposely had gone back the main screen, but I'm guessing it was rebooting. This has happened twice to me that I remember.
Jul 6 2019
Jul 5 2019
This happens to mine as well - I'm constantly trying to adjust it to not rub against it.
Jul 3 2019
So last night after installing and playing with Cura 3.6.13 (~4pm), I left it open overnight and could not get the settings bar to disappear. But now today (~1pm) - again it was left open overnight - it happens about every other time I open/collapse a bar. Just more info I guess, maybe related to leaving it open, dunno for sure.
Jul 2 2019
This has happened to me all the time in 3.2.x and 3.6.x, at least up to 3.6.10. The description says putting something in the search bar fixes - switching between to the Monitor tab and back to Prepare tab also "fixes" it.
Jun 19 2019
@alexei, thank you :-).
Okay, well I don't see a way to post to the Marlin board :-) ... @karrad, help, sorry :-).
Err, I realized this morning I posted this to the wrong board. I'm guessing this would be more appropriate on the Marlin board so I'll post there. I cannot seem to find how to delete this one though :-/ ... can someone who has appropriate rights rectify this and delete it? Sorry for the mistake.
Jun 18 2019
Ah ha, this is what I was seeing a few nights ago too - I suspected what was causing it was already being connected, because after it would crash I would reload and try again without connecting first and that does seem to work. ALTHOUGH, I am fairly sure I was using 3.6.10 (Windows 10) and it still happens there too (not just 3.6.8).
Jun 12 2019
While making it not flash at all would be ideal, could you just put a message in Cura during the flashing that the LCD screen might flicker and that this is normal. Maybe then also make part of the "flashing procedure" that after flashing, tell the user via a dialog to recycle the printer to complete the process. An idea that might make it seem "normal"/"expected" :-).