ctrlX DRIVE bus failure error reaction

[bschmidt]

Hello,

For IndraDrive the error reaction to bus failure could be configured with P-0-4088. With ctrlX DRIVE as of AXS-V-0308 this is not possible. The only possible reaction is F4XXX. Will other options be allowed in future firmware versions?

Best regards,

Brian

[Drives_Uwe]

As one can see in the screenshot there was no real function behind in IndraDrive. So ctrlX DRIVE provides same functionality. Mind that now the reaction can be distinguished in the error reaction itself:

[bschmidt]

I want to clarify that my original post shows ctrlX DRIVE and the AXS-V-03 help system. Below is from IndraDrive and MPX20 help system. Here it shows that the F4XXX bus failure error reaction can be changed to a warning E4XXX, and even the possibility to switch automatically to Easy Startup Mode. We have a customer who uses this setting to avoid error when their TwinCAT control is rebooted. 

I tried the alternate setting you showed for ctrlX DRIVE, of NC Reaction for F4 with a maximum time of 60s just for a test. But it seems to have no effect, as I immediatly see F4002 if I reboot ctrlX CORE (similar resulte with test error). Maybe I am misunderstanding, but it seems to me there is not equivalent functionality to IndraDrive.

[Drives_Uwe · Accepted solution]

Yes, you are right: The functionality like in IndraDrive is not yet realized in ctrlX DRIVE for this particular function.

[joeG]

Are there any plans to add this functionality into the CtrlX?

[bschmidt]

Is it planned or do we need to submit this as a new feature request for AXS firmware?

If I can please ask your guidance on two related topics:

1. The customer implies that auto-triggering the drive reset (C0500) to clear the F4002 could be an acceptable solution, but apparently they are scared off by this note in the Help. Of course, the drive reset is triggered many times on many machines every time the operator presses the reset button, or as an automatic function, and this has never been a real problem that I know of. In fact I don’t know why setting S-0-0099 would be stored in the NVRAM anyway - this is a command, not a setting that needs to be stored. Should this really be a concern for the customer? What is the practical limit for write accesses?

2. The NC reaction time delay in AXS firmware might have helped here, but as you can see from attached video it seems to be ignored. I have tried with test error and real error for F2XXX and F4XXX but the error reaction occurs immediately. I am using AXS-V-0308. 

Best regards,

Brian

[PADE]

Hi,

just small comment to NC reaction in case of bus failure. As far as I know (from IndraDrive) you cannot generate NC reaction when bus is in failure state -> it makes sense because Master control cannot control (there is no connection) drive in that time.

Regards, Pavel