MHUB-OS Firmware 1.30 update – Complete

The first part of this update roll-out has now been completed. Any new MHUB’s connected to the internet will automatically upgrade when the unit is powered on, this may extend the boot time by 30 seconds

 MHUB Firmware 1.30

HDA Cloud is moving to a new & more sophisticated server.
This will automatically start at 8:00am (BST) Monday 30th July.

HDA Cloud is our secure online portal that allows you to remotely access any network-connected MHUB system around the world. It allows you to remotely manage, configure, and troubleshoot installations to help keep your systems running smoothly.
Perhaps most importantly, HDA Cloud is our central data storage server and we take our responsibility to keep all data super safe and secure very seriously. As such, we have provisioned the very latest server technology and security for a faster and more secure connection. Additionally, the platform will enjoy new features and upgrades which will be revealed soon!

The update will come in two stages; first, we will update MHUB systems around the world and after that is complete we will move HDA Cloud to its new home. You will not need to do anything. MHUB systems will update in the following order:

MHUB systems

MHUB MAX (4×4) – Monday 30th July 2018 – Complete
MHUB PRO (4×4) 40 – Wednesday 1st August 2018 – Complete
MHUB (8×6+2) – Wednesday 1st August 2018 - Complete
MHUB (4×3+1) – Thursday 2nd August 2018 - Complete
MHUB PRO (4×4) 70 – Friday 3rd August 2018 – Complete
MHUB PRO (8×8) 70 - Friday 3rd August – Complete

HDA Cloud Migration - Monday 6th August

– Complete
During this migration, HDA cloud will be unavailable. Starting at 10.00am UTC for 4 hours.

In most case’s this is a background update and should not require any user interaction. However, some systems may need a manual hard reboot (full mains power down for 10 seconds, then reconnect) to apply the update. MHUB video operation will function, but if you notice MHUB control (uControl/MHUB-OS/control system) is not responding, perform the above reboot.

 

To confirm that the unit has been updated either check in MHUB-OS on the MHUB setup page or check on HDA Cloud

EDID management on MHUB PRO systems

The PRO range of MHUB systems offer advanced EDID management from within MHUB-OS and from the units front panel. EDID management is an important facet of installing a whole home AV system, and improper configuration will result in a system that doesn’t operate at full capabilities. More and more source devices are limiting there selectable output resolutions based on the EDID they read from the display, as such you may find without proper EDID management that your devices won’t offer you the display resolutions and audio formats you want.

EDID (Extended Display Information Data) data exchange is a standardized means for a display to communicate its capabilities to a source device. The premise of this communications is for the display to relay its operational characteristics, such as its native resolution, to the attached source, and then allow the source to generate the necessary video characteristics to match the needs of the display. This maximizes the functional compatibility between devices without requiring a user to configure them manually, thus reducing the potential for incorrect settings and adjustments that could compromise the quality of the displayed images and overall reliability of the system.

EDID information looks something like this:

(20) Video Input Definition: Analog
0.700, 0.000 (0.700 V p-p)
Separate Syncs, Composite Syncs, Syncs on Green

(21) Maximum Horizontal Image Size: 62 cm
(22) Maximum Vertical Image Size : 34 cm
(23) Display Gamma : 2.20
(24) Power Management and Supported Feature(s):
Active Off/Very Low Power, RGB Color, Non-sRGB, Preferred Timing Mode

(25-34) Color Characteristics
Red Chromaticity : Rx = 0.626 Ry = 0.337
Green Chromaticity : Gx = 0.306 Gy = 0.626
Blue Chromaticity : Bx = 0.156 By = 0.057
Default White Point: Wx = 0.313 Wy = 0.329

(35) Established Timings I

720 x 400 @ 70Hz (IBM, VGA)
640 x 480 @ 60Hz (IBM, VGA)
640 x 480 @ 67Hz (Apple, Mac II)
640 x 480 @ 72Hz (VESA)
640 x 480 @ 75Hz (VESA)
800 x 600 @ 60Hz (VESA)

(36) Established Timings II

800 x 600 @ 75Hz (VESA)
1024 x 768 @ 60Hz (VESA)
1024 x 768 @ 75Hz (VESA)
1280 x 1024 @ 75Hz (VESA)

(37) Manufacturer’s Timings (Not Used)

(38-53) Standard Timings

1920×1080 @ 60 Hz (16:9 Aspect Ratio)
1280×1024 @ 60 Hz (5:4 Aspect Ratio)
1280×960 @ 60 Hz (4:3 Aspect Ratio)
1440×900 @ 75 Hz (16:10 Aspect Ratio)
1440×900 @ 60 Hz (16:10 Aspect Ratio)
1680×1050 @ 60 Hz (16:10 Aspect Ratio)
1280×720 @ 60 Hz (16:9 Aspect Ratio)

However, this becomes much more complicated in situations with multiple displays such as a splitter or a video matrix, this is because the device in question must now decide on a single EDID to present to a source device from the available displays. Normally this will be the lowest common denominator, which is ok for initial setup as it will guarantee you have video/audio in all locations.

Image to be added

However, this may not be the desired result long term. This is where EDID management becomes important. EDID management is the process by which you manually select the EDID you wish to be presented to each individual source device, this ensures you get the desired Video/Audio output from each connected source device and utilise your system to the maximum of its capabilities.

This menu can be accessed via the AV Settings menu in MHUB-OS

Edid 1

This menu contains 2 main types of EDID, Pre-Defined EDIDS such as

4K2K60, Stereo Audio 2.0, HDR

This would present a source device with a ‘display’ capable of 4K video with HDR enabled and 2.0 channel audio. Alternatively, MHUB-OS has the ability to copy an EDID from a connected display. Currently, this is only possible via the HDMI mirror ports. This will make the connected source devices behave as if they are only connected to the chosen copied output.

Updating MHUB-OS to the latest version

If you have received a notification in uControl or by email that an update is available for your MHUB-OS then follow these steps to update your system.

Go to MHUB-OS interface

There are two ways to achieve this:

  1. From MHUB-OS Press the “MENU” button on the front of the MHUB for 5 seconds, wait for the IP address to appear, then enter that IP address (usually something like: http://192.168.1.240) in to any web browser on the same network.
  2. From uControl Visit the settings page in the uControl app and click on the “DASH” (now called “MHUB-OS”) to be directed to the MHUB-OS interface.

Updating MHUB-OS to the latest version

update-process

  1. Click on the menu bar at the top of the page, this will reveal MHUB-OS’s navigation menu
  2. Click on “MHUB SETUP” in the menu
  3. Find a the section at the top of the page called “MHUB” (from this area you can also check what version of MHUB-OS is installed).
  4. Underneath that section there will be a button labelled “Check for updates” (see image). Select that option.
  5. MHUB-OS’s installation wizard should start. Follow the instructions to update MHUB-OS.

MHUB-OS first boot process

Make sure MHUB is connected up correctly before starting the first boot process on MHUB-OS

HDANYWHERE(HDA) recommends that every MHUB install goes through its first boot process to ensure that the MHUB is setup correctly. Please follow the quick start guide (inside MHUB packaging) to make sure your MHUB is connected correctly to your source devices, displays and has an active network connection before proceeding.

I don’t want to use MHUB-OS or go through the first boot process, will MHUB work like a normal matrix?

Yes. You do not need to access MHUB-OS if you don’t want to. MHUB will work distributing video as normal and will be controllable using the included remote controls. Please note that you will not be able to access advanced features such as voice control, the uControl app or build Sequences.

Accessing MHUB-OS (MOS)

There are two ways to access MOS:

  1. Download our app, uControl, from the iOS or Google Play Store and let it find MHUB (and run you through the first boot) for you
  2. Go to your MHUB and press and hold the “MENU” button for 5 seconds to reveal its IP address. Make a note of it then put that address in to any web browser on the same network. You will be forwarded to the first boot process.

First boot process

FIRST-BOOT1

  • BEFORE STARTING:Read and agree to the End User Licence Agreement (EULA) and Privacy Statement
  • First Boot Step 1 – Check for MOS updates

    This is where your MHUB requests available updates from HDA cloud so your unit will update to the latest version. This is done before proceeding.

  • First Boot Step 2 – Name your MHUB
    Here you can give your MHUB a personal name, this can also be used to differentiate multiple installations by HDA Pro’s
  • First Boot Step 3 – Name your sources/inputs
    On this page you can label your input devices, such as Sky, Apple or Tivo. These labels are used in the uControl app and with voice control. Please go here for best practices when adding names. [Best Practices]

FIRST-BOOT2

  • First Boot Step 4 – Name your Displays/Rooms/outputs
    This page is similar to the previous step. You can choose to label them as display manufacturers or room names. Again please follow best practice guidelines available here – [Best Practices]
  • First Boot Step 5 – Turn update notifications On/Off
    MOS updates are released periodically, here you can choose to be notified when an update is available

FIRST-BOOT3

  • First Boot Step 6 – Create or link your MHUB to a HDA cloud account, read and agree to our Terms and Conditions
    MHUB4K(3rd gen) and MHUB4KPRO units can be linked to a cloud based account. When registering as a homeowner this enables a couple of things. Firstly when you register, your warranty period is extended by 1 year, in addition to that cloud access is required when using the uControl IRengine feature allowing you to control source and display devices. Cloud access is also required for voice integration. For a HDA PRO the cloud account allows you to manage your MHUB installations remotely, getting system information as well as a host of other features.
  • First Boot Step 7 – Secure MHUB with a PIN number
    If you wish you can lock local access to MOS stopping any unwanted configuration changes from being made.
  • First Boot Step 8 – Complete First Boot Setup
    Once you have completed the first boot process you can either ‘COMPLETE SETUP’ and go to the MOS DASHBOARD pag, . or goto the uControl page to start adding device/source control. For more information on uControl go here uControl

What is the difference between a HDA Cloud & a HDA Pro account?

^8225B169363E3009548C8F63CF73AC706CD60A0AA3F3C02D7A^pimgpsh_fullsize_distr

1. HDA Cloud

The HDA Cloud acts as our global data storage and service delivery platform offering an interface for MHUB owners, HDA Pro’s and 3rd party devices to talk to one another.

There are two types of cloud account that can be associated with an MHUB system.
account-types

2. HDA Cloud Account

The HDANYWHERE (HDA) Cloud account is the account that belongs to the Homeowner and/or End-User. The owner of the MHUB has to have a verified HDA Cloud account before any communication between MHUB systems and the HDA Cloud can take place.

Registering the MHUB system provides numerous benefits including:

  • Extending the warranty period on the system by 1 year (must be registered within 30 days of purchase, Warranty is non-transferable)
  • Enables advanced functions for things like voice control, uControl, integration with other IoT devices and Sequences
  • Provide advanced troubleshooting information to your HDA Pro installer and HDA
  • Provide your HDA Pro installer permission to remotely manage your system, they can then modify your system for you without physically being there

3. HDA Pro Account

The HDA Pro account can not be added to a unit unless a HDA Cloud account (outlined above) is present first. This account authorises the installer to monitor the MHUB on their customer’s (the homeowner) behalf. This account sits alongside the Cloud account and gives a 3rd party access to the MHUB’s data and the ability to control it. HDA Pro’s can register Here

The following Settings can be managed remotely:

  • Source Routing (and switching)
  • Edid management
  • uControl sequence configuration
  • uControl IR pack configuration
  • Power management
  • You can also monitor the following:

  • IP configuration
  • Temperature
  • Firmware (MHUB-OS, and MHUB)
  • IMPORTANT: a HDA Pro Account has to be created first Here and authorised by HDA staff before the installer can use their account details to enable monitoring on the MHUB.

4. MHUB-OS

MHUB’s operating system which acts as the bridge between using MHUB and managing it. From MHUB-OS it is possible to connect to HDA Cloud, integrate devices like Amazon Alexa, manage network settings and update software to add new features.

5. uControl

uControl is our remote control app for MHUB 4K PRO systems. It pulls all the information it needs to work directly from MHUB-OS and requires no setup or configuration. Just download it and let it find your MHUB and you’re ready to go.

Voice control with Amazon Echo using the “MHUB 4K PRO Control / MHUB 4K PRO Smarthome” Skill

Setting up the MHUB 4K PRO Control / MHUB 4K PRO Smarthome Skill on the Alexa app

HDANYWHERE (HDA) Amazon Alexa App Skill

We are assuming that you have already downloaded the Amazon Alexa app and have a functioning Amazon account.

Skill types:
There are two types of skill which you can enable on the Alexa app.

  • Custom Skill
    With a Custom Skill we have full control over the voice interaction (a voice interaction is the communication you have with an ECHO device when speaking a command and also includes the response given by the ECHO) between you and your Echo device, this allows for a greater range of voice commands including playhead, change channel, switch sources, increase/decrease volume.Click here to view a the full range of voice commands.
  • Smarthome Skill
    The Smarthome skill differs from the custom skill in a couple of ways. Firstly, invoking a smarthome skill is fixed and defined by Amazon, this also applies to the voice interaction. We currently support on/off commands, allowing you to perform actions quickly by uttering “Alexa, turn on TV” or a custom label like “Alexa, turn on movies”.
  • You can of course, use both. They are FREE!

What you need to get your MHUB to respond to voice commands:

  1. You have completed the first-boot procedure within MHUB-OS
  2. You have MHUB-OS version 7.0 or higher installed on your MHUB
  3. You have an active HDA Cloud account
  4. You have downloaded uControl packs for all displays and source devices you want to control
  5. You have an active Amazon account
  6. You have an Amazon Alexa enabled device, such as Amazon Dot/Echo/Show

Linking the custom skill “MHUB 4K PRO Control”

  1. Go to the Skills section on the Alexa app and search for “MHUB 4K PRO Control”
  2. Click on the skill and select “Enable”
  3. Click “Link Account” – when you do this, you will be redirected to HDA Cloud’s secure login page. Enter your username and password in to the fields.

To enable the MHUB 4K PRO Control Skill you will need to add the skill first by pressing the "Enable" button in your Amazon Alexa app. Once enabled you will be forwarded to HDA Cloud to link your account with Amazon Alexa. Enter your HDA Cloud username and password and your MHUB will be connected to Alexa!

Linking the smarthome skill “MHUB 4K PRO Smarthome”

  1. Go to the Skills section on the Alexa app and search for “MHUB 4K PRO Control”
  2. Click on the skill and select “Enable”
  3. Click “Link Account” – when you do this, you will be redirected to HDA Cloud’s secure login page. Enter your username and password into the fields.
  4. After the account has been linked, visit the “Smart Home” screen then navigate to the ‘Manage devices in Smart Home’ then Devices. Next click ‘Discover’.
  5. This action will communicate with MHUB and pull any devices making them ready to use.

Configure voice commands to do exactly what you want

Let’s take the command “Alexa, tell my TV to watch football” as an example.

It might appear like a very simple command but there are a number of things that need to happen in order to watch football! First the TV might need to turn on, but in which room? The volume might need to be set to a desired limit. The correct source input might need to be selected on MHUB and finally that source will need to navigate to the channel hosting the football.

You can configure all those actions in what we call a “Sequence”.

Taking the example above:
Alexa (this wakes up your Amazon Dot/Echo/Show)
tell my TV to… (this invokes HDA’s custom skill)
watch (this is a special function which tells MHUB to start a Sequence)
football (this is your custom name for the Sequence, it can be anything you want)

Inside MHUB-OS we can configure exactly what “football” does.

  • You can select if you want MHUB to turn your TV on and adjust the volume
  • You can tell MHUB to switch to the source device with has the football on it
  • You can instruct MHUB to change the channel on that source device

Read more about Sequences and Scheduling.

Here’s a table of all the commands you can tell your MHUB to do…

Now you’re ready to go. Take a look at a full list of commands that you can say to your Echo.

Creating and Editing Sequences

Sequences allow your MHUB to make more complex things happen. For example, a single command could be setup to Turn on a TV, switch to your Satellite box and enter the number keys for a movie channel. These sequences can be triggered in a number of ways to provide a better user experience for MHUB owners.

Sequences are setup within MHUB-OS via the ‘Sequences and Scheduling’ page. They can also be setup remotely via the HDA Cloud (Currently only available for HDA PRO’s, coming soon to end users)

1

Within this page you can see and edit your current sequences. You can also test all your sequences to make sure they are functioning correctly.

To create a new sequence click the ‘Create New Sequence’ button.

2

The first part of the Sequence Creation page contains several naming fields which serve different purposes. They are:

Sequence name – This is the name that will be displayed within MHUB-OS
Description – Provide a short description of the sequence so you can see what it does at a short glance
uControl label – This is how the sequence will be labelled within the uControl app
Voice label – This is where voice control (such as Alexa) reads the title of the sequence so it can be triggered. You may find if you are struggling to trigger a particular sequence by voice that you can improve the function by changing the title that your voice control device is listening for.

The next section contains the tools to build your sequence using the available parameters

Command Type

Switch – Execute a simple switching command, first define the input and then the output you would like it switched to
Source – Deliver a command to a source device via the IR engine. This can be something simple like a ‘play’ command or something more complex like a ‘Go to channel command’ (a ‘Go to channel command’ delivers sequential number inputs so you can direct a TV receiver to a specific channel)
Display- Deliver a command to a connected display (or projector) such as ‘Power on’ or ‘Volume up’
Audio – Will integrate with “MHUB Audio”
Delay – Add a delay between one command and the next (Time in milliseconds to wait, eg. 500ms = 0.5 sec)

You can either choose to save the command or add ‘another command’ to create a more complex scenario. For instance, in the following example, we have first a “source switch” followed by a “Go to channel command” with a 500ms Delay.

3

Installing, configuring & using uControl on iOS & Android

uControl is HDANYWHERE’s free remote control app and is available for iOS and Android mobile platforms. Below is a guide to configuring and then using uControl.

Checklist:

  • Your MHUB is powered on and connected as per the quick start guide (inside MHUB packaging) to make sure your MHUB is connected correctly to your source devices, displays and has an active network connection before proceeding.
  • You have completed the MHUB-OS first boot process. Not done this yet? Go here for a guide – MHUB-OS First Boot Process
  • Your android or iOS device is connected to the same network as your MHUB

Connecting to your MHUB with uControl

Before using uControl, it needs to be linked to your MHUB. Please follow the instructions below on how to do this.

  1. Download and install the app from the appropriate app store for your device.
  2. setup-1-2
    setup3a

  3. Open uControl and press the ‘START SEARCH’ button. uControl will now search your network for any MHUB devices.
  4. Any MHUB devices found will now be shown. Press ‘CONNECT TO’ MHUB4K44PRO/MHUB4K88PRO/MHUB4K431/MHUB4K682
  5. The app will now attempt to pair with the selected unit, This can take upto 10 seconds. Once connected to your MHUB, Press ‘COMPLETE SETUP’.
  6. uControl is now linked to your MHUB.

Using uControl

After uControl is paired with your MHUB you can start to use it to control your device

Source switching on uControl

Source switching is performed by swiping left or right on the input bar and tapping on the required input. When input names are configured on MOS\MHUB SETUP page they will be reflected here.

To change to a different output, tap on the menu icon, and select the desired output from the popout menu, once again any output names configured on the MOS\MHUB SETUP page will be reflected here.

Using uControl to control source and display devices

To enable uControl to control your source or display devices, an IR pack is required and must be installed on your MHUB. This IR pack contains all the relevant information including a screen layout for uControl.
setup4a
To install an IR pack navigate to the settings menu by pressing on the MENU icon, and tapping on SETTINGS located at the bottom off the pop-out menu. This will bring up the setting page, tap on DOWNLOAD UCONTROL PACKS. this will take you to the UCONTROL page on MHUB-OS.
56
78

  1. Using the drop-down menu, select which source or display you wish to install the IR pack for, This will bring up an expanded menu
  2. Click DEVICE TYPE to select the type of device that will be connected to the chosen port.
  3. Next click DEVICE MANUFACTURER and select the make of your device from the list and click on DOWNLOAD UCONTROL PACK – This will load two test commands from the downloaded IR Pack to confirm the commands are working as expected.
  4. Follow the onscreen instructions to test the two commands
  5. If the commands work as expected click YES to complete the process. If they do not, click NO and repeat step 4 until you find commands that work

Repeat the above steps until all required IR packs are installed. Once complete, click DONE on iOS or the back button on your android device

When an IR pack has been installed the uControl area of the screen is populated with the source device interface. These are device specific. Some control packs have multiple interface screens which can be navigated to by swiping left or right.
ucontrol-control-types

  • Gesture Control – This is where you navigate your devices menu or guide using one or two finger gestures or motions on your mobile device, the majority of the screen is filled with the ‘Gesture control area’
  • Navigation Control – This mirrors a conventional remote control, with individual buttons for navigation.
  • Playhead Control – This screen contains common functions used when viewing a recorded source or watching a bluray. Such as Play, pause, fast forward and rewind.
  • Numeric Keypad – This screen shows a 0 to 9 keypad for entering channel numbers etc.
  • External App – This allows uControl to open external applications such as Sonos.

When using gesture controls the following gestures are supported
gesture-function

  1. Navigation – single finger swipe up, down, left or right
  2. Enter – single finger tap
  3. Play/Pause – two finger swipe up to play, two finger swipe down to pause.

Control Drivers for MHUB Series (IP / RS232) MHUB2K/MHUB4K (2016/2017)

Control Drivers for the MHUB Family (IP / RS232 / IR) – MHUB2K44 MHUB2K88 MHUB4K44 MHUB4K88 MHUB4K431 MHUB4K862 MHUB4KPRO44 MHUB4KPRO88

We have ready-made control system drivers available for MHUB series systems for all the major control systems.

These can all be found in our control pack which can be downloaded Here

Also included in this are the raw IP and RS232 strings so you can create custom drivers and commands for MHUB.

If you have an older MHUB system (2-15 or older) or Modular System, then you can find the drivers below.

Control4 (IP Driver)*

Crestron (IP Driver)*

AMX (IP Driver)*

RTI (IP Driver)*

* -For mHub 4K (2015) please use Modular 4×4 driver

XTND 2K (30) Short run adjust settings (XTND2K30)

If you find that you have no picture or poor picture quality, you may need to adjust the EQ settings on your XTND 2K30 based on the approximate distance of your cable run. If you have any patch points add an additional 10% onto your effective distance. The below diagram shows the correct switch settings for various lengths of cable run. We suggest working from the maximum distance and working down if you are unsure of the length of your cable run.

Error Message: ‘The application has failed to start because its side-by-side configuration is incorrect’

Description

When I try to install the software, I receive this warning:

“The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail.”

This issue is typically caused by a conflict between the program and one or more of the files in the C++ runtime libraries. These libraries are part of the Windows operating system and are used, and potentially updated, by installing or updating several Microsoft or other third party products.

If you are experiencing this error when launching or installing the program, and if the program repair option does not resolve the issue, the most effective method to correct this error is to uninstall and reinstall any Microsoft Visual C++ installations currently available on your computer before proceeding with the installation.

To uninstall all current Microsoft Visual C++ installations

Open the Control Panel and locate the list of programs.

Windows 8/10
From within the Start screen, type “Control Panel” and click on the Control Panel search result when it appears.
Select Programs and Features.

Windows 7/Vista
Click Start> Control Panel
If viewing categories, click Programs> Uninstall a Program
If viewing icons, click Programs and Features

Windows XP
Select Start> Control Panel> Add or Remove Programs

Scroll down to locate the Microsoft Visual C++ entries.

Select each one, starting from the top entry, and choose Uninstall.

Do this for each entry, until there are no more Microsoft Visual C++ entries listed.

To reinstall new Microsoft Visual C++ packages
Click each of the following links in order. If prompted, choose to Run the download to install each Microsoft Visual C++ Redistributable Package.

Microsoft Visual C++ 2005 Redistributable Package (x86)
Microsoft Visual C++ 2005 Redistributable Package (x64)
Microsoft Visual C++ 2008 Redistributable Package (x86)
Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)
Microsoft Visual C++ 2008 Redistributable Package (x64)
Microsoft Visual C++ 2008 SP1 Redistributable Package (x64)
Microsoft Visual C++ 2010 Redistributable Package (x86)
Microsoft Visual C++ 2010 SP1 Redistributable Package (x86)
Microsoft Visual C++ 2010 Redistributable Package (x64)
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
Microsoft Visual C++ 2012 Redistributable Package (x86/x64/ARM)
Microsoft Visual C++ 2013 Redistributable Package (x86/x64/ARM)

Once every package has been downloaded and installed, restart Windows.

Finally, launch the program. If the error message persists after following all of these instructions, then please contact HDanywhere technical support on 01684 576348

A basic guide to troubleshooting video issues

If you find yourself encountering issues with the picture (either poor quality or no picture) then the following list of common problems and solutions will help you diagnose the problem.

Power – Check that both the matrix and the receivers are fully powered. The front panel of the matrix should be illuminated* and the power light on the receiver should be on. If the receiver isn’t powered try an alternate power supply from another receiver that you know works. Alternatively if you’re using the USB power supplies double check that the USB port you are using is supplying the appropriate current.

Is your transmission distance too long? – If you have a power light but the lock light isn’t illuminated this can indicate an issue with the signal strength. The maximum transmission distance for the mHub 2K range is 50m in best case scenarios, and 100m for the mHub 4k Range. The transmission distance can be reduced by several factors, most commonly Wall plates, patch panels and stranded patch leads can significantly reduce signal strength and potentially reduce the maximum distance the matrix can transmit signal. Whenever possible you should try to use a straight point to point connection to guarantee maximum distance.

Resolution – Check that you are using compatible resolutions between your source devices and displays, in particular you should be looking for situations where a TV is perhaps older than the rest of your displays and doesn’t support the same video formats (for instance it only supports 720p) Try reducing the resolution on your source devices and see if this fixes the issue. Also, if reducing the resolution causes picture to appear again this can point to an issue with the bandwidth which can be addressed by reducing the transmission distance.

Snow/Sparkly picture – This is most often seen when the matrix is failing to fully establish a connection with the receiver. Your first step should be to use another working location to verify the integrity of both the receiver and output on the matrix. Once you are happy both the receiver and matrix output are working you should take a look at all your cables. Check that your RJ45 connectors are properly terminated to 568B standards and try swapping out the HDMI cables for ones from working locations.

* – with the mHub family of products, If the unit has been idle for 5 minutes the panel may have gone into power saving mode

mHub 4K control system integration

The mHub 4K range has full support for most popular control systems via serial (RS232) or IP.

All control strings and current available drivers are available in the mHub control pack, available here – Download
IP control

To control the mHub 4k unit via IP you will first need to discover it by using the mHub controller software available in the control pack above

The mHub 4K will acquire an IP address via DHCP the first time it is connected to your home network, use the controller software to locate it on your network.

mhub controller pic 1

In the mHub controller software select IP and then press the ‘search’ button, this should locate your mHub matrix. Press ‘connect’ the red button should turn green.

Press the configure button

mHub IP

From here you can set the matrix to a static IP if you wish (this is generally good practice)

Your matrix is now on your home network and will be able to receive IP commands from whatever control system you are using.

Looking for the mHub 2K information, go here – mHub 2K