Comfort Automation/ Security System Forums
UCM/ETH no longer has a port open - Printable Version

+- Comfort Automation/ Security System Forums (https://www.comfortforums.com)
+-- Forum: Products (https://www.comfortforums.com/forum-3.html)
+--- Forum: UCMs (https://www.comfortforums.com/forum-146.html)
+---- Forum: Ethernet UCM/ETH03 (https://www.comfortforums.com/forum-113.html)
+---- Forum: UCM/ETH01 & UCM/ETH02 (https://www.comfortforums.com/forum-119.html)
+----- Thread: UCM/ETH no longer has a port open (/thread-3300.html)

- Howser - 02-27-2013

My UCM/ETH with firmware 7.008 stopped working this morning.

I am using a Vista (SP2) laptop with Firewall disabled. The DSManager (as well as the version from Tibbo) cannot discover the UCM. Advanced IP Scanner as well as AngryIP Scanner shows the UCM as being alive, but without any Port actively listening.

Any ideas?




- Ingo - 02-27-2013

I have seen this long ago and my local network caused it. Try using a crossover cable between your laptop and UCM.

Also, the UCM should have two open ports, 1001/TCP and 65535/UDP where Tibbo discovers it\'s data.

If all else fails, reflash it using the cable method. If that doesn\'t work then perhaps you got hit by lightning as I had some close ones yesterday afternoon. Oh, always have a lightning protector on the LAN cable to the UCM. I use a RJ45 Isolator \'Clearline 12-00774\'.

Try the attached file, it talks to Tibbo on 65535/UDP. It\'s exactly what DS Manager does. It\'s just a quick test from my side without too much, any actually, error checking.

Ingo

- Howser - 02-27-2013

Thanks Ingo,

I guess the UCM was in a bad bad state. Before attempting anything, I disconnected the UCM for a while and connected it back to the Panel and it seems to be back in working order.

- Ingo - 02-27-2013

Glad to hear.

- ndh_basic - 03-20-2013

I\'ve been doing a new integration for a while and occasionally I have a lockup. It manifests as Ethernet UCM D10 (Green) on solid and D9 is off.  Resetting Comfort does not work and the UCM has to be power cycled.  Firmware including Tibbo is  up-to-date.

If this is on an installed system then either an expensive visit or a convoluted sequence with the client if they are prepared to do it and then probably only once.

This may be a rare protocol glitch that never or virtually never happens when integration is with Comfigurator. That would be well tested and experienced etc.

I am in on-going discussions with Cytech on this but do post here if you have any experiences to share.

It is tricky when it only happens once in a while. I\'ve gone as far as using Wireshark but that is pushing the boundaries of my knowledge and only appears to be useful if the client is the same PC.  Wireshark is not like a third party promiscous datascope \'tapping the communications\'. But as I say I\'m in new territory here and even that description may be tenuous.


- slychiu - 03-22-2013

Quote:Resetting Comfort does not work and the UCM has to be power cycled.
What about resetting the UCM, instead of power cycle??
That is more important