Skip to content
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

my library is not published... #87

Closed
runtimevic opened this issue Sep 6, 2023 · 7 comments
Closed

my library is not published... #87

runtimevic opened this issue Sep 6, 2023 · 7 comments

Comments

@runtimevic
Copy link

runtimevic commented Sep 6, 2023

Hello @seehma , @iadonkey , @zeugwerker

My library is not published...
Is there a log site or where I can see why it is not published?

INFO Publishing package
INFO Updating plcproj, setting Version=1.0.0.9, Company=TcMotion
INFO Checking all objects of PLC TcMotion_Library
ERROR TcMotion_Library does not compile!
INFO Uploading to Twinpack ...
ERROR Could not find a part of the path 'E:\BECKHOFF_TcMotion\Component_Motion_OOP_Axis\TC3_Axis.Zeugwerk\libraries\TC3.1\TcMotion_Library_1.0.0.9.library'.
INFO Log in to Twinpack Server successful

thank you, Víctor.

@iadonkey
Copy link
Contributor

iadonkey commented Sep 6, 2023

Twinpack is only uploading libraries when check all objects is going through without errors. According to the log this is not the case here.
In the output window of your Visual Studio / TcXaeShell there should be some indications why check all object fails. In order to upload the library you have to fix these errors.

However, it is actually a bug that there is no message box popping up to indicate that check all objects failed, we will fix this in the next patch.

@runtimevic
Copy link
Author

  • I had to create this route by hand:
    'E:\BECKHOFF_TcMotion\Component_Motion_OOP_Axis\TC3_Axis.Zeugwerk\libraries\TC3.1\
  • I had to install the library and leave it in the indicated path:
    'E:\BECKHOFF_TcMotion\Component_Motion_OOP_Axis\TC3_Axis.Zeugwerk\libraries\TC3.1\TcMotion_Library_1.0.0.9.library'.

Is this normal? Should these 2 steps be performed?

@iadonkey
Copy link
Contributor

iadonkey commented Sep 6, 2023

No, and this is actually only possible due to the bug I mentioned.
The log message indicates that check all object for your PLC failed and that's why Twinpack wasn't creating the folder and saving to library to this location. The normal process requires that check all objects get through without any errors and thus, the output window of visual studio doesn't show any error.

Can you check this please? If check all objects actually works for you?

image
image
image

@runtimevic
Copy link
Author

Hi, @iadonkey ,
Yes, this is the problem:

Message: Compile complete -- 135 errors, 101 warnings

Thanks you, Víctor

@iadonkey
Copy link
Contributor

iadonkey commented Sep 6, 2023

Do you want me to delete the package you uploaded from the Twinpack Server for now? In any case, if the errors are fixed you can simply upload a new version (i.e.1.0.0.10)
And sorry for the inconvenience that we require check all objects to work, but it is the only way to ensure that all objects the library provides can be used by others without issues

iadonkey added a commit that referenced this issue Sep 6, 2023
…t besides the log

this closes #87

(cherry picked from commit 9b4fe8f)
@iadonkey iadonkey closed this as completed Sep 6, 2023
@runtimevic
Copy link
Author

Do not delete it,
it is a functional library, the errors come from the template provided by PLCOpen, these errors do not affect the Beckhoff TwinCAT library.
If I have time one day I can create a new PLC and put in the template provided by PLCOpen and then the TwinCAT library will be error-free...

@iadonkey
Copy link
Contributor

iadonkey commented Sep 6, 2023

Sure, but I hope you understand that we will prevent the workaround for future releases 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants