1. Timecode Systems
  2. :wave
  3. Troubleshooting - :wave

  • Troubleshooting your :wave

    Troubleshooting your :wave

    If you are having difficulty with your :wave, the following troubleshooting sections may help:

     

    :wave Slave not Connecting to Master

    If your :wave is not receiving timecode from a master device, it could be due to:

    • The master device being switched off. Make sure the master device is on and has sufficient battery power.
    • :waveis set to run in a master mode (see Set the Timecode Mode). The :wave can only connect with a master device if the :wave is running in EXT-RF Slave mode.
    • The master is out of range. Your :wave will use its own internal clock until the master is back in range.
    • The :wave is not set to use the same RF Channel as the master. :wave slave - master communications can only take place between devices that are in the same BLINK network (are set to use the same RF Channel). For more information, see Set the RF Channel.
    • The :wave and/or the master are not set to the correct country/area. You need to set the :wave and master to the country/area in which they are being used (see Set the RF Country/Area).

     

     

    :wave has No Power

    If the :wave has no power, it means its battery is empty and there is no other power source. If you connect an alternative power source and the :wave still has no power:

    1. Check that the power ports on the :wave are clear. Ports can get clogged with dirt and dust from the environment.
    2. Try using a different type of power supply and cables. If the :wave powers up, you can use a process of elimination to determine which power supply port(s) are not working. You should then contact Timecode Systems for assistance.

     

    :wave Clock Freezes when in RF Slave Mode

    if your :wave runs as a slave in a BLINK network, it gets its timecode from a master device, such as another :wave. Some master devices, including :waves, can be set to EXT-TC TX mode, where the master gets its timecode from an external device. If the master device loses its connection to the timecode source, its timecode freezes, and so does the timecode of every slave device in the BLINK network.

    Your :wave's timecode freezing is expected behaviour in this situation.

    If your :wave does not get its timecode from a master device that is running EXT-TC TX mode, but still has frozen timecode, contact Timecode Systems for assistance.

     

    Camera Not Receiving Genlock from :wave

    If your camera is not receiving genlock from your :wave, make sure that you have followed the setup instructions correctly (see Quick Setup :wave Connected to Camera). Check that the camera and :wave are connected via the TC/SYNC port and that the :wave is set to output the correct type of genlock signal for the camera.

    You should also check that the camera is set to receive genlock from an external source.

    If problems persist, contact Timecode Systems for assistance.

     

    Sound Mixer Not Receiving Word Clock from :wave

    If your sound mixer is not receiving word clock from your :wave, make sure that you have followed the setup instructions correctly (see Quick Set Up :wave Connected to Sound Mixer/Recorder). Check that the sound mixer and :wave are connected via the TC/SYNC port and that the :wave is set to output the correct type of word clock signal for the sound mixer.

    You should also check that the sound mixer is set to receive word clock from an external source.

    If problems persist, contact Timecode Systems for assistance.

     

    Cannot Control Devices Connected to a Slave Pulse via BLINK Hub

    This is intended behaviour. You cannot log in to BLINK Hub for a master :wave and use it to remote control devices that are connected to a slave :wave.

    To control the devices that are connected to a slave :wave, you should access BLINK Hub for the slave :wave.