Create Configurations
To create a new configuration, follow these steps:
-
Log in to Customer Portal.
-
Switch to Products → Collector Mobile Client → Configuration.
-
Click Create configuration.
-
Enter a name for the configuration and define the configuration specification.
For details, see Configuration Specification below. -
Click Create configuration.
After creating an organization, you can find a sample configuration file that you can use as a reference for creating your own configurations.
Configuration Structure
The configuration files use the INI format with sections and key-value pairs.
-
Add comments by using the hash (
#) sign. -
Spaces at the end of lines are ignored.
-
Section names must always be uppercase.
-
Key names must always be lowercase.
-
Boolean values accept
1,Y,TRUE, andYESasTRUE.
The CMC configuration contains four sections that are described in detail below.
Section GLOBAL
This section specifies the settings and parameters that apply to the entire application.
The exact contents may vary depending on the application requirements and functionality.
The entries may include data folder paths, time synchronization tolerance, default load profile readout information, license key, REST communication settings, and so on.
|
Key |
Value |
|---|---|
|
|
Specifies the clock difference threshold in seconds after which the time synchronization action is not performed and the action ends with an error. The number must be positive or Example: |
|
|
Specifies the clock difference threshold in seconds before which the time synchronization action is not performed and the clocks are considered synchronized. The number must be positive or Example: |
|
|
Specifies whether time sync force option is enabled by default so that time synchronization thresholds are ignored and time is set. Example: Default: |
|
|
Specifies the comma-separated default selection of registers for
Example: |
|
|
Specifies the comma-separated profile numbers that are selected in the user interface by default for new manual work orders. The numbers must be Example: |
|
|
Specifies the default number of days before the current time that will be read. The number of days is used in new manual work orders for Example: |
|
|
Specifies whether to use a pre-shared key to decrypt encrypted passwords. To activate the pre-shared key, set the value to |
|
|
Specifies the name of the file with the pre-shared key. The file is in the |
|
|
Specifies the validity period in days for driver-cached data (association objects). The value must be Example: |
|
|
Specifies the minimum valid voltage level in volts for the The value is compared to the instantaneous voltage levels. Example: |
|
|
Specifies the maximum valid voltage level in volts for the The value is compared to the instantaneous voltage levels. Example: |
|
|
Specifies the maximum absolute value considered to be 0 (zero) in amperes for the The value is compared to the instantaneous current levels. Example: |
|
|
Specifies the endpoint where the application can connect to an external server for automatic data synchronization. The string can be prefixed with Example: |
|
|
Specifies the name of the file (without the path) to the client authorization certificate in the The certificate is used when the endpoint specified in The file is located upon the application startup and is then stored in the secure Android storage. The file is automatically deleted after loading to the application. |
|
|
Specifies the encrypted password for loading the certificate specified in the |
|
|
Specifies the location of the authorization certificate for connection to Collector Mobile Server. The value can be set to:
The value selected by the user is saved and the application continues to use this user-selected certificate as long as the certificate is valid. If set to |
|
|
Specifies whether synchronization with cybros labs Customer Portal or similar CMS system. Default: |
|
|
Specifies the minimum number of hours that work orders are held in the device after data synchronization before being deleted. |
|
|
Specifies whether to display a button in the user interface to test disconnectors. To hide the button, set the value to |
|
|
Specifies the interval of the sound signal in the Default: |
Section AUTH
This section contains a list of individual users, including passwords, allowed actions, and permission groups.
The default user that will be used to log in to Collector Mobile Client has the following format:
0=n<username>|p<password>|l<userPermissionLevel>
You can add additional users following the same format.
The <userPermissionLevel> must be a positive integer number and specifies the following parameters:
-
p<userPermissionLevel>– A comma-separated list of preset actions (see below). -
r<userPermissionLevel>– A read-only flag that specifies whether user can manage work orders. -
a<userPermissionLevel>– An access control list with action-to access-level mapping in the following format:action@L<accesslevels>. Theaccesslevelsare meter specific permissions. For details, seeSection: <DRIVER_NAME>below.
The actions are:
-
MRT_CHECK- Meter check -
UPDATE_PASSWORD- Update password -
MDM_INIT- Modem initialization -
TOU_LOAD- TOU tariff table load -
DISPLAY_CFG- Display configuration -
LMTR_SET- Limiter settings -
LP_RDT- Load profile read -
DLP_RDT- Daily load profile read -
EVL_RDT- Event log read -
BATT_RESET- Battery reset -
BILLING_RESET- Billing reset -
ALARM_RST- Alarm reset -
SYNC_TIME- Time synchronization -
BV_RDT- Billing values read -
RELAY_SET- Relay control
The accesslevels are meter specific permissions. For details, see Section: <DRIVER_NAME> below.
Example:
0=nAdmin|pSecretPass|l1
1=nTechnician|pTechPass|l2
p1=BV_RDT,LP_RDT,EVL_RDT
a1=MRT_CHECK@L2,EVL_RDT@L1,TOU_LOAD@L2,BV_RDT@L1,LP_RDT@L1
r1=n
p2=BV_RDT
a2=MRT_CHECK@L1,BV_RDT@L1
r2=y
Section <DRIVER_NAME>
This section specifies the settings and parameters for individual driver types.
While some settings are common across all drivers, others are specific to individual driver types.
In the subsections below, the specific settings are introduced by the driver type.
Common Driver Settings
|
Key |
Value |
|---|---|
|
|
Specifies the password values.
You can set multiple passwords and use them in various combinations for different operations. Example:
|
|
|
Specifies the encoding of the The available encoding options are: Plain
Hex
aes/gcm/noppading
aes/cbc/pkcs5padding
|
|
|
Specifies the access levels that are used by the driver for the given user level. Example:
|
|
|
Specifies a semicolon-separated list of DLMS definitions to be read. |
|
|
Specifies a semicolon-separated list of DLMS definitions to be read when |
ACE_SL7000
|
Key |
Value |
|---|---|
|
|
Specifies the DLMS security mechanism that is used for authentication. Available options are:
Default: |
ADDGRUP_NP7X
|
Key |
Value |
|---|---|
|
|
Specifies the read timeout for the load profile readout in seconds. Default: |
|
|
Specifies the maximum number of days allowed to read before today. Default: |
LGZ_E350
|
Key |
Value |
|---|---|
|
|
Specifies the |
LGZ_E360
|
Key |
Value |
|---|---|
|
|
Specifies the DLMS security mechanism that is used for authentication. Available options are:
Default: |
|
|
Specifies keys for relay settings actions. The values are the script numbers according to the parametrization of the meters. Example:
|
|
|
Specifies the modem Default: |
|
|
Specifies the valid response message for the modem Default: |
|
|
Specifies the modem Default: |
|
|
Specifies the modem Default: |
|
|
Specifies the valid response message for the modem Default: |
|
|
Specifies the modem Default: |
LGZ_E450
|
Key |
Value |
|---|---|
|
|
Specifies the DLMS security mechanism that is used for authentication. Available options are:
Default: |
|
|
Specifies keys for relay settings actions. The values are the script numbers according to the parametrization of the meters. Example:
|
LGZ_E550
|
Key |
Value |
|---|---|
|
|
Specifies the DLMS security mechanism that is used for authentication. Available options are:
Default: |
LGZ_E570
|
Key |
Value |
|---|---|
|
|
Specifies the DLMS security mechanism that is used for authentication. Available options are:
Default: |
LG_E650
|
Key |
Value |
|---|---|
|
|
Specifies the DLMS security mechanism that is used for authentication. Available options are:
Default: |
|
|
Specifies the meter-specific input that sets the relay identified by Examples:
|
|
|
Specifies the meter-specific input that sets/switches the relay identified by Examples:
|
|
|
Specifies the meter-specific input that sets/switches the relay identified by Examples:
|
|
|
Specifies the number of minutes to read before the required This is caused by broken firmware that sometimes does not return desired data if the time Default: |
LGZ_E850
|
Key |
Value |
|---|---|
|
|
Specifies the DLMS security mechanism that is used for authentication. Available options are:
Default: |
|
|
Specifies the number of minutes to read before the required This is caused by broken firmware that sometimes does not return desired data if the time Default: |
|
|
Enables |
AEM_ENERLUX
|
Key |
Value |
|---|---|
|
|
Specifies the |
|
|
Specifies the read timeout for the load profile readout in seconds. Default: |
|
|
Specifies the maximum number of days allowed to read before today. Default: |
IEC61107
|
Key |
Value |
|---|---|
|
|
Specifies the time parsing format in the |
|
|
Specifies the date parsing format in the |
|
|
Specifies the ordered list of OBIS codes, separated by semicolons, that are checked in the specified order for the serial number of the meter. The Default: |
|
|
Specifies the OBIS code of the register that contains the current time value. Default: |
|
|
Specifies the OBIS code of the register that contains the current date value. Default: |
|
|
Specifies whether to ignore time in the profile request. By default, drivers read the To disable this behavior, set the value to Default: |
|
|
Specifies the request length for the Default: |
|
|
Specifies the |
EMH_LZQJ
|
Key |
Value |
|---|---|
|
|
Specifies the |
|
|
Specifies the |
ZPA_AMX75
|
Key |
Value |
|---|---|
|
|
Specifies the DLMS security mechanism that is used for authentication. Available options are:
Default: |
ZPA_ZEX16
|
Key |
Value |
|---|---|
|
|
Specifies the DLMS security mechanism that is used for authentication. Available options are:
Default: |
|
|
Specifies the OBIS code for the daily profile object in the meter. It must be in the full format, for example, If the code is not defined, the driver tries to find a load profile with period value Default: N/A |
METERCONTROL_ST402D
|
Key |
Value |
|---|---|
|
|
Specifies keys for relay settings actions. The values are the OBIS codes with action numbers according to the parametrization of the meters. Example:
|
|
|
Specifies the DLMS security mechanism that is used for authentication. Available options are:
Default: |
|
|
Enables |
METCOM_MCS301
|
Key |
Value |
|---|---|
|
|
Specifies the DLMS security mechanism that is used for authentication. Available options are:
Default: |
|
|
Specifies the authentication key if the security mechanism is |
|
|
Specifies the encryption key, if the security mechanism is |
|
|
Specifies a JSON-formatted object where keys represent OBIS codes and values contain the options to be set. For security reasons, only OBIS codes related to relay configuration are permitted. Any other OBIS codes are ignored. Example:
|
Section PASSWORD_SECTION_x
This section specifies default passwords that are used when the CMC application is accessed via API.
Each section name is in the format PASSWORD_SECTION_x, where x is any alphanumeric string of characters.
This section is referenced when the meter_password_section key in the API call contains the same x value.