Introducing Flintium! An open source library of Ignition faceplates

Very cool project and idea, thanks for sharing. We love seeing this sort of collaborative effort in the Ignition community!

1 Like

This is a great idea! Excited to try this out and appreciate your efforts to bring this to the community and provide a Wiki.

1 Like

Thanks Benjamin, I’d love to hear your thoughts once you try it out!

Thank you for sharing. That is what makes our community so great!

1 Like

Hi Jospeh.Burns,

First of all, nice job done with the Library, Looks Great!.

I have Tried to Play Around with This Flintum Library, as I Have a Customer which Wants Ignition, but I’m coming from PlantPAX Based system normally, and i Want the Same Functionality and Look, So i Came Across this Library. I have Succesfully got this up running and everything.

The Issue is:
Have Any of you Guys had Problems With Communication with Multiple AOI with this Library?
I Seems like the Gateway is Choking?

i Have Around Tags Linked to the PLC, And it seems like the Gateway is Choking if we Implement more than 10. The Response Times is somehow between 30 sec - 1 Minute.
If i Only have 10 motors, everything is good.

CIP Connection Sizes is set to 4002. and Max Memory is set to 4096.

Has anyone had a Workaround of how to Fix this problem, or has gone another way?
i’m A bit Curios if this Library only works with Small Prcoess Plants?

Kind Regards

Reading directly from AOIs is not efficient. See this thread for more info.

On top of what @JordanCClark stated, you should also created tag groups. For example, the “Cfg” tags don’t need a fast rate, something like 5-10 seconds is more reasonable.

I had issues with AOIs as you described, but not at the small quantity you have. I agree that you should move towards UDTs, but I also wonder if there isn’t something else going on in your setup.

Not sure what you mean when you say Is that a european comma? e.g. 550000 tags? or am i misinterpreting? Cause that’s a buttload of tags! I wouldn’t be at all surprised though being BloatPAX…

As @nminchin said, I’m not sure exactly what you mean by If you mean 550,000 and by max memory you mean the Max Java Heap Size. I’m curious what the rest of the gateway set up is.

How much memory does the server actually have available and are there any other applications running on the server?

Mabye i was to quick Writing, but yeah, I Mean 550,000 Tags for an Example (Half a Million of tags) after Importing My Program Tags into Ignition.

After that, using the Flintum Library etc. is just Chokes the Gateway and response time is 30 sec-60sec.
By Now i’m Pretty sure it has something to do with the Logix Gateway Ignition is using or has, Compared to RSLinx that i’m Familiar with. It Could be the Optimized Communication Rockwell do, that Ignition cant ? Any Thoughts on that?


Is this Picture below Helpful for you?
Cpu is at 5-10 %, sometimes Peeks to 25%
But my Memory Usage is Constantly High.

How many devices for 550,000 tags? You mentioned 10 motors it’s fine. How many tags for 10 motors? I liked the idea of PlantPax but it’s way too much bloat, I took what they had and stripped it down and then used UDTs.



You didn’t answer the other questions.

How much memory (not allocated memory but total memory) is available on the server?
Are there any other applications running on the server?

When you say you imported the tags, do you mean you grabbed all tags, or you actually have 500K tags you will need for your application?

Also what’s the load factor of your plc in the igntion gateway status under devices?

At This Moment 16Gb Of Memory is Available for the Server. Also Possible to Turn this up if you think that Could Help. But didnt See Any Changes, Going From 8 to 16.
And no other Application is Running, Except Studio 5000 for PLC Development.

I have made a VBA Code, that Creates all my Tags from my PLC (P_Motor, P_ValveSO, P_ValveC, Etc) Into a Json File after playing around with Flinktum and made it work. So this I can Import, and i also have connection for all Motors Etc when its done, but the Gateway Gets Choked,.

So Yes, I Will need those 500.000 Tags, as this is needed to get the FULL Functionality, that the PlantPAX has and FLintum :slight_smile:

550,000 OPC tags will require a well-spec’d gateway and an incredible amount of patience on your part because there is no ControlLogix model that exists that would be able to serve those up via explicit messaging in any reasonable time.

A look at the diagnostics page (response times and overload) should clue you in.

Are you grabbing EVERY tag in the AOIs?

Anything Between 10-25 %

Note that i’m using, or the Plant has a Total of:
2 x L81ES - Rev 32 Firmware
2 x L82ES - Rev 32 Firmware
1 x L83ES - Rev 32 Firmware

Seems fairly small, to be honest. A customer of ours has 70+ PLCs and only have 350k Ignition tags, but they’re not using BloatPAX. We have issues with reading more than 15k tags from PLCs (a few are 81’s) with load factors above 100% reading AOI tags.

I’m Grabbing what is needed to get a FULL 100% Functionalty like PlantPAX has? Dont know if you are Familiar with this DCS System and how Tag Consuming it is?.
But i Know that Hidden Members Etc. in the AOI can cause problems :slight_smile:

But Maybe the Flintum Library is To much for Ignition Gateway to Handle a big Process Plant Using only Rockwell AOI with no Changes or Re-programming of them, that intended to or hoped for.

But Me and my Programmer have just got an Idea of how to use a UDT, instead of Reading Directly to and inside the AOI.
So I will re-program and test this during the weekend. :slight_smile: