Open kosmikza opened 2 years ago
I am also having trouble as metioned by @kosmikza . The point that appears after the printer found the value seems to be offset from where I clicked. It does not always perform a bed level operation when I click on the black area, it just moves to the location and nothing happens. It also appears that the Measure every button does noting most of the time. One time it worked and I saw the printer complete one row of measurements and stopped. I have a Ender 3 with 4.2.7 mainboard. It does appear to show data in the textbox and such.
Hi,
Environment
bed-inspector version 2 Windows 10 ( both normal and administrator mode on the executable ) Ender 3 with BTT SKR e3 mini v2 control board Configured with UBL Marlin 2.0.9.2
Behaviour
Printer connects and accepts all manual commands. Home and center behaves correctly as does force Z to 5mm.
Problem
Side note
I did also pull the repo down, the build is complaining about preview settings being used, I've attempted to enable but still get the same warning, any steps or guidance on it? That was using VS 2019.
The issue looks like somehow the generated gcode is being corrupted or not accurate. But, sending the codes directly in the window or reading the input works fine, including the co-ords of a point and a probe. Also not sure if I missed it, is there a way to send a bed probe command that will populate the screen vs trying to map it out? I tried a g29 P1 and it creates a mesh but nothing is displayed, assuming because the program is listening for the g30 response and maybe that was the intention of the measure by x command?
Happy to send through some screens later if you like. The below is the screen as I did it yesterday, top right circle is my upper right boundry and you can see the diagonal pattern and where it ends. The starting x is weird in the below as I was trying to compensate for the edges of the bed as the probe is offset but in reality, it was no differant whether I used those boundries or set 0 to start. The homing worked fine.