First time posting, and very new to Automation Studio. I am comparing my program given from the vendor (zipped, opened in same file structure location as vendor) and when I compare to the controller before building, everything is the same. I go to build, and it starts compiling and linking routines.
Am I doing something wrong here when I copy the zipped folder? I’m not getting a warning for the project being moved. The vendor and I tried for a couple days to figure out what is going on.
The project after being built changes the dates on the routines and the size is off by a small amount.
Hello Ryan Valentine.
Welcome to join our community.
Even when using the same project file, the metadata may change when the file is saved or rebuild, which can result in it being identified as a different project.
Best regards
I understand from your description that the project builds on your PC but not on the vendor’s. What errors and warnings are in the vendor’s output window while building? If you want us to help you, you must be more specific.
is it possible, that the source file timestamps are influenced by zip/unzip?
From Automation Help:
A mechanism is implemented to check whether a B&R module should be regenerated. It compares the timestamp of the previously created B&R module with the timestamp of the files that have an effect on the B&R module to be generated. If one of these dependent files is newer than the B&R module to be created, then the respective compiler is started.
So the vendor connects to PLC, builds, and the build goes very quickly because nothing has changed. Then he zips and shares the project with me, I extract and open, connect, and then when I build it starts compiling and linking routines. Then on the compare to controllers, everything is slightly different, and I don’t want to transfer now when everything is different from the vendors.
How do I get around that? When he exports the project, does he need to delete his temp and binary files? I just don’t want to transfer a different project into the PLC.
No errors or warnings on either end. When the vendor builds, he get’s a build successful. Same project from him zipped, opened in the same file directory, and same runtime, it starts to compile each routine.
No, binaries and temp have to be included when trying to avoid rebuild… I see the “some byte differences” after compile, but right now I’ve no idea where this comes from… maybe the vendor has some Automation Studio specific settings that are not stored in the project but only in the computers installation?
Does the customer use AS function “Save project as ZIP”, or does he zips from Windows Explorer? If you haven’t tried yet both variants, I would.recommend doing so and check if it makes a difference (but honestly spoken, I don’t think so)?
Last but not least, would it be possible to share a binary out of the project im both variants so that we could have a look into the difference? As it’s a binary, sure we can’t see too much, but how knows, maybe it leads us into the direction where to search next? If the “arconfig.br” or the “iomap.br” are different too, those modules would be interesting for such an imvestigation…
I really hope someone else had a great idea about.
How would I grab the 2 variants? Is it just the binary and temp folders?
I’m also going to look into uploading (if possible) the binaries from the controller, or if the line gets some downtime, grabbing the project from the CF card in the PLC.
If you have still the zip from your software provider, then it’s the from binaries folder there, and the same one from the project you compiled - I assume that already those both folders should have the difference.
As I said, I’ve no idea if we can conclude something out of this data, but it’s worth a try … I’m personally starting into holiday right now, so I hope that someone else can have a look into additionally.
