Problem with multiple instance
- Thread starter Berra
- Start date
Hej Berra.
We cannot see everything in these screenshots.
It may be that your FB and UDT, or the DB and the UDT, or the call of the FB has become unsyncronized. Try a Check Block Consistency. This works wonders to resolve all such errors, maybe it cleans up something you werent even aware of.
If that doesnt fix it, then zip and post your code of both the UDT, the FB, and the code that calls the FB. Put it in a library in stead of a full STEP7 project. In that way it becomes much smaller.
We cannot see everything in these screenshots.
It may be that your FB and UDT, or the DB and the UDT, or the call of the FB has become unsyncronized. Try a Check Block Consistency. This works wonders to resolve all such errors, maybe it cleans up something you werent even aware of.
If that doesnt fix it, then zip and post your code of both the UDT, the FB, and the code that calls the FB. Put it in a library in stead of a full STEP7 project. In that way it becomes much smaller.
TurpoUrpo
Lifetime Supporting Member
Update the Block interface, I think u have changed the udt after making the block.
PS. For the easy of taking relevant screenshots, use ALT+PrintScr to take shot of active window.
PS. For the easy of taking relevant screenshots, use ALT+PrintScr to take shot of active window.
Last edited:
TurpoUrpo
Lifetime Supporting Member
just post the project as library with unrelevant blocks removed.
Timestamp problem may occur if you change a variable type in a FB or if you add or remove something from the interface of the block.
In your case you probably changed your UDT and then after didnt update block call.
In order to overcome this. In LAD/STL/FDB program right click your block FB1 and click Update Block Call or
In LAD/STL/FDB program click File > Check and Update Accesses
There should be a third way but couldnt figure it out now.
In your case you probably changed your UDT and then after didnt update block call.
In order to overcome this. In LAD/STL/FDB program right click your block FB1 and click Update Block Call or
In LAD/STL/FDB program click File > Check and Update Accesses
There should be a third way but couldnt figure it out now.
You dont really tell us anything useful.
If the check block consistency fails, it is probably because you must decide to do something, like adapting some code to reflect other code changes. The check block consistency will tell you where something goes wrong, if not exactly what to do.
Post the full relevant code as a zipped library project. As suggested several times already.
Why ?Berra said:
If the check block consistency fails, it is probably because you must decide to do something, like adapting some code to reflect other code changes. The check block consistency will tell you where something goes wrong, if not exactly what to do.
Post the full relevant code as a zipped library project. As suggested several times already.
Similar Topics
I had to modify a multiple instance FB to add another Parameter and that meant of course that all the calls in the calling FB had to be...
Hello PLC folks,
I am using FTView Studio SE v10 in my project. I have 2 monitors and the headers are duplicated to be able to use on both...
Hi Guys,
I have got a problem regarding the setting of more than one limit for one input field. I have got four motors for extrusion & One for...
Hi Guys,
I have got a problem regarding the setting of more than one limit for one input field. I have got four motors for extrusion & One for...
Hello,
I need to reconfigure an old project that works on single monitor to work on 4 monitors.
Need to make something like picture 1.
Every...