Closed acarslogger closed 5 years ago
Fixed a lazy programmer bug. Thanks for the report Yes there is a max around 16K ! Now with -U in json , man could get big packet (by the way UDP is now not really a good idea).
PS : You seems to receive more "interesting" traffic than me.
Hi Thierry,
Thanks for the corrected version of vdlm2dec.
If you are interested here is 1 example of an acars message greater than 1000 bytes. The first part of the message (Msg F21A) is 998 bytes long. The continuation / second part of the message (Msg F21B) is the remaining 340+ bytes. If an acars message can be up to 16k, I just wonder whether there is a cut off set in the aircraft avionics which cuts a long message at 1000 or 1024 bytes.
Stuart
[#5 (F:136.975 P:-5.6) 21/09/2018 10:33:43.941 -------------------------------- Command from Aircraft:344446 (airborne) to GroundD:2651D7 Frame-I: Ns:6 Nr:2 ACARS Aircraft reg: EC-LUT Flight id: UX0238 Mode: 2 Msg. label: H1 Block id: 2 Ack: ! Msg. no: F21A Message :
[#5 (F:136.975 P:-5.7) 21/09/2018 10:33:46.266 -------------------------------- Command from Aircraft:344446 (airborne) to GroundD:2651D7 Frame-I: Ns:7 Nr:3 ACARS Aircraft reg: EC-LUT Flight id: UX0238 Mode: 2 Msg. label: H1 Block id: 3 Ack: ! Msg. no: F21B Message :
No it's a vdl mode 2 message that could be 16K long. I did not expect that ACARS message send by vdlm2 could be longer than "classical" ACARS. I have to look at my code about that.
Acars messages on L-Band are also greater than the "classical" 220 bytes. An example follows.
Stuart
ACARS mode: 2 Aircraft reg: .OO-SFN (Jaero L-Band GES:43) Message label: 30 Block id: L [Uplink] Message content:- LOADSHEET FINAL 1114 EDNO1 SN371/29 29JUN18 BRU DLA OOSFN 2/8 ZFW 165136 MAX 167000 L TOF 48000 TOW 213136 MAX 215000 L TIF 39900 LAW 173236 MAX 177000 UNDLD 1864 PAX/25/242 TTL 278 DOI 96.7 LIZFW 115.9 LITOW 120.2 MACZFW 28.3 MACTOW 28.3 FUEL DENSITY 0.8 A25 B45 C93 D104 SEATROW TRIM SI A330-300 BW DOW 124804 SALEABLE CONFIGURATION 30C/256Y PAX WEIGHTS USED M94 F76 C35 I0 PANTRY CODE S CHECKED BAGGAGE PIECES DLA 2/Y/185 DLA 3/Y/109 4/C/23/Y/7 5/Y/20 NSI 2/Y/72 3/Y/112 4/C/25/Y/24 5/Y/35 LOAD IN CPTS 0/0 1/0 2/8577 3/7612 4/ 2110 5/1537 DLA C 1993 M 130 B 344/ 7356 O 110 T 0 NSI C 3034 M 0 B 268/ 5674 O 0 T 0 NOTOC: YES ICE/1/52 LIZFW LIMITS + 77.3/+ 171.9 NOW: + 115.9 LITOW LIMITS + 43.2/+ 161.6 NOW: + 120.2 PREPARED BY PIETER/DECLERCK 2 7883191 ISSUANCE DATE AND TIME: 29JUN 09:14 UTC ----------------------------------------------------------[29-06-18 09:15:39]
Hi Thierry,
The JSON UDP -j output is currently truncating UDP packets at 500 bytes. I'm not an expert in using 'c' , but found in 'out.c' there was a line which reads char pkt[500];. So I changed my copy to 1000, recompiled and it worked -- until I got a UDP packet that was greater than 1000 bytes!! The message had an acars message of 985 characters; when you add the preceding data in JSON format it broke the 1000 barrier. I know in traditional (analogue/2400bps) acars messages the maximum length of the acars message is 220 bytes. Is there a corresponding maximum length (1024?) defined for VDL2 processing?
Regards Stuart