I installed and programmed a Comfort I system in my house in 2003 (with SEM, LEM, DS01, KP04, KP01, UCM01). Used Comfigurator v2 for programming .ccl file.Worked brilliantly for years but lightening damaged part of the phone module.

I bought a Comfort II upgrade kit in 2010 and for various reasons I have only just got round to installing it. The parts are therefore 2010 vintage:
Comfort II - v5.172 ULT, PC01-070A
SEM02 - v5.175, PC01-070A
UCM05 (v5.2 PC01-066A) with USB01
old UCM (v5.43 PC01-017E)
LEM01-M2
KP04 (existing older one moved to replace KP01 in bedroom) so 2 KPs on system
DS02 for replacing old DS
I have installed boards and done a quick boot to check the system and it goes through POST. The adapter board didn't work for me and I had to make some bespoke PCB stand-offs for the main board and SEM.
I have installed latest Comfig v3 to convert the .ccl file.

Problems:
1) the UCM05/USB01 USB doesn't work. "Fails to connect to UCM", Gone through the posted check list, deleted/reinstalled latest Win10 drivers, re-booted etc. Set Comfig to USB with serial number so Comfig does see it. D2 red LED flashes briefly when access code 1234 is entered in the dialogue box but fails to connect when requesting system info.
Serial port on UCM board works through a USB serial converter thankfully.Anything else I could try?
Duff USB01?

2) Imported .ccl file and converted with Comfig3 to FS34 ULTII. Module number differs but scanning only finds the new KP04. Surprised it didn't find the SEMI presume I add the rest manually and the .cclx file can just now be sent to ComfortII and debugged/modified?

3) Do I also need to specify ALL the sensors/PIRs etc in Comfig3
4) Can I upgrade the UCM05 firmware with the old UCM01v5.45 ?
Thanks

Does your UCM05 have a serial 9 way connector and the USB01 is pluuged in on top?
If so you have to set the J2 shunt in the "485" position and not the "232" position
The J2 jumper is blow the 9 way serial connector

You should upgrade the Comfort and SEM firmware to the latest firmware

I believe your UCM 5.200 should be able to do this using the UCM Firmware cable. see instructions in http://www.comfortforums.com/forum4/1216.html This may allow the SEM to be scanned
However the UCM cannot upgrade itself and the old UCM01 cannot be used
You can ask Laser if they will help to get it upgraded for you

If you have converted the cl file to cclx you should not need to enter the sensors and zones agaim If PIRs are connected to a single zone then you cannot differentiate them, so it is always advisable to have a PIR in its own Input/zone

Following on... I have a G.R.I. NO Flood sensor which worked directly off the Comfort I board but does not appear to work with the Comfort II. It needs a minimum of 5vdc from the board. Comfort II has only c. 1.5vdc according to my meter.
I presume the changes to Comfort II logic voltages (5v -> 3v) mean that the Zone sensor voltage has dropped and this is why it has stopped working?Thankstimop001 wrote: I installed and programmed a Comfort I system in my house in 2003 (with SEM, LEM, DS01, KP04, KP01, UCM01). Used Comfigurator v2 for programming .ccl file.Worked brilliantly for years but lightening damaged part of the phone module.

I bought a Comfort II upgrade kit in 2010 and for various reasons I have only just got round to installing it. The parts are therefore 2010 vintage:
Comfort II - v5.172 ULT, PC01-070A
SEM02 - v5.175, PC01-070A
UCM05 (v5.2 PC01-066A) with USB01
old UCM (v5.43 PC01-017E)
LEM01-M2
KP04 (existing older one moved to replace KP01 in bedroom) so 2 KPs on system
DS02 for replacing old DS
I have installed boards and done a quick boot to check the system and it goes through POST. The adapter board didn't work for me and I had to make some bespoke PCB stand-offs for the main board and SEM.
I have installed latest Comfig v3 to convert the .ccl file.

Problems:
1) the UCM05/USB01 USB doesn't work. "Fails to connect to UCM", Gone through the posted check list, deleted/reinstalled latest Win10 drivers, re-booted etc. Set Comfig to USB with serial number so Comfig does see it. D2 red LED flashes briefly when access code 1234 is entered in the dialogue box but fails to connect when requesting system info.
Serial port on UCM board works through a USB serial converter thankfully.Anything else I could try?
Duff USB01?

2) Imported .ccl file and converted with Comfig3 to FS34 ULTII. Module number differs but scanning only finds the new KP04. Surprised it didn't find the SEMI presume I add the rest manually and the .cclx file can just now be sent to ComfortII and debugged/modified?

3) Do I also need to specify ALL the sensors/PIRs etc in Comfig3
4) Can I upgrade the UCM05 firmware with the old UCM01v5.45 ?
Thanks

Yes you are correct. Comfort 2 logic level changed to 3V - new logic tends to be lower voltage and current

You may measure 1.5V at the zone terminals due to internal resistance
The Comfort Inputs generally require dry contact
Typically a sensor lime smoke or PIR would have a 12V supply from Comfort and give a dry contact to the zones. This is the preferred and commpn method for sensors.

If the sensor is only 2 wires without a separate supply then you may need an interface circuit for it to work properly

Indeed it is... the product is excellent (and I frequently recommend it) but as a one-off user/installer I find the effort you put into the manuals, covering every conceivable situation worldwide, is outstanding and immensly valuable - on the rare occasion when something is not covered it is promptly dealt with in this forum - keep up the good work Chui.

I'm having some issues with my IRM01 modules after changing to Comfort II board. I have 3 rooms with Futronix Digital lights each controlled by an IRM01. The transmitters are at different ranges in each room - 2m, 4m and 6m from the switch.

I remember having a few problems grabbing codes from the Futronix remote when I first installed the system but all worked fine with the Comfort I board eventually.
Using the same .ifr files and unaltered transmitter set-up, the first problem with the Comfort II board was that 2 rooms (2m and 6m) didn't work. They came off the adjacent zone outputs with a common Com. I checked the outputs worked with an IR sensitive camera and saw the LED flash codes as well as a loaded 12v red LED.

During testing I switched the outputs to another zone and the 2m room then worked fine but the 6m room still did not activate the lights reliably reliable - a couple of response executes needed to activate (it worked reliably previously with Comfort I).

I wondered if re-learning the codes on the latest version of IR utility might help but initial trials of this produce codes that don't work as well as the original set (tolerance 10%, extended encoding).

Questions:
1) Does Comfort II have a lower current output than Comfort I which could explain the lack of range on the 6m room? My IRM01 has a 100ohm loading resistor.

It may be a range issue if the ir code works in some rooms at diferent distanbces
Can you temporailyt short out the 100 ohms reistor so that the IR led fully driver. Just to ensure that the codes are sent correctly. The 100 ohms resistor is meant to protect the output in case the putput is permanently turned on

In fact remote control internal resistor may be around 10 ohms or less. This is because there is no possibllity of latching the output on permanently, whereas Comfort Outputs can be controlled by the user and there is nothing to stop its output being turned on by an action.

Leaving at 40 ohms should be OK

The new IRIO with ISM03 Infrared submodule sends the IR codes using a Set Flag or counter command, and direct control of the Output to ON state is not allowed. That is the preferred method for new installlations