Overview
This section covers aspects of configuring ACM to communicate to Prosoft Enhanced Modules, MVI56E or MVI69E.
Security Options
As of release 7.1.268, ACM does not support the security feature of the enhanced Prosoft module in which an operator ID and password is are supplied to login log in to the module. Even if you have not configured additional operators or passwords have not been configured on the device using EAFC Manager, the default log in still requires a password. This feature must be disabled on the Network Server port or serial port that is used for ACM communication.
If the feature is not disabled, any time ACM sends a Modbus message to the module, it will respond with a Modbus exception log entry of “Illegal Data Value”. This is something to look for if communications do not work with a newly installed module.
To disable the feature, start the EAFC Manager software and set the Communications\Local Port Settings to connect to the module. After connected, select the Communications\Login Module and log in with an Administrator operator account.
Next select the On-Line\Operator Database, then click the button to Connect As Administrator.
...
Operator 3 is the Default Administrator.
Select the Authorization Defaults tab then set the Default Operator Number of the port ACM will use to ‘3’. In this example, ACM will connect via Network Server 1.
Next click on the Privilege Waivers box for the same port in order to disable the password requirement.
Enable Option Zero, Password Not Required. Click OK to save.
Back on the Operator Database screen click Apply, then Done. That completes the Security set up for the module. This must be done for every enhanced module in your system that ACM will communicate with.
ACM Configuration
The remainder of this document will assume you are familiar assumes familiarity with the ACM configuration process and the objects used to define devices, meter, archives, etc. It will step through the process of creating a Prosoft device with one orifice gas meter with hourly EFM collection. The process to create additional meters, or a different type of meter, is the same, only the registers addresses will differ.
Info | ||
---|---|---|
| ||
If |
...
ACM will be |
...
used to do gas analysis downloads to an Enhanced Prosoft module, first read the Gas Analysis Writes and |
...
FLOWCAL SCADA Request Service in order to properly know how to name and configure |
...
ACM meter objects. |
Next, create a Modbus Prosoft device in your the ACM project and correctly configure the Connection and Device properties.
Info | ||
---|---|---|
| ||
When creating a Prosoft device, there is no differentiation between Enhanced or older non- |
...
Enhanced modules as the type is determined automatically at |
...
run-time. |
On the Device tab, set the Register Set property to "Prosoft Enhanced Register Set". If connecting to the Prosoft module via a network port, enable the Modbus/TCP property.
...
For Meter1, enable the Collect Hourly property, then set the Hourly Record Size and the Extended File Size to match the settings for the meter in the EAFC Manager. Note that if your
Info | ||
---|---|---|
| ||
If the actual record size is not in the drop down list, select the next higher value. Example: If |
...
the record has 34 bytes of total data, select 40 for the record size. |
Next, create a Meter object for Meter1.
Info | ||
---|---|---|
| ||
You will need to create a separate meter object for every meter Each meter run on the device requires a separate meter object in ACM. |
Meter Object Configuration
On the Meter tab of the Meter object, set the properties as required by your the project. Next, enable the Advanced Configuration property, then create a new Meter Configuration object.
Meter Configuration objects objects can be reused for multiple Modbus Prosoft devices, so give your the object a descriptive name, such as including the meter/run number and the meter type. In this example, we will create an Orifice configuration is created for Meter1 so and the name chosen is “MVI56E Meter 1 Orifice Configuration”. For any Modbus Prosoft device you create created that has an orifice meter for Run 1, you can reuse select this Meter Configuration object for it.
Meter Configuration Object Configuration
The The Meter Configuration object is used to define the registers from which to read EFM configuration data during an EFM upload. These are the values that will be mapped to the configuration section of your the EFM report. On the Configuration tab of the object, click the Edit Configuration button to show the configuration grid.
For each property that you want to be included in your EFM report, check select the Enabled box on the row of the property. Next, configure the other options on the row as needed. You can use EAFC Manager’s Modbus Dictionary can be used to determine the register address to use if reading the value from the field module. If the property is in one register, enter the Modbus register address. If the value is floating point and in two consecutive registers, append the letter ‘F’ to the address, as shown in the example below.
Once you have the Meter Configuration object is complete for Meter1, you can easily create the objects for the other meter runs can be easily created by copying the Meter Configuration object, renaming it, then changing the addresses in the Advanced Configuration grid. On the Prosoft module, each subsequent Meter’s configuration registers are offset from the prior previous meter by a value of 1000, i.e., all of Meter1’s configuration registers are in the 8000 range, Meter2 in the 9000 range, Meter3 in the 10000 range, etc.
An example object is attached to this documentExample Export of this object.
Archive Object
On the Meter Runs tab of the device object, create a new Archive Object for the Hourly Archive property. Set the new Archive Object to be Periodic with a period of 60.
...
On the Field Configuration tab of the Archive Field object, click the Edit Configuration button. For each field defined in the archive in EAFC Manager, you will need to add the corresponding field record in this object. Each field in the archive must be included even if the field will not be used in reporting or if the field is an empty slot, i.e. <available>. The Position property must be correct and match the order in EAFC Manager.
An example is attached to this documentExample Export of this object.
Combining Totalizer and Residue
Since the Prosoft has separate totalizer and residue fields for accumulators, ACM must be configured correctly to indicate these fields should be combined into one value. This is as simple as setting the Field Identifier property for both fields to be the same ID in the Archive Field Configuration Object. As show below, using the Tabular View, for Volume, both the totalizer field and the residue field have their Field Identifiers set to "Volume Record – Volume". Also note the data types of the two fields. The same configuration applies to the other accumulator fields.
Info | ||
---|---|---|
| ||
The Totalizer field is a 32-bit integer and the Residue is a 32-bit floating point. |
Info | ||
---|---|---|
| ||
If a scale string is configured to be used , when defining the Totalizer field definition in ACM, the same scale string must be used on the Residue field. |
...
The ACM Prosoft module supports downloading gas analysis values to a Prosoft enhanced module. This is done through the ACM GCRequest manager as described in other documents. Obtaining values from Flowcal is also supportedFor guidance on using ACM to write gas analysis data to the module, refer to the Gas Analysis Writes section of the user guide.
The following GC values are supported for download:
...