XVR error reaction to F88XX

[bschmidt]

Hello,

A customer is testing various error reaction scenarios on his machine. The goal is to do everything possible to allow the NC to do a coordinated shutdown of the axes instead of the drive going into its own independent error reaction.

Since the machine will be installed in region with frequent brownouts, he is testing what happens if mains power is disconnected from the XVR while the machine is running. What he sees is F8812 on the XVR and F8064 on the drives. I also get F8064 on my ctrlX DRIVE demo when I hit the estop, which cuts the 48V supply. So F8064 means the DC bus is nearly at 0V cannot supply current to the motor. 

On the machine, one of the axes is a large drum with a high inertia. We expect the regen energy when decelerating should keep the DC bus energized and allow the coordinated stop, but instead the axis gets F8064 and is coasting (torque free). One question I have - how does the XVR react to F88XX? According to this screen in Drive Engineering the reaction is "immediate power off". Does this mean the bleeder resistor is used to actively discharge the DC bus? Or would the bleeder only turn on if the DC bus gets too high, or if commanded to turn on by the power supply control word S-0-1720.0.1 bit 10?

Tomorrow I will have the opportunity to remote connect with the machine and scope the power supply control word, status word, DC bus voltage etc. to get a better idea what is going on, but for now I'm trying to determine what is the expected reaction and if there are any parameters to influence it.

Best regards,

Brian

[StefDu]

Hello Brian,

an automatic discharging of the DC-bus is not possible during F88xx errors. Only the power is switched off.

Can you please share your scope file for evaluation after you created it? The error reaction in the drives is set to NC-reaction?

How is the Bb signal of the power supply provided to the drives? do you write S-0-0240 bit 0 over digital input direct from the power supply or over master communication. Is the bit 15 of S1720.0.2 used as Bb signal?

regards,

Stefan

[bschmidt]

Hello Stefan,

Thank you for the information, this is helpful. S-0-0240 bit 0 of the drive is being controlled over EtherCAT by ctrlX PLC. I will confirm when I get online with the customer, but likely this bit is being dropped immediately when S-0-1720.0.2 bit 15 is dropped on the XVR due to F8812. I suppose in this case we should delay the dropping of S-0-0240 bit 0 to give the drive the chance to follow the NC.

We do have NC error reaction enabled in the drive. However, in my tests the ctrlX Motion app is immediately disabling the drive when it sees the error bit of the drive. I have not been able to find a setting in ctrlX Motion to avoid this.  I made a post about this. But in this case we hope not to see a drive error, only a power supply error. The drive is configured that DC bus undervoltage is a warning (E2026) and not error (F2026). So maybe if we keep S-0-0240 bit 0 = 1 for some seconds after F8812 the drive can still follow the NC to a coordinated stop. 

Best regards,

Brian