• Troubleshooting your :pulse

    Troubleshooting your :pulse

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

     

    :pulse Slave not Connecting to Master

    If your :pulse 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.
    • :pulseis set to run in a master mode (see Set the Timecode Mode). The :pulse can only connect with a master device if the :pulse is running in EXT-RF Slave mode.
    • The master is out of range. Your :pulse will use its own internal clock until the master is back in range.
    • The :pulse is not set to use the same RF Channel as the master. :pulse 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 :pulse and/or the master are not set to the correct country/area. You need to set the :pulse and master to the country/area in which they are being used (see Set the RF Country/Area).

     

     

    :pulse has No Power

    If the :pulse 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 :pulse still has no power:

    1. Check that the power ports on the :pulse 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 :pulse 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.

     

    :pulse Clock Freezes when in RF Slave Mode

    if your :pulse runs as a slave in a BLINK network, it gets its timecode from a master device, such as another :pulse. Some master devices, including :pulses, 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 :pulse's timecode freezing is expected behaviour in this situation.

    If your :pulse 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 :pulse

    If your camera is not receiving genlock from your :pulse, make sure that you have followed the setup instructions correctly (see Quick Setup :pulse Connected to Camera). Check that the camera and :pulse are connected via the TC/SYNC port and that the :pulse 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 :pulse

    If your sound mixer is not receiving word clock from your :pulse, make sure that you have followed the setup instructions correctly (see Quick Set Up :pulse Connected to Sound Mixer/Recorder). Check that the sound mixer and :pulse are connected via the TC/SYNC port and that the :pulse 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 :pulse and use it to remote control devices that are connected to a slave :pulse.

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