Unsupported type for the tag

[Former Member]

Hello,

we are using the URL http://<host>:<port>/XMII/Illuminator?<params>; to query a PIMS.

Using the browser to check the query, for some tags, it works fine, but to others we get an error like:

<?xml version="1.0" encoding="UTF-8" ?> 
<Rowsets DateCreated="2010-03-09T19:17:08" 
                  EndDate="2010-01-14T13:00:00" 
                  StartDate="2010-01-14T00:00:00" Version="12.0.8 Build(24)">
  <Messages>
    <Message>Problem with tag: "XXX", due to: Unsupported type for the "XXX" tag.</Message> 
  </Messages>
</Rowsets>

We have checked the PIMS server and the data is ok. We have no clue what this message error means.

Does someone could give us a hint?

Thanks

Italo Stefani

Vetta Technologies

[Former Member · Accepted solution]

Problem solved.

Checking everything we could we found empty descriptions for some tags in the PIMS server.

Pretty strange problem, but afeter fill the tags descriptions in the PIMS server worked out!

Italo Stefani

Vetta Technologies

[Former Member]

We solved this problem inserting some data into tag descriptions inthe PIMS server.

[Former Member]

Continuing the tests, we ran the Tag Query with param Mode=Statistics and got the following results:

  <?xml version="1.0" encoding="UTF-8" ?> 
  <Rowsets DateCreated="2010-03-10T11:35:42" EndDate="2010-01-14T13:00:00" StartDate="2010-01-14T00:00:00" Version="12.0.8 Build(24)">
    <Rowset>
      <Columns>
        <Column Description="DateTime" MaxRange="0" MinRange="0" Name="DateTime" SQLDataType="93" SourceColumn="DateTime" /> 
      </Columns>
      <Row>
        <DateTime>2010-01-14T00:00:00</DateTime> 
      </Row>
    </Rowset>
    <Messages>
      <Message>Problem with tag: "XXX", due to: Unsupported Type.</Message> 
      <Message>The "Avg" method is not available for the "XX" tag.</Message> 
    </Messages>
  </Rowsets>

Althought it gives us more information, we still can't find the problem.

Thanks

Italo Stefani

Vetta Technologies

[Former Member]

Hi

Check out the valid Data Types for MII XML format here http://help.sap.com/saphelp_xmii115/helpdata/en/Business_Logic_Services/illuminator_xml_format.htm

This is from 11.5 help and I am sure holds true for 12.0 as well.

Compare these data types with your TAG data type definition (lets say in your OPC server) , that might give you some hint as to what the issue could be.

Thanks

Udayan

[agentry_src]

Italo,

Try running it with TWA (Time Weighted Average) instead of AVG (Arithmetic Average).

Regards,

Mike

[Former Member]

Hi Michael,

actually we are not using any method. We are trying to get the absolute tag value. The AVG error appear when I tried to use the mode Statistics. We need to query in Mode=HistoryEvent with no method (AVG, TWA and so on). Anyway, with TWA we get the same Unsupported type issue.

We are checking the Udayan suggestion.

Thank you very much.

Italo Stefani

Vetta Technologies

[Former Member]

Hi Udayan.

Thanks for your suggestion. We have checkd the types in the OPC server and the given URL.

We tried two tags, the working one and the failed one. They are configured with the same value type VT_R4, which means Single Float. The working tag returns the SQLDataType=8 (Double). Based on that, we beleieve there is no problem with the value types.

Another curious point: using another OPC Client we can read the both tags with no problems.

Does anyone have another suggestion?

Thanks.

Italo Stefani

Vetta Technologies

[Former Member]

One more note:

We can not find any register in the log files about the error.

Is there a way to check mor einformation about OPC connections?

Thanks

Italo Stefani

Vetta Technologies

[Former Member]

Interesting!

Not sure why it would do that even though the types are similar.

Just out of curiosity , which OPC server is this?

Lets see , I am not sure if this'll make sense , but have you tried the UDS Alias functionality yet? That would allow you to define the type of the TAG (choices are Double, Integer, Timestamp, and VarChar).

Incase you are not aware of the Aliases go thru the UDS 4.0 help.

Just throwing out some ideas here.

[Former Member]

Hi Udayan. Throwing out some ideas is are we need now! We don't hane anymore!!

We are using an Yokogawa PIMS implementation.

Well, we have tried the Alias approach as well and didn't work. Also, we tried change the type values even in the TAG with no success. Here is a list of some tries:

• Alias

• Change the tag type

• Check the trpes

• Checking the UDS log of a working and not working tag there is no main differences. Basicaly we see the same mesages.

• The MII log does not show any useful information about the error (quite bizarre)

• We tried all Method values (none - our goal, AVG, TWA, Statistics ...)

• We tried all Mode values (History, HistoryEvent ...)

• We applied working templates in a non working tag

• Changed the UDS installation

• Set differents UDS connection in the MII configuration

None gave us a different result. The only thing we notice is that all non working tag is calculated. Basic tags work fine. But we have calculated tags that do not work.

We have a suspicious that there is a bug using JNI inside MII. We are developing another Java UDS Client as a proof of concept.

Any othe ridea for this brainstorm?

Thank you very much.

Italo Stefani

Vetta Technologies