KR C4 using profinet,I have configured it in workvisual,1024 input and output. all can be used on PLC side.
But the PNIO-DEV error shows up(KSS00099), the KR C4 can't ready in Automatic External mode.
If I don't map the IO from profinet to KRC, it will not show this error,
But if I do mapping it, even just 1 input or 1output, it will show up again.
Is my profinet config wrong or what? I've trying to solve this for an entire day.Still no luck.
PNIO-DEV READ/WRITE ERROR.
-
Kurt.Guo -
March 27, 2018 at 4:02 PM -
Thread is marked as Resolved.
-
-
only a day and day is not over yet...
relying on luck or chance to get result is something that may work - if one has plenty of time or a lot of luck. evolution works that way but it takes really long time...
another option is work like an engineer - methodically. this requires reading manuals and instructions.
an example of very basic instructions is READ FIRST topic. it tells how to ask for help and what kind of info one may want to provide...maybe versions of software you use are incompatible or settings are wrong.... your turn
-
OK I can see that my word seems make you very unhappy.
No luck is just saying I haven't fix it, it's not like I'm really count on luck.
And I will try not do that again with my poor English.
A day is indeed over, since its 1:30AM here in China and Im still here reading PDF, had to get up and go for work at 6:30AM.
As software side, both WoV and profinet KOP is copied from the KRC hard drive.
not so sure about settings, because this is the first time I do this. I added PROFINET to the fieldbus, right click to setting, checked active,0safe IO,1024IO, Click Apply and OK.
Then link all of them to KRC DI and DO. -
you can show your settings, you can show how exactly you map I/O, you can tell software versions.... "KRC4" is not specific enough, but saying "i have KSS8.3.33UL" is quite specific. Saying "Profinet" is not specific but "ProfiNet Device 3.2.2.23" is...
KLI setup, filters etc is a starting point, then we go over network addresses and device names etc. you mentioned none of this.i am trying but cannot help you without info. how could anyone?
-
more info about this issue attached
-
more info about network here
-
hmmm, this is odd...
things look ok but the message clearly says that "plasma" device is of wrong type (wrong device description file). your screenshot #4 however shows "8.3 PNET 3.2" which matches installed software option. -
is there any chance that my coworker used wrong GSD file when he config the PLC?
-
yes,
you need to use this one
-
Just checked, he is using this one.
-
your first screenshot shows 131 bye in and out... WoV configuration shows 1024 bits which is 128 byte. can you try turning off in WoV two checkmarks about alarms?
-
still 131 bytes
-
In diagnosis monitor module Profinet Device stack(PNIO-DEV)
there is an Abort indication counter, the value is 1.
just checked the profinet pdf, it says Abort indication counter=Internal error counter. But it didn't tell where it can be.I ask my workmate to pull up 1 and 1024 on PLC side.
It all match with KRC side. -
Hi Kurt,
1.Why is your network adapter undefined?
Are you connected to the KRC controller?This should normally show your PC Ethernet adapter/ Network adapter connected.
2.When you right click --> Profinet --> Connect
Right click Profinet --> Functions --> Device list and profinet names
Do you see any devices here?3.You have activated both Profinet Device and Profinet Controller. So are you implementing the controller to operate as both Profinet fieldbus master and Profinet fieldbus slave device?
Cheers
-
Hi Kurt,
1.Why is your network adapter undefined?
Are you connected to the KRC controller?This should normally show your PC Ethernet adapter/ Network adapter connected.
2.When you right click --> Profinet --> Connect
Right click Profinet --> Functions --> Device list and profinet names
Do you see any devices here?3.You have activated both Profinet Device and Profinet Controller. So are you implementing the controller to operate as both Profinet fieldbus master and Profinet fieldbus slave device?
Cheers
1.Yes, I'm connected to the KRC using KLI, Quadcom PCI-E NIC.
2.Yes, I can see all my device there.like SIMATIC-HMI, SEW driver, ET200S CPU etc.
3.I want to make this KUKA as a slave device.(KUKAplasma, KUKAglue, glue system, SEW turntable drive, turntable encoder)using PROFINET connected to a SIEMENS switch,
from there, 1 cable connected to Beckhoff EL6631, and the rest is all EtherCAT bus. -
That's really unusual,
Based on your pictures provided.
Either you now have a different device connected.
So make sure you request your device merchant to provide you the right gsdml file for the current device.
Or your using the wrong gsdml file for this device. (As it states it hasn't been configured correctly)The device might be the same as the old one but did you check the firmware revision for the hardware/software?
You will find different gsdml file versions too based on the revision. But I do not rule out the idea on broken links between the cat cables.Cheers
-
Is kuka device 100% named "plasma" in plc hardware configuration ?
Try to connect to your profinet network with kuka work visual and then right click on your profinet and select function named Device List and Profinet Names, and check if there is device named plasma.
Usually if you cojnfigure device in TIA portal and if you name it "something" real name on network is going to be for example "xdsomethingxy21"...if name and IP adress is the same like in wov project, than try to reinstal kerc next option, It helped me once after 2 day of unsuccessful attempt of PN configuration :D...ps. sorry for my bad english
Edit: try to post screenshoot of device in hardvare configuration of PLC.
-
Thank you for trying to help me, but due to the tight project schedule, I just gave up that day, then I go out there bought 2 EL6692 and just use EtherCAT.
Much better than ProfiNet.
That's really unusual,
Based on your pictures provided.
Either you now have a different device connected.
So make sure you request your device merchant to provide you the right gsdml file for the current device.
Or your using the wrong gsdml file for this device. (As it states it hasn't been configured correctly)The device might be the same as the old one but did you check the firmware revision for the hardware/software?
You will find different gsdml file versions too based on the revision. But I do not rule out the idea on broken links between the cat cables.Cheers
-
Thanks for the reply, I just switch to using EtherCAT.
I can perfectly understand what you saying.so don't be sorry man.
Is kuka device 100% named "plasma" in plc hardware configuration ?Try to connect to your profinet network with kuka work visual and then right click on your profinet and select function named Device List and Profinet Names, and check if there is device named plasma.
Usually if you cojnfigure device in TIA portal and if you name it "something" real name on network is going to be for example "xdsomethingxy21"...if name and IP adress is the same like in wov project, than try to reinstal kerc next option, It helped me once after 2 day of unsuccessful attempt of PN configuration :D...ps. sorry for my bad english
Edit: try to post screenshoot of device in hardvare configuration of PLC.