I am facing this issue,
Drive : 80VD100PD.C000-01
Hello @veeresh.suranagi
to the right of the messages of “NC Manager” in the logger, there are more details about the reason why software init has been aborted.
It’s in the column “ASCII data”. Could you please check which information you see additionally? You could also attach your logger to this thread so I can check it.
It would also help to see the Network Command Trace of that system during the fault. Potentially some parameter that is transferred to the ACOPOS is not within range and this causes the Init to fail.
Best regards
Lukas
1 Like
Hello @veeresh.suranagi
what I meant was the whole column “ASCII data”, for example like this from a logger I have here:
There is more information when you scroll to the right, you can also shrink the columns so the “ASCII data” column is right next to the “Description” column.
Could you please attach the whole logger .logpkg file or the SystemDump you can load from System Diagnostics Manager?
Thanks!
Hello @veeresh.suranagi
the problem is that the Powerlink interface “IF1” is not configured on this system for Motion in the NC configuration.
Within your NC configuration file, you need to add a Powerlink interface named “IF1”, since Powerlink ACOPOS drives (the 80VD100PD.C000-01) want to use it.
- Go to your Configuration View and find “acp10cfg.ncc” within the folder “Motion”.
- Open this file and right click into the empy space. Chose option “Insert Interface…”
- Add a Powerlink interface named “IF1”.
- Save and transfer the project to the target.
@lukas.struber Thanks for detailed information.
followed same procedure and then issue resolved.
1 Like