BRIDGE TDM FAQ
Can you give me a general overview of the TDM system?
In a Wheatstone TDM system, anything with an IP address needs to have a unique address on a common subnet. The default TDM subnet is 192.168.1.0, but you don’t have to stay with that subnet. If you do change to use another subnet, you’ll need to change the IP addressing of all your Wheatstone equipment since everything must now use an address within the new subnet. Here’s an overview of the main TDM components:
- Tier 1— This can either be a Bridge rack with one or two CPU cards, or it may be one or two WheatNet hubs, so Tier 1 will always have either 1 or 2 IP addresses with the Tier 1 addresses set by that device’s _NET.TXT file (for Bridge and WheatNet CPU config files, the filename is XP_NET.TXT). This file is saved on the device. In very early systems a DOS configuration program was used instead of a text file. If Tier 1 has two CPUs or two hubs, then there will be a primary and a backup address. Both must be changed to the new subnet. The network settings files are accessed via FTP to the device in question and are editable using Windows Notepad. Instructions for changing these addresses are included in the Bridge and WheatNet manuals.
- Other Tiers—Other Tiers will have CPU addresses only if they have CPU cards in them. Any of these cards can have their IP addresses changed by the FTP process using the information found in the Bridge and WheatNet manuals.
- Control Surfaces—Control surfaces will have one or two CPUs each. They will also have device_NET.TXT files. The E-6 Surface CPU file will be named E6_NET.TXT. The procedure for editing these to change the IP address is like that used on the Bridge / WheatNet CPUs, and is covered in the Bridge and WheatNet manuals, and in the specific surface manual.
- XPoint—The XPoint program needs to know the IP addresses of the Bridge/WheatNet CPU primary addresses, and the Surface primary addresses as well. The Bridge manual explains how to change the addresses that XPoint is looking to find CPUs and Surfaces at. Additionally, the PC running XPoint must also have an address on the common TDM system subnet.
• XY Controllers—The utility program WSNetServer is used to change XY controller IP addresses
XPoint is not connecting. What should I look for?
How do I change the IP address of my Gibraltar Network router?
What kind of Ethernet switch do I need for a Gibraltar Network System?
How do I control an OnAir light when a Mic fader is turned on?
I can TAKE some sources OK, but when I try to TAKE others the source switches back after a few seconds. What’s going on?
How do I set the visibility on my XY Controller, or the destination on my X controller?
What output sample rates can I use?
Does X-Point run on Windows 10? How do I set it up?
I have a TDM Bridge system. I'm replacing some CD players, which just needed a closure on the GPIO, with NuMark CDN77USB which need to be pulled up to +5 to trigger the CD with low logic. I'm digging through the manual, but it looks like I'll need an external +5 supply to make this work. Is that the case?
The logs show a lot of errors and we have CPU errors with lots of audio issues throughout our facility. We plan on doing a hard reset but want to cause as little disruption as possible since some components are still working. We may need CPU Card replacements--if still available. What should we do to help prepare for this hard reset?
Which sample rates do your input cards support?
All AES input cards are fitted with premium quality sample rate converters that accept audio source sample rates up to 96kHz. The SRC on the input will re-clock the source to the system's output sample rate.
Can I hot swap cards in my Gibraltar Network cage?
Can I hot swap a fader module on the surface?
Is a PC required for the system to run?
Can a source or destination signal be split into mono?
Can a Salvo be launched based on time of day?
How do I clear the red or yellow triangle from the display on my surface?
I need to replace my PC. How can I transfer XPoint to a new computer?
Can I run X-Point on the same PC as WSTimeSet and other utilities?
We added four analog audio cards to an existing Bridge cage (2in, 2out) so we could cross-connect to the new blade system we're installing. The two systems are inter-connected using analog audio on DB-25 connectors. The issue is we're having trouble making some XPoint connections in the old software and it's not restricted to the new I/Os. Any idea why this might occur?