ELK - M1XP - Ethernet - Update Firmware - Now all sorts of disconnects

[personalt]

I recently updated the firmware on my elk m1xp hoping I could get the outgoing emails working again and now I get lots of disconnects from the central station.   I 'upgraded' to 2.0.42.  Are there any known problems with this version?  If needed, is it possible to go backwards with firmware.
thanks
 

 

[mikefamig]

No you can not undo or roll back the xep firmware update. Are you getting any error messages in your log?
 
Mike.

 

[personalt]

These are my errors. looks like it 'restores' and then goes bad in two minutes and stays bad for 13-15 minutes then goes 'good' and then bad almost right away.  I am using alarm relay.  years ago I had disconnects from time to time but it has been stable for at least a year or two before I did this firmware upgrade. 
 
Sun 6/26/2016 9:55 1 1363 = REMOTE PROGRAMMING
Sun 6/26/2016 9:54 1 1383 = ETHERNET TROUBLE
Sun 6/26/2016 9:49 1 1384 = ETHERNET RESTORE
Sun 6/26/2016 9:36 1 1383 = ETHERNET TROUBLE
Sun 6/26/2016 9:34 1 1384 = ETHERNET RESTORE
Sun 6/26/2016 9:21 1 1383 = ETHERNET TROUBLE
Sun 6/26/2016 9:19 1 1384 = ETHERNET RESTORE
Sun 6/26/2016 9:06 1 1383 = ETHERNET TROUBLE
Sun 6/26/2016 9:04 1 1384 = ETHERNET RESTORE
Sun 6/26/2016 8:51 1 1383 = ETHERNET TROUBLE
Sun 6/26/2016 8:49 1 1384 = ETHERNET RESTORE
Sun 6/26/2016 8:46 1 1130 = FAIL TO COMMUNICATE TROUBLE
Sun 6/26/2016 8:43 1 1364 = REMOTE PROGRAMMING ENDS
Sun 6/26/2016 8:42 1 1363 = REMOTE PROGRAMMING
Sun 6/26/2016 8:36 1 1383 = ETHERNET TROUBLE
Sun 6/26/2016 8:34 1 1384 = ETHERNET RESTORE
Sun 6/26/2016 8:27 1 1130 = FAIL TO COMMUNICATE TROUBLE
Sun 6/26/2016 8:26 1 1383 = ETHERNET TROUBLE
Sun 6/26/2016 8:24 1 1364 = REMOTE PROGRAMMING ENDS
Sun 6/26/2016 8:08 1 1130 = FAIL TO COMMUNICATE TROUBLE

 

[mikefamig]

Did everything appear to go smoothly when you did the firmware upgrade? Did you have any problems or have to attempt the upgrade more than once? Did you make any changes to the ethernet setup in rp2?
 
error 1383 means that the M1 in having trouble communicating with the xep. I would check the serial cable between the M1 and the xep, check all of the ethernet settings in rp2 and re-send them to the elk. Watch the lights on the xep to see if the power supply is constant. Try pinging the xep to see if you can communicate with it from the LAN side.
 
It may be that your firmware upgrade failed but I would exhaust all other possibilities first. It could be something co-incidental like a power or cable problem. This is one of those cases where it would be nice to have another known good xep to try in it's place.
 
I am not familiar with alarm relay. Does the elk report to them through the xep?
 
Mike.

 

[elvisimprsntr]

I upgraded to the new XEP boot/firmware yesterday. I have not experienced any Ethernet issues, but then I don't use a CS

 

[personalt]

Did everything appear to go smoothly when you did the firmware upgrade? Did you have any problems or have to attempt the upgrade more than once? Did you make any changes to the ethernet setup in rp2?
 
error 1383 means that the M1 in having trouble communicating with the xep. I would check the serial cable between the M1 and the xep, check all of the ethernet settings in rp2 and re-send them to the elk. Watch the lights on the xep to see if the power supply is constant. Try pinging the xep to see if you can communicate with it from the LAN side.
 
It may be that your firmware upgrade failed but I would exhaust all other possibilities first. It could be something co-incidental like a power or cable problem. This is one of those cases where it would be nice to have another known good xep to try in it's place.
 
I am not familiar with alarm relay. Does the elk report to them through the xep?
 
Mike.

Firmware upgrade went fine.. I can say that the network at least sorta worked as I could connect via elkrp via ip...  Yes.. alarm relay uses a DSC- Sur-Gard protocal.    

 

[personalt]

I think I found it..   About 6 months ago I got a new router and changed the default gateway from 192.168.1.2 to 192.168.1.1.  The ,m1exp had the wrong gateway and was set to static ip..  Maybe I changed it from dynamic back to static when I was doing the upgrade.  that plus the bad gateway caused it to have issues dialing out.  Seems quiet now...