Logic Server bad events - Printable Version

Logic Server bad events - 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: CQC Support (https://www.charmedquark.com/vb_forums/forumdisplay.php?fid=9)
+--- Thread: Logic Server bad events (/showthread.php?tid=10695)

Logic Server bad events - rbroders - 10-14-2018

I have an any value change trigger on one of my logic server fields.

Recently I have noticed that pausing and resuming *any* driver on my system will cause the logic server to spit out a bogus event which causes my event handler to throw an exception.

Code:
EvID=0AC3AC054CBE1119-D2201C721B13A66A

cqsl.header

{

 ┬á ┬áv=1

 ┬á ┬ásysid=747AB624337F73FA-2FC92546E3382BF8

 ┬á ┬áclass=cqsl.fldchange

 ┬á ┬ásource=cqsl.field:Logic.FZLibraryState

}

cqsl.fldval

{

 ┬á ┬ával=-2147483648

}

EvID=0AC3AC054CBE1119-D2201C721B13A76A

cqsl.header

{

 ┬á ┬áv=1

 ┬á ┬ásysid=747AB624337F73FA-2FC92546E3382BF8

 ┬á ┬áclass=cqsl.fldchange

 ┬á ┬ásource=cqsl.field:Logic.FZLibraryState

}

cqsl.fldval

{

 ┬á ┬ával=40

}

┬áThe bogus event is immediately followed by a legit event, so it fixes itself, but it seems like a bug somewhere.

The FZLibraryState field is defined at an Int4, but the val that comes out -2147483648 cannot be converted to an Int4 thus throwing an exception in my event handler.

Code:
10/14 21:50:43-HARTFORD, CQCEventSrv, CQCEventWorkerThread0

{

 ┬á ┬áCIDLib, CIDLib_String.cpp.4727, Failed/Bad Parms, Error: 3263/0/0

 ┬á ┬áCould not convert '-2147483648' to binary value of type 'tCIDLib::TInt4'

 ┬á ┬á ┬á<CQCEventSrv> CQCEventSrv_ThisFacility.cpp - 2215

}

My logic configuration is as follows
1 FurnaceC.S1Z2_HeatSetpoint
2 FurnaceC.S1Z2_RoomTemp
3 FurnaceC.S1Z2_CoolSetpoint
((100.0 * ToFloat(%(2) - %(1)) / ToFloat(%(3) - %(1))))

I'm guessing the LogicServer gets pinged that all fields have changed, and then does its calculation before the fields have stable values and thus produces the bogus value somehow.

This problem seems to happen more than 50% of the time I resume a driver, but it is not 100%.

--Bob (5.3.2)

RE: Logic Server bad events - Dean Roddey - 10-14-2018

I'm sure that's probably it, and why it's sometimes but not others, in that it's a timing thing so there's room to go either way. I'll take a look at it.