Ignition stopped showing me trends out of nowhere. I am attaching evidecia that if I have variable reading just not graphing.
That looks like a data problem, not a trend problem.
1 Like
Trial expired?
Any errors in the local client's output console, or the gateway's logs?
Status of your DB connections?
What version of Ignition is this?
Have you contacted support?
2 Likes
Si expiro, sin embargo se cuenta con licencia.
Como reviso eso?
La conexión me la marca como conectada.
Ignition 7.1.8
Ignition relies upon a database connection to hold history for trending. You show a working database connection, so the remaining possibilities are limited:
-
The database might be full--Inserts would be failing.
-
Clocks might be out of sync between client machine and gateway or database.
-
IT may have upgrades something that affects your system. (Really old and unsupported versions of Ignition are subject to breakage when IT gets involved.)
4 Likes
When I've run into this in the past, it was a clock issue. After an unexpected power outage, VM system clocks were about a half hour behind and needed reset. Additionally, after power cycling, our Bedrock PLC's clock is set to January 1 1990 and must be reset as well; both of these have caused tag history issues for us.
I'd check the machines or VMs running your gateway and database, and then check the PLCs if VMs were matched up.
2 Likes
Como puedo saber si la base de datos esta llena?
Ya ajuste los relojes y aun no grafica.
Do you have access to the database that is connected to Ignition (via MSSQL Management Studio / SQL Developer / Etc)?
Usually when my devices are suddenly not reporting information I perform a query to see the exact moment when the data stopped reaching my database. Then you can recall if a movement was made in the firewall or something fishy that IT might have done (in my case it is always something with the firewall)