MHUB-OS 8 and uControl 2 update troubleshooting and FAQ

Below is a list of three issues which have been reported to HDANYWHERE (HDA) after updating older systems to MHUB-OS 8 (MOS 8). If you have encountered any of these problems then you will find a solution below. If your issue is not shown below then contact the HDA support team via email on – support@hdanywhere.com.

Jump to issues and solutions:

  1. My MHUB is stuck in a loop and is always prompting me to update again – I can not access any other MHUB-OS page.
  2. I am having problems connecting with HDA Cloud because there is an error with my serial number.
  3. I have connected to my MHUB and all my settings are gone.
  4. I can’t get uControl to connect to MHUB.
  5. I have an 8×8 system and I can not control my TVs anymore.

1.
I’ve clicked the update from within MHUB-OS and now appear to be stuck on an update page and cannot access any other MHUB-OS page.

This error can occur when MHUB fails to complete the update process completely. This can be caused by a power outage, multiple sessions of MHUB-OS being open at the same time (browser tabs, app) or network issues as the update is applied to MHUB. This has been patched in version 8.02 of MHUB-OS. However, if you find yourself with a problem like this, you will need to contact HDANYWHERE technical support services by emailing support@hdanywhere.com with the subject line: “Update error code:728″ and we will treat this with the highest priority.

2.
I’ve updated to MHUB-OS 8 and when linking to HDA cloud it says there is an error with my serial number.

This error can occur when the MHUB cannot connect with HDA cloud. This can be caused by network issues or power outage. This has been patched in MHUB-OS version 8.02. However, should you find yourself in this situation you can recover the serial number following these steps

  1. Step 1 – Load a web browser on a pc or mac(such as Chrome), and enter the following in to the URL bar [MHUB IP ADDRESS]/diagnostics.php. Then click on “GET SERIAL NUMBER”
  2. Step 2 – Confirm that you want to change the serial number
  3. Step 3 – You will get a notifcation saying that the serial number has been updated, and should notice the serial number is showing in the system information section near the top of the page.

If after using the serial number recovery method above, it still does not appear, you will need to contact HDANYWHERE technical support services by emailing support@hdanywhere.com with the subject line: “Update error code:628″

3.
uControl has updated, when I reconnected to my MHUB all my settings were gone.

This can occur when reconnecting to your MHUB after uControl has updated to version 2 or greater and selecting the incorrect option. When uControl loads you are shown 2 options:

  • “SETUP A NEW MHUB SYSTEM” – This is used when you are connecting to a brand new or unconfigured MHUB system. If you select this option and have a previously configured system, all user data will be removed requiring the MHUB to be fully reconfigured like a new system.
  • “CONNECT TO AN EXISTING MHUB SYSTEM” – This is used when you are connecting to a previously configured MHUB system. Existing data will remain untouched, and uControl will sync the data stored. If you were connected with a previous version of uControl this option should be used.

4.
After the update, uControl can not connect to MHUB

HDANYWHERE released an update to uControl and all MHUB systems on Wednesday 10th October 2018. To ensure that your MHUB works correctly both your MHUB and uControl must be on the correct software version.

MHUB / MHUB-OS = version 8 or above
uControl (iOS / Android) = version 2 or above

If you find that one version of uControl can connect to MHUB and the other can not then it is very likely that you did not complete the update to MHUB-OS. As soon as you have run this process then uControl should work on all devices with no issue. For this solution HDANYWHERE are assuming that your system is already in a pre-configured state and that you are wanting to CONNECT TO AN EXISTING SYSTEM.

Steps to resolve this issue:

  1. Ensure that you have the latest version of uControl installed on your iOS or Android device. Download uControl for iOS or download uControl for Android
  2. Once you have the app installed, please load it up and follow the instructions here:

5.
I have a 8×8 or 8×6+2 system and after the update, I lost the ability to control my TVs

If you are able to control your source devices with uControl but can not control your displays then a quick update to your MHUB will resolve this problem. Instructions detailing how to update your MHUB can be found here. Ensure that you use uControl to update your MHUB and do not try to update your system via MHUB-OS.

MHUB-OS 8: a quick guide to zones

Zones define a physical space in a property where outputs from MHUB terminate.

A Zone can include a maximum of 1 video output and a maximum of 4 audio outputs. For example, you can create a zone called “Kitchen” and assign 1 video and 1 audio output to it to provide you with viewable TV and sound. A Zone must contain at least 1 output from an MHUB for it to be addressable for control. Note: outputs can not be shared or split to more than 1 Zone.


MHUB zones

MHUB-OS 8 first boot process

The first boot process for MHUB-OS has remained largely unchanged with the exception of zones.

The slideshow below walks you through the steps within MHUB’s first boot process and how to setup zones to refect the different rooms or areas within you property.

You should be able to complete the process in under 10 minutes.

MHUB-OS first boot steps are as follows:

  1. EULA and Privacy policy
  2. Check for recent MHUB-OS updates
  3. Name your MHUB
  4. Name your source devices
  5. Create zones
  6. Assign outputs to zones
  7. Confirm zones
  8. Connect MHUB to HDA Cloud
  9. Complete setup

HDANYWHERE(HDA) recommends that every MHUB install goes through its first boot process to ensure that the MHUB is setup correctly.

How long does the process take to complete

If you have an update to install then then first boot usually take about 10 minutes. If there is no update you can normally finish the entire process and have an operational MHUB system well within 5-7 minutes.

Yes. You do not need to access MHUB-OS if you don’t want to. But this is only recommended if you intend to control you MHUB via a control system. You will also miss the opportunity to increase your warranty period and open your MHUB to additional features or services.

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

Yes. You do not need to access MHUB-OS if you don’t want to. But this is only recommended if you intend to control you MHUB via a control system. You will also miss the opportunity to increase your warranty period and open your MHUB to additional features or services.

I made a mistake in the first boot process, can I go back or make a change?

Yes. You can go all the way back to the update step and correct any incorrect information you entered. Alternatively, you can also access MHUB-OS (after you have completed first boot) and change anything then.

Updating MHUB-OS to a new 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. All updates are now handled by uControl. Please ensure you have installed the latest version.

If you have not connected to your MHUB before, please follow this guide first – Connecting to a MHUB

If you have received a notification in uControl or by email that an update is available for your MHUB then chose the correct option below:

Updating to MHUB-OS 8.00

If your version of uControl updates to version 2 automatically, any previous connection to your MHUB will be reset. This is normal and part of the update process.


update-mos

Follow the instructions within the app to connect back to your system. During this process uControl will check MHUB(s) to see if they also require updating. At that point you will be presented with two options:

If you are setting up a new MHUB system

This is likely to happen if you have recently bought MHUB and it was shipped to you on older software. You will run through the following steps:

  1. Click ‘Setup a new MHUB system’, uControl will scan your network for any MHUB systems
  2. Select your MHUB device
  3. Connect to your MHUB
  4. Perform first boot process which may or may not include update depending on the MHUB-OS version installed before it shipped to you.

Watch a video of it here:



Connecting to an existing system

The majority of MHUB customers will be on MHUB-OS 7 and their systems will contain user data which needs updating to the latest version. If this is you then follow these steps.

  1. Click ‘Connect to an exisiting MHUB system’, uControl will scan your network for any MHUB systems
  2. Select your MHUB device
  3. Connect to your MHUB
  4. uControl will show popup message that MHUB-OS requires updating, click ‘update’ and follow on screen prompts

Updating an existing system

Open the uControl app

Visit the settings page in the uControl app and click on the “ADVANCED”, then select “FORCE MHUB UPDATE”

update

You will then shown the update screen as shown below. Once the update is complete you will be taken back to the uControl interface

update2

Updating an New system

When connecting to a MHUB for the first time, uControl will check if it requires updating. If there is an update available, it will be applied as part of the configuration process, and these screens will be displayed.

update3

Having trouble updating your MHUB, check here -Update Troubleshooting

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.

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

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.
  • Your Android or iOS device is connected to the same network as your MHUB
  • You have downloaded the latest version of uControl from the relevant app store

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.

    1a

  1. Open uControl and press the ‘SETUP A NEW MHUB SYSTEM’ button. uControl will now search your network for any MHUB devices.
  2. uControl will show relevant options. Press ‘CONNECT TO’ MHUB4K44PRO/MHUB4K88PRO/MHUB4K431/MHUB4K682/MHUBPRO4440/MHUBAUDIO64
  3. The app will now check the status of the unit, This can take upto 10 seconds, then it will show the screen ‘CONTINUE SETUP ON MHUB DEVICE’
  4. This will take you to the First Boot process on MHUB-OS where you will setup your system – First Boot Process
  5. After the first boot process is completed you will be shown the following screen. Click ‘ACCESS UCONTROL’ and you will be taken to the main uControl interface.
  6. 1b

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.

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

How to disable the beep on mHub 2K and 4K (4×4 and 8×8)

To disable the beep on the mHub 2k range of matrices please following the instructions below using either I.P or RS232 connection methods.

To adjust the settings on the mHub range of products, you will need to download the controller software Download

 A) Connecting to the mHub Via I.P

The mHub 2K’s IP address is pre-configured as 192.168.0.100, your computer will need to have it’s IPV4 range configured to be within the same range initially while you setup the matrix. (You don’t need to follow this step if you have a mHub 4K system)

To configure your IPV4 settings you will need to navigate to the following menu

->Network and sharing center

—>Ethernet
—–>Properties
——->Internet Protocol Version 4 (TCP/IPv4)
———>Properties

IPV4

Once you have changed the IP settings on your PC, open the Mhub controller software.

In the Control Mode Select Box choose ‘IP’, then click the ‘Search’ button. When the IP address shows in the mHub IP box, click connect.

 

B)  Connecting to the mHub Via RS232

To connect via RS232 use the supplied serial cable can connect between the mHub and your PC, then on the Controller software select ‘RS232′, then in the RS232 Options section select the Com port being used from the drop down menu then click connect

Capture

 

C) Disabling the Beep

To disable the beep select the ‘Control’ tab and untick the box labeled ‘Enable Feedback Beep’.

mHubbeepimage

Once changed, you can verify the beep has been disabled by performing a source switch operation.

mHub 2K control system integration

The mHub 2K 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 – mHub Control Pack

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

The mhub 2K’s IP address is pre-configured as 192.168.0.100, your computer will need to have it’s IPV4 range configured to be within the same range initially while you setup the matrix. To configure your IPV4 settings you will need to navigate to the following menu

->Network and sharing center
—>Ethernet
—–>Properties
——->Internet Protocol Version 4 (TCP/IPv4)
———>Properties

IPV4

Configure your settings as shown in the image, this will change your computer IP range and you will temporarily lose internet connectivity (if your previous IP range was different from this)

Once you have changed the IP settings on your PC, open the Mhub controller software

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

Change the IP configuration to manual (static), and then enter an IP address within your home network range that is not currently being used and then click ‘Set IP’.

You can now go back into your IPV4 settings and set them back as they were before (obtain an IP address automatically)

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 4K information, go here – mHub 4K