I have to disagree with some of you. My TRONXY x5SA pro (latest edition 2021) is running quite fine with the provided 'Tronxy' software using SD-cards, but when I want to print with the more refined CURA 4.8.0 and USB the printer starts printing as expected, but stops in midprint after about 2 minutes, and does just heat the nozzle and the print bed, but does nothing more.
Printer problem? I do not think so. This looks more to be a software problem as I cannot move the printhead with the jogging keys too. Maybe the problem is in the firmware? I don't know. I am at a loss.
Can anybody of the wise gals and guys give a helping hand?
Peter
.thumb.jpeg.0b7a05eafc09add17b8338efde5852e9.jpeg)
Recommended Posts
Longtoke 25
While I get you're upset at your printer being damaged, you've incorrectly and unfairly attributed it to Cura...
Firstly, the Tronxy you mention is a DIY kit printer, that takes some experience to correctly assemble, while having several design flaws that leave the door open to all sorts of issues.
To quote one of the reviews I've just endured "My testing, however, was a long and frustrating experience due to a range of poor design decisions on this printer."
And another quote "I think with a total overhaul by an experienced owner, this thing could really shine. It’s just that the way it works out of the box leaves a lot to be desired".
While these issues may not be directly associated to the issue you have, it forms a continuing pattern with the printer in general. The manufacturers of the Tronxy package a butchered early version of Cura with a firmware that is a complete mystery and doesn't appear to function correctly. Also notably, the provided slicer requires excessive configuration for the default profile settings which also invites other gremlins into the scene.
Why am I detailing this ?....3d printing in general is not a plug and play affair. It does require some care, attention and time to learn the varied aspects involved, especially when you go the cheap route. DIY + cheap can end up being more expensive in the long run, especially if you don't invest time into it. That said, even with a high priced printer designed to be as user friendly as possible, there's still going to be issues at various times.
Another thing to note is the profiles themselves within Cura for 3rd party printers are community contributed, the Cura developers have little to nothing to do with them beyond gathering them up each release phase. If the profile itself caused the issue, contact the manufacturer and get them to address what is at issue with the printers firmware and / or profile for use in Cura.
Simply put, the onus is on you to ensure your printers compatibility with Cura ( which ever version you use ), and using 3d printers in general is not for the light hearted, especially when you're talking DIY kits from Chinese manufacturers. From the sound of it, you suffered an issue that could have been prevented by installing a $2 end stop on an axis, and was likely caused by the poor coding of the firmware driving it ( that seems to have misinterpreted the G-code commands issued by Cura ).
Sorry you've had such a poor experience, for many of us Cura works extremely well once CONFIGURED correctly when used on a printer with STANDARD Marlin based firmware that has appropriate safely equipment integrated ( end stops ). I would recommend figuring out which 32-bit control board you have and learning the ins-and-outs of firmware updates, install some additional end stops and then configure a profile suitable for Cura. Perhaps even contact the manufacturer and see what they can do to address it, but Cura isn't to blame for your printers malfunction.
Link to post
Share on other sites
GregValiant 1,110
Yes, that was a bad experience. As Longtoke points out, it wasn't the fault of Cura.
When you push the "Home" button, Cura sends the command "G28" to the printer and that is all it does. That G28 is interpreted by the firmware in the printer as "home all axis" and the printer starts the axis motors and moves the print head to the "0" endstops of the X, the Y, and the Z axis. The speed that the motors run at is also set within the firmware and Cura cannot effect the homing speed. It is then each endstop switch's job to inform the firmware "OK you can stop the motor now". When everything is working correctly it really isn't possible to move beyond the switches.
So Cura simply sends 3 characters over the USB. After that everything is handled by the printer. Also, looking at the Tronxy forum on Reddit there are numerous owners using Cura as their slicer. I don't think that would be the case if it was somehow destroying printers.
Link to post
Share on other sites
Mari 35
What colour of shirt were you wearing when you used Cura as slicer? Probably another colour then when you used Slic3r... so blame it in the colour of your shirt...😉
@GregValiant explained it very well what happens when you push the "home" button... If you don't trust the printer-profiles you get with Cura, create your own one!
Link to post
Share on other sites
SandervG 1,519
As clearly explained in the responses, it does not seem to be Cura's fault but rather the firmware. Therefor I have corrected the title claiming it was Cura's fault, which can be considered false and (probably unintentionally) misleading.
Link to post
Share on other sites
geert_2 556
I don't know that printer, but just a thought: if it is a self-built machine, couldn't it be that the end-switches (=the ones that should activate when homing the head) are mounted or wired incorrectly? So that they do not give contact? Or way too late? That would also cause it to keep going.
Link to post
Share on other sites