FAQ

No, the Converter is powered by the electricity meter and should never be connected to the M-bus loop without being energised via the Han P1 connector on the Converter.

Check the manual of your electricity meter the order in which the Obis codes come from the electricity meter. PiiGAB HAN-P1 Converter translates the Obis codes line by line to M-Bus registers. This means that the registers arrive in the same order as the electricity meter sends them.

Check that it is lit at the HAN-P1 port that you have connected to the electricity meter. If a green LED is not lit, the PiiGAB HAN-P1 Converter is not powered and will therefore not work on the loop.

No. It is not possible to know what information will be presented by the converter until it is in a electricity meter. All electricity meters send out different information, the PiiGAB HAN-P1 Converter just takes in all values and translates them to M-Bus.

Try to manually type in the not found secondary address so that the master does a search on that specific address. Many M-Bus masters search differently and can sometimes have problems with two secondary addresses that are right next to each other.

Check if the LED at the HAN-P1 port connected to the electricity meter is flashing. If there is no flashing at least every 10 seconds, there is no information from the electricity meter to the converter.

Vanliga orsaker: 

• Adresskonflikter 

• Trasig mätare 

• M-Bus-spänningen är för låg (överbelastning) 

• Kortslutning av M-Bus slingan 

Håll in reset-knappen i ca 10 sekunder tills LED-lamporna indikerar omstart. Enheten återgår till ursprungs-IP och konfiguration. 

PiiGAB 820 stödjer upp till 250 M-Bus-slavar, beroende på busstopologi och total kabellängd. 

1. Logga in i webbgränssnittet 

2. Gå till Maintanence -> Firmware Upgrade 

3. Ladda upp filen och starta uppgraderingen 

Kontrollera: 

1. IP-adress och nätverksinställningar (Både dator och specificerad IP på din PiiGAB 820 

2. LED-status (Power/Link) 

3. Kablar och switchar 

4. Håll en telefon på framsidan av PiiGAB 820 mellan PiiGAB-logotypen och ethernet-porten. En URL kommer dyka upp på telefonen där du kan utläsa enhetens IP-adress i texten. OBS! IP-adressen visas i webbadressfältet.

Ja. PiiGAB 820 är helt kompatibel med M-Bus Wizard för felsökning, test och konfiguration. Se till att du har uppdaterat PiiGAB Wizard till version 3.3.2. Du kan ladda ner den här

Ja, PiiGAB 820 fungerar lika bra i slutna lokala nätverk som i större företagsnät. 

Ja, PiiGAB 820 stödjer både primär och sekundär adressering. 

Ja, PiiGAB 820 stöder både statisk IP och dynamisk IP via DHCP. 

PiiGAB 820 stöder: 

• M-Bus TCP/UDP 

• M-Bus Slavinterface 

Yes. The license can be changed without replacing the gateway.

Some meters do not handle SND_NKE together with REQ_UD2. Untick the SND_NKE option and the meters should respond.

Check that the supply voltage (24VAC / DC) to the converter is fully isolated from other products in your control panel. Also check the ground on the primary and secondary sides of the protection transformer so that they are not interconnected.

Check that the supply voltage (24VAC / DC) to the converter is fully isolated from other products in your control panel. Also check the ground on the primary and secondary sides of the protection transformer so that they are not interconnected.

To troubleshoot M-Bus meters connected to an PiiGAB M-Bus 810 there are a couple of things to verify.

Here is a list of good tools to use during troubleshooting:

• PiiGAB M-Bus Wizard
• Getting started PiiGAB M-Bus 810
• MicroMaster USB
• PiiGAB's general M-Bus documentation

IP-address
What IP-address is the gateway using? To have network communication with the gateway you need to setup your computer in the same network as the gateway. If there is an IT section please contact them to receive an IP-address for your computer. With the PiiGAB M-Bus Setup Wizard you can search gateways on the network or ping the gateway’s IP-address to verify if the network communication works.
In the PiiGAB M-Bus Wizard, you can search for converters on the network or "ping" the IP address of the converter to verify that the network connector is working.

f it’s not possible to receive the gateway’s IP-address then you need to setup a new IP-address.
Please see the FAQ on how to do this.

Harbour
What port is the gateway set to in order for the the M-Bus client to read the M-Bus meters? If you have network connection with the gateway you can find out the port with the PiiGAB M-Bus Setup Wizard.

Start the PiiGAB M-Bus Wizard -> Change converter parameters -> Connect via network.

Protocol
What protocol is the gateway set to in order for the the M-Bus client to read the M-Bus meters? If you have network connection with the gateway you can find out the protocol with the PiiGAB M-Bus Setup Wizard.

Start the PiiGAB M-Bus Wizard -> Change converter parameters -> Connect via network.

Note: If the gateway uses TCP you might not be able to connect to the gateway with the PiiGAB M-Bus Setup Wizard to read the M-Bus meters. This is due to that another client is connected to the port that the gateway is using. Change the port, change to UDP or turn off the client.

Communication speed
What communication speed is the gateway set to in order for the the M-Bus client to read the M-Bus meters?If you have network connection with the gateway you can find out the communication speed with the PiiGAB M-Bus Setup Wizard.

Start the PiiGAB M-Bus Wizard -> Change converter parameters -> Connect via network.

Note: If the gateway is set to 300 baud the communication speed is very slow. Remember to change the timeout in the PiiGAB M-Bus Setup Wizard to handle the long response time.

M-Bus meters
Is there any documentation of what M-Bus meters that are connected to the gateway? What addresses does the M-Bus meters use? (primary or secondary addresses).

If there is documentation of the meters then you can simple check each meter one by one with the PiiGAB M-Bus Setup Wizard. It’s also possible to read the search function in the PiiGAB M-Bus Setup Wizard.

If there is no documentation of the meters then you can use the search function in the PiiGAB M-Bus Setup Wizard. If the the result of the search function is incomplete then you have to find each meter one by one on the site and test them individually by it’s M-Bus address (primary or secondary address).

A M-Bus meter not responding
If an M-bus meter is not responding then you have to test the meter individually. If possible disconnect all other meters and test only that specific meter. Try with primary address 254 or the meter’s own primary or secondary address.

If it’s not possible to disconnect all meters then you can test the specific meter with a MicroMaster USB.

On the menu in the gateway's interface, click on "Administrations" under which there is then the submenu "Basic settings". Scroll down a bit on the page and you will get to "Webserver Setting", see screenshot.

If nothing else has been specified in the order, the default configurations are set for DHCP.

All configurations are made in the gateway’s web interface.

At least one can be specified. If a meter does not respond after a re-query, an additional re-query is unlikely to help.

The following list will explain how to install a license in the PiiGAB M-Bus 900/900S. These steps will also show the current license of a PiiGAB M-Bus 900/900S.

1. Start the gateway’s web interface in any web browser.
2. Go to the Administrations page.
3. Under the Basic Settings tab you will find the section License. This shows the licence of the converter (SW 2.5.0 or higher)
4. Paste the license into the field Update licence.
5. Press the button Update.
6. Wait for the license to be installed.

The following list will explain how to install software in the PiiGAB M-Bus 900 V2 and PiiGAB M-Bus 900S. These steps are either used to install a new software or update an existing.

1. Download the software as a ZIP file, please click here.
2. Unzip the file to gain access to the tgz-file.
3. Place the tgz-file somewhere on the computer. Don’t open the tgz-file.
4. Start the web interface for the gateway in any browser.
5. Go to the Administration page.
6. Find the section Update Software.
7. Press the Browse… button.
8. Browse to and select the tgz-file.
9. Press the button Install.
10. Wait until the installation has finished.

Note: If QuickPost, Modbus2MBus or Wireless M-Bus is not shown in the web browser, please press CTRL + F5.

If the communication does not work, check that no other process locks that port.

Check that Modbus2Mbus or any slave port is not set to RS485.

Also enable RS-485 Failsafe in MBushub for more stable collection.

Only PiiGAB M-Bus 900 V2.XX.XX.XXX or later versions support the function where the IP address can be changed with the PiiGAB M-Bus Wizard.

Both PiiGAB M-Bus 900 V2 and PiiGAB M-Bus 900S can change their IP address with the PiiGAB M-Bus Wizard.

Keep in mind that the netmask and default gateway will not be set. These need to be set in the converter's web interface. Please read it under the FAQ section "Example of initial contact"

Yes you can download the new update even if you are using http, but you will need to change the configuration so that http is the default before updating, however we recommend that you use HTTPS instead for security reasons. Valid from version 2.6.2

Here's how to change from HTTP to HTTPS in the gateway, click here

If you don't know whether you're running HTTP or HTTPS, you can download our script to find out. Download it here

If you are using TCP and the M-Bus Wizard at the same time you cannot make contact with an additional TCP client since the M-Bus Wizard “owns” the TCP handle. Shut down the M-Bus Wizard before starting the second TCP client. The same goes if you are using COM ports.

Quick start Guide to Configure M-Bus to Modbus 

1. Plug all the meters you want to use on the M-bus loop into Mbus Master ports 1-4 on your Gateway. 

2. Search your meters in the web interface using a "Fast Search" in the Startup Config tab 

Your meters should appear in a list under the "Fast Search" button

3. Go to the overview page in Startup Config where the meters should now be visible in the list below.

Add Encryption Keys to the meters if they are Wireless meters

4. Click on "Auto-Create Myconfig files"

The files to be used to read meters are now created

5. Go to MbusHub and the tab "Master port", then select the configuration file for the Master port file as shown below. Save the configuration.

6. Go to Slave Port 1 and select the configuration file as shown below

7. Now you will be able to query against the registry entries described in the CSV file located in the slave ports tab of the web interface

Conversion of Modbus meters to M-Bus is done in the program Modbus2Mbus Config. You can find this for download at https://www.piigab.com/products/mjukvara/

In order to have a simple and trouble-free conversion, it is important to have the meter's manual available.

Create a new project and then add a device per meter.

Set the parameters for Mbus and Modbus communication

Add objects for each measured value to be read out and set the correct Modbus register as well as unit and scaling.

If you have several meters of each type, copy the meter and only change the Slave and M-Bus address.

It is also possible to save these as templates for future projects.

After the project is finished, it is saved and then uploaded to the 900

Read M-Bus meters from external M-Bus master

The following list instructs how to configure a PiiGAB M-Bus 900/900S as an M-Bus slave, i.e. one or two external M-Bus masters can read the M-Bus meter connected to the gateway.

Notice: On PiiGAB M-Bus 900 there can only be one external M-Bus master connected.

1. Start the gateway’s web interface in any web browser.
2. Go to the Configuration page.
3. Select any slave port to configure as an M-Bus slave.
4. Specify the following parameters:
   • Type: Serial.
   • Com port: M-Bus Slave 1 or M-Bus Slave 2.
   • Baud rate: The specified communication speed on the M-Bus loop.
   • Bit Number: Number of data bits on the M-Bus loop. Standard 8 bits.
   • Parity: The parity for the M-Bus loop. Standard Even parity.
   • Stop Bit: Number of stop bits on the M-Bus loop. Standard 1 stop bits.
   • Timeout: Expected time to get answer from the M-Bus meter.
   • Protocol: The data protocol on the M-Bus loop. Standard M-Bus.
5. Press the Save settings.
6. Connect the external M-Bus loop from the external M-Bus master to the following pins:
   • PiiGAB M-Bus 900: Pins 15-18. Notice only one M-Bus slave.
   • PiiGAB M-Bus 900S: Pins 15-16 (M-Bus slave 1) or pins 17-18 (M-Bus slave 2).

The picture shows Slave port 2 is configured for M-Bus slave 1 on 2400 baud, 8 data bits, even parity, 1 stop bit, 2000ms as timeout and M-Bus communication. M-Bus Slave 1 at 2400 baud, 8 data bits, even parity, 1 stop bit, 2000ms timeout and M-Bus communication.

Note:

• Make sure the gateway doesn’t use the specific M-Bus slave port anywhere else. For instance any other slave ports or the Modbus2MBus and/or the Wireless applications.

The following list instructs how to configure a PiiGAB M-Bus 900/900S so that M-Bus meters can be read with RS232.

1. Start the gateway’s web interface in any web browser.
2. Go to the Configuration page.
3. Select any slave port for the RS232 communication.
4. Specify the following parameters:
   • Type: Serial.
   • Com port: RS-232.
   • Baud rate: The specified communication speed on the RS232 bus.
   • Bit Number: Number of data bits on the RS232 bus.
   • Parity: The parity for the RS232 bus.
   • Stop Bit: Number of stop bits on the RS232 bus.
   • Timeout: Expected time to get answer from the M-Bus meter.
   • Protocol: The data protocol on the RS232 bus.
5. Press the Save settings.
6. Connect the RS232-cable to the RS232-connection on the gateway:
   • PiiGAB M-Bus 900: Pins 10-12.
   • PiiGAB M-Bus 900S: Pins 11-13.

The picture shows Slave port 2 is configured for RS232 on 2400 baud, 8 data bits, even parity, 1 stop bit, 2000ms as timeout and M-Bus communication.

Note:

• Make sure the gateway doesn’t use the RS232-port anywhere else. For instance any other slave ports or the Modbus2MBus and/or the Wireless applications.
• The RX and TX pins should likely go to the opposite pins on the unit.
  For example: RX->TX and TX->RX.

The following list instructs how to configure a PiiGAB M-Bus 900/900S so that M-Bus meters can be read with RS485.

1. Start the gateway’s web interface in any web browser.
2. Go to the Configuration page.
3. Select any slave port for the RS485 communication.
4. Specify the following parameters:
   • Type: Serial.
   • Com port: RS-485.
   • Baud rate: The specified communication speed on the RS485 bus.
   • Bit Number: Number of data bits on the RS485 bus.
   • Parity: The parity for the RS485 bus.
   • Stop Bit: Number of stop bits on the RS485 bus.
   • Timeout: Expected time to get answer from the M-Bus meter.
   • Protocol: The data protocol on the RS485 bus.
5. Press the Save settings.
6. Connect the RS485-cable to the the gateways pin 8 (A) and 9 (B).

The picture shows Slave port 2 is configured for RS485 on 2400 baud, 8 data bits, even parity, 1 stop bit, 2000ms as timeout and M-Bus communication.

Note:

• Make sure the gateway doesn’t use the RS485-port anywhere else. For instance any other slave ports or the Modbus2MBus and/or the Wireless applications.
• The A and B pins should likely go to the opposite A and B on the RS485 master.
  For example: A->A and B->B.

If the search of secondary addresses failes in the PiiGAB M-Bus Setup Wizard through a PiiGAB M-Bus 900/900S then the timeouts are probably set too high.

There are four timeouts that are required to configure:

• MBusHub Master port in PiiGAB M-Bus 900/900S.
• MBusHub slave port in PiiGAB M-Bus 900/900S.
• SND_NKE/SND_UD timeout in PiiGAB M-Bus Setup Wizard.
• RSP_UD2 timeout in PiiGAB M-Bus Setup Wizard

This table shows how to configure the tiemouts depending on the communication speed:

	300 baud rate	2400 baud rate	9600 baud rate
Master port	9600ms	1300ms	400ms
Slave port	9600ms	1300ms	400ms
SND_NKE	11000ms	1500ms	600ms
REQ_UD2	11000ms	1500ms	600ms

If the search of secondary addresses failes in the PiiGAB M-Bus Setup Wizard through a PiiGAB M-Bus 900/900S then the timeouts are probably set too high.

There are four timeouts that are required to configure:

• MBusHub Master port in PiiGAB M-Bus 900/900S.
• MBusHub slave port in PiiGAB M-Bus 900/900S.
• SND_NKE/SND_UD timeout in PiiGAB M-Bus Setup Wizard.
• RSP_UD2 timeout in PiiGAB M-Bus Setup Wizard

This table shows how to configure the tiemouts depending on the communication speed:

	300 baud rate	2400 baud rate	9600 baud rate
Master port	9600ms	1300ms	400ms
Slave port	9600ms	1300ms	400ms
SND_NKE	11000ms	1500ms	600ms
REQ_UD2	11000ms	1500ms	600ms

If the converter is set to static IP address, a name server must be specified. This is done on the PiiGAB M-Bus 900 configuration page and in Name Server static IP address field.

Make sure the computer and the gateway are configured within the same IP-address range. If the gateway is placed in a subnet, the PiiGAB M-Bus Setup Wizard will not be able to find the gateway.

Make sure the computer and the gateway are configured within the same IP-address range. If the gateway is placed in a subnet, the PiiGAB M-Bus Setup Wizard will not be able to find the gateway.

There are two possible cases when the Pwr LED is flashing.

• Short circuit on the M-Bus loop indicates by a hastily red flash (5 flashes/second)
• Overload indication on the M-Bus loop indicates by a slow orange flash (1 flash/second)

In the event where the M-Bus loop is connected to the pulse port by mistake instead of the M-bus port on a meter a flash can occur every time a pulse goes trough. If the meter generates many pulses the power light will flash very fast as the pulses go through.

The gauges in the Overview page of the web interface have three different status modes.

These do not change automatically but require the user to test the status via the Verify function which tests all meters that are Red or via the Read All Meters function which sends a query to all listed meters to see if they are connected.

A client is something which requests the data from the M-Bus meter through the gateway.

• Name: Admin
• Password: Admin

The license depends on the number of load units, clients, protocols and hardware add-ons for which the converter is to be configured.

Quantity of M-Bus loads: 5, 20, 60 eller 120.
Quantity of clients: 1, 2 or 4.
Protocols:

• MBus2MBus
• MBus2Modbus
• MBus2MBusASCII
• QuickPost
• Modbus2MBus.
• Wireless M-Bus

• For https: 443 (standard)
• For http: 80

The actual IP-address of the name server. Not the name of the server.

• For M-Bus communication the default port are 10001, 10002, 10003 and 10004. The port numbers can be changed with the gateway’s web interface.
• To find the gateway on the network port 30718 is used with UDP in PiiGAB M-Bus Setup wizard.

Port 30718 over UDP/IP is used in the following functions:

• Find converters on the network.
• Change the IP settings of the converter.
• Change the parameters of the converter.

Other functions in the PiiGAB M-Bus Wizard you specify yourself which port and protocol to use.

Specific to Find converters on the network

Functions Find gateways on your network. uses the broadcast address (255.255.255.255) to find the PiiGAB M-Bus 810 and PiiGAB M-Bus 900/900S on the network. Keep in mind that broadcast may be disabled in routers. This can cause not being able to find converters that are placed on other subnets.

Check that the supply voltage (24VAC / DC) to the converter is fully isolated from other products in your control panel. Also check the ground on the primary and secondary sides of the protection transformer so that they are not interconnected.

To troubleshoot M-Bus meters connected to an PiiGAB M-Bus 810 there are a couple of things to verify.

Here is a list of good tools to use during troubleshooting:

• PiiGAB M-Bus Wizard
• Getting started PiiGAB M-Bus 810
• MicroMaster USB
• PiiGAB's general M-Bus documentation

IP-address
What IP-address is the gateway using? To have network communication with the gateway you need to setup your computer in the same network as the gateway. If there is an IT section please contact them to receive an IP-address for your computer. With the PiiGAB M-Bus Setup Wizard you can search gateways on the network or ping the gateway’s IP-address to verify if the network communication works.
In the PiiGAB M-Bus Wizard, you can search for converters on the network or "ping" the IP address of the converter to verify that the network connector is working.

f it’s not possible to receive the gateway’s IP-address then you need to setup a new IP-address.
Please see the FAQ on how to do this.

Harbour
What port is the gateway set to in order for the the M-Bus client to read the M-Bus meters? If you have network connection with the gateway you can find out the port with the PiiGAB M-Bus Setup Wizard.

Start the PiiGAB M-Bus Wizard -> Change converter parameters -> Connect via network.

Protocol
What protocol is the gateway set to in order for the the M-Bus client to read the M-Bus meters? If you have network connection with the gateway you can find out the protocol with the PiiGAB M-Bus Setup Wizard.

Start the PiiGAB M-Bus Wizard -> Change converter parameters -> Connect via network.

Note: If the gateway uses TCP you might not be able to connect to the gateway with the PiiGAB M-Bus Setup Wizard to read the M-Bus meters. This is due to that another client is connected to the port that the gateway is using. Change the port, change to UDP or turn off the client.

Communication speed
What communication speed is the gateway set to in order for the the M-Bus client to read the M-Bus meters?If you have network connection with the gateway you can find out the communication speed with the PiiGAB M-Bus Setup Wizard.

Start the PiiGAB M-Bus Wizard -> Change converter parameters -> Connect via network.

Note: If the gateway is set to 300 baud the communication speed is very slow. Remember to change the timeout in the PiiGAB M-Bus Setup Wizard to handle the long response time.

M-Bus meters
Is there any documentation of what M-Bus meters that are connected to the gateway? What addresses does the M-Bus meters use? (primary or secondary addresses).

If there is documentation of the meters then you can simple check each meter one by one with the PiiGAB M-Bus Setup Wizard. It’s also possible to read the search function in the PiiGAB M-Bus Setup Wizard.

If there is no documentation of the meters then you can use the search function in the PiiGAB M-Bus Setup Wizard. If the the result of the search function is incomplete then you have to find each meter one by one on the site and test them individually by it’s M-Bus address (primary or secondary address).

A M-Bus meter not responding
If an M-bus meter is not responding then you have to test the meter individually. If possible disconnect all other meters and test only that specific meter. Try with primary address 254 or the meter’s own primary or secondary address.

If it’s not possible to disconnect all meters then you can test the specific meter with a MicroMaster USB.

The gateway is normally programmed to DHCP unless otherwise specified. The port is configured to 10001 and the gateway is in addition to that configured to UDP.

If you are using TCP and the M-Bus Wizard at the same time you cannot make contact with an additional TCP client since the M-Bus Wizard “owns” the TCP handle. Shut down the M-Bus Wizard before starting the second TCP client. The same goes if you are using COM ports.

No, that is not possible. However the PiiGAB M-Bus 900 may be used for that setup.

Make sure the computer and the gateway are configured within the same IP-address range. If the gateway is placed in a subnet, the PiiGAB M-Bus Setup Wizard will not be able to find the gateway.

Normally there are two different scenarios to be investigated if the power light is blinking.

• If there is a short circuit on the M-Bus loop the power light will flash five times per second.
• If the loop is overloaded, meaning more M-Bus loads than the gateways is dimensioned for; the power light will flash every second.

In the event where the M-Bus loop is connected to the pulse port by mistake instead of the M-bus port on a meter a flash can occur every time a pulse goes trough. If the meter generates many pulses the power light will flash very fast as the pulses go through.

• For M-Bus communication the default port is 10001. The port number can be changed with the application PiiGAB M-Bus Setup Wizard.
• To configure the gateway and find the gateway on the network port 30718 is used with UDP in PiiGAB M-Bus Setup wizard.

Some meters do not handle SND_NKE together with REQ_UD2. Untick the SND_NKE option and the meters should respond.

To troubleshoot M-Bus meters connected to an PiiGAB M-Bus 810 there are a couple of things to verify.

Here is a list of good tools to use during troubleshooting:

• PiiGAB M-Bus Wizard
• Getting started PiiGAB M-Bus 810
• MicroMaster USB
• PiiGAB's general M-Bus documentation

IP-address
What IP-address is the gateway using? To have network communication with the gateway you need to setup your computer in the same network as the gateway. If there is an IT section please contact them to receive an IP-address for your computer. With the PiiGAB M-Bus Setup Wizard you can search gateways on the network or ping the gateway’s IP-address to verify if the network communication works.
In the PiiGAB M-Bus Wizard, you can search for converters on the network or "ping" the IP address of the converter to verify that the network connector is working.

f it’s not possible to receive the gateway’s IP-address then you need to setup a new IP-address.
Please see the FAQ on how to do this.

Harbour
What port is the gateway set to in order for the the M-Bus client to read the M-Bus meters? If you have network connection with the gateway you can find out the port with the PiiGAB M-Bus Setup Wizard.

Start the PiiGAB M-Bus Wizard -> Change converter parameters -> Connect via network.

Protocol
What protocol is the gateway set to in order for the the M-Bus client to read the M-Bus meters? If you have network connection with the gateway you can find out the protocol with the PiiGAB M-Bus Setup Wizard.

Start the PiiGAB M-Bus Wizard -> Change converter parameters -> Connect via network.

Note: If the gateway uses TCP you might not be able to connect to the gateway with the PiiGAB M-Bus Setup Wizard to read the M-Bus meters. This is due to that another client is connected to the port that the gateway is using. Change the port, change to UDP or turn off the client.

Communication speed
What communication speed is the gateway set to in order for the the M-Bus client to read the M-Bus meters?If you have network connection with the gateway you can find out the communication speed with the PiiGAB M-Bus Setup Wizard.

Start the PiiGAB M-Bus Wizard -> Change converter parameters -> Connect via network.

Note: If the gateway is set to 300 baud the communication speed is very slow. Remember to change the timeout in the PiiGAB M-Bus Setup Wizard to handle the long response time.

M-Bus meters
Is there any documentation of what M-Bus meters that are connected to the gateway? What addresses does the M-Bus meters use? (primary or secondary addresses).

If there is documentation of the meters then you can simple check each meter one by one with the PiiGAB M-Bus Setup Wizard. It’s also possible to read the search function in the PiiGAB M-Bus Setup Wizard.

If there is no documentation of the meters then you can use the search function in the PiiGAB M-Bus Setup Wizard. If the the result of the search function is incomplete then you have to find each meter one by one on the site and test them individually by it’s M-Bus address (primary or secondary address).

A M-Bus meter not responding
If an M-bus meter is not responding then you have to test the meter individually. If possible disconnect all other meters and test only that specific meter. Try with primary address 254 or the meter’s own primary or secondary address.

If it’s not possible to disconnect all meters then you can test the specific meter with a MicroMaster USB.

There are three timeouts in the PiiGAB M-Bus Wizard for the three protocols M-Bus, Modbus and MBusASCII. Set each timeout according to how long it takes to get a response to each query that the PiiGAB M-Bus Wizard sends.

Note: For older versions of PiiGAB M-Bus Wizard (3.1.0. or earlier) there was the same timeout for the three different protocols.

To set the respective timeout do the following:

1. In the main menu, select Test, search and configure meters and press Next:
2. Press the Next again.
3. Press the Debug-buttons.
4. Go to the Tools-menu and select Time delays.
5. Enter the desired value for each protocol:
   • M-Bus timeout: For all M-Bus communication.
   • Modbus timeout: To Modbus communication.
   • M-Bus ASCII timeout: For all MBusASCII timeout.
   • Note: In the previous versions, the timeout is called BusTimeout.
6. Press the OK.

Only PiiGAB M-Bus 900 V2.XX.XX.XXX or later versions support the function where the IP address can be changed with the PiiGAB M-Bus Wizard.

Increase the value of M-BusTimeout. The PiiGAB M-Bus Wizard will probably timeout when the response from the meter has not arrived. Press Debug/Tool menu/Time delays. Change the value of M-BusTimeout to 10000 milliseconds.

Both PiiGAB M-Bus 900 V2 and PiiGAB M-Bus 900S can change their IP address with the PiiGAB M-Bus Wizard.

Keep in mind that the netmask and default gateway will not be set. These need to be set in the converter's web interface. Please read it under the FAQ section "Example of initial contact"

If you are using TCP and the M-Bus Wizard at the same time you cannot make contact with an additional TCP client since the M-Bus Wizard “owns” the TCP handle. Shut down the M-Bus Wizard before starting the second TCP client. The same goes if you are using COM ports.

This is due to the fact that one or more network cards have been configured differently while the PiiGAB M-Bus Wizard was running. For example, if you change the IP address on a network card.

The PiiGAB M-Bus Wizard reads the available network cards during startup and when the error occurred, there is a failing link to the network cards.

Please restart the PiiGAB M-Bus Wizard.

If the search of secondary addresses failes in the PiiGAB M-Bus Setup Wizard through a PiiGAB M-Bus 900/900S then the timeouts are probably set too high.

There are four timeouts that are required to configure:

• MBusHub Master port in PiiGAB M-Bus 900/900S.
• MBusHub slave port in PiiGAB M-Bus 900/900S.
• SND_NKE/SND_UD timeout in PiiGAB M-Bus Setup Wizard.
• RSP_UD2 timeout in PiiGAB M-Bus Setup Wizard

This table shows how to configure the tiemouts depending on the communication speed:

	300 baud rate	2400 baud rate	9600 baud rate
Master port	9600ms	1300ms	400ms
Slave port	9600ms	1300ms	400ms
SND_NKE	11000ms	1500ms	600ms
REQ_UD2	11000ms	1500ms	600ms

If the search of secondary addresses failes in the PiiGAB M-Bus Setup Wizard through a PiiGAB M-Bus 900/900S then the timeouts are probably set too high.

There are four timeouts that are required to configure:

• MBusHub Master port in PiiGAB M-Bus 900/900S.
• MBusHub slave port in PiiGAB M-Bus 900/900S.
• SND_NKE/SND_UD timeout in PiiGAB M-Bus Setup Wizard.
• RSP_UD2 timeout in PiiGAB M-Bus Setup Wizard

This table shows how to configure the tiemouts depending on the communication speed:

	300 baud rate	2400 baud rate	9600 baud rate
Master port	9600ms	1300ms	400ms
Slave port	9600ms	1300ms	400ms
SND_NKE	11000ms	1500ms	600ms
REQ_UD2	11000ms	1500ms	600ms

An error message indicates that an OCX file is missing when the PiiGAB M-Bus Wizard starts.

For example:

The error is due to the specified system file being missing from the Windows installation.

To solve the problem:
1) Search for the missing file. Try searching in OCX dump.
2) Save the OCX file in the C:\Windows\SysWOW64\ folder.
3) Start terminals.
4) Run the command: regsvr32 "C:\Windows\SysWOW64\mscomm32.ocx".
NOTE: It may be necessary to run the terminal with administrator rights.

Now the PiiGAB M-Bus Setup should start.

Make sure the computer and the gateway are configured within the same IP-address range. If the gateway is placed in a subnet, the PiiGAB M-Bus Setup Wizard will not be able to find the gateway.

Make sure the computer and the gateway are configured within the same IP-address range. If the gateway is placed in a subnet, the PiiGAB M-Bus Setup Wizard will not be able to find the gateway.

For operating systems newer than Windows XP, C:\Program files is not suitable as an installation directory. Administrator rights are required to write to the directory. If you are a user without administrator rights, the PiiGAB M-Bus Wizard must be installed under a different system directory. We suggest installing directly under C:\, for example C:\PiiGAB_M-Bus_Wizard

• For M-Bus communication the default port is 10001. The port number can be changed with the application PiiGAB M-Bus Setup Wizard.
• To configure the gateway and find the gateway on the network port 30718 is used with UDP in PiiGAB M-Bus Setup wizard.

Port 30718 over UDP/IP is used in the following functions:

• Find converters on the network.
• Change the IP settings of the converter.
• Change the parameters of the converter.

Other functions in the PiiGAB M-Bus Wizard you specify yourself which port and protocol to use.

Specific to Find converters on the network

Functions Find gateways on your network. uses the broadcast address (255.255.255.255) to find the PiiGAB M-Bus 810 and PiiGAB M-Bus 900/900S on the network. Keep in mind that broadcast may be disabled in routers. This can cause not being able to find converters that are placed on other subnets.

QuickPost uses passive mode.

Yes, without PiiGAB QuickPost specified in the licence, PiiGAB QuickPost will not work.

Yes, the raw M-Bus data from the M-Bus meters must be converted to PiiAGB's M-Bus ASCII protocol in order to be exported via PiiGAB QuickPost.

No, not necessarily. However, we recommend setting the converter's internal clock so that the FTP or HttpPost server's clock is synchronised with the converter's clock.

When GMT has reached Upload time the file is uploaded. Not when the local time has reached Upload time.

In the left navigation bar of the converter's web interface, it should be possible to select PiiGAB QuickPost if the application is installed.

The following list will explain how to install a license in the PiiGAB M-Bus 900/900S. These steps will also show the current license of a PiiGAB M-Bus 900/900S.

1. Start the gateway’s web interface in any web browser.
2. Go to the Administrations page.
3. Under the Basic Settings tab you will find the section License. This shows the licence of the converter (SW 2.5.0 or higher)
4. Paste the license into the field Update licence.
5. Press the button Update.
6. Wait for the license to be installed.

The following list will explain how to install software in the PiiGAB M-Bus 900 V2 and PiiGAB M-Bus 900S. These steps are either used to install a new software or update an existing.

1. Download the software as a ZIP file, please click here.
2. Unzip the file to gain access to the tgz-file.
3. Place the tgz-file somewhere on the computer. Don’t open the tgz-file.
4. Start the web interface for the gateway in any browser.
5. Go to the Administration page.
6. Find the section Update Software.
7. Press the Browse… button.
8. Browse to and select the tgz-file.
9. Press the button Install.
10. Wait until the installation has finished.

Note: If QuickPost, Modbus2MBus or Wireless M-Bus is not shown in the web browser, please press CTRL + F5.

Check that the Tag Type is Value in the configuration. If you have copied from a template, such as the Browse Template, it may have a different Tag Type.

Yes, M-Bus ASCII data can be delivered from any PiiGAB M-Bus 900/900S via a slave port configured for M-Bus ASCII.

Yes, PiiGAB QuickPost is downloaded at www.piigab.com. In the web interface of the converter on Administration side under Update Software the application is installed.

No, the content of the PiiGAB QuickPost configuration file can either be part of or the same file as the Master ports.

This depends on how much the timeout on the slave port that delivers the M-Bus ASCII data is set to. The PiiGAB QuickPost's timeout should be higher than the slave port to guarantee that data arrives at the PiiGAB QuickPost application.

This means that Upload time determines when the export takes place.

You probably do not have the current Sentinel driver installed on your computer. The driver can be downloaded at: http://www.safenet-inc.com/support-downloads/sentinel-drivers/ . As of version 2.5, we no longer have support for hardware locks.

If it is a new configuration you want to test, the error is because the OPC server was not turned off when you started the monitor function. In the lower right corner there is an indication that shows whether the server is on (solid green) or off (solid red). You must wait until the OPC server is turned off before testing a change.

When there are two or more instances of the process MBusOPC.exe this is because the OPC clients run with different users and each user starts their own instance of MBusOPC.exe. Therefore, Windows has not been able to synchronize so that each OPC client uses the same process of the M-Bus OPC server.

When there are several instances of MBusOPC.exe, there is a risk that the OPC server will not get in touch with the M-Bus converters and the M-Bus meters. As a result, OPC clients will not receive the desired data from the M-bus meters.

To control Windows to use only one instance of MBusOPC.exe, you must control in the DCOM settings which users should own the process.

• Start DCOM settings (dcomcnfg.exe).
• Browse to Console Root -> Component Services -> Computers -> My Computer -> DCOM Configuration.
  
  

• Find MBus.
• Right-click and select Properties.
• Select the tab Identity.
• Select This user.
• Enter the fields for the user who will own the process.

• Press the OK.

Citect is set up for DA 1.0 OPC Servers. PiiGAB M-Bus OPC Server supports version 2.00, 2.05 and 3.0. This means that you need to add a setting in Citect.ini. Under the [OPC] group, enter UseOPC2=1.

We have found that the WinZip Selfextractor that we used for the installation tool is not stable in the 64 bit environment. From version 2.02.01.001 the WinZip Selfextractor is no longer used and therefore the installation in a 64 bit environment should work as expected.

Find out the existing and new System ID for both computers. Email order@piigab.se and ask for a licence transfer and specify the existing and new System IDs.

As of v2.5, you deactivate the licence on the computer you want to move it from via Tools/License... "Deactivate this workstation" and then activate it with your License ID and activation password on the other computer.

The OPC Server is a thin server, which means that it does not contain a user interface, but the interface is completely external and consists of a real OPC client. The changes made are loaded when the server restarts. The OPC standard says that there must be a small time delay from when you press stop until the server actually crashes. If you restart too quickly, the server will not have time to stop and no new configuration file will be loaded. As of version 1.3.0.1, the server status is displayed in the status bar at the bottom right. This means that it will be easier to understand when the server has really stopped.

After a change in the project in PiiGAB Explorer, both the file must be saved and the Server process must be restarted. If this is not done, the meters affected by the change will not receive communication.

Save the project

 

 

Stop the server via the button Stop Monitor

 

The status of the server should turn red. Only then is the server switched off.
After this, the connection can be started again.

Quick start Guide to Configure M-Bus to Modbus 

1. Plug all the meters you want to use on the M-bus loop into Mbus Master ports 1-4 on your Gateway. 

2. Search your meters in the web interface using a "Fast Search" in the Startup Config tab 

Your meters should appear in a list under the "Fast Search" button

3. Go to the overview page in Startup Config where the meters should now be visible in the list below.

Add Encryption Keys to the meters if they are Wireless meters

4. Click on "Auto-Create Myconfig files"

The files to be used to read meters are now created

5. Go to MbusHub and the tab "Master port", then select the configuration file for the Master port file as shown below. Save the configuration.

6. Go to Slave Port 1 and select the configuration file as shown below

7. Now you will be able to query against the registry entries described in the CSV file located in the slave ports tab of the web interface

Configure ValueSplit scale factor

Here are the scale factors for ValueSplit for data types larger than 32 bits.

Data type	Scale factor
BCD12	0,001
INT48	0,00001
INT64	0,0000000001

ATTENTION!

These scaling factors are generic and scale down the value to fit in an INT32.

Consider deriving which scaling is best suited to the plant.

For example:

The energy 12345Wh i is stored in a BCD12 and should be represented as kWh.

Highest value of BCD12 = 999 999 999 999 999, takes up 6 bytes and does not fit in an INT32 (4 bytes).

With a scale factor of 0.001, the maximum value is 999 999 999 999.999.

The integer part: 999 999 999 now fits in an INT32.

Decimal part: 999, fits in an INT32.

The value will then be 12.345kWh:12kWh and 345Wh.

In this case, one or more OPC clients are still connected to the OPC server. If you want to stop the OPC server, for example to test a new configuration, all OPC clients must release their connection to the OPC server.

.NET Framework V3.5 is the basis for PiiGAB M-Bus Explorer. The requirements for .NET Framework V3.5 are here.

PiiGAB M-Bus Explorer also works on the following operating systems:

• Windows server 2012.
• Windows server 2012 R2.
• Windows server 2016.

The information below only applies to versions <= 2.4.1

Start PiiGAB M-Bus Explorer and go to the menu Tools. Please select Licence... to obtain The licence manager.

• Then locate the System ID field.
• The software licence is entered in the field Registration Code. Then press Store Registration Code button.
• Hardware licence is displayed in the section Sentinel (Parallel/USB).

As of v2.5:

Paste the licence ID and activation password in the respective fields and click Next.

(With version 2.5 of PiiGAB M-Bus OPC Server / Explorer we change the licensing system.

Upon delivery you recieve a delivery note where a license ID as well as an activation code is included. You no longer have to send in your SystemID for activation. You can also easily move your license from one computer to another on your own, free of charge.

This assumes that you have the latest version. Otherwise, the previous licence management will continue to apply).

Below applies to versions <= 2.4.1

Start PiiGAB M-Bus Explorer and go to the Tools menu. Select Licence... to bring up the Licence Manager. Copy the licence into the Registration Code field and press Save Registration Code.

Please be aware that the (LAN) Timeout has been omitted in Citect V7.

When using slow protocols the (LAN) Timeout often has time to exceed the original setting of 8000ms. When this occur the #COM appears sporadically on the screen, the hardware error “Request Timeout from I/O Server” will appear, and at the same time the total number of Timeouts will be counted in the Probe Kernel window. This is normally corrected by changing the (LAN) Timeout to 20000 or higher.

If it is a new configuration you want to test, the error is because the OPC server was not turned off when you started the monitor function. In the lower right corner there is an indication that shows whether the server is on (solid green) or off (solid red). You must wait until the OPC server is turned off before testing a change.

If you have QuickOPC installed on Windows Vista or Windows 7, you may need to run the Licence Manager as administrator.

If you are using .NET Framework 4.6, the EasyDAClient class will crash on instantiation. The following solution in the Windows registry solves the problem:

• Open the registry (regedit.exe)
• Scroll down to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework
• Create a new 32-bit value (DWORD)
• Enter name: useLegacyJIT
• Set value: 1
• Close the register

NOTE: You may need administrator rights to access the register.

Make sure that a licence is installed on the computer where QuickOPC is used. If there is no licence, QuickOPC will only work for 30 minutes.

This problem occurs when you instantiate the EasyDAClient class very often and do not clean up the instances correctly.
When an instance should not be used anymore call EasyDAClient.Dispose() to flag to the .NET GC (Garbage Collector) that the instance should be deleted. Alternatively, try to use one or few instances of EasyDAClient instead of several. But call EasyDAClient.Dispose() when the instances should be deleted.

When there are two or more instances of the process MBusOPC.exe this is because the OPC clients run with different users and each user starts their own instance of MBusOPC.exe. Therefore, Windows has not been able to synchronize so that each OPC client uses the same process of the M-Bus OPC server.

When there are several instances of MBusOPC.exe, there is a risk that the OPC server will not get in touch with the M-Bus converters and the M-Bus meters. As a result, OPC clients will not receive the desired data from the M-bus meters.

To control Windows to use only one instance of MBusOPC.exe, you must control in the DCOM settings which users should own the process.

• Start DCOM settings (dcomcnfg.exe).
• Browse to Console Root -> Component Services -> Computers -> My Computer -> DCOM Configuration.
  
  

• Find MBus.
• Right-click and select Properties.
• Select the tab Identity.
• Select This user.
• Enter the fields for the user who will own the process.

• Press the OK.

The problem is probably that only the Designo Insight license key is installed on the computer, however the Citect key also has to be installed. It is enough to have a so called zero license, which can be delivered from Siemens.

Citect is set up for DA 1.0 OPC Servers. PiiGAB M-Bus OPC Server supports version 2.00, 2.05 and 3.0. This means that you need to add a setting in Citect.ini. Under the [OPC] group, enter UseOPC2=1.

From version 2.02.03.001 the M-Bus driver is compiled in VS2010. If the driver can not be registered, you probably did not run any program written in VS2010 unmanaged on the current computer. You need to run the redistributable package from microsoft to install the latest libraries on your computer. See the link below.

https://www.microsoft.com/en-us/download/confirmation.aspx?id=5555

We have found that the WinZip Selfextractor that we used for the installation tool is not stable in the 64 bit environment. From version 2.02.01.001 the WinZip Selfextractor is no longer used and therefore the installation in a 64 bit environment should work as expected.

This box will appear unless the driver is OS signed and approved for your current operating system. Version 2.02.02.001 of the M-Bus driver is OS signed for the following operating systems: Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows 8.1, Windows Server 2012 , Windows Server 2012 R2.
If you are running an unapproved version, you can prevent the dialogue box from appearing by using the OverrideOSProtection parameter in your driver group in Citect.ini
[MBUSCIT]
OverrideOSProtection=1

Many new parameters have been implemented in version 2 of the M-Bus driver. The InitTimeOut is only used for the starting question and can be set as low as 500ms, and there is also a MainTimeOut to be used for normal questions. This can be used individually by port for 300baud or 2400 baud and can be handled individually or optimally. During the session it is possible to prevent the starting question completely by using the parameter IgnoreDeviceStartup. For more information see the driver manual.

The Citect driver supports multitelegram, and if you have a multi telegram meter like the Armatec or F4 from Metrima connected they will read all the telegrams from the meters. The everyday information is normally to be found in telegram 1, and if that is the only information needed set the parameter NrOfTelegrams=1, which means that only telegram number 1 will be read. By doing this the stress on the M-Bus loop will be noticeably reduced.

After a change in the project in PiiGAB Explorer, both the file must be saved and the Server process must be restarted. If this is not done, the meters affected by the change will not receive communication.

Save the project

 

 

Stop the server via the button Stop Monitor

 

The status of the server should turn red. Only then is the server switched off.
After this, the connection can be started again.

First off you have to set the initial questioning so that it can be logged in syslog.dat, which is easily done by writing DebugStr=*ALL for your driver in Citect.ini. ‘*’ can be replaced by the port name and that way that specific port will be logged.
For example M-Bus can look like the following:
[MBUSCIT]
DebugStr=Port1_Board1 ALL
Now you can see if a question is asked or if you get answers from your equipment.

In this case, one or more OPC clients are still connected to the OPC server. If you want to stop the OPC server, for example to test a new configuration, all OPC clients must release their connection to the OPC server.

The different formats are listed on the PiiGAB QuickPost configuration page in File Format field. You can read more about the different formats in the manual.

By changing the ArrayLimit parameter, you can sample 1-10 tags at once.

The first thing to check is that you have actually set a sampling time on the relevant tags. If they are set to 00.00:00:00, the sampling will not start.

By ticking "Sample At Startup", the first sample will be taken immediately even if you have chosen to sample every hour.

Under advanced settings of the project, there is the parameter Threads. Set it to 1 as value.

In order to run QuickLoop, the .NET framework 4.5.2 needs to be installed on the computer.

Among others, these operating systems support .NET Framework 4.5.2:

• Windows 7 (x86 or x64) with service pack 1.
• Windows 8 (x86 or x64) with Update.
• Windows 10 (x86 or x64).
• Windows Server 2008 R2 (x64) with service pack 1.
• Windows Server 2012 (x64).
• Windows Server 2012 R2 (x64).

Quick start Guide to Configure M-Bus to Modbus 

1. Plug all the meters you want to use on the M-bus loop into Mbus Master ports 1-4 on your Gateway. 

2. Search your meters in the web interface using a "Fast Search" in the Startup Config tab 

Your meters should appear in a list under the "Fast Search" button

3. Go to the overview page in Startup Config where the meters should now be visible in the list below.

Add Encryption Keys to the meters if they are Wireless meters

4. Click on "Auto-Create Myconfig files"

The files to be used to read meters are now created

5. Go to MbusHub and the tab "Master port", then select the configuration file for the Master port file as shown below. Save the configuration.

6. Go to Slave Port 1 and select the configuration file as shown below

7. Now you will be able to query against the registry entries described in the CSV file located in the slave ports tab of the web interface

Conversion of Modbus meters to M-Bus is done in the program Modbus2Mbus Config. You can find this for download at https://www.piigab.com/products/mjukvara/

In order to have a simple and trouble-free conversion, it is important to have the meter's manual available.

Create a new project and then add a device per meter.

Set the parameters for Mbus and Modbus communication

Add objects for each measured value to be read out and set the correct Modbus register as well as unit and scaling.

If you have several meters of each type, copy the meter and only change the Slave and M-Bus address.

It is also possible to save these as templates for future projects.

After the project is finished, it is saved and then uploaded to the 900

Viltrus Converter Mbus2RS485
250 loads

Mbus connects to Converter terminals 1 and 2 - polarity independent

If connected correctly, Operating should be flashing and Offline and Overload should be off.
(in case of few loads, Offline may still be lit)

RS485 between Converter and Piigab

T+/R+ (3) on the Converter is connected to RS485 A (8) on Piigab

T-/R- (4) on the Converter is connected to RS485 B (9) on the Piigab

GND (5) on the Converter is connected to GND (10) on the Piigab

Plinth	Details
1	Mbus +
2	Mbus
3	RS485 TD(A+)
4	RS485 TD(B-)
5	RS485 GND
6	230V GND
7	230V N
8	230V L

If the communication does not work, check that no other process locks that port.

Check that Modbus2Mbus or any slave port is not set to RS485.

Also enable RS-485 Failsafe in MBushub for more stable collection.

The following list instructs how to configure a PiiGAB M-Bus 900/900S so that M-Bus meters can be read with RS485.

1. Start the gateway’s web interface in any web browser.
2. Go to the Configuration page.
3. Select any slave port for the RS485 communication.
4. Specify the following parameters:
   • Type: Serial.
   • Com port: RS-485.
   • Baud rate: The specified communication speed on the RS485 bus.
   • Bit Number: Number of data bits on the RS485 bus.
   • Parity: The parity for the RS485 bus.
   • Stop Bit: Number of stop bits on the RS485 bus.
   • Timeout: Expected time to get answer from the M-Bus meter.
   • Protocol: The data protocol on the RS485 bus.
5. Press the Save settings.
6. Connect the RS485-cable to the the gateways pin 8 (A) and 9 (B).

The picture shows Slave port 2 is configured for RS485 on 2400 baud, 8 data bits, even parity, 1 stop bit, 2000ms as timeout and M-Bus communication.

Note:

• Make sure the gateway doesn’t use the RS485-port anywhere else. For instance any other slave ports or the Modbus2MBus and/or the Wireless applications.
• The A and B pins should likely go to the opposite A and B on the RS485 master.
  For example: A->A and B->B.

Download the meter list dlms2mbus_meterlist.csv under the Administration tab.

Edit the file in Notepad or Excel and replace the meter number on the old meter with the new one.

If you want to list the meter in Overview, a meter change must also be done there

Then upload the edited file in the DLMS2MBUS programme.

Normally it takes up to 30 minutes for the meter to be read and saved in the programme memory for access by other systems/programmes.

Create a list of your meters according to the defined template.

Primary address

Meter type

Metaride

Meter name

Designation

The file format must be of type .csv

The list is uploaded on the 900 under the DLMS2MBUS programme

Set the reading parameters to your liking. Recommended is a reading period of 30 minutes and a telegram lifetime of 1440 minutes.

You can then see the latest readout under the Results tab (Updated after a readout is complete).

For those who want to list the meters under Overview, they also need to be added there.

Our configuration files and meter lists are in CSV format.

If you want to edit these in Excel, they will look strange when you open them as all the information is in the same column.

For an easier overview, follow these steps.

Tick column A.
Go to Data in the menu
Then select Text to column

When the wizard asks for the Original data type, select Delimited fields and then Next
Now select Comma to be a delimiter, press Next and then Finalise.

Now the information has been split into different columns.