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

Error Code 8383 | S7-1200 | Modbus RTU Slave

Created by: parshva at: 9/11/2014 1:53 PM (13 Replies)

Rating (3)

Thanks 3

Result pages:: |; 1 | 2; |

14 Entries

Entries per page: 10 | all

9/11/2014 1:53 PM	Rate (0)
parshva Posts: 24 Rating: (1)	Hello all, I am trying to configure my S7-1200 as Modbus RTU Slave and a 3rd party HMI as master with TIA Portal V13 via RS-485. I have developed a sample program (attached) for transferring I0.3 to bit 40004.3 and I0.4 to bit 40004.4 on the HMI. The Tx/Rx LED on CM1241 flashes very quickly (seems almost steady). So I am assuming the connection has been established. But the problem is that the STATUS of the MB_SLAVE block returns Error 8383 intermittently once every 5-6 seconds. The returning of error is also so fast, that it is almost difficult to read out the error. I would really appreciate if someone can review the program and help me figure out the problem. Wasted the whole day, still no luck trying to figure the problem. Thank you. Best Regards, Parshva Attachment D:\Temp\MB_Test_V1.zip (491 Downloads)
parshva Posts: 24 Rating: (1)	Last edited by: Min_Moderator at: 9/18/2014 8:53 AM Add attachment
Suggestion To thank Quote Answer

9/11/2014 2:54 PM	Rate (0)
Pittiplatsch Posts: 1368 Rating: (126)	The manual say to your error code 16#8383 Error in the data address or address is not in the range of the valid area ofMB_HOLD_REG perhaps you can check if thisapplies to your problem.
Pittiplatsch Posts: 1368 Rating: (126)
Suggestion To thank Quote Answer

9/11/2014 3:25 PM	Rate (0)
parshva Posts: 24 Rating: (1)	Hi Pittiplatsch, Thanks for the reply. Already read that in manual. Still cannot figure out the problem. Can you find anything wrong with my program? One thing that I noticed though was that my HMI Master uses 6-bit addressing (ex: 400001), while Siemens uses 5-bit addressing (ex:40001). Maybe this has something to do with the problem? Best Regards, Parshva
parshva Posts: 24 Rating: (1)
Suggestion To thank Quote Answer

9/11/2014 4:27 PM	Rate (0)
Kaulquappe Posts: 3093 Rating: (323)	Hello Parshva, with holding registers the S7-1200 is capable of 6 digit addressing as well. Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (323)
Suggestion To thank Quote Answer

9/11/2014 6:54 PM	Rate (0)
parshva Posts: 24 Rating: (1)	Hi Kaulquappe, If you're talking about setting up Extended Addressing, I've already looked into that. By setting up Extended addressing, the communication error 8383 goes away, but so does the Tx/Rx LED on the Communication Module. This means that communication is lost between both the devices. I suspect that the Station addresses will change too because of the Extended Addressing. For my Master HMI, the node addresses are from 0-to-255 and only 6-bit addressing is allowed. As for the Siemens, for 5-bit addressing, addresses are from 1-to-247 and for 6-bit addressing address, are from 0-to-65535. When I configure the devices such that Master Station Address: 2 (with 6-bit addressing) and Siemens Slave Address: 2 (with 5-bit addressing), I get that Error Code 8383 with Tx/Rx ON. Now, if I try 6-bit addressing for Siemens (while keeping Master Station Address as it is), I don't know what should be the Slave Station address with 6-bit addressing. I have tried configuring 1,2,3,255,256,257,etc.. but none of the, work. With all these cases there is no error code, but again Tx/Rx light also turns OFF. I know it's a bit confusing what I'm trying to say, but I've tried to explain it in the best way possible. Please let me know if you've any further doubts. P.S: I just tried the above attached configuration with Modscan acting as Master, and it worked well! Although, it was again 5-bit addressing. Not sure how to configure for 6-bit addressing. Thank you. Best Regards, Parshva
parshva Posts: 24 Rating: (1)
Suggestion To thank Quote Answer

9/12/2014 11:52 AM	Rate (1)
Kaulquappe Posts: 3093 Rating: (323)	Hello Parshva, extended addressing of registers and addressing a Modbus device via the UNIT id are two different things. They do not influence each other. Whatever addressing you use, 5 digit or 6 digit, the 3rd party device will send an exception telegram when you try to access a registerwhich is not available. Then you will get a different error number. Regarding the UNIT id you must check the manual of the 3rd party device whether a special UNIT is required. Due to my experience, mostdevices can handle UNIT=1. I think you do not evaluate the outputs of MB_CLIENT correctly. They are displayed dynamically, that means they are only available one cycle. When watching them in the variable table you can only see the errors which are present each cycle. I recommend to evaluate the outputs, insert a done counter and an error counter and store STATUS when ERROR is set. Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (323)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users parshva

9/12/2014 2:36 PM	Rate (0)
parshva Posts: 24 Rating: (1)	Hi Kaulquape, Thanks for the reply. 1. I thought that Extended addressing and Unit ID affected each other, since for Standard addresing Unit ID starts from 1 and goes on to 247 whereas for Extended addressing it starts from 0 and goes on to 65535. Anyway, I may be wrong and I trust you that they do not influence each other. 2. Kaulquappe Regarding the UNIT id you must check the manual of the 3rd party device whether a special UNIT is required. Due to my experience, mostdevices can handle UNIT=1. I do not understand what you are trying to say. In the user manual of the 3rd party device, I didn't come across anything called a Special Unit. Can you please give me an example of what should be the Unit IDs for Master 3rd party device and a Slave Siemens PLC should be? 3. I will try to implement your way of monitoring the Status of both MB_COMM_LOAD block as well as MB_SLAVE block. But as far as I know, MB_COMM_LOAD's status shows no error, whereas MB_SLAVE's status shows only 8383 error intermittently. I will still confirm that by the method you suggested. 4. What I am confused about is that since you say that it doesn't matter if it is a 5-bit addressing or a 6-bit addressing, why would the same Siemens Slave configuration successfully communicates with MODSCAN (with 5-bit addressing) and not to the 3rd party Master (having 6-bit configuration). Apart from these different addressing concepts, I do not notice anything that is different Look forward to receiving your valuable inputs soon. Thanks again. Best Regards, Parshva
parshva Posts: 24 Rating: (1)
Suggestion To thank Quote Answer

9/12/2014 4:20 PM	Rate (1)
Kaulquappe Posts: 3093 Rating: (323)	Hello Parshva, the UNIT id is especially necessary when using a ModbusTCP/ModbusRTU gateway. Via the UNIT id the serial slaves are addressed. Addressing of holding registers at the data link layer (to which the Modbus specification refers) are from 0 to 65535. Some system use the addressing of the application layer - e.g. address 40001 means holding register 0. And some manufacturers created the extending addressing of the application layer e.g. address 400001 means holding register 0. When the S7 acts as server, it echoes the received UNIT id. As the S7 is no gateway there are no different serial devices connected. When the S7 acts as client it sends the UNIT id as set in the IDB and expects a response with the identical one. Unfortunately some devices don't answer when the UNIT id is different to what they expect. Then it is hard to find the reason. From my experience I know, that Telemechanique expects 255 (or so) and only responds when the request has got this UNIT. Some devices (e.g. PAC3200 do not answer with UNIT=0), Wonderware expects UNIT=1..... If the manual of the 3rd party device does not mention a UNIT id, the only way is to try. Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (323)
Suggestion To thank Quote Answer

9/12/2014 4:51 PM	Rate (0)
parshva Posts: 24 Rating: (1)	Hello Kaulquappe, Thanks for your note. I understand what you're trying to say. Kaulquappe When the S7 acts as server, it echoes the received UNIT id. As the S7 is no gateway there are no different serial devices connected. When the S7 acts as client it sends the UNIT id as set in the IDB and expects a response with the identical one. Unfortunately some devices don't answer when the UNIT id is different to what they expect. Then it is hard to find the reason. I see. So in Modbus RTU terms, as far as I understand Server~Slave and Client~Master, right? Hence from what you're saying, I can infer that it is hard to find the reason when we configure S7 as Master. But in my case, it is configured as Slave, so I don't think it should be hard to troubleshoot. From my experience I know, that Telemechanique expects 255 (or so) and only responds when the request has got this UNIT. Some devices (e.g. PAC3200 do not answer with UNIT=0), Wonderware expects UNIT=1..... If the manual of the 3rd party device does not mention a UNIT id, the only way is to try. Well my 3rd party device is a HMI by Renu Electronics. No special unit ID has been mentioned in their manual. All they have mentioned is that the Device ID should be between 0 to 255. When I set the 3rd party Master's address at say, 2 and the S7 Slave at 2 too, it does not work. It still shows Error 8383. Any suggestions on that front please? Thanks. Best Regards, Parshva
parshva Posts: 24 Rating: (1)
Suggestion To thank Quote Answer

9/12/2014 5:34 PM	Rate (0)
Kaulquappe Posts: 3093 Rating: (323)	Hello Parshva, error 8383 indicates that the client tries to read an address which is not available in the S7. So which function code does the client use and which register / bit address. Does this address belong to the data link layer or to the application layer? Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (323)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users parshva

|

Share this page:

Share this page on...

Follow us on