Jump to content

Goodbye Cartographer [CLOSED]


mvdveer

Recommended Posts

Since upgrading to cartographer touch and the latest firmware, I just cannot complete a print. 

Followed the instructions in the documentation to the letter, but getting persistant errors on all 4 of the machines.

The first print generally progresses, but ANY subsequent print fails

Verry, very frustrating:

Voron 300:

image.png.ac7e71741248f24ca0d86d5d73cae08f.png

Trident 300

image.png.1158df18cec0340840cb1b1fb24c4ce7.png

Trident 250

image.png.7ff63a3a7679e74f993d153575643d51.png

Voron 350

 

image.png.7a6f277c5b15389d4e527bfd9806b9ad.png

 etc, etc, etc 

Looks like the time has come to switch to Beacon H probes. Up to now it was just laziness that kept me from swapping. But I thing the decision is made

  • Like 1
Link to comment
Share on other sites

There has been an announcement on Discord that explains your issue, an update to Klipper has changed I2C clocking rate which has caused issues.

 

@everyone

I apologise for the ping but I need to make a quick announcement

There seems to be an issue with the latest fw (5.1.0) and klippers new I2C protocol which bumped I2C speeds to 400kbps (up from 100kbps)

While this obviously has greater performance gains for us, it also seems to have introduced an unfortunate problem.

My suspicions have led me to believe
that it's requesting from cartographer quicker than cartographer can come out of its sleep/idle state causing klipper to think the coil is shorted or the frequency is higher than it really is.

Now this isn't a sign of a bad board or anything, it's just on the python-klipper side of things we have a check in place that causes a shutdown to protect your system if these things were to be legitimate.

I can't adjust that safety check as if you did have an actual fault, you'd more likely damage your printer.

Richard is currently in the process of moving countries and has no internet, so a few update might take a few days.

In the meantime I will continue to investigate this and keep you all up to date BUT just be aware it's not a hardware issue so nothing is wrong with your device.

Deepest apologies for any undue stress this has caused anyone.

I will be closing any tickets made that ask about this issue as this is all I have for now.

- quick solutions seem to be once restarted it should work.

 

Edited by Methos
  • Like 2
  • Thanks 1
Link to comment
Share on other sites

1 hour ago, mvdveer said:

Since upgrading to cartographer touch and the latest firmware, I just cannot complete a print. Looks like the time has come to switch to Beacon H probes. Up to now it was just laziness that kept me from swapping. But I thing the decision is made

Well, that sucks even if it is not Cartographer's fault. Do you already have the Beacons? I did Beacon on the V2  and I'm glad I waited to do my Trident. It looks like I'll be doing Beacon on it as well.

Link to comment
Share on other sites

10 minutes ago, mhzpower said:

Is this with USB or CAN?  I’ve had good luck with CANbus. Even with the updates. I am using a cm4 instead of the cb1/2. 

All on CANBus. Seems when the chamber is hot, the problem is exacerbated. The first print with a relatively cooler chamber prints first time around. Subsequent prints ALL fail with the above errors.  I am running Beacon Contact on two other machines and they have not faltered.

  • Like 1
Link to comment
Share on other sites

10 hours ago, Methos said:

There has been an announcement on Discord that explains your issue, an update to Klipper has changed how I2C has caused issues.

Thanks, will jump on Discord today and explore further, but still going to change to Beacon

Link to comment
Share on other sites

The latest announcement from Cartographer. Seems an update will be pushed soon for those affected. (Exactly the issue I have been having)

Currently in Beta Testing. Will be merged too v1.1.1 through update manager

image.thumb.png.c41e22e2dcf7d080e256ab42b05830c3.png

 

Link to comment
Share on other sites

I'm still on the old Carto (non-contact version), and as much as I want to upgrade to touch I am worried about it. Bummer that Klipper upgrades can break things so easily, even for something as innocent as a safety check that's in place. I suppose that's something that could have happened to Beacon just as easily, it's just a choice of how they implemented some safety code and whether or not Beacon has something similar in place.

Either way, it feels like we are so close to a reliable and precise Z-positioning, just note quite there...

It felt like a big upgrade just not having to worry about my z-endstop and nozzle ooze anymore.

 

Link to comment
Share on other sites

2 hours ago, KrauTech said:

Trident 250 doesn't seem to be cartographer? Looks like beacon is failing too?

Its cartographer

Trident 250:

image.thumb.png.59e4b277b155ac2c91af49fd6c1a78f0.png

Trident 300

image.thumb.png.3a2dcecfec2dcaf6cb52fa5a238fd351.png

My beacon probes are on the VZBot, Switchwire and Micron - they have NOT failed.

 

  • Like 1
Link to comment
Share on other sites

1 hour ago, KrauTech said:

@mvdveer don't suppose you wanna try 5.1.1 and see if it continues? 🤔 All testers so far it's stopped for but if yours seems consistent it'd be a good test.

Just ran an update - latest firmware was 5.1.0

image.thumb.png.204d8dd75b9d51922c2d23b943741a20.png

image.png.762bf333fb16bad97d9467b2e2264c2a.png

and cartographer v1.0.0

image.png.bf0065a1049500d4cbbca42265b149b6.png

Problem still persists.

Will check again later tonight and see if 5.1.1 is available. Not that keen switching to the Beta branch.

However Beta Branch shows same firmware:

image.thumb.png.a29200199cf14b37e9e9822cb1772b00.png

Link to comment
Share on other sites

5 hours ago, Penatr8tor said:

I totally get it why people choose the Cartographer over the more costly Beacon however...

Like @mvdveer I have had zero issues with the 4 I have installed.

Personally, I have no need to change but my heart goes out to those that are having to deal with the growing pains.

Will be converting the weekend as I just had a look on Discord and still no movement on merging the beta software to the main branch. All I can deduce from that, is that the issue may not be resolved as yet.

Link to comment
Share on other sites

It is truly Goodbye to the Cartographer probes. (No update on the release of the new firmware 5.1.1 or new software v1.1.1. as yet on the discord channel)

Will miss the CANBUS functionality but not the frustration that came with the probe. And running the USB Cables was really not that big of an issue.

HELLO BEACON

All four the machines with cartographers are now fitted with Beacon probes. I bought the 3 x H Versions in June this year, but how easy was it to install and setup. During the install process with the following commands,

cd ~
git clone https://github.com/beacon3d/beacon_klipper.git
./beacon_klipper/install.sh

it did not only install the Klipper plugin but automatically updated all the probes to the latest firmware. Talk about a hassle free installation.

Unfortunately I only had 3 x H probes, which the V2.4 300; V2.4 350 and Trident 300 got. The Trident 250 got an Revision D probe (just doesn't have the accelerometer).

All machines calibrated and BACK in bussiness!

GOODBYE CARTOGRAPHER

[CLOSED]

  • Like 2
Link to comment
Share on other sites

  • mvdveer changed the title to Goodbye Cartographer [CLOSED]
  • 2 weeks later...
On 12/21/2024 at 6:56 AM, mvdveer said:

It is truly Goodbye to the Cartographer probes. (No update on the release of the new firmware 5.1.1 or new software v1.1.1. as yet on the discord channel)

Will miss the CANBUS functionality but not the frustration that came with the probe. And running the USB Cables was really not that big of an issue.

HELLO BEACON

All four the machines with cartographers are now fitted with Beacon probes. I bought the 3 x H Versions in June this year, but how easy was it to install and setup. During the install process with the following commands,

cd ~
git clone https://github.com/beacon3d/beacon_klipper.git
./beacon_klipper/install.sh

it did not only install the Klipper plugin but automatically updated all the probes to the latest firmware. Talk about a hassle free installation.

Unfortunately I only had 3 x H probes, which the V2.4 300; V2.4 350 and Trident 300 got. The Trident 250 got an Revision D probe (just doesn't have the accelerometer).

All machines calibrated and BACK in bussiness!

GOODBYE CARTOGRAPHER

[CLOSED]

I know you've closed this but...

What did you do to de-install the Cartographer firmware?

I installed one on my v2.4 (Mellow Super 8 pro & SHT36 v3) and now both UUIDs are no longer visible to the system.

I need to de-install it and wait for the Beacon that I've ordered.

Link to comment
Share on other sites

56 minutes ago, TitusADuxass said:

What did you do to de-install the Cartographer firmware?

1. Removed all references to it from printer.cfg file and my macros.cfg file

2. Removed the section in the moonraker.conf file for the update

3. Deleted the cartographer Klipper directory from the pi.

  • Like 1
Link to comment
Share on other sites

19 minutes ago, mvdveer said:

1. Removed all references to it from printer.cfg file and my macros.cfg file

2. Removed the section in the moonraker.conf file for the update

3. Deleted the cartographer Klipper directory from the pi.

Thanks,  I thought about the first 2, but Nr. 3 was what I missed.

  • Like 1
Link to comment
Share on other sites

I totally understand the frustration Dirk. I've had trouble with each firmware update they have had. Too bad the Beacon designers can't figure out canbus because that's the only viable option I have.

Edited by jetcat
Link to comment
Share on other sites

1 hour ago, jetcat said:

I totally understand the frustration Dirk. I've had trouble with each firmware update they have had. Too bad the Beacon designers can't figure out canbus because that's the only viable option I have.

I am not Dirk, but thanks. As per the Beacon Discord, there is no indication of developing a CanBus version in the near future.  

  • Like 1
  • Sad 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...