Machine Tool Import In Pm 2023?????

[johnc4668]

Fellas,

Anyone else getting a weird result importing the machine tool in 2023? If i delete the machine tool and reimport, it works fine again. Did not have this issue in 2022. See pics. Let me know, Thank you!

Bad:

Good:

[Sean570]

I had that issue in 2022 whenever I moved a project from one computer to another and it couldn't find the MTD file. I have yet to have that happen in 2023 however.

[Jonathan.Artiss-DSI]

This issue was resolved a few times recently with 2023 by setting the option to save machine tool with project. However, this didn't work with you when we spoke earlier. 

I wonder if this is a similar issue to the machine option file not allow you to select it. 

This is what I believe is the repeatable process from our discussion:

Create a project in 2022 with machine tool imported from network location

Option to save machine tool with project > not turned on

Save project to network location

Open project on a different computer in 2023 > MTD data missing and location lost resulting in your first image.

*** Same project opened in 2022 imports the MTD.

Any ideas @Benjamin.Br ? Sorry to call you out but you were also dealing with the machine option issue with the new security feature. I believe this may be related. 

[Benjamin.Br]

As the machine tool file is on the network, it may be related to the new security feature in PowerMill 2023. You can add trusted directory paths by going to File > Options > Application Options > Security > Security. We do not encourage turning the feature off all together, although it may be worth doing that temporarily to be certain of whether this is the cause of the issue.

Also, are you willing to share the network path that you're using to access these files? It's possible it's somehow connected to the naming or format of the path.

[johnc4668]

@Benjamin.Br Does this help?

[Jonathan.Artiss-DSI]

@Benjamin.Br 

Thanks for getting involved here. I will submit a case for you guys shortly on this with all my details collected. 

I was helping John yesterday, we did try to setup their network location as a trusted path but it didn't help. Also tried to disable the restricted paths and the security all together. 

[Benjamin.Br]

@johnc4668, yes I think it does. As you're using a mapped network drive, can you confirm the same mapping and drive letter is being used on the other machines?

And did you try changing the PowerMill security feature setting?

[johnc4668]

@Benjamin.Br Yes we are using the same mapping on all our computers. 

I did try all the security settings and still got the same result. Now the computer that programs with this machine model did not have "save machine model with project" turned on. I fixed that and turned it on and I created a macro as a workaround to delete the machine model and reimport it and to re insert the machine tool into the nc program- project save. Now when i reload that project it sticks and keeps the good machine tool. Let me know if we can get a fix on this though as going back and redoing old jobs will be annoying see that bad model. thanks!

[Benjamin.Br]

@johnc4668 I'm glad to hear you've got a workaround. Jonathan's ticket will come through to development, so we'll investigate. Reproducing a problem or identifying the change that likely causes it is always key. It seems the new security feature can be ruled out.

[johnc4668]

@Benjamin.Br  Yes, i dont think it has anything to do with the security feature at all. I tried to break it muliple times with different features and paths turned on and off. It seems directly tied to the machine model as our dmu50 5ax model does not give us any issues in 2023 so far.

[Jonathan.Artiss-DSI]

@Benjamin.Br 

I have sent the case in with additional details and information. Thanks to all for looking at this issue. 

Case Number 19177198

[Benjamin.Br]

For reference, this issue is now covered by our internal issue code PMILL-18542. We have investigated and identified the problem. The problem is that the remote machine model MTD file has internal references to other files that are also on a remote path. Those internal references are now blocked by the new security feature, regardless of the settings, which is a mistake. We are working on a fix.

[johnc4668]

@Benjamin.Br Thank you for looking into this. Yes it seems as this is a pm2023 only related issue, i cannot replicate this is pm2022.