Comfort Automation/ Security System Forums > Products > UCM > Ethernet UCM/ETH03 > Unable to connect to UCM/ETH03 |
Comfort Automation/ Security System Forums > Products > UCM > Ethernet UCM/ETH03 > Unable to connect to UCM/ETH03 |
| Moderated by: ident | ||
| Author | Post | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
daniedb Member
|
I have installed a new UCM/ETH03 component on my system. The initial install went well and after completion I was able to connect and able to use the UCM for its purpose. Then I saw the UCM/ETH03 was not on the latest firmware and updated the firmware. The update completed (or so it seem), and asked me if it should scan the components again. I selected yes and then it required the sign-on password again. From this point onwards I was not able to login. It constantly replies with the message to go the UCM connection settings. I've also seen a comment on the forum where someone had a similar problem after an upgrade of the firmware and then had to downgrade the firmware on the ETH03 component to connect again. I have tried that, but no difference. Is there a way to reset the UCM board back to factory settings, so that one can start the install process again? |
|||||||||
|
slychiu Administrator 
|
Did you upgrade the ucm or the eth03? After the upgrade did you go to comfort server manager to check the ip address and port? Please make sure the ip and port are the same as on thy ucm connection otherwise you will not be able to log in. VAlso check the d9 red and d10 green leds on the ucm base board are blinking |
|||||||||
|
daniedb Member
|
I upgraded the ucm first and after that I was not able to connect. I assume the upgrade did not complete successfully, because only d10 was blinking and the d1 to d4 ligths were on. I did check the ip address and it was the same as previously set. I then read the comments on the forum regarding the ETH02 firmware and the problem to connect if it was not on the correct level. I downgraded the ETH03 firmware, but it did not make a difference. In the meantime I've put back my previous ucm board that has the ETH02 module and connected again. The firmware version on this board was 7.141 A question. Can I replace the ETH02 module on this previous board with the received ETH03 module? Unscrew the ETH02 module and replace with only the ETH03 module. The previous board is in good working order and on the latest firmware level. |
|||||||||
|
slychiu Administrator
|
ETH02 on UCM is not able to do the UCM Firmware upgrade. I am confused about whether you are using ETH02 or ETH03. You can replace the ETH02 with ETH03 submodule If you have 2 UCM/s you can upgrade the other UCM that failed to upgrade, using the UCM programing cable method |
|||||||||
|
daniedb Member
|
My previous board before I tried to upgrade was a UCM/ETH02 board. I have tried to use the old UCM (firmware 7.141) with the new ETH03 submodule, but I still get a connection error. I must assume that the new UCM/ETH03 board is corrupted. Very frustrating. I am using currently the ETH02 board else I cannot connect to the system, but need to move to ETH03 to be able to do Vocabulary upgrades. When installing the ETH03 submodule on the previous UCM base board do I need to remove the UCM module from the Comfigurator config and then scan for it again or can I simply continue on the same UCM config definition? |
|||||||||
|
slychiu Administrator
|
I assume you have a working UCM/ETH02 module at ID1. You have another UCM/ETH03 (where the UCM firmware is corrupted?. ) Replace the ETH02 with ETH03 on the UCM with ID 1. Set the IP address and Port of ETH03 in Comfigurator using Comfort Server Manager. Check that you can log in to Comfigurator Connect the other corrupted UCM to the 1st UCM using the UCM Programming Cable to upgrade the firmware of the corrupted UCM See instructions at http://www.comfortforums.com/forum4/1782.html The corrupted UCM doesnt need to be connectted to Comfort other than by the UCM programming cable After upgrade, the corrupted UCM should work, with ETH02 or ETH03. If you want to cpnnect both to the system then the 2nd UCM must be at a different ID Last edited on Tuesday Apr 6th, 2021 04:11 am by slychiu |
|||||||||
|
daniedb Member
|
Thank you, I try this. Can you perhaps check the link for instructions provided? This link provided does not work. |
|||||||||
|
slychiu Administrator
|
Thanks, the link has been fixed |
|||||||||
|
daniedb Member
|
Thank you for the assistance. The above process worked and I have now two UCM's connected to my system. ETH02 and ETH03. |
|||||||||
|
slychiu Administrator
|
Thats good. try not to use the ETH02 except for standby |
|||||||||
|
caravanboy Member
|
Just spotted this thread and it sounds pretty identical to the issue that I had a couple of weeks ago (mentioned on another thread) - essentially a UCM/ETH03 upgrade of the main UCM firmware which then corrupted the UCM and I was no longer able to connect to it. I didn't have the benefit of having another UCM so mine had to be sent off to Laser to be re-flashed. slychui - Could there be a bug with UCM/ETH03 firmware upgrades if that is two of us that have ended up with the UCM/ETH03 in same state? |
|||||||||
|
slychiu Administrator
|
This was due to the ETH02 submdoule. It is not able to upgrade its own UCM, so yours is not ghe sae issue |
|||||||||