EBO Discovery - AS-P point value called "Value"?

[mike_meirovitz]

Hi,

During the discovery of the EBO values, the discovery finds a point/value inside the AS-P controller called "Value". See below:

11/9650KU0501_1000/Lon/Net/IO/M4/UC\8252GF262B000/Value

I don't see a point called "Value" in the Workstation. See the attached screen capture. 

In addition, the discovery finds the same point/value under "01". See below:

01/9650KU0501_1000/Lon/Net/IO/M4/UC\8252GF262B000

Can someone explain? What does "11" (in 11/9650KU0501_1000/Lon/Net/IO/M4/UC\8252GF262B000/Value) stands for?

Thank you.

Mike

[ardak]

Hi,

Please take a look at this thread:

https://community.se.com/t5/SmartConnector-Forum/SmartConnector-codes-and-types/td-p/274479

This means "01/..." is the point(ValueItem) and "11/..." is a property of that ValueItem. "/Value" is just one of the properties a ValueItem can have.

Hope this helps.

[mike_meirovitz]

Hi Armend,

Thank you for your answer. I saw this thread before. My question is:

If we set the "Folder To Scan" value to "00/9650KU0501_1000/Program/UC" in our SmartConnector extension discovery processor, what value items we should expect?

01/9650KU0501_1000/Program/UC/Value1

01/9650KU0501_1000/Program/UC/Value2

01/9650KU0501_1000/Program/UC/Value3

...

or:

11/9650KU0501_1000/Program/UC/Value1

11/9650KU0501_1000/Program/UC/Value2

11/9650KU0501_1000/Program/UC/Value3

Thank you.

Michael

@JeffBowman 

[mike_meirovitz]

Hi,

One more question:

If the SmartConnector discovers an item as:

"11/9650KU0501_1000/Program/UC/8252GF262B000SNVT",

Can I use a folder name (in Folders To Scan) such as "00/9650KU0501_1000/Program/UC". When I try this I get th3 "INVALID_ID" response in the SmartConnector log file:

2021-06-14 16:08:46.3352,Debug,EwsConsume,<no principal>,GetContainerItems,e92a9a76-bab0-4a81-8451-05390a390095,Response,{"GetContainerItemsItems":[],"GetContainerItemsErrorResults":[{"Id":"11/9650KU0501_1000/Program/UC","Message":"INVALID_ID"}],"GetContainerItemsStatus":null,"version":"1.2"}

Any idea why?

Thanks.

Mike

@JeffBowman 

[ardak]

Hi,

I tried this on my system and it seems to work fine.

Could you attach a screenshot of the system tree, showing the points and container you are trying to reach?

[mike_meirovitz]

Hi Armend,

Thank you for your answer.

We have one controller (9650KU0501_1000) connected in the EBO. See the attached screen capture. The discovery processor finds the controllers' values in two branches:

11/9650KU0501_1000
and
01/9650KU0501_1000

Can you explain why two branches are discovered for one controller? What is the difference between "11" and "01"?

Thanks.

Mike

[ardak]

Hello,

Could you please expand the tree on the left so that the points we are talking about are visible? 

I do not know how your processor works so I can't know for sure but it seems like you are building the tree based on the EWS ID, including the first two digits. These are not part of the "path" but show what kind of node it is. 00 is a container etc.. as discussed in the thread mentioned above.

Hope this clears it up a bit.

[mike_meirovitz]

Hi,

Sure. See attached. So I assume we should always use "00" prefix for all value items in folders.

Regards,

Mike

[ardak · Accepted solution]

I just noticed in your logs:

2021-06-14 16:08:46.3352,Debug,EwsConsume,<no principal>,GetContainerItems,e92a9a76-bab0-4a81-8451-05390a390095,Response,{"GetContainerItemsItems":[],"GetContainerItemsErrorResults":[{"Id":"11/9650KU0501_1000/Program/UC","Message":"INVALID_ID"}],"GetContainerItemsStatus":null,"version":"1.2"}

You seem to have given it the wrong EWS ID. The prefix should be 00/, as "UC" is a container. From what I can see the right ID to use would be 00/9650KU0501_1000/Program/UC 

Sure. See attached. So I assume we should always use "00" prefix for all value items in folders.

---

No, 00 is for ContainerItem(e.g. folder), ValueItem is 01. 

Hope this solves your problem.

BR

Armend