Sorry, the first image was not attached.
I am trying to get the linkup status of an Ethernet port. I'm using SysEthernetPortConfigAndStatus, but the value I get is Unknown. On Linux, the linkup is working, but is there something wrong with the way I use it? Or do I need to configure something in order to use it?
I understood that the problem is on the slave side. Since this phenomenon can be avoided by the PLC program, we will try to program it according to the slave.
The problem seems to occur when the axis reference (AXIS_REF) is initialized. The reason for this is that the "Fault Reset" bit is set when SMC3_ReinitDrive is executed. It is no problem to reset the drive error explicitly by executing MC_Reset or SMC3_ReinitDrive. However, if the drive error that occurred before the establishment of EtherCAT communication is reset in a non-explicit way (this phenomenon), it may cause unexpected problems and should be avoided.
In the project, there is no program, only the system configuration (see attached file).Why is the Controlword set?
There are no errors in the drive. "Fault Reset" bit is automatically set regardless of whether the drive is in error.
A few millimeters after synchronizing with the slave in EtherCAT communication, the "Fault Reset" bit is automatically set to TRUE (see attached file). I want to disable this, is there any way?
Hi, I want to connect to AWS using the client certificate created by "One-Click certificate creation" (see attachment). However, the key (.pki \ own \ key) is not generated even if the issued client certificate is registered using "Security Agent". Therefore, I converted the issued private key to DER format and saved it in .pki \ own \ key, but the error "TlsCreateContext2: Private key for certificate / CN = AWS IoT Certificate not available" occurs. Will it only support client certificates issued...