@droftarts said in Parsing error when loading height map:

@sbNielsen

axis0,axis1,min0,max0,min1,max1,radius,spacing0,spacing1,num0,num1 X,Y,0.00,17000.00,0.00,9000.00,-1.00,100.00,100.00,18,10

You have changed the axis length from 1700mm to 17000mm, and 900mm to 9000mm?! Also, you only have 17 points for each line of the probe data; you need 18 to go to from 0 (the first point) to 1700 (the 18th and last point) in 100mm steps.

Ian

Damn it, I change things to quick and then I fuck it up, sorry!

It works now! The main issues was the missing 18th column in the grid..

I feel stupid and happy haha, thank you for your help and patience!

To anybody reading this in the future, here is the .csv file that ended up working:

RepRapFirmware height map file v2 axis0,axis1,min0,max0,min1,max1,radius,spacing0,spacing1,num0,num1 X,Y,0.00,1700.00,0.00,900.00,-1.00,100.00,100.00,18,10 0.600, 0.500, 0.400, 0.400, 0.400, 0.400, 0.400, 0.300, 0.300, 0.400, 0.400, 0.500, 0.500, 0.600, 0.700, 0.900, 1.100, 1.100 0.400, 0.400, 0.300, 0.300, 0.200, 0.200, 0.200, 0.200, 0.200, 0.200, 0.300, 0.350, 0.450, 0.500, 0.700, 0.800, 1.050, 1.050 0.300, 0.200, 0.200, 0.100, 0.100, 0.100, 0.050, 0.000, 0.000, 0.000, 0.100, 0.200, 0.300, 0.450, 0.600, 0.800, 1.000, 1.000 0.200, 0.100, 0.000, -0.100, -0.100, -0.100, -0.150, -0.200, -0.200, -0.200, -0.100, -0.100, 0.150, 0.280, 0.450, 0.680, 0.900, 0.900 0.100, 0.000, -0.100, -0.200, -0.200, -0.300, -0.300, -0.300, -0.220, -0.220, -0.180, -0.050, 0.020, 0.180, 0.400, 0.600, 0.900, 0.900 0.100, 0.000, -0.100, -0.200, -0.300, -0.400, -0.400, -0.400, -0.300, -0.300, -0.200, -0.150, -0.100, 0.000, 0.280, 0.500, 0.800, 0.800 0.100, 0.000, -0.150, -0.280, -0.400, -0.450, -0.400, -0.400, -0.200, -0.250, -0.200, -0.200, -0.050, 0.160, 0.400, 0.700, 0.700, 0.700 0.180, -0.050, -0.200, -0.300, -0.400, -0.400, -0.400, -0.400, -0.400, -0.350, -0.300, -0.250, -0.150, 0.050, 0.300, 0.600, 0.900, 0.900 0.100, -0.100, -0.200, -0.300, -0.400, -0.400, -0.400, -0.400, -0.380, -0.350, -0.280, -0.200, -0.200, 0.080, 0.250, 0.600, 0.900, 0.900 0.100, -0.100, -0.280, -0.380, -0.400, -0.440, -0.400, -0.400, -0.380, -0.350, -0.300, -0.280, -0.200, 0.000, 0.200, 0.550, 0.900, 0.900

@Damien said in Auto Bed Leveling Mesh made easy??:

Nothing about what to do when your height map is not centered on your bed, but offset because of the parameters you put in for the map to compensate for the offset.

I don't understand what you mean by this part. Can you give us some more information? Showing your gcode files would be helpful as well. config.g, homing files, bed.g. Maybe a screenshot of your height map as it is displayed now.

@alankilian said in LIDAR Bed Leveling:

@3Dreamer The sensor being discussed is not a LIDAR sensor, it's a LASER triangulation sensor, so it's nothing special technology-wise.

People use triangulation sensors for bed leveling all the time and it has it's good and bad points.

Hi alankilian,
you are right. I'll quote a paper in order to introduce readers to the differences:

3D ranging technologies generally fall into either position-based (triangulation) or time-based (LIDAR) approaches. Triangulation can provide much higher precision at close to mid-range but degrades quickly with the square of distance. LIDARs can provide reasonable precision over much longer distances but, unlike triangulation, they do not improve in capabilities at short range where precision and speed are critical for many applications such as autonomous rendezvous and docking, guidance and navigation, obstacle avoidance, and inspection.

So let's us speak about those technologies!

@mikeabuilder

I finally found time to do your very helpful scientific experiment.
Was to complicated for me. 😄

But for anyone else having this problem:

My z axis minimum was set to z0

Changing M208 for Z0 to Z-2 in config.g was finally solving the problem.

@atall thank you all for your great and quick help, tips and tricks.

After 10 months of guessing and time consumable troubleshooting I am finally able to use my most expensive printer!

hooray!