Charmed Quark Systems, Ltd. - Support Forums and Community
5.5 Beta Discussions Thread - Printable Version

+- Charmed Quark Systems, Ltd. - Support Forums and Community (https://www.charmedquark.com/vb_forums)
+-- Forum: General Discussion (https://www.charmedquark.com/vb_forums/forumdisplay.php?fid=3)
+--- Forum: Beta Discussions (https://www.charmedquark.com/vb_forums/forumdisplay.php?fid=12)
+--- Thread: 5.5 Beta Discussions Thread (/showthread.php?tid=10858)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30


RE: 5.5 Beta Discussions Thread - Dean Roddey - 02-05-2020

You receieve a trigger that is of the user action variety. So when they press one of the buttons you should see a user action trigger that you can react to.


RE: 5.5 Beta Discussions Thread - gReatAutomation - 02-13-2020

Dean did you make any changes to the RadioRA2 driver? The RadioRA2 driver shows the high and low set points set to 77 when my physical thermo reads 78 for cooling (HighSetPnt)

[Image: Capture6.jpg]

When I attempt to update the HighSetPnt or LowSetPnt via a test IV that has worked previously, it does not work at all.

[Image: Capture7.jpg]

I am reticent to install any further betas.


RE: 5.5 Beta Discussions Thread - Dean Roddey - 02-14-2020

Some folks had reported something simillar, basically a rounding issue. At least on the most recent stuff I don't see that. I ran the set points up and down through their range and the driver always showed the same as the thermo.


RE: 5.5 Beta Discussions Thread - gReatAutomation - 02-14-2020

What do you recommend for resolution?


RE: 5.5 Beta Discussions Thread - Dean Roddey - 02-14-2020

I'm not sure. It certainly seems to work for me at any settings in the current code. There were some changes in the underlying rounding stuff, but I think that was only for when rounding negative numbers and it was well after I ran those checks. I wonder if somehow yours are at a different .x value than mine? The display only shows the rounded value. I'm not sure how they are rounding. I'm doing it to the nearest value to whatever they send, which does have a decimal digit part. I'd have thought it would always be zero since you can only set full degree increments on set points, but maybe yours aren't.

If you run it up a degree at a time, is it consistently off in the same way, or correct sometimes and off sometimes?


RE: 5.5 Beta Discussions Thread - gReatAutomation - 02-16-2020

(02-14-2020, 04:11 PM)Dean Roddey Wrote: I'm not sure. It certainly seems to work for me at any settings in the current code. There were some changes in the underlying rounding stuff, but I think that was only for when rounding negative numbers and it was well after I ran those checks. I wonder if somehow yours are at a different .x value than mine? The display only shows the rounded value. I'm not sure how they are rounding. I'm doing it to the nearest value to whatever they send, which does have a decimal digit part. I'd have thought it would always be zero since you can only set full degree increments on set points, but maybe yours aren't.

If you run it up a degree at a time, is it consistently off in the same way, or correct sometimes and off sometimes?

Here are the logs. There is definitely something going on for one reason or another.

Code:
02/16 14:03:50-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:03:55-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.2398, Status/App Status
    Error in Int fld write: Lutron Error. Code=4
}
02/16 14:03:55-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCKit, CQCDriver_DriverBase.cpp.7616, Status/Lost Connection
    Driver 'RadioRA2' has lost connection to it's device
}
02/16 14:03:55-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCKit, CQCDriver_DriverBase.cpp.7650, Status/Lost Connection
    Driver 'RadioRA2' has lost its communcations resource
}
02/16 14:03:55-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCKit, CQCDriver_DriverBase.cpp.3636, Status/App Status
    Driver 'RadioRA2' is trying to get its comm resource
}
02/16 14:03:55-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCKit, CQCDriver_DriverBase.cpp.3675, Status/App Status
    Driver 'RadioRA2' has its comm resource
}
02/16 14:03:55-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCKit, CQCDriver_DriverBase.cpp.3693, Status/App Status
    Driver 'RadioRA2' is trying to connect to its device
}
02/16 14:03:56-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCKit, CQCDriver_DriverBase.cpp.3743, Status/App Status
    Driver 'RadioRA2' has connected to its device
}
02/16 14:04:16-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:04:28-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.2398, Status/App Status
    Error in Int fld write: Lutron Error. Code=4
}
02/16 14:04:28-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCKit, CQCDriver_DriverBase.cpp.7616, Status/Lost Connection
    Driver 'RadioRA2' has lost connection to it's device
}
02/16 14:04:28-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCKit, CQCDriver_DriverBase.cpp.7650, Status/Lost Connection
    Driver 'RadioRA2' has lost its communcations resource
}
02/16 14:04:28-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCKit, CQCDriver_DriverBase.cpp.3636, Status/App Status
    Driver 'RadioRA2' is trying to get its comm resource
}
02/16 14:04:28-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCKit, CQCDriver_DriverBase.cpp.3675, Status/App Status
    Driver 'RadioRA2' has its comm resource
}
02/16 14:04:28-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCKit, CQCDriver_DriverBase.cpp.3693, Status/App Status
    Driver 'RadioRA2' is trying to connect to its device
}
02/16 14:04:29-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCKit, CQCDriver_DriverBase.cpp.3743, Status/App Status
    Driver 'RadioRA2' has connected to its device
}
02/16 14:04:49-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:05:09-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:05:29-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:05:50-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:06:10-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:06:30-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:06:50-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:07:10-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:07:19-CQC, CQCServer, CQCIRActThread_HTTPTrigger
{
    CQCAct, /Security/AlarmDecoder/RFXMessage.0, Warn/App Status
    /Security/AlarmDecoder/RFXMessage
}
02/16 14:07:30-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:07:50-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:08:10-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:08:30-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:08:51-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:09:11-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:09:31-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:09:51-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:10:11-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:10:31-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:10:51-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:11:11-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:11:31-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}
02/16 14:11:36-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.2382, Status/App Status
    Low SP must be < High SP
}
02/16 14:11:36-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCKit, CQCDriver_DriverBase.cpp.7067, Failed/Not Found, Error: 2016/0/0
    The value written to field RadioRA2.THERM#Thermostat~LowSetPnt was rejected by the driver. Reason=CmdParms
    Invalid Command Parameters
      <CQCServer> CQCDriver_DriverBase.cpp - 8617

}
02/16 14:11:36-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCKit, CQCDriver_DriverBase.cpp.7067, Failed/Not Found, Error: 2016/0/0
    The value written to field RadioRA2.THERM#Thermostat~LowSetPnt was rejected by the driver. Reason=CmdParms
    Invalid Command Parameters
      <CQCServer> CQCDriver_DriverBase.cpp - 8617
      <CQCServer> CIDOrb_ThisFacility.cpp - 598
      <CQCAdmin> CQCKit_CQCSrvAdminClientProxy.cpp - 1976
      <CQCAdmin> CQCAdmin_DrvMonTab.cpp - 1328

}
02/16 14:11:52-CQC, CQCServer, CQCDrv_RadioRA2Thread22
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Lutron.RadioRA2.DriverImpl.1948, Status/App Status
    No recent asyncs, doing active poll
}



RE: 5.5 Beta Discussions Thread - Dean Roddey - 02-16-2020

Most of that looks fine. It's just the driver saying that the thermostat hasn't talke to me in a while I'm going to ping it to make sure it's still there and it is. The errors at the end look like you are trying to write to the field from the driver monitor tab and that's failing? What value where you trying to write? It looks like it didn't like the value.


RE: 5.5 Beta Discussions Thread - gReatAutomation - 02-17-2020

(02-16-2020, 02:40 PM)Dean Roddey Wrote: Most of that looks fine. It's just the driver saying that the thermostat hasn't talke to me in a while I'm going to ping it to make sure it's still there and it is. The errors at the end look like you are trying to write to the field from the driver monitor tab and that's failing? What value where you trying to write? It looks like it didn't like the value.

I am simply trying to change the set point. Here is the thermo, set at 78 (High Set Point). The Heating (Low Set Point is showing bot 77 in the thermo and the driver). Trying to make a change in either set points from the driver or from an IV results in the driver going to all ????. What is Lutron Error Code=4?


[Image: IMG-2207.jpg]

And here is what the driver is displaying (High Set Point of 79 versus thermo value of 78).

[Image: Capture.jpg]


RE: 5.5 Beta Discussions Thread - Dean Roddey - 02-18-2020

That's pretty weird. Does the other set point do the same?


RE: 5.5 Beta Discussions Thread - Dean Roddey - 02-18-2020

One issue is that the set points can't cross or the driver will complain. So when they were set to the same value, it was having a problem with that. I guess it should allow them to be equal at least.