Yesterday night I installed Creality Print V6 and the printer is nor reacting to LAN printing comands. It can’t even perform a self-check or callibration. Instead of showing files in USB or LOCAL it show a set of files with the name TEXT. When I try to print one of then the printer shows a message saying “invalid file index”.
I have this same problem, just started now after a few hours from switching to CP6, the printer will not home, and also the motor unlock button doesnt work.
as well, when you go to ‘network’ it just spins and then stays blank.
there is a yellow symbol next to the now dark wifi symbol also.
Hello, after I sent a g code to my ender 3 v3 printer with creality print 6.0, I turned off my printer and when I turned it on, it got stuck on the login creality screen. I can’t get a solution even if I try to reset the firmware.
If you know the printers IP address, enter it in a web browser and add :4408 to the end to get to the Fluidd interface, scroll down to Jobs on the left side and delete the newest file
I also had problems with this new version. Started a print and it homed for quite a while then slowly raised print head to top of gantry. Problem then it tried to keep going up causing a very anxious few moments until I turned the power off. Immediately went back to previous version no problems. Think I will leave 6 alone until I hear positive reports about it. Another rushed release perhaps?
I only had the printer issue with Creality Print 6.0.0.1078 after that everything is working fine. Mine did the initial homing, then the nozzle clear and locked up when doing the z axis home after that. I am not sure if it is a Creality Print issue as there is nothing odd in the gcode file. It could be something from the latest firmware update for the Ender 3 V3 but even that worked fine with Creality Print 5.1.7
If the printer hasn’t started printing the piece it is still doing automated stuff from START_PRINT macro, even the 2 lines done on the left is part of that macro
Creality Print 6.0.0.1078 has caused no issues with my K1 and the START_PRINT macros are very similar