• State Not Answered
  • Date
    jon weir
  • Date
  • Replies 40 replies
  • Subscribers 5 subscribers
  • Views 4906 views
  • Users 0 members are here

3.2.0 b3148 Two part Console and DP connectivity

8-11-11
V3.2.0 b 3148
1 - Hog 2
1 - DP 8K (new unit, June 14 build date)
1 - DP 2K in Art-Net Mode
1 - Netgear switch

Issue 1 - This may or may not be an issue. When the unit powers up and is not attached to a console, it does not boot into the No Server screen. It goes as far as "initializing show", sits there and every 5 seconds the screen briefly goes blank and code runs through it. Then it goes back to the initializing screen. This is the only DP I have noticed doing this. This could be completely normal, but like I mentioned, I have not noticed this before with other units.

Issue 2 - The console will not talk to the DP. This is the primary issue. With the console up and running, the DP will never load the show and join in. The DP always shows scanning for show, or occasionally when it does completely boot, it shows no server and will not join.

Occasionally, in the network window of the desk it shows the DP as being there, but being offline. However on the DP, it shows it as not being connected.

This originally led me to believe it was a DP issue especially when coupled with the first issue. However, when I bring out a different desk, that DP joins right in and runs fine.

I tried the problem console on a different DP rack and have the same issue, no communication.

When I added a second console to the network, it drove the DP's and then the first desk was able to control them as well. I took the second console away and the system still worked. Shut the system down, started a new show, and I'm back to the same problem. The console won't talk to the DP's.

So, it looks like there seems to be an issue with the desk starting communication back and forth, but once that door is open, it's happy.

I have re-installed software on the console and tried various cables between the console and DP. The console is set to run a DHCP server and have all 4 red network lights on the back of the desk. Any thoughts?

Much beard stroking going on here....
Parents
  • 0
    I think we might have been able to reproduce your problem here in the lab early this morning but unfortunately the problem did not persist through a power cycle and is no longer reproducable again in our lab.

    What we saw was the same behavior you were seeing whereby the DP8000 has an IP address and is ready to connect but keeps reinitializing network every 4 or 5 seconds. We've been trying all day to get it back into this state but what is curious to me is that your desk appears to be stuck in this state even after a power cycle.

    What was interesting is that when we had the console in this state, we could not get another console to initialize properly on the network as those consoles would come up with a Hog Clock Init error right at the start screen... which is what Bob was reporting from Cache Creek.

    So here's what I would like to try. Find a router that serves DHCP and setup the console to obtain IP using DHCP (make sure console is not running DHCP server itself) and setup the DP8000 to obtain IP using DHCP as well. This way the console is going to be served it's IP address and cannot possibly negotiate a bum IP. Then see if the console can connect to the DP8000.
Reply
  • 0
    I think we might have been able to reproduce your problem here in the lab early this morning but unfortunately the problem did not persist through a power cycle and is no longer reproducable again in our lab.

    What we saw was the same behavior you were seeing whereby the DP8000 has an IP address and is ready to connect but keeps reinitializing network every 4 or 5 seconds. We've been trying all day to get it back into this state but what is curious to me is that your desk appears to be stuck in this state even after a power cycle.

    What was interesting is that when we had the console in this state, we could not get another console to initialize properly on the network as those consoles would come up with a Hog Clock Init error right at the start screen... which is what Bob was reporting from Cache Creek.

    So here's what I would like to try. Find a router that serves DHCP and setup the console to obtain IP using DHCP (make sure console is not running DHCP server itself) and setup the DP8000 to obtain IP using DHCP as well. This way the console is going to be served it's IP address and cannot possibly negotiate a bum IP. Then see if the console can connect to the DP8000.
Children
No Data
Related

www.etcconnect.com