Accessory 2 cables

  • Thread starter Thread starter jpmorris
  • Start date Start date
jpmorris

jpmorris

Tape Wolf
Right, hopefully it will be third time lucky on the synchronisation thing. I now have an ATS-500, but no accessory-2 cables (the MMC100 has them built in to the unit).

The manual does give the pinout, so I can knock some up when I get the D-plugs, but it doesn't say if the connections are straight-through or whether TX and RX have to be swapped. Does anyone happen to know offhand?

I almost had it with the Lynxes, but for some reason they wouldn't talk to each other properly. Once one of the units was brought online, they were both supposed to light their RS424 lights, but only one ever would. The cables checked out OK and there was some communication between them because the timecode difference was correct. I was never sure I'd quite got the deck communication protocol right either - it would sometimes go into hard rewind for no obvious reason...

I suppose I ought to sell them, but I might keep one anyway because the Lynx timecode display looks nicer :p
 
4 (RX) and 2 (TX) are swapped. Everything else is straight through.

14 is shield.

:)
 
Beck said:
4 (RX) and 2 (TX) are swapped. Everything else is straight through.
Click to expand...

Thanks. The bits should be arriving in a few days. If it works, I'll have 14 tracks and double my tape costs. RMGI will be so happy... :rolleyes:
 
I haven't had time to run a full test yet, but I've managed to get the slave TSR-8 to lock against a generated timecode :D

Now there is one problem that still needs solving, the timecode from the master machine. I'm going to need to split it three ways: to drive the SMPTE-MTC box, to feed into the ATS-500 for sync, and to feed into one of the Lynxes so I can actually read the timecode (the ATS500 display is tiny).

I'm piggybacking the signal from the MTC, so that does one of them, and I was hoping to feed the Lynx from the 'MTC THRU' socket on the ATS500. The problem is that if I do this, it somehow stops the ATS from being able to see the incoming timecode. Does anyone know why that would happen and how to prevent it?

Would I be better off making some kind of Y-lead?
 
You must log in or register to reply here.
Back
Top