Can we conclude from this that the damage is on the detected device and can we replace it immediately?
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.
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?
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?
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
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?
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 )
Apart from the module itself, can it be from a cable or another part?
donât let us guess.
- first check the status indicators of the ACOPOS drive itself
- and the LEDs of the AC114
- and also a systemdump (including all diagnosis files) after powering on the PLC could be helpful
1 Like
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?
1 Like
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
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âŚ
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.
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.
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?
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.