Hi Bob, and many thanks for the reply.
I'm very glad that your experience is different from mine, and mostly positive. I still believe that the Ultimaker S5 is a good, reliable 3D printer, and would really hate to have to end up purchasing a different brand (what else is there anyway, at this level of performance, open architecture, selection of materials, track record?). This is my first 3D printer, but I know about 3D printing and have played with friends' and colleagues' machines. Trust me when I say that I'm the kind of person that's very comfortable and "at home" in understanding and handling such machines. I'm pretty sure that what I've experienced so far, as outlined in my post above, was not caused by user error. It was the reseller (a trained professional) that actually did most of the interaction with the printer anyway, and he was as much, if not more, puzzled than me. Jokingly, after the 2nd printer failed test, he suggested I should play the Lottery, because the chances of the 2nd machine not working were so low...
Something I want to say (again) is that when the Ultimaker S5 works as it should, it really shines! I mean that. I saw that. We were able to print a couple of objects that came out really beautifully. No distortions, no stringing, no warping, no blobs, no problems. We even printed with PVA and the object came out perfectly clean. But the statistics of good vs. bad behaviour were not in our favour, at least on the two units that we played with.
Another thing I must note is that the local reseller did (and are still doing) everything in their power to help out and resolve all issues. They also tell me that they are in contact with Ultimaker HQ, and the mother company is also doing their best to help in solving the problems. It's very good to know that there is good support when we need it most.
About Marlin, I know it's a very well-respected platform for 3D printing. I don't have a problem with a microcontroller being 8-bit vs. 32-bit. Not at all. Some of my best designs are 8-bit and are rock-solid. It's more of a quality issue for me, being something that came out of the makers' community, where sometimes bugs and poorly written code can creep in. From my experience and observation of the two Ultimakers, I wouldn't blame Marlin, but, perhaps, the connectivity and data feed between the Linux small computer and the Marlin h/w. Maybe that UART stream isn't as stable as it should be. Maybe something gets corrupted in there, and forces Marlin to misbehave. Maybe Marlin is fed bad data and just does as instructed. What would help validate or reject my guess, is to compare printer stability between the new machines (S5, S3) and the old ones (3, 2+). If the old ones are rock-solid and don't freeze mid-print, no UI crashing, no need for power-cycling, etc., this could mean that the new implementation (Linux system, touch screen) may be to blame. I hope this gets sorted out in a future f/w update and the machines become nice and stable, if they aren't already.
The reseller will be coming to our lab tomorrow morning to collect the 2nd Ultimaker S5 and take it to their lab for extensive stress-testing and observation using special G-codes from mother Ultimaker, as well as their own objects. If everything goes smoothly and any issues rectified, the printer will be back to our lab by mid-February. I will do a thorough post-delivery inspection before turning it on, as you've suggested, and report here what I observe. I really, really hope everything will be sorted out in the end.
To the Ultimaker community: just to help get to the bottom of this, I'd love to have some data about the underlined text above. Any users out there with experience in both the new (S5, S3) and old (3, 2+) Ultimaker machines? Any comments on how they compare in terms of overall stability? Is one generation more stable than the other? Would love to hear from anyone with such experience.
Looking forward to more replies from the community (hopefully positive, like Bob's). To everyone, thanks in advance for any information shared, I really appreciate it.
I have an S5 Pro Bundle and have not seen the issues you saw. I have indeed seen this and that, but not what you have seen. The S5 has been out for a while and it is a bit odd to have issues like you are reporting. That is in no way saying things did not happen, only that they are out of the "normal range". My guess is there is something different about what you are doing with your printer or wrong with your printer. Again, not to say "doing wrong", simply different. Without being there and directly observing, this would become a "10,000 questions" sort of thing. We are far more likely to get tangled up doing that vs actually finding a root cause.
There are a number of things I would run through on a printer in front of me *if* this was my printer. Mostly they involve checking various mechanical bits and pieces. Each should "look right" and "feel right". That's of zero help if you have not seen and worked with a printer before. Hopefully your dealer *does* have experience. I have had many printers arrive with shipping induced this and that. I always go over any printer before I turn it on. ....... actually not always. Always since I damaged that first one turning it on back about 10 years ago 🙂
The "Arduino" core is present to run firmware based on Marlin in its native environment. It is a *very* well respected approach and pretty much bulletproof. Porting the code to a 32 bit MCU has been a "real soon now" work in progress for many years. They are getting closer and closer.
The Linux side of things handles what you would expect it to: the com with the outside world and fun stuff like that. You likely could bring out a serial port and feed the gcode file into the Arduino to get a full print. The bells and whistles would not work ( = no camera / WiFi / remote status reports). Integrating true real time code into a Linux machine is not at all easy. Linux is not something I would pick as an RTOS.
Link to post
Share on other sites