Test of 3rd party software at grundfos
This presentation is the property of its rightful owner.
Sponsored Links
1 / 14

Test of 3rd Party Software at Grundfos PowerPoint PPT Presentation


  • 100 Views
  • Uploaded on
  • Presentation posted in: General

Test of 3rd Party Software at Grundfos. Jens Lyngsoe Software Developer [email protected] Agenda. Introduction Test of 3rd party software (4 examples of what we have been doing) MODBUS protocol stack Premptive OS – Segger EMBOS PLC with development environment

Download Presentation

Test of 3rd Party Software at Grundfos

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Test of 3rd party software at grundfos

Test of 3rd Party Software at Grundfos

Jens Lyngsoe

Software Developer

[email protected]


Agenda

Agenda

Introduction

Test of 3rd party software (4 examples of what we have been doing)

MODBUS protocol stack

Premptive OS – Segger EMBOS

PLC with development environment

Integrated operating system and development environment


Introduction to grundfos

Introduction to Grundfos

Pumps and pump systems

16k employes world wide

5k5 employes in DK

600 in R&D in DK

Company vision: 75k people in 2025


Grundfos products

Grundfos Products

All market segments: HVAC, Water Supply, Waste Water, Industry, Dosing


Global r d

Global R&D

Electronic developers world wide


Software development overview

Software Development Overview

Distribution of people in sw projects:


Key objectives of grundfos software development

Key Objectives of Grundfos Software Development

  • Small projects (1-7 persons)

  • Focus on quality rather than time

  • No dedicated testers

  • Software testing is integrated in the software development proces

  • Embedded software

  • Homegrown OS (scheduler)

  • Homegrown datacommunication protocol


Test of 3rd party software 4 examples of what we have been doing

Test of 3rd party software(4 examples of what we have been doing)

  • Premptive OS – Segger EMBOS

  • PLC with development environment

  • Integrated operating system and development environment

  • MODBUS protocol stack


Premptive os segger embos

Premptive OS – Segger EMBOS

What we wanted:

  • Graphics library

  • Preemptive multitasking

  • TCP/IP stack


Premptive os segger embos1

Premptive OS – Segger EMBOS

What happened:

  • Supplier qualification

  • New MCU platform – 2 bugs found

  • Qualification test – listbox

  • Pc platform

  • Support

  • TCP/IP stack


Plc with development environment

PLC with development environment

What we wanted:

  • Platform for pump controllers

  • Flexible and scalable system

    What happened:

  • Major partner – full confidence

  • Extensive changes to software

  • Testing: Review of spec.’s, test spec.’s


Integrated operating system and development environment

Integrated operating system and development environment

  • For LONworks

  • Echelon operating system

  • Fast time to market for user application

  • Hardware integration

  • Development environment integration

    What happened:

  • No faults found

  • Smooth integration creates confidence

  • Test: None specific to OS


Modbus protocol stack

MODBUS protocol stack

Background:

  • Addition to proprietary protocol stack

  • Homegrown version

  • Payd for version

    What happened:

  • Test: protocol end-to-end as part of acceptance testing

  • No bugs found


Conclusion

Conclusion

  • Confidence in supplier is the basis

  • We don’t want extra work – that’s a major reason for choosing 3rd party suppliers in the first place

  • Review / overview of documentation

  • Small and fast initial test

  • Problems fastly creates a sense, that everything needs to be tested


  • Login