Introduction

What is the Guru Hub?

What is a Zigbee/Digimesh network?

Commissioning a hub

Requirements

• A Guru commissioning cable (available from Guru Systems)
  
• A valid. p12 security certificate (available from Guru Systems)
  
• A portable computer with the latest version of the Java Runtime Environment (available from www.java.com). If you’re unsure whether this is the case, please ask your systems administrator.
  
• The latest FTDI driver for use with the Guru commissioning cable. This should automatically install on first use of the commissioning cable. If you’re unsure whether you have the latest drivers, please ask your systems administrator.
  

Before you commission

1. The Guru Base Unit has been installed in accordance with the Guru Hub Installation Guide
   
2. The “mains present” LED is illuminated (See figure 1 Arrow 1).
   
3. The mains cover plate is in place and has been secured with the screws provided with the Guru Base Unit. (See figure 1 Arrow 2).
   

Figure 1 – The inside of a Guru Hub

1. Attach the Top Unit to the Base Unit using the ribbon connector and put the Top Unit in the offset position as described in the Guru Hub Installation Guide.
   
2. Plug the Guru commissioning cable into a USB port on your portable computer. Connect the other end of the cable to the debug port on the Base Unit (see figure 1 arrow 3).
   
3. Run the Commissioning Tool by double-clicking on the “CommissioningApp.jar” file in its folder on your laptop If you’re unsure where this is, please ask your systems administrator. You should now see the screen as shown in [figure 2].
   
4. Choose your security certificate by navigating to and selecting it [figure 2 Arrow 1] and enter your passphrase. This passphrase is unique to your certificate and click OK.
   

1. Connect to the Guru Hub by choosing the correct serial port in the drop-down and clicking “connect”. If you receive a “device not responding” message, you probably need to try another serial port to choose from the drop-down list. You should now see the screen as shown in [figure 3]. You’re ready to start commissioning.
   

Basic commissioning

1. Enter the name of the Hub into the “Location Name” text box and click “set”. It is typical practice for the name to correspond to the flat number or plot number.
   
2. Load the config script by clicking on the “Load Config” button and navigating to the file provided by your IT team. Once loaded, click “Run Configuration”. You should receive “Success” at the end of the script. If this is not the case, please refer to the person responsible for writing the scripts in your company.
   
3. Click “Set Time from Gateway” to set the time and ensure that a) the Hub is connected to the wireless mesh network and b) can see the Gateway. (This can take up to 3 minutes on Hub II due to the way the network joins new nodes.
   
4. Once the configuration script has been successfully run, you can create and save a summary report in the following way:
   
1. Click “Initialise Report” to create a report header in the output window of the “Hub” tab.
   
2. Run configuration as above.
   
3. Click “Save Report” and choose a suitable location for the output file.
   
5. Disconnect from the Hub by clicking on “Disconnect” in the commissioning app.
   
6. Attach the Top Unit to the Base Unit as shown in the Installation Guide and apply tamper-proof seals (recommended).
   

Manual commissioning

Configuring accounts

• Account Name (Hub 2 only) - You can name the account here eg heat account
  
• Account active tick box – sets an account to the active or inactive. When inactive, all items for an account are greyed out.
  
• Utility type drop-down – sets the type of account, for example, Heat/Electric/Water
  
• Utility unit’s drop-down – sets the unit of measurement for the utility you have selected in the step above, e.g. kWh for heat, m3/h for water
  
• Primary relay drop-down – sets relay that the shut-off valve is connected to for the utility you are configuring. Please refer to site documentation for the correct option as this can differ from site to site. If the correct relay is not selected then if a tenant goes into an “Exhausted Credit” state on the Hub then their supply will not be shut off.
  
• Secondary relay drop-down – typically not used. May be used in the case where two relays are used to control a single valve.
  
• Shut-off Mode drop-down – sets the way in which the shut-off valve works. “Primary off enables” will leave the utility supply connected until the account is in use. Please consult the shut-off valve manufacturer’s documentation for the required setting.
  
• Meter – see section below on configuring a meter
  
• Report Period drop-down – sets the frequency with which data is sent to the HES. 30 minutes is recommended.
  

• Enable manual control of relay – Use this to test the Shut Off valve is functioning correctly.
  
• Automatically update the display of meter readings – This area will display the details in real time from the meter.
  

• Manual add; Click manual add and enter the Mbus address of the meter. Click OK. The Mbus address should now show in the left-hand column. Clicking on the address in the left-hand column will read and display all values in the right-hand pane. Click ok.
  
• Automatic Scan; Click on “Start Scan”. The scan will progress through each Mbus address. Once the scan reaches the address of the meter, the address number should appear in the left-hand column. To stop the scan, click on “Start Scan” a second time. Click ok.
  

Pulse meter

Viewing logs

• Joined (yes/no) – this indicates whether the Hub has successfully seen and joined the ZigBee/Digimesh network.
  
• Connected (yes/no) – this shows if the hub is currently connected to the ZigBee/Digimesh network. Note, a Hub may be joined to a network, but not currently connected.
  
• Channel (Hub I only)– This indicates the channel of the currently connected network, this should match up with the Gateway’s operating channel.
  
• Pan ID – indicates the short Pan ID of the current radio network.
  
• Extended Pan ID (Hub I only)– indicates the long Pan ID of the current radio network.
  
• Preamble (Hub II Only) - This is unique to each gateway. It should be a value between 1 and 5.
  

• Channel – as described above
  
• Pan ID – as described above
  
• Extended Pan ID (Hub I only)– as described above
  
• Link Quality – indicates the strength of the signal [between the Hub being commissioned and the node displayed in the Networks. 255 is the best possible link quality.
  
• Level (dBm) – indicates the strength of the received signal at the location of the Hub being commissioned. A level of more than 85 dBm indicates a weak signal level, which should not be relied upon to form a stable network.
  
• Joinable – This will indicate whether you can connect to this hub as part of the ZigBee network.
  

Basic Hub Troubleshooting

The Hub screen is off.

Is the screen in sleep mode?

Is there power to the unit?

1. The first is to make sure any isolation switches are switched on, eg a switched fused spur installed that inadvertently turns off the Guru Hub (We say that the hub should always be on unless isolated for maintenance).
   

1. The second is to remove the top unit carefully and check for a mains power light on the PCB of the base unit. If the red LED is not on, then there is no power. If the mains supply is on, then there could be a problem with the base unit itself. We recommend a qualified electrician measure the voltage across the mains terminals.
   

Is the ribbon cable inserted correctly?

No meter data is being collected

Has the hub been commissioned correctly to the meter?

1. Make sure there is continuity between the heat meter and the hub mbus cable. For example, there have been cases when the cable has had screws driven through it.
   
2. Ensure that the mbus cable has been terminated into terminals 1 and 2 on the guru base unit on the right-hand side.
   
3. Ensure that the mbus cable has been terminated into the correct terminals on the heat meter. Mbus protocol normally conforms to terminal numbers 24 & 25
   
4. Ensure that the meter is an mbus meter and there are no special functions required to bring it out of a sleep state.
   
5. Make sure the baud rate selected on the hub is compatible with the heat meter. Normally 2400 is required.
   
6. If there is more than one mbus meter connected to the hub, then make sure they support the same baud rate as one another, two different baud rates can’t exist on one mbus master.
   
7. If there is more than one mbus meter connected to the hub, make sure they are on independent mbus addresses. If there is an mbus conflict, you will be able to tell because, in the scan for mbus section on the commissioning app, you will see a number inside triangle brackets like <XX>
   
8. Has the meter been approved for use with the Guru Hub II? You can obtain this information from Appendix 2.
   
9. Is the meter mains powered? If so has it been wired into the mains?
   
10. If you are seeing multiple mbus addresses but only expecting one address, then you might be connected to a sitewide mbus network. (Please disconnect the mbus cable from the hub as a site-wide network also feeds 36v over the mbus cables
    
11. Is there 36v over the two mbus terminals, if not then there could be a problem with the circuit board. This could be either the top unit or the base unit.
    

1. To check this, use a multimeter and measure the voltage over terminals 1 & 2.
   
2. If there is no voltage, then please try a new top unit and return the old unit to Guru.
   
3. If there is still no voltage then swap the base unit and return the faulty unit to Guru.
   

No power to the unit.

1. Check there are no isolation switches that are switched off.
   
2. Check voltage over the mains power terminals located under the mains cover plate. (NB This should be carried out by a qualified electrician, DO NOT ASSUME THERE IS NO POWER IF THE LED IS UNLIT)
   
3. If there is no voltage then the supply to the Hub needs to be checked.
   
4. If there is voltage but the top unit is not powering up or there is no LED present then please send the base unit back to Guru and install a new base unit.
   
5. If the new base unit has power and the LED is lit then please change the top unit and return the top unit to Guru.
   

The valve is not operating when the relay is controlled.

1. The valve may not be wired to the base unit. Check for continuity between the relay and the control valve. NB this is mains voltage, please turn off the hub before you test this.
   
2. The valve may be wired incorrectly to the base unit. If this is the potential cause, then a qualified electrician should check to make sure the valve requirements have been met by the Hubs supply.
   
3. The relay may be faulty, although this has never happened.
   
4. The valve may be faulty. Please have an electrician investigate this.
   

Appendix 1 - Top Unit Swap Out

1. Find the Hub’s Location ID. This is one of the Hub Attributes found on the Advanced tab in the Hub Overview screen, or in the commissioning app on the Hub tab, although if there is a problem with the hub and there is no power you wont be able to use the commissioning app to find this out)  
   
2. Find the ZigBee/Digimesh link key for the network the Hub is connected to. This is found in your KeePass file (usually found in the Dropbox folder provided by Guru).
   

Swapping the top unit

1. Replace the original top unit with the replacement unit and wait for 30 seconds after power on.
   
2. Connect the commissioning cable to the back box in the normal way.
   
3. Log into the commissioning app.
   
4. Click the ZigBee/Digimesh tab and connect to the network where the top unit belongs using the encrypted link key.  
   
5. On the setup tab of the commissioning app, click the “Replacement Hub” button.  
   
6. 
   
7. In the “Location ID number” field, enter the Location ID that was retrieved from the HES.
   
8. Tick the box that says download configuration from server. Then click OK.
   
9. All relevant data will now download to the top unit from the HES. While the time it takes to download the data is dependent on the network strength, it could be only a matter of minutes, allowing the engineer to check the Hub has successfully reconfigured itself before leaving the dwelling, this is identifiable when the hub is showing account data on its screen. The data included in the transfer includes:
   
1. Account settings e.g. Meter, relay and M-Bus address for all active accounts.
   
2. Any credit balances and previous reading data.
   
10. Once this process has been completed, the engineer should wait to check that the data transfer has been successful as described in the previous paragraph. If the hub screen does not change then it could be down to weak comms on the network, the engineer should check with someone with visibility of the HES to ensure the new top unit is contactable, and if so then carry out the process from step 5 again.
    

Appendix 2 - Compatible meter list

Recommended Heat Meter Commissioning Guidelines

Appendix 3 - Config Script building

Information required before you start

1. {
   
2. “config”: [
   

1. “set general font_controller ReportingInterval null”,
   
2. “set general font_controller ZigbeeAllowJoining true”,
   
3. “set general font_controller AwaitingConfiguration false”,
   
4. “set account1 font_account AccountActive true”,
   
5. “set account1 font_account PrimaryRelay 0”,
   
6. “set account1 font_account SecondaryRelay null”,
   
7. “set account1 font_account ShutOffMode 2”,
   
8. “set account1 font_account ReportingInterval null”,
   
9. “set account1 metering UnitOfMeasure 0”,
   
10. “set account1 metering MeteringDeviceType 5”,
    
11. “set account2 font_account AccountActive false”,
    
12. “set account3 font_account AccountActive false”,
    
13. “set account4 font_account AccountActive false”,
    
14. “set account5 font_account AccountActive false”,
    
15. “digimesh network 11 0xab2a 0x8fa64882bad720a04ba3392d1519b”
    
16. “set account1 font_account Meter mbus/0”,
    
17. null],
    

1. “end” : []
   
2. }
   

General config file overview

The lines explained

“0” =  kW 
“1” = m3/h 
“2” =  ft3/h 
“3” =  cdf/h 
“4” = US gl/h 
“5” = IMP gl/h 
“6” = BTU/h 
“7” =  litres/h 
“8” = kPa (gauge) 
“9” =  kPa (absolute) 
“10”= mcf/h 
“11”= none 
“12”= mcf/h 
“13”= MW 

“0” =  Electricity  
“1” = Gas 
“2” =  Water 
“3” =  Thermal (Deprecated) 
“4” = Pressure 
“5” = Heat 
“6” = Cooling 

“set general font_controller ReportingInterval null”, 

Basic composition of a config file

{ 
“config”: [ 

(COMMANDS INSERTED HERE) 

null], 

“end” : [] 
} 

How each line is built?

general 

account1 
account2 
account3 
account4 
account5 

font_controller 
font_account 
metering 

ReportingInterval   < used with font_controller 
ZigbeeAllowJoining  < used with font_controller 
AwaitingConfiguration < used with font_controller 
AccountActive  < used with font_account 
PrimaryRelay   < used with font_account 
SecondaryRelay  < used with font_account 
ShutOffMode   < used with font_account 
ReportingInterval  < used with font_account 
UnitOfMeasure  < used with metering 
MeteringDeviceType  < used with metering 
AccountActive  < used with font_account 
AccountActive  < used with font_account 
AccountActive  < used with font_account 
AccountActive  < used with font_account 
Meter    < used with font_account 

Quick Fault Diagnosis sheet