looking for hmi recommendations

[ganutenator]

Preferably one that isn't tag license based.

 

[Old Man]

Maple Systems

 

[Steve Bailey]

What do you want to do with the HMI? Do you require historical data logging?
If all you need is an operator panel, the stand-alone units like Maple Systems, Red Lion, or Automation Direct C-More are sold as a separate entity rather than on the basis of the number of tags. HMI software that runs on a Windows machine is typically tag count-based.

 

[tlf30]

If it is windows based as a requirement and does not need a robust historian, then I would recommend Ignition.

 

[bkottaras]

Maple Systems

+1

 

[robertmee]

If it is windows based as a requirement and does not need a robust historian, then I would recommend Ignition.

Huh? Ignition is probably one of the strongest and most robust historians. Much better than Aveva or FactoryTalk. Ignition is way overkill for a single HMI requirement. Maybe you're thinking Edge?

 

[tlf30]

Not sure what ignition historian you have used, but the last time I performance tested their historian was back on 8.1, and it had major issues pulling large amounts of data. I had to build my own postgres historian using timescale and build a SQL interface to replicate how ignition was accessing the database. FactoryTalk historian is just PI, and is by far one of the most superior historians in terms of performance and data storage. AVEVA historian is very good. Canary is also good for high speed data.

 

[robertmee]

Not sure what ignition historian you have used, but the last time I performance tested their historian was back on 8.1, and it had major issues pulling large amounts of data. I had to build my own postgres historian using timescale and build a SQL interface to replicate how ignition was accessing the database. FactoryTalk historian is just PI, and is by far one of the most superior historians in terms of performance and data storage. AVEVA historian is very good. Canary is also good for high speed data.

Odd...ive experienced no such issues on multiple factory rollouts integrated together for local visualization to cross division MES. In that Ignition allows for you to roll your own underlying db architecture, perhaps there was a deficiency in your setup not restricted by Ignition. We use standalone MSSQL boxes, querying 30,000 tags A second with no issues.

I can appreciate FT, Aveva and Canary from a time server historian perspective for recording data, however, I've always found their integration beyond the data clumsy and lacking. FT is overpriced, Aveva has one foot in the grave, and Canary isn't an integrated platform.

 

[mk42]

If you're looking for an embedded (not PC based) machine HMI panel, I don't think I've seen any that do tag based licensing, although most do have a system limit.

 

[I_Automation]

Depending on the need I either use A-D CMore or AdvancedHMI on a PC

 

[joseph_e2]

My first choice is generally Red Lion, followed by C-More for standalone stuff. If it's PC-Based, I've used AdvancedHMI but not in a production environment yet.

 

[anderson_ab]

I recommend Ignition 100%

 

[JesperMP]

Based on the extensive and precise description of the application and system requirements, I recommend a switch with integrated lamp.

 

[tlf30]

Odd...ive experienced no such issues on multiple factory rollouts integrated together for local visualization to cross division MES. In that Ignition allows for you to roll your own underlying db architecture, perhaps there was a deficiency in your setup not restricted by Ignition. We use standalone MSSQL boxes, querying 30,000 tags A second with no issues.

I can appreciate FT, Aveva and Canary from a time server historian perspective for recording data, however, I've always found their integration beyond the data clumsy and lacking. FT is overpriced, Aveva has one foot in the grave, and Canary isn't an integrated platform.

Ah, all the ignition work I've done is in systems that are 150k tags minimum. Usually in terms of 250k to 500k tags.

Ignition runs great on embedded computers as a standalone HMI and I think there is a free tier for such installs now, but I don't remember the details.

 

[robertmee]

Ah, all the ignition work I've done is in systems that are 150k tags minimum. Usually in terms of 250k to 500k tags.

Ignition runs great on embedded computers as a standalone HMI and I think there is a free tier for such installs now, but I don't remember the details.

the 30K was the query size/second. If you're querying 500K tags a second, I'd like to see that application. The overall tag count well exceeds 200K, but if you're having to store and retrieve 200K tags every second, you have Ignition scan classes set up wrong or deadbands set wrong.