Recent Posts

Pages: [1] 2 3 ... 10
1
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« Last post by broconne on Today at 07:58:37 am »
So far...WOW! So much better! Even just clicking the device in EMS, it used to take up to 5 minutes to populate, now it's almost instant. Everything about the driver is faster. Great job!

I knew there was a thread about this so I looked it up. Here it is:
http://www.codecoretechnologies.com/community/index.php?topic=430.msg2168#msg2168

Most may have already been included but I would still like to be able to view the logs from Elve. This is the equivalent of "read from controller" in pc access.
Glad you like it.  The reason its faster is because I had to change the core of the driver and maintain the hai state in my own objects in memory.  I have no idea what the core hai library does when you query its fields, but that is why it was breaking in 2.1 the underlying hai library was too slow.
2
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« Last post by broconne on Today at 07:54:56 am »
Finding some issues with rules that trigger off of flag changes. They seem to trigger multiple times and sometimes multiple rules are triggering from one flag, a flag that should only trigger one rule.
I remade all HAI rules and will see if theres any change.
Also, still getting the negative light error.

Code: [Select]
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
Setting status to negative(-95) for unit(UNIT 137) original status (5)

Code: [Select]
Date:     11/22/2014
Time:     5:01:39 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
HAI Omni Driver received unsolicited packet (shown in hex): 21 0A 3B 02 07 00 89 05 00 00 00 00 DB 1D 00 00 4E 4D 91 07 72 65 65 74 8D 94 00 00 00 00 00 00 86 00 19 4A 00 00 00 00 00 00 00 00 00 00 00 00 EF A3 1E 87 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 46 F2 00 00 00 98 D2 3A FA 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Code: [Select]
Date:     11/22/2014
Time:     4:58:36 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
Setting status to negative(-96) for unit(UNIT 137) original status (4)

Code: [Select]
Date:     11/22/2014
Time:     4:58:35 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
HAI Omni Driver received unsolicited packet (shown in hex): 21 0A 3B 02 07 00 89 04 00 00 00 00 E6 DD 00 00 6F 39 68 2F 91 00 00 00 00 00 00 00 00 00 00 00 77 A9 F5 38 00 00 00 00 00 00 00 00 00 00 00 00 EF A3 1E 87 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 46 F2 00 00 00 98 D2 3A FA 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

The weird thing is unit 137 isn't even used. But in Elve it does now show a level of 5, and in pc access in shows Scene D??
Do you have an example rule I can make a test case?  Also, is this a rule where the hai changes the flag and elve observes?  Or is elve also adjusting flag value?
3
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« Last post by Frunple on November 22, 2014, 04:19:45 pm »
Finding some issues with rules that trigger off of flag changes. They seem to trigger multiple times and sometimes multiple rules are triggering from one flag, a flag that should only trigger one rule.
I remade all HAI rules and will see if theres any change.
Also, still getting the negative light error.

Code: [Select]
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
Setting status to negative(-95) for unit(UNIT 137) original status (5)

Code: [Select]
Date:     11/22/2014
Time:     5:01:39 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
HAI Omni Driver received unsolicited packet (shown in hex): 21 0A 3B 02 07 00 89 05 00 00 00 00 DB 1D 00 00 4E 4D 91 07 72 65 65 74 8D 94 00 00 00 00 00 00 86 00 19 4A 00 00 00 00 00 00 00 00 00 00 00 00 EF A3 1E 87 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 46 F2 00 00 00 98 D2 3A FA 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Code: [Select]
Date:     11/22/2014
Time:     4:58:36 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
Setting status to negative(-96) for unit(UNIT 137) original status (4)

Code: [Select]
Date:     11/22/2014
Time:     4:58:35 PM
Severity: Debug
Source:   DriverService
Computer: OPTIPLEX755
Context Type: Driver
Context Name: HAI Omni Pro II - Debug : HAI Omni Pro II - Debug
Description:
HAI Omni Driver received unsolicited packet (shown in hex): 21 0A 3B 02 07 00 89 04 00 00 00 00 E6 DD 00 00 6F 39 68 2F 91 00 00 00 00 00 00 00 00 00 00 00 77 A9 F5 38 00 00 00 00 00 00 00 00 00 00 00 00 EF A3 1E 87 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 46 F2 00 00 00 98 D2 3A FA 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

The weird thing is unit 137 isn't even used. But in Elve it does now show a level of 5, and in pc access in shows Scene D??
4
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« Last post by Frunple on November 22, 2014, 10:24:50 am »
So far...WOW! So much better! Even just clicking the device in EMS, it used to take up to 5 minutes to populate, now it's almost instant. Everything about the driver is faster. Great job!

I knew there was a thread about this so I looked it up. Here it is:
http://www.codecoretechnologies.com/community/index.php?topic=430.msg2168#msg2168

Most may have already been included but I would still like to be able to view the logs from Elve. This is the equivalent of "read from controller" in pc access.
5
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« Last post by broconne on November 21, 2014, 01:56:17 pm »
No status. Nothing to bind to a boolean to tell if the door is locked or unlocked.

Ok, I will take a look at that.  I just sent you a new driver with the thermostat support you requested.
6
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« Last post by Frunple on November 21, 2014, 01:14:29 pm »
No status. Nothing to bind to a boolean to tell if the door is locked or unlocked.
7
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« Last post by broconne on November 21, 2014, 12:43:34 pm »
I'm in!
Still need access control added.
Also, if you can find a way to get the actual "running" status of the thermostats, that would be great. Meaning when the system is actually heating or cooling.
I'll see if I can think of other things that were missing.

What is missing from an access control perspective?  I see Lock/Unlock for doors..
8
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« Last post by Frunple on November 21, 2014, 08:54:37 am »
I'm in!
Still need access control added.
Also, if you can find a way to get the actual "running" status of the thermostats, that would be great. Meaning when the system is actually heating or cooling.
I'll see if I can think of other things that were missing.
9
Elve Version 2.1 Beta / Re: Elve 2.1 Beta Download
« Last post by broconne on November 21, 2014, 07:41:19 am »
I have finished converting over the entire HAI driver to use the new methods...  So I need someone to help me test it out..
Also, if there is any functionality someone wants in the HAI driver now is a good time to ask while the details are still fresh for me.

10
Touch Screen Interfaces / Re: Boolean and multiple lights?
« Last post by Frunple on November 18, 2014, 07:08:38 am »
Update.

Turns out this is working fine but when the second, or third etc, light changes, the TS does not update immediately. If I leave that screen and go right back the change is shown.
Any way to use the "boolean value changed" event to update the screen?? Maybe a refresh?


I got it working. Had to use the "device property changed" event instead.
Pages: [1] 2 3 ... 10