AlfredoQuintero
Lifetime Supporting Member
Hello parky, goghie, Brian and all of you who kindly come to help when I get stuck.
I cannot look into the clock issue that parki has written for me, because I have a bigger problem.
We are developing for a customer a firmware for some remote IO device that supports CC-Link IE TSN Class A.
Since this specification's name is so long, I will use here CCLIE for this term.
We are members of the CLPA foundation (the equivalent of ODVA for EhterNet/IP or ETG for EtherCAT). We have ported the CLPA stack to one particulard board, and one of our customers even had their device tested and registered. So our solition is good.
Now there is this new customer who is new to remote IO technology and wants to have a CCLIE interface that can send process data, the equivalent of Profinet IO cyclic data or EtherNet/IP implicit messaging with a payload of 124 words both ways.
We developed the application and when communicating with the iQ-R PLC though the CC-Link IE TSN "intelligent" board, we see normal communication with the remote IO and we see Wireshark showing that what the master sends to the remote IO, our application returns it back. This is the only thing that our application does.
By the way, this is why I needed the millsec resolution timer, to measure in the GxWorks3 program how long it takes to send data and get it back.
The problem is...
That the TSN master does not send the process data to the PLC, so the PLC sees no new data from the remote IOs, even though the data can be seen in Wireshark!
It could be my incorrect settings of the program, but if that was the case, the PLC should give communication error. There is good comms. I am using the sample PLC program as documented in the Mitsubishi manuals.
Below is a glance of my problem. If you read this far thank you. Could it be that there is a limitation in the number of words that a CCLIE device can send?
By the way, the discrete data from the remote IO is received as expected.
I cannot look into the clock issue that parki has written for me, because I have a bigger problem.
We are developing for a customer a firmware for some remote IO device that supports CC-Link IE TSN Class A.
Since this specification's name is so long, I will use here CCLIE for this term.
We are members of the CLPA foundation (the equivalent of ODVA for EhterNet/IP or ETG for EtherCAT). We have ported the CLPA stack to one particulard board, and one of our customers even had their device tested and registered. So our solition is good.
Now there is this new customer who is new to remote IO technology and wants to have a CCLIE interface that can send process data, the equivalent of Profinet IO cyclic data or EtherNet/IP implicit messaging with a payload of 124 words both ways.
We developed the application and when communicating with the iQ-R PLC though the CC-Link IE TSN "intelligent" board, we see normal communication with the remote IO and we see Wireshark showing that what the master sends to the remote IO, our application returns it back. This is the only thing that our application does.
By the way, this is why I needed the millsec resolution timer, to measure in the GxWorks3 program how long it takes to send data and get it back.
The problem is...
That the TSN master does not send the process data to the PLC, so the PLC sees no new data from the remote IOs, even though the data can be seen in Wireshark!
It could be my incorrect settings of the program, but if that was the case, the PLC should give communication error. There is good comms. I am using the sample PLC program as documented in the Mitsubishi manuals.
Below is a glance of my problem. If you read this far thank you. Could it be that there is a limitation in the number of words that a CCLIE device can send?
By the way, the discrete data from the remote IO is received as expected.