Store PLCnext CommunityPLCnext on LinkedInPLCnext on Instagram  PLCnext on YouTube Github PLCnext CommunityStore PLCnext Community

  1. sngonkha
  2. PLCnext Technology & PLCnext Controls
  3. Friday, 27 November 2020

Regarding with the communication byte size from twos device not equal

  • AXC 2152 [ PND IO  = 512 ]
  • ILC 131 [PND IO = 256]

Does it possible to communicate each other together ?

Oliver PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo

Hello,

I think in both cases the Data you mention are the PN Device Data.
You have to use one PLC as a controller for this to work.
Who should be PN Controller?
How many data do you need?

Phoenix Contact Electronics Headquarter - PLCnext Runtime Product Management and Support

sngonkha Accepted Answer Pending Moderation
0
Votes
Undo

Hi Oliver

 

The PN controller is AXC 2152, ILC 131 is PN device. I try to create the new data type  PN_IO_256 but the connectivity still not work. Please suggest if further suggestion !

Oliver PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo

Hello,
you can modify the IO length in your ILC /PCWorx Project.
And Adapt the IO Length at the Submodule Settings of the PN Device in the PLCnext engineer.
PN ILC AXC

Phoenix Contact Electronics Headquarter - PLCnext Runtime Product Management and Support

sngonkha Accepted Answer Pending Moderation
0
Votes
Undo

For this project PN IO 256 it's good enough to transfer data between 2 device. But from the PN client side AXC 2152 default PN IO is 512. 

So I decide to create new PN IO 256 in new datatype worksheet, but the communication is still cannot establish.

Do you have any check list to help me investigate it ?

Oliver PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo

Hello,
I do not see the problem.
You do not needto change the PN device parameters of the AXC F 2152.

You dont need to touch those if the AXC should be the PN Controller.

1. Change PN IO in the ILC 131 Project to 256 in PC Worx -> Wrie new configuration to device
 
2. Change PN IO at the PN ->131 Submodule in the PLCnext Engineer to 256 like displayed in my screenshot.

There is nothing else you have to change I think.

Please send me a screenshot of the error you are seeing and your current configuration.

kind regards,
Oliver

Phoenix Contact Electronics Headquarter - PLCnext Runtime Product Management and Support

sngonkha Accepted Answer Pending Moderation
0
Votes
Undo

In attachment is my configuration from both PN - Controller and Device. Feel free to let me know if you see something missing

Attachments (2)
Oliver PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo

Hello,
Configuration looks okay.
Now the question is if you assgined the Name "ilc-131-eth-device-1" to your ILC?
What PN error code do you get when your PLC starts?
What can you see in the WBM of the AXC F 2152 PN Diagnostic.

Phoenix Contact Electronics Headquarter - PLCnext Runtime Product Management and Support

sngonkha Accepted Answer Pending Moderation
0
Votes
Undo

The Station name has already assigned to "ilc-131-eth-device-1" bu the error  [ CODE 23 ] still indicate from AXC 2152 Profinet diagnostic.

Note - error figure and PCWORX Profinet communication setting are in attachment

 

Attachments (2)
Oliver PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo

Hello sngonkha,


please try setting it up following these instructions.

  • Create a new PnE project
  • Include the Controller ILC 131 below the PN configuration
  • Assign the devicename below the ILC 131 settings
  • Set the device name with Netnames for example
  • Create a new PC Worx program
  • Select the ILC 131 template
  • Select the same devicename in PCW as in PnE
  • Send the PN device activation to the ILC 131(s.A)
    • ​​
  • Reboot the Controller ILC 131
  • The PN communication should be established

Phoenix Contact Electronics Headquarter - PLCnext Runtime Product Management and Support

  • Page :
  • 1


There are no replies made for this post yet.
However, you are not allowed to reply to this post.