Alternate Pen Source options on the Power Chart

Ignition
, ,
1

I am trying to find a way to get a pen into the power chart that is tied to a named query. I tried the DB Table Historian route, but I need a WHERE on my data and the table is not structured in a way that makes that possible with the 1 given key value for that feature. I have a named query that gives me the value and timestamp, looking for ideas on the best way to get that to a power chart. I even thought about creating a "dummy historical tag" and creating fake historical entries in the Ignition DB in a script. But that seemed too hacky. Thanks

2

You cannot. The DB Table historian is the only other option for the Power Chart.

If you cannot make your data fit the DB Table Historian's requirements, you will have to switch to the TimeSeries chart, or to one of the 3rd-party chart modules.

3

Dang. I was afraid of that. I may have to revisit my "fake tag" idea. I think we have too many other things built into this power chart tool to scrap it for this.

4

Sorry I am bringing up an old post, but I am just running into this scenario. As @pturmel mentioned, you probably just need to create a database view to make your data “fit” and have your names query point to that.

But I’m with you on having the Power Chart support DB Pens. In a hub-spoke architecture, I’d have to duplicate every single Tag Historian with a DB Table Historian pointing to the same database just to have my additional pens show up on the chart. The Easy Chart in Vision has DB Pens. The natural progression of Power Chart in Perspective would be to also support DB Pens functionality….without needing to create a separate DB Table Historian.

The props,pens.data.source property in the Power Chart accepts these two types of strings. It would be great to just specify another property to help it determine if this is a Tag Historian query or a DB direct query.

Tag Historian format:
histprov:localDB:/drv:GWName(OptionalForLocal):tagProviderName:/tag:some/tag/path

DB Table Historian format:
histprov:localDB:/table:localDBTableOrView:/column:floatvalue:/timestamp:t_stamp:/keycolumn:tagid:/keyvalue:mytagid

This would be a quick win for migrating Vision charting to Perspective.