FAQ
Here you can find a number of questions and answers regarding our products.
Guides (1)
The following instruction shows how to use Browse-template in the PiiGAB M-Bus Explorer to display the M-Bus objects in an M-Bus meter.
Note:
This instruction assumes that the PiiGAB M-Bus Explorer is already configured to communicate with the M-Bus converter and the address of the M-Bus meter.
- Start the PiiGAB M-Bus Explorer.
- Create a new project or open an existing one.
- Create and configure or select the converter to which the template will be applied.
- Press the Templates menu and select Import template.
- In the box Templates, press PiiGAB on the left and Browse on the right.
- Enter a man on the template.
- Press the Load template. The template is created in the PiiGAB M-Bus Explorer tree view as a gauge under the selected converter.
- Double-click on the meter in the tree view.
- Enter the primary or secondary address.
- Press the OK button.
- Save the project.
- Tap the meter in the tree view.
- In the meter view, press Data record column. All tags (objects) will then be in numerical order.
- Press the Start monitor button.
- Wait until Quality column shows Good on all the tags.
NOTE: If it appears Bath there is most likely a configuration or communication error. - Expand Value column until all the data in each tag is displayed. The Value column displays each tag's object number, data type, physical representation, scaling and value.
The picture shows an M-Bus meter with the identification number 53880741 and its two M-Bus objects.
Keep in mind:
- The Browse template shows what is in the first 40 M-Bus objects in the meter.
For some meters there are less than 40 items and for some meters there are more than 40 items. The template only shows 40 items by default. The browse template can be extended with more tags if desired. - The browse template can also be used to show if the meter contains multiple M-Bus telegrams. Look for a tag whose value contains N/A (0x1F) Manufacturer specific. This indicates the last object in the telegram and that there are more objects in the next telegram in the meter. Tags that come afterwards belong to the next telegram.
- Please note that the column Data type fish VT_BSTR for all tags. This is specific to the Browse template and should not be confused with the M-Bus object's real data type. The M-Bus object's real data type is in Value columns.
- Tagging Header includes the meter's secondary address, manufacturer and type.
Below is an image of how to read the contents of the Browse template.
Category
Guides,
PiiGAB Explorer
0
0
PiiGAB 900S/T (1)
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
4
6
PiiGAB Explorer (14)
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.
Category
PiiGAB Explorer
0
0
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.
Category
PiiGAB Explorer,
OPC and Citect
0
0
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.
Category
PiiGAB Explorer,
OPC and Citect
0
0
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.
Category
PiiGAB Explorer,
OPC and Citect
0
0
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.
Category
PiiGAB Explorer,
OPC and Citect
0
0
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.
Category
PiiGAB Explorer
0
0
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.
Category
PiiGAB Explorer
1
0
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.
Category
PiiGAB Explorer,
OPC and Citect
0
0
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
4
6
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.
Category
PiiGAB Explorer
0
0
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.
Category
PiiGAB Explorer,
OPC and Citect
0
0
.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.
Category
PiiGAB Explorer
0
0
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).
Category
PiiGAB Explorer
0
0
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.
Category
PiiGAB Explorer
0
0
OPC and Citect (6)
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.
Category
PiiGAB Explorer,
OPC and Citect
0
0
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.
Category
PiiGAB Explorer,
OPC and Citect
0
0
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.
Category
PiiGAB Explorer,
OPC and Citect
0
0
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.
Category
PiiGAB Explorer,
OPC and Citect
0
0
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.
Category
PiiGAB Explorer,
OPC and Citect
0
0
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.
Category
PiiGAB Explorer,
OPC and Citect
0
0
Modbus2Mbus (1)
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
4
6
