PNFD_IL_DIAG and AsynCom_PN_Info
Hi,
I downloaded https://www.plcnextstore.com/#/192 and tried to use the block PNFD_IL_DIAG and in manual it refers to AsynCom_PN_Info_V1_01.
I can't find that block in the folders. I have downloaded the asyncom library but it is not in that library as well.
Best regards Stefan
Comments
This is a documentation error. AsynCom_PN_Info* does only exist in PC Worx 6, not in PLCnext Engineer.
Should I use some other block to read all profinet devices or is it not possible to use PNFD_IL_DIAG in plcnext?
Br Stefan
It is possible to use PNFD_IL_DIAG like this:
8 PNFD_IL_Diag
...
Then we have to fill out the FDestAddr and the SlotID for the safety module. Here we have the safety module on
slot 3 at the first bus coupler and on slot 1 at the second bus coupler. The first safety module has the FDestAddr
33 with the NodeID 90 and the second FDestAddr 35 with NodeID 112.
In PC Worx 6 this is done by AsynCom_PN_Info. But this is technically not possible in PLCnext.
That AsynCom_PN_Info was mentioned in the PLCnext documentation was a mistake because the PLCnext documentation was created from the PC Worx 6 documentation.
Best regards, Oliver
Ok. then it should be possible to read diagnostic to PLC software.
What about the data type ASYN_ARR_DEVICES_PN_0_255, I get error is inaccessible on that data type.
/Stefan
ASYN_ARR_DEVICES_PN_0_255 is provided by the AsynCom library and used in PN_Dev_Diag.
If you include PN_Dev_Diag_4 in your PLCnext project it should work.
If you want to use ASYN_ARR_DEVICES_PN_0_255 directly in your PLCnext project you have to include AsynCom_9 in your PLCnext project too.
AsynCom_9.pcwlx is includes in the MSI file (https://www.plcnextstore.com/#/192, PLCNE_PN_Dev_Diag_4_20200305.msi) too.
If there are any more problems please send your PLCnext project to automation-service@phoenixcontact.com with the call number 00128406 in the subject of your email.
Thank you and kind regards, Oliver