CQC elk driver

[comet48]

Looking at cqc trial, and trying the elk driver. It seems very limited re what can be accessed - can't see any zones, outputs etc - see a bunch of Custom Values etc. Am I missing something?

 

[IVB]

yeah, you need to add the client side driver. Then you can pick & choose which zones, outputs, etc you want.

Otherwise you'd be crushed by navigating through 208 outputs, 208 zones, 208 PLCs, thermos, and god knows what else.

 

[comet48]

yeah, you need to add the client side driver. Then you can pick & choose which zones, outputs, etc you want.

Otherwise you'd be crushed by navigating through 208 outputs, 208 zones, 208 PLCs, thermos, and god knows what else.

Thx IVB- where is that?

 

[EST]

In CQC Admin the 2nd button down in the 2nd column is Administer Client Side Drivers. Add Elk driver there and then you can go through each option and check off what your Elk system has (Zones, Outputs, TStats, ...). This will trim down everything in the selections to just what your system has.

Eric

 

[comet48]

In CQC Admin the 2nd button down in the 2nd column is Administer Client Side Drivers. Add Elk driver there and then you can go through each option and check off what your Elk system has (Zones, Outputs, TStats, ...). This will trim down everything in the selections to just what your system has.

Eric

Thanks - once I got rid of elkrp it connected and ran great.
A couple of queestions re the interface -
1. I see both Phys and Lod zones - the diff?
2. Probes and voltages - what do they link to?
3. I use elk temperature sensors - can I read the temperature from these zones.
Sorry fo all the newbie questions.

 

[EST]

In CQC Admin the 2nd button down in the 2nd column is Administer Client Side Drivers. Add Elk driver there and then you can go through each option and check off what your Elk system has (Zones, Outputs, TStats, ...). This will trim down everything in the selections to just what your system has.

Eric

Thanks - once I got rid of elkrp it connected and ran great.
A couple of queestions re the interface -
1. I see both Phys and Lod zones - the diff?
2. Probes and voltages - what do they link to?
3. I use elk temperature sensors - can I read the temperature from these zones.
Sorry fo all the newbie questions.

First, if you haven't read the CQC info on the Elk driver you can HERE. This will explain all the details of the driver. For future reference, goto CQC web site and goto Support and then Supported devices for info on any driver you use.

1. Physical Zone is the physical state the zone is in: Normal, Violated, ... . Logzone is the logical state: Open, EOL, shorted, ...
2. Can't help you there, I don't use that (yet).
3. I assume so, under thermocouples in the client side window of CQC Admin.

No problem about the questions...you are where I was at last year. I found the support file much later and it was like a light went off...that's how you do it!!!

Good luck

 

[IVB]

Oy, this is from memory, and I haven't touched it in months (years?), but:
2) Probes are temperature probes (I think). If you have a temp sensor hooked up to zone 9, use Probe09. Ditto for Voltages, it's if you use analog voltages via the Elk. I do this with a photoresistor, so I can tell if an LED is on or not.

3) See above. (I think, but then what the hell is the thermocouple? god I need to stop replying to threads where i'm not 100% certain on the answer).

The driver documentation will have all this info.

 

[comet48]

In CQC Admin the 2nd button down in the 2nd column is Administer Client Side Drivers. Add Elk driver there and then you can go through each option and check off what your Elk system has (Zones, Outputs, TStats, ...). This will trim down everything in the selections to just what your system has.

Eric

Thanks - once I got rid of elkrp it connected and ran great.
A couple of queestions re the interface -
1. I see both Phys and Lod zones - the diff?
2. Probes and voltages - what do they link to?
3. I use elk temperature sensors - can I read the temperature from these zones.
Sorry fo all the newbie questions.

First, if you haven't read the CQC info on the Elk driver you can HERE. This will explain all the details of the driver. For future reference, goto CQC web site and goto Support and then Supported devices for info on any driver you use.

1. Physical Zone is the physical state the zone is in: Normal, Violated, ... . Logzone is the logical state: Open, EOL, shorted, ...
2. Can't help you there, I don't use that (yet).
3. I assume so, under thermocouples in the client side window of CQC Admin.

No problem about the questions...you are where I was at last year. I found the support file much later and it was like a light went off...that's how you do it!!!

Good luck

Thanks mate - that's exactly what I needed - it's a bit overwhelming at the moment!!!

 

[123]

1. Physical Zone is the physical state the zone is in: Normal, Violated, ... . Logzone is the logical state: Open, EOL, shorted, ...

The nomenclature used by the CQC driver to describe Physical and Logical states is incorrect. It was based on ELK's documentation (ASCII Protocol manual) that was in error up until version 1.66. I encountered the error while developing my ELK driver; there were others.

Beginning with version 1.66 of the documentation, the correct description is as follows:

Physical zone state
• 0 Unconfigured
• 1 Open
• 2 EOL
• 3 Short

Logical zone status
• 0 Normal
• 1 Trouble
• 2 Violated
• 3 Bypassed

If a Zone is open or shorted, that is its physical state (i.e. the wire representing that zone is shorted).
If a Zone is normal or violated, that is its logical state (i.e. the zone's condition is normal).

Someone may want to report this on the CQC forum and have the driver updated.

 

[IVB]

oy crap, talk about a massively disruptive change, that is going to royally suck for anyone who has an elk driver. I probably reference Physical zones in 80+ different locations in templates & triggers.

 

[comet48]

oy crap, talk about a massively disruptive change, that is going to royally suck for anyone who has an elk driver. I probably reference Physical zones in 80+ different locations in templates & triggers.

There seem to be a couple of inconsisenties between docs and driver. e.g. I can't see the InvokeCmd field anywhere. I understand I need this to invoke tasks etc.

 

[EST]

You can see the InvoleCmd field in the Admin Interface under the browse button (last button on the second column). This is also where you select fields that you want to use as triggers. Under the Action tab of certain widgets as well as Events you use the InvokeCmd to send certain commands to Elk.

Using a command button widget I have this:

To bypass a zone:
[On Click]
Devices::Fieldwrite(Elk.InvokeCmd,ZoneBypass: 17, 1, 001234)

To run a task:
[On Click]
Devices::Fieldwrite(Elk.InvokeCmd,ActivateTask: 1)

 

[comet48]

oy crap, talk about a massively disruptive change, that is going to royally suck for anyone who has an elk driver. I probably reference Physical zones in 80+ different locations in templates & triggers.

There seem to be a couple of inconsisenties between docs and driver. e.g. I can't see the InvokeCmd field anywhere. I understand I need this to invoke tasks etc.

I worked it out