Why is my instance DB not accepted

Please also see the attached screenshots.

I am adding 4 new emergency shutdown buttons to a machine.

I have copied the FB and (instance)DB for one of the existing emergency shutdown buttons and that seems OK but when I will add the new buttons in the FC calling the blocks I can add the new FB but the corresponding new DB is not accepted.

What am I doing wrong and how can I make it work?

Thank you for answering hdhosseini,

Normally the FB number and symbol name is the same if you have a similar instruction and DB number should differ.

I am not sure what you mean - but I can see that the existing emergency stops have the same number for the FB and the IDB (Like FB5307/DB5307 and FB5308/DB5308) - so I am maitaining that.

Error may happen:

1- Copied and renamed IDB doesn't match the data structure of target FB.

How do I see that - it is a writeprotected DB so I cannot open it - but it IS a copy from a similar emergency stop FB

2- If you are calling a wrong FB or use a symbol for a non-existing FB.

I am certainly NOT calling a non existing FB (as the screenshot should show you (the FB is not red). I have tried to connect to the DB both as DB5331 and as Estop5IndCat (the symbolic name) but still no joy.

So what else can I try?

hdhosseini

The main instruction is in the FB and you always need one copy of that. Each FB need associated instance DB in several cases. Normally the FB number and symbol name is the same if you have a similar instruction and DB number should differ.

Error may happen:

1- Copied and renamed IDB doesn't match the data structure of target FB.

2- If you are calling a wrong FB or use a symbol for a non-existing FB.

I hope it helps

hdhosseini

Thank you for answering smiffy,

Hmm - not sure what you mean - there IS dot at the end of the FB symbolic names - taht is the only difference between the symbolic name of the FB and the corresponding IDB - like this:

FB5307 Estop1Indcat. - DB5307 Estop1Indcat

FB5308 Estop2Indcat. - DB5308 Estop2Indcat

etc.

That work for the existing 8 similar emergecy stops so it should work for the 4 new ones too.

smiffy

@hdhosseini

Cross post .

If you look carefully at the screenshots, I think the issue is simply a stray dot at the end of the DB reference. See my post.

Smiffy.

Thank you for answering again hdhosseini,

The new FB's are similar to the old ones but each FB is connected to its "own" FDI and each "own" line in the DB for safety data (maybe it gets a even text from there too).

I just did as you suggested and I CAN use FB5310 (Estop4IndCat.) with DB5331 (Estop5IndCat) but when I try to use FB5331 (Estop5IndCat.) with DB5331 (Estop5IndCat) it will not accept it.

But I am not sure what that tells me - what do I need to correct to make it work?

Edit in after I watched your video - thank you for taking the time for that:

I DID give the IDB's new numbers but I THINK the mistake is that I created the IDBs myself (copied from an existing IDB) where I should have let the FB create the IDB after I picked the number. I will try this tomorrow.

hdhosseini

As far as I know, the symbolic name inside the FB block is related to the FB itself. The original block number is FB5310 (Net11) with the symbolic name “Estop4IndCat.” The FB and its IDB are OK and they are matching as there is no complaints from compiler.

In Net12 , “Estop5IndCat.” Is not recognized by the LAD|STL|FBD editor and FB number is not reported by editor. I don’t have the project, but I guess this is a non-existing block or it doesn’t match the requirement to be reported.

If your FB is similar in both cases , simply call FB5310  in Net12.