It's the platform price with no other modules. (Now $1,100, not $1,000.) You get a handful of OPC drivers, scripting, and databases. You would have to script everything that happens with your DBs.
Add Vision 1-client and you're at $3k. That makes an extremely capable alternative to a Panelview. (:
That's not a valid option, you can't buy the platform just by itself. You have to buy at least one other module, the cheapest of which is Opto22 snap pac driver.
I am doing this this Month, however rather than buying a random module just because it is the cheapest, I am buying 1 report license at 1/5th the cost of the listed price on the website.
You can't pick it from the pricing page any more, but I bet you can still buy it.
Incorrect. PM me your email and I will forward the email from IA sales rep (senior).
For posterity, you can only buy the "standard" (official term) platform by itself, if it is part of a scale-out architecture.
If this is a stand-alone instance, and the only one for that customer, then my advice regarding at least one other module, is correct.
I, admittedly, have not dissected this thread. However, there are significant changes to Edge licensing (The New Ignition Edge) this year. If struggling to pick between Full vs Edge for a local HMI, the decision should be a LOT easier now (hint: strongly consider Edge).
Edge licensing has been completely revamped. Some noteworthy bullet points I see:
Hi everyone. I have a doubt the new Ignition Edge Historian. I got a license for Edge Panel on December 2023 and it's storing only 7 days instead of 35 days of historian data. Is any other liminitation or condition to get the 35 days for edge historian?
This was introduced around, from memory, 8.1.32. Upgrade to the latest version.
Just for clarification 8.1.35 was when the limit was extended from 7 to 35 days.
If I recall, EXISTING upgraded edge systems keep their old limit so things don't break, however I can't find where I read that now.
Once you upgrade to 8.1.35 or greater, the limit will automatically be increased. I don't think there's anything preventing an upgraded gateway from just using the new limit. I don't see how increasing the limit would break anything unless you run out of storage.
I'm wondering something about the time limitation of the edge historian: Is it based on when the record was added, or on its timestamp ?
What if I'm pushing values manually, with a forced timestamp ?
Let's say I want to store data for march 2022. That's way out of the 35 days window. Will it get removed ? When ?
I'm asking because I'm doing exactly this at the moment. I got data that's 2 years old into the historian successfully. But that was yesterday, and today it seems the data is gone. So I'm guessing it was considered too old, and pruned.
But I was able to play with it for a while though, so I'm wondering what happens exactly. Pruning on a schedule ?
edit: Note that I'd very much like to see the edge historian experience improved - Since you can't see the database itself, you need to rely on system.tag.queryTagHistory and its siblings. It's painful to dev with this. Sometimes it's hard to tell if you messed up the queryTagHistory call, or if there's actually something wrong with the data you pushed in.
Also, you can't delete records manually, gotta wait for the pruning to happen - which, again, makes development painful when you need to clean up the history to start a new batch of tests.
Pre-8.1.35 it was 7 days OR 10 Million rows (10M row limit removed if using MQTT), whatever came first.
I believe the 10M rows limit still holds true.
This can be confirmed by looking at the Store and Forward Status page to see limits on the local cache.
We had a couple of sites that had similar issues (3.5 days retention due to 10M rows limitation). Found a few (~100) overly-ambitous contributors to the Historian (poorly selected compression settings on UDT definitions). Hopefully you can find some offenders and remedy the situation with better compression settings.