Uwe Kullmann

My feedback

  1. 65 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Uwe Kullmann commented  · 

    Maybe a nice idea: Using WEBAPI to deliver such Infos, which was set up in AF. Osi can use their own Software to do that :-)
    We have now a PiVision Display showing all PI-Versions in our environmant. Just the link to the new Versions from Osisoft is missing.

    Uwe Kullmann supported this idea  · 
  2. 53 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  PI Connectors » OPC UA  ·  Flag idea as inappropriate…  ·  Admin →

    We understand that for slow changing points, values might not change often and thus there is a need to collect values at certain time intervals as opposed to on change. However, scanning at frequent intervals leads to increased load on the server and thus can lead to performance degradation. We are discussing how best to solve this problem with PI Connector for OPC UA.

    An error occurred while saving the comment
    Uwe Kullmann commented  · 

    We have same issue with that.
    Most times it makes sense to ASK OPC Server to get actual values for some specific tags just to check, if connnection is alive or broken.
    It is not unusual that something is going wrong on the connection and we can't see if values are reliable or not.

    Uwe Kullmann supported this idea  · 
  3. 204 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    25 comments  ·  PI Connectors » General  ·  Flag idea as inappropriate…  ·  Admin →

    We plan to provide users the ability to pick their tag naming convention and not worry about managing a cache file. We are working on implementing this functionality with PI Connector for OPC UA.

    An error occurred while saving the comment
    Uwe Kullmann commented  · 

    Why not using the Instrumenttag field or exdesc for the Interface? Then we can Name the Tag to whatever we want.

    Uwe Kullmann supported this idea  · 
  4. 52 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Vision » Authoring Displays  ·  Flag idea as inappropriate…  ·  Admin →
    Uwe Kullmann supported this idea  · 
  5. 5 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PI Connectors » OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Uwe Kullmann commented  · 

    And by the way:
    Connectors doesn't care about Pointsources, Instrument tags, Location 1-5 etc any more.
    To be honest i don't understand in which direction osisoft want to develope the connectors.
    the "old" solution gave us the possibilities to change the datasource by changing Location 1 or pointsource. Even more, we were able to name the PI tag different from sourcetag.

    I can't see how i can do that with the OPC UA connector...

    An error occurred while saving the comment
    Uwe Kullmann commented  · 

    Actual issue is: The OPC UA IF is NOT browsing the Information Model. It is browsing the address space to reinvent the classes of the objects to create the AF structure. Siemens SPPS T3000 has a huge structure on OPC UA Server and they use different names for attributes and variables, so the type identifier differs from the name of the Information models class.
    This result in a strange behaviour:
    For example:
    Information model describe a Motor modul.
    In Address space we have 100 Motor modules, each object has a different name.
    In AF, ONE template is created with 100 attributes. In Elements, each Motor has 100 attributes where only one Attribute is active and the rest is excluded.
    Furthermore, without Special handling, the OPC UA IF is producing a 15MB csv file which could not be handled by the Interface itself and it is nearly impossible to maintain that csv file!

    My Suggestion is:
    A Switch in the config file to browse the Information Modell to create the type Definition file.
    The user can then select the classes he want to get.
    If Interface is starting subscribing it filter out only these objects that was derived from the type definitions in the Information model. Each object carries Information about the type Definition behind and each variable carry original name from Information model in "Browse-name"

    One tricky Point is then still open:
    Should the Interface create AF templates based in the Information model? I believe yes as it perfectly relates to the object orientated model of OPC UA, but
    If real objects are created as elements, they have the Attribute names as described from the template. In real world, the attributes were renamed!

    In summary:
    Yes, i want to get this fixed asap, as Siemens distributes the new T3000 V8.1 and up, which ONLY supports OPC UA.

Feedback and Knowledge Base

Posted ideas will have one of the following statuses.
Full definition of these statuses can be found on the Home Page.
No status
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA/PREVIEW
COMPLETED