G29 using FSR's

Having a problem? Post it here and someone will be along shortly to help
Post Reply
User avatar
DeltaCon
Printmaster!
Posts: 616
Joined: Sat Nov 14, 2015 5:01 am
Location: Wessem, The Netherlands
Contact:

G29 using FSR's

Post by DeltaCon »

I have been using OpenDact in a FSR setup to calibrate my machine, and that seems all to work now. I would not think this, but even after that challenge I have some leftover noob-questions...

What is the procedure to set the Z height automatically?

My research shows me I will probably have to give the g29 s2 command. But the problem is that it does not probe the points I specified in the repetier Z-probing chapter of my coniguration.h

Code: Select all

// #################### Z-Probing #####################

#define Z_PROBE_Z_OFFSET 0
#define Z_PROBE_Z_OFFSET_MODE 0
#define UI_BED_COATING 0
#define FEATURE_Z_PROBE 1
#define Z_PROBE_BED_DISTANCE 10
#define Z_PROBE_PIN ORIG_Z_MIN_PIN
#define Z_PROBE_PULLUP 0
#define Z_PROBE_ON_HIGH 0
#define Z_PROBE_X_OFFSET 0
#define Z_PROBE_Y_OFFSET 0
#define Z_PROBE_WAIT_BEFORE_TEST 0
#define Z_PROBE_SPEED 3
#define Z_PROBE_XY_SPEED 150
#define Z_PROBE_SWITCHING_DISTANCE 1
#define Z_PROBE_REPETITIONS 3
#define Z_PROBE_HEIGHT 0
#define Z_PROBE_START_SCRIPT ""
#define Z_PROBE_FINISHED_SCRIPT ""
#define Z_PROBE_REQUIRES_HEATING 0
#define Z_PROBE_MIN_TEMPERATURE 150
#define FEATURE_AUTOLEVEL 1
#define Z_PROBE_X1 -77.94
#define Z_PROBE_Y1 -45
#define Z_PROBE_X2 77.94
#define Z_PROBE_Y2 -45
#define Z_PROBE_X3 0
#define Z_PROBE_Y3 90

#define BED_LEVELING_METHOD 0
#define BED_CORRECTION_METHOD 0
#define BED_LEVELING_GRID_SIZE 5
#define BED_LEVELING_REPETITIONS 5
#define BED_MOTOR_1_X 0
#define BED_MOTOR_1_Y 0
#define BED_MOTOR_2_X 200
#define BED_MOTOR_2_Y 0
#define BED_MOTOR_3_X 100
#define BED_MOTOR_3_Y 200
#define BENDING_CORRECTION_A 0
#define BENDING_CORRECTION_B 0
#define BENDING_CORRECTION_C 0
#define FEATURE_AXISCOMP 0
#define AXISCOMP_TANXY 0
#define AXISCOMP_TANYZ 0
#define AXISCOMP_TANXZ 0
Seems no matter what I set there it always probes at the same coordinates and it gets off-bed at the third probe, bumping into the z-tower. Also there must be some correction to upper z=0 after the average height has been determined. It does a too good job because after calibrating with opendact the distance from nozzle to bed is too high and the layer doen't stick.

Maybe someone with a working FSR setup can publish these settings? Thanks!
I am DeltaCon, I have a delta, my name is Con, I am definitely PRO delta! ;-)
Rostock V2 / E3D Volcano / FSR kit / Duet 0.6

PS.: Sorry for the avatar, that's my other hobby!
User avatar
DeltaCon
Printmaster!
Posts: 616
Joined: Sat Nov 14, 2015 5:01 am
Location: Wessem, The Netherlands
Contact:

Re: G32 using FSR's

Post by DeltaCon »

I am trying to get the probing positions corrected, but it seems no matter what values I put in the configuration.h, it always starts probing the first at the far right end of the bed, and the next will run off the bed. That cannot be my coordinates! Are the defined somewhere else?

Code: Select all

#define Z_PROBE_X1 0
#define Z_PROBE_Y1 80
#define Z_PROBE_X2 69.28
#define Z_PROBE_Y2 -40
#define Z_PROBE_X3 -69.28
#define Z_PROBE_Y3 -40
In the host log i can read that the first probe point is located at
Z-probe:10.64 X:100.00 Y:19.99
That does not look nearly like x1 and x2 above.!

Any ideas are appreciated.
I am DeltaCon, I have a delta, my name is Con, I am definitely PRO delta! ;-)
Rostock V2 / E3D Volcano / FSR kit / Duet 0.6

PS.: Sorry for the avatar, that's my other hobby!
User avatar
DeltaCon
Printmaster!
Posts: 616
Joined: Sat Nov 14, 2015 5:01 am
Location: Wessem, The Netherlands
Contact:

Re: G29 using FSR's

Post by DeltaCon »

Hmm... Looks like I found the culprit.
I can define whatever I want in the configuration.h, but after I upload, and look in RH at the eeprom values, it still gives me something else... after I change the eeprom through RH the the leveling works fine. Isn't that strange? Why is the definition in configuration.h not leading?
I am DeltaCon, I have a delta, my name is Con, I am definitely PRO delta! ;-)
Rostock V2 / E3D Volcano / FSR kit / Duet 0.6

PS.: Sorry for the avatar, that's my other hobby!
Polygonhell
ULTIMATE 3D JEDI
Posts: 2417
Joined: Mon Mar 26, 2012 1:44 pm
Location: Redmond WA

Re: G29 using FSR's

Post by Polygonhell »

EEPROM always overrides configuration.h, if your tweaking things in configuration.h that are also in the EEPROM there is a number you can bump that will rewrite all the EEPROM values with the new configuration.h values.
User avatar
DeltaCon
Printmaster!
Posts: 616
Joined: Sat Nov 14, 2015 5:01 am
Location: Wessem, The Netherlands
Contact:

Re: G29 using FSR's

Post by DeltaCon »

A number I can bump...?
A lot of other values in the configuration.h actually do get overwritten (I think).
I'll look into that, but what do you mean by a number I can bump?
I am DeltaCon, I have a delta, my name is Con, I am definitely PRO delta! ;-)
Rostock V2 / E3D Volcano / FSR kit / Duet 0.6

PS.: Sorry for the avatar, that's my other hobby!
User avatar
Nylocke
ULTIMATE 3D JEDI
Posts: 1418
Joined: Sun Jun 23, 2013 1:43 pm
Location: Iowa

Re: G29 using FSR's

Post by Nylocke »

EEPROM_Set or something like that. If it differs from the number in EEPROM the EEPROM will be overridden by the config.h file. Its on the first page of the config tool.
Post Reply

Return to “Troubleshooting”