Fragmented message.

[boss569]

Hi,
Can anyone help me, Im getting fragmented messages and with some of the filters i have it then sends 2 or three emails

There is no specific order for messgaes coming through as fragmented.

Id like the whole message to display as one whole message, not separated when coming through as fragmented.

Running serial input on a Flex 1600 system decoding 100%
thanks

[VidarParry]

Hi Boss569

Don't have any experience with Flex but....

Can you provide some examples of the filter entries and the messages/emails that are problematic?

What version of PDW? Discriminator tap? connection to PC (soundcard, serial etc)?

Cheers
...Steve
 

[boss569]

Hi,
Running Ver 3.1
Slicer via serial, discriminator tap from scanner.
First part came through ok

1909187 11:35:31 17-12-15 FLEX-A  ALPHA  1600  MFS:  HAS BEEN PLACED OUT OF SERVICE FOR 60 MINUTES DUE TO INABILITY TO CREW FOR INC 051 . A DEFAULT UNIT HAS BEEN DISPATCHED.

Second one to a different address is fragmented

1909192 11:35:31 17-12-15 FLEX-A  ALPHA  1600  MFS:  HAS BEEN PLACED OUT OF SERVICE FOR 60 MINUTES DUE TO INABILITY TO CREW FOR INC 051 . A DEFAULT

[Fragment #2]
1909192 11:35:32 17-12-15 FLEX-A  ALPHA  1601  UNIT HAS BEEN DISPATCHED.


11:39:39 17-12-15   ALPHA   MFS: PLEASE CONFIRM MOBILISATION OF GWLR34 TO INC 051 IMMEDIATELY BY PHONE OR REGIONAL DISPATCH
                   1909172

11:39:41 17-12-15   ALPHA   CHANNEL
  [Fragment #2]    1909172


Cheers

[VidarParry]

Hi Boss569
Looks strange to me - never seen that on a POCSAG system (can't imagine how it could happen on POCSAG), so I can only assume its to do with Flex (which I know very little about).

Sorry - no help from me. Any thoughts Rene?

Cheers
...Steve

[boss569]

Thanks.
Cheers

[Discriminator]

Can anyone help me, Im getting fragmented messages and with some of the filters i have it then sends 2 or three emails

There is no specific order for messgaes coming through as fragmented.

Id like the whole message to display as one whole message, not separated when coming through as fragmented.

In PDW, this is not possible unfortunately. The way PDW handles fragmented messages is described here, under 'History'-

Fragmented FLEX messages

Since FLEX messages are being sent in 'frames' (numbered data blocks), there is a maximum number of characters that can be sent in one single frame. If the network needs to send lots of messages at once, it can happen that one message can not be completed in one single frame, causing the messages to be split in two (or more) parts which will be sent in a next frame. If this happens, the message is 'fragmented'.

When receiving such a message on a pager, you normally wouldn't notice this, because in most cases the second part will be received before you are able to read the message. When monitoring with PDW, it would seem that one capcode is receiving more than one message, because the fragmentation-bit is not being displayed.

In this version, some additional information will be displayed when receiving the second (or third/fourth) part of a message, so it is clearer that you are receiving a fragmented message: