Open electronicm opened 2 years ago
Your firmware does a 7x9 grid? I think this may be part of the problem. I remember at one point there was an issue with unequal grid dimensions causing issues.
I configured the 7x9 grid to get as close as possible to the bed level screws. I test it again with 9x9 / 7x7 and give feedback.
Can I do anything else to help?
So, I have now made a test with a 7x7 grid. The result is the same.
I need you to enable serial logging in octoprint's settings, restart octoprint, and update mesh once, then disable serial logging after. Then provide the serial.log.
I probably won't make it until next weekend, but you'll get the log.
here it is: serial.log
btw: here is also the debug log plugin_bedlevelvisualizer_debug.log
Do you have remove row labels
enabled on the collection tab in the plugin's settings?
Yes
My configuration:
bedlevelvisualizer:
_config_version: 1
camera_position: 0,-2,0.3
colorscale: '[[0, "rebeccapurple"],[0.4, "rebeccapurple"],[0.45, "#006aff"],[0.5,
"green"],[0.55, "yellow"],[0.6, "red"],[1, "red"]]'
command: "@BEDLEVELVISUALIZER\t; tell the plugin to watch for reported mesh\n\
M420 V\t\t\t\t\t; Mesh ausgeben"
commands:
- command: "@BEDLEVELVISUALIZER\t; tell the plugin to watch for reported mesh\n\
G28 O\nG29 J2\t\t\t\t\t; Checking the mesh using n² points\n@BEDLEVELVISUALIZER\t\
; tell the plugin to watch for reported mesh\nM420 V\t\t\t\t\t; Mesh ausgeben"
confirmation: false
enabled_while_graphing: true
enabled_while_printing: false
icon: fas fa-vector-square
input: []
label: ''
message: ''
tooltip: 4 Point tilt probing
- command: "@BEDLEVELVISUALIZER\t; tell the plugin to watch for reported mesh\n\
G28 O\nG29 P1\nG29 P3\nG29 P3\n@BEDLEVELVISUALIZER\t; tell the plugin to watch\
\ for reported mesh\nG29 S%(SLOT)s T0 V4 \t\t; Mesh speichern und ausgeben\n\
M500"
confirmation: true
enabled_while_graphing: true
enabled_while_printing: false
icon: fas fa-file
input:
- label: hideme
parameter: SLOT
value: '0'
label: ''
message: Dadurch wird das Mesh neu erfasst und der gewählten Slot überschrieben.
tooltip: Das Mesh wird komplett neu erstellt und in den gewählten Slot gespeichert
- command: "@BEDLEVELVISUALIZER\t; tell the plugin to watch for reported mesh\n\
G29 L%(SLOT)s\n@BEDLEVELVISUALIZER\t; tell the plugin to watch for reported\
\ mesh\nM420 V\t\t\t\t\t; Mesh ausgeben"
confirmation: false
enabled_while_graphing: true
enabled_while_printing: false
icon: fas fa-file-import
input:
- label: hideme
parameter: SLOT
value: '0'
label: ''
message: ''
tooltip: Das Mesh aus Slot wird geladen
- command: 'G29 S%(SLOT)s\nM500'
confirmation: true
enabled_while_graphing: true
enabled_while_printing: false
icon: fas fa-file-export
input:
- label: hideme
parameter: SLOT
value: '0'
label: ''
message: Der gewählte Slot wird überschrieben.
tooltip: Speichert das aktuelle Mesh im ausgewählten Slot.
descending_y: true
ignore_correction_matrix: true
mesh_timestamp: 25.9.2021, 18:39:23
rotation: '0'
screw_hub: 0.7
showdegree: true
stored_mesh:
[REMOVED]
stored_mesh_x:
[REMOVED]
stored_mesh_y:
[REMOVED]
stored_mesh_z_height: 250
stripFirst: true
What happens if you disable that option and update mesh again?
Yes, you are obviously on the right track. If I disable the option and update the mesh, I get all the values for the X axis. When I enable it, the first column is missing again. This can be reproduced over and over again.
Tested it for 7x7 and 9x7 grids with the same result.
You don't need to fix the bug immediately because of me. I now know and have figured out a workaround.
In case you want to document it for others: For now, I've hidden the line via CSS.
div#tab_plugin_bedlevelvisualizer div.meshtable tfoot tr:nth-of-type(0n+2) {
display:none;
visibility: hidden;
}
0n+2
hides only the second element, preventing future possible tr
in tfoot
from being accidentally hidden.
Yes, you are obviously on the right track. If I disable the option and update the mesh, I get all the values for the X axis. When I enable it, the first column is missing again. This can be reproduced over and over again.
That is the point, if you have that option enabled it's suppose to remove the first column, otherwise leave it unchecked, so I'm not exactly sure what you are trying to accomplish with the css to hide things?
Please excuse my absence. Based on the options label "Remove Row Labels" I was hoping to remove the row "x - Positiony y - Position". The option label here is confusing and should be "Remove first y-Row".
It's more obvious what that means when you have a report that includes them because they are an incremental series of numbers, similar to row labels in excel.
Describe the bug I have entered 7 mesh points for the X-axis and these are also output on the
G29 T
orM420 V
. However, only columns 1-6 are displayed by the plugin under "Data" and "Corrections".Expected behavior I would also like to see column 0 of the X axis. :D
Debug Log plugin_bedlevelvisualizer_debug.log
octoprint.log
Screenshots
Firmware and Version Marlin bugfix-2.0.x (Sep 18 2021 19:29:44) It can also be reproduced with the current stable.