Drive Parameter Loading with the Drive Connect App

I am investigating a feature involving a ctrlx core updating the parameters of a drive, given the drive has been replaced. I know this is to be done by the Drive connect app, but I'm struggling to find how exactly. I've searched through the forums and wasn't successful in finding someone using the drive connect app like this.

My first thought was to pull the data of the serial numbers of the connected drives, and if that didn't match the last time the core had been booted up to write the parameters stored within the drive connect apps data locations to the drives by their ethercat position. I was able to load firmware and drive parameters to the drive connect app, but have been unable to querry what drives are actually connected. 

Is there an example or guide somewhere on how to do this? The drive connect apps manual explains how to do it all manually but not how to do it automatically, as it happening without much human intervention is best. 

Best reply by Nick

I'm sorry to have missed closing this out. The ultimate solution to the problem in our case was in the CtrlX IO engineering. 

There is an item called a "Startup Parameters" and activates everytime the Ethercat loop is attempts to go to OP state. You do need to feed in every parameter that you would like different from default, but this is a good solution to the problem of replacing drives without the parameter file and engineering computer. 

View original
8 replies