I've almost certainly been able to post with multiple work offsets AND keeping the initial WCS offset to 0. However, as shown in the video below if I post with multiple work offsets AND keep the initial WCS offset to 0 posting fails. I am able to post fine if I change the initial work offset from 0 to 1.
Also, when the post fails fusion writes an image of my current screen to my flash drive.
Error:
It's a setting within the Post @ line 1254, so either a recent version change idk when it happened there isn't anything in the version release notes
As far as the png, could that be an M130 image thing related to your post?
Hi thanks. I also don't see anything related to not being able to use an initial work offset value of 0 in the Haas NGC release notes. I'm using the latest Haas NGC post.
I do not include part/tool images in my posts:
this is a logic implemented inside the post.
And it's coming from an old issue.
We are assigning G54 to wcs 1 ....
Most of the controller doesn't have a wcs equal to 0 except Heidenhain, and potentially older Fadal.
When setting a wcs=0 in Fusion, the post was changing this to G54.
If we are using only one wcs in the program, and no multiple work offsets there is not problem.
If we then uses multiples offsets, first part use 0, 2nd part use 1 ....
If we map 0 to G54, and 1 to G54, there is a conflict, hence the error message.
When doing correctly, the first offset must be 1, and using multiple work offset 2nd part use 2, 3rd part use 3....
This is mapped to G54 part 1, G55 part 2 .....
Regards
______________________________________________________________
If my post answers your question, please click the "Accept Solution" button. This helps everyone find answers more quickly!
As the post have a specific keyword inside, a preview picture is automatically created.
keywords = "MODEL_IMAGE PREVIEW_IMAGE";
But when the post succeed, depending on a post property, we will keep or deleted the picture.
It was pointed by @rengfx. As by default the property use M130 is false, we should have deleted the file by the function previewImage, if the test was executed:
if (!getProperty("useM130PartImages") || !permittedExtension) {
FileSystem.remove(FileSystem.getCombinedPath(FileSystem.getFolderPath(getOutputPath()), images[i])); // remove
images.splice([i], 1); // remove from array
}
But as the post have failed before reaching this code, we could not cleanup.
Regards.
______________________________________________________________
If my post answers your question, please click the "Accept Solution" button. This helps everyone find answers more quickly!
