Startup Config can handle a various range of user setups. Either the user uploads a meterlist to the 900-unit or initiates a search for meters via the web interface. Any of PiiGAB 900-units S/T, SW/TW are supported and if the user works on a unit without internal wireless card, the user has to connect a wireless node to receive wireless meters. The wireless nodes supported so far are PiiGAB 900SW/TW and Elvaco CMi5110.
It’s possible to upload a meterlist with only ID numbers where the user must then verify the meters. Verification happens by a REQ_UD2 request, reading meters from wireless nodes, or from the internal wireless card.
All verified meters can be viewed in real-time and their data can be sent to overriding system. Startup config handles wired and wireless M-Bus meters, Modbus and Han-meters meters converted to M-Bus, and wireless nodes.
The template file created in Startup Config can be used in other facilities with the same setup and same composition of meters meaning it’s possible to make one template file for multiple identical facilities.
All search functions shut down MBusHub and search directly on the wired M-Bus loop therefore no slave ports are available during a search. All meters not connected through the M-Bus loop are excluded as well. Devices that will be found are: 1. Wired M-Bus meters 2. Wireless Nodes connected to the M-Bus loop. 3. Wireless meters that are detected by the wireless nodes.
The search function should ideally only find wired meters.
Status | Description |
---|---|
![]() |
The meter has enough information for the configuration file and last reading by the user was successful. Wireless meter has a duration lower then one day (1440 minutes) |
![]() |
The meter has enough information for the configuration file but the last attempt by user to perform a read failed. Wireless meters has a duration higher then one day (1440 minutes) |
![]() |
The meter is not online and have not provided enough data for the configuration file |
This is a file containing all the different meter types in the facility. Each meter will get a template name. For example a Lansen meter with secondary address: 00015642.3033.02.2A will get the following template name: LAS_02_2A. It is a composition of each individual meters columns in the following way: LAS is manufacturer in text column[4] 02 is Medium column[2] 2A is Version column[3]
The template name is an important part of the template file. It’s the template name which connects each individual meter to the correct template in myconfig.csv. If this connection can’t be done then the meter cannot be read out in Quickpost.
Field | Description |
---|---|
Format | The format Quickpost will use to send the meter data. |
Time format | Default yyyy-mm-ddTHH:MM:SS (24). |
Tag type | Default Record (8) |
Time stamp | For wired meters “Quickpost”. For wireless meters “Telegram”. |
Time record no | For wireless meters recieved through a PiiGAB unit this value can be set to 4. |
Read period | Default empty. |
Read offset | Default empty. |
For further information see documentation for Quickpost.
This function DO NOT work for facilities with wireless meters received through units which are not PiiGAB. In those facilities you have to manually add each metertype to the template.csv file. All metertypes in your meterlist will be added automatically.
To add a metertype to the template.csv press the meters Id-number in the list. Choose which Mbus-objects you want to report by pressing the ON/OFF field for each Mbus-object. If you only want one object it is faster to first uncheck the box “Report All” and check the box for the Mbus-object you want to report.
If you want to edit the Vif/Tag name for the object you can do this by pressing the Edit button for the object in the Edit column. A pop-up modal will appear where you can type in the new name. Characters that are not allowed are the following:
Not allowed Vif/Tag characters |
---|
# , ; < > |
Press the button “Add metertype” to add the metertype template to template.csv.
This is the configuration file to use when reading out meter data in Quickpost. When creating the configuration file Quickpost will be restarted with this file as configuration file.
MBusHub will restart with this file in the masterport when creating myconfig.csv and when Auto-create myconfig.csv. This file make it possible to both read out MBus objects in Quickpost and to convert MBus objects to Modbus registers through a MBusHub slaveport.
If you read out MBus meters over Modbus you need to place this file in the MBusHub slaveport which are making the readout. This file will map the modbus registers to the correct MBus objects.
The default device name format is <ID><MFCT><VER><MED>. This should be used if there are no other specific demands on the output file.
If you use <Description> as device name it is important you do not use åäö in the description. You have to use ASCII letters only. If you readout the device and send with Quickpost the device name will be converted from UTF-8 to ASCII. This means the device name will change if you do not only use ASCII letters. All meter with a description in the decription field will get this as device name. The meters without description will get PiiGAB default device name <ID><MFCT><VER><MED>.
Default channel name in the “myconfig.csv” file is the 900-units serial number. Channel name used in the template.csv file is ‘channel’.
This will create the configuration files which is used in the MBusHub masterport and in Quickpost to enable sending meter data with Quickpost.
If you are NOT using Mbus2Modbus conversion you do not need to care about this button. Just use the regular create myconfig.csv button instead.
Here the meters which are not present in an earlier version of masterport_Mbus2Modbus.csv will be appended in the end of the masterport_Mbus2Modbus.csv file. The previously added modbus registers will not be affected by new meters.
The status will only change if the user press any of the buttons “Verify meterlist” or “Read meters”. When the user press the meters ID-number to read out the real-time values, the status will not change.
The functions mbus_secondary_search and mbus_primary_search set the status to “Green” if a response is received from a REQ_UD2 request to the wired meter and the wireless node.
The make_node_meterlist set the status “Yellow” to wireless meters if the meters id-number is found in /tmp/meterlist_wireless.txt and the duration is higher then one day. If the duration is lower the meter gets the status “Green”.
For wired meters the function verify_meterlist give the status “Green” if the meter recieve a respons from a REQ_UD2 request. The REQ_UD2 request will only be asked to a meter with either not enough information in the meter fields or the parameter verifyMeter is set to “True”.
Status | Value | Description |
---|---|---|
Red | 0 | No response or not enough information to add the meter to the template thus not all of the required fields have been filled. |
Yellow | 10 | There’s enough information to construct a template (wireless meters must have a fabrication number). If a wired meter have the status “Green”, and recieves a REQ_UD2 but give no response, when user press “Read meters”, the status will go from “Green” to “Yellow”. |
Green | 20 | For wired meters all required fields are present and can answer a REQ_UD2 request. For wireless meters all fields are present, can answer to a REQ_UD2 request, and have a duration lower then one day. If a meter in meterlist_wireless.txt to not contain all the fields. Id,Mfct,Ver,Med,Fabrication,Metertype, then it is an error. |
Type | Description |
---|---|
integer | A non-negative whole number of the range |
hexadecimal | A non-negative number in base 16 consisting of 0-9 and a-f representing ranges 0-9 and 10-15 respectively. |
text | Ascii is preferable, ISO-8859-1 is ok. All ISO-8859 should work ok. UTF-8 needs more testing. |
verification set | Integers: Red not verified, Yellow enough info for template, Green REQ_UD2 response |
Field | Type |
---|---|
ID | Identification number in BCD form (see 1, pp. 34-35) |
Manufacturer | Hexadecimal |
Version | Hexadecimal |
Medium | Hexadecimal (see 1, pp. 76 for the list of possible values) |
Manufacturer (text) | Three character text string representing the manufacturer |
Fabrication number | Integer |
Primary address | Integer between 0 and 250 inclusive |
Status | Integers: Red,Yellow,Green |
Meter type | set of types as a string |
Wireless key | 32 byte long alpha/numeric value |
Description | Max 50 characters long ASCII string. No whitespaces allowed. Commonly used Latin-1 characters will be converted to ASCII. |
Timestamp | Timestamp from when the meter was last readout. To update the timestamp you need to press the button “Read all meters”. |
Meter type | Description |
---|---|
R | Wireless |
W | Wired |
N | Wireless Node |
H | Hanbus meter |
M | Modbus meter |