Relays not graphing

[Michael McSharry]

The mcsTemperature debug shows that during that for the full duration of the test there was no status change of any device reported by HS. The Ocelot Comm Log shows the following reported to HS

9/11/2009 7:33:17 PM SECU16 Setting device \12 to  2

This correlates to the source code

1740                                  If cs <> stat Then
1750                                      If gLogComms = 1 Then
1760                                          WriteLog "SECU16 Setting device " + h + Trim(Str(j + 8)) + " to " + Str(stat)
1770                                      End If
1780                                      hs.SetDeviceStatus h + Trim(Str(j + 8)), stat
1790                                      callback.ValueChangeEvent h & Trim(Str(j + 8)), p
1800                                  End If

This shows that ADIOcelot is doing what it was designed to do

I then looked at mcsTemperature and see that no discretes are being recognized in the setup. I see that I was only looking for input discretes (switch type) and not for output discretes (relay type). I make this change is V6.0.2 http://board.homeseer.com/showthread.php?t=137503. Also make certain in your setup that you do have a database field name entered for the relay.

Mike,

got busy over the holiday weekend and finally got around to getting that debug data .. sent an e-mail with files attached .. let me know what you come up with ..

Pete

[Michael McSharry]

I asked a similiar question to HST and never got an answer. The pattern that was used in ADIOcelot was based upon the original HST Ocelot pluign. There were just some things added to it to improve its usabilty.

Have you collected any debug data yet?

Mike,

maybe a shot in the dark..but anyway..

in the ADIOcelot code, what is the difference between device types Interface I/O and Interface Output? The acFan and acCond I'm trying to graph are device type Interface Output.

The temp sensors are Ocelot variables and the AC devices are relays on a Secu16 (I/O points). I'll enable debug and put the devices thru their paces and see what I come up with ..

[Michael McSharry]

The log message when debugging is enabled in ADIOcelot for a IO point change is below. Note that both a status change and a value change is done.

300                       hs.SetDeviceStatus sDC, stat
310                       callback.ValueChangeEvent sDC, p
320                       If gLogComms = 1 Then
330                           WriteLog "Set HS device: " & h & sDC & " to " & mess
340                       End If

If you have both plugin debugs enabled then they may info to help understand. Most CMAX programs communicate with HS via variables. Variables are not IO points and variables will not have a Device Status change. The variables values are conveyed to HS as Device Value.

I'm using ADIOcelot 1.14.0.3 .. by you and GD (not the HS version). Never made any major changes to anything, so I don't know why the relays aren't being picked up by mcsTemp? If I toggle the status of the relays within my CMax program they work as expected and the changes are reflected in the HS device status ..

any other ideas on where things are going screwy ?

[Michael McSharry]

On any device status change reported by HS, the following line is executed by mcsTemperature. This will be for any HS device even if it has not been setup in mcsTemperature. You need to check with the plugin author of whatever you are using to control the relay to assure that the Device Status is being managed. HS will display the Device String if it is not empty in the status column. This will not necessarily be the Device Status.

70        If DebugLog Then
80            hsWritelog PLUGIN_DEBUG, "Check Device Event " & device & "=" & CStr(iCommand) & ",DictionaryExists=" & CStr(DiscreteDeviceDictionary.Exists(device))
90        End If

yes, the relays are showing on/off as they should on the hs device status page .. I'm not seeing anything in the debug log file either ??

[Michael McSharry]

Do the relay devices change status (not value) when they go on/off? I believe the general debug will capture the events that are being provided to mcsTemperature. You can enable it, change a relay, and then disable it again. The file will be in the \data\mcsTemperature folder.

Sent those files as requested. I took a look at the db and don't see any data, although the table and labels look OK.

Why would the data not be getting recorded?

[Michael McSharry]

Daily is the graph of your entire database quantized by day. It is not something one normally uses.

The relay that you are trying to graph shows in the table to always be in the 0 state so there are no transitions to chart. If your relay state is changing then it should be in the database. There is a table for each discrete. You can look or provide your mcsTemperature.mdb and mcsTemperature.ini at mcsSolutions at CenturyTel dot net.

Your table data shows your selected discrete to always be 0 so there were no transitions to graph.

where do I change this?

updated to V6, and while I'm not sure what the 'Daily' time period used to look like, but now it looks like the screen shot below .. '24Hour' still looks good (minus the relays) .. '6Hour' still is just the table with "No Items Selected For Line Graph" ..

[Michael McSharry]

http://board.homeseer.com/showthread.php?t=137153

Your table data shows your selected discrete to always be 0 so there were no transitions to graph. I expect it to still graph the analog data. In any case go with V6 as we can work from there.

If I select the 6 hour scale all I get is the table and "No Items Selected For Line Graph" even though the same devices are checked. I was manually controlling the acFan for the screen shots, but the acCond has been running for a few days (on and off, controlling temp, as expexted) and I get the same thing if trying to graph it's runtime. Running 5.18.0.3 from the V5 sticky. Were can I get V6?