Loading Profile...
Wah! Do I have to fiddle with cables (god forbid)?
Good Morning! We recently moved all our equipment, which meant 3 million or so disconnections and then reconnections between all the pieces of our broadcasting equipment. So yesterday, when we finally got power to the temporary construction trailer; I plugged in the UPS, turned on all the surge protectors and components and got a "test screen" - could not access Tightrope. Tried a bunch of stuff - booting the servers, switching from 1 to 2 on the splitter that connects to the servers - got a test screen on one, blank screen on the other. Came home and was able to connect to Cablecast and Carousel and operate remotely, but when I sent autopilot, this is what I got back:
The send FAILED.
An error occured sending to 'VSX'. Check the configuration or the physical connections.
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 72.45.174.59:56700
An error occured sending to 'Encoder'. Check the configuration or the physical connections.
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 72.45.174.59:56700
I was not the person who disconnected and reconnected everything; he is out of town. Can you guide me to where I should look for the missing connection? Or is this an internal problem? Thanks for your help! ~ Mary Ellen
The send FAILED.
An error occured sending to 'VSX'. Check the configuration or the physical connections.
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 72.45.174.59:56700
An error occured sending to 'Encoder'. Check the configuration or the physical connections.
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 72.45.174.59:56700
I was not the person who disconnected and reconnected everything; he is out of town. Can you guide me to where I should look for the missing connection? Or is this an internal problem? Thanks for your help! ~ Mary Ellen
I’m frustrated
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?Yikes! It sounds like you have a bit of a mess.
1.) I'm not sure what to say about the 'test screen' issue, I don't think that comes from TRMS equipment, we don't send out a test screen when the equipment is on (or off for that matter).
2.) I'm sure the reason you can't send autopilot is because the IP address of you VSX and Encoder have changed. You will need to figure out what the IP addresses are, then re-set them in Cablecast under System Settings : Control Modules2 Comments
Add a comment
This answers the question
-
Thanks, JJ. I call it a "test screen", but it's just a pattern being displayed on the monitor and on the channel - I can make out spades (card suit), but that's about it. The screen eventually (30 minutes?) goes to fuzzy gray/black.
We have static IP addresses - they shouldn't change. I'll check with the cable company, but If this isn't the problem, any other ideas? -
Thanks, JJ. I call it a "test screen", but it's just a pattern being displayed on the monitor and on the channel - I can make out spades (card suit), but that's about it. The screen eventually (30 minutes?) goes to fuzzy gray/black.
We have static IP addresses - they shouldn't change. I'll check with the cable company, but If this isn't the problem, any other ideas? -
Inappropriate?Hi mecrowley,
I think JJ's right about the IP address... the error message that autopilot is giving you is basically saying: "Hey, I tried connecting to the VSX at address 72.45.174.59:56700 and no one answered." Same thing for the Encoder.
So, odds are that the VSX has a new address (from the big equipment switcharoo) that Cablecast doesn't know about, or it's not plugged into the network, or something along those lines.
Unfortunately, there isn't much we can do to help troubleshoot those particular issues. But, once you know for sure what the IP address is of the VSX (and that it's connected to your network properly), we can help inform Cablecast about the change.
I hope this helps!
-John
I’m happy
-
Inappropriate?Okay, guys, we think something is seriously wrong with the VSX. It won't boot. We get the BIOS screen, but that's it. Only twice have we managed to get a Microsoft screen. It's either deathly ill or dead. Should I overnight all the drives to you?
I’m sad
EMPLOYEE
EMPLOYEE
