Issues & Fixes


We're working on it...

We strive to provide products that offer the most accurate and reliable timecode solutions on the market. Unfortunately, from time to time things go wrong, and when this happens we work hard to provide solutions as quickly as possible.

On this page, we share known faults that our development team are currently working on, along with suggestions on how to avoid these issues occurring or to minimise the impact caused by a fault until an update is released.

We encourage all users to report any issues with our system as soon as they are noticed. You can report a fault using the link on this page, which will ensure it is flagged with our development team promptly.


No current device faults

Noticed a problem with this product? Please report the fault here.

UltraSync BLUE

No current device faults

Noticed a problem with this product? Please report the fault here.

UltraSync ONE

UltraSync ONE

"***Device Fault***" error

An intermittent issue was causing ***Device Fault*** to appear on the UltraSync ONE screen.

When this happens, the unit becomes unresponsive and all menu operation halts. Although the device can neither receive nor transmit timecode over RF when this occurs, it will continue to free run, so timecode continues to roll and sync remains accurate.

This issue has been resolved

New firmware v2.09 (released January 2019) has addressed this issue.
In firmware v2.09 we have added a background feature to log any fault condition, which will assist with the diagnosis of hardware fault errors. Additional routines have also been added to reduce the possibility of system freeze occurring from a fault connection.

Click here for more information and advice on how to update your units.

If you are using an earlier firmware version and experience the above error, resetting the unit will resolve this and restore complete functionality of the UltraSync ONE. So when there is an appropriate break in filming, we advise to reset the faulty unit by pressing down the ‘up’ and ‘down’ keys together and holding for 10 seconds. Please be aware doing this will reset the timecode to zero. If this unit is a slave, it will re-sync to its master when in RF range. If the faulty unit is a master, please ensure slaves units are in range when you reset to ensure accuracy is maintained across your sync network. Please ensure you then update to the latest firmware version as soon as possible.

BLINK Hub app

BLINK Hub app

iOS 13 Compatibility

The BLINK Hub fails to launch correctly on devices running the new iOS13 operating system.

Users attempting to launch the BLINK Hub app on devices running iOS 13 will notice that the screen starts flashing and becomes corrupted when the passcode pop-up appears.

This issue has been resolved

A new version of the BLINK Hub app is now available on the app store and resolves these launch issues. Please ensure that you have downloaded the latest version of the BLINK Hub to restore full functionality. **Compatible with all devices on iOS 11 or higher**

Android 9 Compatibility

The BLINK Hub is failing to launch on Android 9.

The BLINK Hub app fails to launch on devices running the new Android 9 operating system.

Due to new Google security regulations the BLINK Hub app is not compatible with Android 9.0 and as a result has been removed by Google from the Play Store.

If you currently have our Android App installed it will continue to work provided you continue to run a version of Android prior to 9.0.

Users on Android 9.0 will be required to use their web browser to access BLINK Hub. This can be done by typing the IP address of your :pulse / :wave into your mobile devices browser once connected via WiFi.

Scaling issues on small scale mobile devices

The BLINK Hub display is not scaling correctly for screens on smaller smartphone devices.

This fault is causing some buttons to fall out of visibility and difficulties updating some data fields. This problem does not occur on iPads and other tablets.

This issue has been resolved

Scaling issues on small scale mobile devices has been resolved in the 3.10 webview.