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
  • I have an internal software patch I am currently testing on Hillbilly's console that should resolve these connectivity problems that both of you are seeing. Basically we are seeing a Hognet adapter initialization problem at boot up that causes downstream connectivity issues with DPs and client consoles. To my knowledge this issue is only known to be reproducible on a small number of Hog 3 consoles (sadly none of our lab consoles show this problem) but I am sure you two are not the only ones so if anyone else is experiencing this problem hang on while we test this most recent fix. I want to be sure of our fix so I will be continuing test on Hillbilly's console in our lab with this fix I got from development today and should have the desk ready to ship back to you early next week (Tues/Wed).

    Bob, I am going to send you a message soon with a test build I would like you to install to help ensure this issue goes away with the fix we have been testing.
Reply
  • I have an internal software patch I am currently testing on Hillbilly's console that should resolve these connectivity problems that both of you are seeing. Basically we are seeing a Hognet adapter initialization problem at boot up that causes downstream connectivity issues with DPs and client consoles. To my knowledge this issue is only known to be reproducible on a small number of Hog 3 consoles (sadly none of our lab consoles show this problem) but I am sure you two are not the only ones so if anyone else is experiencing this problem hang on while we test this most recent fix. I want to be sure of our fix so I will be continuing test on Hillbilly's console in our lab with this fix I got from development today and should have the desk ready to ship back to you early next week (Tues/Wed).

    Bob, I am going to send you a message soon with a test build I would like you to install to help ensure this issue goes away with the fix we have been testing.
Children
No Data
Related