3/6/2014 11:25 AM | |
Joined: 9/22/2010 Last visit: 7/25/2024 Posts: 225 Rating:
|
Hello Valerio, in general as soon as athe Modbus block recognizes a valid license, the SF should no longer flash. If it still flashes eventhough you have a valid REG_KEY, I would recommend to check the following FAQ: Why is the status value A090 (hex) output for Modbus TCP although you have entered the correct license? Regards, Sakura |
This contribution was helpful to
1 thankful Users |
3/6/2014 12:15 PM | |
Posts: 23 Rating:
|
Hello Sakura and many thanks. I see the adviced FAQ regarding error code A090 (hex) and analized every remedy. Attached You can find my Modbus DBs. In my opinion it is strange that: in DB-param at line 38.0 LICENSED=TRUE while in the CONTROL-DAT DB at line 33.0 LICENSED=FALSE By means of a modbus tcp/ip simulator it was possible to check all my input register from CPU315-2PN/DP, so my conclusion is "it works". Note: the modbus communication is by CPU-PN Maybe there is some problem with OB121 PROG_ERR (Remove call of the Modbus block from OB121, see a/m FAQ), but my OB121 is empty. Otherwise I can broke SF led Regards. Valerio AttachmentREG_KEY-IDENT_CODE.pdf (1244 Downloads) |
3/6/2014 4:04 PM | |
Posts: 23 Rating:
|
Well, attached step by step my Modbus TCP wizard in order to check my Modbus DBs. First of all, please note that I choose to exclude Modbus TCP from redundancy, each CPUs has own Modbus that works separately, with 2 nos. license, so I prefer that:
So far it seem that CPU works correctly: SW redundancy ok, Modbus TCP ok, only flashing SF led for missing license (A090). Many thanks Sakura AttachmentModbus TCP wizard.pdf (885 Downloads) |
Last edited by: valerio.albo at: 3/6/2014 4:06 PM |
|
Follow us on