# Regarding the diagnostic results on the device **URL:** \ **Category:** B&R Software & Runtime\ **Tags:** automation-studio\ **Created:** [June 4, 2025, 12:54pm UTC](https://community.br-automation.com/t/regarding-the-diagnostic-results-on-the-device/7193 "2025-06-04T12:54:44Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![arijaluddin](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/arijaluddin/32/4066_2.png) [@arijaluddin](https://community.br-automation.com/u/arijaluddin)\ **Post date:** [June 4, 2025, 12:54pm UTC](https://community.br-automation.com/t/regarding-the-diagnostic-results-on-the-device/7193/1 "2025-06-04T12:54:44Z")
![WhatsApp Image 2025-06-04 at 17.15.34](https://europe1.discourse-cdn.com/brcommunity/original/2X/9/9dd4479d21c94644926c8164e6a623ea41b5cc00.jpeg) Can we conclude from this that the damage is on the detected device and can we replace it immediately? ---
**Author:** ![marcusbnr](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/marcusbnr/32/256_2.png) [@marcusbnr](https://community.br-automation.com/u/marcusbnr)\ **Post date:** [June 4, 2025, 1:43pm UTC](https://community.br-automation.com/t/regarding-the-diagnostic-results-on-the-device/7193/2 "2025-06-04T13:43:56Z")
I wouldn’t say it’s possible to conclude anything from just that screenshot. It’s been some time since I’ve worked with the 8V ACOPOS drives, but if I recall correctly, that “X” in the SDM wasn’t abnormal. This is because the hardware that’s on the Powerlink network is actually the 8AC114.60-2 communication module rather than the drive itself. You can see this in the upper right-hand corner. It’s looking for the drive but sees the communication module, which is expected. Which module do you think is damaged? If you’re having problems with your drive, can you please give us some more details about what those problems are? If you’re having communication issues, then the Network Command Trace may help you. ---
**Author:** ![arijaluddin](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/arijaluddin/32/4066_2.png) [@arijaluddin](https://community.br-automation.com/u/arijaluddin)\ **Post date:** [June 4, 2025, 1:49pm UTC](https://community.br-automation.com/t/regarding-the-diagnostic-results-on-the-device/7193/3 "2025-06-04T13:49:06Z")
![image](https://europe1.discourse-cdn.com/brcommunity/original/2X/3/3dbec4ebe944b93adef90d2d35680b13588c9a68.png) If I see that the type is a module in the device, with the information from the SDM, can it be ascertained that this module is the one that is damaged? ---
**Author:** ![christoph.hilchenbac](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/christoph.hilchenbac/32/423_2.png) [@christoph.hilchenbac](https://community.br-automation.com/u/christoph.hilchenbac)\ **Post date:** [June 4, 2025, 2:00pm UTC](https://community.br-automation.com/t/regarding-the-diagnostic-results-on-the-device/7193/4 "2025-06-04T14:00:34Z")
> Can we conclude from this that the damage is on the detected device and can we replace it immediately? It is only a small effort to replace the 8AC114 once, you only have to take over the node number. But I agree with Marcus: no, just with this information you can’t be sure. so please: > can you please give us some more details about what those problems are? ---
**Author:** ![arijaluddin](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/arijaluddin/32/4066_2.png) [@arijaluddin](https://community.br-automation.com/u/arijaluddin)\ **Post date:** [June 4, 2025, 2:08pm UTC](https://community.br-automation.com/t/regarding-the-diagnostic-results-on-the-device/7193/5 "2025-06-04T14:08:46Z")
I don’t understand what you mean by this, what I want is just to normalize everything again so that there are no red marks on the diagnostic system. What I know is that the function of this diagnostic is to detect whether there is a device that is problematic or not, maybe I just need an answer that can provide some solutions ---
**Author:** ![arijaluddin](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/arijaluddin/32/4066_2.png) [@arijaluddin](https://community.br-automation.com/u/arijaluddin)\ **Post date:** [June 4, 2025, 2:09pm UTC](https://community.br-automation.com/t/regarding-the-diagnostic-results-on-the-device/7193/6 "2025-06-04T14:09:58Z")
If I replace it with a new module of the same type, is that possible? So that this problem doesn’t drag on too long? ---
**Author:** ![christoph.hilchenbac](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/christoph.hilchenbac/32/423_2.png) [@christoph.hilchenbac](https://community.br-automation.com/u/christoph.hilchenbac)\ **Post date:** [June 4, 2025, 2:12pm UTC](https://community.br-automation.com/t/regarding-the-diagnostic-results-on-the-device/7193/7 "2025-06-04T14:12:51Z")
yep, simple doing: 1.) switch off the drive 2.) set the number of the new card (copy from old card) 4.) exchange the cards (only 2 screws) 5.) switch on again ( + 6.) dont’ expect the error to be disappeared ) ---
**Author:** ![arijaluddin](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/arijaluddin/32/4066_2.png) [@arijaluddin](https://community.br-automation.com/u/arijaluddin)\ **Post date:** [June 5, 2025, 1:50am UTC](https://community.br-automation.com/t/regarding-the-diagnostic-results-on-the-device/7193/8 "2025-06-05T01:50:15Z")
Apart from the module itself, can it be from a cable or another part? ---
**Author:** ![christoph.hilchenbac](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/christoph.hilchenbac/32/423_2.png) [@christoph.hilchenbac](https://community.br-automation.com/u/christoph.hilchenbac)\ **Post date:** [June 5, 2025, 6:13am UTC](https://community.br-automation.com/t/regarding-the-diagnostic-results-on-the-device/7193/9 "2025-06-05T06:13:14Z")
don’t let us guess. - first check the [status indicators of the ACOPOS](https://help.br-automation.com/#/en/4/hardware/maacp2/kapitel_technische_daten/anzeigen.html) drive itself - and the [LEDs of the AC114](https://help.br-automation.com/#/en/4/hardware/maacp2/kapitel_technische_daten/anzeigen-3.html) - and also a [systemdump (including all diagnosis files) after powering on the PLC could be helpful](https://help.br-automation.com/#/en/4/automationruntime/targets/sdm/sdm/sdm2_sdmpage_systemdump.html) ---
**Author:** ![marcusbnr](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/marcusbnr/32/256_2.png) [@marcusbnr](https://community.br-automation.com/u/marcusbnr)\ **Post date:** [June 5, 2025, 1:55pm UTC](https://community.br-automation.com/t/regarding-the-diagnostic-results-on-the-device/7193/10 "2025-06-05T13:55:47Z")
> what I want is just to normalize everything again so that there are no red marks on the diagnostic system This page of the SDM helps you to diagnose hardware issues by showing you what hardware is connected vs. what hardware is configured in the project. A red X does not necessarily mean a faulty module, nor does it indicate a problem on its own. Are you having problems with the drive, or is the only symptom that X? ---
**Author:** ![arijaluddin](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/arijaluddin/32/4066_2.png) [@arijaluddin](https://community.br-automation.com/u/arijaluddin)\ **Post date:** [June 10, 2025, 3:27pm UTC](https://community.br-automation.com/t/regarding-the-diagnostic-results-on-the-device/7193/11 "2025-06-10T15:27:10Z")
Is there a possibility of errors in the plc program? or is it certain from installed hardware such as on cables or other supporting hardware ---
**Author:** ![christoph.hilchenbac](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/christoph.hilchenbac/32/423_2.png) [@christoph.hilchenbac](https://community.br-automation.com/u/christoph.hilchenbac)\ **Post date:** [June 11, 2025, 5:50am UTC](https://community.br-automation.com/t/regarding-the-diagnostic-results-on-the-device/7193/12 "2025-06-11T05:50:49Z")
Only with the information we have so far, we cannot make a reliable statement. It could be ‘anything’. I’m not even sure if a green tick is displayed if everything is OK… ---
**Author:** ![arijaluddin](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/arijaluddin/32/4066_2.png) [@arijaluddin](https://community.br-automation.com/u/arijaluddin)\ **Post date:** [June 13, 2025, 1:36am UTC](https://community.br-automation.com/t/regarding-the-diagnostic-results-on-the-device/7193/13 "2025-06-13T01:36:26Z")
Well, after I checked it myself, it turned out that the Acopos indicator light was red and there was an error, and maybe I wanted to try replacing the communication cable first because here the function of the hub module is to communicate between PLC - Powerlink - Acopos, so if it has been replaced but the problem is not solved, I will try to repair the Acopos itself, whether it is damaged in another part of the Acopos or the interface hub module that needs to be replaced. ---
**Author:** ![christoph.hilchenbac](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/christoph.hilchenbac/32/423_2.png) [@christoph.hilchenbac](https://community.br-automation.com/u/christoph.hilchenbac)\ **Post date:** [June 13, 2025, 6:31am UTC](https://community.br-automation.com/t/regarding-the-diagnostic-results-on-the-device/7193/14 "2025-06-13T06:31:19Z")
the concept of the error message in ACOPOS is very much dependent on the PLC. The onboard LEDs can only provide a very rough indication of the status. Only the PLC is able to precisely display an error status and the possible causes. Whether it does this depends on the application program, which of course does not come from B&R itself. You should therefore first clarify whether there is a connection between the PLC and the ACOPOS at all. This is indicated by the LEDs on the Powerlink card and there should also be an error message on the PLC (if it has got an HMI of course). If the LEDs indicate a connection, a current network command trace will also show you precise error descriptions. You can obtain a network command trace via Automation Studio (in which case you will of course need the PLC project) or, if necessary, via a system dump. Well, and sometimes a diagnosis via this community is also not optimal, it may take too much time. Don’t hesitate to contact your local B&R support for this. ---
**Author:** ![arijaluddin](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/arijaluddin/32/4066_2.png) [@arijaluddin](https://community.br-automation.com/u/arijaluddin)\ **Post date:** [June 16, 2025, 1:06am UTC](https://community.br-automation.com/t/regarding-the-diagnostic-results-on-the-device/7193/15 "2025-06-16T01:06:46Z")
I think you should read from the beginning of my question, because I have asked in full, I was told to check the hardware, okay I checked, they said through HR is not always accurate, then getting your answer like this makes me even more confused, all device connections must go to the PLC first, right? ---
**Author:** ![christoph.hilchenbac](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/christoph.hilchenbac/32/423_2.png) [@christoph.hilchenbac](https://community.br-automation.com/u/christoph.hilchenbac)\ **Post date:** [June 16, 2025, 9:12am UTC](https://community.br-automation.com/t/regarding-the-diagnostic-results-on-the-device/7193/16 "2025-06-16T09:12:06Z")
> all device connections must go to the PLC first, right? right. But with the information you provided so far we can’t even be sure if there is a proper communication with the PLC. And with just the red LED on the drive we cannot conclude what’s wrong with the drive. And if you not own the Automation Studio project, then all we have left are the LEDs (ACOPOS + AC114) and the SDM.