Issue with Access - "pin is not writable" Error when using setp

Hello everyone,I'm currently facing an issue while trying to write to the pinusing thecommand in my configuration. Despite the documentation indicating that this pin should be set to read-write by default, I am receiving the error message:"pin 'cia402.4.controlword' is not writable."Here are some details about my setup:

• I have verified the HAL configuration and ensured that the pin is defined correctly.
• The EtherCAT configuration appears to be set up properly, with the relevant PDO and SDO entries.
• The drive is in a state that should allow writing to the control word.

I would appreciate any insights or suggestions on how to resolve this issue. Has anyone else encountered a similar problem? Any help would be greatly appreciated!Thank you!

According to the documentation, the control word is transmitted from the controller to the driver. What should it be? (I checked, and both with out and in I get the same error: not writable.)

controlword is an output pin, not writable.

Here is a small example of how you connect the cia402 component
github.com/dbraun1981/hal-cia402/tree/main/example

If it still doesn't work after that, we need to see your hal and ethercat-conf.xml files.

How should the control word be written and transmitted if it is not a writable pin? I need to write and transmit the control word; how can I do this if it is not writable through HAL? This is a valuable instruction that the driver must execute

You need to share more about what you want to achieve. Sounds like you are going about things the wrong way...
cia402.comp is an interface between Linuxcnc joints and the ethercat cia402 servo drive.

where then in Linux are these signals generated, how to register them for a specific driver And where is the PLC of the machine written?

The cia402 component generates the necessary signalling with the drive's controlword pin.
It has the logic to do state changes and other things required by cia402. Therefore, we don't bother about that, it is all handled by the cia402 component. We just use the cia402 component.

If you want to go your own way, and do the signalling yourself to the drive you write to the drive's controlword lcec.0.0.controlword.
But that is just unnecessary, use the cia402 component instead, connect it as in the example.
You can check the source code for the cia402, it is where the example is.