disco_stu

Haha! Yeah, the fans are driving me nuts already. Tried to open one up to lube it and can't see much of a way in. Had fans on chargers etc that were dry from the factory and were nice after some lube. From China...of course! Hopefully got some that will suit in my piles of spares from various things in the garage. I did buy this with the intention of eventually changing and upgrading bits and pieces to be able to print better engineering type plastics at some stage. So hot end was on the list, and the extruder eventually seems to be a given. Given the shortcomings, Chinese stuff at least gives a way in for a lot of these more specialised pursuits, knowing you'll have to modify. If 3d printer was $1300 I wouldn't be able to give it a go. Me being me I'm more than happy to rip new stuff apart and modify and improve things-can't seem to help myself! While frustrating at times, the learning curve with new things is something I like. I did actually start with learning CAD basics before buying the printer, figuring for what I will do those skills are needed (I won't be making star wars figurines). Since getting the printer and spending all my time on that, I've forgotten all the tricks I learned! Got something I need soon so I'll have to relearn to get that drawn up. Appreciate those hints of things to look at changing/fixing. Will start slowly upgrading bits as needed. Funnily enough, googled around last night out of interest and someone on Reddit had the same issue with the same firmware version (or as much as they would let me read before their weird ways of trying to make people join kicked in), in case this helps anyone else out. Thanks again for all your help

I contacted the guy I bought the printer off, and he sent me some earlier firmware to try. So far it has printed one object fine that previously was only printing in one line on the right hand side of the bed. (although as I typed this I fired it up again and Z was 10mm high trying to print, but homing and trying again worked fine) So it looks like it was a firmware issue as you suspected Greg. I really should have tried this earlier and actually feel a bit stupid for not trying. I think it was the fact it was only doing it on the downloaded models that had me thinking it was something weirder going on. Maybe it was just pure coincidence that mine were fine and all the downloaded models from thingiverse were bad. Maybe the CPU has something to do with it. I'll have to print some more things to really be comfortable that the issue is solved, but for the moment things are looking good. I really appreciate the time you've taken to help me out. Bit hard being new to this and not having much idea. Hopefully I can offer the same assistance to others some day

I did have issues with original firmware-extruder was out and it wouldn't save my calibration. Had to look back through to remember why I updated. I can always load the current firmware back onto it easy enough if the new one doesn't work. I'll check the Creality site and see if they happen to have one to suit the 256k board. Fingers crossed one of these works

So, googling around about 4.2.2 board issues, I came across some info that they are sending some of the 4.2.2 boards with RCT6 256k CPUs rather than the original RET6 512k CPUs. Opened up the bottom and wouldn't you know-I've got the RCT6 256k. My assumption is that the firmware I updated to was intended for the 512k CPU. Do you think this could be causing the strange behaviour? I noticed that TH3D have firmware for the 256k. You think I would be best trying that out?

Thanks. That gcode worked perfectly, no issues at all. The thing with the movement and slamming to the end issues I'm having is that it isn't only one axis that will go wrong. For that one it was the x axis, but I've had a few where it was the Y axis. One print it was the Z axis. The extruder doesn't seem to cause an issue, that one always appears to work correct to my untrained eye. But there was also the cube where the speed wouldn't change despite what I set in the slicer. The slamming always occurs to the opposite side of the end switch, haven't seen it yet go towards the end switch always away from it. That would all mean if it is in the board then it isn't the driver for one axis, but something common to all movement. Can they see if I've used other firmware on it, or only what's loaded onto it currently? Just wondering if I should try a 3rd party firmware and see if the same issues are there, and if so contact Creality/the seller. I'm wondering if I should send a copy of the gcode that is going wrong to someone else with the same printer and see if it goes bad for them also. Figuring if it goes wrong that would indicate something in the gcode/slicer/stl/computer side, and if its fine then its my printer. Appreciate all your help. Pretty hard to nut this stuff out on my so it is greatly appreciated

Thanks Greg. Is there any way to test the board? Would I be best off trying Jyers or some other firmware before going down the path of main board warranty or similar?

Thank you. I just tried the 3mf, and once it got to temp the head went flying over to the right and the stepper motors started screaming. Just turned off the power switch. I clicked to create new profile etc etc. It didn't create the new printer, but it did the material profile and settings, and I chose the Trailers PLA that it installed. Not sure if I did anything wrong though, but I wouldn't think the profile would cause that The stl is currently printing fine. I'll stop it soon, but speed and everything else looks to be about right. I did use the standard quality profile I've been using for other prints with this one

Just tried a file from cults which seemed fine, in the right place at least

Thanks Greg. I ran that code and reset (I reset through the printer screen the other day) and problem file still does the wrong thing. So that to me takes the printer itself out of the potential causes. Looking at the problem file, like you it looks fine in Cura. Next thing for me to try is something from another download source than Thingiverse, but the fact things are fine for you and the one you sliced is fine for me makes me think the issue is still here, and likely my computer......but why, WHYYYY?

The GV_filament guide pulley gcode printed normally. Stopped it after it started fine as bed was out of level, but it didn't give the issues I had edit. Just tried reslicing the filament guide wheel myself and trying again after the keychain seemed to print normally. This one did the same as before-went all the way over to the right hand side edge of the bed and printed everything in one line along there. Given that the GV_filament guide gcode was fine and mine wasn't leads me again to believe its something here or that I'm doing. But you resliced that with what I uploaded here and its fine, and files I create myself are fine, its only the downloaded files. So is something going wrong with the downloads? But then they appear fine on the screen. I'm pretty basic when it comes to the software side of things, so I can't think what it could be.

I completely missed that initial line layer width. I think I loaded someone else's profile onto Cura which might have had it in it. I didn't set it myself, and it would explain the expansion at the bottom that I'm seeing. Thanks for pointing that out. The I updated the printers firmware when I got it after I had some issue, but can't remember what the issue was. But I thought if it was the printer then it would do it with both the files I made myself and with ones downloaded, just not sure what the difference would be between them. I've attached the gcode for the filament pulley. Funny thing, just sliced the keychain one after changing to 100% lower layer (only thing I changed) and its printing normally. So I haven't attached that one. I'll give the one you posted a try and see how it goes. Thanks for the help so far problem_FilamentGuide_Pulley_Half.gcode

Awesome, thanks Greg. The filament guide pulley is one that caused issues yesterday. I just resliced and checked it and its doing the exact same thing-head moves right along the very front of the bed, hits the glass bed clip (that is outside print area) and then prints everything in one line along the very right hand side of the bed, like it thinks the print location is somewhere further to the right of the printer bed. Home is front left corner. Home is set correctly in the slicer, and other files that work properly print exactly where I set them to go in the slicer As I mentioned, each different downloaded file has a different issue, but they are all doing something wrong I've thrown in the keychain one just so there is something different to compare to. Downloaded this just as another test yesterday. This one raised the Z axis right to the top before I cancelled the print. I haven't checked if this one is printing different when resliced, but all the others did the same thing wrong each time it was resliced so I'll put money on it being the same as it was yesterday Appreciate the response, thanks problem_FilamentGuide_Pulley_Half.3mf problem_keychain.3mf

I'm not sure if this is a bug with Cura or what. I don't even know what terms to search for, and not finding anything similar through google searches. So, I'm new to 3d printing and recently purchased an Ender 3 v2. Using Cura as slicer, I was having issues with calibration cube I downloaded having really bad corners. Tried slowing down and issue was the same. Turns out it wasn't actually slowing down to what I set in the software, but if I made a cube myself and sliced it in Cura it was nice and slow and corners were perfect. I've since figured out that any .stl files that I download are acting weird and something is wrong, but if I've made the 3d item myself it is printing perfectly fine. To outline things. Downloaded XYZ calibration cube and repeatedly tried to print with issues. I tried changing all settings and nothing fixed the issue. On recommendations I tried an alternative slicer. Prusaslicer printed something I made myself fine, but when printing the cube I downloaded it slammed the bed right forward and had the stepper motors screaming in pain. Tried a few different things there and all were wrong to very bad. Tried superslicer with a very similar issue occuring. I then tried creality slicer, being Cura with a different name on it. That printed the calibration cube with the same very high speed, and it wouldn't improve the corner issue I was having. On trying a 20mm cube I made myself it printed fine, and was much slower. In my inexperience, I thought the speed it was going with the calibration cube was how fast I set in Cura, and it was only when measuring and timing that I found out that was much faster. I then tried another thing I downloaded from Thingiverse and this one tried to print on the very right hand side of the bed instead of near the middle where I set it. It then ended up a line along the very edge of the plate. I made my own thing again, exported as an .stl and tried it, and it was fine. Reslicing the things that are causing issues just end up having the same thing wrong in the new gcode, despite any settings that I change in Cura or Creality slicer. Whatever goes wrong is unique to that specific .stl and stays with it. I just downloaded something again from Thingiverse and this one tried to print with the z axis at the very top. So its definitely a pattern occurring with only downloaded files being crazy. I haven't found any other formats to download and try to see if its only with .stl files I believe this was likely the same issue that was happening with Prusaslicer and superslicer. Not that I particularly want to go back to them or anything, but just to highlight that it isn't Cura only having this issue. Given the files I downloaded have been done hundreds to thousands of times and there is no comments discussing issues, it seems fair to discount them as the issue, especially when anything I've downloaded has done something wrong. I've had the same issue on Cura, Creality, Prusaslicer and Superslicer, so it seems safe to discount the slicer as the cause. The printer is printing other things fine and seems to obey the insturctions given to it, so it seems that isn't to blame. That really only leaves my computer as the cause if my reasoning is right. Hopefully that all makes sense. Can anyone help me figure out what is going on and why? Can anyone give me some search terms to even look further for this? Would anyone know what to look for in the gcode to see what is causing this behaviour? Is there anything I should upload to help? Would really appreciate any help or advice anyone can give Thanks, Stuart