Who did work with nexia tc?

Tassadar

On 7s and 8s inputs i have a radio microfons. And i need command to mute them.
This SET 1 INPMUTE 129 1 1 or SET 1 AECINPMUTE 129 1 1 or SET 1 PAECINPMUTE 129 1 1 are unworkable. Nexia answers me Invalid SVC. What i can do?
Sorry for bad english, thank you for adwise

filpee

send_string dvNexiaTC,"'SET 1 FDRMUTE 94 1 1 ',13,10"

works for a fader that I'm controlling on a job.

I've found that the best way to figure out the commands is by controlling the Nexia from a laptop in a telnet session.
That way you can plug away at the thing for as long as you need untill you find the correct syntax.

Be carefull though. Sometimes it can be handy to send a carriage return before sending the string. this will clear the Nexia's internal buffer.

Good luck.

filpee

Jeff B

The correct string is:

SEND_STRING dvNexiaTC, "'SET X INPMUTE Y Z 1',$0D"

Were:

X = the unit number. If only one unit is used then this number is 1.

Y = The instance number. You will need to get this from the file in the unit. The default number for this in the files I have gotten from BiAmp have been 71, but yours could be different.

Z = The channel number. In you case this number should be 7 or 8 .

JB

Chip Moody

Isn't the correct delimiter for Biamp commands a linefeed ($0A) not carriage return?

- Chip

Jeff B

The PDF file does say that, but the $0D has always worked fine for me. I have worked with a lot of BiAmp products in the last year and never a problem.

AMXJeff

according to the protocol manual, $0A is the correct delimiter...

Jeff B

AMXJeff wrote:

according to the protocol manual, $0A is the correct delimiter...

You are correct, but as I said he $0D has always worked fine for me. I have worked with a lot of BiAmp products in the last year and never a problem. I use to send $0D $0A and it would work but then one day I noticed it gave me an error back, so I took off the $0A and it stopped yelling at me, but it always worked correctly.

JB