highaltitude.log.20190304

[01:32] Hoogvlieger (~Hoogvlieg@541A8CEB.cm-5-3c.dynamic.ziggo.nl) joined #highaltitude.
[01:41] happysat (~katpoep@s5594c83f.adsl.online.nl) left irc: Ping timeout: 245 seconds
[01:50] Hoogvlieger (~Hoogvlieg@541A8CEB.cm-5-3c.dynamic.ziggo.nl) left irc: Quit: Leaving
[02:21] happysat (~katpoep@s5594c83f.adsl.online.nl) joined #highaltitude.
[02:28] tripleclones (~tripleclo@2001:ba8:1f1:f273::2) left irc: Ping timeout: 264 seconds
[02:29] tripleclones (~tripleclo@85.119.83.134) joined #highaltitude.
[02:38] tjq (uid339161@gateway/web/irccloud.com/x-jeafyeafnmwgvuqc) joined #highaltitude.
[03:08] charlesnw (~charlesnw@158.69.183.161) left irc: Quit: ZNC 1.6.3+deb1ubuntu0.1 - http://znc.in
[03:14] charlesnw (~charlesnw@158.69.183.161) joined #highaltitude.
[03:55] tweetBot (~nodebot@philcrump.co.uk) left irc: Remote host closed the connection
[03:55] tweetBot (~nodebot@philcrump.co.uk) joined #highaltitude.
[05:01] YO9GJX (~YO9GJX@109.100.112.75) left irc: Remote host closed the connection
[05:27] Lahti2 (2588328e@gateway/web/freenode/ip.37.136.50.142) joined #highaltitude.
[05:55] tjq (uid339161@gateway/web/irccloud.com/x-jeafyeafnmwgvuqc) left irc: Quit: Connection closed for inactivity
[06:04] adam_ (c209f52c@gateway/web/freenode/ip.194.9.245.44) joined #highaltitude.
[06:04] adam_ (c209f52c@gateway/web/freenode/ip.194.9.245.44) left irc: Client Quit
[06:09] GeekShadow (~antoine@reactos/tester/GeekShadow) left irc: Ping timeout: 250 seconds
[06:10] GeekShadow (~antoine@nzf.turmel.info) joined #highaltitude.
[06:10] GeekShadow (~antoine@nzf.turmel.info) left irc: Changing host
[06:10] GeekShadow (~antoine@reactos/tester/GeekShadow) joined #highaltitude.
[06:20] Kodar (~Kodar@93-139-223-230.adsl.net.t-com.hr) joined #highaltitude.
[06:20] Kodar (~Kodar@93-139-223-230.adsl.net.t-com.hr) left irc: Client Quit
[06:20] Kodar (~Kodar@93-139-223-230.adsl.net.t-com.hr) joined #highaltitude.
[06:23] tjq (uid339161@gateway/web/irccloud.com/x-bocldztorefytuyb) joined #highaltitude.
[06:29] <SpacenearUS> New vehicle on the map: 03SQ5PGC - 12https://tracker.habhub.org/#!qm=All&q=SQ5PGC
[06:38] <SpacenearUS> New vehicle on the map: 03TA2MUN-13 - 12https://tracker.habhub.org/#!qm=All&q=TA2MUN-13
[06:45] Viproz (~Viproz@unaffiliated/viproz) joined #highaltitude.
[06:53] chandroid (~chandroid@bnn76.neoplus.adsl.tpnet.pl) left irc: Ping timeout: 258 seconds
[06:53] chandroid (~chandroid@brh21.neoplus.adsl.tpnet.pl) joined #highaltitude.
[06:58] <SpacenearUS> New position from 03DL4MDW-11 after 038 hours silence - 12https://tracker.habhub.org/#!qm=All&q=DL4MDW-11
[07:10] <SpacenearUS> New position from 03SP9UOB-P28 after 0314 hours silence - 12https://tracker.habhub.org/#!qm=All&q=SP9UOB-P28
[07:27] number10 (d42c14ce@gateway/web/freenode/ip.212.44.20.206) joined #highaltitude.
[07:30] <SpacenearUS> New position from 03U3B-25 after 0315 hours silence - 12https://tracker.habhub.org/#!qm=All&q=U3B-25
[07:39] Viproz (~Viproz@unaffiliated/viproz) left irc: Ping timeout: 244 seconds
[08:04] <SpacenearUS> New position from 03BSS18 after 0312 hours silence - 12https://tracker.habhub.org/#!qm=All&q=BSS18
[08:32] Muzer (~muzer@tim32.org) left irc: Ping timeout: 268 seconds
[08:38] Guest29496 (~anony@cpe-85-10-26-226.dynamic.amis.net) left irc: Read error: Connection reset by peer
[08:43] Muzer (~muzer@tim32.org) joined #highaltitude.
[08:43] ok1cdj (b04a8da0@gateway/web/freenode/ip.176.74.141.160) joined #highaltitude.
[08:44] <ok1cdj> hello all
[08:47] chandroid (~chandroid@brh21.neoplus.adsl.tpnet.pl) left irc: Ping timeout: 245 seconds
[08:48] chandroid (~chandroid@bnx10.neoplus.adsl.tpnet.pl) joined #highaltitude.
[08:48] <fsphil> morns
[08:53] GeekShadow (~antoine@reactos/tester/GeekShadow) left irc: Ping timeout: 245 seconds
[08:53] GeekShadow (~antoine@nzf.turmel.info) joined #highaltitude.
[08:53] GeekShadow (~antoine@nzf.turmel.info) left irc: Changing host
[08:53] GeekShadow (~antoine@reactos/tester/GeekShadow) joined #highaltitude.
[09:12] m6olz (520b4ab1@gateway/web/freenode/ip.82.11.74.177) joined #highaltitude.
[09:14] <m6olz> Who is BUZZ_AUTO_RX near Ipswich UK?
[09:14] <Darkside> daveake:
[09:14] <daveake> Nope!
[09:14] <m6olz> I have few questions
[09:14] <Darkside> oh!
[09:14] <daveake> John someone iirc
[09:14] <Darkside> daveake: i just assumed given the name :P
[09:14] <daveake> yeah I never (c) it :)
[09:15] <Darkside> m6olz: shoot with your qurstions, someone here can probably answer
[09:15] <Darkside> maybe
[09:16] <ok1cdj> all: i made mistake in QRG of my Pico flight this afternoon, right is 434.690 MHz, by prediction will be direction to SP, EW, LY, UA3, any trackers are welcome
[09:16] <m6olz> I see on habhub website that he have station and receive very far radisondes and just want to know what antenna,sdr and setting for gain he use
[09:16] <Darkside> ahh
[09:16] <Darkside> well SDR will be a RTLSDR, as thats all auto_Rx supports
[09:17] <Darkside> dunno about antenna and other settings
[09:17] <Darkside> not sure if he's on the radiosonde_auto_rx google group either
[09:18] <m6olz> RTL SDR has many version on ebay.......i think the better is silver v3 with low noise floor
[09:18] <Darkside> yes
[09:18] <Darkside> thats what i recommend in the installation guide
[09:18] <m6olz> thank you Mark
[09:18] <dbrooke> it claims to be using a 1/4 wave monopole (click on the mast icon)
[09:19] <Darkside> dbrooke: thats the default antenna description
[09:19] <dbrooke> oh
[09:19] <Darkside> maybe i should change the default to "I haven't changed my default settings!"
[09:19] <dbrooke> I set mine correctly 8-)
[09:19] <m6olz> i now use sirio cx395
[09:20] <m6olz> better than x50
[09:21] <m6olz> but I am in London and too many high buildings around me....no way for high antenna mast
[09:25] m6olz (520b4ab1@gateway/web/freenode/ip.82.11.74.177) left irc: Ping timeout: 256 seconds
[09:32] ok1cdj (b04a8da0@gateway/web/freenode/ip.176.74.141.160) left irc: Quit: Page closed
[09:49] dfm (59cc9bad@gateway/web/freenode/ip.89.204.155.173) joined #highaltitude.
[09:52] <dfm> darkside, i added the continuous output -c for dft_detect, can be time limited, -t <sec>. So if you can detect a few seconds and evaluate, which detection is the most promissing, or iterate through result.
[09:53] <dfm> Usefull when using lower boundaries.
[09:53] <dfm> thresholds
[09:57] dfm (59cc9bad@gateway/web/freenode/ip.89.204.155.173) left irc:
[10:18] lahti (~lahti@87-92-72-134.bb.dnainternet.fi) got netsplit.
[10:18] Mikitsubs (~mikitsubs@87-92-72-134.bb.dnainternet.fi) got netsplit.
[10:29] Mikitsubs (~mikitsubs@87-92-72-134.bb.dnainternet.fi) got lost in the net-split.
[10:29] lahti (~lahti@87-92-72-134.bb.dnainternet.fi) got lost in the net-split.
[10:29] <SpacenearUS> New vehicle on the map: 03SQ5PGC-13 - 12https://tracker.habhub.org/#!qm=All&q=SQ5PGC-13
[10:48] chandroid (~chandroid@bnx10.neoplus.adsl.tpnet.pl) left irc: Ping timeout: 250 seconds
[10:48] chandroid (~chandroid@bvr2.neoplus.adsl.tpnet.pl) joined #highaltitude.
[11:11] michal_f (~michal_f@212.75.108.114) joined #highaltitude.
[11:13] Lahti2 (2588328e@gateway/web/freenode/ip.37.136.50.142) left irc: Quit: Page closed
[11:32] qyx (~qyx@gw2.krtko.org) left irc: Read error: Connection reset by peer
[11:37] qyx (~qyx@gw2.krtko.org) joined #highaltitude.
[12:07] chandroid (~chandroid@bvr2.neoplus.adsl.tpnet.pl) left irc: Ping timeout: 268 seconds
[12:08] chandroid (~chandroid@bqy102.neoplus.adsl.tpnet.pl) joined #highaltitude.
[12:09] sam__ (~sms@89.238.183.61) joined #highaltitude.
[12:23] Lahti2 (25215c07@gateway/web/freenode/ip.37.33.92.7) joined #highaltitude.
[12:23] xfce (~anony@cpe-85-10-26-226.dynamic.amis.net) joined #highaltitude.
[12:23] Nick change: xfce -> Guest667
[12:24] TT7 (d5c2e677@gateway/web/freenode/ip.213.194.230.119) joined #highaltitude.
[12:32] geheimnis` (~geheimnis@23.226.237.192) left irc: Remote host closed the connection
[12:40] geheimnis` (~geheimnis@23.226.237.192) joined #highaltitude.
[12:41] m6olz (520b4ab1@gateway/web/freenode/ip.82.11.74.177) joined #highaltitude.
[12:41] <TT7> there is around 10 pico balloons about to be released from Brno in the Czech Republic
[12:42] <TT7> a couple of them APRS, one WSPR, RTTY, Contestia, a few using LoRaWan
[12:44] <TT7> all on 36" qualatex balloons
[12:46] <TT7> flight path: http://predict.habhub.org/#!/uuid=79035e0144adb658e8b4681922d1cea962296f1d
[12:52] <TT7> information about some of the trackers: http://picoballoon.sosa.sk/viewforum.php?f=9
[13:03] Mikitsubs (~mikitsubs@87-92-72-134.bb.dnainternet.fi) joined #highaltitude.
[13:03] lahti (~lahti@87-92-72-134.bb.dnainternet.fi) joined #highaltitude.
[13:04] lahti (~lahti@87-92-72-134.bb.dnainternet.fi) got netsplit.
[13:04] Mikitsubs (~mikitsubs@87-92-72-134.bb.dnainternet.fi) got netsplit.
[13:05] tjq (uid339161@gateway/web/irccloud.com/x-bocldztorefytuyb) left irc: Quit: Connection closed for inactivity
[13:06] chris_99 (uid26561@gateway/web/irccloud.com/x-tdvnjfnuirfwydfe) joined #highaltitude.
[13:08] Mikitsubs (~mikitsubs@87-92-72-134.bb.dnainternet.fi) returned to #highaltitude.
[13:08] lahti (~lahti@87-92-72-134.bb.dnainternet.fi) returned to #highaltitude.
[13:14] BrainDamage_ (~BrainDama@unaffiliated/braindamage) joined #highaltitude.
[13:15] <SpacenearUS> New position from 03SP9UOB-P33 after 0320 hours silence - 12https://tracker.habhub.org/#!qm=All&q=SP9UOB-P33
[13:17] BrainDamage (~BrainDama@unaffiliated/braindamage) left irc: Ping timeout: 268 seconds
[13:17] Nick change: BrainDamage_ -> BrainDamage
[13:18] m6olz (520b4ab1@gateway/web/freenode/ip.82.11.74.177) left irc: Quit: Page closed
[13:19] <SpacenearUS> New position from 03CDJ3 after 03a day silence - 12https://tracker.habhub.org/#!qm=All&q=CDJ3
[13:23] ok1cdj (2e87196e@gateway/web/freenode/ip.46.135.25.110) joined #highaltitude.
[13:23] <ok1cdj> hello all CDJ3 is alive 434.680 +/- drift
[13:23] <ok1cdj> please tracking
[13:24] m0nba (uid314743@gateway/web/irccloud.com/x-tootyfmnxnmjlsmu) left irc: Ping timeout: 264 seconds
[13:25] m0nba (sid314743@gateway/web/irccloud.com/x-skswooslwmsavadw) joined #highaltitude.
[13:41] shiftplusone (~shift@unaffiliated/shiftplusone) left irc: Remote host closed the connection
[13:41] <SpacenearUS> New vehicle on the map: 03HgjHgj_chase - 12https://tracker.habhub.org/#!qm=All&q=HgjHgj_chase
[13:41] shiftplusone (~shift@unaffiliated/shiftplusone) joined #highaltitude.
[13:44] <ok1cdj> anyone QRV now on 70cm, please try tracking CDJ3, TNX
[13:48] cshields (sid142@gateway/web/mozilla/x-ptznctcyuluofvfd) left irc: Ping timeout: 250 seconds
[13:54] cshields (sid142@gateway/web/mozilla/x-olwtlmixnqckctjo) joined #highaltitude.
[14:00] cacoethes (~sms@5.39.181.45) joined #highaltitude.
[14:01] cacoethes (~sms@5.39.181.45) left irc: Client Quit
[14:01] sam__ (~sms@89.238.183.61) left irc: Ping timeout: 240 seconds
[14:01] __sam (~sms@5.39.181.45) joined #highaltitude.
[14:02] __sam (~sms@5.39.181.45) left irc: Client Quit
[14:02] cacoethes (~sms@5.39.181.45) joined #highaltitude.
[14:06] <ok1cdj> anyone from SP to track CDJ3 please
[14:06] <ok1cdj> Callsign: CDJ3 434.690MHz +/- drift USB RTTY 50 baud 450Hz shift ASCII-7 no parity 2 stop bits atl < 4000m 3 RTTY frames every 1 minute float > 4000m 3 RTTY frames every 10 minutes
[14:11] ok1cdj (2e87196e@gateway/web/freenode/ip.46.135.25.110) left irc: Ping timeout: 256 seconds
[14:25] fl_0 (unknown@unaffiliated/fl-0/x-7355575) left irc: Quit: STRG + Q
[14:31] fl_0 (~fl_0@unaffiliated/fl-0/x-7355575) joined #highaltitude.
[14:47] matt_ (836fb945@gateway/web/freenode/ip.131.111.185.69) joined #highaltitude.
[14:47] Nick change: matt_ -> Guest25387
[14:47] Guest25387 (836fb945@gateway/web/freenode/ip.131.111.185.69) left irc: Client Quit
[14:48] <TT7> I've been looking for CDJ3, but there's been nothing in the waterfall so far. though my rx setup is not the best.
[15:48] happysat (~katpoep@s5594c83f.adsl.online.nl) left irc: Quit: Hunger-the-inner-diva
[15:50] TT7 (d5c2e677@gateway/web/freenode/ip.213.194.230.119) left irc: Quit: Page closed
[15:56] happysat (~katpoep@s5594c83f.adsl.online.nl) joined #highaltitude.
[16:29] <SpacenearUS> New vehicle on the map: 03SH07 - 12https://tracker.habhub.org/#!qm=All&q=SH07
[16:36] <SpacenearUS> New vehicle on the map: 03SH05 - 12https://tracker.habhub.org/#!qm=All&q=SH05
[16:54] cacoethes (~sms@5.39.181.45) left irc: Ping timeout: 255 seconds
[16:59] <SpacenearUS> New position from 03YO3ICT after 032 days silence - 12https://tracker.habhub.org/#!qm=All&q=YO3ICT
[17:00] cacoethes (~sms@5.39.181.45) joined #highaltitude.
[17:05] cgosling (1827521e@gateway/web/freenode/ip.24.39.82.30) joined #highaltitude.
[17:07] <cgosling> High school teacher looking for help creating payload documents for HAB launch. Trying to figure out what a "typical telemtry string" looks like. We've been trying various portions of the RTTY signal we're sending/receiving without success. Can anyone help?
[17:19] <daveake> If you check the PITS manual it has the field list there, including the extra fields you get if you've added any extra devices
[17:19] <daveake> Also see https://ukhas.org.uk/guides:documents
[17:19] chandroid (~chandroid@bqy102.neoplus.adsl.tpnet.pl) left irc: Ping timeout: 245 seconds
[17:19] chandroid (~chandroid@bsn113.neoplus.adsl.tpnet.pl) joined #highaltitude.
[17:55] <cgosling> Thanks <daveake>. This is our input: $$KC2VMF,96,14:52:47,44.32800,-74.14440,00514,0,0,12,31.5,0.0,0.001,21.3,954*DD36. I've tried pasting that into the payload is into the parser, but it doesn't work. Which bits need to be entered?
[17:57] <daveake> Get the field list from the manual Enter those fields into genpayload.
[17:58] Craghill (51696dd8@gateway/web/freenode/ip.81.105.109.216) joined #highaltitude.
[18:00] <daveake> Fields will look like this to start with, but remember to include ALL fields including battery voltage/current, air pressure etc (refer to manual) https://usercontent.irccloud-cdn.com/file/KAA3TaMg/image.png
[18:02] <Craghill> I am launching a HAB for a school project next tuesday from Cambridge. For our GPS we are using a habduino. I have managed to succesfully receive coordinates using an SDR and decode them using DL FLDigi. The one thing I don't know how to do is upload the data to the habhub tracker and to get it track it on the map. If someone could advise me on this that would be greatly appreciated.
[18:05] <SpacenearUS> New vehicle on the map: 03KC2VMF - 12https://tracker.habhub.org/#!qm=All&q=KC2VMF
[18:09] <cgosling> Thanks <daveake>, it's sorted.
[18:18] <cgosling> Is the chase car iOS App still available? The link here (https://ukhas.org.uk/general:chase_car_trackers) doesn't work and iTunes says it's not available.
[18:19] test (b9a5f125@gateway/web/freenode/ip.185.165.241.37) joined #highaltitude.
[18:19] test (b9a5f125@gateway/web/freenode/ip.185.165.241.37) left #highaltitude.
[18:21] Craghill_ (51696dd8@gateway/web/freenode/ip.81.105.109.216) joined #highaltitude.
[18:22] Viproz (~Viproz@unaffiliated/viproz) joined #highaltitude.
[18:23] Craghill (51696dd8@gateway/web/freenode/ip.81.105.109.216) left irc: Ping timeout: 256 seconds
[18:29] YO9GJX (~YO9GJX@109.100.112.75) joined #highaltitude.
[18:32] <Craghill_> I am launching a HAB for a school project. I am using a habduino. I know how to receive and decode the coordinates using FL DLDigi. However, I don't know how to track the payload on the habhub tracker. Our launch day is the 12th of March and if anyone could help it would be greatly appreciated thanks.
[18:32] FireFighter (~firefight@2601:44:4200:ab4f:2845:e7ec:b22f:c409) joined #highaltitude.
[18:33] <daveake> No idea about iOS app, sorry
[18:35] <daveake> Craghill_: See https://ukhas.org.uk/guides:documents with reference to whatever the habduino docs say
[18:37] <Craghill_> Thankyou.
[18:40] nigelvh (~nigel@50-46-212-13.evrt.wa.frontiernet.net) left irc: Ping timeout: 240 seconds
[18:42] nigelvh (~nigel@50-46-212-13.evrt.wa.frontiernet.net) joined #highaltitude.
[18:42] Nick change: nigelvh -> Guest63833
[18:50] Guest63833 (nigel@50-46-212-13.evrt.wa.frontiernet.net) left #highaltitude.
[18:50] nigelvh (~nigel@50-46-212-13.evrt.wa.frontiernet.net) joined #highaltitude.
[19:11] <SpacenearUS> New vehicle on the map: 03SQ5OUZ-14 - 12https://tracker.habhub.org/#!qm=All&q=SQ5OUZ-14
[19:13] sumie-dh (~sumie-dh@78.108.102.220) left irc: Ping timeout: 255 seconds
[19:15] sumie-dh (~sumie-dh@78.108.102.220) joined #highaltitude.
[19:19] <Craghill_> I have created a payload document using a template and altering some details. However when i try to select the payload on the list of payloads on dl fldigi, it doesn't work. Am I missing something or is the software faulty.
[19:21] <SpacenearUS> New vehicle on the map: 03KM4MRH-2 - 12https://tracker.habhub.org/#!qm=All&q=KM4MRH-2
[19:24] <Craghill_> Also what is a GPS Lock
[19:26] <daveake> Means the GPS has locked onto enough satellites to get a position
[19:26] <daveake> Needs 3 for long/lat; 4 to include altitude
[19:29] <Craghill_> Ohhhh thanks. I have that. do you know if there is an issue with dl fldigi in regards to linking to a payload document. I have tried on three different devices and it doesnt work. Whenever I press on the document in the list it doesn't select it.
[19:31] cgosling (1827521e@gateway/web/freenode/ip.24.39.82.30) left irc: Quit: Page closed
[19:33] <daveake> Dunno I never use that
[19:34] <PE2BZ> Craghill) you use the payload document in fldigi ¨just for¨ autoconfigure fldigi for the settings you have set in the payload doc.
[19:34] <daveake> I checked the logtail.... first thing is you should change your payload ID from "HABDUINO" to something specific to you .... project name, school name, radio callsign if you have one. Something shortish too.
[19:34] <PE2BZ> That is, the speed (baudrate) shift and parity.
[19:35] <Craghill_> Ok will change it now
[19:43] <Craghill_> I have changed it to "JHN_HAB_GPS" I see in the parser logtail that there are some errors. What do they mean?
[19:44] <daveake> Well, you don't have a payload doc that matches that callsign
[19:56] <Craghill_> I have made a doc with a matching callsign. Now it is saying that it got 10 fields when it expected 9
[19:56] <daveake> Well that's fairly descriptive
[19:57] <daveake> Means your payload is transmitting 10 fields but the payload doc is set up for 9
[19:57] <Craghill_> Ok. Thanks
[19:59] <daveake> So figure out what's missing, by comparing the field list of your payload with the that in the document, and add what's missing. Make sure you have them in the right order too.
[20:02] <Craghill_> Ok
[20:08] dfm (59cc9b60@gateway/web/freenode/ip.89.204.155.96) joined #highaltitude.
[20:08] cacoethes (~sms@5.39.181.45) left irc: Ping timeout: 240 seconds
[20:09] <dfm> Viproz: have you be running some test with the snr-samples?
[20:10] <dfm> en
[20:12] <Viproz> dfm, I haven't been but I'm only doing M10 anyway right now
[20:12] <dfm> yes, M10.
[20:13] <dfm> the csdr chain
[20:13] <SpacenearUS> New vehicle on the map: 03JHNBALLOONV3 - 12https://tracker.habhub.org/#!qm=All&q=JHNBALLOONV3
[20:14] <dfm> only small changes in parameters can make a lot of difference
[20:15] <dfm> even baud rate, just counted the samples of the preamble at 96kHz, it is more 9615 than 9616, at 9.5dB can improve decoding from 15 to 20 frames OK
[20:16] <Craghill_> Thank you for all your help. I really appreciate it.
[20:16] Craghill_ (51696dd8@gateway/web/freenode/ip.81.105.109.216) left irc: Quit: Page closed
[20:16] <dfm> I'am not sure how constant this baud rate is, don't want to evaluate the preamble, wouldn't be accurate anyway.
[20:22] <Viproz> The optimal baudrate changed from 9614 to 1916 iirc in my testing on different audio files
[20:22] <Viproz> 9616*
[20:25] <dfm> and changing bandpass filter from -0.2..0.2 to -0.21..0.21 improved from 16 to 40 correct frames at 9.5dB.
[20:28] <dfm> Only numbers for the file I generated, if I would generate another 9.5dB file, it would be a bit different.
[20:43] <Viproz> I'll do some testing with a longer recording then
[20:46] <dfm> Or generate several 9.5db samples from the original one.
[20:48] <dfm> best results so far: cat m10_96k_float_9.5dB.bin | csdr fir_decimate_cc 2 0.005 | csdr bandpass_fir_fft_cc -0.21 0.21 0.005 | csdr fmdemod_quadri_cf | csdr limit_ff | csdr convert_f_s16 | sox -t raw -r 48000 -b 16 -e signed - -t wav - 2>/dev/null | ./m10decoder
[20:48] <dfm> but only with one file, as I said.
[20:49] <Viproz> you're using my cpp version of the decoder or you c version ?
[20:49] <dfm> if you save the fm-audio, you should see the spikes. it is good to filter them.
[20:50] <dfm> I tried yours, so maybe not the newest version
[20:51] <dfm> if i don't filter the spikes, yours got some more.
[20:51] <dfm> with --spike i got 40 ok-frames, and 105 alltogether i think
[20:51] <Viproz> I haven't improved the decodign for a while now but you should use -b and -b2 on my version, it just adds tries, can't be less decodes
[20:52] <dfm> i know
[20:52] <Viproz> -s too but I haven't had much luck with this one
[20:52] <Viproz> only usefull before the first decode
[20:54] <dfm> with the right bandpass, it is similar, you got 42/82
[20:54] <Viproz> what's --spike ? you remove them with csdr or in code ?
[20:56] <dfm> no, in decoding, because when only integrating, then a sample that goes through the roof is not so good.
[20:56] <dfm> so i compare to the sample before and after.
[20:56] <dfm> but yours decodes fine.
[20:56] <Viproz> -b normilizes eveyrhing so I guess it's less sensible to peaks
[20:57] <dfm> maybe be, i will try without
[20:57] <dfm> yes, about half.
[20:58] <dfm> -b2 didn't make a difference
[20:58] <Viproz> yeah b2 tries to replace the part that don't change with the data it stored from a good frame
[20:59] <dfm> oh, ok.
[20:59] <Viproz> -s tries to guess what the good part are before having a correct decode
[21:00] <dfm> ok, -b and -b2 alone is almost the same 24-26.
[21:00] <dfm> together its 42.
[21:00] <dfm> so without using previous frames, it is about 25 frames.
[21:01] <Viproz> I didn't add something to remove the basic decoding, could be usefull to compare the two methods
[21:01] <dfm> with this spikes, there are parameters to choose, what is considered as a spike.
[21:01] Lahti2 (25215c07@gateway/web/freenode/ip.37.33.92.7) left irc: Quit: Page closed
[21:02] <dfm> the csdr-fm has some gain, don't know why it procudes so much spikes.
[21:02] <Viproz> didi you make a decoder for m2k2 too ?
[21:02] <dfm> so i think ive seen this with sdr before, but not sure.
[21:03] <Viproz> could be usefull to compare with rtl_fm but can't bandpass
[21:03] <dfm> only know, m2k2 has 8F as type (2nd byte) but Ive never seen a m2k2, only the sample on this radiosonde.ec.website i think
[21:04] <Viproz> Okay I though they were just like M10 since they are (were ?) made by MeteoModem
[21:05] <dfm> what i wanted to say, if csdr is to be used in the decoding chain, maybe the typical csdr-fm output should be considered, and if these spikes often occur, it is maybe good to filter them.
[21:06] <dfm> Probably they are similar.
[21:06] <dfm> on the photos it was also a trimble gps, not sure if copernicus or lasse.
[21:07] <dfm> so i don't hear much about the new developedment, the m20 was tested, but don't hear much.
[21:07] <Viproz> the trimble sonde no longer use trimble GPS, we're using a bad name ^^
[21:08] <dfm> and the gtop? did they find another replacement for the trimble now, didn't you say, now is another chip inside? sierra airprim? and the old trimble-gps output!?
[21:08] <Viproz> I don't know why they created a whole new frame for Gtop but then just used a Sierra and kept the old frame
[21:09] <dfm> ok, it was trimble for many years.
[21:09] <Viproz> https://photos.app.goo.gl/63HypaFZBS5sWepF9
[21:09] sp8ncg (5ee89e40@gateway/web/freenode/ip.94.232.158.64) joined #highaltitude.
[21:09] <dfm> since ever, i think.
[21:10] <Viproz> I caught it like a month ago, manufactured in 2018-03 (it's the recording w're using)
[21:10] Ruben_ (5478ac8b@gateway/web/freenode/ip.84.120.172.139) joined #highaltitude.
[21:10] <dfm> and the gps-data is like the trimble-binary data. maybe they want to have continuity/compatibility.
[21:10] test89775 (25ad7142@gateway/web/freenode/ip.37.173.113.66) joined #highaltitude.
[21:10] <dfm> Ah, it say M10+V01
[21:11] sp8ncg (5ee89e40@gateway/web/freenode/ip.94.232.158.64) left irc: Client Quit
[21:11] <test89775> We don't need to register while on the webinterface right ?
[21:11] <Viproz> ok good
[21:11] test89775 (25ad7142@gateway/web/freenode/ip.37.173.113.66) left irc: Client Quit
[21:11] <dfm> thanks for photos.
[21:12] <Ruben_> Hello... I am Ruben EA5BZ.
[21:12] <Viproz> I ordered a JTAG cable to pull the firmware out, can compare it to the older firmware
[21:12] <Viproz> Ruben_, hey nice
[21:13] chris_99 (uid26561@gateway/web/irccloud.com/x-tdvnjfnuirfwydfe) left irc:
[21:13] <Ruben_> I wrote an issue on radiosonde_auto_rx about m2k2 reception.
[21:13] <Ruben_> How could i help?
[21:13] <Viproz> dfm, Ruben_ just made an issue to support m2k2 on auto_rx, that's why I was asking :D
[21:13] <dfm> then you can see if the gps data is converted. i will check the sierra documentation, found only nmea-output, then they would have to convert it.
[21:14] <dfm> but where is the m2k2 in use?
[21:14] <Viproz> We're going to need some samples of some good recordings, do you know what the bandwidth of the signal is ?
[21:15] <Ruben_> I am using around 30 khz
[21:15] <dfm> ok, the gtop-pcb also says m10+V01, it is the pcb-sn after all (i guess).
[21:15] <Ruben_> it is a little lower.
[21:15] <Darkside> ugh wide bandwidth one
[21:16] <Darkside> Ruben_: a IQ recording, maybe a few hundred khzbandwidth, with the signal at the centre would be good
[21:16] <Viproz> Darkside, maybe it's just like the M10, when you have a good signal it's really fat on the sides
[21:16] <Darkside> true
[21:16] <dfm> Who is using the M2K2? Where is it flying?
[21:16] <Ruben_> Darkside: I will work on it tomorrow.
[21:17] <Ruben_> Will contact you when saved IQ.
[21:17] <Darkside> French Modem MK2K
[21:18] <Darkside> oh wait
[21:18] <Darkside> nope, m2k2
[21:18] <Darkside> wow they are old - 2004
[21:18] <Viproz> SondeMonitor is decoding it so finding the frame won't be too hard
[21:19] <dfm> yes, then m10 came to take its place. thats why i ask. the m20 is already knocking at the door.
[21:19] <Viproz> I don't know if MeteoModem still makes pilotsonde btw, might be worth adding too
[21:19] <Ruben_> Now i can send you some audio....is valid for you?
[21:19] <Ruben_> Tomorrow i will try IQ Saving.
[21:19] <Viproz> Ruben_, where are they sending them ?
[21:19] <Ruben_> Murcia (Spain)
[21:20] <Darkside> Ruben_: the reason IQ is useful as it helps with picking an optimal receiver bandwidth
[21:20] <Ruben_> I understand.
[21:20] <Darkside> but FM demodulated audio, whatever much work with sondemonitor, is a start
[21:20] <Viproz> but yeah audio is good to start the decoding process, would be usefull if it's not hard to upload
[21:20] <Darkside> i hope they upgrade soon...
[21:20] <Ruben_> how can i send you this audio?
[21:20] <Darkside> having to deal with old drifty sondes is a pain
[21:21] <Viproz> Ruben_, well how heavy is the file ?
[21:22] <dfm> How many of them did they order?
[21:22] <Ruben_> 4 mb around
[21:22] <dfm> Udine always ordered so many vaisala sondes, they had the rs92-k till 2015 i think.
[21:23] <Viproz> oh, mail is good enough then, you can send it to viproz12@gmail.com, I'll pass it around if someone else wants it
[21:24] <Ruben_> sent
[21:24] <Ruben_> we will be in toch !
[21:24] <dfm> this 10 sec sample from radiosonde.eu gives 648f and check-OK,
[21:24] <Viproz> in france I guess we have a one year backlog and Ury was still sending M10 the other time, never saw something that we couldn't decode
[21:24] <dfm> so it is very similar to m10
[21:25] <Viproz> Ruben_, thanks !
[21:25] <Ruben_> Thank's to you.
[21:25] <dfm> sure it is interesting, historically.
[21:26] <Viproz> sounds just like M10 trimble
[21:26] <Viproz> with the GPS infos sent on a double frame too I guess
[21:26] <Ruben_> viproz: you can contact by email if not here.
[21:26] <dfm> do you have a better sample, don't even now if there is a gpslock in here.
[21:26] cacoethes (~sms@2a00:23c5:eb0f:2300:ad4a:e11f:d5db:4f25) joined #highaltitude.
[21:27] <dfm> so if you want to include it in auto_rx, it makes it more complex, detection e.g. don't know how much future the m2k2 has, maybe as imet1ab
[21:28] <Viproz> GPS lock, sondemonitor detected a frame
[21:28] <Viproz> oh on the other sample, dm me your email I'll pass it
[21:28] <Viproz> wird it sounds like it's going down but it's going up
[21:29] <Darkside> but yeah... how many of these ancient sondes do we really want to spend effort on supporting?
[21:29] <Darkside> its possibly they wont xist in a years tiem
[21:29] <dfm> it has 8f and 47 frames-
[21:29] <Darkside> exist*
[21:30] <Viproz> wait what
[21:30] <Ruben_> Darkside: A friend of me tells me that this project can decode it using mk2a: https://github.com/rs1729/RS?files=1
[21:31] <Ruben_> I am decoding using Sonde Monitor with m2k2 mode
[21:31] <Viproz> I'm decoding the recording sent with trimble
[21:31] <Darkside> Ruben_: dfm wrote that repository :_)
[21:31] <Viproz> Ruben_, it's a M10 Trimble, already supported
[21:31] <dfm> mk2a is sippican, before lms6
[21:31] <dfm> and now lms6-1680 mhz.
[21:32] <Viproz> { "sub_type": "Trimble", "frame": 1548200892, "id": "M10-T-607-2-14087", "dxlid": "ME100079", "datetime": "2019-01-22T23:48:12Z", "satelites": 9, "lat": 37.57155, "lon": -0.95397, "alt": 8888.36, "vel_h": 50.13942, "heading": 170.69736, "vel_v": 0.90, "temp": -47.0, "battery": 5.26, "crc": 1 }
[21:32] <Darkside> haha
[21:32] <Ruben_> Is it already supported?
[21:32] <Darkside> yup
[21:32] <Viproz> it's old, 2016 but still Trimble
[21:33] <dfm> what is the raw frame?
[21:33] <dfm> with the m10-decoder you can output also m2k2 raw data.
[21:33] <Viproz> 649F20 CA 0142 D6D1 0168 0F685600 1AB75E69 FF525DB7 0087DA99 000001180912 07F5 0A141A101B15081207000000 08741200 A87D09 30DA08 FD0008220000 01 17AC D60A D40A 1B03 38 330A 0100 0700 1300 0000000000 E50F1900 730D 0400 021C67F72F AD 8D 4F [OK]
[21:34] <dfm> m2k2 starts with 648f or 6447, 648f is like 649f for m10
[21:34] <dfm> 9f is m10
[21:34] <Ruben_> great then...
[21:34] <Ruben_> I will test it tomorrow.
[21:34] <Viproz> m2k2 is the same header and everything ?
[21:34] <Ruben_> Thank's all for your help.
[21:34] <Viproz> Yeah good news, you can already setup a reciever :)
[21:35] <dfm> 648f2309800000001abfb333331cbfb333331d8000000008bfcccccc0abfb333330fbfb3333312bfe6666600000000000000c36209bf0b0900000000000001df9ad60ad70a5300394a0b0000040000000000000000e50f1400400a000002167a8728a22c23 # 2c23 [OK]
[21:35] <Viproz> No worries !
[21:35] <dfm> from radiosonde.eu
[21:35] <Ruben_> perfect.... thank's again.
[21:35] TheGuv (~yaaic@a85-138-211-60.cpe.netcabo.pt) joined #highaltitude.
[21:36] <Viproz> dfm, if we don't have anyone sending any might not be worth the time even though it's the same header
[21:36] <Darkside> dfm: i got some samples of the 1680 MHz RS92-NGP, its just RS92 telemetry, but with a wider bandwidth
[21:37] <dfm> yes, someone told me, only the transmitter/mixer is different, 1680mhz.
[21:38] <Darkside> i have a few samples - they decode fine with the rs92dm_dft, jut with a wider FM filter bandwidth
[21:38] <Darkside> so i guess we coudl have a 1680 mhz mode, which just widens out the bandwidths a little
[21:39] <Darkside> that said im not sure how people will go with auto_rx at 1680 MHz!
[21:39] <Darkside> they would need a very good omni and preamp
[21:40] <Ruben_> One more question: Using crontab.... i must use after a killall to finish the process???
[21:40] <dfm> never received a radiosonde on 1680mhz.
[21:41] <Darkside> Ruben_: i suggest you use the systemd approach
[21:41] <Darkside> much more reliable
[21:41] <dfm> i hear, us is moving away, so canada, and then, sometimes in poland i think, seen on NOTAMs.
[21:42] <Viproz> moving away from what ?
[21:42] <dfm> darkside, when you want to lower the threshold and get possible false positives.
[21:43] <dfm> when you have the results of a certain interval, lets say 5 seconds, you could choice the one you think is the most likely.
[21:43] <Darkside> dfm: i really only lowered the thresholds for the RS41 and RS92, the others are pretty siilar to what you set them as
[21:43] <dfm> add -c for that-
[21:43] <Darkside> the threshold is et high enough above the correlation noise to avoid false positives
[21:43] <dfm> yes, for rs92 i also think it is ok. only m10 and imet are dangerous.
[21:43] <Darkside> yeah
[21:43] <Darkside> i have left those high
[21:44] <Darkside> m10 is the worst one
[21:44] <Darkside> imet i havent really considered yet
[21:44] <Darkside> but will get there
[21:44] <Darkside> thos are still on their defaults
[21:45] <dfm> i have the imet1ab included that was flying in belgium until last year.
[21:45] <dfm> but it makes some trouble.
[21:45] <dfm> and i don't know if it has to be included.
[21:45] <dfm> like c34/c50, could be #define-excluded for auto-rx.
[21:46] <dfm> the decoding is not so good anyway.
[21:46] <dfm> and i think the imet4 will take over.
[21:46] <Darkside> dfm: yeah i already excluded c34
[21:46] <Viproz> dfm, that's what I was wondering yesterday, if a RS is falsely detected as a M10 once is it likely to be detected a second time as M10 ? the -t 5 option seems really good for our application, don't need to kill anything anymore either :)
[21:47] <Darkside> Viproz: go look at the plots i produced
[21:47] <Darkside> it shows coreelation score with SNR
[21:47] <dfm> try -c -t 5, then you get more results, see if the false m10 appears twice.
[21:47] <Darkside> you can see that for sondes like the RS41, as the SNR increases, the M10 score also increases
[21:47] <Viproz> yeah I know but not how many detects, if it's just a lucky game then detecting multiple times solves it
[21:48] <Darkside> https://github.com/projecthorus/radiosonde_auto_rx/blob/testing/auto_rx/test/notes/2019-03-01_dft_detect_optimization.md
[21:48] <dfm> the scores should be weighted though, but if m10 with 0.74 and imet with 0.82, and maybe 3/5, then i would go with imet.
[21:50] <Viproz> M10 should be weighed pretty low then cause when it's a M10 there is never a shadow of a doubt
[21:50] <dfm> i tested reading the first 2 bytes for m10. so the type could be detected. on the other hand, if the signal is weak, these bytes cuold be corrupted.
[21:51] <Darkside> https://camo.githubusercontent.com/e9a51acdc6a85bb7a7afb4876c8dc91b7fd2cc35/687474703a2f2f7266686561642e6e65742f736f6e6465732f706c6f74732f6466745f6465746563745f7468726573686f6c64732f6d31305f6e65777468726573682e706e67
[21:51] <Viproz> since they are all so similar might as well detect it in the code
[21:51] <Darkside> urgh
[21:51] <Darkside> https://camo.githubusercontent.com/e9a51acdc6a85bb7a7afb4876c8dc91b7fd2cc35/687474703a2f2f7266686561642e6e65742f736f6e6465732f706c6f74732f6466745f6465746563745f7468726573686f6c64732f6d31305f6e65777468726573682e706e67
[21:51] <Darkside> ffs even worse
[21:51] <Darkside> dammit github
[21:51] <dfm> with "weight" i mean, the correlation score depends a bit on the length and pulse shape,
[21:51] <Darkside> anyway... M10 is detected even at very low SNR
[21:52] <Darkside> much lower than is decodable reliably
[21:52] <Darkside> so its threshold could be bumped up a little bit, which would reduce mis-detections
[21:52] pb1dft (~pb1dft@ampache/staff/pb1dft) left irc: Quit: Uh Oh
[21:52] <Viproz> oh I thought you meant when detecting multiple times, if you have one time M10 and another RS41, we know it's a RS41 no matter what value it was at (well above a reasonable level)
[21:53] pb1dft (~pb1dft@ampache/staff/pb1dft) joined #highaltitude.
[21:53] <dfm> the false positives i found where in imet-recordings, though imet1ab 30khz wide-fm, very digital pulses...
[21:53] <Viproz> Darkside, https://github.com/rs1729/RS/commit/b67a86d31ab280b711daafe43b66868084278891 I'm talking about this
[21:54] larsan (v3aKmFbYre@norma.uberspace.de) left irc: Ping timeout: 272 seconds
[21:54] larsan (yqozxSrmrq@norma.uberspace.de) joined #highaltitude.
[21:54] <dfm> yes, this way you get up to 5 results per 5 seconds, mybe some more or less, if to types are detected.
[21:54] <Darkside> oh
[21:55] <Darkside> ugh, need to head to work
[21:55] <Darkside> cya
[21:55] <dfm> then you decide, which score is the best
[21:55] <Viproz> see you ^^
[21:55] <Viproz> dfm, can two types be detected during the same frame ?
[21:56] <dfm> in principle, yes.
[21:57] <Darkside> Viproz: with FM demodulation in use, the FM Capture effect will lock you onto a single signal
[21:57] <Darkside> so if theres 2 sondes on the same frequency, you will either detect one of them or nothing
[21:57] <dfm> the K-samples-window is moved forward, and then it loops over the different waveform to match.
[21:57] <Viproz> Oh, we could add weight to say something like if you have M10 at 0.75 and RS41 at 0.7 you take the RS41 even though the M10 is higher
[21:57] <Darkside> Viproz: my testing doesnt show that occuring
[21:58] <Viproz> Darkside, no no I meant to detect the headers, one false positive and one right x)
[21:58] <dfm> what i mean, it could be a second sonde type detected as false positive.
[21:59] <Darkside> Viproz: the point of the testing i did was to see, for a set of samples of a parcitular sonde type, waht the score for the *other* types was
[21:59] <Darkside> that sets a minimum threshold for all the types
[21:59] <dfm> in one window you get 6 different results, only the one over threshold is shown, but there could be more then one result above.
[21:59] <Viproz> yeah right, I had the answer in front of my eyes
[21:59] <Darkside> yes, you can tweak it a bit, but at the moment we detect everything way below where we can even decode them reliably
[22:00] <Viproz> Darkside, even at 22kHz ?
[22:00] <Darkside> yep
[22:00] <Viproz> all good then :)
[22:00] <dfm> i run through several hundred (or more) recordings and compare results, sometimes the differ because of false positives, in noise when scores are similar.
[22:01] <dfm> although mostly for these WFM-recordings of imet1ab.
[22:01] <dfm> so if imet1ab is turned off, this problem would disappear.
[22:03] <Darkside> thats the very wide one?
[22:03] <dfm> after all, it is maybe a handful of questionable results in, in 3700 recordings...
[22:03] <Darkside> i think we can limit support to just the narrowe bandwidth AFSK imets (imet4)
[22:03] FireFighter (~firefight@2601:44:4200:ab4f:2845:e7ec:b22f:c409) left irc: Quit: Leaving
[22:04] <dfm> and 1-2 results in 137mhz satellite... ;)
[22:04] <dfm> imet4 like imet1rs have 2200mhz tones, this is checked, more reliable.
[22:05] <Darkside> so i have a box iabelled imet1ab, which has the same teleemtry as an imet4
[22:05] <Darkside> it has a sticker o it saying '6 khz bandwidth'
[22:05] <dfm> very wide 60khz is imet1rs, imet1ab was around 30khz. i think both are replaced by imet4
[22:05] <dfm> yes, you wrote this, strange.
[22:06] <Darkside> yeah i think we just support imet4 then
[22:06] <Darkside> bugger the rest
[22:06] <Darkside> too hard
[22:06] michal_f_home (~mfratczak@91-145-163-242.internetia.net.pl) joined #highaltitude.
[22:07] <Darkside> right, gtg
[22:07] <Darkside> cya
[22:07] <dfm> and in the future the probability to receive an imet1ab or m2k2 will be lower and lower.
[22:08] <Viproz> m2k2 is probably nil already
[22:08] <dfm> so, the imet-stickers on the envelope, i don't know, and the documentation on there website said bell202 only, but the imet1ab i found here was different.
[22:08] <Viproz> Gtop I'm guessing are gone too
[22:08] <dfm> that strange too.
[22:09] <dfm> it is okay to test from ury.
[22:09] <dfm> but when they launched from trappes, i thought this would be the gps-replacement.
[22:09] cacoethes (~sms@2a00:23c5:eb0f:2300:ad4a:e11f:d5db:4f25) left irc: Ping timeout: 258 seconds
[22:10] <dfm> so maybe it was not a good idea to change the gps-data, all the stations would have to update.
[22:10] <Viproz> maybe they thought it too but people complainted that they had to update their ground equipment to decode them
[22:10] <Viproz> complained*
[22:10] <dfm> maybe they have a replacement solution that is compatible.
[22:11] <dfm> anyway, what about m20?
[22:11] cacoethes (~sms@89.238.132.37) joined #highaltitude.
[22:11] <dfm> thats what i mean.
[22:11] <Viproz> I think I read somwhere that the GPS chip was using Galileo too, the sat IDs that are sent should be different than before if that's true
[22:12] <Viproz> I have never heard any
[22:12] <dfm> sometimes even if the old format has some issues, if you change, someone will complain...
[22:12] <dfm> or GLONASS
[22:12] <Viproz> do we have a recording already of a m20 ?
[22:12] <dfm> i think the new gps chips have all gnss included anyway.
[22:14] <dfm> for accuracy, position is not so important, velocity was accurate enough, only altitude could be interesing, when pressure is calculated through the other sensor/gps data.
[22:15] <dfm> maybe, so as long it is not in regulare operation, it can change anyway.
[22:16] <Viproz> the new chip are going to be more accurate anyway arn't they ?
[22:16] <dfm> well, there are limits for a single receiver.
[22:17] <dfm> hm... i have seen something called m18.
[22:17] <dfm> i thought i have seen m20 as well.
[22:18] <dfm> it is on there website quite a while.
[22:19] <dfm> and the m10 was decoded like m10gtop
[22:20] <dfm> prototype.
[22:20] <Viproz> I'll ask F5MVO to keep an eye out, I'm on a spammy maillist, if Ury send some m20 test sonde I think we should be able to know about it
[22:20] <Viproz> the M10 or M20 ?
[22:21] <dfm> Metemodem and Graw change alot, Vaisala is moer consistent.
[22:21] <dfm> oh, the "M18", sorry.
[22:22] <Viproz> Oh okay, weird
[22:22] <dfm> i think there was alot more activity aounrd m20 1-2 years ago.
[22:23] <Viproz> Actually I'm in Toulouse and apparently that's where Meteofrance does its tests to compare RS to one another, maybe I'll rx something at some point
[22:30] <dfm> ok, bye
[22:30] dfm (59cc9b60@gateway/web/freenode/ip.89.204.155.96) left irc:
[22:41] Viproz (~Viproz@unaffiliated/viproz) left irc: Ping timeout: 250 seconds
[22:50] _Ded_ (53f06f54@gateway/web/freenode/ip.83.240.111.84) joined #highaltitude.
[22:52] cacoethes (~sms@89.238.132.37) left irc: Ping timeout: 250 seconds
[22:54] _Ded_ (53f06f54@gateway/web/freenode/ip.83.240.111.84) left irc: Ping timeout: 256 seconds
[22:57] Ruben_ (5478ac8b@gateway/web/freenode/ip.84.120.172.139) left irc: Ping timeout: 256 seconds
[23:00] Kodar (~Kodar@93-139-223-230.adsl.net.t-com.hr) left irc: Read error: Connection reset by peer
[23:06] TheGuv (~yaaic@a85-138-211-60.cpe.netcabo.pt) left irc: Quit: Yaaic - Yet another Android IRC client - http://www.yaaic.org
[23:07] zabow (~zab@host63-84-dynamic.250-95-r.retail.telecomitalia.it) left irc: Ping timeout: 244 seconds
[23:07] happysat (~katpoep@s5594c83f.adsl.online.nl) left irc: Remote host closed the connection
[23:09] michal_f_home (~mfratczak@91-145-163-242.internetia.net.pl) left irc: Quit: Leaving
[23:11] LordQuorra (~Zerarf@2001:8a0:67ea:4a01:70c3:2729:3081:7609) joined #highaltitude.
[23:19] happysat (~katpoep@s5594c83f.adsl.online.nl) joined #highaltitude.
[23:21] LordQuorra (~Zerarf@2001:8a0:67ea:4a01:70c3:2729:3081:7609) left irc: Remote host closed the connection
[23:30] zabow (~zab@host163-82-dynamic.46-79-r.retail.telecomitalia.it) joined #highaltitude.
[00:00] --- Tue Mar 5 2019