We are facing critical issues in our current setup involving OPTO 22 GROOV EPIC PR2 PLC and the Ignition Full V8.17 system

Ignition
1

We are facing critical issues in our current setup involving OPTO 22 GROOV EPIC PR2 PLC and the Ignition Full V8.17 system.

Our system configuration includes-

  1. OPTO 22 PLC: First Ethernet port- Serum Corporate IP & Second Ethernet port- Local IP of Siemens PLC network.

  2. Implemented Data store-and-forward within the OPTO 22 PLC.

  3. Established communication between Ignition and 6 nos of Siemens PLCs using OPC devices within the OPTO 22.

  4. Integration of 6 databases communication with SQL 2019 in the Ignition system.

Following issues occurred frequently in both Ignition and the OPTO 22 PLC-

  1. Inconsistencies in database communication, where data from one PLC occasionally fails to lock into SQL.

  2. Intermeditely all PLC data is locked into SQL, yet updates to tags from one PLC fail to reflect in Ignition Designer.

  3. Difficulty in pinpointing the root cause of these issues within the Ignition or OPYO 22 PLC systems.

Please note- This system is installed for our most critical application & due to frequent failures, we have faced Data loss & impacting our 24x7 operation.

I request your immediate attention to this matter.

2

Hello and welcome,
This is a forum with friendly and helpful users, but we're not support.

If you need to finish your post with

Then you're in the wrong place.
You should contact support. We're not them.

6 Likes
3

BTW, this isn't a proper Ignition version number. I would expect it to be v8.1.17 or perhaps v8.0.17. If the latter, then it is years past end-of-life, and completely unsupported. (Latest Ignition is v8.1.36.)

Also, note that Inductive Automation does not sell Opto 22 hardware. Opto 22 doesn't sell fully-integrated systems. So some other entity sold you this and deployed it. What do they say about your issues?

4

The latest release on Groov PR is 8.1.21.

Opto need to do their own regression testing against the build, therefore there is a lag between the versions.

You can obtain shell access, and that way install 8.1.36, but you're totally on your own if it hits the fan.

5

That's Edge. This OP is using Full Ignition in order to have DB connections. Totally custom, by someone.

6

The PR2 processor supports "full" ignition as it has better hardware. The image downloaded to the EPIC processor contains the Ignition build, in one compiled file.

1 Like
8

They have a support ticket open, let's not pile on any more.

2 Likes