Issue with Access - "pin is not writable" Error when using setp
1 year 8 months ago #320650
by rodw
Replied by rodw on topic Issue with Access - "pin is not writable" Error when using setp
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.
cia402.comp is an interface between Linuxcnc joints and the ethercat cia402 servo drive.
Please Log in or Create an account to join the conversation.
1 year 8 months ago #320739
by Ri
Replied by Ri on topic Issue with Access - "pin is not writable" Error when using setp
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?
Please Log in or Create an account to join the conversation.
1 year 8 months ago #320755
by Aciera
Replied by Aciera on topic Issue with Access - "pin is not writable" Error when using setp
You need to connect the relevant signals in your .hal file as in the example linked in the post above.
Not sure which PLC or which machine you are referring to.
And where is the PLC of the machine written?
Not sure which PLC or which machine you are referring to.
Please Log in or Create an account to join the conversation.
1 year 8 months ago - 1 year 8 months ago #320779
by Hakan
Replied by Hakan on topic Issue with Access - "pin is not writable" Error when using setp
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.
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.
Last edit: 1 year 8 months ago by Hakan.
Please Log in or Create an account to join the conversation.
1 year 8 months ago #321868
by Ri
Replied by Ri on topic Issue with Access - "pin is not writable" Error when using setp
Where in Linux are these signals generated, and how can I configure them for a specific driver? At what point do I need to inform Linux that the driver should specifically use control word 0Fh? I need to insert 0Fh into 6040, but it doesn't seem to work.
Please Log in or Create an account to join the conversation.
1 year 8 months ago #321871
by Ri
Replied by Ri on topic Issue with Access - "pin is not writable" Error when using setp
If I turn on the machine with a button, why doesn't the control word value change? Please explain to me not where the signals are transmitted, but how to send a specific value to the control word.
Please Log in or Create an account to join the conversation.
Time to create page: 0.305 seconds