Factory Talk View -vs- Ignition

[TConnolly]

Anyone work with both?

Pros? Cons?

[bce123]

Ignition! hands down!

[rdrast]

Anything BUT FTView.

[Ken Roach]

Both software packages have their advantages and disadvantages. I have used FactoryTalk View ME very extensively, FactoryTalk View SE on a few projects, and Ignition only sparingly.

When the software choice is mine, I will try to use Ignition in the future, for several reasons.

1. Installation is significantly simpler and faster.

2. Stability is impressively better. I'm including both the core components ability to run and stay running, and the speed and volume at which patches and problems are revealed and rolled out.

3. SQL database integration in Ignition is fantastic. I don't have to convert or export or otherwise mess with my data; it's all available in SQL. While RA has connectivity to SQL, the legacy database and log formats are big headaches (and the Machine Edition stuff is proprietary and disappointing).

4. Vector graphics are very nice. It takes some work to make things line up and scale to different screens in a meaningful way (a fixed-pixel display is simpler !) but it's worth the effort. RA's launch of PV5000 next year will narrow this advantage a little at the low end.

5. Client licensing issues don't exist; the Web Launch is almost trivial to configure.

6. It's hugely powerful. I can do nearly anything in Ignition, while I frequently found frustrating limitations in FactoryTalk View (especially ME) in terms of which aspects of an object I had programmatic access to.

7. The trending and database access objects are head and shoulders above everything else I have used.

FactoryTalk View does have some advantages, especially now that it's reasonably stable. Versions 3 and 4 were not pleasant to live through, but that's in the past now. Those responsible have been sacked.

FTView is very well integrated with ControlLogix. The RSLinx Enterprise Tag Browser and Direct Referencing are by far the fastest and easiest way to get data from ControlLogix to an HMI. RA has the keys to the box of secrets for ControlLogix communication optimization, and they make it work well, especially for fast trending.

Because it's a native Windows application, it mixes fairly well with other Windows applications, including Visual Basic. If I started tossing apples from my office, I could hit one Python programmer and one Linux guru but three Windows programmers.

FactoryTalk View ME runs on the rugged and reliable PanelView Plus hardware. I've seen a lot of touchscreen PCs and none of them are as sturdy as PV+ hardware.

FactoryTalk View has a significant user base, from which you can draw experienced contractors. While I admire Inductive Automation's skill and dedication, RA just hosted an open bar on the flight deck of an aircraft carrier during their annual software training event. There's some momentum there !

This week I'm on a customer site where we have a bunch of PanelView Plus and custom software doing heavy trending and high-integrity data logging. And I find myself wishing I could do it all over again with Ignition, because of the limitations on storage, speed, reporting and connectivity in FactoryTalk.

[bce123]

Haven't tried it yet, however I am told Ignition will run on a panel view+ ?
Have not used FTV 7 yet so I will reserve the Pro/con until further research.
For now Ignition seems to be the the best HMI for the buck If you need to use data.
For a simple OP there are better deals out there!

[Ken Roach]

Ignition definitely won't run on a PanelView Plus; there is no Java SE runtime for Windows CE 5.0 or 6.0. I have seen a mockup in which the PV+ ran VNC Viewer so you had remote control of another Ignition desktop session, but that's hardly the same thing.

If I could get a limited-power, fanless touchscreen from Allen-Bradley that ran Linux or XP Embedded, I would buy them and use them as Ignition clients. Even A-B's own VersaView is physically no match for the PanelView Plus hardware.

[jstolaruk]

Originally Posted by TConnolly

Anyone work with both?

Pros? Cons?

Haven't used Ignition but they look like they could complement each other: FTView on PV+ on the floor at the machine, Ignition for the rest.

[JordanCClark]

Originally Posted by bce123

Haven't tried it yet, however I am told Ignition will run on a panel view+ ?

Ignition on a PanelView CE6 using the mobile module

HowTo on Inductive Automation's site

Been using Ignition for a few years. Getting back into FTView with some OEM-made machines. For me, overall, Ignition still wins. Ken pretty well covered everything with both packages, but I just like the extra versatility with Ignition.

[jstolaruk]

sweeet, now if they could port it for the older units a big market could be tapped.

[Oakley]

My world is heavily dominated by RA. ControlLogix is the control system of choice, and the SCADA is FTView ME.

BUT - we do have some Wonderware. A few stand-alone InTouch apps, and a few ArchestrA apps.

I love the ArchestrA approach. Once engineered and locked down, the developers (which aren't really developers, but rather configuration specialists) can manage the objects and the InTouch screens we ease and speed.

I have also began leveraging PlantPAX and some custom AOIs. Love them. Saves a lot of time programming and validating. Also forces standardization and conformance.

Now - FTView has a huge leg up with their integration with ControlLogix and PlantPAX. I wish that RA would release the methods to do the integration. I know that you can do custom programming with ArchestrA objects to achieve basically the same thing, but it isn't as tightly integrated.

I have not used Ignition, but I would love to.
How does Ignition stack up to ArchestrA?

[Fullmanido]

We went through the whole Win 32>Win 64>Skip Win 8>Win 10 mess and replaced our FTME with Ignition. Now our five year old PNLV 1000's (27) have been obsoleted and repair exchanges are no longer supported, that sealed the deal. Swapped out our first PNLV with a stainless touch screen with Ubuntu and Ignition, works like a champ.

[harryting]

Note, 2013 thread.

So, did you get the single node version of Ignition, what's the price point like and which touch screen computer did you get?

[Fullmanido]

Are RT was about $2500, the touch EX rated touch panel was $2700. We could have used a Maple touch screen for $1500, we chose the EX stainless.

[Paully's5.0]

Originally Posted by harryting

Note, 2013 thread.

So, did you get the single node version of Ignition, what's the price point like and which touch screen computer did you get?

FYI, they have now released "Ignition Edge" to be cost competitive on small systems, reduced features and such but something to explore if you have not seen it yet.

https://inductiveautomation.com/whats-new-ignition-edge

[VAN]

Originally Posted by Paully's5.0

FYI, they have now released "Ignition Edge" to be cost competitive on small systems, reduced features and such but something to explore if you have not seen it yet.

https://inductiveautomation.com/whats-new-ignition-edge

What about the 500 tag limitation on edge? I like the concept of Edge but I think that 500 tags needs to be bumped up at least to 1000 tags.