AM2434: EtherNET/IP CIP Motion Feature Support

Hi Andrea,

We do not have CIP Motion feature support on AM243x. I will check internally if we have any plans or not.

Hi Nilabh,

Thank you for your reply.

If we implement the Motion Device Axis Object(0x42) by our self, we also need the connection between connection object and application object.

Motion I/O Connection is created by Forward_Open / Large_Forward_Open services.

We find Forward_Open callback function in EtherNet/IP example, but it hasn't more detail information.

Do you have any idea about this?

Thanks,

Chia-Hsun

Nilabh Anand said:

I will check internally if we have any plans or not.

We do not have plans as of now. 

Joshua CH Li said:

If we implement the Motion Device Axis Object(0x42) by our self, we also need the connection between connection object and application object.

Motion I/O Connection is created by Forward_Open / Large_Forward_Open services.

We find Forward_Open callback function in EtherNet/IP example, but it hasn't more detail information.

Do you have any idea about this?

Let me check this internally once.

Hi Nilabh,

Do you have any updates?

We have another question.

1.

Joshua CH Li said:

If we implement the Motion Device Axis Object(0x42) by our self, we also need the connection between connection object and application object.

Motion I/O Connection is created by Forward_Open / Large_Forward_Open services.

We find Forward_Open callback function in EtherNet/IP example, but it hasn't more detail information.

Do you have any idea about this?

2.

We try to use Time Sync Object(0x43), but it seems not implement complete.

For example, we try to get instance Attribute ID 2 "IsSynchronized".

This type is bool and required from CIP specification.

We get IsSynchronized = 0x43 and errcode = 0x0.

Could you help us to check?

uint8_t IsSynchronized;
uint32_t errcode;
errcode = EI_API_CIP_getAttr_bool(pCip_s, 0x43, 0x1, 0x2, &IsSynchronized);

Thanks,

Chia-Hsun

Hi Nilabh,

Do you have any updates?

Thanks,

Chia-Hsun

Hi Li,

Apologies for delay in response, As discussed in today's call the attribute is supported and we will get back once we verify if api call back.

Hi Nilabh,

Do you have any updates?

Thanks,

Chia-Hsun

Hi CH Li,

updated Wireshark trace that is recorded with a 2.1 stack flashed to the LP-AM243 Rev E2, a tp-link TL-SG108E switch for monitoring, and a Allen-Bradley CompactLogix L16ER as clock master.

You see that the launchpad synchronized with the master clock, and that all attributes contain reasonable data. All attributes from 1 - 28 are implement Attribute 29 and further not, but the are not required.

Time Sync Object Attribute Access LP-AM243 EtherNetIP Rev 2.1 2023-07-04.pcapng.zip

Ps: In Wireshark I use a filter !mdns&& !ssdp && !nbns && !igmp to better find the relevant frames.

Please let me know in case if you still see wrong data in attributes, also please check the setup on your end.

Hi Nilabh,

Thank you for your reply, but we discussing in the meeting is get attribute from API side.

Nilabh Anand said:

As discussed in today's call the attribute is supported and we will get back once we verify if api call back.

Your Wireshark capture file is still show the accessing attribute from Ethernet side.

Please help us to check this issue.

Thanks,

Chia-Hsun