Production Switchers

 View Only
  • 1.  UMDs from Tallyman dropping out in Carbonite Black multiviewer

    Posted 01-28-2020 10:50

    I have setup the Carbonite Black internal Multiviewer to read tally status and UMD information from a TSL Tallyman TM1. I have done this by creating a "Serial Tally" device on the desk over TCP, using port 5727.
    The problem we are having is that the names and the tally status keep dropping out on the multiviewer after roughly a minute.
    Choosing a new source on the bus brings back the the tally and UMD information.
    Has anyone encountered this problem before?
    One thing I have considered is that the Tallyman manual mentions that I should connect over UDP rather than TCP, but I haven't been able to achieve this successfully. Is there a port number that would allow me to connect over UDP instead of TCP?

    Thanks



  • 2.  RE: UMDs from Tallyman dropping out in Carbonite Black multiviewer

    Posted 01-28-2020 20:47

    sounds like the Tally Man is dropping the connection and when you initiate a switch it is re connecting...

    Carbonite only supports TCP and only on 5727.  Carbonite is acting as the Server device and the Tallyman is a Client that connects to the switcher.  They need to maintain the connection.  Do you by any chance have another device that might be trying to connect to the Carbonite on that same port?

    We have many Carbonite units in the field with Tallyman systems.  Daniel Bailey did a lot of work with his team to ensure that they had a profile for Carbonite and that it was working well..


    #Carbonite


  • 3.  RE: UMDs from Tallyman dropping out in Carbonite Black multiviewer

    Posted 01-29-2020 10:24
    Hi Les, I believe I have solved the problem now (fingers crossed). I deleted the second TSL device in the Carbonite (communicating on Port 5727), and the system seems to be stable now. I am still getting correct names and tally information from Tallyman even with the 2nd device deleted. I thought I needed this device set up in order to receive the UMD information, but obviously not! The first device is still set up on port 8900, which is working correctly.
     
    The multiviewer device in Tallyman still has communications set to port 5727, so I believe that maybe this was conflicting with the Carbonite device settings, and only one of these was required?
    Not seen any dropouts for a while now, so hoping that this is the answer.
     

    #Carbonite


  • 4.  RE: UMDs from Tallyman dropping out in Carbonite Black multiviewer

    Posted 01-29-2020 14:53

    What device were you "talking" to from that second port...ie which device IP address had you entered?

    Correct for TSL UMD input there is nothing to setup on the Carbonite.  They are always running the TSL Port on 5727 as a server.

    To send TSL out we setup a device to send to the controller (or Video Server like a Tria and soon XPression will support it) to update it on the TALLY data of the switcher.  That is a one way port and the carbonite will setup as the "client" and reach out to connect to the other device that is receiving and setup to act as the server device.

    Sounds like you might have been sending back to the same IP address as the Carbonite with that port and they would be fighting over the port.  You make a switch which updates the Tally Man and that in turn "reconnects" to send an update message....but at some point the Carbonite would probably "reconnect" to that port with nothing...


    #Carbonite