So @Shameiko, you have the following inter-connectivity mapping?
X32 <-> [A] S16-Top [B] <-> [A] S16-Bottom
and you don't have sync on S16-Bottom A port?
If that is the case, you probably have a hardware problem. I would suggest you contact CARE (contact info is phone at (+1) 702-800-8290 for the US and Canada and (+44) 1562 732290 in Europe, email CARECREA@musictribe.com).
I had a cable that no matter what I did, would not sync. I reterminated and tested (with a network cable tester), etc. In the end, I pulled the ethercon shells, pitched the cable and made up another one.
After six months of great use and success with the MR 12 at gigs, I am now having a problem when I try to conncect using my Samsung notebook/software. Can this be a firmware update problem?
Unlikely @DaveEagleston. What firmware are you using? The last time I used my MR12 (I don't use it that often due to its input/output limitations), it was working fine on the latest firmware.
How are you connected to the MR12?
Yes the T568A or T568B are just color code differences and should work as long as you are using the straight and not crossover wiring. The other key thing is the inter-connectivity of devices in an X32 eco-system. I usually use the following:
X32 [B] <-> [A] DL16 [B] <-> [A] DL16
The reason for this is that the stagebox (DL16) can only use the B port for cascading to other stageboxes. Connecting an X32 to the DL16 B port will give you the non-syncing issue.
Also make sure the X32 is the master clock (Setup, global, Synchronization -> Internal) and the DL16 set to mode 1 or 2 (not master clock). It does weird things when it is the other way around.
Welcome to the forum. What console are you using? Is it an X32, M32, X-Air or M-Air digital console? If so, export your scene to a file, zip it and attach it here so we can have a look and better advise.
Actually most network cable testers can test everything (including the drain wire), as long as you are willing to remove the ethercon shell. This is not that difficult. Simply twist back the stress relief plastic boot and remove the shell. When putting back the ethercon shell, I would suggest you plug it into an AES50 port before tightening the stress boot.
Welcome to the forum. Yes you can setup routing to provide for the Aviom and FOH outputs. Please provide more info as to how you currently have the Aviom connecte to the X32 and what routing you are currently using. Better yet, export your scene to a file (using the Utility button), zip it and attach it here. That way we can know what is available (routing-wise) for the additional FOH outputs.