FAQ
Understanding Enervista PMCS Architecture
PMCS 6.15 is designed to communicate with GE Modbus devices. It is comprised of the following components.
Hardware
Modbus devices – Typically GE Multilin devices supported Modbus RTU and/or Modbus TCP/IP (natively or with a Multinet gateway)
Communication network – Either a twisted pair
PC – Windows based x86 PC
Software
Operating system – Windows2000 SP4, XP SP2 or Windows 2003 Server R2
Enervista PMCS 6.15 software – From the users prespective PMCS appears to be a single software unit but it is actually a suite of software running together.
Two Modbus Server exe’s – Polls for Modbus data from appropriate device. The servers will not poll for data on their own. A client (PMCS, wfserver, eventserver, etc.) must request data.
GE32MODB.exe – The Modbus RTU server. This server is used whenever the PC is connected directly to a Modbus RTU communication network via the PC’s COM ports. Most typically via a RS232/485 converter
GE32MTCP.exe – The Modbus TCP/IP server. This server is used when communicating to devices supporting a direct Ethernet interface (UR’s, etc.) or Modbus RTU devices using a GE Multinet converter.
EventServer.exe – Polls and retrieves the device generated eventlog. The event is placed in a Sql database For a device to be polled it must support an eventlog function and also have the poll enabled in PMCS (see ‘device setup’ section)
Eventlog.exe – Viewer for events collected by the Eventserver.exe
Wfserver- Polls and retrieves waveforms generated by devices. For a device to be polled it must support a waveform function and also have the poll enabled in PMCS (see ‘device setup’ section)
WFC.exe – Waveform Client application to view the waveforms retrieved in CSV format by WFServer.exe. It has features to Trigger and Upload the waveforms from supported devices.
WaveformViewer.exe – Waveform Viewer application to view the waveforms retrieved in COMTRADE format by WFServer.exe. It has features like viewing Phasors and Harmonics and
19
