Error assigning to cpu

Ask Questions
1

When i add a library or technology solution i get the following popups.

image
image414Ă—171 3.65 KB
error
error416Ă—171 4.22 KB

It seems to only be happening to libraries that i have also used in other projects (Except the error with runtime, that shows every time).
It seems I am able to use the libraries and technology solutions but i would like to know what could cause this error message.

2

Hi Axel,

I haven’t seen this error before, but my advice would be to check your Cpu.sw file in the Configuration View. Every software object (including programs and libraries) that should be transferred must be added to this file. This is usually done automatically, and a new Configuration is started with an empty file. However, there are a couple of things to keep in mind with this file:

  1. No two objects may have the same name, and
  2. Names of objects in this file are truncated to (I think) 10 characters

I would recommend double checking that there is only one instance of the “runtime” library added to this file. Also, make sure you don’t have any tasks with the same name. You can then do the same with “FileIO”.

Did you start this new configuration from scratch or did you copy an existing one? I wonder if new versions of libraries are being added without deleting the old ones.

3

Hi Marcus

There are no duplicates of files within the Cpu.sw and all the names are indeed less then 10 characters.

This project is indeed a copy of an earlier version it could be that this is part of the issue, although i have made the older project into a .zip and moved it to another folder. This has fixed the error message showing for the library but the error with “runtime” is still showing. the same happens when an library is added when it is already present, the “runtime” error shows but not for the library.
I also found that the configuration ID in the PLC configuration in the physical view is the same as the old project.

I also haven’t noiticed any problems using the libraries so it does feel like they are still being used properly.

I guess a follow up question would be, what is the best way to copy an project in AS6?

4

Hi Axel,

Sorry for the late reply. I think the easiest way to copy a project is just to File->Save Project As and give it a new name/location. The Configuration ID shouldn’t affect this as the Cpu.sw file references files by relative file path, which should be unique to each project.

It’s interesting that the location of the project affects the messages. It’s possible to reference files that are outside of the file path, or include references to other Cpu.sw files (i.e. if files are shared between AS configurations). I wonder if there is a reference in there somewhere that is pulling in additional libraries.

5

Hi Marcus,

Interesting that you should mention that as the way to copy a project, that is the way I have copied the project in the past. During the typing of this reply I went and dug through all the project files to look for older configuration files. And after looking I have found other configurations of the projects where the current one is derived from.

These configurations do not show in Automation studio.

image
image509Ă—179 4.23 KB

Where it is also interesting that ints not only the configuration of the previous version but also that of the project before it, so this happend both times the project was copied.
I found these files in multiple locations:
project/Diagnosis,
project/Temp/transfer
project/Temp/Simulation
project/Temp/Archives

Now I have deleted these and the error messages are gone, so these were being referenced when adding a library. And this explains why it only happens with libraries that were present in these projects.
Luckily it is an easy fix for a minor problem.
I’ll mark this as solved and thanks for your replies.

1 Like