I believe this was a new-in-box unit we found during our pre-config
process. Sorry, I don't have more info on it.
On 7/20/2015 11:27 AM, Ken Hohhof wrote:
This is an SM that has been in service for a couple months, I am
troubleshooting it remotely. It did eventually register, otherwise I
could not see the log entries. Now I see a new one:
07/20/2015 : 15:31:46 UTC : :XO trim at min diff=-37 c=0 cmove=-1 f=0
fmove=113
07/20/2015 : 15:31:52 UTC : :XO trim at min diff=-1389 c=0 cmove=-9
f=8064 fmove=-39
07/20/2015 : 15:31:53 UTC : :XO trim at max diff=1394 c=58 cmove=9 f=0
fmove=44
07/20/2015 : 15:31:55 UTC : :XO trim at max diff=6133 c=63 cmove=41
f=8191 fmove=-17
07/20/2015 : 15:31:56 UTC : :XO trim at max diff=7178 c=63 cmove=48
f=8191 fmove=-22
07/20/2015 : 15:31:58 UTC : :XO trim at max diff=7178 c=63 cmove=48
f=8191 fmove=-22
07/20/2015 : 15:31:59 UTC : :XO trim at max diff=7177 c=63 cmove=48
f=8191 fmove=-23
07/20/2015 : 15:32:01 UTC : :XO trim at max diff=7176 c=63 cmove=48
f=8191 fmove=-24
07/20/2015 : 15:32:19 UTC : :XO trim at max diff=5242 c=63 cmove=35
f=8191 fmove=-8
07/20/2015 : 15:32:20 UTC : :XO trim at max diff=7216 c=63 cmove=49
f=8191 fmove=-134
07/20/2015 : 15:36:43 UTC : :XO did not trim after 200 attempts. FPGA
TCXO/XO compare:04c497e2 (79992802)
07/20/2015 : 15:37:55 UTC : :Reset due to error setting receive
frequency 5540 at temperature 46 C
07/20/2015 : 15:38:55 UTC : :Forced reset;
07/20/2015 : 15:38:55 UTC :
I had moved the AP from 5.7 to 5.4 as a troubleshooting step, I think
that is unrelated to the problem, but this looks like a problem
adjusting a VCXO to the AP frequency. Did you see something like this
on yours also, or just the ADI communication failure? (I assume that
refers to communication with an Analog Devices Inc. chip).
*From:* Brian Sullivan <mailto:installe...@foxvalley.net>
*Sent:* Monday, July 20, 2015 11:18 AM
*To:* af@afmug.com <mailto:af@afmug.com>
*Subject:* Re: [AFMUG] 450 SM ADI communication failure
We currently have an RMA ticket open regarding this.� The note from
our guys about it was, " The unit I am looking at says 'ADI
Communication failure' at the top of the status page. After factory
resetting and configuring the unit, that error message is still there."
So not familiar, but Cambium had no problem letting us RMA the unit.
On 7/20/2015 11:05 AM, Ken Hohhof wrote:
Anyone familiar with this log entry?� I'm assuming I have an SM with a
hardware problem?� We had heat advisory Saturday but mostly due to
high
humidity, I don't think the actual temperature got above 90.
******System Startup******
System Reset Exception -- Watchdog Reset Cur ExtInt 0 Max ExtInt 0 Cur
DecInt 0 Max DecInt 0 Cur Sync 0 Max Sync 0 Cur LED 1 Max LED 1 Cur
WDOG 0
Max WDOG 1 Cur EthXcvr 0 Max EthXcvr 1 Cur FEC 0 Max FEC 0 Cur FPGA 0
Max
FPGA 0 Cur FrmLoc 0 Max FrmLoc 0 Cur WatchDog 33 Max WatchDog 33
RTMLogStats
0 AAState 0
Software Version : CANOPY 13.2 SM-DES
Board Type : P11
Device Setting : 5.4/5.7GHz MIMO OFDM - Subscriber Module -
0a-00-3e-b2-03-92
FPGA Version : 081514
FPGA Features : DES, Sched;
07/20/2015 : 15:09:03 UTC : :ADI communication failure
07/20/2015 : 15:09:03 UTC : :InitADI936x() : Catalina register
failures, ADI
forced reset has been invoked!
07/20/2015 : 15:10:03 UTC : :Forced reset;
07/20/2015 : 15:10:03 UTC :
******System Startup******
System Reset Exception -- Watchdog Reset Cur ExtInt 0 Max ExtInt 0 Cur
DecInt 0 Max DecInt 0 Cur Sync 0 Max Sync 0 Cur LED 1 Max LED 1 Cur
WDOG 0
Max WDOG 1 Cur EthXcvr 0 Max EthXcvr 1 Cur FEC 0 Max FEC 0 Cur FPGA 0
Max
FPGA 0 Cur FrmLoc 0 Max FrmLoc 0 Cur WatchDog 33 Max WatchDog 33
RTMLogStats
0 AAState 0
Software Version : CANOPY 13.2 SM-DES
Board Type : P11
Device Setting : 5.4/5.7GHz MIMO OFDM - Subscriber Module -
0a-00-3e-b2-03-92
FPGA Version : 081514
FPGA Features : DES, Sched;
07/20/2015 : 15:13:43 UTC : :Time Set
