| Posted: Wednesday Mar 8th, 2017 02:58 pm |
|
1st Post |
caravanboy
Member
| Joined: | Wednesday Mar 8th, 2017 |
| Location: | United Kingdom |
| Posts: | 130 |
| Status: |
Offline
|
back to top
|
Hi,
I have a Comfort Ultra II (gen 2) system that I purchased in April 2011 (plus 2x LEMs, and 1 SEP). For various reasons it got bench tested and then never installed. I'm finally resurrecting my plans again and will be unboxing and installing it soon.
From a quick skim of the firmware updates page it seems things have moved on a lot. I believe my firmware is v5.x and I understand from the upgrade instructions that I will need to use a cable-based UCM to upgrade my firmware and then I can use a UCM/ETH03 after that.
Can anyone answer a couple of simple questions for me:
1) I don't yet have a UCM/ETH03 - if I buy a new one, will the "UCM" part of it let me do the initial firmware upgrade that means I can then use the ETH03 part for future updates, or do I have to buy a basic cable-based UCM?
2) Have there been any other mandatory hardware updates in the last 6 years that would prevent me from simply upgrading to the latest 7.x firmware for the main Comfort system?
Thanks.
|
| Posted: Wednesday Mar 8th, 2017 04:37 pm |
|
2nd Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5495 |
| Status: |
Offline
|
back to top
|
Yes, much has changed in 6 years
Comfort Firmware version >5.00 must be upgraded by UCM [programming cable
But if the firmware is < 5.100 then you first need to buy a MpU01 Plug in Module to replace the processor with a flash-based type. The MPU01 will have the latest v7 firmware so you do not need to upgrade the firmware, and can use Comfigurator and the UCM to upgrade in future
see info at http://www.comfortforums.com/forum4/1783.html
The new UCM/ETH03 will have the UCM firmware upgrading cable
The Comfort 2 hardware will still be compatible with the new systems, although there may be minor improvements
|
| Posted: Friday Mar 24th, 2017 06:18 pm |
|
3rd Post |
caravanboy
Member
| Joined: | Wednesday Mar 8th, 2017 |
| Location: | United Kingdom |
| Posts: | 130 |
| Status: |
Offline
|
back to top
|
Hi, thanks for the info.
My main Comfort system appears to be v5.206 firmware but the MPU01 module (I assume that's the extra add-on bit in my attached photo) looks different to other MPU01s that I've seen for sale. Can my module definitely be upgraded through a UCM/ETH03?
Just to be clear, I assume the cable that you said would come with a new ETH03 will definitely allow me to upgrade my old 5.206 firmware? I'm sure I saw elsewhere that the ETH03 will only with v7.xx firmware - I won't be in a chicken & egg situation, will I?
Also, can you confirm that I can connect both an ETH03 and a GSM4 module at the same time?
Thanks
Attachment: Comfort main board.jpg (Downloaded 64 times)
|
| Posted: Saturday Mar 25th, 2017 05:26 am |
|
4th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5495 |
| Status: |
Offline
|
back to top
|
The plug in module in the photo is OP01 the Output module, not MPU01
Your comfort 2 is not the old one that comes with MPU01 sockets because the CPU is a flash processor that can be upgraded
However firmware 5.206 needs to be upgraded using the UCM firmware upgrading cable. The UCM/ETH03 or UCM/USB comes with the cable that can be used to upgrade the firmware to version 7
Comfort allows 8 ucms to be connected so UCM/ETH03 and UCM/GSM both can be commected
|
| Posted: Wednesday Apr 5th, 2017 02:19 am |
|
5th Post |
caravanboy
Member
| Joined: | Wednesday Mar 8th, 2017 |
| Location: | United Kingdom |
| Posts: | 130 |
| Status: |
Offline
|
back to top
|
I'm hoping someone can advise as I'm getting very frustrated here...
So, my ETH03 arrived. I've connected it up as per the instructions for doing an old 5.xxx cable upgrade (my current main Comfort Ultra firmware is 5.206):
ETH03 is connected to local LAN.
IP address is static
Comfigurator (v3.11.12.0) is talking to ETH03 - CS Manager can see it and Comfigurator comms method changed and IP set and it shows in toolbar (and proved if I unplug Ethernet cable that it says there is an error)
UCM is connected to Comfort using standard 4 way cable AND the programming cable (6 wire header at comfort end, the other two wire and 6 way 4wire version at the UCM/ETH03 end). PP2 is shunted (although there is one jumper labelled PP2 below it and PP1 above it - I assume this is the correct one to shunt)
Green RDY light is lit on UCM. Red power and Green Status both lit on daughter ETH03
NOTHING lit on Comfort mainboard (is that normal?)
Yes that is normal - Cytech support
Keypad is beeping constantly about twice per second (VERY annoying after an hour of this)
Yes keypad will beep because Comfort is not operational in this mode so keypad is not polled. Once the programming cable is disconnected and Comfort is reset, the beeping will stop
In Comfigurator, selecting upgrade Firmware by UCM cable lets me choose the file 7.116 that I downloaded (I tried 7.032 too). It then asks for confirmation, then almost immediately says "UCM does not support this operation", then the Busy1 red LED on the UCM lights up and stays on.
Same happens if I try again whether or not I press reset on UCM.
When you see an error message and Scan for Modules Yews/No. Enter NO. Do Not scan for modules again as thet will not work, and will cause the error to be repeated
Justy performa the upgrade operation again
I also just tried powering up without the UCM Upgrade cable connected. I believe this shouldn't work anyway as my main firmware is too old to work with the UCM/ETH03? Anyway, it doesn't seem to do anything when I try to do something like Get System Info, it asks for a user code (I've tried default user code and engineer code, which work on keypad) and it then says it cannot connect to UCM. The Keypad also says "Phone Trouble. Controller" The Comfigurator UCM IO monitor shows:
> LT01
> LT01
> LT01
> UB0100FE
< NA
< NA
< NA
< UB01F0
< LU00
> LT01
> LT01
> LT01
> UB0100FE
< NA
< NA
< NA
< UB01F0
< RS11
> LI****
> LI****
> LI****
> LI****
If you attempt the upgrade wuth initial error and you repeat the operation, the IO monitor will show this
> LI
< LU00
> LT01
> LT01
> LT01
> UB0100FA
< NA
< NA
< NA Initial Error message
Repeat the upgrade Operation
< UB01F0
> LT01
< NA
> LT01
< NA
> LT01
< NA
> UB0100FA
< UB01F0 This 2nd attempt succeeds
> UB02
< UB02
> UD03FEF0F0F3EBC9568D8CD0E5B4169BAF5059CCC3DAE41F05D3EAA67657E2F978BE715D9957E2F978BE715D9957E2F978BE715D991B6AA10BCBEA862E80FF0A1E1D385D91D2057DC51084E15AA2CDF9BE2B5626CDEC2DC2FDFB198FEEDFEF08735C7B6399C839A89E4C029640887B679296D0A7D42DEB6CF82BDAB28ED8B5F41C1B321ECCA4D852B02BD4A2EF97D879CCFE6AE8626257FF32CE4FE47D55CDF957909FA6104373F56EEBE8C1A38DC2A1AE2471AE3957E2F978BE715D9957E2F978BE715D99FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF6D
< OK
> UD000000F040A6305C6708278E7385818F35B751773593FBDC7B9F2DAF2891FC6558839683C104B31BE378DD9EBE740C7BE52DDCD829A348BA008F6B7E0F512BD8C8447DE551F577CD33854EBAF1ABBA63C4AE847D85A32CDDD8ECCADB839EB91F9090502C0012FBDF154436DF3869B6D76F6E5F8DCA447EB19EEE1F8948DEDDC8DFFEE92472340179103AB6533206D370DAA761FD5C605ED28EFEDD87503884272A6B23F2315E40A357BF6B26FEE131C297EA08CD2CC24DD90A25FFB1A7DFDA759AA0A20BA3096E6117AD94C3FA73BA1F766011403432988B5977F6EA8B8D36A7845D825304349BAC2CAA82283055156246C9356004
< OK
> UD0000F0F0E03A8C7362CF3EE871010990CE401D0135AB74D35BA1DF6299FE9360BF701D16EDB71D9E314B0234EF36A589D821A27610DCBFFD7BE50FA8C5CF6E2F793CD50B2BB3518CFD33B961E7B72EC66B645F8B527DC658D00C750B6DE69F85B974764A253FF9A49C98DC4F0ABC7318258086E239B6EBB0E13F6C7810004BE9AFDDB01C08CBAA98723F2C0C226A9AABF20DE3398B8100680094236B417505672AAC6B49D5C723AFB0597DA0CB084C3153ACAD811193FEF47CA5D077D86BA94BD23D22C1415E287BE2370729FF58CF36C96F02C0F0AA4DF879327BA675129B5A3B7CFABBA15D43FBAF539FD97B2ADE9519372546E9
<
Powering up Comfort without UCM/ETH03 connected at all seems fine. Goes to Security Off mode, and then after maybe 30 seconds it says Phone Trouble Controller (so a red herring I assume - no phone connected at the moment since I'm still bench testing)
Last edited on Thursday Apr 6th, 2017 11:42 am by
|
| Posted: Wednesday Apr 5th, 2017 06:30 am |
|
6th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5495 |
| Status: |
Offline
|
back to top
|
Yes Comfort LEDs will be off when the programing cable is connected to it. In this state comfort firmware is not working, the keypadsd beep because there is no polling going on
Please upgrade the UCM firmware to 7.098 by right clicking on the UCM and selecting "Check for Upgrades"
see the changes in
http://www.comfortforums.com/forum81/4670.html\
This fixes a relevant issue
"Fixed bug UCM/ETH03 upgrade by cable fails 1st time Allow LT to be received without login so UCM can reply OK, not NA."
|
| Posted: Wednesday Apr 5th, 2017 11:45 am |
|
7th Post |
caravanboy
Member
| Joined: | Wednesday Mar 8th, 2017 |
| Location: | United Kingdom |
| Posts: | 130 |
| Status: |
Offline
|
back to top
|
Thanks, I'll try that tonight when I get home. I don't recall seeing the ETH03 show-up in the list of UCMs on the left hand side though and I'm sure Scan for Modules didn't show anything. I'll have to look closely.
Comfigurator was definitely talking to the ETH03 though as I could see the IP address at the bottom of the window and as I mentioned, unplugging the Ethernet cable gave a different error.
|
| Posted: Wednesday Apr 5th, 2017 11:50 am |
|
8th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5495 |
| Status: |
Offline
|
back to top
|
You will see UCM- General on the list of UCMs, not ETH03
Comfigurator does not know if you are using USB or ETH03 as the serial interface
|
| Posted: Thursday Apr 6th, 2017 02:25 am |
|
9th Post |
caravanboy
Member
| Joined: | Wednesday Mar 8th, 2017 |
| Location: | United Kingdom |
| Posts: | 130 |
| Status: |
Offline
|
back to top
|
Hi, sorry to be a pain but this is still not working.
I manually set IP of ETH03 to 192.168.1.200. I can ping it and CS Manager sees it blue.
Configured it as Network Local in Configurator (even tried all of this on 2 different PCs)
It works to some extent as per previous message about it failing to upgrade my Comfort 5.206 firmware caused the UCM's busy1 light to come on. I have also just successfully upgraded the ETH03 sub-module firmware to 2.23 now so that part is definitely working on the LAN and talking to the PC. It still gives the same errors as below though.
UCM green D9 LED is on solid (slightly dim, maybe flickering very slightly?). I only noticed the red D10 LED come on very briefly once so far.
UCM Leds D9 is RED and D10 is green. D10 green will blink rapidly, D10 red should blink more slowly
ETH03 board has solid green and red light which is good.
Tried to scan for UCMs - asks for sign-in code. Finds nothing and says "Failed to connect to UCM". Without that working I seem unable to upgrade the UCM's firmware. Feels like a Chicken & Egg situation.
Upgrading UCM Firmware does not need a Login as long as the connection is good, as you have confirmed
Just Right Click on the UCM select Check for Upgrades" This will upgrade the UCM firmware
Tried it with and without main Comfort UCM Programming cable connected. Still gives the same "failed to talk to UCM message" in all cases.
If the Comfort Uograde has failed do a Reset on Comfort in order to get out of the Firmnware upgrade. You should hear security off, and the UCM D9 and D10 should start blinking again
The UCM SW7 are all set to ON which should give it ID1
I also tried it with the "New method" of setting ID to 1 by using SW7 all OFF and the COPY button - no difference.
Please can you give me any further suggestions? This is very frustrating. I was hoping that a brand-new UCM/ETH03 would allow me to bring my old Comfort 5.206 to the 7.xxx firmware and then have the benefit of having it on the LAN too. I haven't even unpacked the new UCM/GSM4 yet - I hope I don't have similar issues with that.
I just noticed another forum post suggesting a DOWNGRADE of ETH03 firmware to 2.01 if you cannot talk to the UCM but surely since my UCM/ETH03 has only just been sent from Cytech to the UK (via Hunters Wholesalers) this week then the base UCM firmware will be fairly new anyway so shouldn't have this problem?
You should not need to downgrade ETH03 firmware
Thanks
Attachment: Comfigurator.JPG (Downloaded 40 times) Last edited on Thursday Apr 6th, 2017 11:47 am by
|
| Posted: Thursday Apr 6th, 2017 11:11 am |
|
10th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5495 |
| Status: |
Offline
|
back to top
|
Please do the following and let us know the results
Without The UCM programming cable connected to Comfort, what are the states of the D9 (RED) and D10 (Green) LEDs on the UCM?
if the UCM is working correctly, the RDY Green led should be on and both red and Green leds should be blinking (The green led appears solid because it is blinking very fast) If both are blinking then skip to the next section
If the Red D9 led does not Blink, you will not be able to log in.
Are any of the BUSY1, BUSY2 and ERR leds also on? This may indicate the UCM firmware was corrupted because of an earlier attempt up upgrade the UCM firmware (Not Comfort firmware). Not to worry, the UCM firmware can still be upgraded if it is corrupted by following the instructions below.
Without attempting to log in, do a firmware upgrade of the UCM firmware by right clicking on the UCM in the Modules Tab and selecting "Check for Upgrades"
If you have an error message, ignore it and repeat the Upgrade operation. If there is a message to do "Scan for Modules, - Yes/No?"select NO. The repeat upgrade operation should succeed
Upgrade Comfort Firmware using UCM programming Cable
Once the UCM is working and has been upgraded to 7.098, ie D9 and D10 leds are blinking, then do the firmware upgrade using the Programming Cable connected to Comfort. Even if D9 and D10 do not blink, but the RDY green led is ON you can go on to the Comfort Upgrade
To do the Comfort Upgrade, once the Programmming cable is connected do not attempt to log in as that will fail
Go to Transfer > Upgrade Firmware using UCM programming cable. Select the cbf file for Comfort Ultra 7.xxx
If you get an errer message "UCM does not support this operation" repeat the firmware upgrade again. Ignore the message "Scan for Modules ", enter NO as scan for modules will not work. Just repeat Transfer > Upgrade Firmware using UCM programming cable. Select the cbf file for Comfort Ultra 7.xxx
If there still are any problems, copy the Monitor IO and send it to us
The UCM IO Monitor when upgrading Comfort by UCM cable using UCM 7.098 is shown below
> LT01
> LT01
> LT01
> UB0100FA
< OK
< OK
< OK
< UB01F0
> UB02
< UB02
> UD03FEF0F0A832161277B0A3F0B4169BAF5059CCC3333D3EBABA02E69F5319369E5B0591855319369E5B0591855319369E5B0591856CBE36595C5E07B61A474411BAF507D8BBBEF12081D6BF6C84EFBF2EBAB65773BFE186FCF51F0CA8DE2CCE28C6D130569D1CF6F221E5F2A4C718E0786080C234656A2C32D84084ACA2CDF9BE2B5626CDE45A92A4A85990846CA88D68958B42A5F52A9731E9A512105C594C4A00E1AA73994D9B99733D097F49CE3DD0368599E95319369E5B0591855319369E5B059185FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF6A
< OK
> UD000000F0B24C968EEF68037B280F0D0ADA41787E1A2788CC6FC3EF94FAA8EE0693E910BDA55AB68237F96677C12EE174EBED197D1ADF9740E979DDC1D364022A763A496E4F9F7EAD510CFD13074B2D46B43496503A81EF2954CA1B87F314DA9E7E5D2187252BF03A96DAE7CD58B0A0D5AE4CA92A65FAED349B718A5221BC45A12C9ABAA7D90E375339F98490E9DAE8B99C7DCF54A71A131BF396FCCC9DC7EB57E718418D3D044E309500D034E49A4F1664CF76FDA18AABD35B164D8A11816B7DCA11831F56615C7B559C55963ADE07103979433CE2A974F3E624E8E3F2C38824894665C4F3D3F2624CCFA4BE0118351221FBB5296B
< OK
> UD0000F0F058316AD228A6CDCFF2D850BDF560323F1D92250569308702C6053DA178D1FB22A566F43B7ED4BF5BEFD99912F201C5D6DC8126DCE3F94CADB6F519CCB5E29C513B5EAB3E6AA3AB84BB87F7CF0F688FDCA91DDCC572A71C1B5ADC1D1C6280EA9351A85CD64D09A7CE615A54CA08119ACD10004BE9AFDDB01C5EE4E445574EC42050AA3354F14A109D9B39A810C0C52754EC8D1950FD2724FDA578B860429685A2D75F9295D57B2C5320F9487AD660D0A87A68531992294DE0C9AD54E4F03624BFEB66DA2C9051F77EF38BC3D159D01B09278A30055F25AD3D830453C83D35F9706CDCB11C75CE4711515B0D44F2104F1D65
< OK
This shows the firmware upgrading in progress, and will com,pl;ete without any problems
Last edited on Thursday Apr 6th, 2017 11:34 am by slychiu
|
| Posted: Thursday Apr 6th, 2017 11:48 am |
|
11th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5495 |
| Status: |
Offline
|
back to top
|
Please see further comments and replies to some points in your original posts that I have edited in RED
|
| Posted: Thursday Apr 6th, 2017 11:51 am |
|
12th Post |
caravanboy
Member
| Joined: | Wednesday Mar 8th, 2017 |
| Location: | United Kingdom |
| Posts: | 130 |
| Status: |
Offline
|
back to top
|
Ok, I'll try all that tonight. The first time the UMC/ETH03 was ever powered-up it was connected to comfort with the programming cable (and standard cable too).
I don't see how the UCM firmware can be corrupted by a failed attempt as I've not yet been able to even try upgrading its firmware as Comfigurator has always said it has failed to contact it.
Anyway, I'll follow your suggestions and see where I get to. Thanks again for all your help so far.
Last edited on Thursday Apr 6th, 2017 11:51 am by caravanboy
|
| Posted: Thursday Apr 6th, 2017 11:54 am |
|
13th Post |
caravanboy
Member
| Joined: | Wednesday Mar 8th, 2017 |
| Location: | United Kingdom |
| Posts: | 130 |
| Status: |
Offline
|
back to top
|
Actually, reading your instructions closely - I forgot to say I cannot select "Check for upgrades" as it is always greyed out because the UCM is not showing up in the list for COmfigurator. I tried the "upgrade from local file" but that was failing with the "cannot communicate error".
Ahh - just seen your red edits too. Yes, sorry, I mentioned the D9 and D10 the wrong way around. There are no other error/busy lights, just green RDY all the time on UCM. I really don't think I've see the red D10 blink ever though, perhaps just one brief flicker for a fraction of a second.
I'll start from scratch again tonight with your red comment edits as it sounds like if I get the first "UCM does not support this operation" I should just try again - I'm sure I did try that though and I had ignore the login the first few times (as I'd seen the instructions saying it wouldn't work). I only tried it later out of desperation.
Last edited on Thursday Apr 6th, 2017 11:59 am by caravanboy
|
| Posted: Thursday Apr 6th, 2017 12:04 pm |
|
14th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5495 |
| Status: |
Offline
|
back to top
|
Even if Check for Firmware upgrades is grayed out because you have not logged in, Uphgrade from local file should wrok
Attachment: Image1.jpg (Downloaded 35 times)
|
| Posted: Thursday Apr 6th, 2017 12:15 pm |
|
15th Post |
caravanboy
Member
| Joined: | Wednesday Mar 8th, 2017 |
| Location: | United Kingdom |
| Posts: | 130 |
| Status: |
Offline
|
back to top
|
yes, but after selecting the local file that was the point where it says "Unable to communicate with UCM".
Can you confirm if my Comfigurator screenshot above is what you'd expect to see - it shows no details of the UCM at all?
|
| Posted: Thursday Apr 6th, 2017 01:13 pm |
|
16th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5495 |
| Status: |
Offline
|
back to top
|
It shoukd be detected
The first step is to check if the D9 and D10 leds are blinking (wiuthihut the ucmn programming cable connecte)
|
| Posted: Thursday Apr 6th, 2017 01:19 pm |
|
17th Post |
caravanboy
Member
| Joined: | Wednesday Mar 8th, 2017 |
| Location: | United Kingdom |
| Posts: | 130 |
| Status: |
Offline
|
back to top
|
Ok. That will have to be tonight but I'm sure I already did that list night as follows when I was going to try upgrading the UCM firmware:
a) UCM/ETH03 connected to Ethernet cable
b) UCM/ETH03 connected with the standard RS485 cable to Comfort (which is still on 5.206 firmware)
c) Programming cable was NOT connected
d) Comfort PP2 was NOT shunted
I'm 99.9% certain that only the green D9/10 LED was flickering very fast, the red one did nothing. Does that mean I have a faulty UCM?
|
| Posted: Thursday Apr 6th, 2017 01:49 pm |
|
18th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5495 |
| Status: |
Offline
|
back to top
|
Also check the RDY led? Is it on?
|
| Posted: Thursday Apr 6th, 2017 01:54 pm |
|
19th Post |
caravanboy
Member
| Joined: | Wednesday Mar 8th, 2017 |
| Location: | United Kingdom |
| Posts: | 130 |
| Status: |
Offline
|
back to top
|
Yes, RDY was on all the time. Also, FYI, as I mentioned in my post after first trying the ETH03 to upgrade Comfort, the BUSY1 lights up after the first (failed) attempt to upgrade firmware by cable.
I did notice two more LEDs hiding under the ETH03 daughterboard last night. Those are not lit up.
|
| Posted: Thursday Apr 6th, 2017 03:12 pm |
|
20th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5495 |
| Status: |
Offline
|
back to top
|
The UCM cannot be faulty as it does reply as you copied from UCM IO Monitor
> LT01
> LT01
> LT01
> UB0100FE
< NA
< NA
< NA
< UB01F0
< LU00
> LT01
At least that was the case when you tried the initial upgrade
Now you are not able to log in
This could be because of the Comfort firmware being corrupted by a partial upgrade.
If that is the case the keypad would not be able to login, and may make a beeping sound until you press any key
This can be fxied by the UCM upgrade cable
Another possibility if the UCM has been corrupted due to a partial firmware upgrade. if this is the case then the UCM firmware can be upgraded by Comfigurator
A 3rd possibility is that both UCM and Comfort firmware are working but Comfigurator is not connecting to the UCM due to a connection problem
So..
if D9 and D10 are blinking, it means both are working and you should be able to login
If D10 is blinking and D9 red is not blinking it means Comfort is working but UCM is not responding. Either the UCM firmware is corrupt or there is an ID issue
|
| Current time is 02:56 am | Page: 1 2   |
|
