1 / 12

QNX based DCS Unique Value Proposition

QNX based DCS Unique Value Proposition. Igor V. Lapko ( lapko@rts.ua). Which code is more reliable ?. Ask the question ! What is the code length ? How long/thoroughly it was tested ? Is it vulnerable from outside ?. Code A. Code B. Traditional OS Architecture.

remillarda
Download Presentation

QNX based DCS Unique Value Proposition

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. QNX based DCSUnique Value Proposition Igor V. Lapko (lapko@rts.ua)

  2. Which code is more reliable? • Ask the question ! • What is the code length? • How long/thoroughly it was tested? • Is it vulnerable from outside? CodeA Code B

  3. Traditional OS Architecture Protection among kernel components is absent !

  4. QNX OS Architecture Tiny microkernel, refined for 20+ years Hardware protected address spaces! QNX – it is 99.999% of availability (or 5 minutes of downtime annually !)

  5. Real Time All delays are specified and are in hundreds of nanoseconds range

  6. Why QNX? • QNX was intentionally developed for real time and mission critical applications rather than it was adopted for it • Advanced and reliable scheduling. Bullet proof preemptive multitasking. Priority inheriting . All abovementioned enables the coexistence of control functions with HMI and DBMS functions at the same CPU core. • True microkernel. PerfectMMU. • Ability to restart every software component without system rebooting enables software watchdog functions. • Fault protected file system. Multiple redundant network connections. • POSIX-compatible. Very predictable, reliable and robust. No viruses.

  7. S3™ Software Architecture QNX based DCS, generalized node architecture Multimedia HMI OPC Server WEB Server SQL Database (MySQL,Empress) IEC-61131 Engine(S3) QNX microkernel Distributed I/O Drivers Local I/O Drivers Gateway

  8. HMI OPC SQL QNX SL WEB I/O I/O I/O Software Architecture PAC features SCADA Workstation • Extended programming capabilities • Extended communication options • Extended database options • Extended HMI Operator Panel PAC

  9. Communications • Availability of PAC’s data in any networks • Fieldbus adapters (PROFIBUS DP/FMS/FDL, CAN, LON, ASI, INTERBUS) from many vendors (Allen Bradley, Comsy, Echelon, Engenuity Systems, Inova Computers, PEP, Phoenix Contact, Siemens, Softing, SST, TMG i-tec, VISTA Electronics , etc) • Full TCP/IP support and concomitant protocols (FTP, HTTP, ODBC, SNMP и т. п.) • Communication with MS Windows SCADAs viaOPC

  10. DBMS • It is possible to store data directly in PAC now • ERP/MES integration via ODBC/JDBC and replication; • Popular DBMS support (MySQL, PostgreSQL Empress)

  11. HMI and WEB HMI • PAC itself can provide full featured HMI now. • It can realize complex graphical objects including animation and Flash objects • Even Apache server runs at PAC providing full featured WEB HMI

  12. S3 Software Architecture DCS architecture Redundant fault tolerant network S3™ S3™ S3™ Watch dog HMI OPC SQL QNX QNX QNX SL WEB I/O I/O I/O

More Related