-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No longer able to add as a PLC Library Repository on 4026.11 #78
Comments
According to Beckhoff USA support, this is an issue with 4026.11 and is not specific to the SPT Library. They recommend downgrading to a previous TC build. |
Any path to making the libraries compatible with the new version?
From: barry-baker ***@***.***>
Sent: Tuesday, October 15, 2024 10:49 AM
To: Beckhoff-USA-Community/SPT-Libraries ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [Beckhoff-USA-Community/SPT-Libraries] No longer able to add as a PLC Library Repository on 4026.11 (Issue #78)
According to Beckhoff USA support, this is an issue with 4026.11 and is not specific to the SPT Library. They recommend downgrading to a previous TC build.
—
Reply to this email directly, view it on GitHub<#78 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOFZHUVX4GD2PKID64U5IXLZ3UTOPAVCNFSM6AAAAABP7J23PCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJUGE2DSOBWHE>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>
|
I was told the product manager would be notified about the issue but not given any further information. |
Some have had success deleting the cache file from the library repository
directory.
…On Tue, Oct 15, 2024 at 11:36 AM barry-baker ***@***.***> wrote:
I was told the product manager would be notified about the issue but not
given any further information.
—
Reply to this email directly, view it on GitHub
<#78 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEMHY7JMMURGXVZLGNEY6DLZ3UZA3AVCNFSM6AAAAABP7J23PCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJUGM2TKNJQHA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Thanks @nshiggins that worked! |
Tc 4026.12 also has the same issue, somehow it resolved by deleting cache file |
Can you please elaborate on where this cache file lives? |
Read the manual. Everything works and adds without problems. For new repositories you can only use empty directories or a valid existing repository. |
Issue
When I upgraded from 4026.10 to 4026.11 I had to re-add the SPT Libraries as a PLC library Repository. I followed documentation verbatim (which as an aside is quite good :)) but I'm encountering the following error indicating that the path is not the root of a repository.
![image](https://private-user-images.githubusercontent.com/83728509/376651977-b3970924-47b5-4782-b10e-231ab6de9ad0.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk2OTA3MjgsIm5iZiI6MTczOTY5MDQyOCwicGF0aCI6Ii84MzcyODUwOS8zNzY2NTE5NzctYjM5NzA5MjQtNDdiNS00NzgyLWIxMGUtMjMxYWI2ZGU5YWQwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE2VDA3MjAyOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTM4MTkyZjZlMGJmZmU3MzFkZDYwMGIyMmVlZTNjYjQ3NTM4ODIxNWIxNDBkMjEwMTZhYjM5YzA5ZGY2ODU2YWYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.h5u1Epv639c6tdeupVEFP5C-B3ZVlOZP0KSXWNzFymI)
I've tried the same steps multiple times in multiple projects opening them in the XAE shell and Visual Studio 2022. One colleague experienced the same issue and after hours of re-trying the same steps, it finally worked (she could not pinpoint what she did to break it through). Another colleague had no problems with re-adding the library repository location... I had this issue when I upgraded to 4026.10 but after a few tries and some PC reboots it was resolved. Now, on 4026.11, after hours of trying basic troubleshooting steps I'm still stuck.
System Configuration
AB#5907
The text was updated successfully, but these errors were encountered: