All,
I encountered something very strange last week when I was on-site at our customer's facility as I was commissioning the system. There was 2 issues that I can't wrap my head around:
1.) Everytime I upload the new VIM configurations and export the FHX file to be imported into the controller, it would stop the E300s and other devices connected to the VIM. I would have to download the new configure, then stop the device and start it again. This poses a serious problem if the motor is critical to the process. Anyway setting to have only the updated devices stop and keep current actives devices run at current state?
2.) When there is a communication loss between the VIM and E300, the DeltaV HMI dynamo shows the motors as Running (in terms of colors) but in reality, the physical E300 are not running if communication is lost (say someone pulled the RJ45). In other words, I have the RUN status feeding back into a DC1 block and the DeltaV logic holds the value of the motor as running. Is there some type of feedback that will tell the DeltaV system what is the current state of E300 when there is a loss of communication?
We have a S-Series controller with VIM2 card. All our motors where either PF 755 or E300 connected via EtherNet/IP.
Andre Dicaire
In reply to Andre Dicaire:
In reply to JPC1080: