Ignition Features and Ideas

Would be nice to be able to click on an image that is in the image component and there would be a native feature that would result in this click opening a focus popup that you can pan and zoom on the picture, similar to the way many applications handle images when they are clicked on

We ran into an issue where our gateway redundancy sync fell behind, resulting in an unsuccessful failover on a production system at Merck. We'd love to see a System Tag added for monitoring the Sync Status of the Redundancy. Thanks.

Be able to save script in the script console would be great.

Currently have to use kepware's driver for Beckhoff PLC, and would be great to have a direct connection using a driver in Ignition

It would be nice to be able to bind Item Names/Tag Paths (as a string or maybe utilizing indirect tag binding) and Target Names to a dataset tag. I'm writing data from PLC to SQL using Transaction Groups, and multiple transaction groups are writing to the same SQL table. Instead of navigating through each group individually on Ignition, it would be nice to have the ability to bind those properties to a dataset, so that I can directly modify that instead of individually updating the transaction group settings and any Named Queries that we're using to pull the recorded data from SQL.

I'd like the ability to pop out project scripts into a separate window like we can with the Tools (Script Console, Database Query Browser, etc.). In general, the ability to pop out (and/or dock) any type of tabbed resources (especially independent ones like the script editor and named queries) (even Vision Windows and Perspective Views, if that's feasible) for a more multi-threaded designer experience could be really helpful to my workflow. Projects I work on can get complex, and sometimes I have to jump quickly between scripts, windows, and named queries. It can be hard to keep track of where I'm at and what I was last looking at. But being able to see and edit the named query that's called by a function that's called by a vision component all on the same screen would make that process way easier. I don't know how big of an ask this is from a programming standpoint, but from a workflow standpoint, it would be huge for me.

Are there any plans to add a dark theme to the ignition designer? I see that this question has been posted a few years ago but its 2020 now so I thought I would ask again.

Tag history storage and easy chart with support of a Time Serie DB like Influx DB or TSDB

In a normal use case, we use Microsoft Sql Server, but when we work with some provider, we need to switch to Sqlite or Postgres during development. Some queries are the "same", but in some case, we need a different query depending on the driver used. Would be nice to be able to define a different version of a query, depending on the driver in use.

I think it would be very useful if TCP driver had an option to choose if we want Active or Passive connection to the other party. Currently, TCP driver is Active connection only. Active connection means, that TCP Driver will initiate the connection to the other party, which must be in passive (listen) mode. Passive connection means, that TCP driver will be in passive (listen) mode, and another party will initiate the connection to the Ignition. I have an upcoming project with 25 WLAN (wifi) handheld scanners. The scanner sends barcode string to the remote IP and port, but the remote IP must be in listen (passive) mode because the scanner is initiating the Active connection. And now I can't use these scanners directly with Ignition because Ignition TCP Driver is also Active connection initiator. I was on the phone with Ignition support and together we established, that this is the current situation. In order to get this implemented ASAP, they asked me to submit a new feature request and if enough people would find useful, then they'll do something about it. :smiley: So, we need an option to choose Active/Passive connection in existing TCP Driver or another TCP Passive Driver (listen mode).