Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

licence for Modbus/TCP IP communication

Created by: Import-User-1 at: 2/1/2014 11:30 PM (42 Replies)

Rating (10)

Thanks 23

Result pages:: |; 1 | 2 | 3 | 4 | 5; |

43 Entries

Entries per page: 10 | 20 | all

2/1/2014 11:30 PM	Rate (0)
Import-User-1 Posts: 3609 Rating: (29)	Import of a Technical Question of the user Ahamed Ahamed Do we need separate licence for Modbus/TCP IP communication,the protocol ,where i am going to use for third party communication. Please reply if do u have idea on this
Import-User-1 Posts: 3609 Rating: (29)
Suggestion To thank Quote Answer

2/2/2014 3:00 AM	Rate (1)
dchartier Grandmaster Joined: 9/27/2006 Last visit: 11/9/2024 Posts: 12293 Rating: (2691)	Hello Ahamed; Siemens offers a Modbus/TCP software for the CP 343-1/443-1 of for the integrated PN port of certain of its CPUs. See the following link for the ordering data for OpenModbus TCP licenses: https://www.industry.siemens.com/services/global/en/IT4Industry/products/simatic_add_ons/s7_open_modbus_tcp/Pages/default_tab.aspx?tabcardname=Order%20Data Note that you can download demo versions with full functionnality from the same page, in the Downloads tab. These demo versions work as well as the licensed ones, so you can use them to prepare and test your comms before the license arrives. However, your diagnostic LEDs will always be active until the licenses are installed, and the diagnostic buffer will fill up with messages telling you there is a license missing, which is a nuisance and somethingyour client can live without. Hope this helps, Daniel Chartier

Suggestion To thank Quote Answer
This contribution was helpful to 3 thankful Users Kaulquappe valerio.albo jack_lohana

3/6/2014 10:11 AM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello Daniel and thank. Doesn't exist a procedure to turn off the slow flashing SF led? Anyway, be so kindly to say at Siemens to inform all client by means message in the support website and also in the Modbus TCP/IP manual. I spent lot of time to understand the problem despite the fact that I had the REG_KEY. It was the first time that I was working with the Modubus TCP/IP, but it was unfriendly to start as a lame duck. Sorry for sounding bitter and thank again. Valerio
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

3/6/2014 11:25 AM	Rate (1)
Sakura Silver Member Joined: 9/22/2010 Last visit: 7/25/2024 Posts: 225 Rating: (28)	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

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users valerio.albo

3/6/2014 12:15 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	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 Attachment REG_KEY-IDENT_CODE.pdf (1339 Downloads)
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

3/6/2014 1:37 PM	Rate (1)
Sakura Silver Member Joined: 9/22/2010 Last visit: 7/25/2024 Posts: 225 Rating: (28)	I noticed that the STATUS_MODBUS is A080, which indicates that value at the input DB_PARAM was changed during runtime. When this error appears, a restart of the PLC is needed. I also noticed that you chose DB100 as the value for DB_PARAM. But according to your screenshots DB100 is not a parameter DB but the control DB from the example project. The parameter DB is the DB that contains the connection settings as well as the Modbus settings. In the example project DB2 is the parameter DB. You can create and edit this DB with the Modbus TCP wizard. So you should first try to fix that problem and then take a look at the licensing again. Maybe the problem is gone afterwards. Regards Sakura

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users valerio.albo

3/6/2014 2:53 PM	Rate (1)
valerio.albo Posts: 23 Rating: (1)	thank again Sakura, in my project DB2 has already occupied for software redundancy (SWR), so I renamed DB2 into DB100 and other relevant DBs, trying to respect the example. Also I used MODBUS TCP Wizard for the configuration, where DB99 is my MODBUS_PARAM For me, it is not clear how to be initialized this DB because I tried but all values has reset i.e. DB100 returns to DB2, IDENT_CODE & REG_KEY values deleted, so I'm understanding that initial values are overwrote by actual values, thus I think that this operation it is not necessary. At the contrary, as per Modbus TCP manual, this a/m procedure is necessary for REG_KEY LICENSE_DB, as you can see in my attachment. Anyway, your collaboration ishighly appreciated, I will try to make the best with your suggestions. Attachment 20140305_154009.jpg (848 Downloads)
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

3/6/2014 3:31 PM	Rate (0)
Sakura Silver Member Joined: 9/22/2010 Last visit: 7/25/2024 Posts: 225 Rating: (28)	If the DB99 is the DB that you created with the Modbus TCP wizard, you have to use this DB for the input DB_PARAM. So when you call MODBUSPN in OB100, you have to insert DB99 at DB_PARAM. The DB100 CONTROL_DAT is only used manage the inputs and outputs of MODBUSPN. It is not "the" parameter DB for DB_PARAM. I've never worked with software redundancy, so I'm not 100% sure how it works. But I know that the license of the MODBUSPN block is only valid for 1 CPU. Which means you need 2 licenses when you use the block on 2 CPUs. And you have to make sure that the correct license is used for each CPU. Regards Sakura

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users valerio.albo

3/6/2014 4:04 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	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: when CPU "A" master, it works Modbus "A" when CPU "B" spare, it works Modbus "B" Anyway, next week I test my control panel (linked to an hardware simulator) in our workshop. 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 Attachment Modbus TCP wizard.pdf (979 Downloads)
valerio.albo Posts: 23 Rating: (1)	Last edited by: valerio.albo at: 3/6/2014 4:06 PM
Suggestion To thank Quote Answer

3/6/2014 4:41 PM	Rate (0)
Sakura Silver Member Joined: 9/22/2010 Last visit: 7/25/2024 Posts: 225 Rating: (28)	Hmm, if you use 2 different licenses, one for each CPU, and if you checked the list in the FAQ, I'm more or less out of ideas... Are you sure that the flashing LED is caused by a license problem? Did the licensing work on your the second CPU? Regards Sakura

Suggestion To thank Quote Answer

Result pages:: |; 1 | 2 | 3 | 4 | 5; |

43 Entries

Entries per page: 10 | 20 | all

|

Share this page:

Share this page on...

Related topics by keywords:

ModbusTCP

Follow us on