C90 control freezing up

[cdnadmin]

This document was generated from CDN thread

Created by: Kyle Wilcoxen on 11-01-2010 06:26:54 PM
I have an NI-700 controller and am trying to test the AMX module with a C90 that just arrived in the office. When I load the program I get control for about 5 seconds and then I get nothing. No menu navigation or camera control. This occurs RS-232 and IP. I've even set the baud rate to 9600 with the same result.

I have the latest Duet firmware installed in the processor and even updated the codec to the latest firmware. BTW, Crestron's C90 module works perfectly. Anyone else have issue with this?

Subject: RE: C90 control freezing up
Replied by: Kyle Wilcoxen on 11-01-2010 07:07:05 PM
I take back IP control of the C90. Upon further review, I was un-commenting the PROPERTY command for IP control but forgot to un-comment the device 0:3:0 for IP. I disconnected the RS-232 cable from the codec and re-uploaded the code with the above parameters un-commented. I get no control of the codec at all IP.

However, the project I'm programming for we are not controlling IP only RS-232. So, back to the original issue. Does anyone know why control would freeze after 5 seconds? If I press the Reinitialize button in the System Information area I get back control, but only for another 5 seconds.

Subject: RE: C90 control freezing up
Replied by: Viggo Fredriksen on 12-01-2010 02:21:57 PM
Hi Kyle,

  while testing IP, did you remember to enable the telnet service on the C90?

1xconfiguration NetworkServices Telnet Mode: On

With RS-232, do you get any output from the NI-master that could indicate what's
going wrong? Should be just a matter of telnetting in to the master and look for
any suspicious output when the control is lost. Feel free to post the output here
if you cannot find anything.

Thanks,
  Viggo

Subject: RE: C90 control freezing up
Replied by: Kyle Wilcoxen on 12-01-2010 06:35:06 PM
Hm, I did not do that. I called AMX and their tech support guy was on the phone with me for about 40 minutes trying to figure it out. We couldn't find a solution so he sent a trouble ticket to their ITG group to see if they've run into the same issue. They suggested pretty much what you did. To set DEBUG-4 and look at the Diagnostic output, then send them the log.

I won't be able to do this until Friday but I'll set telnet mode on and try IP again. Thanks.