Z offset numbers for each 9 points

Well, yes there is ...

Try issuing the following from a GCode terminal on the printer:

G29 V4;

You should get an output similar to this:

G29 Auto Bed Leveling
Bed X: 5.000 Y: 0.000 Z: 1.343
Bed X: 100.000 Y: 0.000 Z: 1.421
Bed X: 195.000 Y: 0.000 Z: 0.814
Bed X: 195.000 Y: 87.000 Z: 0.987
Bed X: 100.000 Y: 87.000 Z: 1.356
Bed X: 5.000 Y: 87.000 Z: 0.997
Bed X: 5.000 Y: 174.000 Z: 0.934
Bed X: 100.000 Y: 174.000 Z: 1.486
Bed X: 195.000 Y: 174.000 Z: 1.260
Eqn coefficients: a: -0.00037443 b: 0.00019721 d: 1.19787788
Mean of sampled points: 1.17759323
planeNormal x: 0.000374 y: -0.000197 z: 1.000000

Bed Height Topography:
+-----------+
|...Back.... |
|Left..Right|
|...Front... |
+-----------+
-0.24355 +0.30884 +0.08286
-0.18078 +0.17827 -0.19083
+0.16572 +0.24355 -0.36407

Corrected Bed Height vs. Bed Topology:
+0.01507 +0.60302 +0.41262
+0.09499 +0.48962 +0.15609
+0.45865 +0.57206 +0.00000

Bed Level Correction Matrix:
+1.000000 +0.000000 -0.000374
+0.000000 +1.000000 +0.000197
+0.000374 -0.000197 +1.000000

I have not had a chance to try this on the C2, but it is on Marlin 1.10 RC6 or RC8 and this went in with RC3 (if memory serves)

 

There should be a way to simply switch to MESH bed leveling (which happens once with some manual intervention) and then never do it again (no sampling). It would get stored in EEPROM and you are done. There would be two things involved:
1) doing the sampling the one time and store to firmware
2) switching your software to not engage the ABL routines (i.e. use MESH instead).

The second one would take a bit of fiddling with OctoPrint (or whatever you are printing with -- I assumed Octo) and I will do my darndest to get this tested this weekend at the latest. The actual changes/configuring would not be massive, but I need to free up the time to try it.

 

Actually the first one requires using OctoPrint since you need to use the GCode terminal to interact with it.
Let me see if I can't get the details. @WheresWaldo has the awesome thread on the new marlin* if you want to experiment:

http://community.robo3d.com/index.p...grade-1-1-0-rc8-rcbugfix-for-r1-r1-plus.5806/


*this is effectively what is already on the C2 with minor version differences, it was *new* for the R1 series.

 

Actually the start up gcode is virtually unchanged from the auto-level. I don't even think Robo adds M851 to the startup code, I think the Z offset wizard just stores the value in EEPROM when you run the wizard. So the startup gcode has a G29 auto-level command in it and if MESH is enabled all that does is display the current MESH values in the terminal screen. So you can leave it right where it is in the print startup code.

I tried once to provide a generic Marlin 1.1.0 for the C2 but since I have no way of testing it and I am not buying a C2 anytime soon I abandoned the effort. Robo has taken a lot of liberties with Marlin 1.1.0 removing code, adding new code, reinserting removed code, the same way a College dorm dweller tests to see if spaghetti is ready. I would currently take their source, if you can actually find the most current, and edit Configuration.h and comment out the #define AUTO_BED_LEVELING_LINEAR and uncomment #define MESH_BED_LEVELING and #define MANUAL_BED_LEVELING a few lines after that.