About ericvergara

Hello colleagues, please return the device to DC-AE/SVC432 and ask for cost-free express handling. Most probably there is a defect inside the EtherCAT EEPROM. It results exactly in the symptoms you see in the ctrlX I/O Engineering. The identification by the information from the device description file is not possible. It is not a hardware damage, but a software defect that will be corrected in the factory. You will get your very same device back. Your ctrlX SAFETY team @Drives_Uwe , @Dias : FYI ... View more

We did not find a solution but it was not important for the customer anymore, ... View more

Hi, The error in description file will fixed in next release of adaption package. Yes, the error in description file may lead switching torque mode work incorrectly. If you don't wait for next release, you can edit the decription file manually and reintall it in deveice repository. There should be 2 changes: <Parameter ParameterId="8040" type="std:INT"> <Attributes channel="none" download="true" functional="false" offlineaccess="read" onlineaccess="read"/> <Default> 1168 </Default> <Name name="localStrings:out.dwSetTorque"> MDT.Torque_force_command_value </Name> </Parameter> ... <Parameter ParameterId="8540" type="std:INT"> <Attributes channel="none" download="true" functional="false" offlineaccess="read" onlineaccess="read"/> <Default> 1119 </Default> <Name name="localStrings:in.dwActPosition"> AT.Actual_velocity_value_encoder_1 </Name> </Parameter> Thank you! ... View more

Hello, Just a quick update, I have checked that inside the WR there is an app that is called "Android Agent", there it is only needed to go "Rotate Control" and "Portrait" Then the HMI is displayed as vertical! 😄   ... View more

Hello we checked the behavior and found out, that there are some settings in the PLC runtime we have to add. Currently there's no workaround. We addressed the issue to the development to fix this issue by Bug 582376. kind regards ... View more