Firmware v0.7.0

[ajf]

Version 0.7.0 of the MOD-t firmware has been released.  I'm running my first test print with it now, a 20mm cube.  Haven't tried printing from the cloud interface or even allowing MOD-t to connect to WiFi.

To early to say how well this update preforms overall, but I am seeng what looks like more and longer pauses during the print than I did with 0.5.* versions.

Please share your experiences with 0.7.0.

[Loke]

So far it connected to wifi and it has made two small prints from my library. Huge progress!

[Atrix]

I have spoken with mod-t they currently have a massive back log of replacement hot ends going out, so I have to wait 4 weeks for them to come in and then they will send one out :( 

[Christopher Leger]

The 0.7.0 upgrade went smoothly for me as did the desktop app update.

I ran a few hour print tonight (bust of Batman) after updating to 0.7.0 - however, I used Cura and not the store.  

It was one of the largest and best prints I've done yet I think.

I didn't notice any changes in the printing behavior overall.

Until I have control over settings like infill percentage and base raft/brim via the store, I have no reason to ever go back to using the store.

(as an aside, since I've been using a very thin brim, keeping the cover on and blue tape on the base, I've had zero problems with adhesion over 10+ prints!)

My only issue at this point is once in a while just after the initial head drop to the bed at the very start of the calibration process, the whole thing just stops.  I usually crank up the head an inch manually and reload the gcode file and try again.  It always works on the second try.  I haven't been able to tell if it is a firmware issue or a problem with my start settings in Cura, but I suspect is is firmware because if it was the start settings, I'd be seeing the behavior for every print.  This happened on my 0.7.0 print tonight so whatever it is, it is still there, but it is a minor inconvenience.

Chris

[Sanosuke en-la-red]

For me it is the worst so far firmware.
With 0.6 after two hours of hot-end printing suddenly melting down the entire model and making a major hole in the printing bed.
With 0.7, three impressions on two printing bed shifted leaving the model shifted one axis.
I am considering to downgrade to 0.5.3

Sorry for my english

[Jacob Zdvorak]

Version 0.7.0 seems exactly the same to me.  I've printed 4 things since the firmware upgrade.  The Tipsy Vase bottom piece printed no problem over wifi from the store.  The main, larger part of the Vase failed at 53% complete (also over wifi from the store).  The printer just stopped mid print.  The fan shut off and the nozzle melted the print until it cooled off.  I then tried printing a case I made in 123D and exported to Cura.  I used an INI file and settings I got from http://blog.mitchelledgar.com/?p=142.  About 30% into the print the X-Axis motor went full speed and slammed the bed into the wall and just kept spinning grinding away the teeth at the bottom of the bed.  I then uploaded the exact same STL file to the New Matter store and printed over Wifi with no problems.  Worked perfectly. (I had a second bed I got from New Matter with good teeth).

This is the exact same behavior I got with 0.6.0.  Both from the New Matter store and using 123D and Cura (same settings and INI).

[Jacob Ramsey]

What is the more or less consensus on most stable firmware? 

Having lost my printer to a jam about a month ago and sending it back, I have just gotten it back and I am looking to get up and running fast without having a month or so of hands on experience with anything past .5.

[ajf]

I've found 0.5.3 to be most stable. But I don't let it connect to WiFi and use Slic3r.

[Christopher Leger]

With regard to firmware versions, I think that your own experience with your machine will be the determining factor.

I experienced some of the minor issues early on (i.e. failed prints partway through) but I never had the platform-penetrating nose dive that many seemed to have nor most of the other issues.

I have to believe that there must be quality variations within the ARM chip they used - that is the only thing that I can think of that explains why there are some of us who have been thankfully unaffacted by the major bugs.

As they say - your mileage may vary.

Best of luck to you.

[Jacob Ramsey]

I have been running .7 since I got a machine back from New Matter. Purposefully never set up wifi. At this time I have started 9 prints, with only 1 failing. These are about 4-5 hour prints.

Comparatively, when I was using .5 or earlier, with wifi on, about 50% of my prints would fail.

 

So while not true experimentation in that I have two parameters that have changed, I am not willing to open up the wifi as it just doesn't add any value with the new matter store.

Cannot speak for the internal ARM chips, but the current state of the printer on my desk is much better off than it was.

[Jesse Klug]

I have been having good luck with prints when using Cura and printing direct. WiFi jobs seem to never finish uploading, The web console sticks at sending status perpetually. I've printed a few simple jobs and a 6+ hour long job, no failures yet from direct print.

On Wednesday, December 16, 2015 at 3:50:13 PM UTC-5, ajf wrote:

[Alan Hyman]

Hello Jesse,

What are the settings you use for Cura?