CP 6.0 "Unknown Error"

Software
1

I apologize for a redundant post, but I’m not sure if this is a software or hardware issue, but I think it’s a software issue. Going from 5.7 to 6.0 during the set-up phase of each print I get an unknown error. The bed doesn’t seem to want to come all the way up to the tip to start its calibration. I tried to do a self test and get the same error.

2

Does it still work in the old version as V6 seems quite buggy? Or try Orca?

3

I’ve been looking for a 5.7 download, but can’t find one. Can you provide a link? Also, not familiar with Orca. What are the advantages? Thanks.

4

V6 is based on Orca and the advantage is there are fewer bugs. should get you the older version of creality print

5

Hello saline,

The reason many are using Orca is because it seems to be what Creality Print version 6 tries to be.

It generally simply WORKS.

Cheers.

6

Yup simply works, got it running my V3SE, V3KE, Ender 5 plus, Qidi Q1 Pro and Qidi Xplus3. Not tried it on my Snapmaker because I use other software for that.

7

Hello saline,

Try this link and select the V5.1.7.10514 one

This is the one that I am using with my V3SE and it appears to work well for me.
I do have Orca, but don’t find a need to use it really as this one does what I need at present.

Cheers.

8

Thanks all

9

Going back to 5.7 didn’t work. I’m going to try Orca, but could it be the K1Max’s firmware? I took the update on that recently as well, but both new firmware and CP6.0 worked for a day or 2 before this started happening.

10

Can you roll back the firmware to the previous version?

11

Not sure where to find the firmware for the printer, or how to install it. The upgrades are a simple press of the button.

I have the printer in the garage connected by wifi. If I go to the printer, the error msg on its screen gives me an option to continue, where the software on my PC doesn’t. If I hit continue, the printer prints. It’s just going to be a pain to run out to the garage for every print, but I can do that while looking for a solution.

12

You do realize that in order to run Orca you will need to install at a minimum moonraker and Fluuid. It’s actually a mostly automatic process, here’s the web page.

K1C Rooting Helper Script

13

YouTube videos just install Orca without the interfaces. Do I really need them? what are the advantages?

14

You can use Orca to generate the G-code and then copy the G-code onto a USB stick and plug it into the printer. However, my printer is in another room, and I do everything by WiFi, for that you need moonraker and Fluuid to find the printer directly with Orca. It’s a pretty painless install, you enable Root access and then just run the update scripts.

15

Hello saline,
Here is a link to the firmware files.
I would probably select the Oct 24/2024 one for now.
Copy the file xxxxxxx.img to a USB stick.
With the printer turned off, plug in the USB stick and turn the printer on. Then wait a minute.
If nothing is happening, turn off, remove USB stick and turn on again.
Check to see if firmware has changed.

Hope it goes ok for you.

Cheers.

16

Thanks all for your valuable options. I didn’t get to redoing the firmware on the printer, but at last I know how to do that, so thanks for that. I did try everything else.

I did want to report back, and don’t know if this matters. I loaded and reloaded software, but I’m back to where I started, and it seems to work now. Here is what I’ve noticed. Ever since I loaded 6.0 I get an extrusion of about 3 to 4 mm left behind after the job completes that I did not get with 5.7. I am now cleaning that off the tip before each new print. Now, I don’t know if this makes a difference, but I thought during the touch process, where it initializes against the bed, is it possible that the extra thickness of the pigtail as it bends over is telling the software that the touch point is out of range because it can’t get to a point within the expected tolerance? Just a guess.

17

I did read somewhere in Creality manual or website that it did mention that if the current version works satisfactorily, it advised not to upgrade if you don’t have to and once upgraded, you can’t go back to the previous version. What about a factory reset?

18

The “Unknown Error” in CP 6.0 (presumably referring to Checkpoint 6.0 or a related product like Check Point Security Management or Firewall software) can stem from several potential issues. Here are some common troubleshooting steps to resolve the error:

1. Check Logs for More Information

  • Review the log files in the Check Point management system for more details on the error.
  • Logs often provide specific error codes or messages that can help pinpoint the underlying issue.

2. Ensure Proper Configuration

  • Double-check the configuration settings in the Check Point product. Misconfigurations can lead to errors, including “Unknown Error.”
  • Review firewall, VPN, and security policies for any incorrect or missing rules.

3. Check for Software Updates

  • Ensure that your Check Point 6.0 version is up to date with the latest patches and updates. Sometimes, known issues or bugs causing the error may have been addressed in newer releases.

4. Restart Services

  • Restart the relevant Check Point services (such as Management Server or Firewall services) to resolve temporary issues.
  • You can restart services from the command line using commands like:
    • cpstop and cpstart for stopping and starting services.
    • fw halt and fw start to restart the firewall.

5. Check for Database Issues

  • If you’re using a Check Point Security Management Database, it might have become corrupted. Check the database integrity and perform recovery if needed.
  • Use cpdb commands to check and recover the database.

6. Review Disk Space and Resources

  • Ensure there’s enough disk space and system resources (CPU, RAM) available. Lack of resources can sometimes trigger errors in CP 6.0.

7. Reinstall or Upgrade

  • If the issue persists, consider reinstalling the software or performing an upgrade to a more recent version if you are not already on the latest release.

8. Contact Check Point Support

  • If none of the above steps resolves the issue, contact Check Point Support for more advanced troubleshooting or if the error is related to a bug or issue specific to your setup.

If you are referring to a different software or context with CP 6.0, please provide more details, and I’ll tailor the response accordingly.