AutolevellerAE-0.8.0 Bugs on mesh edition

[lordrafa]

Hello I have downloaded the new AutolevellerAE (v0.8.0) and I have found that when I modify the mesh parameters to be smaller than the working area the preview is not updated to reflect that the probing area is smaller than the job area.

Also if a load a new file, the previous mess configuration is reset, even if I click on "no" when I am asked.

Also a feature that I miss is the summary in the bottom with the probe area details. In this version I can see only the job area info but no the probe area.

Edit: wops looks like the generated code is incorrect too. My country configuration is Spain. Maybe some of the changes done to fix the comma issue has broken the input?

[daedelus]

Thanks for this, I suspected there could be some issues like this.

Will address these problems next week and provide an update ASAP.

[daedelus]

If possible, could you send the input gcode to my email: daedelus@autoleveller.co.uk Thanks.

Will be easier to find and fix the generated code errors then.

[daedelus]

OK so I have been testing this but have been unable to replicate these issues so far.

I have changed my Windows 10 region to Spain, ran a lot of my automated tests with many input files but everything ran as expected.

I shall address each point below:

when I modify the mesh parameters to be smaller than the working area the preview is not updated to reflect that the probing area is smaller than the job area.

Works OK for me. If you change one of the Mesh values, you need to press Tab or Enter to update the mesh and the preview area changes to reflect the changes.

Also if a load a new file, the previous mess configuration is reset, even if I click on "no" when I am asked.

For me, clicking "no" here left the probe settings how they were previously. So I couldn't replicate this one either.

Also a feature that I miss is the summary in the bottom with the probe area details. In this version I can see only the job area info but no the probe area.

I agree and have already added this back to the new version being worked on. So you will see its return in the next release, its at the bottom of the mesh tab now, this seemed a better place to put it since the info is related to the probe mesh.

wops looks like the generated code is incorrect too. My country configuration is Spain. Maybe some of the changes done to fix the comma issue has broken the input?

Couldn't find a problem here but that doesn't mean there isn't one.

Please let me know if anyone finds the same or new issues with AE 0.8.0 so I can test and fix. Thanks.

[lordrafa]

Hello thank you for your reply and the fixes. Sorry I didn't come back till now I become really busy the week after I wrote my last post and after I forgot this post completely. The new version 0.8.2 has solved mostly of the issues that I had also the new look is better. I like that you have combined the conf screen with the load screen.

Just one comment more something look a little bit weird when you modify the starting point. If you see in the images that I have attached when I load a gcode file the blue area matches the probe area, as it's expected. However if I modify the starting x I would expected to see the the red polygon move but rather than that it gets expanded.

I am working with ArchLinux and using the oracle's java8.

PS: This time I have attached the GCode that I was using too.

[lordrafa]

Checking again I think that what is happening is that the viewer is fixed on the red polygon and since it is moving part of the blue polygon gets hide. I would try to fix the viewer to the blue polygon so when the probe area is modified you can see how is going to be in reference to the PCB.

Keep the PCB fixed on the middle of viewer would make sense since the PCB is not going to change the size but can create some issues if the red polygon increases it's size till the point that doesn't fit in the screen scale out both polygons would be needed so the can fit again.

Anyway this would be more suggestions that bugs.

[daedelus]

Thanks Rafa,

You are completely correct about the red polygon (mesh / probe area) In fact, if the blue area (OGF) and red polygon are both visible, the X and Y positions of the red box are always fixed in the bottom left corner of the display, so when you change the X or Y values, it appears the box is fixed and the blue box appears to shift left or right, up or down.

This is confusing I know and hopefully I shall provide something better soon.

Thanks for the feedback and dont hesitate to let me know if you find any other issues.