I am still trying to figure out how to use the tag historian. for example I get a tag for an event code. If it is like 2210 then I know the part was too small, shrunk too much 2211 too big, didn’t shrink enough 2212 missing a hole for the keychain 2213 deformed from the mold I also have a tag…

[image] zacharyw.larson: Just not sure how to do the 1 hour total. It seems like tag historian has a 1 hour count option, but I don't know if it works across a reset. Like if the value were 9, then shift change reset it to 0, would the tag history binding count the ones that happened in the last…

Yes, make some kind of trigger that indicates a new record/part/whatever has been processes so you know it’s a new part even if the event code doesn’t change Then just create a transaction group with a Execution time lower than the shortest time between two records could be in your process: [image…

A bunch of time has passed. I don’t understand many ways to make the tag historian useful. So many tags are historized with expectations that it would be so useful. I open a table on perspective, bind the tag history, and it shows the t_stamp in epoc. I got some things to be useful in tag histo…

I’m on the other side of the fence in that i find the historian much more useful than transaction groups. I come from a SQL background, so i am much more comfortable manipulating the data with queries, and transaction groups you don’t necessarily need to have any SQL knowledge. That said you don’t a…

if you have a tag historized that shows you the reason for a stop as a 4 digit number, how do you get the top five stops in the last month with the historian? I was taught how to do it with the transaction groups in a named query SELECT Top 40 myCode, sum(myQuantity) as Quantity, count(myCode) as …

Y'all might find this topic helpful: [image] SQL Tall/Long vs Wide Table Structure Ignition I am in the process of trying to collect high speed historical data to an MSSQL database. We would like to collect data to set up a predictive maintenance system. We would like t…

What @pturmel said. Somethings are best in the historian, others in transaction groups, and yet other times it is easier to script it based on what is going on when that data needs to be logged. Part of the trick is knowing when to use what technology.

Tag history is very convenient, transactions are not. That’s my opinion. Before you make your decision get very familiar with both. I have a feeling you don’t know either very well at all.

how do you get the top five event codes in the last month with the historian? I can get it from the transaction group. I don’t know how to get it from the historian. SELECT Top 40 myCode, sum(myQuantity) as Quantity, count(myCode) as myCode_Count FROM myTable where ( t_stamp > DATEADD(minute, -…

With scripting. Grab the data with system.tag.queryTagHistory - Ignition User Manual 8.1 - Ignition Documentation then write code to do what you want. I believe @pturmel has a module to make querying a dataset easier. There is a lot of help online for Python.

Historian help needed

Ignition

pturmel February 22, 2024, 12:47pm 33

It's name was changed: