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

Modbus TCP error code inquiry (8304, A083)

Created by: Lynx_H at: 11/27/2024 1:26 AM (11 Replies)

Rating (3)

Thanks 1

Result pages:: |; 1 | 2; |

12 Entries

Entries per page: 10 | all

11/27/2024 1:26 AM	Rate (0)
Lynx_H Regular Member Joined: 6/17/2019 Last visit: 8/19/2025 Posts: 5 Rating: (0)	Our equipment is communicating with other equipment via Ethernet via MODBUS TCP. (FB 905, a Siemens-specific communication function) Both equipment are always powered on, and I am contacting you because a communication error message occurs once in a while without a long cycle. We have processed the logic so that the remaining error codes except A090 can be received sequentially. As a result of checking, communication errors occurred repeatedly once in a while as shown below: W#16#A083 (2~3 times), W#16#8304 (1 time). Only these two error codes appeared. The communication error occurred like that, and normal communication returned within a few seconds. 1. What does the error code mean? What problem does it refer to? 2. What can I check based on the above situation? ============================================================================ Below is the communication error cycle. ----------------------------------------------------- 2024-03-27 Communication fault 13:36:09 Incoming error message 13:36:17 Outgoing error message 2024-03-29 Communication fault 6:54:43 Incoming error message 6:54:52 Outgoing error message 2024-04-07 Communication fault 6:42:18 Incoming error message 6:42:27 Outgoing error message Communication fault 23:16:07 Incoming error message 23:16:15 Outgoing error message 2024-04-10 Communication fault 11:11:20 Incoming error message 11:11:28 Outgoing error message Communication fault 20:40:48 Incoming error message 20:40:56 Outgoing error message 2024-04-12 Communication fault 7:23:41 Incoming error message 7:23:49 Outgoing error message 2024-05-09 Communication fault 3:48:39 Incoming error message 3:48:48 Outgoing error message Communication fault 8:51:08 Incoming error message 8:51:17 Outgoing error message 2024-05-13 Communication fault 13:42:46 Incoming error message 13:42:54 Outgoing error message 2024-05-14 Communication fault 0:59:05 Incoming error message 0:59:13 Outgoing error message 2024-05-17 Communication fault 10:48:14 Incoming error message 10:48:22 Outgoing error message ============================================================================ Attachment Error code & Diagonostics.zip (206 Downloads)

Suggestion To thank Quote Answer

11/27/2024 7:15 AM	Rate (1)
Wüstenräuber Gold Expert Joined: 10/3/2008 Last visit: 9/8/2025 Posts: 996 Rating: (129)	Hi, A083 in a running system means, that ENQ was set during a telegram is still running. You can start the next telegram when the previous telegram was finished. (Have a look at the manual or F1 help, there the error codes are described). Wüstenräuber

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Lynx_H

11/27/2024 7:55 AM	Rate (0)
Lynx_H Regular Member Joined: 6/17/2019 Last visit: 8/19/2025 Posts: 5 Rating: (0)	Wüstenräuber Hi, A083 in a running system means, that ENQ was set during a telegram is still running. You can start the next telegram when the previous telegram was finished. (Have a look at the manual or F1 help, there the error codes are described). Wüstenräuber Thank you so much for your reply. So, regarding the communication error, it sounds like A083 is something that needs to be checked on the client side, and what kind of problem is 8304, and what can I check? When 8304 occurred, the DONE_NDR_Counter stopped, which caused us to display a message that there was a communication error.

Suggestion To thank Quote Answer

11/27/2024 8:10 AM	Rate (1)
Wüstenräuber Gold Expert Joined: 10/3/2008 Last visit: 9/8/2025 Posts: 996 Rating: (129)	Yes, if A083 occurs on client side you must correct the client configuration. Another possibility is, that you tried to initialize the block during a telegram is running. 8304 means, that the connection is not established. Either a communication partner disconnected or there was an internal telegram error, because of the block disconnected and connected again. In this case there must be an error code before 8304 occurs.

Suggestion To thank Quote Answer

11/29/2024 12:28 AM	Rate (0)
Lynx_H Regular Member Joined: 6/17/2019 Last visit: 8/19/2025 Posts: 5 Rating: (0)	Wüstenräuber Yes, if A083 occurs on client side you must correct the client configuration. Another possibility is, that you tried to initialize the block during a telegram is running. 8304 means, that the connection is not established. Either a communication partner disconnected or there was an internal telegram error, because of the block disconnected and connected again. In this case there must be an error code before 8304 occurs. Thank you for your kind reply. Then, does it mean that A083 may have appeared due to an internal telegram operation problem before 8304, and 8304 may have occurred? Let's organize the details related to A083... - The internal function error codes for communication FAULT were A083 and 8304. In the order of error codes, A083 appeared two or three times and 8304 occurred. After that, communication was normal within about 10 seconds. - A083 means that A083 occurs when data transmission is attempted in a MODBUS-only function and data transmission is attempted again before the DONE state, which indicates that the transmission is complete, and the ERROR state, which indicates that it has failed. - The data transmission is currently attempted unconditionally every 0.2 seconds. So I judged that this error occurred every 0.2 seconds when detecting this error called 8304. The forum recommends that you try to send data when it is in ERROR and DONE status. * Are these contents correct? If it is not correct or there seems to be another reason, please let me know.

Suggestion To thank Quote Answer

11/29/2024 6:54 AM	Rate (1)
Wüstenräuber Gold Expert Joined: 10/3/2008 Last visit: 9/8/2025 Posts: 996 Rating: (129)	No, A083 causes no connection break with 8304. These are 2 completely different errors. A083: Before you start the next telegram you have to wait until the current telegram is finished with DONE or ERROR = TRUE. Change your program so that this is fulfilled. You can have a look at the example project too, that is programmed into it. After the change check, that this error doesn't still occur. Then check the 8304. If this error still occur, then check the diagnostic buffer of the PLC/CP, which communication partner terminates the connection: S7 or the partner. Wüstenräuber

Suggestion To thank Quote Answer

12/3/2024 5:32 AM	Rate (0)
Lynx_H Regular Member Joined: 6/17/2019 Last visit: 8/19/2025 Posts: 5 Rating: (0)	뷔스텐로이버 아니요, A083은 8304와 연결이 끊어지지 않습니다. 이 두 오류는 완전히 다릅니다. A083: 다음 텔레그램을 시작하기 전에 현재 텔레그램이 DONE 또는 ERROR = TRUE로 완료될 때까지 기다려야 합니다. 이 조건이 충족되도록 프로그램을 변경하세요. 여기에 프로그래밍된 예제 프로젝트도 살펴보세요. 변경 확인 후 이 오류가 여전히 발생하지 않는지 확인하세요. 그런 다음 8304를 확인합니다. 이 오류가 계속 발생하면 PLC/CP의 진단 버퍼를 확인합니다. 연결을 종료하는 통신 파트너는 S7인지 아니면 파트너인지 확인합니다. 뷔스텐로이버 고맙습니다. A083에 대해 완전히 이해합니다. 8034에 대한 오류는 다음과 같이 CP443-1 모듈의 진단을 통해 얻어졌습니다. 정보는 간헐적으로 발생하며, 발생할 때마다 다음과 같이 대각선에 반복적으로 기록됩니다. ------------------------------------- ------------------------------- "이벤트 1/232: 이벤트 ID 16# F9C1:261A 모듈이 연결을 적극적으로 종료하고 있습니다. 연결 번호 : 1 외부 오류, 들어오는 이벤트 오후 2시 23분 48초 141초 1984년 7월 24일 (코딩: 16# F9C1 261A 0100 0000 E2E0 0001)" "이벤트 2/232: 이벤트 ID 16# F9C1:260D 연결 1이 설정되지 않았습니다. 외부 오류, 들어오는 이벤트 오후 2시 23분 48초 141초 1984년 7월 24일 (코딩: 16# F9C1 260D 0100 0000 E2E0 0001)" "이벤트 3/232: 이벤트 ID 16# F9C1:2622 제어 블록에 의해 연결 1에서 연결 재설정이 트리거되었습니다. 외부 오류, 들어오는 이벤트 오후 2시 23분 48초 141초 1984년 7월 24일 (코딩: 16# F9C1 2622 0200 0000 0100 0000)" ------------------------------------- ------------------------------------- ----- * 제 생각에는 외부 기기와의 연결에 문제가 있다는 것은 알고 있습니다만, 이 정보가 로컬 문제인지 파트너사의 문제인지는 잘 모르겠습니다.

Suggestion To thank Quote Answer

12/3/2024 6:39 AM	Rate (0)
Moderator_Lan Moderator Joined: 7/30/2024 Last visit: 9/12/2025 Posts: 951 Rating: (16)	Hello Lynx_H, Please try to discuss your question in English language. This is an international community and we try to focus on one language. Posting in English will help to generate more replies to your question. This is the translation of your post: Lynx_H Thank you. I completely understand about A083. The error for 8034 was obtained through diagnostics of the CP443-1 module as follows: The information occurs intermittently, and each time it occurs, it is repeatedly written on the diagonal as follows: ------------------------------------- ------------------------------- "Event 1/232: Event ID 16# F9C1:261A The module is actively terminating a connection. Connection number: 1 External error, incoming event 2:23:48 PM 141 seconds 7/24/1984 (Coding: 16# F9C1 261A 0100 0000 E2E0 0001)" "Event 2/232: Event ID 16# F9C1:260D Connection 1 not established. External error, incoming event 2:23:48 PM 141 seconds 7/24/1984 (Coding: 16# F9C1 260D 0100 0000 E2E0 0001)" "Event 3/232: Event ID 16# F9C1:2622 Connection reset triggered by control block on connection 1. External error, incoming event 2:23:48 PM 141 seconds 7/24/1984 (Coding: 16# F9C1 2622 0200 0000 0100 0000)" ------------------------------------- ------------------------------------- ----- * I think we know there is a problem with the connection to the external device, but I don't know if this is a local issue or a partner issue. Kind regards, Moderator_Lan

Suggestion To thank Quote Answer

12/3/2024 7:36 AM	Rate (0)
Wüstenräuber Gold Expert Joined: 10/3/2008 Last visit: 9/8/2025 Posts: 996 Rating: (129)	If CP terminate the connection, another errorcode must be occur before 8304. Either you check the errorcode before 8304 with programming or you write a telegram traffic with wireshark. Wireshark is es very good way to check the communication telegrams. When you have a wireshark trace, attach here.

Suggestion To thank Quote Answer

12/9/2024 7:01 AM	Rate (0)
Lynx_H Regular Member Joined: 6/17/2019 Last visit: 8/19/2025 Posts: 5 Rating: (0)	뷔스텐로이버 CP가 연결을 종료하면 8304 이전에 다른 오류 코드가 발생해야 합니다. 프로그래밍으로 8304 이전의 오류 코드를 확인하거나 Wireshark로 텔레그램 트래픽을 작성합니다. Wireshark는 통신 텔레그램을 확인하는 매우 좋은 방법입니다. Wireshark 추적이 있으면 여기에 첨부합니다. 이에 관심을 갖고 감사드립니다. Wireshark 패킷을 첨부하여 보내드립니다. 본 패킷은 1회 발생한 통신 FAULT 상황이며, 발생시간 번호는 19300 ~ 19437입니다. 관련 IP는 소스(로컬) 192.168.1.4, 목적지(타겟) 10.0.240.1입니다. 상호 IP가 다른 이유는 물리적 연결 중간에 라우터가 있어서 로컬 기기가 라우터를 인식하고 해당 타겟 IP로 송수신하도록 설정되어 있기 때문입니다. 첨부된 패킷을 확인하시고 오류 원인 및 분석 부탁드립니다 TT Attachment modbusTCP_capture.txt (204 Downloads)

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on