Bug: FLEX: group message and regular message in same frame

EliasOenal / multimon-ng

GNU General Public License v2.0

919 stars 206 forks source link

Bug: FLEX: group message and regular message in same frame #127

Open bierviltje opened 5 years ago

bierviltje commented 5 years ago

While the flex decoder is looping the message received in a frame with a group message with the capcodes index made in the previous frame that contained the short instructions, there could also be another non-group alphanumeric message in the same group frame. These messages aren't shown in multimon-ng.

I also politely request to make it in a future update possible to show all capcodes on a single output line instead of outputting a copy of the message with a new line for each capcode in a group message.

Side note: I noticed inconsistencies in the way of indentation in the code. Either tabs and spaces are used.

bierviltje commented 5 years ago

Extra information:

This bug occurs when the single message is transmitted AFTER the group message in the same frame.

bertinholland commented 5 years ago

I would like to analyse this situation.. At what date and time has this happend so i can have a look at the p2000 data set.

bierviltje commented 5 years ago

I have no dates/times but from now on I will write them down.

Currently I only monitor a couple of capcodes and sometimes I compare them with online (PDW based) monitor websites.

What I noticed and I'm unsure if this is the way how the P2000 network transmits messages, or if it is part of the bug:

If the groupcode is 2029568 and there is also a single message in the same frame, the single message comes before the group message (this works). In case the groupcode is 2029569 or higher, and there is also a single message in the same frame, the single message comes AFTER the groupcode and will not be shown in multimon-ng.

bertinholland commented 5 years ago

Okay i understand this scenario. So let me know time and date and capcodes so i can do investigation

bertinholland commented 5 years ago

I have a realtime online p2000 dump for 7 days (debug level 3) so when you let me know the date and time. Also please add the groupmessage (capcodes) and also the missing capcode and text so I can do some analyse. When you send this information I can also make a sample radio file for the developer for further in depth analyse and do some tests. Thanks in advance.

bertinholland commented 5 years ago

I have no dates/times but from now on I will write them down.

Okay no problem, let me know when you write down the timestam and capcode and message so I can do an in depth analyse.

bertinholland commented 5 years ago

@bierviltje

Can you let me know what capture code you are monitoring
What capcode are sometimes missing (after group message in same frame). Is that always the same capcode?
How often does this occur (approximately)
Can you reply in 12 hours when you missed a capcode? Thats because I can only store for max 15 hours raw radio files.
I'm using the most recent multimonNG software (1.1.7 including last update till 1 march). Which version do you use (multimon-ng --h)

After you replied this message I can startup to capture the raw radio files (dutch network flex p2000) for further analyses. The raw radio files are really large files so it helps when you reply in 12 hours after the missed capcode scenario occurs. I can safe only for maximum 1 day of raw radio files to capture.

So keep in touch! Have a nice day and keep me please informed.

bertinholland commented 5 years ago

@Zanoroy Zanoroy goodmorning, I started up my test capturing system for raw radio files (in chunks of 180 MB/30min) for this issue (#127) and waiting for additional information from bierviltje. Analyse is in progress.

Zanoroy commented 5 years ago

@bertinholland Morning mate, Thank you for all the chasing you are doing on this issue. I'm currently developing a Drive Test Kit for Flex networks (Hardware and software) so I have limited time in the short term, but if we can gather enough information to track down the issue I could hopefully offer a fix. If the issue is going to take several days to investigate and fix it will have it wait a couple of weeks I'm sorry to say.

But as always I'm happy to help in anyway I can. I see by your comments you are already on the task of getting some raw data of an occurrence recorded, I should be able to process it in my test lab and track down the issue (hopefully).

@bierviltje over the years the flex decoding module has moved from person to person and has had quite a few contributors. Yes there are plenty of inconsistencies, not only in the spacing/formatting but also in the style of coding used. Its quite normal for projects that are supported on a voluntary basis.

We all work together to get the best outcome for the community but too often we lack the time to go over each others formatting/coding styles to move to a single standard.

I'm happy to add the capcode's to a single line, but I will need to add a command line flag to ensure the tool is backwards compatible.

Cheers

bierviltje commented 5 years ago

@bertinholland

The capcodes I capture in my Python script are 000706001 (monitorcode Utrecht) and 000736090 (persberichten Utrecht). The first one always comes in a group message so I have no problems with this one and the latter always comes as a single message and will not be received with multimon-ng a couple of times a week. I'm using the version prior the 1st of March update (I didn't know there was an update).

@Zanoroy

Do you know if the capcodes in a short instructions for an upcoming group message need to be added to an array (a for loop is neccessary to retrieve them that way) or if all capcodes can be added to a string at once (and easily be retreived without the need of a for loop)?

bierviltje commented 5 years ago

@bertinholland

I was comparing messages addressed to 000736090 on my system (they get delivered to a Discord channel) and on the website 112meldingen.nl (they have an archive with search function) and it seems I missed a message send at 01:03:03 on 30-03-19.

Edit:

Again, I was looking at a couple of online monitor websites, and it seems at the exact time mentioned above, there were 3 messages sent:

1: Group message to 21 capcodes. (Arkel fire department) 2: Group message to 2 capcodes. (Rotterdam ambulance) 3: Single message. (Utrecht press information) the message I didn't receive

The website I'm looking at don't show group codes and frame numbers, but I suspect message 1 was sent to 002029568 and group message 2 to 002029569. (exactly how I expected/presumed when and how this bug behaves)

Zanoroy commented 5 years ago

@bierviltje You could easily change the code to collect the capcodes in a single string if you wanted to. But lets face it Flex even at it fasted board rate is only 6400 bps, so looping through an array, which at its largest is 16 elements, there is NO impact to performance.

I had a very (and I mean VERY) quick look over the other issues raised against Flex decoding for multimon-ng and I'll probably get around to putting them into the mainline (or at least put them into my code and creating a pull request). Although I have a few questions regarding the 'fixes' that have been implemented.

bierviltje commented 5 years ago

@Zanoroy

Group messages can be very large in the Netherlands, this one below is a fallback system test that got sent once every month. (copied from an online monitor)

19:00:12 01-04-19 | GROUP-1 | Goedenavond, dit is uw maandelijks proefalarm via noodalarmering vanuit de Gemeenschappelijke Meldkamer Utrecht.
  | 0706006 | BRW Utrecht (Abcoude) (Noodalarmering)
  | 0707175 | BRW Utrecht (Achterveld) (Noodalarmering)
  | 0709498 | BRW Utrecht (Adviseur Gevaarlijke Stoffen - Oost)
  | 0709534 | BRW Utrecht (Adviseur Gevaarlijke Stoffen - West)
  | 0709567 | BRW Utrecht (Algemeen Commandant Crisiscommunicatie / Communicatieadviseur ROT)
  | 0706054 | BRW Utrecht (Amerongen) (Noodalarmering)
  | 0706138 | BRW Utrecht (Amersfoort Centrum) (Noodalarmering)
  | 0706139 | BRW Utrecht (Amersfoort Noord) (Noodalarmering)
  | 0706137 | BRW Utrecht (Amersfoort) (Korpsalarm)
  | 0706251 | BRW Utrecht (Baarn) (Noodalarmering)
  | 0707364 | BRW Utrecht (Benschop) (Noodalarmering)
  | 0706599 | BRW Utrecht (Bilthoven) (Noodalarmering)
  | 0706334 | BRW Utrecht (Breukelen) (Noodalarmering)
  | 0706446 | BRW Utrecht (Bunnik - Werkhoven) (Noodalarmering)
  | 0706445 | BRW Utrecht (Bunnik) (Noodalarmering)
  | 0706515 | BRW Utrecht (Bunschoten) (Noodalarmering)
  | 0709531 | BRW Utrecht (CaCo)
  | 0709506 | BRW Utrecht (Centralist)
  | 0709507 | BRW Utrecht (Centralist)
  | 0709508 | BRW Utrecht (Centralist)
  | 0709510 | BRW Utrecht (Centralist)
  | 0709511 | BRW Utrecht (Centralist)
  | 0709513 | BRW Utrecht (Centralist)
  | 0709514 | BRW Utrecht (Centralist)
  | 0709516 | BRW Utrecht (Centralist)
  | 0709517 | BRW Utrecht (Centralist)
  | 0709518 | BRW Utrecht (Centralist)
  | 0709519 | BRW Utrecht (Centralist)
  | 0709610 | BRW Utrecht (Centralist) (Persoonlijk)
  | 0709611 | BRW Utrecht (Centralist) (Persoonlijk)
  | 0709612 | BRW Utrecht (Centralist) (Persoonlijk)
  | 0709613 | BRW Utrecht (Centralist) (Persoonlijk)
  | 0709614 | BRW Utrecht (Centralist) (Persoonlijk)
  | 0709616 | BRW Utrecht (Centralist) (Persoonlijk)
  | 0709617 | BRW Utrecht (Centralist) (Persoonlijk)
  | 0709520 | BRW Utrecht (Centralisten)
  | 0709522 | BRW Utrecht (Centralisten)
  | 0709529 | BRW Utrecht (Coördinator RAC)
  | 0709533 | BRW Utrecht (Commandant van Dienst)
  | 0709553 | BRW Utrecht (Communicatie ROT)
  | 0709609 | BRW Utrecht (Communicatieadviseur CoPI)
  | 0709008 | BRW Utrecht (Cothen-Langbroek) (Noodalarmering)
  | 0706598 | BRW Utrecht (De Bilt) (Noodalarmering)
  | 0708525 | BRW Utrecht (De Meern) (Noodalarmering)
  | 0709362 | BRW Utrecht (Den Dolder) (Noodalarmering)
  | 0706776 | BRW Utrecht (Doorn) (Noodalarmering)
  | 0706435 | BRW Utrecht (DOvD Binnensticht - Zeist - Bunnik)
  | 0706836 | BRW Utrecht (Driebergen-Rijsenburg) (Noodalarmering)
  | 0706897 | BRW Utrecht (Eemnes) (Noodalarmering)
  | 0708054 | BRW Utrecht (Elst) (Noodalarmering)
  | 0706601 | BRW Utrecht (Groenekan) (Noodalarmering)
  | 0709503 | BRW Utrecht (Groepsalarm Centralisten)
  | 0709551 | BRW Utrecht (Groepscode HOvD's Oost)
  | 0709557 | BRW Utrecht (Groepscode HOvD's West)
  | 0708908 | BRW Utrecht (Hagestein) (Noodalarmering)
  | 0709113 | BRW Utrecht (Harmelen) (Noodalarmering)
  | 0706958 | BRW Utrecht (Houten) (Noodalarmering)
  | 0709501 | BRW Utrecht (HOvD Oost / Leider CoPI)
  | 0709500 | BRW Utrecht (HOvD West / Leider CoPI)
  | 0707049 | BRW Utrecht (IJsselstein) (Noodalarmering)
  | 0709540 | BRW Utrecht (Informatiemanager CoPI Oost)
  | 0709541 | BRW Utrecht (Informatiemanager CoPI West)
  | 0706775 | BRW Utrecht (IOvD Heuvelrug West)
  | 0709115 | BRW Utrecht (Kamerik) (Noodalarmering)
  | 0706336 | BRW Utrecht (Kockengen) (Noodalarmering)
  | 0707116 | BRW Utrecht (Leersum) (Noodalarmering)
  | 0707174 | BRW Utrecht (Leusden) (Noodalarmering)
  | 0708932 | BRW Utrecht (Lexmond) (Noodalarmering)
  | 0709600 | BRW Utrecht (Lid Sectie IM / Plotter ROT)
  | 0709594 | BRW Utrecht (Lid Sectie Resourcemanagement / ICT)
  | 0707733 | BRW Utrecht (Linschoten) (Noodalarmering)
  | 0707267 | BRW Utrecht (Loenen a/d Vecht) (Noodalarmering)
  | 0707363 | BRW Utrecht (Lopik) (Noodalarmering)
  | 0707514 | BRW Utrecht (Maarn-Maarsbergen) (Noodalarmering)
  | 0707584 | BRW Utrecht (Maarssen) (Noodalarmering)
  | 0707585 | BRW Utrecht (Maarsseveen/Tienhoven) (Noodalarmering)
  | 0706600 | BRW Utrecht (Maartensdijk) (Noodalarmering)
  | 0709499 | BRW Utrecht (Meetplanleider Oost)
  | 0709535 | BRW Utrecht (Meetplanleider West)
  | 0708148 | BRW Utrecht (Mijdrecht) (Noodalarmering)
  | 0707732 | BRW Utrecht (Montfoort) (Noodalarmering)
  | 0707840 | BRW Utrecht (Nieuwegein Noord) (Noodalarmering)
  | 0707839 | BRW Utrecht (Nieuwegein Zuid) (Noodalarmering)
  | 0706335 | BRW Utrecht (Nieuwer ter Aa) (Noodalarmering)
  | 0707268 | BRW Utrecht (Nigtevecht) (Noodalarmering)
  | 0709555 | BRW Utrecht (Notulist RBT)
  | 0709556 | BRW Utrecht (Ondersteunend Secretaris RBT)
  | 0709539 | BRW Utrecht (Operationeel leider)
  | 0707932 | BRW Utrecht (Oudewater) (Noodalarmering)
  | 0706582 | BRW Utrecht (OvD Binnensticht)
  | 0709730 | BRW Utrecht (OvD Defensie)
  | 0706514 | BRW Utrecht (OvD Eemland Noord)
  | 0706118 | BRW Utrecht (OvD Eemland-Zuid)
  | 0708793 | BRW Utrecht (OvD Heuvelrug Oost)
  | 0707048 | BRW Utrecht (OvD Lekstroom Noord)
  | 0706947 | BRW Utrecht (OvD Lekstroom)
  | 0706005 | BRW Utrecht (OvD Rijn & Venen Noord)
  | 0707731 | BRW Utrecht (OvD Rijn & Venen Zuid)
  | 0708441 | BRW Utrecht (OvD Utrecht)
  | 0708489 | BRW Utrecht (Pelotonscommandant Logistiek)
  | 0709527 | BRW Utrecht (Piketcentralist)
  | 0709532 | BRW Utrecht (RCvD) (Groepscode)
  | 0707995 | BRW Utrecht (Renswoude) (Noodalarmering)
  | 0708487 | BRW Utrecht (Reserve OvD Utrecht)
  | 0709530 | BRW Utrecht (Resourcemanager ROT)
  | 0708052 | BRW Utrecht (Rhenen) (Noodalarmering)
  | 0706957 | BRW Utrecht (Schalkwijk) (Noodalarmering)
  | 0708300 | BRW Utrecht (Soest) (Noodalarmering)
  | 0708301 | BRW Utrecht (Soesterberg) (Noodalarmering)
  | 0709597 | BRW Utrecht (Teamleden Hoogtereddingsteam)
  | 0709598 | BRW Utrecht (Teamleider Hoogtereddingsteam)
  | 0708521 | BRW Utrecht (Utrecht Leidsche Rijn) (Noodalarmering)
  | 0708520 | BRW Utrecht (Utrecht Noord) (Noodalarmering)
  | 0708522 | BRW Utrecht (Utrecht Oost) (Noodalarmering)
  | 0708523 | BRW Utrecht (Utrecht Tolsteeg) (Noodalarmering)
  | 0708524 | BRW Utrecht (Utrecht Zuilen) (Noodalarmering)
  | 0708815 | BRW Utrecht (Veenendaal) (Noodalarmering)
  | 0709596 | BRW Utrecht (Verzorgingsgroep)
  | 0708907 | BRW Utrecht (Vianen) (Noodalarmering)
  | 0708149 | BRW Utrecht (Vinkeveen) (Noodalarmering)
  | 0708526 | BRW Utrecht (Vleuten) (Noodalarmering)
  | 0706602 | BRW Utrecht (Westbroek) (Noodalarmering)
  | 0709006 | BRW Utrecht (Wijk bij Duurstede) (Noodalarmering)
  | 0708150 | BRW Utrecht (Wilnis) (Noodalarmering)
  | 0709112 | BRW Utrecht (Woerden) (Noodalarmering)
  | 0709288 | BRW Utrecht (Woudenberg) (Noodalarmering)
  | 0709114 | BRW Utrecht (Zegveld) (Noodalarmering)
  | 0709361 | BRW Utrecht (Zeist) (Noodalarmering)
  | 0709537 | BRW Utrecht (Monitorcode Hoogtereddingsteam)
  | 0708915 | BRW Utrecht (Onbekende code)
  | 0708923 | BRW Utrecht (Onbekende code)
  | 0708927 | BRW Utrecht (Onbekende code)
  | 0708938 | BRW Utrecht (Onbekende code)
  | 0709566 | Veiligheidsregio Utrecht (Algemeen Commandant Bevolkingszorg)
  | 0709550 | Veiligheidsregio Utrecht (Directeur VRU)

bertinholland commented 5 years ago

@bertinholland

I was comparing messages addressed to 000736090 on my system (they get delivered to a Discord channel) and on the website 112meldingen.nl (they have an archive with search function) and it seems I missed a message send at 01:03:03 on 30-03-19.

Edit:

Again, I was looking at a couple of online monitor websites, and it seems at the exact time mentioned above, there were 3 messages sent:

1: Group message to 21 capcodes. (Arkel fire department) 2: Group message to 2 capcodes. (Rotterdam ambulance) 3: Single message. (Utrecht press information) the message I didn't receive

The website I'm looking at don't show group codes and frame numbers, but I suspect message 1 was sent to 002029568 and group message 2 to 002029569. (exactly how I expected/presumed when and how this bug behaves)

Multimon-ng: 2019-03-30 01:03:03 [000736090] ALN Utrecht Burgemeester Reigerstraat Wilhelminapark Aanrijding letsel fietser gevallen

multimon-ng debug mode 3: 2019-03-30 01:03:01: FLEX: FrameInfoWord: cycleno=00 frameno=106 fix3=0x3c time=03:18 There are two group messages decoded (groupbit 0 and groupbit 1) AND 1 single message decode (capcode 736090] 2019-03-30 01:03:02: FLEX: Parse Alpha Numeric 2019-03-30 01:03:02: FLEX: 2019-03-30 00:03:02 1600/2/K/A 00.106 [000736090] ALN Utrecht Burgemeester Reigerstraat Wilhelminapark Aanrijding letsel fietser gevallen 2019-03-30 01:03:02: FLEX: State: SYNC1

There is no lost message. Decoding group messages and 1 single message in the same frame is correct.

bertinholland commented 5 years ago

Today (april 2 2019, analyse capcode 736090.

Multimon-ng:

pi@p2000:~/output$ cattekst "2019-04-02.*000736090" | wc -l
20
pi@p2000:~/output$ cattekst "2019-04-02.*000736090"
2019-04-02 08:15:54 [000736090] ALN Maarsbergen Woudenbergseweg Stremming wegverkeer
2019-04-02 08:17:28 [000736090] ALN Vianen UT Prins Bernhardstraat Afrit A2 Li - Vianen 11 Stremming wegverkeer
2019-04-02 08:56:03 [000736090] ALN Amersfoort Arnhemseweg-Zuid Stremming wegverkeer
2019-04-02 09:20:08 [000736090] ALN Mogelijk explosief, Egelinglaan te Zeist. Politie doet onderzoek.
2019-04-02 09:33:12 [000736090] ALN Oud Zuilen Daalseweg Aanrijding letsel
2019-04-02 10:22:14 [000736090] ALN Nieuwegein A2 Li 70,5 Stremming wegverkeer
2019-04-02 11:27:36 [000736090] ALN Austerlitz Weideweg Aanrijding letsel
2019-04-02 11:41:52 [000736090] ALN Leusden A28 Re 14,1 Stremming wegverkeer
2019-04-02 11:45:08 [000736090] ALN Eemnes A27 Li 100,1 Stremming wegverkeer
2019-04-02 13:08:45 [000736090] ALN Gangenstelsel aangetroffen onder huize JP Coenstraat. Politie doet onderzoek
2019-04-02 14:23:59 [000736090] ALN Zijderveld A2 Re 80,0 Stremming wegverkeer
2019-04-02 15:03:50 [000736090] ALN Utrecht Ds. Martin Luther Kinglaan Stremming wegverkeer
2019-04-02 16:10:27 [000736090] ALN Zeist Panweg Aanrijding letsel
2019-04-02 17:11:09 [000736090] ALN Utrecht A2 Li 59,6 Stremming wegverkeer
2019-04-02 17:12:09 [000736090] ALN Utrecht A2 Re 58,6 Stremming wegverkeer
2019-04-02 17:17:48 [000736090] ALN Utrecht A2 Re 60,0 Stremming wegverkeer
2019-04-02 18:03:41 [000736090] ALN Utrecht Domplein Stremming wegverkeer
2019-04-02 18:06:26 [000736090] ALN Utrecht Stadsbaantunnel L Stremming wegverkeer
2019-04-02 19:51:05 [000736090] ALN IJsselstein De Baan Televisiebaan Aanrijding letsel
2019-04-02 21:32:15 [000736090] ALN Odijk N410 - Burgweg Aanrijding letsel
pi@p2000:~/output$

Analyse http://www.112meldingen.nl/index.php / pdw 19 lines not showing at 112meldingen/pdw 2019-04-02 11:41:52 [000736090] ALN Leusden A28 Re 14,1 Stremming wegverkeer

multimon-ng decodes more lines!

It is not look like a logical multimon-ng problem. Everything is today working fine.

bierviltje commented 5 years ago

Can the speed of my setup be an issue? It's running on a Raspberry Pi 3B+ with Raspian Lite.

I also tried running it simultaneously with 2 identical setups. One with a (badly) modified flex decoder and one without. If my hardware is powerful enough then I assume it's a signal (strength) issue.

I'm glad it's sorted out now and would thank you guys for your time and effort!

@Zanoroy is there any chance we can still look forward to a version with one line group output?

bertinholland commented 5 years ago

@bierviltje

What is your type of hardware / dongle?
Is your rtl_sdr dongle kalibrated?
Is your receiving signal quality good/excellent
What kind of antenna?
What is do distance to the p2000 transmitter?
when u are running multimon in debug mode, per 24 hour how many corruption, lost synchronisations and timeouts did you find?

bertinholland commented 5 years ago

On april 3 I will do an extra crosscheck (mutimon versus pdw) for capcode 000736090.

Raw radio capturing is still activated on my system, so when a lost message / decode problem occure I can reproduce it with a raw radio file.

Please keep me informed about your investagation and send me a reply about your analyse tomorrow. So do I ;-)

Bye bye

bierviltje commented 5 years ago

I have official rtl-sdr.com v3 dongles, not calibrated, hear some fluttering with aplay because 3 closest masts are all about 5 km away from me, tested with Diamond RH771, MH77S and X30N antennas situated indoors on the loft. I did see some errors but very rarely.

bertinholland commented 5 years ago

My configuration is also a raspberry Pi 3B+. The load for multimon-ng is very low 1 or 2% The load for rtl_sdr is a little bit higher 12% but that's not very high. The total system load is max 18 / 19 %. That very good.

Im using a RTL2832U DVB-T Tuner Dongle and it's kalibrated. Accurate tuning and almost zero temperature drift (2 PPM max. initial offset, 0.5-1 PPM temperature drift).

Probably you can kalibrate your system, analyse your multimon debug log file for errors, sync lost or timeouts.

bertinholland commented 5 years ago

I advice you to run multimon-ng in debug mode (-v 3) and when you have a lost message you can reply your entire frame output so we can analyse it (my archive is 7 till 14 days p2000 log level 3).

Also you can correct if necessary your ppm_error. Or you can try to upper or lower your gain.

bertinholland commented 5 years ago

pi@p2000:~/output$ cattekst "2019-04-03.*000736090"  | wc -l
20
pi@p2000:~/output$ cattekst "2019-04-03.*000736090"
2019-04-03 07:28:11 [000736090] ALN Amersfoort Het Masker Stille Steeg Oost Aanrijding letsel
2019-04-03 08:04:32 [000736090] ALN Er is een lichaam gevonden op de Amstelkade in Wilnis. Politie doet onderzoek.De Amstelkade is afgezet.
2019-04-03 08:54:49 [000736090] ALN Utrecht Vleutenseweg Stremming wegverkeer
2019-04-03 09:05:53 [000736090] ALN Leusden Dodeweg Stremming wegverkeer
2019-04-03 12:05:20 [000736090] ALN Abcoude A2 Re 38,0 Stremming wegverkeer
2019-04-03 12:09:16 [000736090] ALN Nieuwegein A2 Li 71,0 Stremming wegverkeer
2019-04-03 12:15:33 [000736090] ALN Maarssen Sweserengseweg Aanrijding letsel
2019-04-03 13:23:04 [000736090] ALN Woerden Minkemalaan Aanrijding letsel
2019-04-03 13:25:37 [000736090] ALN Woerden Minkemalaan Aanrijding letsel
2019-04-03 15:41:39 [000736090] ALN Utrecht Carnegiedreef Rio Negrodreef Aanrijding letsel
**_2019-04-03 15:49:48 [000736090] ALN Utrecht Carnegiedreef Rio Negrodreef Aanrijding letsel_**
2019-04-03 15:59:58 [000736090] ALN Utrecht A2 Re 58,8 m Stremming wegverkeer
2019-04-03 16:02:32 [000736090] ALN Vianen UT Afrit A2 Re - Vianen 11 Stremming wegverkeer
2019-04-03 16:11:57 [000736090] ALN Amersfoort A28 Re 18,3 Stremming wegverkeer
2019-04-03 16:12:44 [000736090] ALN Utrecht Stadsbaantunnel R Stremming wegverkeer
2019-04-03 16:43:07 [000736090] ALN Amersfoort Meridiaan Ringweg-Koppel Aanrijding letsel
2019-04-03 17:47:26 [000736090] ALN Woerden A12 Re 47,0 Stremming wegverkeer
2019-04-03 18:07:06 [000736090] ALN Utrecht Tivoli Vredenburg Vredenburgkade Aanrijding letsel
2019-04-03 19:03:01 [000736090] ALN Breukelen A2 Re 51,7 Stremming wegverkeer
2019-04-03 19:05:32 [000736090] ALN Amersfoort HAP Amersfoort Maatweg Aanrijding letsel
pi@p2000:~/output$ date
wo  3 apr 2019 19:30:17 CEST
pi@p2000:~/output$

Multimon-ng prints 20 lines PDW / 112meldingen.nl prints 19 lines

PDW is missing the line 2019-04-03 15:49:48 [000736090] ALN Utrecht Carnegiedreef Rio Negrodreef Aanrijding letsel

So multimon-ng is functioning very good and captures all messages (1 more than PDW!).

bertinholland commented 5 years ago

I am stopping capturing the raw audio files because it seems there is no multimon-ng bug.

bertinholland commented 5 years ago

@bierviltje Can you publish your debug level 3 output when you missed a capcode. I was wondering what has happened.

I think it is not a bug. My rapberry system (3b+) runs:

the latest raspberry OS (4.14.98-v7+ #1200)
the latest rtl_sdr 0.6.0 with commits till 7 october 2018
the latest multimon-ng 1.1.7 included commits till 1 march)
RTL2832U DVB-T Tuner Dongle and it's kalibrated. Accurate tuning and almost zero temperature drift (2 PPM max. initial offset, 0.5-1 PPM temperature drift).
good strong signal strength I'm deploy a daily build for OS and software.

Please upload / share your debug level 3 output when you missed a capcode.

bierviltje commented 5 years ago

Could you help me how I can write the output to a log file?

bertinholland commented 5 years ago

Just add >> outputfilename.txt

bertinholland commented 5 years ago

I have analysed 31331 capcodes for april 1,2,3 and there is no missing capcode for multimon-ng in my configuration (compared with pdw)

pi@p2000:~/output$ date ; cattekst "2019-04-0.*" |wc -l
wo  3 apr 2019 22:09:04 CEST
31331
pi@p2000:~/output$

I think you can close this bug issue?

bierviltje commented 5 years ago

Thank for your testing and effort again. I think it's a isolated problem with my setup. I will close it now.

bierviltje commented 3 years ago

This bug stil exist..

To be honest, I don't have much time to look into the issue. I have to read, interpret and understand all code over again since all commits that has been made ever since. The code change I made that got implemented is all gone. Like someone has been editing an older version and the version with my code changes got skipped and forgotten. Only the "|" delimiter is still there?

My code change (which didn't solve the bug completely): https://github.com/EliasOenal/multimon-ng/commit/46c4a53eeb07b8e0f8e371897983ddea4b470997#diff-53fd5c7fdf490c0f007dd18d5bb87d844ed78787ad937bd6e7dbbc9d3b0b774f

daanthju commented 3 months ago

@bierviltje I'm experiencing exactly the same problems as you on two different setups. It happens dozens of times a day that when multiple messages are received (of which at least 1 is a group message) in the same frame, a regular message is not received.

I use a raspberry pi 4 with an RTL2832U DVB-T Dongle. Previously an R820T2 with the same problem.

Have you found a solution?

filibuster007 commented 2 months ago

Found this issue as I noticed the same. Captured an occurrence in debug level 3. Where "1180000 15:45:24 09-06-24 FLEX-A ALPHA 1600 TESTOPROEP MOB" is missing in the multimon-ng capture.

You see that the message is received as the cap code is in the multimode-ng log (FLEX: CAPCODE:0000000000120160)

PDW: 1523001 15:45:24 09-06-24 FLEX-A GROUP 1600 A1 Richard Wagnerlaan VOORSC : 16174 1523174 15:45:24 09-06-24 FLEX-A GROUP 1600 A1 Richard Wagnerlaan VOORSC : 16174 2029568 15:45:24 09-06-24 FLEX-A ALPHA 1600 A1 Richard Wagnerlaan VOORSC : 16174 1180000 15:45:24 09-06-24 FLEX-A ALPHA 1600 TESTOPROEP MOB 1520008 15:45:34 09-06-24 FLEX-A GROUP 1600 A2 Lindenhof Cort van der Lindenstraat DELFT : 15108 1520999 15:45:34 09-06-24 FLEX-A GROUP 1600 A2 Lindenhof Cort van der Lindenstraat DELFT : 15108 2029568 15:45:34 09-06-24 FLEX-A ALPHA 1600 A2 Lindenhof Cort van der Lindenstraat DELFT : 15108

multimon-ng FLEX: State: SYNC1 FLEX: SyncInfoWord: sync_code=0x870c baud=1600 levels=2 polarity=POS zero=-0.031537 envelope=0.090149 symrate=1586.061278 FLEX: State: FIW FLEX: FrameInfoWord: cycleno=11 frameno=043 fix3=0x3c time=45:20 FLEX: State: SYNC2 FLEX: State: DATA FLEX: BlockInfoWord: (Phase A) BIW:0000040B AW:01-01 (0 pages) FLEX: State: SYNC1 FLEX: SyncInfoWord: sync_code=0x870c baud=1600 levels=2 polarity=POS zero=-0.030960 envelope=0.090275 symrate=1586.079159 FLEX: State: FIW FLEX: FrameInfoWord: cycleno=11 frameno=044 fix3=0x3c time=45:22 FLEX: State: SYNC2 FLEX: State: DATA FLEX: BlockInfoWord: (Phase A) BIW:00000C03 AW:01-03 (2 pages) FLEX: CAPCODE:0000000000173de6 FLEX: Found Short Instruction, Group bit: 0 capcodes in group so far 1, adding Capcode: [001523174] FLEX: CAPCODE:0000000000173d39 FLEX: Found Short Instruction, Group bit: 0 capcodes in group so far 2, adding Capcode: [001523001] FLEX: State: SYNC1 FLEX: SyncInfoWord: sync_code=0x870c baud=1600 levels=2 polarity=POS zero=-0.030753 envelope=0.090401 symrate=1586.096993 FLEX: State: FIW FLEX: FrameInfoWord: cycleno=11 frameno=045 fix3=0x3c time=45:24 FLEX: State: SYNC2 FLEX: State: DATA FLEX: BlockInfoWord: (Phase A) BIW:00000C03 AW:01-03 (2 pages) FLEX: CAPCODE:00000000001ef800 FLEX: Parse Alpha Numeric FLEX Group message output: Groupbit: 0 Total Capcodes; 2; index 1; Capcode: [001523174] FLEX Group message output: Groupbit: 0 Total Capcodes; 2; index 2; Capcode: [001523001] FLEX|2024-06-09 13:45:07|1600/2/K/A|11.045|002029568 001523174 001523001|ALN|A1 Richard Wagnerlaan VOORSC : 16174 FLEX: CAPCODE:0000000000120160 FLEX: Parse Alpha Numeric FLEX: State: SYNC1 FLEX: SyncInfoWord: sync_code=0x870c baud=1600 levels=2 polarity=POS zero=-0.031169 envelope=0.090404 symrate=1586.101231 FLEX: State: FIW FLEX: FrameInfoWord: cycleno=11 frameno=048 fix3=0x3c time=45:30 FLEX: State: SYNC2 FLEX: State: DATA FLEX: BlockInfoWord: (Phase A) BIW:0000040B AW:01-01 (0 pages) FLEX: State: SYNC1 FLEX: SyncInfoWord: sync_code=0x870c baud=1600 levels=2 polarity=POS zero=-0.030586 envelope=0.090530 symrate=1586.118947 FLEX: State: FIW FLEX: FrameInfoWord: cycleno=11 frameno=049 fix3=0x3c time=45:31 FLEX: State: SYNC2 FLEX: State: DATA FLEX: BlockInfoWord: (Phase A) BIW:00000C03 AW:01-03 (2 pages) FLEX: CAPCODE:0000000000173567 FLEX: Found Short Instruction, Group bit: 0 capcodes in group so far 1, adding Capcode: [001520999] FLEX: CAPCODE:0000000000173188 FLEX: Found Short Instruction, Group bit: 0 capcodes in group so far 2, adding Capcode: [001520008] FLEX: State: SYNC1 FLEX: SyncInfoWord: sync_code=0x870c baud=1600 levels=2 polarity=POS zero=-0.031114 envelope=0.090655 symrate=1586.136665 FLEX: State: FIW FLEX: FrameInfoWord: cycleno=11 frameno=050 fix3=0x3c time=45:33 FLEX: State: SYNC2 FLEX: State: DATA FLEX: BlockInfoWord: (Phase A) BIW:00000807 AW:01-02 (1 pages) FLEX: CAPCODE:00000000001ef800 FLEX: Parse Alpha Numeric FLEX Group message output: Groupbit: 0 Total Capcodes; 2; index 1; Capcode: [001520999] FLEX Group message output: Groupbit: 0 Total Capcodes; 2; index 2; Capcode: [001520008] FLEX|2024-06-09 13:45:16|1600/2/K/A|11.050|002029568 001520999 001520008|ALN|A2 Lindenhof Cort van der Lindenstraat DELFT : 15108

filibuster007 commented 2 months ago

And another one. Missing message has the same capcode 1180000 as the previous occurrence.

In multimon-ng this one is missing: "1180000 16:15:25 ALPHA TESTOPROEP MOB"

PDW: 1002061 16:15:25 GROUP P 1 BLB-03 Ongeval wegvervoer A2 Li - Autosnelweg A2 223,5 Echt 235331 235531 1002067 16:15:25 GROUP P 1 BLB-03 Ongeval wegvervoer A2 Li - Autosnelweg A2 223,5 Echt 235331 235531 1002078 16:15:25 GROUP P 1 BLB-03 Ongeval wegvervoer A2 Li - Autosnelweg A2 223,5 Echt 235331 235531 1002700 16:15:25 GROUP P 1 BLB-03 Ongeval wegvervoer A2 Li - Autosnelweg A2 223,5 Echt 235331 235531 1002701 16:15:25 GROUP P 1 BLB-03 Ongeval wegvervoer A2 Li - Autosnelweg A2 223,5 Echt 235331 235531 1002707 16:15:25 GROUP P 1 BLB-03 Ongeval wegvervoer A2 Li - Autosnelweg A2 223,5 Echt 235331 235531 1002718 16:15:25 GROUP P 1 BLB-03 Ongeval wegvervoer A2 Li - Autosnelweg A2 223,5 Echt 235331 235531 1002730 16:15:25 GROUP P 1 BLB-03 Ongeval wegvervoer A2 Li - Autosnelweg A2 223,5 Echt 235331 235531 1005080 16:15:25 GROUP P 1 BLB-03 Ongeval wegvervoer A2 Li - Autosnelweg A2 223,5 Echt 235331 235531 1005998 16:15:25 GROUP P 1 BLB-03 Ongeval wegvervoer A2 Li - Autosnelweg A2 223,5 Echt 235331 235531 2029568 16:15:25 ALPHA P 1 BLB-03 Ongeval wegvervoer A2 Li - Autosnelweg A2 223,5 Echt 235331 235531 1180000 16:15:25 ALPHA TESTOPROEP MOB 1500141 16:15:27 GROUP P 1 BDH-01 OMS brandmelding Prinsenhof NH-Hotel Toren D Prinses Margrietplants 's-Gravenhage 159633 1503902 16:15:27 GROUP P 1 BDH-01 OMS brandmelding Prinsenhof NH-Hotel Toren D Prinses Margrietplants 's-Gravenhage 159633 2029569 16:15:27 ALPHA P 1 BDH-01 OMS brandmelding Prinsenhof NH-Hotel Toren D Prinses Margrietplants 's-Gravenhage 159633

multimon-ng: FLEX: State: SYNC1 FLEX: SyncInfoWord: sync_code=0x870c baud=1600 levels=2 polarity=POS zero=-0.030750 envelope=0.087751 symrate=1585.667877 FLEX: State: FIW FLEX: FrameInfoWord: cycleno=03 frameno=108 fix3=0x00 time=15:22 FLEX: State: SYNC2 FLEX: State: DATA FLEX: BlockInfoWord: (Phase A) BIW:0000300C AW:01-12 (11 pages) FLEX: CAPCODE:00000000000f59ae FLEX: Found Short Instruction, Group bit: 0 capcodes in group so far 1, adding Capcode: [001005998] FLEX: CAPCODE:00000000000f5618 FLEX: Found Short Instruction, Group bit: 0 capcodes in group so far 2, adding Capcode: [001005080] FLEX: CAPCODE:00000000000f4cea FLEX: Found Short Instruction, Group bit: 0 capcodes in group so far 3, adding Capcode: [001002730] FLEX: CAPCODE:00000000000f4cde FLEX: Found Short Instruction, Group bit: 0 capcodes in group so far 4, adding Capcode: [001002718] FLEX: CAPCODE:00000000000f4cd3 FLEX: Found Short Instruction, Group bit: 0 capcodes in group so far 5, adding Capcode: [001002707] FLEX: CAPCODE:00000000000f4ccd FLEX: Found Short Instruction, Group bit: 0 capcodes in group so far 6, adding Capcode: [001002701] FLEX: CAPCODE:00000000000f4ccc FLEX: Found Short Instruction, Group bit: 0 capcodes in group so far 7, adding Capcode: [001002700] FLEX: CAPCODE:00000000000f4a5e FLEX: Found Short Instruction, Group bit: 0 capcodes in group so far 8, adding Capcode: [001002078] FLEX: CAPCODE:00000000000f4a53 FLEX: Found Short Instruction, Group bit: 0 capcodes in group so far 9, adding Capcode: [001002067] FLEX: CAPCODE:00000000000f4a4d FLEX: Found Short Instruction, Group bit: 0 capcodes in group so far 10, adding Capcode: [001002061] FLEX: CAPCODE:00000000000f4a4c FLEX: Found Short Instruction, Group bit: 0 capcodes in group so far 11, adding Capcode: [001002060] FLEX: State: SYNC1 FLEX: SyncInfoWord: sync_code=0x870c baud=1600 levels=2 polarity=POS zero=-0.031121 envelope=0.087798 symrate=1585.676130 FLEX: State: FIW FLEX: FrameInfoWord: cycleno=03 frameno=109 fix3=0x3c time=15:24 FLEX: State: SYNC2 FLEX: State: DATA FLEX: BlockInfoWord: (Phase A) BIW:0000140A AW:01-05 (4 pages) FLEX: CAPCODE:00000000001ef800 FLEX: Parse Alpha Numeric FLEX Group message output: Groupbit: 0 Total Capcodes; 11; index 1; Capcode: [001005998] FLEX Group message output: Groupbit: 0 Total Capcodes; 11; index 2; Capcode: [001005080] FLEX Group message output: Groupbit: 0 Total Capcodes; 11; index 3; Capcode: [001002730] FLEX Group message output: Groupbit: 0 Total Capcodes; 11; index 4; Capcode: [001002718] FLEX Group message output: Groupbit: 0 Total Capcodes; 11; index 5; Capcode: [001002707] FLEX Group message output: Groupbit: 0 Total Capcodes; 11; index 6; Capcode: [001002701] FLEX Group message output: Groupbit: 0 Total Capcodes; 11; index 7; Capcode: [001002700] FLEX Group message output: Groupbit: 0 Total Capcodes; 11; index 8; Capcode: [001002078] FLEX Group message output: Groupbit: 0 Total Capcodes; 11; index 9; Capcode: [001002067] FLEX Group message output: Groupbit: 0 Total Capcodes; 11; index 10; Capcode: [001002061] FLEX Group message output: Groupbit: 0 Total Capcodes; 11; index 11; Capcode: [001002060] FLEX|2024-06-09 14:15:07|1600/2/K/A|03.109|002029568 001005998 001005080 001002730 001002718 001002707 001002701 001002700 001002078 001002067 001002061 001002060|ALN|P 1 BLB-03 Ongeval wegvervoer A2 Li - Autosnelweg A2 223,5 Echt 235331 235531 FLEX: CAPCODE:0000000000120160 FLEX: Parse Alpha Numeric FLEX: CAPCODE:000000000016f29e FLEX: Found Short Instruction, Group bit: 1 capcodes in group so far 1, adding Capcode: [001503902] FLEX: CAPCODE:000000000016e3ed FLEX: Found Short Instruction, Group bit: 1 capcodes in group so far 2, adding Capcode: [001500141] FLEX: State: SYNC1 FLEX: SyncInfoWord: sync_code=0x870c baud=1600 levels=2 polarity=POS zero=-0.031031 envelope=0.087828 symrate=1585.684352 FLEX: State: FIW FLEX: FrameInfoWord: cycleno=03 frameno=110 fix3=0x3c time=15:26 FLEX: State: SYNC2 FLEX: State: DATA FLEX: BlockInfoWord: (Phase A) BIW:0000100E AW:01-04 (3 pages) FLEX: CAPCODE:00000000001ef801 FLEX: Parse Alpha Numeric FLEX Group message output: Groupbit: 1 Total Capcodes; 2; index 1; Capcode: [001503902] FLEX Group message output: Groupbit: 1 Total Capcodes; 2; index 2; Capcode: [001500141] FLEX|2024-06-09 14:15:09|1600/2/K/A|03.110|002029569 001503902 001500141|ALN|P 1 BDH-01 OMS brandmelding Prinsenhof NH-Hotel Toren D Prinses Margrietplants 's-Gravenhage 159633

filibuster007 commented 2 months ago

Same situation but now using FLEX_NEXT seems to be handled ok.

I don't have a trace, but this message: "1180000 16:40:25 ALPHA TESTOPROEP MOB" would be the missing message using FLEX as a decoder.

PDW: 1400273 16:40:25 GROUP P 1 BRT-02 BR woning Albert Cuypstraat Capelle aan den IJssel 171151 171132 171131 1400331 16:40:25 GROUP P 1 BRT-02 BR woning Albert Cuypstraat Capelle aan den IJssel 171151 171132 171131 1400332 16:40:25 GROUP P 1 BRT-02 BR woning Albert Cuypstraat Capelle aan den IJssel 171151 171132 171131 1400349 16:40:25 GROUP P 1 BRT-02 BR woning Albert Cuypstraat Capelle aan den IJssel 171151 171132 171131 1400375 16:40:25 GROUP P 1 BRT-02 BR woning Albert Cuypstraat Capelle aan den IJssel 171151 171132 171131 1400999 16:40:25 GROUP P 1 BRT-02 BR woning Albert Cuypstraat Capelle aan den IJssel 171151 171132 171131 2029568 16:40:25 ALPHA P 1 BRT-02 BR woning Albert Cuypstraat Capelle aan den IJssel 171151 171132 171131 1180000 16:40:25 ALPHA TESTOPROEP MOB 0806240 16:40:37 GROUP Graag telefonisch contact MKB 0901927 16:40:37 GROUP Graag telefonisch contact MKB 2029568 16:40:37 ALPHA Graag telefonisch contact MKB

multimon-ng:

FLEX_NEXT: State: SYNC1 FLEX_NEXT: SyncInfoWord: sync_code=0x870c baud=1600 levels=2 polarity=POS zero=-0.030659 envelope=0.090133 symrate=1586.010181 FLEX_NEXT: State: FIW FLEX_NEXT: FrameInfoWord: cycleno=10 frameno=011 fix3=0x3c time=40:20 FLEX_NEXT: State: SYNC2 FLEX_NEXT: State: DATA FLEX_NEXT: Decoding phase A FLEX_NEXT: BlockInfoWord: (Phase A) BIW:0000040B AW 01 VW 01 (up to 0 pages) FLEX_NEXT: State: SYNC1 FLEX_NEXT: SyncInfoWord: sync_code=0x870c baud=1600 levels=2 polarity=POS zero=-0.031305 envelope=0.090413 symrate=1586.050462 FLEX_NEXT: State: FIW FLEX_NEXT: FrameInfoWord: cycleno=10 frameno=012 fix3=0x3c time=40:22 FLEX_NEXT: State: SYNC2 FLEX_NEXT: State: DATA FLEX_NEXT: Decoding phase A FLEX_NEXT: BlockInfoWord: (Phase A) BIW:00001C02 AW 01 VW 07 (up to 6 pages) FLEX_NEXT: Processing page offset #1 AW:0015E0A7 VW:00003417 FLEX_NEXT: CAPCODE:00000000001560a7 1400999 FLEX_NEXT: AIW 1: capcode:1400999 long:0 group:0 groupbit:0 FLEX_NEXT: Invalid VIW FLEX_NEXT: Processing page offset #2 AW:0015DE37 VW:00003417 FLEX_NEXT: CAPCODE:0000000000155e37 1400375 FLEX_NEXT: AIW 2: capcode:1400375 long:0 group:0 groupbit:0 FLEX_NEXT: Invalid VIW FLEX_NEXT: Processing page offset #3 AW:0015DE1D VW:00003417 FLEX_NEXT: CAPCODE:0000000000155e1d 1400349 FLEX_NEXT: AIW 3: capcode:1400349 long:0 group:0 groupbit:0 FLEX_NEXT: Invalid VIW FLEX_NEXT: Processing page offset #4 AW:0015DE0C VW:00003417 FLEX_NEXT: CAPCODE:0000000000155e0c 1400332 FLEX_NEXT: AIW 4: capcode:1400332 long:0 group:0 groupbit:0 FLEX_NEXT: Invalid VIW FLEX_NEXT: Processing page offset #5 AW:0015DE0B VW:00003417 FLEX_NEXT: CAPCODE:0000000000155e0b 1400331 FLEX_NEXT: AIW 5: capcode:1400331 long:0 group:0 groupbit:0 FLEX_NEXT: Invalid VIW FLEX_NEXT: Processing page offset #6 AW:0015DDD1 VW:00003417 FLEX_NEXT: CAPCODE:0000000000155dd1 1400273 FLEX_NEXT: AIW 6: capcode:1400273 long:0 group:0 groupbit:0 FLEX_NEXT: Invalid VIW FLEX_NEXT: State: SYNC1 FLEX_NEXT: SyncInfoWord: sync_code=0x870c baud=1600 levels=2 polarity=POS zero=-0.030906 envelope=0.090665 symrate=1586.090402 FLEX_NEXT: State: FIW FLEX_NEXT: FrameInfoWord: cycleno=10 frameno=013 fix3=0x3c time=40:24 FLEX_NEXT: State: SYNC2 FLEX_NEXT: State: DATA FLEX_NEXT: Decoding phase A FLEX_NEXT: BlockInfoWord: (Phase A) BIW:00000C03 AW 01 VW 03 (up to 2 pages) FLEX_NEXT: Processing page offset #1 AW:001F7800 VW:000742D5 FLEX_NEXT: CAPCODE:00000000001ef800 2029568 FLEX_NEXT: AIW 1: capcode:2029568 long:0 group:1 groupbit:0 FLEX_NEXT: VIW 3: type:5 mw1:6 len:29 frag:3 FLEX_NEXT|1600/2|10.013.A|0002029568|SG|5|ALN|3.0.K|P 1 BRT-02 BR woning Albert Cuypstraat Capelle aan den IJssel 171151 171132 171131k4 FLEX_NEXT: Processing page offset #2 AW:00128160 VW:0001915F FLEX_NEXT: CAPCODE:0000000000120160 1180000 FLEX_NEXT: AIW 2: capcode:1180000 long:0 group:0 groupbit:0 FLEX_NEXT: VIW 4: type:5 mw1:35 len:5 frag:3 FLEX_NEXT|1600/2|10.013.A|0001180000|SS|5|ALN|3.0.K|TESTOPROEP MOB FLEX_NEXT: State: SYNC1 FLEX_NEXT: SyncInfoWord: sync_code=0x870c baud=1600 levels=2 polarity=POS zero=-0.030939 envelope=0.090445 symrate=1586.074410 FLEX_NEXT: State: FIW FLEX_NEXT: FrameInfoWord: cycleno=10 frameno=018 fix3=0x3c time=40:33 FLEX_NEXT: State: SYNC2 FLEX_NEXT: State: DATA FLEX_NEXT: Decoding phase A FLEX_NEXT: BlockInfoWord: (Phase A) BIW:0000040B AW 01 VW 01 (up to 0 pages) FLEX_NEXT: State: SYNC1 FLEX_NEXT: SyncInfoWord: sync_code=0x870c baud=1600 levels=2 polarity=POS zero=-0.031361 envelope=0.090719 symrate=1586.113715 FLEX_NEXT: State: FIW FLEX_NEXT: FrameInfoWord: cycleno=10 frameno=019 fix3=0x3c time=40:35 FLEX_NEXT: State: SYNC2 FLEX_NEXT: State: DATA FLEX_NEXT: Decoding phase A FLEX_NEXT: BlockInfoWord: (Phase A) BIW:00000C03 AW 01 VW 03 (up to 2 pages) FLEX_NEXT: Processing page offset #1 AW:000E4327 VW:00005019 FLEX_NEXT: CAPCODE:00000000000dc327 901927 FLEX_NEXT: AIW 1: capcode:901927 long:0 group:0 groupbit:0 FLEX_NEXT: VIW 3: type:1 mw1:33 len:0 frag:0 FLEX_NEXT: Found Short Instruction, Group bit: 0 capcodes in group so far 1, adding Capcode: [0000901927] FLEX_NEXT: Processing page offset #2 AW:000CCD60 VW:00005019 FLEX_NEXT: CAPCODE:00000000000c4d60 806240 FLEX_NEXT: AIW 2: capcode:806240 long:0 group:0 groupbit:0 FLEX_NEXT: VIW 4: type:1 mw1:33 len:0 frag:0 FLEX_NEXT: Found Short Instruction, Group bit: 0 capcodes in group so far 2, adding Capcode: [0000806240] FLEX_NEXT: State: SYNC1 FLEX_NEXT: SyncInfoWord: sync_code=0x870c baud=1600 levels=2 polarity=POS zero=-0.031147 envelope=0.090992 symrate=1586.152692 FLEX_NEXT: State: FIW FLEX_NEXT: FrameInfoWord: cycleno=10 frameno=020 fix3=0x3c time=40:37 FLEX_NEXT: State: SYNC2 FLEX_NEXT: State: DATA FLEX_NEXT: Decoding phase A FLEX_NEXT: BlockInfoWord: (Phase A) BIW:00000807 AW 01 VW 02 (up to 1 pages) FLEX_NEXT: Processing page offset #1 AW:001F7800 VW:0002C1D3 FLEX_NEXT: CAPCODE:00000000001ef800 2029568 FLEX_NEXT: AIW 1: capcode:2029568 long:0 group:1 groupbit:0 FLEX_NEXT: VIW 2: type:5 mw1:4 len:11 frag:3 FLEX_NEXT|1600/2|10.020.A|0002029568|SG|5|ALN|3.0.K|FLEX Group message output: Groupbit: 0 Total Capcodes; 2; index 1; Capcode: [0000901927] 0000901927|FLEX Group message output: Groupbit: 0 Total Capcodes; 2; index 2; Capcode: [0000806240] 0000806240|Graag telefonisch contact MKB

ramonsmits commented 3 days ago

The following comment contains audio and log output that coincidentally shows this behavior too:

https://github.com/EliasOenal/multimon-ng/issues/219#issuecomment-2328149721