You Can Make IIoT and Industry 4.0 Implementation Much Simpler

 If you’re concerned with developing IIoT and Industry 4.0 solutions, be prepared for some very good news. Below is the first paragraph of a new data sheet available on Emerson’s PACEdge software platform. You can get your copy of the data sheet here. As you’ll see, PACEdge software overcomes the big challenges usually faced in implementing IIoT in industrial plants.

“PACEdge is an IIoT application enablement platform for the development of scalable data intensive Industry 4.0 solutions. It provides integration between OT and IT domains without disrupting OT assets, architectures or systems while satisfying IT cybersecurity, communications and application requirements. It has been designed specifically to be user-friendly to both IT and OT experts. PACEdge is capable of supporting integrations and architectures ranging from IIoT gateways and remote monitoring to edge AI/ML analytics and data visualization. The PACEdge software environment provides all the tools necessary to collect, store, process, share, visualize, secure and integrate data allowing users to focus on applications and solutions instead of tools and platforms. All components necessary in an IIoT application are brought together in a scalable package to decrease your development time and increase your deployable footprint.”

Check out the data sheet today. You’ll be glad you learned about PACEdge software.

6 Replies

  • Hi Eldin, thanks, yes good news indeed.  I could not find reference to scan times though.  The minimum time to read inputs, execute the logic and write outputs.  Obviously that is dependent on user memory and I/O, is there some information on that?
    Best regards,
    Dave Evans
  • In reply to David Tudor Evans:

    PACEdge is focussed at IT level data, typically this updates at cycles of 1 second or slower or is exception based. PACEdge can cope with approximately 2,000 variables or I/O tags per second but this is also dependent upon the architecture and computrer and network peformance. A PLC is still recommended for high speed process and machine control down to 1ms cycle times. Note that SQL Server database is only benchmarked at 2,000 transactions per second and that's on high-end servers. Time-series databases like influxDB are significantly faster.
  • In reply to Steve Ward:

    Dave, if you need fast scan times AND a great IOT platform take a look at our edge controllers, CPE400 and CPL410.
  • Thanks Mats, looking around the datasheets I don’t see the scan times.  Could you advise?  Have a potential packaging application that currently uses Siemens PLCs, but I need to know the best scan times available.  I understand it will be program complexity and number of I/O dependent, but where can I see this info?
    Dave Evans |   | Lead Instrumentation and Control Engineer | Lvl 1, 197 St Georges Tce, Perth, Western Australia |
  • In reply to David Tudor Evans:

    There are details of the execution times of each instruction in the CPU Reference Manual, GFK-2222. Boolean execution is 46ns per Boolean instruction for the high-end CPUs (CPE330/CPE400/CPL410) and 68ns for the mainstream CPUs (CPE302/305). What you also need to consider is what the required scan time is and if any special programming techniques are required. PACSystems RX3i easily achieves overall scan times of 5-10ms and by using timed interrupts for critical functions we can go down to 1ms scan times. You will also need to consider the scan time of any network, for example PROFINET which goes down to 1ms scan times, and the response times of any I/O modules. For the fastest response, a rack-based PACSystems RX3i can achieve 2ms response times and remote I/O on PROFINET adds at least 1ms. Chassis based CPUs also support input interrupts for some I/O modules for immediate repsonse.