Quinn-Curtis Forums

Quinn-Curtis Forums

All Forums

Tools for Javascript/Typescript

QCSPCChart for Javascript/GWT

Different alarm checking color for OOC and OOS

Note: You must be registered in order to post a reply.
To register, click here. Registration is FREE!

Screensize:

UserName:

Password:

Format Mode:

Format:

Message:

* HTML is OFF
* Forum Code is ON

Smilies

Check here to include your profile signature.

T O P I C R E V I E W
dbhardwaj	Posted - 21 Apr 2020 : 15:41:19 Is there a way to assign different color for the samples outside the control limits vs spec limits. In code below, I'm trying to show OOC samples in BLUE and OOS samples in RED, but looks like OOC takes precedence over OOS and it works fine if control limits are wider than spec limits. But it should be the other way round. Example 1: Spec Limits: 10 to 30 Control Limits: 5 to 35 Result: - Work fine. - Anything more than 35 or less than 5 gets marked BLUE. - Anything between 30 & 35 or 5 & 10 gets marked RED. Example 2: Spec Limits: 10 to 30 Control Limits: 15 to 25 Result: - Anything more than 25 or less than 15 gets marked BLUE. - No RED alarms gets set even when out of spec Here is the JSON: "PrimaryChartSetup": { "SpecificationLimits": { "LowSpecificationLimit":{ "LimitValue": 10 ,"LineWidth":3 ,"LineColor": "RED" }, "HighSpecificationLimit":{ "LimitValue": 30 ,"LineWidth":3 ,"LineColor": "RED" } }, "ControlLimits": { "Target":{ "DisplayString": "Target" ,"LimitValue": 20 }, "UCL":{ "LineColor": "BLUE" ,"LimitValue": 25 ,"DisplayString": "UCL" }, "LCL":{ "LineColor": "BLUE" ,"LimitValue": 15 ,"DisplayString": "LCL" } } }, "SampleData": { "DataSimulation": { "StartCount": 0, "Count": 50, "Mean": 20, "Range": 60 } } Dhruv Bhardwaj
2 L A T E S T R E P L I E S (Newest First)
dbhardwaj	Posted - 22 Apr 2020 : 12:45:32 Thanks for the quick response and clearing it up Dhruv Bhardwaj
quinncurtis	Posted - 21 Apr 2020 : 17:19:24 That version of the software is not designed to have all of the options for coloring the out of limit symbols that you seem to want to use. It does not separate the control limits and spec limits that way. In general, all > control limits have one symbol color (RED by default), and all < control limits have another (BLUE). it doesn't matter if it is a spec limit or a control limit. So when either the process value exceeds the UCL (or HSL) it will go to the high alarm symbol color, and similarly the LCL (LSL). If you set enough conflicting colors you will get anomalies. If you want both > alarms and < alarms to appear in color RED, as your setup looks, change the default colors to RED using the StaticProperties block. "StaticProperties": { "DefaultAlarmColors": { "LowAlarm": "0xFFFF0000", "HighAlarm": "0xFFFF0000", } }, Then assuming your spec limits are always outside of the HCL and LCL, the color for the symbol outside of either HCL or HSL will always be RED. But you can't add another level to also change the color if the HSL and LSL are exceeded. If you can discard the requirement that control limits and spec limits use different alarm symbol highlighting, but want something different than the defaults, we can probably tell how to do it.

Quinn-Curtis Forums