Here’s what more than 2,500 business decision-makers around the world say.Download the report
...with the Facility Hero app in hand! Discover how you can optimize your maintenance efforts today.Learn more
Access tailored services, 24/7 self-service and expert help. Anywhere, anytime, any project.Discover now
Everything you need to know about our IoT technology backbone.Learn more
Explore our global offerings or select your country from one of our five regions.Global
Découvrez nos offres globales ou sélectionnez votre pays dans l’une de nos cinq régions.
Goals and Symptoms
I have a customer using devicenet control with vsd's. They are planning to go with ATV58 & Devicenet. The problem they are having with there orignal system is below: The control of the ECL cranes is performed by a combination of a serial communications link, and a single hardwired start/stop command. During normal operation the direction and speed commands are transmitted from the controller to the drive over the serial communication link and written in to specific memory locations in the drive memory. When the communications link fails, no new command information can be written in to the relevant memory address and the settings at the time of the communications failure remain. The hardwired start/stop command controls the overall run or stop operation of the drive and is fail safe, i.e. if power were lost in the circuit for any reason the drive will not receive a run command. If the serial communications link fails when a crane is running in a certain direction, the crane will continue to run as expected. If the crane operator then stops the crane by releasing the joystick to the neutral position the hardwired start/stop command stops the drive. However, if the serial communications link is still not functioning the previous speed and direction information is retained by the drive. If the crane operator then moves the joystick to operate the crane again, the hardwired start/stop command to run is provided to the drive and it will operate in the direction and at the speed it was operating at the time of the communications failure. In two recorded instances this has resulted in the crane moving in an unexpected direction. The fault has been recreated in tests by removing the serial communications cable during operation of the crane. The customer would like to know what is in place with the ATV58 drives to stop a similar event happening if comms are lost and what happens to data written in the drive memory?
Facts and Changes
Causes and Fixes
As I understand when you speak about serial link, it's about Devicenet. Do you agree with me.
Regarding this application there is some programming capacities inside the VSD. It's not possible with only ATV58, the solution is to use the Controller Inside card option for ATV58 but the field bus is Canopen.