So, is the connector reading the low half of the signal into one PI point/AF attribute and the high half into a separate PI point/AF attribute? If that is the case, Asset-based Analytics has a Concat() function you could use to then combine those into a single value. What format do you need the final value in?
Multiply the upper half by 2^16=65536 and add to the lower half?
That assumes both halves are read into unsigned integers.
Your numbers are a bit odd though. 1010110101111010 is decimal 44410, not -21126, adding to a total of 241018 (196608+44410)
It approach very much, but I don't know why, it doesn't match exactly.
Given a timestamp:
Binary concatenation: 00000000011100111001011100110111 (this is 7575351 decimal)
('TagHigh'*2^16)+('TagLow') = 7,5307E+06
Separately, both parts in AF return:
('TagHigh'*2^16) = 7.5366E+06
('TagLow') = -5910
So I don't know why, PI is considering the second term as negative.
For the underlying PI PointType of Int16, that should be unsigned: https://livelibrary.osisoft.com/LiveLibrary/content/en/server-v8/GUID-98A705E8-85D6-4850-8B60-6A9C9B68211C
So why that is represented as signed is a bit unclear. What you could try however is to read the Int16 PI Points into an Int32 AF attribute. Did not test if that resolves your issue.
About the 'unclear' part: Int16 in AF is signed, giving an explanation why this becomes a negative number: https://livelibrary.osisoft.com/LiveLibrary/content/en/server-v8/GUID-1787AE16-9080-42DA-BEC1-D23D6A5DC0A0
Thank you for your answer. I have tried, but it doesn't work.
I've tried too to change the original TAG attribute from INT32 to INT16, but because it comes from the PI IEC104 it doesn't allow me to change to INT16. (Error modifying point on Server...)
I think I am pretty near the solution, but I can't achieve it
Then you need to do the math: if the number is negative, subtract it from 65536 (2^16). That way the signed int is converted back into an unsigned int.
Did not check though, my math is a bit rusty and pressed for time.