MXT-1000 cycles on/off line after a master file transfer

vining · September 2015

I've been having this weird issue which my test MXT-1000 (G4) where if cycles on and offline dozens of times after a file transfer to my master when the master is coming back online. In diagnostics I see

Line    545 (09:00:45)::  CIpEvent::OnLine 10004:1:1
Line    546 (09:00:45)::  UI DEBUG: (1) [ 10004:1:0 ], STATE-[ ONLINE ] :DEBUG&lt;4999&gt;
Line    547 (09:00:45)::  UI DEBUG: (1) DATA_EVENT: UI INDEX-[ 4 ], IS NOW ONLINE :DEBUG&lt;2204&gt;
Line    548 (09:00:45)::  UI DEBUG: (1) UI DEVICE-[ 10004:1:0 ], DEVICE_ID-[ 0 ] :DEBUG&lt;2211&gt;
Line    549 (09:00:45)::  UI DEBUG: (1) UI DEVICE-[ 10004:1:0 ], IS-[ Unknown ], TYPE-[ 1 ] :DEBUG&lt;2354&gt;
Line    550 (09:00:45)::  CIpEvent::OffLine 10004:1:1
Line    551 (09:00:45)::  UI DEBUG: (1) [ 10004:1:0 ], STATE-[ OFFLINE ] :DEBUG&lt;5007&gt;
Line    552 (09:00:45)::  CIpEvent::OffLine 10004:2:1
Line    553 (09:00:45)::  CIpEvent::OffLine 10004:3:1
Line    554 (09:00:45)::  CIpEvent::OffLine 10004:4:1
Line    555 (09:00:45)::  CIpEvent::OffLine 10004:5:1
Line    556 (09:00:45)::  CIpEvent::OffLine 10004:6:1
Line    557 (09:00:45)::  CIpEvent::OffLine 10004:7:1
Line    558 (09:00:45)::  CIpEvent::OffLine 10004:8:1
Line    559 (09:00:45)::  CIpEvent::OffLine 10004:9:1
Line    560 (09:00:45)::  CIpEvent::OffLine 10004:10:1
Line    561 (09:00:45)::  CIpEvent::OffLine 10004:11:1
Line    562 (09:00:45)::  CIpEvent::OffLine 10004:12:1
Line    563 (09:00:45)::  CIpEvent::OffLine 10004:13:1
Line    564 (09:00:45)::  CIpEvent::OffLine 10004:14:1
Line    565 (09:00:45)::  CIpEvent::OffLine 10004:15:1
Line    566 (09:00:45)::  CIpEvent::OffLine 10004:16:1
Line    567 (09:00:45)::  CIpEvent::OffLine 10004:17:1
Line    568 (09:00:45)::  CIpEvent::OffLine 10004:18:1
Line    569 (09:00:45)::  CIpEvent::OffLine 10004:19:1
Line    570 (09:00:45)::  CIpEvent::OffLine 10004:20:1
Line    571 (09:00:45)::  CIpEvent::OffLine 10004:21:1
Line    572 (09:00:45)::  CIpEvent::OffLine 10004:22:1
Line    573 (09:00:45)::  CIpEvent::OffLine 10004:23:1
Line    574 (09:00:45)::  CIpEvent::OffLine 10004:24:1
Line    575 (09:00:45)::  CIpEvent::OffLine 10004:25:1
Line    576 (09:00:45)::  CIpEvent::OffLine 10004:26:1
Line    577 (09:00:46)::  CIpEvent::OffLine 10004:27:1
Line    578 (09:00:46)::  CIpEvent::OffLine 10004:28:1
Line    579 (09:00:46)::  CIpEvent::OffLine 10004:29:1
Line    580 (09:00:46)::  CIpEvent::OffLine 10004:30:1
Line    581 (09:00:46)::  CIpEvent::OffLine 10004:31:1
Line    582 (09:00:47)::  Accepted connection:socket=30 addr=192.168.1.41 port=35616
Line    583 (09:00:47)::  Closing connection to 192.168.1.41 due to transmission failure to system 1 device 10004
Line    584 (09:00:47)::  CICSPTCP Rx connection to 192.168.1.41 has been closed locally or by peer
Line    585 (09:00:47)::  Closed Socket Connection socket=30 addr=192.168.1.41 index=3
&#8203;

After the last master file transfer and I got this 43 times before it stopped. The panel is usually rebooting too for some odd reason, maybe a built feature to reboot when it looses connection to a master and since the master reboots after the file transfer that start a viscous cycle. The panel's running fw rev v2.104.68. Also when it comes online it won't give me a proper dev_id response, I get a dev_id of 0.

John Nagy · September 2015

Use a larger capacity power supply. I've seen this too, when the panel power is insufficient.

vining · September 2015

Ok, right now it's using a Pakedge POE mid span injector class 3 and class 3 should be good for 6.4-12.9 watts, spec on the TP is 8w full on and there's only a 6' patch between the TP and the injector so drop should be next to nothing. Actually the sticker on the injector says 0.6A and at 48v that should be 28.8w. I should have some higher current models on the shelf so I'll give it a try.

MXT-1000 cycles on/off line after a master file transfer

Comments

Categories