0

Firmware 3.8.34

Has Firmware 3.8.34 fixed the Bug that causes the HD1010 to lock up if a synchronize command is sent when no router or TCP connection is present. 

This rather serious bug was reported in firmware version 3.8.24 via Request #6751

I am stuck with using firmware version 3.7.44 until this is resolved.

5 comments

  • 0
    Avatar
    Lyndon

    This has not changed yet. What's odd is that you don't see it on 3.7.44. I have seen this issue previously before and after 3.7. When you say no router or tcp, you mean no ethernet link, correct? Because I can connect two units set to dhcp directly to each other with no problems. I only see an issue if there's no ethernet link.

    Also, for your sync project, can you confirm if your master is set to broadcast to all subnets under file, presentation properties, interactive? 

  • 0
    Avatar
    Brian2

    As stated in my initial bug report " Brightsign 3.5.68 Bug report posted on September 23, it happens with the loss of the router.  The units are still connected together but have no router and no DHCP

    In Brightauthor, No not all devices on the subnet is checked but a UDP broadcast 255.255.255.255

    Port: 1988

  • 0
    Avatar
    Lyndon

    I can't duplicate the problem where just the loss of the router causes sync to fail. Were the unit setup for updates from a brightsign network account or simple networking? Maybe, some other networking issue is a factor. But, so far, can't duplicate it. 

  • 0
    Avatar
    Brian2

    OK,   it does not happen if the master is set to broadcast to all subnets.

    It does still happen if the master is set to UDP broadcast 255.255.255.255

    Do you want me to attach the files ?

  • 0
    Avatar
    Lyndon

     

    No, I don't need your files. There's already a bug logged on this issue from a much earlier firmware release. What I find odd is that you don't see this on earlier releases. I can duplicate this issue on the same firmware release that you say doesn't have this problem.  For the time, I can only recommend that your workaround for this issue is to make sure the master unit either has a manually assigned IP address, or that you set the master project to broadcast to all subnets, and set that as your default. 

Please sign in to leave a comment.