Menu
▾
▴
#250 AL vs "Mismatched Context Tag Value"
In every script for 3.4.10 I have ran, any line using ‘ALDATA’ (or ‘AL’ ) generates a “Mismatched Context Tag Value”. Does anyone know what is causing this and how to fix it?
Here is an example from the TimeSync Script:
SEND (
Network = "bip"
DA = IUT_IP
bvlci =ORIGINAL-UNICAST-NPDU
DER = TRUE
PDU = Confirmed-Request
SegMsg = 0
SegResp = 0
MaxResp = 1476
InVokeID = 3
Service = ReadProperty
Object = 0, OBJECT1
Property = 1, Local-Date
)
EXPECT (
Network = "bip"
DA = TD_IP
bvlci =ORIGINAL-UNICAST-NPDU
SA = IUT_IP
DER = FALSE
PDU = ComplexAck
Service = ReadProperty
Object = 0, OBJECT1
Property = 1, Local-Date
OpenTag 3
ALDATA != X'0000000000'
CloseTag 3
)
Logged In: YES
user_id=1637751
Originator: NO
My approach was to include the tag information within the AL data. This would place the ALDATA argument after the Property argument and nothing would follow afterwards. The tag statement afterwards may be the reason of failure.
Logged In: YES
user_id=1630579
Originator: YES
I will have to try that ... again. I tried it once,but I probably encoded it wrong.