Does anybody have an idea, how to use/manage fairly simple recipes on the Ignition Edge gateway (where are no database connections and no transaction groups), installed on the panel PC (Win10) on the machine?
The customer has a welding machine, where they weld various different parts. Each part has its own tool which has an ID number. When they change the tool, the various setting on the machine (which is controlled by Siemens PLC) must be changed according to the ID number.
If I could use the SQL database and transaction groups, that wouldn’t be a problem (I’ve done it before).
But on Edge I can’t use that, so what other options are out there?
I’m sure that I’m not the only one who stumbled upon this…?
Consider maintaining a dictionary of dictionaries in a script module. Initialize the dictionary from a JSON or XML file at the top level of the script module. Save the dictionary back to the file whenever your UI makes changes or additions. Recipe selection and viewing would simply look up the relevant information in that dictionary and write to your tags.
Thanks, @pturmel.
I found this: TinyDB
Probably no one used until now, because it needs python 2.6+. But with Ignition 8 it will be possible…?
Maybe something similar exist already for python 2.5?
A dataset tag should do the trick, assuming it can be used the same way on Edge. It’s also easy to backup/restore to/from CSV if needed (we have had memory tags lose values once on an Ignition server).
That is the way we did it before we started to use Ignition. We didn't like it, but if there is no other way, then... yes.
I've done some preliminary testing with TinyDB in Ignition 8 and so far it's looking pretty good.
If the project comes after the release of the Ignition 8, then I'll probably use the TinyDB. If not then dataset tag....
