highaltitude.log.20170717

[00:04] stryx` (~stryx@unaffiliated/stryx/x-3871776) left irc: Ping timeout: 246 seconds
[00:05] stryx` (~stryx@unaffiliated/stryx/x-3871776) joined #highaltitude.
[00:45] Laurenceb_ (~laurence@host86-154-54-179.range86-154.btcentralplus.com) joined #highaltitude.
[00:49] DL7AD (~sven@p2003004603140A00699C6774520D4FEA.dip0.t-ipconnect.de) left irc: Ping timeout: 276 seconds
[01:02] rjsnyder (~rjsnyder@p20030080AD1E19000545E7C2B64B6ACD.dip0.t-ipconnect.de) joined #highaltitude.
[01:03] DL7AD (~sven@p200300460307A400C11421CD632D6C54.dip0.t-ipconnect.de) joined #highaltitude.
[01:07] rjsnyder (~rjsnyder@p20030080AD1E19000545E7C2B64B6ACD.dip0.t-ipconnect.de) left irc: Ping timeout: 276 seconds
[01:21] kc2uez (~SKA0ut@static-74-42-252-20.br1.glvv.ny.frontiernet.net) left irc: Ping timeout: 276 seconds
[01:22] kc2uez (~SKA0ut@static-74-42-252-20.br1.glvv.ny.frontiernet.net) joined #highaltitude.
[01:45] Laurenceb_ (~laurence@host86-154-54-179.range86-154.btcentralplus.com) left irc: Ping timeout: 260 seconds
[03:03] rjsnyder (~rjsnyder@p20030080AD1E1900793FF028484FEC8F.dip0.t-ipconnect.de) joined #highaltitude.
[03:07] day_ (~Flutterba@unaffiliated/day) joined #highaltitude.
[03:07] rjsnyder (~rjsnyder@p20030080AD1E1900793FF028484FEC8F.dip0.t-ipconnect.de) left irc: Ping timeout: 246 seconds
[03:10] daey (~Flutterba@unaffiliated/day) left irc: Ping timeout: 260 seconds
[03:10] Nick change: day_ -> daey
[03:27] day_ (~Flutterba@unaffiliated/day) joined #highaltitude.
[03:30] daey (~Flutterba@unaffiliated/day) left irc: Ping timeout: 240 seconds
[03:30] Nick change: day_ -> daey
[03:43] jmusac (~joefly@lns01-0300.dsl.iskon.hr) joined #highaltitude.
[03:45] joefly (~joefly@lns01-0300.dsl.iskon.hr) left irc: Ping timeout: 260 seconds
[03:55] tweetBot (~nodebot@philcrump.co.uk) left irc: Remote host closed the connection
[03:55] tweetBot (~nodebot@philcrump.co.uk) joined #highaltitude.
[04:03] jmusac (~joefly@lns01-0300.dsl.iskon.hr) left irc: Ping timeout: 240 seconds
[04:14] YO9GJX (~YO9GJX@109.99.23.22) left irc: Remote host closed the connection
[04:16] day_ (~Flutterba@unaffiliated/day) joined #highaltitude.
[04:19] daey (~Flutterba@unaffiliated/day) left irc: Ping timeout: 240 seconds
[04:19] rjsnyder (~rjsnyder@p5B297428.dip0.t-ipconnect.de) joined #highaltitude.
[04:19] Nick change: day_ -> daey
[04:56] joefly (~joefly@lns01-0300.dsl.iskon.hr) joined #highaltitude.
[04:58] rjsnyder (~rjsnyder@p5B297428.dip0.t-ipconnect.de) left irc: Remote host closed the connection
[06:20] number10 (d42c14ce@gateway/web/freenode/ip.212.44.20.206) joined #highaltitude.
[06:36] LeoBodnar (~LeoBodnar@79-76-228-193.dynamic.dsl.as9105.com) left irc: Quit: LeoBodnar
[06:48] LeoBodnar (~LeoBodnar@host86-158-94-78.range86-158.btcentralplus.com) joined #highaltitude.
[06:58] rjsnyder (~rjsnyder@p20030080AD1E19002D021B110D156561.dip0.t-ipconnect.de) joined #highaltitude.
[07:02] rjsnyder (~rjsnyder@p20030080AD1E19002D021B110D156561.dip0.t-ipconnect.de) left irc: Ping timeout: 240 seconds
[07:04] BrainDamage (~BrainDama@unaffiliated/braindamage) left irc: Ping timeout: 240 seconds
[07:06] BrainDamage (~BrainDama@unaffiliated/braindamage) joined #highaltitude.
[07:22] number10 (d42c14ce@gateway/web/freenode/ip.212.44.20.206) left irc: Quit: Page closed
[07:25] stryx` (~stryx@unaffiliated/stryx/x-3871776) left irc: Ping timeout: 240 seconds
[07:26] stryx` (~stryx@unaffiliated/stryx/x-3871776) joined #highaltitude.
[07:37] costyn (~costyn@s55946021.adsl.online.nl) joined #highaltitude.
[07:39] number10 (d42c14ce@gateway/web/freenode/ip.212.44.20.206) joined #highaltitude.
[07:52] shortstheory (~nic@106.200.204.103) joined #highaltitude.
[08:06] shortstheory (~nic@106.200.204.103) left irc: Quit: Leaving
[08:18] michal_f (~michal_f@84-10-62-166.static.chello.pl) left irc: Ping timeout: 255 seconds
[08:19] LazyLeopard (~irc-clien@chocky.lazyleopard.org.uk) joined #highaltitude.
[08:19] LazyL-M0LEP (~irc-clien@chocky.lazyleopard.org.uk) joined #highaltitude.
[08:20] LazyL-M0LEP (~irc-clien@chocky.lazyleopard.org.uk) left irc: Client Quit
[08:27] michal_f (~michal_f@84-10-62-166.static.chello.pl) joined #highaltitude.
[08:36] KT5TK1 (~thomas@i577B918A.versanet.de) joined #highaltitude.
[08:36] <SpacenearUS> New vehicle on the map: 03XSky3 - 12https://tracker.habhub.org/#!qm=All&q=XSky3
[08:37] KT5TK (~thomas@i577B9307.versanet.de) left irc: Ping timeout: 246 seconds
[08:41] BrainDamage (~BrainDama@unaffiliated/braindamage) left irc: Ping timeout: 248 seconds
[08:43] BrainDamage (~BrainDama@unaffiliated/braindamage) joined #highaltitude.
[08:50] priyesh (~priyesh@unaffiliated/priyesh) left irc: Ping timeout: 268 seconds
[08:57] priyesh (~priyesh@unaffiliated/priyesh) joined #highaltitude.
[08:59] rjsnyder (~rjsnyder@p20030080AD1E19001D74AE66460D8AA8.dip0.t-ipconnect.de) joined #highaltitude.
[09:04] costyn (~costyn@s55946021.adsl.online.nl) left irc: Quit: costyn
[09:04] rjsnyder (~rjsnyder@p20030080AD1E19001D74AE66460D8AA8.dip0.t-ipconnect.de) left irc: Ping timeout: 276 seconds
[09:21] <SpacenearUS> New position from 03KD2EAT-14 after 0310 hours silence - 12https://tracker.habhub.org/#!qm=All&q=KD2EAT-14
[09:43] heathkid (~heathkid@unaffiliated/heathkid) left irc: Read error: Connection reset by peer
[09:43] heathkid (~heathkid@unaffiliated/heathkid) joined #highaltitude.
[09:54] andycamb (~Thunderbi@global-5-143.nat-2.net.cam.ac.uk) joined #highaltitude.
[09:57] SushiKenBrown (~quassel@cmr-208-124-174-194.cr.net.cable.rogers.com) joined #highaltitude.
[09:59] SushiKenBrown_ (~quassel@cmr-208-124-174-194.cr.net.cable.rogers.com) left irc: Ping timeout: 268 seconds
[10:06] <SpacenearUS> New position from 03HIRFW-6 after 0312 hours silence - 12https://tracker.habhub.org/#!qm=All&q=HIRFW-6
[10:13] costyn (~costyn@s55946021.adsl.online.nl) joined #highaltitude.
[10:23] BARC (3e1e8fda@gateway/web/freenode/ip.62.30.143.218) joined #highaltitude.
[10:23] <BARC> Hey, Can I speak to someone who can possibly remove my uploaded images from ssdv live images?
[10:29] <BARC> It's really urgent.
[10:30] <dbrooke> fsphil: ^^
[10:34] <fsphil> hi BARC, sure one sec. what's the callsign
[10:35] <BARC> LORA4 :)
[10:37] <fsphil> they'll disappear shortly
[10:38] <BARC> Thank you so much :)
[10:39] <BARC> You guys have a nice day
[10:40] BARC (3e1e8fda@gateway/web/freenode/ip.62.30.143.218) left irc: Quit: Page closed
[10:54] <SpacenearUS> New position from 03BIDOOF after 033 days silence - 12https://tracker.habhub.org/#!qm=All&q=BIDOOF
[11:00] rjsnyder (~rjsnyder@p20030080AD1E1900F4ABCB0DBCED1FDE.dip0.t-ipconnect.de) joined #highaltitude.
[11:05] rjsnyder (~rjsnyder@p20030080AD1E1900F4ABCB0DBCED1FDE.dip0.t-ipconnect.de) left irc: Ping timeout: 276 seconds
[11:18] <SpacenearUS> New position from 03YPADSONDE after 0310 hours silence - 12https://tracker.habhub.org/#!qm=All&q=YPADSONDE
[11:22] LazyLeopard (~irc-clien@chocky.lazyleopard.org.uk) left irc: Quit: Now QRT
[11:40] <SpacenearUS> New position from 03RSIST after 032 days silence - 12https://tracker.habhub.org/#!qm=All&q=RSIST
[11:44] stryx` (~stryx@unaffiliated/stryx/x-3871776) left irc: Ping timeout: 260 seconds
[11:45] stryx` (~stryx@unaffiliated/stryx/x-3871776) joined #highaltitude.
[11:48] tunekey (~tunekey@unaffiliated/tunekey) left irc: Ping timeout: 260 seconds
[11:57] costyn (~costyn@s55946021.adsl.online.nl) left irc: Quit: costyn
[12:04] <SpacenearUS> New position from 03PayloadL after 035 days silence - 12https://tracker.habhub.org/#!qm=All&q=PayloadL
[12:07] <SpacenearUS> New position from 03U3B-3 after 0317 hours silence - 12https://tracker.habhub.org/#!qm=All&q=U3B-3
[12:13] <SpacenearUS> New vehicle on the map: 03BGSBoys_chase - 12https://tracker.habhub.org/#!qm=All&q=BGSBoys_chase
[12:24] acne (33065eb2@gateway/web/freenode/ip.51.6.94.178) joined #highaltitude.
[12:28] <adamgreig> what do people use for az/el with habs/habitat these days?
[12:33] <Darkside> heh
[12:33] <AndyEsser> child holding a yagi?
[12:33] <AndyEsser> :)
[12:33] <Darkside> i have a friend with a Alfa Spid mount
[12:33] <Darkside> cost more than i would want to pay
[12:33] <adamgreig> I mean software wise, sorry
[12:33] <adamgreig> someone has a few az/el on radios and they want them to autotrack habs during downtime
[12:33] <Darkside> oh
[12:34] <Darkside> dunno, you'd probably need to roll your own
[12:34] <AndyEsser> habrotate?
[12:34] <Darkside> habrotate will talk to pstrotator
[12:34] <AndyEsser> hopefully in the new house I can get my antennas finally set up and look at getting an Az/El mount
[12:34] <Darkside> tbh i think most rotator control software, and rotator control protocols are kind of crap
[12:34] <AndyEsser> *grumbles about having to move house again*
[12:34] <Darkside> as no rotator protocol really does overwind properly
[12:35] <Darkside> or even exposes an overwind condition to the user
[12:35] <fsphil> AndyEsser: at this rate just get a mobile home, save time
[12:35] <Darkside> so instead you go from 350 to 10 degrees the loooong way around
[12:35] <AndyEsser> Darkside: I read overwind as over wind... (in terms of breeze, not turning..)
[12:35] <Darkside> heh
[12:36] <AndyEsser> which still seemed to make sense in my mind...
[12:36] <Darkside> heh, kind of
[12:36] <Darkside> but you get the point
[12:36] <AndyEsser> indeed - I was wondering about this
[12:36] <Darkside> its more difficult for HABs i guess
[12:36] <AndyEsser> I guess you can only overwind by a certain number of degrees, then it'd have to go the long way around?
[12:36] <Darkside> with a satellite you know what the path is going to be ina dvance and can make better decisions about where to start, where to track
[12:36] <Darkside> with a hab you are really just taking it as it comes
[12:37] <Darkside> so i think at some point you have to just go 'fuck it' and let it do its thing
[12:37] <fsphil> maybe it can take into account the predicted path
[12:37] <fsphil> probably not worth it
[12:37] <Darkside> fsphil: this way be complications
[12:37] <Darkside> and complexity
[12:37] <Darkside> i was thinking the sae
[12:37] <Darkside> but fuuuuuuck
[12:37] <Darkside> way too hard basket imo
[12:37] <Darkside> anyway, i actually wrote some rotator control code the other day :P
[12:38] <Darkside> code to grab data from my lora ground station stuff and control pstrotator
[12:38] <AndyEsser> and I guess there's a certain probability of habs you're going to receive in your location, and sort of put the 'center point' in a place that catches most of those
[12:38] <Darkside> it should support rotctld too, but i havent really tested it
[12:38] <AndyEsser> I want to build a rotator
[12:38] <AndyEsser> eventually... at some point... when I have time...
[12:38] <AndyEsser> should've taken the windscreen motors from the landie before I Scrapped it
[12:39] <Darkside> adamgreig: anyway, PSTRotator is a nice wrapper for controlling rotators, but i think its windows only (may work in wine) and costs money
[12:39] <Darkside> rotctld is of course the open source abstraction layer for this stuff
[12:39] <Darkside> as for pulling stuff from habitat, tuning radios, etc, i think you're kind of on your own
[12:40] <Darkside> if it's an az-el rotator, maybe get him to run a satnogs ground station instead :-)
[12:40] <Ian_> I like the idea of software that puts out ASCII strings rather than client server crap, so that we can all have a crack with the windscreen wiper motors and Arduino etc. I have a cement mixer gearbox
[12:40] <Darkside> would probably be more useful than tracking habs
[12:40] <adamgreig> heh
[12:40] <adamgreig> I think they mostly do track satellites currently
[12:41] <Darkside> well a satnogs station will do that automatically
[12:41] <adamgreig> have sent him the link to habrotate tho
[12:41] <Darkside> well, kind of automatically
[12:41] <Darkside> it was apparently a bit hard on rotators for a while
[12:42] <Darkside> used to send a new position request at about 10 Hz
[12:56] <craag> lol v0.0.1 of habrotate did something like that :P
[12:58] <Darkside> pretty sure they fixed that :P
[12:59] Action: AndyEsser writes naive implementation with busy loop that constantly updates
[12:59] Action: AndyEsser adds sleep(250);
[12:59] <AndyEsser> :P
[12:59] <Darkside> mine just updates when it get a new pcket
[12:59] <Darkside> which is usually about once every 5 seconds anyway
[12:59] <Darkside> so thats not too bad
[12:59] <Darkside> a smarter implementation would do somethign based on antenna beamwidth i think
[12:59] <Darkside> like how gpredict does it
[13:00] <Darkside> because theres no point moving 0.5 degrees if the antennas 3dB beamwidth is 20 degrees wide
[13:00] <craag> habrotate has a threshold and overshoot to minimise movement
[13:00] <Darkside> right
[13:00] <craag> but originally just sent the commanded output straight to pstrotator
[13:00] <Darkside> craag: i see you are just talking to pstrotator too
[13:01] rjsnyder (~rjsnyder@p20030080AD1E1900FD6E20D5F24E513B.dip0.t-ipconnect.de) joined #highaltitude.
[13:01] <Darkside> mine will do both rotctld and pstrotator, but pstrotator seems a bit nicer
[13:01] <Darkside> well, in some respects
[13:01] <craag> yeah - was what the original requesters were running
[13:01] <craag> I didn't have a rotator of my own at the time :P
[13:01] <Darkside> also pretty easy to interface to
[13:01] <Darkside> though you have to get the current position back asynchronously
[13:02] <Darkside> you can poll it and it sends the position info via UDP to localhost:12001
[13:02] <craag> yeah I ignore that - just tell it where to go when it needs to move from where I told it last
[13:02] <AndyEsser> and hope it's aligned?
[13:02] <craag> I used to tell it every second (143deg, 143deg, 143deg, etc)
[13:02] <fsphil> do the big expensive rotators have feedback?
[13:03] <Darkside> they often have a potentiometer, yes
[13:03] <Darkside> you still need to align it to north/south or whatever
[13:03] <fsphil> yeah
[13:03] <craag> but then most rotator interfaces will have landed at 142 or something, and try again every second to land at 143 dead...
[13:03] <craag> 144, 142, 145, 142, etc...
[13:04] LazyLeopard (~irc-clien@chocky.lazyleopard.org.uk) joined #highaltitude.
[13:05] <Darkside> http://imgur.com/iCh8uhG
[13:05] <Darkside> this is my attempt
[13:05] rjsnyder (~rjsnyder@p20030080AD1E1900FD6E20D5F24E513B.dip0.t-ipconnect.de) left irc: Ping timeout: 276 seconds
[13:05] <Darkside> both the 'my location' and 'payload location' data are tapped off from my exsiting ground station software stack
[13:05] <Darkside> which throws all its data around the network via udp broadcast
[13:06] <Darkside> so it wasnt hard to sniff off the 'chase car' (stationary in this case) gps position data, and the payload telemetry data
[13:06] <craag> so I have a new thing I'm writing for our uni groundstation, calculates orbits for spacecraft and schedules passes by priority for the next week
[13:06] <Darkside> hrm
[13:06] <Darkside> why not just use satnogs?
[13:06] <craag> it currently runs my hamtv station using udp -> stm32 ethernet
[13:06] <Darkside> or is this uplink too
[13:06] Laurenceb_ (~laurence@host86-154-54-179.range86-154.btcentralplus.com) joined #highaltitude.
[13:07] <craag> and will hopefully support HABs too eventually :)
[13:07] <craag> hmm played with satnogs last year - wasn't impressed
[13:07] <Darkside> its gotten a bit better i think
[13:07] <craag> seems to have moved on though
[13:07] <Darkside> needs more RF type people to help with the demod stuff
[13:07] <fsphil> silly name
[13:07] <Darkside> at the moment its fairly basic demods, with minimal customizability per satellite
[13:08] <craag> does it do demod of non-afsk sats yet?
[13:08] <Darkside> well the point is it doesnt really demod anything properly
[13:08] <Darkside> it will do FM, SSB demod
[13:08] <Darkside> to audio
[13:08] <Darkside> but it doesnt go any further
[13:08] <craag> ah ok, does ssb
[13:08] <craag> that's what I meant :)
[13:08] <Darkside> well it does 1200 baud BPSK demod
[13:08] <Darkside> demods using a SSB demod and tries to keep the signal at a 1.5 kHz IF
[13:08] <craag> I see
[13:08] <craag> hmm
[13:09] <Darkside> i want to see that functionality with more customization
[13:09] <Darkside> i.e. specify a receive bandwidth and an IF
[13:09] <Darkside> then you can tell it to receive, say, a 9600 baud BPSK downlink and put it at a 12 kHz IF
[13:09] <Darkside> but its not there yet
[13:10] <Darkside> again, don't think it woudl take much work to make it do that
[13:10] <Darkside> and then the next step woudl be automated demodulation of specific satellites telemetry, but i can see that being hard to maintain for the mountain of different telemetry formats
[13:11] <Darkside> just doing the AX.25 ones, and dukping frames to a file would be a good start
[13:11] <Darkside> dumping*
[13:11] <Darkside> anyway, they definitely need help from RF/gnuradio savvy people
[13:12] <craag> so I've put together bascially rtl_tcp for the fcdpp to go with this, which we'll have headless demods hanging off, and then also resamples to 250KHz 8-bit for sdr sharp rtl_tcp compatibility so people can run their own gui demods
[13:12] <Darkside> mm
[13:13] <Darkside> it really woudlnt be hard to get satnogs to dump all received data as IQ
[13:13] <Darkside> that can very easily happen *after* the doppler correction too
[13:13] <craag> already done that bit too :/
[13:13] <Darkside> not tuning the receiver i hope
[13:14] <craag> no, on a demod off a feed from the scheduler db, bit clunky but works
[13:14] <Darkside> does bad things to PSK receivers apparently
[13:15] <craag> heh not surprised - hmm would be interested to see how they do it
[13:15] <Darkside> yeah not 100% sure whats going on in there
[13:16] <craag> I'm not really up to scratch on sdr/gnuradio - we've got a final year uni group starting in october to build our downlink + demod
[13:17] <Darkside> https://network.satnogs.org/observations/9471/
[13:18] <craag> have seen those nice graphs from csete on twitter :)
[13:18] <gonzo_> you have a cubesat project there?
[13:18] <Darkside> i think the best thing to add to satnogs at the moment would be to add raw IQ logging
[13:18] <Darkside> but the amount of disk apce required is huge
[13:23] stryx` (~stryx@unaffiliated/stryx/x-3871776) left irc: Ping timeout: 260 seconds
[13:24] <craag> looks like satnogs mixes it with a an LO that's periodically updated..
[13:24] stryx` (~stryx@unaffiliated/stryx/x-3871776) joined #highaltitude.
[13:25] <craag> I guess to do anything better you have to it in the demodulation itself
[13:28] <SpacenearUS> New position from 03W9YJ-11 after 039 days silence - 12https://tracker.habhub.org/#!qm=All&q=W9YJ-11
[13:30] acne (33065eb2@gateway/web/freenode/ip.51.6.94.178) left irc: Ping timeout: 260 seconds
[13:32] <Laurenceb_> !whereis HIRFW-6
[13:32] <SpacenearUS> 03Laurenceb_: 03HIRFW-6 is over 03North Atlantic Ocean 10(32.10607,-60.03785) at 0314110 meters
[13:35] <daveake> PE2BZ: Dunno if you're aware but $$PE2BZ_test is spamming the logtail somewhat
[13:36] kc2uez (~SKA0ut@static-74-42-252-20.br1.glvv.ny.frontiernet.net) left irc: Ping timeout: 240 seconds
[13:37] kc2uez (~SKA0ut@static-74-42-252-20.br1.glvv.ny.frontiernet.net) joined #highaltitude.
[13:50] costyn (~costyn@s55946021.adsl.online.nl) joined #highaltitude.
[14:00] costyn (~costyn@s55946021.adsl.online.nl) left irc: Quit: costyn
[14:04] vk3xco (af206d5a@gateway/web/freenode/ip.175.32.109.90) left irc: Ping timeout: 260 seconds
[14:30] <PE2BZ> daveake sorry :-(
[14:30] <daveake> np just made it difficult to see my own error earlier :)
[14:30] <PE2BZ> I have that one listener who forgets to disable the habitat when receiving me....
[14:31] HarveyPwca (~HarveyPwc@ip-64-134-173-177.public.wayport.net) joined #highaltitude.
[14:32] <PE2BZ> Would there be any chance that an update in the lora-gateway is made that I can tell in the pisky.txt that I don´t want my receivers to upload to the habitat when I am not flying ?
[14:32] <PE2BZ> I am trying to get rid of the corrupted images and the exiv2 errors...
[14:33] <daveake> Uploading of images and/or telemetry?
[14:34] <PE2BZ> no telemetry because (or when) I am stationary ?
[14:34] <daveake> Well I'm trying to understand what you're actually doing, or want to do
[14:36] d33p3y35 (~d33p3y35@91-145-163-242.internetia.net.pl) left irc: Ping timeout: 240 seconds
[14:36] d33p3y35 (~d33p3y35@91-145-163-242.internetia.net.pl) joined #highaltitude.
[14:37] <PE2BZ> I am sending SSDV on a UHF frequency to have G8FJG receiving it. pb0ahx is also receiving my images. He forgets to disable the habitat so all goes to the logtail. (when I forget it this also happens) the way to let Ron know I am transmitting is when he notices my images on the ssdv habhub page. Does that make sense ?
[14:39] <daveake> Can you just use a different frequency so pb0hax doesn't receive it ?
[14:39] <daveake> or do you want him to receive ?
[14:40] <daveake> You could hack pits to use a different first byte in ssdv packets, and hack the gateway to use those packets but not upload
[14:41] <daveake> This is too much an edge case for me to change the master, really
[14:41] <daveake> Also easy to hack it so it only ever sends ssdv and no telemetry
[14:49] <PE2BZ> Indeed I want him to receive also. He uses my SNR and RSSI to improve his setup and as propagation / tropo indication when the SNR goes up. I understand it´s not something which needs a change in the master because I use the software for a complete other purpose.
[14:50] <PE2BZ> I guess I give the send SSDV and no telemetry a go next weekend :-)
[14:50] <craag> So he really just wants a beacon..
[14:52] d33p3y35 (~d33p3y35@91-145-163-242.internetia.net.pl) left irc: Ping timeout: 246 seconds
[14:53] d33p3y35 (~d33p3y35@91-145-163-242.internetia.net.pl) joined #highaltitude.
[14:59] <daveake> It all seems a bit odd to be using the hab infrastructure for propagation tests
[15:00] <craag> yes, and to be awkward I'm not sure limiting it to *only* spamming the ssdv page is the answer.
[15:01] rjsnyder (~rjsnyder@p20030080AD1E19005915D9A5CCF3E28E.dip0.t-ipconnect.de) joined #highaltitude.
[15:02] <daveake> If you want to use lora for it, just use a python lora library and knock upa transmitter and receiver/logger
[15:06] Laurenceb_ (~laurence@host86-154-54-179.range86-154.btcentralplus.com) left irc: Ping timeout: 246 seconds
[15:06] rjsnyder (~rjsnyder@p20030080AD1E19005915D9A5CCF3E28E.dip0.t-ipconnect.de) left irc: Ping timeout: 276 seconds
[15:25] happysat (~katpoep@s5594c83f.adsl.online.nl) left irc: Ping timeout: 240 seconds
[15:30] happysat (~katpoep@s5594c83f.adsl.online.nl) joined #highaltitude.
[15:39] <SpacenearUS> New vehicle on the map: 03MARIJA_chase - 12https://tracker.habhub.org/#!qm=All&q=MARIJA_chase
[15:44] SopaXorzTaker (~SopaXorzT@unaffiliated/sopaxorztaker) joined #highaltitude.
[15:57] andycamb (~Thunderbi@global-5-143.nat-2.net.cam.ac.uk) left irc: Ping timeout: 276 seconds
[16:07] spencer (aed0271a@gateway/web/freenode/ip.174.208.39.26) joined #highaltitude.
[16:07] <spencer> Anyone on?
[16:12] <daveake> 172 currently
[16:15] <spencer> ;) I was on a few weeks back and I had an admin set my call to be permanantly pulled from APRS to habhub. Seems like I went to another channel though to chat. Is there an admin channel?
[16:15] <daveake> yes, #habhub
[16:15] <spencer> Thanks, I'll check in over there.
[16:16] <spencer> BTW, has anyone heard of reverse prediction (you choose the desired landing spot and calculate the launch spot)? I was wondering if any exist.
[16:18] <russss> I don't think so. it's not so useful if you have to file a NOTAM a month in advance
[16:19] newbie92 (~heathkid@12.228.170.9) joined #highaltitude.
[16:19] heathkid (~heathkid@unaffiliated/heathkid) left irc: Read error: Connection reset by peer
[16:19] <spencer> I am not using it for NOTAMs. I would use it for choosing launch sites based on a desired landing area.
[16:20] <russss> right, but that requires on you knowing what the weather will be a month in advance
[16:21] <spencer> Do you choose your launch location that far in advanced? We choose a general area and then pick the actual site 24 hours prior. Maybe the rules are different in your location. We are in the US are you in the UK?
[16:22] <russss> oh, that's nice. Yeah in the UK you have to specify the exact site.
[16:22] LeoBodnar (~LeoBodnar@host86-158-94-78.range86-158.btcentralplus.com) left irc: Quit: LeoBodnar
[16:22] <russss> so such a feature would not be terribly useful here
[16:25] <spencer> Makes sense. Yeah, here they just have a HAB form and they want the predictions but then you call them 30 min before launch and update them on the actual launch site.
[16:26] <spencer> I might have to just make my own reverse prediction program. Is there open source stuff for the prediction code?
[16:29] <russss> yup https://github.com/jonsowman/cusf-standalone-predictor/
[16:29] <russss> the actual prediction stuff is some slightly impenetrable C code but in theory it's not (quite) rocket science
[16:36] rjsnyder (~rjsnyder@p5B297428.dip0.t-ipconnect.de) joined #highaltitude.
[16:37] <adamgreig> spencer: check out https://github.com/cuspaceflight/tawhiri
[16:37] <adamgreig> for the updated version of the predictor code
[16:37] <adamgreig> in less inpenetratable python
[16:37] <adamgreig> reverse prediction has been on the to-do list for a while
[16:38] <spencer> I actually write firmware in C so C is more readable for me than Python but either works. If the python is more updated then I will start there.
[16:41] <adamgreig> the python is a more efficient numerical integration
[16:42] <adamgreig> the predictor has two main tasks, 1) know what the velocity of the payload is at any moment in flight (both the up/down speed due to lift/parachute, and the sideways motion due to wind); 2) integrate that velocity over time to get a trajectory
[16:42] <adamgreig> (1) is split into up/down for which we assume constant ascent rate and drag-equation descent (with appropriate atmospheric density for altitude)
[16:42] <adamgreig> and into wind speed, which is the other major hard thing; we download the NOAA GFS wind predictions, which give wind velocity at a series of time intervals, pressure-altitudes, and on a lat/lng grid
[16:43] LeoBodnar (~LeoBodnar@79-76-228-193.dynamic.dsl.as9105.com) joined #highaltitude.
[16:43] <adamgreig> then we interpolate through position, pressure-altitude, and time, to get an estimated wind velocity at the current position
[16:43] <adamgreig> finally numerical integration; the old c version uses a very simplistic naive algorithm, the python one is a lot better so is more accurate and requires less computation
[16:44] <adamgreig> the wind datasets are about 8GB or more each; we download them separately and load them into a large file-backed array which you just seek to index directly on each axis; then mmap it into the predictor process
[16:44] rjsnyder (~rjsnyder@p5B297428.dip0.t-ipconnect.de) left irc: Read error: Connection reset by peer
[16:44] <adamgreig> downloading them efficiently is its own undertaking, done here: https://github.com/cuspaceflight/tawhiri-downloader (in ocaml)
[16:44] rjsnyder (~rjsnyder@p20030080AD1E1900E989CD76431B914C.dip0.t-ipconnect.de) joined #highaltitude.
[16:45] <adamgreig> ( spencer ^ )
[16:45] <russss> heavens
[16:45] <russss> that's only 8GB if you want the whole world though, presumably
[16:45] <adamgreig> correct
[16:45] <adamgreig> though it's hardish to download a section of the world iirc
[16:45] <adamgreig> they are split into altitudes and times rather than geographic zones
[16:45] <russss> hmm
[16:46] <adamgreig> I think there are ways, can't remember
[16:46] <russss> there are plenty of sailing tools which do it somehow
[16:46] <adamgreig> I mean, we also mirror our files, and also we extract out the UK section and archive that long-term
[16:47] <adamgreig> (it's 8GB 4 times a day, too)
[16:48] <adamgreig> (compressed over the network though, can't remember what the traffic per day is exactly)
[16:49] <adamgreig> http://predict.habhub.org/datasets/
[16:50] <spencer> Very good information.
[16:50] bertrik (~bertrik@rockbox/developer/bertrik) joined #highaltitude.
[16:51] <spencer> Question is... how to reverse that so that a user gives an end location and a start location is calculated.
[16:51] <adamgreig> it's pretty much the same
[16:52] <adamgreig> you start at a landing spot, you put a negative sign in front of the wind velocity and ascent/descent rate, you run the numerical integration, you model time going backwards instead of forwards
[16:52] <adamgreig> if you basically just put a minus sign in front of dt and v you'd be done
[16:52] <adamgreig> (it's not quite that simple as the ascent rate modelling assumes you go up with one profile then come down with another, so you'd need to swap those around too)
[16:53] <adamgreig> honestly it's a feature we should have just added to tawhiri when we were writing it, because it'd probably have taken less than an hour when the whole system was in our heads
[16:54] <adamgreig> big talk for someone who still hasn't deployed tawhiri to production, four years or so after the python version was done, though
[16:57] <spencer> never heard of tawhiri but I am new to HAB. I am reading about it now.
[16:58] <russss> don't worry, I'd never heard of it either and I've been here for years
[16:58] <adamgreig> have you seen http://predict.habhub.org ?
[16:58] <russss> adamgreig: btw the github link in the about page of the predictor links to the old one
[16:59] <adamgreig> for good reason
[16:59] <adamgreig> the predictor page runs the old one
[16:59] <adamgreig> though that about page is pretty out of date anyway, the email addresses are pretty ancient too I think and the github repo that the predictor is actually deployed from is something like cuspaceflight/tawhiri-oldui-juryrig
[16:59] <adamgreig> (it uses the new downloader and memmaps in a new way and various things)
[17:00] <spencer> Yeah, we used http://predict.habhub.org on our flight this past saturday. We also used the tracker for the flight. I like how the tracker updates the prediction mid-flight.
[17:00] <adamgreig> tawhiri is the latest version of predict.habhub.org, by the same team, more or less
[17:01] <spencer> I see. Just not deployed yet I guess?
[17:01] <adamgreig> yea, something like that
[17:01] <adamgreig> it is running and live as an api somewhere
[17:02] <spencer> link?
[17:05] <adamgreig> http://predict.cusf.co.uk/api/v1/?launch_latitude=52&launch_longitude=0&launch_altitude=0&launch_datetime=2017-07-18T11%3A30%3A00%2B00:00&ascent_rate=5.000&burst_altitude=300007&descent_rate=5
[17:06] <adamgreig> wow uhm
[17:06] <adamgreig> that is going a bit high
[17:06] <adamgreig> let's pretend I didn't typo a 7 on the end of the burst altitude lol
[17:06] <adamgreig> http://predict.cusf.co.uk/api/v1/?launch_latitude=52&launch_longitude=0&launch_altitude=0&launch_datetime=2017-07-18T11%3A30%3A00%2B00:00&ascent_rate=5.000&burst_altitude=30000&descent_rate=5
[17:06] <russss> lol
[17:07] <spencer> very nice. so this one is a tad bit more accurate?
[17:08] <adamgreig> I guess
[17:08] <adamgreig> both are more accurate than you're likely to be with your launch time or ascent rate or burst altitude
[17:09] <mattbrejza> does this one allow you to make predictions for launches a short time in the past?
[17:10] <adamgreig> kinda
[17:10] <adamgreig> http://predict.cusf.co.uk/api/v1/?launch_latitude=52&launch_longitude=0&launch_altitude=0&launch_datetime=2017-07-17T17:00:00%2B00:00&ascent_rate=5.000&burst_altitude=30000&descent_rate=5
[17:10] <adamgreig> is a little in the past
[17:10] <adamgreig> it lets you predict up to the start of the current dataset
[17:10] <mattbrejza> ok
[17:10] <adamgreig> so you see it's currently using the 12Z dataset from today, so the earliest you can predict is from noon today
[17:11] <mattbrejza> still better than the current one
[17:11] <adamgreig> think that limit on the current one is artificial anyway
[17:11] <mattbrejza> although i assme that could be changed with one line change...
[17:11] hibbert[m] (hibbertcha@gateway/shell/matrix.org/x-qjykgyhrpfdiuobh) left irc: Ping timeout: 264 seconds
[17:11] <adamgreig> general predictor stuff is on my to-do list for my months of fun-employment after phd
[17:11] <spencer> makes sense. I notice on the tracker the predicted end still shows even after the payload has landed. Is this because it assumes a landing of 0 ft or just the inaccuracy of the current land elevation?
[17:11] <SIbot26> In real units: 0 ft = 0.00 m
[17:12] <adamgreig> on the web predictor, it assumes prediction ends at 0m ASL
[17:12] <adamgreig> the new predictor has an elevation model it uses to determine landing
[17:12] <adamgreig> in the UK it doesn't make much difference (and all the developers are in the UK)
[17:13] <spencer> yeah, we are just getting the ball rolling here in the US.
[17:13] <mattbrejza> at least crossing the merdian is well tested...
[17:14] <spencer> Last weekend our payload hit the ground but the tracker still showed some distance for a prediction.
[17:14] <adamgreig> probably your not-at-sea-level ground
[17:14] jbayfield (~jbayfield@cpc1-slou5-2-0-cust296.17-4.cable.virginm.net) joined #highaltitude.
[17:14] mDjtI (~mDjtI@cpc78041-stav21-2-0-cust252.17-3.cable.virginm.net) left irc: Ping timeout: 260 seconds
[17:14] <spencer> Yeah, we are 5000 ft.
[17:14] <SIbot26> In real units: 5000 ft = 1524 m
[17:15] <adamgreig> i had plenty of fun learning that black rock desert is about 1km ASL, so the rocket flight computer was already 1km up when it turned on
[17:15] <adamgreig> when developing it never sees more than like 20m asl at init, and that's on the second floor, lol
[17:15] <russss> also in the UK everything tends to travel east where the land is flatter
[17:15] <adamgreig> so yea, the new predictor (tawhiri) should be better for you, it will terminate at your actual elevation
[17:16] mDjtI (~mDjtI@cpc78041-stav21-2-0-cust252.17-3.cable.virginm.net) joined #highaltitude.
[17:16] <spencer> Nice. Just got to get that rolled into tracker.habhub.org, right? ;)
[17:16] <adamgreig> yea
[17:17] <adamgreig> it would be nice if it had some way to easily tell the tracker what your ascent rate/burst alt/descent rate were going to be per-payload too
[17:17] <adamgreig> i think habitatv2 should really have flight docs for aprs flights too, and the flight docs should have that information captured, and use it to configure predictor
[17:17] <adamgreig> bit of a pipe dream atm though
[17:17] <adamgreig> need some fresh young people just starting their undergrad with loads of spare time to write code to do it lol
[17:18] <spencer> Yeah, I was chatting with someone (maybe you) a couple weeks back about that. Maybe an IRC bot that updates that.
[17:18] <adamgreig> maybe
[17:18] <spencer> lol
[17:18] <adamgreig> that's how the current thing got done, back when
[17:18] <adamgreig> but it mostly works, so...
[17:19] <spencer> yeah, what we have now is great. Always something better.
[17:20] <adamgreig> always work out what the better system would be once we've built the current one too ofc
[17:20] <spencer> That's how it works. Well, I might take a crack at the reverse predictor if I get a moment.
[17:22] hibbert[m] (hibbertcha@gateway/shell/matrix.org/x-jsygnurlbynxrspf) joined #highaltitude.
[17:30] <edmoore> i like the idea of a reverse prediction
[17:30] <edmoore> semantically, i mean
[17:30] <adamgreig> haha, yes
[17:31] <adamgreig> more of a.. log? demonstration? determination?
[17:32] <edmoore> yes i suppose. a determination
[17:38] OZ1SKY_Brian (~Brian@x1-6-8c-10-d4-ff-6d-62.cpe.webspeed.dk) joined #highaltitude.
[17:38] <OZ1SKY_Brian> hi
[17:40] <spencer> ;) looking through the code now.
[17:41] <spencer> Maybe call it launch predictor instead of reverse predictor.
[17:54] <spencer> adamgreig, just like you said... it looks like this newer predictor does terminate when ground level is reached (not sea level).
[17:57] <adamgreig> good good
[17:58] <spencer> Do you remember which file has the integration calculation?
[17:58] <adamgreig> solver.pyx
[17:59] <adamgreig> the rough gist is, api.py is the web api, dataset.py manages access to the wind dataset, interpolate.pyx does the 5d interpolation of wind data
[17:59] <adamgreig> models.py contains the ascent/descent models, and the velocity models, and the burst/ground models, and their combinations to make flight profiles like "constant ascent rate, burst at some altitude, drag descent rate, stop when hits the ground"
[17:59] <adamgreig> solver.pyx has the rk4 integrator
[17:59] <adamgreig> the rest are less interesting
[18:08] <spencer> I see. Runge-Kutta
[18:12] jbayfield (~jbayfield@cpc1-slou5-2-0-cust296.17-4.cable.virginm.net) left irc: Ping timeout: 240 seconds
[18:12] <SpacenearUS> New vehicle on the map: 03DC2EH-6 - 12https://tracker.habhub.org/#!qm=All&q=DC2EH-6
[18:14] pb0ahx (~pb0ahx@53540677.cm-6-5a.dynamic.ziggo.nl) joined #highaltitude.
[18:19] spencer (aed0271a@gateway/web/freenode/ip.174.208.39.26) left irc: Ping timeout: 260 seconds
[18:23] jbayfield (~jbayfield@cpc1-slou5-2-0-cust296.17-4.cable.virginm.net) joined #highaltitude.
[18:39] SopaXorzTaker (~SopaXorzT@unaffiliated/sopaxorztaker) left irc: Remote host closed the connection
[18:47] namor (53963b74@gateway/web/freenode/ip.83.150.59.116) joined #highaltitude.
[18:52] <namor> good evening. here is the swiss chaos team trying to get allowance for the following doc id: 0437f6fd336a803b796520813a681267. if the weather stays nice it should happen tomorrow at about 1 p.m.
[18:54] <Upu> hi namor - nothing changed since last flight ?
[18:55] <SpacenearUS> New vehicle on the map: 03DC2EH-11 - 12https://tracker.habhub.org/#!qm=All&q=DC2EH-11
[18:55] <namor> well the parser is slightly different, therefore also the payload: 5f31434539ec4b03b24ee0bf6e7860fa
[18:56] <Upu> last parsed a month ago
[18:56] Mike-SA6BSS (~Mike-SA6B@h-155-4-222-166.NA.cust.bahnhof.se) left irc: Read error: Connection reset by peer
[18:56] <Upu> nothing changed in a month ?
[18:56] <namor> no. nothing changed in the last month.
[18:57] Mike-SA6BSS (~Mike-SA6B@h-155-4-222-166.NA.cust.bahnhof.se) joined #highaltitude.
[18:57] <Upu> 19:57:47 <SpacenearUS> Upu: Flight hkSOL4 (0437f6fd336a803b796520813a681267) has been approved! Good luck
[18:59] jmusac (~joefly@141-136-202-125.dsl.iskon.hr) joined #highaltitude.
[19:00] d33p3y35 (~d33p3y35@91-145-163-242.internetia.net.pl) left irc: Ping timeout: 240 seconds
[19:00] d33p3y35 (~d33p3y35@91-145-163-242.internetia.net.pl) joined #highaltitude.
[19:01] joefly (~joefly@lns01-0300.dsl.iskon.hr) left irc: Ping timeout: 276 seconds
[19:01] YO9GJX (~YO9GJX@109.99.23.22) joined #highaltitude.
[19:05] <namor> Upu: thank you!
[19:14] BrainDamage_ (~BrainDama@unaffiliated/braindamage) joined #highaltitude.
[19:15] BrainDamage (~BrainDama@unaffiliated/braindamage) left irc: Ping timeout: 248 seconds
[19:15] Nick change: BrainDamage_ -> BrainDamage
[19:18] jbayfield (~jbayfield@cpc1-slou5-2-0-cust296.17-4.cable.virginm.net) left irc: Remote host closed the connection
[19:19] jbayfield (~jbayfield@cpc1-slou5-2-0-cust296.17-4.cable.virginm.net) joined #highaltitude.
[19:25] andycamb (~Thunderbi@2a00:23c4:bf80:f700:25a6:d177:23cf:b169) joined #highaltitude.
[19:25] <jbayfield> Hi, just wanted to ask a quick question as I'm interested in getting into HAB but have a rather limited budget at the moment (teenager, no job). It's known that the cheap SDR dongles are okay for tracking, but only with additional components. What would you recommend to get a somewhat decent receiver setup? For example, I've seen the uputronics habamp preamps/filters - are they are a good investment?
[19:26] <jbayfield> I'm assuming having a decent antenna setup would help too - so any suggestions for that would be welcome.
[19:31] BrainDamage (~BrainDama@unaffiliated/braindamage) left irc: Ping timeout: 260 seconds
[19:32] <SpacenearUS> New position from 03KE0GEO-12 after 035 days silence - 12https://tracker.habhub.org/#!qm=All&q=KE0GEO-12
[19:33] BrainDamage (~BrainDama@unaffiliated/braindamage) joined #highaltitude.
[19:33] <SpacenearUS> New position from 03SP9UOB after 0319 hours silence - 12https://tracker.habhub.org/#!qm=All&q=SP9UOB
[19:40] namor (53963b74@gateway/web/freenode/ip.83.150.59.116) left irc: Ping timeout: 260 seconds
[19:41] drsnik_ (~drsnik@gate3.ima.cz) left irc: Quit: Leaving
[20:06] bertrik (~bertrik@rockbox/developer/bertrik) left irc: Remote host closed the connection
[20:07] bertrik (~bertrik@rockbox/developer/bertrik) joined #highaltitude.
[20:07] clopez (~tau@neutrino.es) joined #highaltitude.
[20:33] jbayfield (~jbayfield@cpc1-slou5-2-0-cust296.17-4.cable.virginm.net) left irc: Ping timeout: 248 seconds
[20:38] jbayfield (~jbayfield@cpc1-slou5-2-0-cust296.17-4.cable.virginm.net) joined #highaltitude.
[20:41] BrainDamage (~BrainDama@unaffiliated/braindamage) left irc: Ping timeout: 255 seconds
[20:41] rjsnyder (~rjsnyder@p20030080AD1E1900E989CD76431B914C.dip0.t-ipconnect.de) left irc: Remote host closed the connection
[20:44] BrainDamage (~BrainDama@unaffiliated/braindamage) joined #highaltitude.
[21:08] acne (33065eb2@gateway/web/freenode/ip.51.6.94.178) joined #highaltitude.
[21:09] andycamb (~Thunderbi@2a00:23c4:bf80:f700:25a6:d177:23cf:b169) left irc: Ping timeout: 246 seconds
[21:11] jmusac (~joefly@141-136-202-125.dsl.iskon.hr) left irc: Ping timeout: 260 seconds
[21:11] Mike-SA6BSS|2 (~Mike-SA6B@h-155-4-222-166.NA.cust.bahnhof.se) joined #highaltitude.
[21:11] <acne> What have I done wrong? fldigi is successfully uploading data - Ive created a payload doc but in the logtail I get "No configuration doc for '1ACS-1' found"
[21:13] mattbrej1a (~mattbrejz@kryten.hexoc.com) joined #highaltitude.
[21:14] Mike-SA6BSS (~Mike-SA6B@h-155-4-222-166.NA.cust.bahnhof.se) left irc: Ping timeout: 255 seconds
[21:15] <Vaizki> acne, are you sure the order of fields etc is the same?
[21:16] <Geoff-G8DHE-Lap> No control codes between or around the callsgn ?
[21:16] mattbrejza (~mattbrejz@kryten.hexoc.com) left irc: Ping timeout: 240 seconds
[21:17] <acne> sorry - first time trying this - I'm using habduino and stock code
[21:18] <acne> so I assume fields are ordered correctly
[21:18] <acne> geoff do you mean I cant have the minus sign in the call sign?
[21:19] Nick change: mattbrej1a -> mattbrejza
[21:19] <Geoff-G8DHE-Lap> No CONTROL codes, like an extra null or ctrl-C or someother none displaying character
[21:19] <jbayfield> This is probably not very helpful but I'd like to chip in anyway just so I can learn a bit too - looking at the payload config there isn't any parser configuration set up? Is that just a side-effect of the "start from existing" function?
[21:19] OZ1SKY_Brian (~Brian@x1-6-8c-10-d4-ff-6d-62.cpe.webspeed.dk) left irc: Quit: Please pause the radiowaves !
[21:20] <acne> geoff there shouldnt be any non displaying characters
[21:21] <Geoff-G8DHE-Lap> Have you checked or is that an assumption ?
[21:21] <Geoff-G8DHE-Lap> and yes there is no parser config setup looking at genpayload
[21:22] <Geoff-G8DHE-Lap> looks like you have just entered the description info and not the actual telemetry format itself
[21:22] <jbayfield> cool, wondered if that was just me. I'll go away now and let the people who know what they're talking about help. ^.^
[21:22] <acne> got it thanks
[21:34] Mike-SA6BSS (~Mike-SA6B@h-155-4-222-166.NA.cust.bahnhof.se) joined #highaltitude.
[21:34] Mike-SA6BSS (~Mike-SA6B@h-155-4-222-166.NA.cust.bahnhof.se) left irc: Client Quit
[21:36] <SpacenearUS> New vehicle on the map: 03KD2KPZ-11 - 12https://tracker.habhub.org/#!qm=All&q=KD2KPZ-11
[21:45] <SpacenearUS> New vehicle on the map: 031ACS-1 - 12https://tracker.habhub.org/#!qm=All&q=1ACS-1
[21:48] <jbayfield> acne: Good to see it's working now :)
[21:48] <acne> top job - thanks guys
[21:48] <acne> rtfm next time
[21:49] <jbayfield> ;)
[21:50] <acne> night night
[21:50] acne (33065eb2@gateway/web/freenode/ip.51.6.94.178) left irc: Quit: Page closed
[21:56] jbayfield (~jbayfield@cpc1-slou5-2-0-cust296.17-4.cable.virginm.net) left irc: Ping timeout: 240 seconds
[21:58] joefly (~joefly@141-136-202-125.dsl.iskon.hr) joined #highaltitude.
[21:59] tunekey (~tunekey@unaffiliated/tunekey) joined #highaltitude.
[22:03] <SpacenearUS> New position from 03BSS8 after 0321 hours silence - 12https://tracker.habhub.org/#!qm=All&q=BSS8
[22:14] TIBS-OLDSKOOL (~TIBS01@5751bf78.skybroadband.com) left irc: Ping timeout: 260 seconds
[22:15] TIBS-OLDSKOOL (~TIBS01@5751bf78.skybroadband.com) joined #highaltitude.
[22:23] LazyLeopard (~irc-clien@chocky.lazyleopard.org.uk) left irc: Quit: Now QRT
[22:27] HarveyPwca (~HarveyPwc@ip-64-134-173-177.public.wayport.net) left irc: Ping timeout: 268 seconds
[22:37] pe2bz_ (~pe2bz@005-038-128-083.dynamic.caiway.nl) joined #highaltitude.
[22:40] PE2BZ (~pe2bz@005-038-128-083.dynamic.caiway.nl) left irc: Ping timeout: 240 seconds
[22:42] rjsnyder (~rjsnyder@p20030080AD1E190030C5A8815C003182.dip0.t-ipconnect.de) joined #highaltitude.
[22:46] michal_f_home (~michal_f_@91-145-163-242.internetia.net.pl) joined #highaltitude.
[22:48] rjsnyder (~rjsnyder@p20030080AD1E190030C5A8815C003182.dip0.t-ipconnect.de) left irc: Ping timeout: 276 seconds
[22:51] drsnik (~drsnik@gate3.ima.cz) joined #highaltitude.
[22:59] bertrik (~bertrik@rockbox/developer/bertrik) left irc: Quit: "This incident will be reported"
[23:05] <michal_f_home> !flights
[23:05] <SpacenearUS> 03michal_f_home: Current flights: 03OLHZN-7 10(377f), 03Waddesdon School HAB2 10(121b), 03hkSOL4 10(1267), 03BIDOOF 10(d7f1), 03SP9UOB-P30 144.251 MHz CTSTIA 10(cbd2)
[23:08] en4rab (~en4rab@2a02:c7d:b767:300:604b:63d5:48c4:f9a0) left irc: Ping timeout: 240 seconds
[23:10] stryx` (~stryx@unaffiliated/stryx/x-3871776) left irc: Ping timeout: 260 seconds
[23:14] Laurenceb_ (~laurence@host86-143-84-93.range86-143.btcentralplus.com) joined #highaltitude.
[23:14] d33p3y35 (~d33p3y35@91-145-163-242.internetia.net.pl) left irc: Remote host closed the connection
[23:15] stryx` (~stryx@unaffiliated/stryx/x-3871776) joined #highaltitude.
[23:15] d33p3y35 (~d33p3y35@91-145-163-242.internetia.net.pl) joined #highaltitude.
[23:17] michal_f_home (~michal_f_@91-145-163-242.internetia.net.pl) left irc: Quit: HydraIRC -> http://www.hydrairc.com <- Would you like to know more?
[23:18] <SpacenearUS> New position from 03YPADSONDE after 0311 hours silence - 12https://tracker.habhub.org/#!qm=All&q=YPADSONDE
[23:20] <SpacenearUS> New vehicle on the map: 03KD2KPZ_chase - 12https://tracker.habhub.org/#!qm=All&q=KD2KPZ_chase
[23:45] <SpacenearUS> New position from 03RSIST after 039 hours silence - 12https://tracker.habhub.org/#!qm=All&q=RSIST
[00:00] --- Tue Jul 18 2017