Bed Visualizer Error

[cobaltburrito]

I am receiving the following when trying to pull the mesh from my printer(using UBL)-

Error:
TypeError: Cannot set property '0' of null

Received Data:
[object Object]

My GCODE commands:

M155 S30
G29 L0
@BEDLEVELVISUALIZER
G29 T
M155 S3

I enabled debug logging and the following is from the debug log:

[2021-03-25 14:20:36,845] DEBUG: mesh collection started
[2021-03-25 14:20:36,857] DEBUG: []
[2021-03-25 14:20:36,883] DEBUG: ['-0.034', '-0.063', '-0.077', '-0.093', '-0.098', '-0.107', '-0.069', '-0.065', '-0.025', '+0.015']
[2021-03-25 14:20:36,886] DEBUG: []
[2021-03-25 14:20:36,891] DEBUG: ['-0.017', '-0.042', '-0.055', '-0.065', '-0.070', '-0.067', '-0.037', '-0.024', '+0.003', '+0.029']
[2021-03-25 14:20:36,896] DEBUG: []
[2021-03-25 14:20:36,900] DEBUG: ['+0.087', '+0.054', '+0.022', '+0.004', '-0.011', '-0.019', '+0.006', '+0.014', '+0.018', '+0.023']
[2021-03-25 14:20:36,903] DEBUG: []
[2021-03-25 14:20:36,908] DEBUG: ['-0.003', '-0.025', '-0.045', '-0.049', '-0.050', '-0.043', '-0.004', '+0.008', '+0.028', '+0.047']
[2021-03-25 14:20:36,911] DEBUG: []
[2021-03-25 14:20:36,915] DEBUG: ['-0.014', '-0.024', '-0.037', '-0.042', '-0.035', '-0.029', '+0.012', '+0.036', '+0.053', '+0.071']
[2021-03-25 14:20:36,919] DEBUG: []
[2021-03-25 14:20:36,924] DEBUG: ['+0.028', '+0.015', '+0.005', '-0.006', '-0.001', '-0.003', '+0.025', '+0.050', '+0.054', '+0.058']
[2021-03-25 14:20:36,928] DEBUG: []
[2021-03-25 14:20:36,932] DEBUG: ['+0.006', '+0.011', '-0.002', '-0.009', '+0.004', '+0.011', '+0.054', '+0.078', '+0.098', '+0.118']
[2021-03-25 14:20:36,936] DEBUG: []
[2021-03-25 14:20:36,941] DEBUG: ['+0.066', '+0.050', '+0.036', '+0.019', '+0.023', '+0.030', '+0.067', '+0.079', '+0.093', '+0.108']
[2021-03-25 14:20:36,945] DEBUG: []
[2021-03-25 14:20:36,951] DEBUG: ['+0.088', '+0.056', '+0.030', '+0.004', '+0.010', '+0.002', '+0.030', '+0.039', '+0.041', '+0.044']
[2021-03-25 14:20:36,955] DEBUG: []
[2021-03-25 14:20:36,959] DEBUG: ['+0.023', '+0.001', '-0.004', '-0.025', '-0.016', '-0.004', '+0.023', '+0.040', '+0.075', '+0.110']
[2021-03-25 14:20:36,984] DEBUG: {'type': 'rectangular', 'x_min': 10.0, 'x_max': 220.0, 'y_min': 10.0, 'y_max': 220.0, 'z_min': 0, 'z_max': 250.0}
[2021-03-25 14:20:36,985] DEBUG: stopping mesh collection
[2021-03-25 14:20:36,986] DEBUG: flipping y axis
[2021-03-25 14:20:36,988] DEBUG: [['+0.023', '+0.001', '-0.004', '-0.025', '-0.016', '-0.004', '+0.023', '+0.040', '+0.075', '+0.110'], ['+0.088', '+0.056', '+0.030', '+0.004', '+0.010', '+0.002', '+0.030', '+0.039', '+0.041', '+0.044'], ['+0.066', '+0.
050', '+0.036', '+0.019', '+0.023', '+0.030', '+0.067', '+0.079', '+0.093', '+0.108'], ['+0.006', '+0.011', '-0.002', '-0.009', '+0.004', '+0.011', '+0.054', '+0.078', '+0.098', '+0.118'], ['+0.028', '+0.015', '+0.005', '-0.006', '-0.001', '-0.003', '+0
.025', '+0.050', '+0.054', '+0.058'], ['-0.014', '-0.024', '-0.037', '-0.042', '-0.035', '-0.029', '+0.012', '+0.036', '+0.053', '+0.071'], ['-0.003', '-0.025', '-0.045', '-0.049', '-0.050', '-0.043', '-0.004', '+0.008', '+0.028', '+0.047'], ['+0.087',
'+0.054', '+0.022', '+0.004', '-0.011', '-0.019', '+0.006', '+0.014', '+0.018', '+0.023'], ['-0.017', '-0.042', '-0.055', '-0.065', '-0.070', '-0.067', '-0.037', '-0.024', '+0.003', '+0.029'], ['-0.034', '-0.063', '-0.077', '-0.093', '-0.098', '-0.107',
 '-0.069', '-0.065', '-0.025', '+0.015']]

[jneilliii]

Please share a screenshot of your settings.

[cobaltburrito]

[jneilliii]

Ok, so for UBL, you'll want to use a slightly different approach. There are a couple of options. You can manually probe your bed with the G29 P1 and G29 P3 (possibly need to run this a couple of times) and then save the mesh and then replace the command G29 T with M420 V in your update mesh code. This will then just visualize what's stored in EEPROM. The other option is to put the whole process in the update mesh code section as documented here.

[cobaltburrito]

I'm not looking to use your plugin to run the bed leveling sequence. I'm just trying to pull already generated mesh and visualize it. That's why I'm just running the G29 T.

[jneilliii]

The fact that it's showing mesh data makes me think the plugin is choking on the rendering side, which is in handled in the browser. Are there any other errors in the developer console (F12) of your browser?