[00:11] Viproz (~Viproz@unaffiliated/viproz) joined #highaltitude.
[00:29] Hoogvlieger (~Hoogvlieg@541A8CEB.cm-5-3c.dynamic.ziggo.nl) left irc: Quit: Leaving
[00:30] Viproz (~Viproz@unaffiliated/viproz) left irc: Ping timeout: 252 seconds
[01:08] happysat (~katpoep@s5594c83f.adsl.online.nl) left irc: Quit: Hunger-the-inner-diva
[01:10] happysat (~katpoep@s5594c83f.adsl.online.nl) joined #highaltitude.
[01:42] bertrik (~bertrik@rockbox/developer/bertrik) left irc: Quit: "This incident will be reported"
[01:45] <SpacenearUS> New vehicle on the map: 03KJ6YXG-11 - 12https://tracker.habhub.org/#!qm=All&q=KJ6YXG-11
[02:08] Laurenceb_12 (~laurence@host86-130-23-101.range86-130.btcentralplus.com) left irc: Ping timeout: 250 seconds
[03:03] d33p3y35 (~d33p3y35@91-145-163-242.internetia.net.pl) left irc: Remote host closed the connection
[03:03] d33p3y35 (~d33p3y35@91-145-163-242.internetia.net.pl) joined #highaltitude.
[03:12] chris_99 (uid26561@gateway/web/irccloud.com/x-wurwmuztajtqutrr) left irc: Quit: Connection closed for inactivity
[03:15] toofat (~john@unaffiliated/toofat) left irc: Quit: Leaving
[03:55] tweetBot (~nodebot@philcrump.co.uk) left irc: Remote host closed the connection
[03:55] tweetBot (~nodebot@philcrump.co.uk) joined #highaltitude.
[05:19] day__ (~Unknown@unaffiliated/day) joined #highaltitude.
[05:22] day (~Unknown@unaffiliated/day) left irc: Ping timeout: 246 seconds
[05:22] Nick change: day__ -> day
[07:25] Kodar (~Kodar@93-139-173-245.adsl.net.t-com.hr) joined #highaltitude.
[07:48] <SA6BSS-Mike|2> SAQ on ai 17.2
[08:42] bertrik (~bertrik@rockbox/developer/bertrik) joined #highaltitude.
[08:48] <SpacenearUS> New vehicle on the map: 03KJ6YXA-11 - 12https://tracker.habhub.org/#!qm=All&q=KJ6YXA-11
[09:57] <SpacenearUS> New position from 03BSS18 after 03a day silence - 12https://tracker.habhub.org/#!qm=All&q=BSS18
[10:14] rubdos (~rubdos@ptr-1uzevqefjgxdm5wv65h.18120a2.ip6.access.telenet.be) joined #highaltitude.
[10:16] <SpacenearUS> New position from 03IU2EFA-12 after 032 days silence - 12https://tracker.habhub.org/#!qm=All&q=IU2EFA-12
[10:24] Viproz (~Viproz@unaffiliated/viproz) joined #highaltitude.
[10:26] Hoogvlieger (~Hoogvlieg@541A8CEB.cm-5-3c.dynamic.ziggo.nl) joined #highaltitude.
[10:27] <SpacenearUS> New vehicle on the map: 03KJ6YXK-11 - 12https://tracker.habhub.org/#!qm=All&q=KJ6YXK-11
[10:29] xfce1 (~anony@cpe-85-10-26-226.dynamic.amis.net) left irc: Read error: Connection reset by peer
[10:36] <Viproz> Darkside, Hey, you're there ?
[10:38] <Darkside> yup
[10:39] <Darkside> not for long tho
[10:42] <Viproz> I found a way to home in to the actualk frequency, when the frequency is offset from the middle it indicates by how much the center is off so I might implement it
[10:42] <Darkside> the issue is it needs to work with all sonde types...
[10:42] <Viproz> but my question is is there a ting to get all of the data collected about one sonde so far on the web interface ?
[10:42] <Darkside> no, only the latest data and the track
[10:42] <Darkside> all the data is saved into log files however
[10:43] <Viproz> I can just make it a M10 thing, I wanted to add a center_frequency on the json outputed and use it in the code, you need to remove the highpass filter for it to work so the code needs to be different
[10:45] <Darkside> hrm
[10:45] <Darkside> that will require some significant changes imo
[10:45] <Darkside> as that needs tas you cant change the receive frequency 'live'
[10:46] <Darkside> it would be best if the frequency was found at the scan stage
[10:46] <Viproz> might be able to do it with the scan, is this something that could improve other sondes detection or only M10s ?
[10:46] <Darkside> we dont seem sto have issues with the RS92/RS41 and DFM sondes
[10:46] <Darkside> just quantizing the rx frequency to 10 khz steps works fine
[10:47] <Darkside> for M10 i would have thought quantizing to 100 Khz steps would be a suitable compromise
[10:47] <Darkside> however if you can detect the offset somehow in rs_detect, and feed that back into the receiver, that could be an improvement
[10:49] <Viproz> my issue probably comes from the fact that I live in a high noise environment so using a higher bandwidth to accommodate for frequency offset (up to 3kHz) is a bad compromise
[10:49] <Viproz> and manually tuning in the center gives better results
[10:49] <Darkside> if thats done in the detect stage it might be ok
[10:49] <Darkside> as the packet preamble is detected with a much lower SNR than is required for a valid decode
[10:50] <Viproz> do you have IQ files from rtl_sdr that I could use to test on other RS ?
[10:51] <Darkside> unfortuantely no
[10:51] <Darkside> plus i'm away from home at the moment
[10:51] <Darkside> also you wouldnt be able to feed those into rtl_power :-)
[10:52] <Viproz> okay no worries, it is the 24th of December after all ^^
[10:52] <Darkside> hmm, one thought for the scan step might be to do a second pass over the rtl_power output, looking for peaks spaced a paritcular distance apart
[10:53] <Viproz> would work for a scan but not for whitelisted frequencies
[10:54] <Darkside> well for whitelisting the assumption is you know what the frequency is anyway
[10:54] <Darkside> and yes, that might involve a compromise in reception if the sonde drifts noticably
[10:54] Nick change: pe2bz__ -> PE2BZ
[10:55] <Darkside> again, hasnt been a problem with the Vaisala and DFM sondes.... its sounding like we're going to need to add a 'M10' mode, where we enable all these mods to enable reliable reception of M10 sondes
[10:55] <Darkside> which is a bit of a pain
[10:56] <Viproz> maybe I'm just optimizing too much too actually
[10:56] <Darkside> what woudl be good is to get it to a working state (perhaps just trying with 100 khz quantization for now) and running it for a while
[10:56] <Darkside> see how it goes
[10:57] <Darkside> *then* optimize if required.
[10:57] <Viproz> yeah can even do 200kHz, you can't program them to anything else
[10:58] <Darkside> cool
[10:58] <Darkside> but yeah, i think that would be a good baseline point
[10:58] <Viproz> indeed pushing something to master that works for people and then see where it goes
[10:59] <Darkside> then we can integrate it with a M10-enable flag in the config file for now, which just overrides the quantization and allows M10s to be detected
[10:59] <Darkside> as a quantization of 10 khz may cause issues with M10s
[10:59] <Darkside> but it would be worth seeing what happened
[10:59] <Darkside> what happens*
[11:00] <Viproz> maybe the scan will detect a M10 and in that case you just home in to the nearest 200kHz
[11:00] <Darkside> yep perhaps
[11:00] <Darkside> however - the detection step occurs after quantization occurs
[11:00] <Darkside> so im wondering if its going to detect a M10 if its tuned up to 10 khz off frequency... (probably not)
[11:01] YO9GJX (~YO9GJX@ left irc: Remote host closed the connection
[11:01] <Viproz> let me try
[11:04] <Viproz> no not a a bandwidth of 22k
[11:05] <Darkside> mm thought as much
[11:06] <Darkside> if we increase the bandwidth then the detection performance will decrease due to the added noise
[11:06] <Darkside> definitely needs the quantization to 100 khz *before* the detection step
[11:06] <Darkside> itll be interesting to look at the list on radiosondy.info and see how many are not on 100 khz steps as it is..
[11:19] <Darkside> Viproz: https://radiosondy.info/sonde.php?sondenumber=ME681398
[11:19] <Darkside> not sure how they are coming up with that callsign
[11:20] <Darkside> i guess one of the important things here is that the generated callsign, sequence number, and all other data have to be generated the same across all receivers
[11:20] <Darkside> would be nice if were compatible with... whatever the hell that person is receiving
[11:20] <Darkside> what they are receiving with, rather
[11:22] <Darkside> ahh it looks like dxlAPRS does M10s..
[11:25] <Darkside> hmm, but im not sure thats whats producing those packets though..
[11:35] <Viproz> I really don't understand where ME comes from
[11:40] <Viproz> I can't find a way to contact YT1NIV, maybe I'm not looking on the right websites
[11:41] <Darkside> i cant figure out what dxlAPRS is doing either
[11:42] <Darkside> https://github.com/oe5hpm/dxlAPRS/blob/master/src/sondemod.c#L3301
[11:42] <Darkside> at least i try and comment my python code well...
[11:43] <Viproz> looks like it's M10 ptu, gtop doesn't give a week value
[11:44] <Darkside> realistically we only need HH:MM:SS to upload to habitat or aprs..
[11:45] <Viproz> both give a way to get a complete timestamp, they just work differently
[11:46] <Darkside> ok
[11:47] <Darkside> right bedtime for me
[11:47] <Darkside> gnight
[11:50] <Viproz> okay, gn
[12:47] chris_99 (uid26561@gateway/web/irccloud.com/x-fhbcsvbjmxctulfj) joined #highaltitude.
[13:33] Hoogvlieger (~Hoogvlieg@541A8CEB.cm-5-3c.dynamic.ziggo.nl) left irc: Quit: Leaving
[15:17] Viproz (~Viproz@unaffiliated/viproz) left irc: Ping timeout: 252 seconds
[15:39] tibs02 (~tibs01@tibs01.steve-gibbs.co.uk) joined #highaltitude.
[15:39] tibs01 (tibs01@tibs01.steve-gibbs.co.uk) left irc: Ping timeout: 250 seconds
[16:08] Kodar (~Kodar@93-139-173-245.adsl.net.t-com.hr) left irc:
[16:34] xfce (~anony@cpe-85-10-26-226.dynamic.amis.net) joined #highaltitude.
[16:55] YO9GJX (~YO9GJX@ joined #highaltitude.
[17:28] gb73d (gb73d@88-106-143-142.dynamic.dsl.as9105.com) joined #highaltitude.
[17:32] Viproz (~Viproz@unaffiliated/viproz) joined #highaltitude.
[17:43] bertrik (~bertrik@rockbox/developer/bertrik) left irc: Ping timeout: 268 seconds
[17:53] Laurenceb_12 (~laurence@host86-130-23-101.range86-130.btcentralplus.com) joined #highaltitude.
[18:11] Steffanx (~steffanx@unaffiliated/steffanx) left irc: Quit: Meh
[18:12] Steffanx (~steffanx@unaffiliated/steffanx) joined #highaltitude.
[18:24] bertrik (~bertrik@rockbox/developer/bertrik) joined #highaltitude.
[18:38] Hiena (~boreger@81-93-195-181.ipv4.datatrans.hu) joined #highaltitude.
[19:08] <SpacenearUS> New position from 034Z7HKA-11 after 037 days silence - 12https://tracker.habhub.org/#!qm=All&q=4Z7HKA-11
[19:12] bertrik (~bertrik@rockbox/developer/bertrik) left irc: Ping timeout: 268 seconds
[19:29] bertrik (~bertrik@rockbox/developer/bertrik) joined #highaltitude.
[20:09] <SpacenearUS> New position from 03U3B-24 after 032 days silence - 12https://tracker.habhub.org/#!qm=All&q=U3B-24
[20:13] bertrik (~bertrik@rockbox/developer/bertrik) left irc: Ping timeout: 244 seconds
[20:15] happysat (~katpoep@s5594c83f.adsl.online.nl) left irc: Quit: Hunger-the-inner-diva
[20:34] happysat (~katpoep@s5594c83f.adsl.online.nl) joined #highaltitude.
[20:51] bertrik (~bertrik@rockbox/developer/bertrik) joined #highaltitude.
[20:54] bertrik (~bertrik@rockbox/developer/bertrik) left irc: Read error: Connection reset by peer
[20:58] bertrik (~bertrik@rockbox/developer/bertrik) joined #highaltitude.
[21:02] gb73d (gb73d@88-106-143-142.dynamic.dsl.as9105.com) left irc:
[21:14] sumie-dh_ (~sumie-dh@ joined #highaltitude.
[21:18] sumie-dh (~sumie-dh@ left irc: Ping timeout: 250 seconds
[21:23] bertrik (~bertrik@rockbox/developer/bertrik) left irc: Quit: Lost terminal
[21:26] bertrik (~bertrik@rockbox/developer/bertrik) joined #highaltitude.
[21:35] kristianpaul (~kristianp@unaffiliated/kristianpaul) left irc: Quit: Lost terminal
[21:51] bertrik (~bertrik@rockbox/developer/bertrik) left irc: Ping timeout: 250 seconds
[21:57] bertrik (~bertrik@rockbox/developer/bertrik) joined #highaltitude.
[23:03] <Darkside> Viproz: might be worth doing the serial number truncation stuff in the C++ code
[23:04] <Viproz> I would really like to be sure that the first is hardware and to know what the second one is before removing informations tho
[23:04] <Darkside> the Habitat upload code just passes the serial number straight through as the callsign, so would be better to not use the long one for that
[23:04] <Darkside> ok
[23:05] <Viproz> oe3jtb might have spotted an issue of using a higher bandwidth for the scan
[23:06] <Darkside> false detections?
[23:07] Hiena (~boreger@81-93-195-181.ipv4.datatrans.hu) left irc: Quit: Konversation terminated!
[23:07] <Darkside> i've had my station at home running at 22 khz bw for scanning fo ra while
[23:07] <Darkside> for a while*
[23:07] <Darkside> and it seems ok...
[23:07] <Viproz> yeah he says that it's detecting what should be a RS41 as a M10, I asked for both frequencies to see if they are pretty close or not
[23:08] <Darkside> hmm
[23:08] <Darkside> anyway, bbl...
[23:32] chris_99 (uid26561@gateway/web/irccloud.com/x-fhbcsvbjmxctulfj) left irc:
[23:52] Viproz (~Viproz@unaffiliated/viproz) left irc: Ping timeout: 252 seconds
[23:59] suep_ (uid317081@gateway/web/irccloud.com/x-oddmdjdcypfrfmjs) joined #highaltitude.
[00:00] --- Tue Dec 25 2018