About Trumpf_Gunnar

Trumpf_Gunnar · ‎11-16-2023

There are ALIAS parameter available that can be written over SOE and these are following the 16Bit IDN. In your case you have to use P2389 ad P2390 to be able to write S602.1.130 and S602.1.130. These are list parameters and you have to write the first list element to configure the physical encoder type. Please refer to the parameter description of IndraDrive

Trumpf_Gunnar · ‎06-12-2023

No you don't need a restricted firmware

Trumpf_Gunnar · ‎06-07-2023

I had a look to the scope. You see that right before the C0600 is finished the control is switching the command value (P47) from a value close to the actual position to -260mm. This jump in the commanded position is the reason for the F2037. If you are able to do an other oszi plot, then please add the status information S135 and P115. Then we have the possibility to get some more drive status information There is an E4071 also present, that indicates an problem with EtherCAT communication (parameter channel). For further diagnostic the parameterfile is need to get the detail diagnostiv for this warning.

Trumpf_Gunnar · ‎04-26-2022

An addition to the post: The encoder of MS2S motors ctrlX SENSEmotor ist not suitable for safe motion application. You can only use this MS2S motors in combination with STO function of an ctrlX DRIVE.

Trumpf_Gunnar · ‎02-14-2022

I think the best way is to add the Parameter S-0-0139 in the "Startparameter". Go to IO-Engineering and double click on the drive you want to activate the parking axis. Each startup of the EtherCAT bus the parameter will be written to 3 an and function "parking axis" is activated.

About Trumpf_Gunnar

Re: write SOE Parameter with structure index

Re: ctrlX DRIVE

Re: F2037 when homing

Re: Safemotion for all encoder types?

Re: Parking axis after reboot