Ideally, seek a solution that does not rely on license tags.
Maple Systems: Your Source for High-Quality Control Solutions
Are you looking to utilize the HMI for historical data logging? If you simply need an operator panel, stand-alone units such as Maple Systems, Red Lion, or Automation Direct C-More are available as individual purchases rather than being based on tag quantity. HMI software designed for Windows machines usually operates on a tag count system. Explore your options for HMI functionality and compatibility with these popular standalone units.
If your system requires a Windows-based platform and doesn't require a sophisticated historian, then I suggest considering Ignition for optimal performance.
The elderly man mentioned the benefits of using Maple Systems. Click to learn more and discover how it can improve your processes. +1
According to tlf30, if you require a Windows-based system that does not need a sophisticated historian, you may want to consider Ignition. Ignition is known for being one of the most powerful and reliable historians compared to Aveva or FactoryTalk. However, for a single HMI requirement, Ignition may be considered excessive. Perhaps you meant to consider Edge instead?
I am not sure which historian you have utilized for your ignition system, but the last time I tested its performance was on version 8.1, and it encountered significant difficulties when handling extensive data loads. As a result, I had to create a custom postgres historian with timescale and develop a SQL interface to mimic the way ignition interacted with the database. Unlike FactoryTalk historian, which is essentially PI, AVEVA historian stands out as a highly efficient option with exceptional performance and data storage capabilities. Additionally, Canary is well-suited for high-speed data processing.
In a discussion about historians, a user shared their experience with different systems. While some have had issues with Ignition's historian in the past, others have found it to be reliable when integrated properly. The FactoryTalk historian, similar to PI, is praised for its superior performance and data storage capabilities. AVEVA's historian is highly regarded, and Canary is known for handling high-speed data effectively. Although some users appreciate FT, AVEVA, and Canary for their data recording capabilities, they find their integration features lacking. FT is considered expensive, AVEVA is seen as struggling, and Canary is not seen as a fully integrated platform.
If you're in search of a machine HMI panel that is embedded (not PC-based) with tag-based licensing, it may be challenging to find one as most options typically have a system limit.
I choose between A-D CMore and AdvancedHMI on my PC based on my specific requirements. This decision allows me to maximize the functionality and effectiveness of my automation software.
When it comes to my top picks for HMI systems, Red Lion stands out as my go-to choice. For standalone applications, I often turn to C-More. Although I have experience with AdvancedHMI for PC-based systems, it has yet to be implemented in a live production environment.
I highly recommend using Ignition for optimal performance.
After analyzing the detailed specifications and demands of the application, my suggestion is to opt for a switch that comes equipped with an integrated lamp.
Robertmee expressed surprise at experiencing no issues during various factory rollouts that were integrated for local visualization across division MES. Ignition provides the flexibility to customize the underlying database architecture, suggesting that any problems may have stemmed from the setup rather than Ignition itself. Utilizing standalone MSSQL servers, the system was able to handle querying 30,000 tags per second without any issues. While acknowledging the merits of FT, Aveva, and Canary in terms of time server historian capabilities, the integration beyond data recording was deemed lacking and cumbersome. FT was considered expensive, Aveva's future seemed uncertain, and Canary was criticized for not being an integrated platform. The projects Robertmee worked on with Ignition typically had a minimum of 150k tags, often ranging from 250k to 500k tags. Ignition was found to perform well on embedded computers as a standalone HMI, and there may now be a free tier available for such installations, although specific details were not recalled.
tlf30 mentioned that the ignition work they have experience with typically involves systems with a minimum of 150k tags, ranging up to 250k to 500k tags. Ignition performs well on embedded computers as a standalone Human-Machine Interface (HMI), with a new free tier available for such installations. The 30k query size per second was mentioned, but querying 500k tags per second would be impressive. If you are struggling with storing and retrieving 200k tags every second, it may be due to incorrect setup of Ignition scan classes or deadbands.
In his recommendation, JesperMP emphasized the importance of integrating a lamp switch that aligns with the detailed application and system requirements. It is essential to include labels for the lamp to ensure smooth operation and easy identification.
lostcontrol suggested adding labels for the lamp to make it easier for operators. Why make things more difficult than they need to be?
If you're looking for affordable HMI options, don't miss out on the Red Lion and C-more CM5 series. Also, check out AdvancedHMI for advanced solutions.
Pro-face is no longer as popular as it used to be among consumers.
In search of a more cost-effective alternative to a pc-based Wonderware system for a client's remote access needs. Considering options like Red Lion, Proface, and Maple interfaces among others. Ignition is highly recommended but may be out of budget. Exploring Advanced HMI as a potential solution. Appreciating RS View and other well-known brands, but keeping in mind the client's status as a small OEM.
When it comes to programming PLC tags on a Windows PC, my top choice is to utilize Ingear drivers for reading and writing. For creating interactive displays, Symbols Factory is my go-to tool. By purchasing a developer license, you have the flexibility to use it across multiple projects. I rely on Net.Studio for designing displays, allowing me to create an unlimited number of systems. While there may be a learning curve, your potential is only limited by your imagination. It is worth noting that most HMIs today run on Windows, including older AB Panelviews which were originally DOS-based before the introduction of Windows.
User ganutenator expressed their preference for RS View, stating that they love it. While opinions may vary, it's great to hear that this software option is working well for them. Let's keep the conversation respectful and constructive.
In response to mk42's comment, I want to respectfully express my differing perspective. While some may find RSview32 to be a necessary tool, personally, I did not hold any strong affection for it. However, it did prove to be valuable in maintaining my business for a period, especially with a VBA code application that required significant effort to convert to SE. As the saying goes, "Everyone has a soul mate," and for some, RSview32 may fit that description. Ultimately, it comes down to individual experiences and preferences in the world of industrial automation software.
Answer: 1. Q: What are some recommended HMI solutions that do not require license tags? Some HMI solutions that do not rely on license tags include [list relevant solutions here].
Answer: Using HMI solutions without license tags can help reduce costs, simplify deployment, and eliminate the need for ongoing license management.
Answer: You can explore different HMI software providers, compare their offerings, and specifically look for solutions that explicitly mention not requiring license tags.
Answer: While HMI solutions without license tags offer benefits, it's important to consider factors such as support, updates, and scalability to ensure they meet your specific needs.