
adccommunitymod (AutomationDirect) asked a question.
Created Date: August 14,2015
Created By: dieselvette
**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****
Using an ERDV100 with the GS3. I have the drive being successfully controlled by an analog input with a PID controller. With an on/off bit I the drive stops via GSW AutoRun line. I have a NC/NO output wired to external fault and ext. fault reset, and logic to kill the output when PLC is not in run mode (and/or other conditions). So I 've got the basics figured out, but my issue is what exactly should I monitor to know the drive is getting the signal and what logic to use to deal with a non-responsive issue? For example, if I unplug the RS485 cable the drive continues running in last state. If I unplug the ethernet from ERDV100 the drive continues running in last state. Is there a one-stop parameter in the drive to have it shutdown on comm loss, and then how to monitor that with PLC and what logic to reset the error/shutdown/etc and have it restart. (It's a slow-moving machine, only pumping water no other moving parts, runs unattended. I'd like to be able to ride-through small comm problems and would like to auto-reset/restart any particular drive if there is an error that stops the GS3).
Created Date: August 14,2015
Created by: plcnut
Check P9.03
From the manual:
Transmission Fault Treatment Default Setting: 00
Settings:
00 Display fault and continue operating
01 Display fault and RAMP to stop
02 Display fault and COAST to stop
03 No fault displayed and continue operating
This parameter is used to detect an error and take appropriate action.
Also check P9.04 and 9.05
All is found on page 4-74 of the manual.
Created Date: August 17,2015
Created by: dieselvette
Thanks for the reply.
Setting the parameters in this way does stop the drive on comm fault, which is desired operation.
But then I need to re-start the drive upon restoring comm, this means the PLC needs to know it lost comm, and then know when comm is restored (or keep re-trying?) and then re-start the drive. I suppose I could do this in the logic by monitoring GSR and/or GSW timeout and/or error......and when there is one, wait until it goes away then attempt to restart the drive, but I'm wondering if there's a textbook method or simpler way?
Created Date: August 18,2015
Created by: plcnut
If you are reading the drives status bits (which you should be doing in this type of app), then you can compare the status of the drive to what you have commanded the drive, and if they are not the same, then command a re-start.
Created Date: August 18,2015
Created by: dieselvette
Thanks, I finally found page 5-11 in the manual shows what the status monitor addresses really mean.
P21.00 I could monitor for "anything but 00 " and if error code then shutdown process & prompt operator to address drive issue.
P21.01 we can monitor at bit-level, only the first 3 bits will really matter to me for op. verification. Will have to work out how to parse & display on HMI or use in ladder, etc.
If you are reading the drives status bits (which you should be doing in this type of app)
You are correct, seems like it would be easy to have these further steps as part of the GSR function or a different instruction, if so commonly used for monitoring.
There's also this thread http://forum.automationdirect.com/showthread.php?t=14601 which clued me in a little too.
Created Date: August 14,2015
Created by: dieselvette
Using an ERDV100 with the GS3.
I have the drive being successfully controlled by an analog input with a PID controller. With an on/off bit I the drive stops via GSW AutoRun line.
I have a NC/NO output wired to external fault and ext. fault reset, and logic to kill the output when PLC is not in run mode (and/or other conditions).
So I 've got the basics figured out, but my issue is what exactly should I monitor to know the drive is getting the signal and what logic to use to deal with a non-responsive issue? For example, if I unplug the RS485 cable the drive continues running in last state. If I unplug the ethernet from ERDV100 the drive continues running in last state. Is there a one-stop parameter in the drive to have it shutdown on comm loss, and then how to monitor that with PLC and what logic to reset the error/shutdown/etc and have it restart.
(It's a slow-moving machine, only pumping water no other moving parts, runs unattended. I'd like to be able to ride-through small comm problems and would like to auto-reset/restart any particular drive if there is an error that stops the GS3).