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

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: 9/14/2025 Posts: 12408 Rating: (2717)	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: 2/10/2025 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 (1566 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: 2/10/2025 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 (999 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: 2/10/2025 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 (1190 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: 2/10/2025 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

3/6/2014 5:43 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	unfortunately I have alreay disassembled the CPUs, in the tab Diagnostic Buffer, in both CPU, it appears two errors: A090 I'm not sure, some regarding OB121, about write error ... ok next time is better to make more snapshots I'm reading this FAQ http://support.automation.siemens.com/WW/view/en/58497002 So the license is necessary only to turn off the SF led License or not license, this is the question
valerio.albo Posts: 23 Rating: (1)	Last edited by: valerio.albo at: 3/6/2014 5:44 PM
Suggestion To thank Quote Answer

3/7/2014 9:38 AM	Rate (1)
Sakura Silver Member Joined: 9/22/2010 Last visit: 2/10/2025 Posts: 225 Rating: (28)	Both errormessages (A090 and write error) belong together, they are both about the missing license. And yes, the license is "only" necessary to stop the LED flashing. But I would say it's a good thing. Because that way you have the complete functionality of the Modbus block without having to buy a license. You can do the configuration and the testing without a license. Only the productive PLC needs a license.

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

3/28/2014 10:21 AM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello Sakura, I'm testing my PLC and slow flashing LED is still present. Program works correctly, both sw redundancy and MODBUS TCP/IP, but I'm trying to remove the problem regarding MODBUS license without any result. I'm attaching all DBs that contain information regarding Modbus license. If necessary I will send you whole program, please indicate me how to do. Thanks in advance. Valerio Albo Attachment Modbus license.pdf (744 Downloads)
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

3/28/2014 1:48 PM	Rate (0)
Kaulquappe Posts: 3093 Rating: (324)	Hello Valerio, is FC10 EQ_STRNG available in the CPU? It is required to evaluate the registration key. Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (324)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users valerio.albo

3/28/2014 2:14 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello Kaulquappe, FC10 EQ_STRNG is available in my programm, see attached picture. As I wrote in previous post, from diagnostic buffer I see error code A090 for missing license, but as you can see in my DB, I insert reg_key, ident_code, but when I test online I see license = false. Well, tips for next control step? Thanks to all in advance. Attachment FC10.GIF (657 Downloads)
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

3/28/2014 2:41 PM	Rate (1)
Kaulquappe Posts: 3093 Rating: (324)	Hello Valerio, I was so concentrated on the registration key, that I didn't recognize that you get error A080. As long as this error is present, the evaluation of the registration key is not possible. Error A080 occurs when the Modbus FB is not called in OB 100 or when you transfer the IDB of the Modbus block during runtime. Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (324)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users valerio.albo

3/28/2014 3:58 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello Kaulquappe, many thanks ... Now we try but MOD_PARAM is configured by Modbus TCP wizard (see attached), maybe shifting end address for data area (i.e. from 14 to 20, I don't know exactly). I'm not sure what to do, please be so kind to help me. Attachment error code and wizard.pdf (577 Downloads)
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

3/28/2014 5:05 PM	Rate (1)
Kaulquappe Posts: 3093 Rating: (324)	Hello Valerio, error A080 is not caused by any parameterization. It is a missing OB100 execution (STOP/RUN of the CPU). Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (324)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users valerio.albo

3/28/2014 5:20 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello Kaulquappe I'm posting my OB100, maybe the problem is here, or not. However I only change the number of DB of the example. I have to delete the online DB? Or exist a procedure to follow? Many time I have tried with STOP/RUN of the CPU by means of its selector on the frame. Or I do this operation by PC forcing STOP/RUN via buffer diagnostic? A big prize for the solution! Anyway I seem that the end is near ... the light at the end of the tunnel Attachment OB100.pdf (670 Downloads)
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

3/28/2014 6:18 PM	Rate (1)
Kaulquappe Posts: 3093 Rating: (324)	Hello Valerio, your OB100 is correct. The only thing I can think of at the moment, that you use different IDBs for the Modbus block in OB100 and OB1. The IDBs must be the same. Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (324)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users valerio.albo

3/31/2014 9:00 AM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello Kaulquappe, attached my OB1. Take note that, in this program there are Modbus TCP and software redundancy, as you saw in my OB100. This morning I try again ... anyone have any suggestions is welcome Attachment OB1.pdf (626 Downloads)
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

3/31/2014 11:39 AM	Rate (1)
Kaulquappe Posts: 3093 Rating: (324)	Hello Valerio, I think now I got it! You use ID=1for both connections. You must use different connection IDs. Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (324)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users valerio.albo

3/31/2014 12:13 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	You got it Kaulquappe, I set for master cpu=A ID=3 and for spare cpu=B ID=2 and all SF led are now off. Champagne for everyone. Thanks a lot
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer
This contribution was helpful to 2 thankful Users S_Moderator Kaulquappe

4/3/2014 5:09 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Last question (I hope). Now I changed ID for modbus connection, but now it is not possible to check by means of modbus simulator. Is it necessary some change in OB100? L 1 or ID set by MODBUS TCP WIZARD? T "CONTROL_DAT".ID L T#500MS T "CONTROL_DAT".RECV_TIME L T#5S T "CONTROL_DAT".CONN_TIME CALL "MODBUSPN" , "IDB_MODBUS" ID :="CONTROL_DAT".ID DB_PARAM :="MODBUS_PARAM" RECV_TIME :="CONTROL_DAT".RECV_TIME CONN_TIME :="CONTROL_DAT".CONN_TIME KEEP_ALIVE := ENQ_ENR := DISCONNECT := REG_KEY := LICENSED := BUSY :="CONTROL_DAT".BUSY CONN_ESTABLISHED:="CONTROL_DAT".CONN_ESTABLISHED DONE_NDR :="CONTROL_DAT".DONE_NDR ERROR :="CONTROL_DAT".ERROR STATUS_MODBUS :="CONTROL_DAT".STATUS_MODBUS STATUS_CONN :="CONTROL_DAT".STATUS_CONN STATUS_FUNC :="CONTROL_DAT".STATUS_FUNC IDENT_CODE := UNIT := DATA_TYPE := START_ADDRESS := LENGTH := TI := WRITE_READ := UN "CONTROL_DAT".ERROR S "CONTROL_DAT".ENQ_ENR //INIT completed without error, enable data transfer SPB end L "CONTROL_DAT".STATUS_CONN T "CONTROL_DAT".Save_STATUS_CONN //for static display in VAT L "CONTROL_DAT".STATUS_MODBUS T "CONTROL_DAT".Save_STATUS_MODBUS //for static display in VAT // STATUS_FUNC => Save_STATUS_FUNC L DB100.DBD 38 T DB100.DBD 92 L DB100.DBD 42 T DB100.DBD 96 L DB100.DBW 46 T DB100.DBW 100 end: NOP 0
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

4/3/2014 5:39 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	or in the IDB_MODBUS, first row ID? or both IDB_MODBUS and OB100? others?
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

4/3/2014 5:42 PM	Rate (0)
Sakura Silver Member Joined: 9/22/2010 Last visit: 2/10/2025 Posts: 225 Rating: (28)	You have to change the ID in the program as well as in the parameter DB (by using the Modbus TCP Wizard). This means if you use ID=3 for one connection and ID=2 for the other one in OB100, you need to have one connection with ID=3 and one connection with ID=2 in the parameter DB(s).

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

4/4/2014 10:41 AM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello I change ID in the OB100, by means wizard I compile DB MODBUS_PARAM, in the relevant DB IDS_MODBUS I set the correct ID but the result is that modbus works but license=false (A090). If I change again the ID the license=true but modbus doesn't work and the code error is A079. Where is the problem? Now I try with ID=100 to test any conflicts.
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

4/4/2014 1:29 PM	Rate (0)
Sakura Silver Member Joined: 9/22/2010 Last visit: 2/10/2025 Posts: 225 Rating: (28)	I'm not sure if I understood the changes you made correctly. Assuming you use the IDs 2 and 3 and one DB_PARAM, the OB100 should look like this: ********************************************** // first connection L 2 T "CONTROL_DAT".ID ... CALL "MODBUSPN" , "IDB_MODBUS" ID :="CONTROL_DAT".ID DB_PARAM :="MODBUS_PARAM" ..... // second connection L 3 T "CONTROL_DAT2".ID ... CALL "MODBUSPN" , "IDB_MODBUS2" ID :="CONTROL_DAT2".ID DB_PARAM :="MODBUS_PARAM" ..... ********************************************** The parameter DB MODBUS_PARAM should look like this: OUCW_1 STRUCT block_lengthWORD W#16#40 id WORD W#16#2 ..... OUCW_2 STRUCT block_lengthWORD W#16#40 id WORD W#16#3 ..... I hope this helps. Regards, Sakura
	Last edited by: Sakura at: 4/4/2014 1:30 PM
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users valerio.albo

4/4/2014 3:09 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello Sakura I have a connection for each CPU, anyway I've already tested your instruction but the problem is always the same, working modbus with no license, or license with no working modbus. So I think, are there some mistakes in my IDB_MODBUS? In my attached DB shall I to change address 0.0, 2.0, 348.0 and 350.0? Attachment IDB_MODBUS.pdf (624 Downloads)
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

4/4/2014 3:50 PM	Rate (0)
Sakura Silver Member Joined: 9/22/2010 Last visit: 2/10/2025 Posts: 225 Rating: (28)	No, never change the values in the instance DB directly. This wouldmess up the functionality of the Modbus block. If you attach your OB1, OB100 and theparameter DB(s), I can check if I find the problem.

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

4/4/2014 4:14 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Thanks in advance, please take note that ID=9 attachment: OB1 OB100 DB97 IDB_MODBUS DB99 MODBUS_PARAM Attachment OB1-OB100-DBs.pdf (578 Downloads)
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

4/4/2014 4:44 PM	Rate (0)
Sakura Silver Member Joined: 9/22/2010 Last visit: 2/10/2025 Posts: 225 Rating: (28)	I think I'm a little confused now about the two different connections, probably because I don't know much about software redundancy... When using software redundancy, you have two different CPUs. And you have the same program on CPU, which means on both CPUs there is a CONTROL_DAT, IDB_MODBUS and a MODBUS_PARAM. On both CPUs you use the same ID for the connection. Is that correct? I'm asking that because I can only see one connection in the OBs / DBs that you uploaded and I'm wondering where the second connection is.

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

4/4/2014 5:02 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello I have different ID, ID=8 for the first CPU, ID=9 for the second CPU. In the previous post I attached OBx and DBs for the second CPU. Now I am attaching also CONTROL_DAT DB. Modbus TCP is not in the software redundancy. Hence two CPUs, with two modbus, with two different ID, in order to avoid any problem with the redundancy. Attachment DB100.pdf (521 Downloads)
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

4/7/2014 10:54 AM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello I'm checking the Modbus example to try to find any errors, and I have found that FB104 is used both sw redundancy and MODBUS TCP, so I decided to use FB104 SWR_AG_COM (for sw redundancy) because my modbus is server (not client). Is it a problem? And if yes, what can I do? Attachment FB104.pdf (580 Downloads)
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

4/7/2014 11:44 AM	Rate (0)
Sakura Silver Member Joined: 9/22/2010 Last visit: 2/10/2025 Posts: 225 Rating: (28)	I checked the OBs in your pdf-File and I couldn't find anything wrong. The DB97 IDB_MODBUS looked a little strange to me. The title says it's an offline DB, but there are a few online values in it (DB_PARAM, REG_KEY, IDENT_CODE). That's not how it is suppose to be. But to be honest, I have no clue what causes the problems in your project Have you contacted the support about the problem? They should be able to help you. If you already have another FB104 in your project, I would suggest to rewire the MOD_CLI block. You shold probably check if all the blocks that theMODBUSPN block calls are the correct ones. Just to be sure that this doesn't cause any problems.

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

4/7/2014 12:01 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello Sakura, don't worry, I call the support. How is it possible to rewire the FB104? I'm afraid to rewire, what happen in FB104 SWR_AG_COM? I see a FAQ that explain what I do but I'm not sure how to do, can you help me? Step by step if possible, see attachment Attachment rewire.pdf (611 Downloads)
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

4/7/2014 2:52 PM	Rate (1)
Sakura Silver Member Joined: 9/22/2010 Last visit: 2/10/2025 Posts: 225 Rating: (28)	This is how I usually do the rewiring: - create a new S7 program in my project (just temporary for the rewiring) - copy all Modbus blocks and the T-blocks to the blocks folder of the temporary S7 program - use the rewire function on the blocks in the temporary S7 program - check the reference data afterwards to make sure it worked properly - copy all the blocks back to the block folder I use for my actual program - delete the temporary S7 program Do you only want to rewire the FB104? In that case you just have to enter FB104 in the "Vecchio operando" and the new FB number in the "Nuovo operando" column. Regards, Sakura

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

4/7/2014 3:15 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello Sakura, perfect! License valid new code error A003, but in the manual it is not clear for me what I can do now, DB is too short ... what?
valerio.albo Posts: 23 Rating: (1)	Last edited by: valerio.albo at: 4/7/2014 3:40 PM
Suggestion To thank Quote Answer

4/7/2014 4:52 PM	Rate (0)
Sakura Silver Member Joined: 9/22/2010 Last visit: 2/10/2025 Posts: 225 Rating: (28)	It means that a DB that is used to store the Modbus datais too short. I can see in the parameter DB99 that you only use data area 1. You use DB90 to store input registers from 0 to 14. This means DB90 has to be at least 16 words long. 15 words are used for storingModbus data and 1 word is used for internal purposes.

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

4/7/2014 4:59 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello, I supposed the same problem and I tried with end address 30 but I have the same error, is it wrong?
valerio.albo Posts: 23 Rating: (1)	Last edited by: valerio.albo at: 4/7/2014 5:17 PM
Suggestion To thank Quote Answer

4/7/2014 5:21 PM	Rate (0)
Sakura Silver Member Joined: 9/22/2010 Last visit: 2/10/2025 Posts: 225 Rating: (28)	How large is your DB90?

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

4/7/2014 5:28 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	hello attached my DB90 Attachment DB90.pdf (754 Downloads)
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

4/8/2014 11:19 AM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello, I've done it! I fixed my DB90 following the example and now it all works
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Sakura

|

Share this page:

Share this page on...

Related topics by keywords:

ModbusTCP

Follow us on