Example calibration corexy with 3 Z motors

A Former User

This post is deleted!

oliof

@arnold_r_clark you keep repeating that. I've reviewed it before I linked it and couldn't find any obvious flaws. If you point me to where the flaws are mentioned, I'll work with them on getting it improved.

Disclosure: I am part of the RatRig beta team.

Nurgelrot

@oliof The config works but my big heartburn is in the RatRig wiring diagram. Having the simple endstops for X & Y going to IO_0 and IO_1 is just a waste of more "advanced" ports that have much better uses. Better to have them moved off to 4-6.

A Former User

This post is deleted!

oliof

@arnold_r_clark you're unusually unhelpful compared to what I am usually used to in this forum. That's disappointing.

A Former User

This post is deleted!

oliof

That's funny. Let's continue a discussion whenever you'd like to provide useful technical advice. Maybe just for @peirof s sake who asked for input which you keep withholding.

A Former User

This post is deleted!

oliof

@arnold_r_clark which errors? How to correct them?

Phaedrux

@arnold_r_clark Oliof is as helpful and sincere as anyone you're likely to meet and he appears to be in a position to correct the issues you've found.

rjenkinsgb

@arnold_r_clark said in Example calibration corexy with 3 Z motors:

Also if you are :

Disclosure: I am part of the RatRig beta team.

How can you direct people to the page but say the following :

I haven't worked on that and cannot vouch for it.

As a third party with no bias to either side, I see that as meaning olief is a product beta tester and not one of the programming team.

There is no contradiction between the two statements.

Why not just post some example problems, rather than going in circles???

[I'd never heard of "ratrig" other than here and have no interest in it].

Nuramori

@rjenkinsgb

A quick glance at the linked code, I agree - right off the bat there's a bad error in line 6.

G29 S1 ; Set Units to Millimeters

Ughhhh no, the proper code there would be:

G21

I got fascinated by this thread and just happened to take a look. I didn't get past even that, and I may keep looking later.

ok, I looked a bit more, and the BLTouch config is also wrong, and will result in slamming the bed into the nozzle. The pull-up resistor has to be enabled with the "^" in the command, like so...

M558 P9 C"io7.in" H5 F240 T10800 A5

Should read :

M558 P9 C"^io7.in" H5 F240 T10800 A5

Also, that F240 is REALLY slow. I run F2000 and it's fine.

Also, why is Homeall.g just a cut and paste of homex, homey, and homez? If you make a change in one of those, then you have to remember to also edit it in the homeall.g file. a far more elegant approach would have been to have the contents of the homeall.g file just call each of the axis, in order.

; Home all axis
M98 P"homex.g" ; Home X
M98 P"homey.g" ; Home Y
M98 P"homez.g" ; Home Z

G90 ; absolute positioning

Cleaner, and less prone to problems from redundant coding.

I happen to have very custom BLV so I have no particular connection to rat-rig, but there's commonality in the config.g set up with most all XY cubes.

martin7404

@arnold_r_clark what's wrong with you?
Nothing here should be personal.
If you can help just do
If you find error somwhere just point it

oliof

@peirof I have powered on my Pi that ran with the V-Core Pro in SBC mode and updated my configuration files on my personal github. Not much has changed. Be aware that you will need to adjust for your own machine and that you won't be able to copy it over 1:1 unless you use a toolboard with address 10, a Hemera with maxiwatt heater, and a dc42 IR probe. And even then you will likely have somewhat different offsets etc. since my V-Core Pro was not a V-Core 3 (even if some of the V-Core 3 features were beta tested on it).