|
FAST Protocol
< Previous Next >
Re: PMAP decoding issues
Darshan Khedekar
23 Mar 2009 12:17PM ET Assuming that OpenFAST is a reasonable application that allows a receiver application to decode data stream against a set of templates in my opinion the problem is most likely with incorrect templates.
For your information EnBS utilizes maximum 12 PMAP bits in its current version.
Regards,
Darshan
> There are a number of ways in which the pmap can have an excess number
> of bits. That is, more bits than are utilized by the field operators
> of the template. In an otherwise functional environment a possible
> reason can be that the template used for decoding is different from
> the one used for encoding. Other possibilities include a broken
> encoder or decoder.
>
> /David
>
> > Hi. I don't know if this forum is the appropriate place to post this.
> > I'm kinda lost with some openfast issues. I inserted into the template
> > the FASTRESET message. That allowed me to decode messages other than
> > the first VERSION msg. EBS is sending a FASTRESET in between messages.
> > Whenever I get a freset I'm reseting the openfast context object. My
> > main problem now is with an openfast exception. I'm receiving a Single
> > Leg Reference message, some of them are ok and others throw:
> >
> > org.openfast.error.FastException: An error occurred while decoding
> > SingleLegReferenceInformation Caused by:
> > org.openfast.error.FastException: The presence map BitVector [00111110
> > 00001000 11110101] has too many bits for the group
> > SingleLegReferenceInformation
> >
> > How is possible for the Pmap to contain more bits that the decoder is
> > expecting? Can you help me? Openfast people doesn't seem to read the
> > mailing list that much.
> >
> >
> > Thank you. Augusto.
Re: PMAP decoding issues
Darshan Khedekar 23 Mar 2009 12:17PM ET
|
