Cyril,
I concur. Bearing in mind the internal structure of the CCSDS time formats, I
would regard an unsigned integer not the appropriate data type, although we
admittedly do not model the internal structure in terms of ASN.1 data types.
Best regards,
Wolfgang
From: "Cyril Thomas" <cyril.thomas at c-s.fr>
To: <css-csts at mailman.ccsds.org>
Cc: Fabien SCELLES <fabien.scelles at c-s.fr>
Date: 03/08/2010 11:55
Subject: [Css-csts] Error in ASN.1 0.22 for time field
Sent by: css-csts-bounces at mailman.ccsds.org
CSTSWG colleagues,
Finalizing implementation of Monitored Data Service, I think we found an
error in the ASN1 : the TypeAndValue type is defined as follows :
TypeAndValue ::= CHOICE
{ integer [0] INTEGER
, intUnsigned [1] IntUnsigned
, duration [2] Duration
, characterString [3] VisibleString
, boolean [4] BOOLEAN
, octetString [5] OCTET STRING
, float [6] REAL
, time [7] IntUnsigned
, enumerated [8] IntUnsigned
, valueExtension [100] Extended
}
the "time" choice is currently defined as an "IntUnsigned". I think this
field should be defined as "Time" defined just above in the ASN.1 :
Time ::= CHOICE
{ ccsdsFormatMilliseconds [0] TimeCCSDSMilli
, ccsdsFormatPicoseconds [1] TimeCCSDSPico
}
TimeCCSDSMilli ::= OCTET STRING (SIZE(8))
TimeCCSDSPico ::= OCTET STRING (SIZE(10))
regards,
Cyril.
_______________________________________________
Css-csts mailing list
Css-csts at mailman.ccsds.org
http://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts