Elk Driver and Counters

[Ron Haley]

Does the Elk Driver support access to the Elk counters? I can't find them.
Ron

[wuench]

Not supported in the Elk protocol (and therefore the driver) at this time. But several have requested it from Elk.

[Ron Haley]

Thanks - BTW, I think there ia a bug in your Elk time macro. The display goes from 08:00AM to 07:15AM with a decrease of one minute. Am I going something wrong?

[wuench]

Yep, you are right. I'll take a look at it. Elk really screwed up with the time representation of custom values, they made it so difficult to work with.

Hopefully if we get that code worked out, maybe we can get it added to the driver itself so we won't need the macro and all the action code anymore.

[wuench]

Well, the macro is working fine. It is the ELK that is screwing it up. That numeric value actually translates to that time into the ELK.

So for example, the if the custom value is 2048 that equals 8:00 am. But the value of 2047 equals 7:15am. At least according to ElkRP. I am going to post on their forum and see if they can give me a better algorithm for this...

What it looks like is we'll need a better way to set values. The Macro only converts from decimal to time, not the other way around. It probably needs a method added to convert time to decimal.

[wuench]

Not supported in the Elk protocol (and therefore the driver) at this time. But several have requested it from Elk.

And now that I look at the protocol document, I was wrong about this. It looks like Counters are available in the latest version of the protocol.

[Ron Haley]

And now that I look at the protocol document, I was wrong about this. It looks like Counters are available in the latest version of the protocol.

Is that a Dean issue?

[Dean Roddey]

They weren't available at the time that the last updates of the driver were done, so the driver doesn't support them. They'd have to be added.

[Ron Haley]

Well, the macro is working fine. It is the ELK that is screwing it up. That numeric value actually translates to that time into the ELK.

So for example, the if the custom value is 2048 that equals 8:00 am. But the value of 2047 equals 7:15am. At least according to ElkRP. I am going to post on their forum and see if they can give me a better algorithm for this...

What it looks like is we'll need a better way to set values. The Macro only converts from decimal to time, not the other way around. It probably needs a method added to convert time to decimal.

Thanks - I'm integrating a Pool Control screen into your BlueGlass design. I'll send you a copy when I've completed it. I built a nice elk relay based control system for the pool cleaning, Jacuzzi heat and pool cover control.