Hi to all.

I read a lot regarding the Modbus TCP licence, and i think i understand which is my problem.

First of all, i've a 319 2 PN DP and through the PN port i've two different modbus comunications.

I've the SF steady on and the error code A090 on the diagnostic buffer, but i found out that on the modbus's instace DB is configured the DB1 as a DB_PARAM but (i dont know why) the true number of the DB_PARAM is DB3.

I read also that is not possible to make a change in the modbus's instance DB if this has been created with the wizard.

My question is how can change this value without impact on the comunication?

Regards.

Hi Kaulkuappe,

Yes you are rigth ,  i've found out it today when i invert th DB1 an DB3.

As i said before i read a lot about the licence problem, even an your  discussion, but i try to follow all suggest from the forum and the FAQ, but the problem is still present.

The SF lamp is steady on, not blinking, but i'm pretty sure that the problem is the licence because if i perform a stop run of the CPU without the OB121 inside, the CPU doesn't start and the cause on the buffer is referred at the first call of the FB102.

When i restar the CPU with the OB121 inside, the error on the buffer is A090.

Later i will post the instance DB and you could see that the row Licence is true, the IDENT_CODE is ok, but the REG_KEY is missing.

I try to repeate the procedure for insert the REG_KEY even in the data view, i've checked the FC10 is inside, i've cheked the space or 0 insteade of O, but the problem is still present.

Please help me.

Hi Alfredo@as99

did I get you right? You already registered your Modbus product and received a REG-Key from the license team?

Your matter sounds a little strange. Because if the license for modbus is missing the SF-LED will blink and not be steady on. You wrote the license bit is 'true" but the Reg-Key is empty? That also can not be.

Maybe their is an other fault in your program (like a calculation error) which will call the OB121, and so if its missing the CPU stops and turns on the SF-LED.

Did you try to comment out the modbus function for test? Just to see if the CPU stop comes really from the modbus function block.

Greetings Bachgeist 

Hi Bachgeist,

thanks for your reply, yes i did it, i've already registered my licence.

I'm pretty sure that the problem is the licence because if i sart the cpu without the OB121, doesn't start and in the buffer i see the cause of the stop from the first call of the modbus.

I don't know if could be the reason of the problem, but in my project i've two comunication in modbus tcp for two different devices.

Do you think could be that?

i've attached my db's

Regards.

Hi Alfredo@as99,

as I can see the license key is valid, so this is not the problem.

Did you uncommend the modbus function for test, what else the problem could might be?

Regards bachgeist