I have an extensive list of events recorded in the diagnostic buffer, but I lack the expertise to decipher or address them effectively (as my background is primarily in AB PLC systems). The first event recorded is as follows: Event 1 of 120: Event ID 16# 38B3I/O encountered an error while updating the process image input table in the outgoingP area. The error pertains to byte access at address 517 in process image partition 0, which is not user-relevant (Z1: 2942). The requested OB is Program Execution Error OB (OB85) with a priority class of 25. This is an external error occurring at 07:20:04.002 PM on 12/05/1994. The second event is categorized as Event 14 of 120, with Event ID 16# 38CB related to PROFINET IO. The error involves the station return address, specifically the input address 16355. The IO system ID is 100, and the station number is 51. The logical basic address of the IO controller is 16383, and the requested OB is Rack Failure OB (OB86) with a priority class of 25. Like the previous event, this is an external error occurring at 07:20:04.001 PM on 12/05/1994. There are numerous instances of these two events with varying values for the "Basic address of the IO controller: 16383." It would be greatly appreciated if someone could provide a detailed breakdown of each line to explain the significance, potential issues caused, and possible resolutions. The system is currently operational but experiences intermittent halts accompanied by alarms. The main PLC red LEDs indicating "Ext Fault" and "Bus Fault" illuminate briefly before turning off, after which the system resumes normal operation without any manual intervention. This occurs randomly and on a daily basis. The errors observed in Proneta have been attached for reference and assistance is requested in understanding and resolving these issues.
Performing a cross-reference on PQW 517 and PIW 517 reveals attempts to communicate with a device that is currently offline or disabled. Additionally, Profinet node 51 has an address exceeding the configuration set in the controller, indicating unauthorized modifications to the system setup. It appears that changes were made by an individual lacking knowledge of the system's configuration. The expansion of the 417 image table is possible, but only when not in run mode and depending on the memory module installed.
Thank you for responding. Can you provide more information about PQW 517 and PIW 517? I am new to this and unsure how to cross-reference these terms. Could you please guide me on what to look for? Your assistance is greatly appreciated.
If you are searching for the remote IO station with assigned IO address 517, you can locate this information in the HW configuration. Alternatively, you can identify the Remote IO Station by finding the number 51 in the list of stations. It is important to note that a system utilizing an S7-417H CPU is quite complex. An "H" CPU is typically used in a high-availability and redundant configuration. It may be beneficial to seek expert assistance for further guidance.
When troubleshooting a PLC issue related to a faulty IO, it may be helpful to search for the code that accesses the problematic input table using byte access at access address 517. A cross reference search for PIB517 may provide insights, but it's possible that the access method is more intricate and not easily identified. The primary issue lies in stations dropping off the network, rather than the PLC code itself.
From the details you've shared, it seems like you're dealing with two main issues pertaining to your PLC system. The first relates to a program execution error (Event ID 16# 38B3) and the other to PROFINET IO (Event ID 16# 38CB). The former is an error pertaining to the process image partition while the latter is connected to your I/O system. These issues manifest as brief external faults signaled by the red LEDs. Based on my experiences, intermittent faults can suggest several things: loose connections, hardware errors, or even intermittent network disruptions. Since the LED lights indicate "Ext Fault" and "Bus Fault," you may need to check your field devices, as well as your bus system – if there's a loose connection or inconsistent communication, it can lead to occasional system halts. Additionally, it's worth noting that frequent executions of OB85 and OB86 can slow your system down, as it will be busy with error routines. Lastly, remember to seek help from a Siemens PLC expert if possible, because these OBs are specific to Siemens systems and someone with AB PLC expertise might find it challenging to address these errors directly.
From your description, it appears that your system is experiencing timing issues between the field devices and the PLC. This is indicated by "I/O encountered an error while updating the process image input table" and "PROFINET IO" issues. For instance, the address 517 error in the first event suggests a communication error with a specific device attempting to input its state in the process image. The second event, with an error at input address 16355, suggests a similar communication error, this time involving a different device. Both problems seem to be caused by communication errors during the updating cycle. Interpreting the timing, the PLC seems to be halting operations temporarily to handle these exceptions, which would explain the intermittent operation and transient fault lighting. Checking and possibly optimizing your network configuration and the timing of your communication devices might help resolve these errors. This could involve removing or replacing defective devices, checking cabling and connections or adjusting the update rates for devices. Once you address these potential issues, you could clear the error memory to see if the issue persists. Lastly, remember to have the latest firmware installed and PLC programming done correctly. You may need to consult with troubleshooting experts or a Siemens representative directly for more personalized guidance.
It seems like you're dealing with pretty complex scenarios. The first error message suggests a fault in updating the data structure that holds the input information from the external devices. The reference to "byte access at address 517" implies the location within that data structure where the fault occurred. An OB85 or Program Execution Error points towards a fault in the execution of a user program. The second error sounds like a communication error with a PROFINET device, indicated by the term "PROFINET IO" and the Event ID being 16# 38CB. This can happen if there is an error in transmitting data between the PLC and an IO device. The 'Rack Failure OB' or OB86 error generally indicates a hardware issue or a fault in one of the IO modules. To start, I would recommend double-checking your hardware connections, grounding, electromagnetic interference, power supply issues, and making sure all modules are properly seated in your rack. For the OB85 error, check the program blocks for any faults that can be triggered during execution. If the problem persists, you may want to consider contacting a service representative or using a process control software with error handling and debugging features. I hope this gives you a rough idea of what those errors could mean.
These errors seem to revolve around issues with the IO system. For the first event, the issue seems to be in the process image input table, which if I'm not mistaken, is an area where input data from sensors/IO devices is stored before being processed. Some issue with byte access sounds like a memory fault or corruption - a pointer is perhaps trying to reference data in a byte that does not exist in the process image partition. Check if maybe there's an overflow of data - if any of the sensors is sending more data than the allocated buffer can accommodate. As for the second event, it seems to be a communication failure with one of your PROFINET IO devices. The error involves a station return address - this is basically the address from which the signal originated, indicating there's a returning error from the I/O device at station number 51, probably due a rack failure. Check the wiring, connection and functionality of the I/O devices at station 51. Regarding your intermittent halts, this may be due to the PLC briefly losing communication with its I/O devices during these faults. The fact that it recovers without manual intervention suggests the fault is being cleared, maybe when the buffer is full and then cleared? I'd recommend monitoring your I/O data closely, to find out if there’s any trend in the data just before the halt. Also, updating firmware may come in handy in these cases.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: - The events in the diagnostic buffer provide detailed information about errors encountered during the system operation, such as issues with updating process image input tables and station return addresses in the Profinet IO setup.
Answer: - The Event IDs correspond to specific errors related to byte access, process image partition addresses, and IO system IDs, which are crucial for diagnosing the root cause of the Profinet errors.
Answer: - The intermittent halts and alarms, along with the illuminated red LEDs indicating "Ext Fault" and "Bus Fault," suggest underlying issues that may lead to disruptions in system performance and signal potential problems that require attention.
Answer: - Troubleshooting steps may involve analyzing the Proneta logs in detail, identifying patterns in the errors, checking for loose connections, verifying network configurations, and possibly updating firmware or addressing hardware issues to resolve the Profin
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.