highaltitude.log.20180118

[00:01] jbayfield (~quassel@cpc87601-slou5-2-0-cust26.17-4.cable.virginm.net) left irc: Ping timeout: 256 seconds
[00:08] day (~Unknown@unaffiliated/day) left irc: Ping timeout: 240 seconds
[00:16] day__ (~Unknown@unaffiliated/day) joined #highaltitude.
[00:29] drsnik (~drsnik@gate3.ima.cz) joined #highaltitude.
[00:43] Geoff-G8DHE_ (~Geoff-G8D@geoffg8dhe.plus.com) joined #highaltitude.
[00:47] Geoff-G8DHE-Tab (~Geoff-G8D@geoffg8dhe.plus.com) left irc: Ping timeout: 276 seconds
[00:48] Geoff-G8DHE-m (~Geoff-G8D@geoffg8dhe.plus.com) joined #highaltitude.
[00:48] Kryczek (~kryczek@about/security/staff/Kryczek) left irc: Ping timeout: 276 seconds
[00:48] Geoff-G8DHE (~Geoff-G8D@geoffg8dhe.plus.com) left irc: Ping timeout: 276 seconds
[00:48] Kryczek_ (~kryczek@about/security/staff/Kryczek) joined #highaltitude.
[00:53] en4rab_ (~en4rab@2a02:c7d:b774:6d00:34a2:8393:c00c:31c5) joined #highaltitude.
[00:53] en4rab (~en4rab@2a02:c7d:b774:6d00:91ac:3794:52cd:b2d5) left irc: Read error: Connection reset by peer
[00:57] <SpacenearUS> New position from 03IV3SRD-11 after 0312 hours silence - 12https://tracker.habhub.org/#!qm=All&q=IV3SRD-11
[00:58] Nick change: day__ -> day
[01:05] DocHopper (~DocHopper@unaffiliated/dochopper) left irc: Ping timeout: 268 seconds
[01:23] DL7AD (~sven@i5E863466.versanet.de) joined #highaltitude.
[01:24] orbyt_ (~orbyt@172.92.5.20) left irc: Quit: My MacBook has gone to sleep. ZZZzzz&
[01:25] DL7AD1 (~sven@i5E863BC0.versanet.de) left irc: Ping timeout: 255 seconds
[01:52] Smaned (~IceChat78@129.123.28.131) joined #highaltitude.
[01:55] DanielRichman (~daniel@unaffiliated/danielrichman) got netsplit.
[01:55] janeUbuntu (~jane@2001:3c8:c103:a001:224:7eff:fe0a:3ec9) got netsplit.
[01:55] d33p3y35 (~d33p3y35@91-145-163-242.internetia.net.pl) got netsplit.
[01:55] PE2BZ (~pe2bz@148-230-045-062.dynamic.caiway.nl) got netsplit.
[01:55] Maxell (~Maxell@duplex.bewaar.me) got netsplit.
[01:55] petrinm (niemelp1@gateway/shell/tkk.fi/x-ygveouygebboldar) got netsplit.
[01:55] spe (~spe@static.173.105.130.94.clients.your-server.de) got netsplit.
[01:55] tripleclones (~tripleclo@unaffiliated/tripleclones) got netsplit.
[01:55] Haxxa (~Harrison@180-150-30-18.NBN.mel.aussiebb.net) got netsplit.
[01:55] Vostok (vostok@kapsi.fi) got netsplit.
[01:55] qyx (~qyx@krtko.org) got netsplit.
[01:55] BrainDamage (~BrainDama@unaffiliated/braindamage) got netsplit.
[01:55] en4rab_ (~en4rab@2a02:c7d:b774:6d00:34a2:8393:c00c:31c5) got netsplit.
[01:55] Geoff-G8DHE-m (~Geoff-G8D@geoffg8dhe.plus.com) got netsplit.
[01:55] Geoff-G8DHE_ (~Geoff-G8D@geoffg8dhe.plus.com) got netsplit.
[01:55] nigelp (~nigel@host86-150-168-239.range86-150.btcentralplus.com) got netsplit.
[01:55] marian1235813 (~marian123@2a01cb0c08ac5e00d05a4ce3cc9bc22e.ipv6.abo.wanadoo.fr) got netsplit.
[01:55] Mike-SA6BSS|2 (~Mike-SA6B@h-155-4-221-109.NA.cust.bahnhof.se) got netsplit.
[01:55] zeusbot joined #highaltitude.
[01:55] edmoore (sid147314@gateway/web/irccloud.com/x-galjbuyqolizzdnx) joined #highaltitude.
[01:56] dustinm` (~dustinm@68.ip-149-56-14.net) joined #highaltitude.
[02:00] Darkside (~darkside@zedm.net) joined #highaltitude.
[02:05] Laurenceb_ (~laurence@host86-145-122-125.range86-145.btcentralplus.com) left irc: Ping timeout: 256 seconds
[02:05] zyp (zyp@zyp.no) left irc: Remote host closed the connection
[02:06] Ian_ (4d66af83@gateway/web/freenode/ip.77.102.175.131) left irc: Quit: Page closed
[02:09] Ian_ (4d66af83@gateway/web/freenode/ip.77.102.175.131) joined #highaltitude.
[02:12] Haxxa (~Harrison@180-150-30-18.NBN.mel.aussiebb.net) left irc: Quit: ZNC 1.6.2+deb1+jessie0 - http://znc.in
[02:35] Haxxa (~Harrison@180-150-30-18.NBN.mel.aussiebb.net) joined #highaltitude.
[03:03] d33p3y35 (~d33p3y35@91-145-163-242.internetia.net.pl) left irc: Remote host closed the connection
[03:04] d33p3y35 (~d33p3y35@91-145-163-242.internetia.net.pl) joined #highaltitude.
[03:16] day__ (~Unknown@unaffiliated/day) joined #highaltitude.
[03:18] day (~Unknown@unaffiliated/day) left irc: Ping timeout: 248 seconds
[03:19] Nick change: day__ -> day
[03:20] orbyt_ (~orbyt@172.92.5.20) joined #highaltitude.
[03:30] pb1dft (~pb1dft@ampache/staff/pb1dft) got netsplit.
[03:30] evilroots (~roots@bnc.janky.solutions) got netsplit.
[03:30] nickjohnson (sid789@gateway/web/irccloud.com/x-wlmuemqcobvgpwaa) got netsplit.
[03:30] Upu (sid143953@gateway/web/irccloud.com/x-eorduxempuhtsxwk) got netsplit.
[03:30] danielsaul (~danielsau@braavos.dansaul.co.uk) got netsplit.
[03:30] kswtch_ (~kswtch@laforge.schizzr.de) got netsplit.
[03:30] pb1dft (~pb1dft@ampache/staff/pb1dft) returned to #highaltitude.
[03:30] danielsaul (~danielsau@braavos.dansaul.co.uk) returned to #highaltitude.
[03:30] kswtch_ (~kswtch@laforge.schizzr.de) returned to #highaltitude.
[03:30] Nick change: danielsaul -> Guest19744
[03:31] nickjohnson (sid789@gateway/web/irccloud.com/x-ubhdhbbkrbvrlpsg) joined #highaltitude.
[03:31] Upu (sid143953@gateway/web/irccloud.com/x-psftjlmfnkzrdtyd) joined #highaltitude.
[03:32] happysat (~katpoep@s5594c83f.adsl.online.nl) left irc: Ping timeout: 260 seconds
[03:38] happysat (~katpoep@s5594c83f.adsl.online.nl) joined #highaltitude.
[03:41] evilroots (~roots@bnc.janky.solutions) got lost in the net-split.
[03:55] tweetBot (~nodebot@philcrump.co.uk) left irc: Remote host closed the connection
[03:55] tweetBot (~nodebot@philcrump.co.uk) joined #highaltitude.
[03:57] evilroots (~roots@bnc.janky.solutions) joined #highaltitude.
[04:00] <SpacenearUS> New position from 03icarusIV after 036 hours silence - 12https://tracker.habhub.org/#!qm=All&q=icarusIV
[04:21] heathkid (~heathkid@unaffiliated/heathkid) joined #highaltitude.
[04:22] heathkid (~heathkid@unaffiliated/heathkid) left irc: Client Quit
[05:03] day__ (~Unknown@unaffiliated/day) joined #highaltitude.
[05:06] day (~Unknown@unaffiliated/day) left irc: Ping timeout: 248 seconds
[05:06] Nick change: day__ -> day
[05:09] YO9GJX (~YO9GJX@109.99.23.188) left irc: Read error: Connection reset by peer
[05:12] orbyt_ (~orbyt@172.92.5.20) left irc: Quit: My MacBook has gone to sleep. ZZZzzz&
[05:27] Nick change: en4rab_ -> en4rab
[05:42] rjsnyder (~rjsnyder@p54A44CE0.dip0.t-ipconnect.de) joined #highaltitude.
[06:20] SushiKenBrown_ (~quassel@cmr-208-124-174-194.cr.net.cable.rogers.com) left irc: Ping timeout: 264 seconds
[06:45] kc2uez (~SKA0ut@static-74-42-252-20.br1.glvv.ny.frontiernet.net) left irc: Ping timeout: 240 seconds
[06:46] kc2uez (~SKA0ut@static-74-42-252-20.br1.glvv.ny.frontiernet.net) joined #highaltitude.
[06:57] zyp (zyp@zyp.no) joined #highaltitude.
[07:00] SushiKenBrown (~quassel@cmr-208-124-174-194.cr.net.cable.rogers.com) joined #highaltitude.
[07:10] tec (~tec@178.218.160.112) joined #highaltitude.
[07:16] Kodar (~Kodar@93-142-30-123.adsl.net.t-com.hr) joined #highaltitude.
[07:39] number10 (d42c14ce@gateway/web/freenode/ip.212.44.20.206) left irc: Quit: Page closed
[08:01] marian1235813 (~marian123@2a01cb0c08ac5e00d05a4ce3cc9bc22e.ipv6.abo.wanadoo.fr) left irc: Quit: My MacBook has gone to sleep. ZZZzzz&
[08:08] FireFighter (~firefight@2601:44:4200:ab4f:f419:6f7c:fc25:5734) joined #highaltitude.
[08:15] FireFighter (~firefight@2601:44:4200:ab4f:f419:6f7c:fc25:5734) left irc: Remote host closed the connection
[08:19] FireFighter (~firefight@2601:44:4200:ab4f:8c8a:e588:6e68:3a5) joined #highaltitude.
[08:23] scorpia (~tw16g08@login.ecs.soton.ac.uk) left irc: Ping timeout: 256 seconds
[08:23] scorpia (~tw16g08@login.ecs.soton.ac.uk) joined #highaltitude.
[08:24] Smaned (~IceChat78@129.123.28.131) left irc: Ping timeout: 256 seconds
[08:39] LazyLeopard (~irc-clien@chocky.lazyleopard.org.uk) joined #highaltitude.
[08:44] <SpacenearUS> New vehicle on the map: 03WESTG - 12https://tracker.habhub.org/#!qm=All&q=WESTG
[08:49] en4rab (~en4rab@2a02:c7d:b774:6d00:34a2:8393:c00c:31c5) left irc: Read error: Connection reset by peer
[08:49] en4rab_ (~en4rab@2a02:c7d:b774:6d00:34a2:8393:c00c:31c5) joined #highaltitude.
[08:55] sumie-dh (~sumie-dh@78.108.102.220) joined #highaltitude.
[09:04] stilldavid (~stilldavi@stilldavid.com) left irc: Quit: ZNC - 1.6.0 - http://znc.in
[09:18] forrestv (forrestv@unaffiliated/forrestv) joined #highaltitude.
[09:19] tec (tec@178.218.160.112) left #highaltitude ("Leaving").
[09:28] marian1235813 (~marian123@195.101.46.153) joined #highaltitude.
[09:33] rjsnyder (~rjsnyder@p54A44CE0.dip0.t-ipconnect.de) left irc: Remote host closed the connection
[09:34] rjsnyder (~rjsnyder@alcatraz-vpn-74.zim.uni-wuppertal.de) joined #highaltitude.
[09:51] FireFighter (~firefight@2601:44:4200:ab4f:8c8a:e588:6e68:3a5) left irc: Ping timeout: 276 seconds
[09:55] <SpacenearUS> New position from 03BB04 after 0314 hours silence - 12https://tracker.habhub.org/#!qm=All&q=BB04
[10:44] sumie-dh (~sumie-dh@78.108.102.220) left irc: Ping timeout: 276 seconds
[10:50] Laurenceb_ (~laurence@host86-145-122-125.range86-145.btcentralplus.com) joined #highaltitude.
[10:50] day__ (~Unknown@unaffiliated/day) joined #highaltitude.
[10:51] day (~Unknown@unaffiliated/day) left irc: Ping timeout: 248 seconds
[10:51] Nick change: day__ -> day
[10:53] tony__ (9f08aa19@gateway/web/freenode/ip.159.8.170.25) joined #highaltitude.
[10:53] tony__ (9f08aa19@gateway/web/freenode/ip.159.8.170.25) left irc: Client Quit
[11:02] Laurenceb_ (~laurence@host86-145-122-125.range86-145.btcentralplus.com) left irc: Ping timeout: 260 seconds
[11:18] drsnik (~drsnik@gate3.ima.cz) left irc: Read error: Connection reset by peer
[11:18] drsnik (~drsnik@gate3.ima.cz) joined #highaltitude.
[11:19] <SpacenearUS> New vehicle on the map: 03M2353412 - 12https://tracker.habhub.org/#!qm=All&q=M2353412
[11:19] <SpacenearUS> New vehicle on the map: 03M4453020 - 12https://tracker.habhub.org/#!qm=All&q=M4453020
[11:24] jordan (~jordan@94.199.28.194) joined #highaltitude.
[11:24] <jordan> dentify pokemonkyurem10
[11:24] <jordan> lul
[11:24] <jordan> everyone steal my nickname
[11:24] Nick change: jordan -> Guest69410
[11:24] Guest69410 (~jordan@94.199.28.194) left irc: Client Quit
[11:25] Guest69410 (~jordan@94.199.28.194) joined #highaltitude.
[11:25] Guest69410 (~jordan@94.199.28.194) left irc: Client Quit
[11:25] Guest69410 (~jordan@94.199.28.194) joined #highaltitude.
[11:25] Guest69410 (~jordan@94.199.28.194) left irc: Client Quit
[11:25] J4rdn (~jordan@94.199.28.194) joined #highaltitude.
[11:26] <J4rdn> Hi guys. I wondered If anyone has had the same problem with me.
[11:26] <J4rdn> as me*
[11:26] <J4rdn> yesterday as I let go of the balloon (or just before) the tracking on fl-digi cut out.
[11:27] <J4rdn> and spat out a load of crap on Fl-digi
[11:27] Kodar (~Kodar@93-142-30-123.adsl.net.t-com.hr) left irc: Ping timeout: 248 seconds
[11:28] <J4rdn> Like being able to track is just a must on a launch day
[11:28] <J4rdn> So I really need assistance to get to the bottom of this.
[11:29] <craag> 'tracking cut out' can you describe this more? Was the rtty still visible on the waterfall, were the red lines still aligned?
[11:29] <craag> do you have screenshots?
[11:30] <J4rdn> Mode was RTTYR (for some reason). the rtty was still visible on the waterfall.
[11:30] <J4rdn> craag, unfortunately no. I am just the guy to investigate the error. I wasn't in the field when this happened.
[11:32] Kodar (~Kodar@93-142-30-123.adsl.net.t-com.hr) joined #highaltitude.
[11:32] <J4rdn> apparently lower case V's lots of colons, lower case F's on the output display.
[11:32] Kodar (~Kodar@93-142-30-123.adsl.net.t-com.hr) left irc: Client Quit
[11:32] <J4rdn> Probably not helpful.
[11:32] <craag> Unfortunately from that information there's any number of things that it could have been, most commonly it's an accidental touchpad scroll that untunes the red lines.
[11:32] <J4rdn> craag, I was thinking that
[11:33] <fsphil> there was nothing uploaded from the launch site at all
[11:33] <fsphil> was it decoding at all?
[11:33] <J4rdn> I think they struggled for internet.
[11:34] <J4rdn> I was part of thr recovery team. we listened into it fine when it came across wales.
[11:34] <mfa298> the other thing might be common like that are switching between RTTYR/RTTY/LSB/USB or toggling the rv button
[11:34] <craag> ^^ yeah there might be some keyboard press that does this
[11:34] <mfa298> I think RTTYR or USB would be the current setting, normally with Rv off
[11:34] <J4rdn> The mode has to be RTTYR for some reason. Maybe that has something to do with it
[11:35] <mfa298> s/current/normal/
[11:35] <craag> consistent characters tend to indicate that it was seeing the signal, but either slightly mistuned or misconfigured
[11:35] <fsphil> or they where tuned to an alias
[11:36] <craag> yeah true. Using an rtlsdr for rx?
[11:36] <fsphil> I've done that myself once
[11:37] <craag> same. Easy mistake to make when you're right next to it.
[11:37] <J4rdn> I don't understand guys what?
[11:38] <craag> when the transmitter is very close, it can overload the receiver, with how SDRs work this means that you get aliases, or 'ghost signals'
[11:38] <J4rdn> we use the NooElec dongles RTLSDR2838
[11:38] <daveake> I did the alias thing on my first launch
[11:38] <craag> they'll look very look the real signal, often not quite as strong and with some distortion that prevents 100% copy
[11:38] <daveake> Wondered wtf was going on
[11:38] <craag> RTL SDRs are famous for it, as they're a very cheap design.
[11:39] day (~Unknown@unaffiliated/day) left irc: Ping timeout: 260 seconds
[11:39] <J4rdn> oh right a ghost signal you say.
[11:39] <daveake> This was an AOR scanner
[11:39] <daveake> very close obv
[11:39] <J4rdn> So the "signal could be fine" but then when i let go of the balloon it drops ?
[11:39] <daveake> Well not alias really - just tuned the wrong side of the signal
[11:40] <craag> yep, would be a classic alias.
[11:40] <daveake> Yeah if it's an alias those disappear once there's some distance to the tracker
[11:40] <J4rdn> How can I prevent this then>?
[11:40] <craag> this is why knowing the real transmit frequency of your tracker is usefull, to make sure you find the real one.
[11:40] <daveake> remove aerial on rtl
[11:40] <J4rdn> since the launch team. look for the green checksums and then launch.
[11:41] <fsphil> it could also simply be a bad antenna, or connection
[11:41] <craag> are you running this as a commercial operation?
[11:41] <daveake> yup
[11:41] <J4rdn> Hmm we know the freq of our trackers. so it's not an alias then.
[11:42] <craag> J4rdn: you often don't on here :P
[11:42] <SpacenearUS> New position from 03RSISP after 03a day silence - 12https://tracker.habhub.org/#!qm=All&q=RSISP
[11:42] <SpacenearUS> New position from 03RSIZM after 03a day silence - 12https://tracker.habhub.org/#!qm=All&q=RSIZM
[11:42] <J4rdn> The launch team do. I don't back at HQ. I ask them when they get 4g service.
[11:43] <craag> Ah ok
[11:43] <J4rdn> Yeah it's a stupid system. Very hard to break out of.
[11:43] <J4rdn> in my opinion.
[11:44] <craag> All I can say is that it's useful to have someone at the launch site who knows what they're doing.
[11:44] <daveake> You guys certainly don't help yourselves by not publicising flights in advance, with correct details
[11:44] <J4rdn> The tracking monitor who has these issues yesterday said he did lots of "spare equipment" switching so that he could rule out equipment failiures. but nothing worked in the end.
[11:45] <J4rdn> daveake, yeah its a pain. a lot of our launches are short notices.
[11:45] <daveake> Usually (seems to me) it's "we have a flight up somewhere near X not sure of frequency"
[11:45] <fsphil> the other stations had no problem tracking it
[11:45] <J4rdn> so i didn't piss you admins off. I decided to terminate the flight docs from our checklist.
[11:45] <daveake> Mailing list would help. Or here, the day before
[11:45] <J4rdn> Yeah i tracked it too fsphil so im thinking operator mistake.
[11:45] <daveake> and not or
[11:46] <fsphil> yeah
[11:46] <SpacenearUS> New vehicle on the map: 03M4t53020 - 12https://tracker.habhub.org/#!qm=All&q=M4t53020
[11:46] <craag> Without further evidence of what exactly happened (eg. screenshots, phone video) you're not going to know.
[11:47] <craag> Was a misconfiguration of the rx/fldigi somewhere.
[11:47] <SpacenearUS> New position from 03RSIST after 0310 hours silence - 12https://tracker.habhub.org/#!qm=All&q=RSIST
[11:47] <J4rdn> craag, problem is, the guy who knows stuff about these things (me) arn't on all the launches. So I have to train the guys that do. I think screenshots and logging would seems to insignificant on there part.
[11:48] sumie-dh (~sumie-dh@cst2-62-95.cust.vodafone.cz) joined #highaltitude.
[11:50] <craag> Honestly, lora tracking would make a lot more sense for you. We switched to it for primary tracking in SUSF just to streamline the launch process, we weren't getting paid - it just made our lives easier.
[11:50] Kodar (~Kodar@93-142-30-123.adsl.net.t-com.hr) joined #highaltitude.
[11:51] <J4rdn> craag, i tried LoRa tracking. I could never get it working. And I don't know enough about it to ask in here. because id frankly just get told to RTFM
[11:52] <craag> You're at the limits with RTTY in that you always need someone skilled enough to handle/debug dl-fldigi.
[11:52] <J4rdn> Agreed.
[11:53] <Mike-SA6BSS|2> I would also sugest running the tracker at 50 or 100 bauds that will work much betterthen 300
[11:54] <daveake> yup
[11:54] <craag> Learning to develop a plug'n'play system with lora or equivalent is the only way forward for you in that respect. (note that we always still carried a rtty rx as backup)
[11:54] <J4rdn> I have one tracker on 50 bd..
[11:55] <daveake> I tend to only fly rtty to keep the rtty listeners happy :)
[11:55] <Mike-SA6BSS|2> :)
[11:55] <craag> yeah never had reason to use the backup, it was more incase our lora rx failed as we only had 1x in the chase car.
[11:55] <Mike-SA6BSS|2> I have a aprs / rtty tracker ready for flight as soon the sun get a little higher
[11:55] <J4rdn> I mean thats my approach too. I ran 2 lora flights. both cut out after release.
[11:56] <J4rdn> and now my gateway doesnt even work at HQ, so i put it in a box and stored it haha
[11:57] <Mike-SA6BSS|2> any one that knows of the dynamics behind why a foil balloon looses 1 gram of free lift at ground level every 30 hours but can stay afloat for weeks at 10000m?
[11:58] <J4rdn> The problem I had with LoRa was defineitly to do with the different modes and also what antenna i needed for the lora board on the payload
[11:58] <craag> This is the point where you need some external expertise then, even if only briefly to help you with the wall you've hit (ie. "lack of range on lora, no idea why")
[11:59] <craag> Antenna is identical to rtty.
[11:59] <J4rdn> craag, I just don't wanna seem nooby. cos i've been doing this a while now. And sometimes when people tell me to try stuff. i have no lcue what there asking me to do
[12:00] <Mike-SA6BSS|2> thre is a lora 869Mhz ? that would need another antenn
[12:00] <J4rdn> I got both 434 an 868 licence exempt lora boards.
[12:00] <Mike-SA6BSS|2> ok
[12:01] chandroid (~chandroid@brk139.neoplus.adsl.tpnet.pl) left irc: Ping timeout: 240 seconds
[12:02] <J4rdn> I got the 868 one for more bandwith allocation that applied to IR2030 or something like that
[12:02] day (~Unknown@unaffiliated/day) joined #highaltitude.
[12:02] <craag> There's always more to learn, particularly in radio comms - I've been doing some level of stuff for years, now professionally and still learning :)
[12:02] <J4rdn> craag, I joined my local radio club last week :)
[12:02] <craag> perfect :)
[12:02] <J4rdn> they talked about vhf comps. it was fairly interesting
[12:03] <J4rdn> Yeah i'm working toward my foundation license.
[12:03] chandroid (~chandroid@dur5.neoplus.adsl.tpnet.pl) joined #highaltitude.
[12:04] <craag> that'll give you the basics of how antennas & coax work, which sounds like a prime area of interest for your issues
[12:08] <J4rdn> It does, i got this booklet with me which talks me through that stuff.
[12:08] <J4rdn> Like i learned that ground planes arn't actually for vertical signals lol
[12:08] <J4rdn> which confused me alot.
[12:12] <J4rdn> Like right now I wanna ask, where do I even restart with LoRa?
[12:16] chandroid (~chandroid@dur5.neoplus.adsl.tpnet.pl) left irc: Ping timeout: 255 seconds
[12:20] chandroid (~chandroid@bwi30.neoplus.adsl.tpnet.pl) joined #highaltitude.
[12:23] <J4rdn> do you need the PITS board for lora to work?
[12:28] <craag> for the lora link to work, you need a transmitter on the payload, receiver on the ground. For the balloon to know where it is it needs a gps. Start from there and work out the easiest available hardware to use.
[12:29] <J4rdn> craag, i think I have all the hardware i need with me
[12:29] <J4rdn> thanks though
[12:29] <craag> Ok. If you PITS kit then there's plenty of instructions too :)
[12:29] <craag> *have PITS kit
[12:30] <J4rdn> Yeah i do.
[12:30] <J4rdn> followed them instruction. got my gateway working before. but now it doesn't. adn i need to re hook up a lora board to a po
[12:30] <J4rdn> pi
[12:31] <craag> Easiest thing to do at this point might be to wipe the sd card and start again.
[12:31] <craag> Then you can rule out software/configuration as the issue
[12:32] <SpacenearUS> New position from 03IV3SRD-11 after 0311 hours silence - 12https://tracker.habhub.org/#!qm=All&q=IV3SRD-11
[12:33] <J4rdn> alright good idea!
[12:33] <J4rdn> im gunna boot my windows up, wont be long
[12:34] <fsphil> optimistic thing to say when booting windows
[12:35] <J4rdn> haha yeah
[12:35] J4rdn (~jordan@94.199.28.194) left irc: Remote host closed the connection
[12:39] <day> rip
[12:42] _Jord (5ec71cc2@gateway/web/freenode/ip.94.199.28.194) joined #highaltitude.
[12:43] <_Jord> I'm back. I prefer my new name
[12:43] <_Jord> What should my (hobbiest) callsign be at home when I get my antenna rig set up?
[12:44] <mfa298> _Jord: one thing that might help (for you and the launch teams) is trying to track others flights, that would give scope to experiment with settings when the pressure is off.
[12:45] <daveake> +1
[12:46] <_Jord> Yeah unfortunately we only have our HQ antenna (x-50 N) and it isn't allowed to go on the roof of the building so its on the side of a window and can only pick up when the payload is in its range (like a range cone)
[12:46] <_Jord> Although I did manage to work out airspy and sdr# so thats good
[12:48] <mfa298> getting the launch teams to practice on other flights sounds like it might be a useful exercise as well and the presumably they have a decent (mobile) setup for launch/chase/recovery
[12:48] <_Jord> Yeah thing is. The launch team don't want to practice. they just want plug n play 100 % of the time
[12:49] <_Jord> they go down there to get a job done. not to practise. As far as they are concerned they plug the pi in. load hdsdr. load fl-digi and connect to internet and it works.
[12:49] <mfa298> I don't think that's really an option with rtty, and might not be fully gaurenteed with Lora. Knowing how to fix things when they don't work (especially with rtty) is important
[12:50] <fsphil> reality is going to disappoint them
[12:50] <_Jord> Yes and it comes back on me.
[12:50] <_Jord> rtty is hardly ever plug n play
[12:50] <_Jord> in my experiences
[12:52] <daveake> "Connect to internet" doesn't seem to happen often either
[12:52] <fsphil> no, but I do prefer it as I get a better overview of what's going on
[12:52] <mfa298> practicing on others flights ought to be a case of driving up a decent hill and seeing what you can get for a couple of hours. It doesn't have the pressure of havign to launch a balloon, recover it or drive whilst tracking.
[12:52] <_Jord> Nope.
[12:52] <gonzo_> there is no plug and play HAB tracker solution. Just picking up on other people's work and running with it
[12:52] <craag> ^^ this is very true
[12:52] <fsphil> you can tell a lot just by listening to an rtty signal
[12:53] <_Jord> Thing is. we launch alot. and i must say, commerically. I don't think that they will accept "rtty is never plug n play" when in there eyes it is and has been for ages.
[12:54] <daveake> yup. First I knew that my babage had (on second attempt) jumped was the changed in sound of the rtty signal
[12:54] <daveake> -ed
[12:55] <daveake> About time they stepped back a bit and got it sorted then, IMO
[12:55] <mfa298> If they lose the signal without knowing why as it sounds like it did on the last launch then I don't think they can say it's always been plug and play.
[12:55] <gonzo_> _Jord, you will have to design your own plug and play system. And prove it out as reliable. Which is what many here have done. But no-one currently offers one for sale.
[12:56] <_Jord> gonzo_: sounds like a big ask for someone who isnt quite clued up with this stuff
[12:56] <_Jord> I just feel like i rely on you guys an awful lot and that if i was to take this up at home. I'd never stop chatting in this irc channel;
[13:00] <craag> It sounds like you're going the right way with self-education. Remember that you're trying to engineer a reliable solution something a lot of people still do just for the challenge, and that takes time. Often significant time the first time round.
[13:00] <_Jord> So i wouldn't use the pisky then? i'd haev to start from scratch?
[13:01] <craag> It's a case of taking it a problem at a time, fixing that problem, checking that it is actually fixed, and then moving on.
[13:01] <craag> Not what I'm saying.
[13:01] <_Jord> craag: I'm somewhat a developer for python. but the pisky code mind boggles me
[13:01] <daveake> boggles me too
[13:01] <_Jord> it does?
[13:01] <craag> Start with the pisky as a platform, get it working, then get it working automatically at boot. That'll mostly be linux-stuff rather than code-stuff.
[13:01] <_Jord> Didn't you write it?
[13:02] <daveake> </humour>
[13:02] <craag> Then fault-test it, try unplugging/replugging, see what went wrong and find out how to fix it, etc.
[13:02] <_Jord> I've used cron for some project in the past. that way you can get bash or python scripts to work on boot,
[13:02] <craag> The most useful thing this teaches you is how to spot problems
[13:03] <craag> and immediately know the route to fix/deal with them.
[13:03] <craag> this only comes with experience.
[13:03] <_Jord> so make a thing that opens PISKY, HDSDR, FLIDIGI etc and tunes them into the correct settings automatically?
[13:03] <daveake> This is a systems thing, rather than worrying about pits code or something. Making sure you always have working aerials, that the launch team has a means of testing that the aerial is connected and working, that the batteries are new, that the receiving equipment is working, etc etc
[13:04] <craag> sorry, I'm meaning lora. As I said before RTTY will take you no further in the direction of plug'n'play-ness.
[13:04] <craag> Yes this is systems engineering.
[13:04] <daveake> e.g. in my kitbag I have frequency meters (so I know wtf frequency I chose), signal strength meter, DMM etc
[13:05] <_Jord> daveake: 3 things ive never heard of
[13:05] <daveake> You're doing this commercially there's no reason not to spend time and money getting it all reliable
[13:06] <_Jord> I'm not. the people i do it for are. I came here for a "software developer" job
[13:06] <daveake> Things break, and that especially includes things that kept used a lot for flight. So an aerial that worked once might have gotten broken on landing, and you don't want to fly that one again
[13:06] <daveake> "you" = company not you = individual
[13:06] <_Jord> so straight away make a new aerial?
[13:06] <mfa298> and if you're doing it commercially then the launch chase teams should be prepared to spend time learning the system, how it works, how to fix it when broken etc.
[13:06] <_Jord> yeah i agree.
[13:06] <daveake> Yes new aerial. Or make it very solid.
[13:08] <daveake> This is the one I flew last time
[13:08] <_Jord> What would you recommend for keeping track of stuff. just lots and lots of documents of lists ?
[13:08] <daveake> Soldered, shrink-wrapped, sugrued.
[13:08] <daveake> https://usercontent.irccloud-cdn.com/file/b6xMHA0K/image.png
[13:08] <_Jord> is that play-doh?
[13:08] <daveake> Sugru
[13:09] <daveake> Rubber putty that sets
[13:09] <_Jord> ah
[13:09] <daveake> Point is, those things hit the ground at 10mph+ and are liable to get broken
[13:09] <_Jord> yeah
[13:09] <mfa298> if the company thinks RTTY is a solid, plug and play system maybe try and organise a challenge day. split into teams, let one team set up a transmitter and then others try and decode it with minimal starting information (maybe just a frequency), or have a working tracker & reciever, change one setting on the receiver side and see if the other teams can work out how to get back to receiving
[13:10] <_Jord> yeah mfa ill note that down
[13:10] <daveake> Like I said, no excuse for the guys not spending the time on this stuff. I know I do and I don't do anywhere near the number of launches.
[13:10] <_Jord> Yeah but you blog it all aswell which takes time right?
[13:11] <_Jord> where as we turn around phone calls in maybe 2-3 days.
[13:11] <daveake> I spend a lot of time on it, yes. Mostly unpaid. If I can spend the time doing it right so can they.
[13:11] <daveake> So, they spend 2-3 days getting sorted then they'll be OK next time they get an order.
[13:12] <_Jord> That would require alot of organisation from me.
[13:12] <_Jord> almmost like a platform i would need to stand on but no clue how to get.
[13:12] <_Jord> almost like a presence.
[13:13] <daveake> For me a launch is 3 days minimum. 1 day getting all the kit together, programmed, tested. 1 launch day. 1 day collecting videos, photos, sending it out, blogging, whatever.
[13:14] <daveake> 4th day rest as I'm knackered by then :)
[13:15] <daveake> And for bigger launches there's the planning, getting the customer to understand what they're getting, predictions, permission, designing the payload if that's at all special, writing any new code if I'm doing anything new, etc.
[13:15] <daveake> The telnet flight was probably a week of coding, for example
[13:15] <_Jord> Your incredibly intelligent i must say
[13:16] <_Jord> that telnet shit really shocked me
[13:16] <daveake> Seems to me the missing bit for your guyes is the setting up and testing prior to launch day.
[13:16] <daveake> Yeah that one was a lot of fun
[13:16] <mfa298> it sounds like they might need to manage customer expectations, I'd have thought having a 1-5 week (depending on scale needed) turnaround would be acceptable to most customers if suitably explained. if you're doing anything of any scale you're potentially going to need the 4 weeks lead time with the CAA to get permission
[13:16] <_Jord> We don't test. I do. and my tests are on my desk.
[13:17] <daveake> mfa298: Managing expectations is job #1 when I get the first email
[13:17] <daveake> Which is mainly about predictions and having to wait for a launch
[13:18] <daveake> but also what they will/won't get out of it, possibility of losing kit, etc
[13:19] <_Jord> yeah.
[13:24] <_Jord> right ill follow the LoRa manual- starting from scratch in but in here if i need anything answered lol
[13:24] <daveake> yup
[13:25] <_Jord> is your github README the best place to start daveake?
[13:25] <daveake> yup
[13:25] <_Jord> alrighty
[13:25] <fsphil> I need to get back to working on those modules
[13:26] <fsphil> gonna give up on the 869mhz ones, I just can't seem to get a useful power level out of them
[13:26] <daveake> The range is much less with high bandwidth
[13:29] <SpacenearUS> New vehicle on the map: 03M2413059 - 12https://tracker.habhub.org/#!qm=All&q=M2413059
[13:30] _Jord (5ec71cc2@gateway/web/freenode/ip.94.199.28.194) left irc: Ping timeout: 260 seconds
[13:32] <fsphil> even with the low rates it seemed to struggle
[13:32] <fsphil> the receiver might only hear 1 out of every 10 packets
[13:32] <daveake> hmmm
[13:33] _Jord (5ec71cc2@gateway/web/freenode/ip.94.199.28.194) joined #highaltitude.
[13:34] <daveake> I had one module (the one I was using to receive flights) seemed OK with my usual settings (250kHz, everything else set as fast as poss) that didn't get many packets when set to different bandwidth etc
[13:34] <daveake> Swapped module problem went away
[13:34] <fsphil> hmm, might get another lora board
[13:34] <daveake> I've only flown them using 250kHz and that works up to about 50 miles then drops off a cliff
[13:34] <fsphil> I know the 434 one works as I've received some of your flights with it
[13:35] <daveake> Goes very quickly from near 100% reception to near 0
[13:35] <_Jord> I dced. did i miss much.
[13:35] <daveake> I had one 434 board that txd OK wouldn't rx anything
[13:36] <gonzo_> _Jord, not muh
[13:37] <gonzo_> much
[13:37] es5nhc (~es5nhc@95.149.250.238) joined #highaltitude.
[13:39] <fsphil> the lack of feedback from the modules is annoying
[13:39] Action: fsphil wants a pretty waterfall
[13:40] <gonzo_> you could have a waterfall of one bit bucket
[13:42] <_Jord> this is going to take a while. all i did was plug a etho into a fresh install of raspbian stretch desktop...
[13:54] <SpacenearUS> New vehicle on the map: 03BRUCE - 12https://tracker.habhub.org/#!qm=All&q=BRUCE
[14:07] N2NXZ (3231701e@gateway/web/freenode/ip.50.49.112.30) joined #highaltitude.
[14:08] <N2NXZ> habhub tracking map has not been working here,very slow as if something is bogging it down.Will not load.Going on 4 days or so like this.Server issues or overload?
[14:09] <daveake> Loads OK here, in a few seconds
[14:09] <N2NXZ> Maybe too many flights going.Short duration flights should be removed once they land ?
[14:10] <N2NXZ> I see they are on the map for 24 hours...
[14:10] <N2NXZ> My browser will not load,I get WAIT or QUIT option
[14:11] <N2NXZ> Have to try later
[14:12] <fsphil> I've found it quite slow, but it's just the large amount of data
[14:12] <N2NXZ> Appears lots of data...maybe a bad connection from NY to server too.
[14:13] <N2NXZ> There,finally loaded up...what are the "M" flights anyhow...they seem to be non stop ?
[14:14] <fsphil> meteorological sondes
[14:14] <N2NXZ> Tethered or actual multiple flights taking place?
[14:15] <vaizki> N2NXZ, open it in developer mode or similar to see what transfer is taking too long
[14:15] <N2NXZ> Got it
[14:15] <N2NXZ> I`ll look this over,ever since the "M" bunches this has been happening.Perhaps just a lot of data coming in
[14:18] <N2NXZ> Loading up now...just takes some time
[14:18] <N2NXZ> Tnx for info
[14:18] N2NXZ (3231701e@gateway/web/freenode/ip.50.49.112.30) left irc: Quit: Page closed
[14:20] <mfa298> it was quite slow loading for me earlier, although lots of things seem worse since last patch tuesday so might not be habhub as such that's the issue
[14:41] <Mike-SA6BSS|2> heard that firefox might have problem loading the page
[14:42] <Mike-SA6BSS|2> using chrome here, loads in seconds
[14:42] <Mike-SA6BSS|2> ahh. Jim signed out :/
[14:42] <_Jord> still not even got an image on the SD card. seems that diskpart didnt work and neither did my raspbian stretch image
[14:48] <daveake> I use win32diskimager on a windows pc
[14:53] <_Jord> Yeah disk part was to clear the old image and everything on it.
[14:54] <daveake> No need
[14:55] <daveake> Just write the new image. It'll resize on first boot anyway.
[14:55] <_Jord> ah okay.
[15:00] marian1235813 (~marian123@195.101.46.153) left irc: Quit: My MacBook has gone to sleep. ZZZzzz&
[15:04] es5nhc (~es5nhc@95.149.250.238) left irc: Ping timeout: 248 seconds
[15:10] hyde00001 (~hyde00001@cpc69050-oxfd25-2-0-cust745.4-3.cable.virginm.net) joined #highaltitude.
[15:14] Nick change: Kryczek_ -> Kryczek
[15:15] orbyt_ (~orbyt@172.92.5.20) joined #highaltitude.
[15:15] <hyde00001> Looks like a challenging chase for the Epsom team...
[15:21] PE1ANS (52b04031@gateway/web/freenode/ip.82.176.64.49) joined #highaltitude.
[15:23] es5nhc (~es5nhc@95.149.250.238) joined #highaltitude.
[15:25] <PE1ANS> !dial westg
[15:25] <SpacenearUS> 03PE1ANS: Latest dials for 03WestonG Epsom 10(af62): 03434.6 MHz
[15:28] orbyt_ (~orbyt@172.92.5.20) left irc: Quit: My MacBook has gone to sleep. ZZZzzz&
[15:31] es5nhc (~es5nhc@95.149.250.238) left irc: Quit: Konversation terminated!
[15:32] d33p3y35 (~d33p3y35@91-145-163-242.internetia.net.pl) left irc: Read error: Connection reset by peer
[15:34] d33p3y35 (~d33p3y35@91-145-163-242.internetia.net.pl) joined #highaltitude.
[15:36] es5nhc (~es5nhc@95.149.250.238) joined #highaltitude.
[16:00] marian1235813 (~marian123@195.101.46.153) joined #highaltitude.
[16:10] OLHZN (~tcarissim@rrcs-24-105-183-114.nys.biz.rr.com) joined #highaltitude.
[16:18] OLHZN (~tcarissim@rrcs-24-105-183-114.nys.biz.rr.com) left irc: Quit: Leaving.
[16:41] rjsnyder_ (~rjsnyder@p54A44CE0.dip0.t-ipconnect.de) joined #highaltitude.
[16:45] jbayfield (4d63291b@gateway/web/freenode/ip.77.99.41.27) joined #highaltitude.
[16:45] <jbayfield> !dial WESTG
[16:45] rjsnyder (~rjsnyder@alcatraz-vpn-74.zim.uni-wuppertal.de) left irc: Ping timeout: 265 seconds
[16:45] <SpacenearUS> 03jbayfield: Latest dials for 03WestonG Epsom 10(af62): 03434.59692 MHz, 434.597782 MHz, 434.65 MHz, 1.3 MHz
[16:48] OLHZN (~tcarissim@rrcs-24-105-183-114.nys.biz.rr.com) joined #highaltitude.
[16:49] Smaned (~IceChat78@129.123.28.131) joined #highaltitude.
[16:49] <PE2BZ> jbayfield I think this is not a good test for your antenna. With the outdoor Diamond over her it´s barely visible and rarely decodes
[16:52] <jbayfield> Thought so - I was mainly testing new RTL-SDR dongle. Didn't plan on decoding anything
[16:52] rjsnyder_ (~rjsnyder@p54A44CE0.dip0.t-ipconnect.de) left irc:
[16:52] <jbayfield> It has travelled quite far, I must say
[16:54] jbayfield (4d63291b@gateway/web/freenode/ip.77.99.41.27) left irc: Quit: Page closed
[16:55] <PE2BZ> 145 km/h I have seen :-)
[16:55] rjsnyder (~rjsnyder@p54A44CE0.dip0.t-ipconnect.de) joined #highaltitude.
[16:56] OLHZN (~tcarissim@rrcs-24-105-183-114.nys.biz.rr.com) left irc: Quit: Leaving.
[16:56] _Jord (5ec71cc2@gateway/web/freenode/ip.94.199.28.194) left irc: Quit: Page closed
[17:05] DocHopper (~DocHopper@unaffiliated/dochopper) joined #highaltitude.
[17:06] orbyt_ (~orbyt@172.92.5.20) joined #highaltitude.
[17:09] OLHZN (~tcarissim@rrcs-24-105-183-114.nys.biz.rr.com) joined #highaltitude.
[17:09] OLHZN (~tcarissim@rrcs-24-105-183-114.nys.biz.rr.com) left irc: Read error: Connection reset by peer
[17:10] YO9GJX (~YO9GJX@109.99.23.188) joined #highaltitude.
[17:16] <PE2BZ> Does WESTG have a chute attached ?
[17:19] orbyt_ (~orbyt@172.92.5.20) left irc: Quit: My MacBook has gone to sleep. ZZZzzz&
[17:22] orbyt_ (~orbyt@172.92.5.20) joined #highaltitude.
[17:24] en4rab_ (~en4rab@2a02:c7d:b774:6d00:34a2:8393:c00c:31c5) left irc: Read error: Connection reset by peer
[17:24] en4rab__ (~en4rab@2a02:c7d:b774:6d00:34a2:8393:c00c:31c5) joined #highaltitude.
[17:28] <PE1ANS> Grtzz Ben...
[17:29] PE1ANS (52b04031@gateway/web/freenode/ip.82.176.64.49) left irc: Quit: Page closed
[17:30] YO9GJX (~YO9GJX@109.99.23.188) left irc: Read error: Connection reset by peer
[17:30] YO9GJX (~YO9GJX@109.99.23.188) joined #highaltitude.
[17:33] orbyt_ (~orbyt@172.92.5.20) left irc: Quit: My MacBook has gone to sleep. ZZZzzz&
[17:34] sumie-dh (~sumie-dh@cst2-62-95.cust.vodafone.cz) left irc: Ping timeout: 256 seconds
[17:37] hyde00001 (~hyde00001@cpc69050-oxfd25-2-0-cust745.4-3.cable.virginm.net) left irc:
[17:47] <SpacenearUS> New vehicle on the map: 03OM4AOZ_chase - 12https://tracker.habhub.org/#!qm=All&q=OM4AOZ_chase
[17:53] Hiena (~boreger@81.93.195.181.datatrans.hu) joined #highaltitude.
[17:55] orbyt_ (~orbyt@172.92.5.20) joined #highaltitude.
[17:59] Smaned (~IceChat78@129.123.28.131) left irc: Ping timeout: 256 seconds
[18:03] HarveyPwca (~HarveyPwc@ip-64-134-173-72.public.wayport.net) joined #highaltitude.
[18:03] es5nhc (~es5nhc@95.149.250.238) left irc: Ping timeout: 240 seconds
[18:05] n00by_d00by (~n00by_d00@2600:380:9c42:f78f:462:9527:2c35:8f8d) joined #highaltitude.
[18:14] n00by_d00by (~n00by_d00@2600:380:9c42:f78f:462:9527:2c35:8f8d) left irc: Ping timeout: 276 seconds
[18:30] es5nhc (~es5nhc@95.149.250.238) joined #highaltitude.
[18:34] Nick change: en4rab__ -> en4rab
[18:37] bertrik (~bertrik@rockbox/developer/bertrik) joined #highaltitude.
[18:38] rjsnyder (~rjsnyder@p54A44CE0.dip0.t-ipconnect.de) left irc:
[18:46] marian1235813 (~marian123@195.101.46.153) left irc: Quit: My MacBook has gone to sleep. ZZZzzz&
[18:46] rjsnyder (~rjsnyder@p54A44CE0.dip0.t-ipconnect.de) joined #highaltitude.
[18:48] es5nhc (~es5nhc@95.149.250.238) left irc: Quit: Konversation terminated!
[18:48] es5nhc (~es5nhc@95.149.250.238) joined #highaltitude.
[18:58] d33p3y35 (~d33p3y35@91-145-163-242.internetia.net.pl) left irc: Ping timeout: 240 seconds
[19:01] d33p3y35 (~d33p3y35@91-145-163-242.internetia.net.pl) joined #highaltitude.
[19:01] marian1235813 (~marian123@2a01cb0c08ac5e0065d1d39f85d2821a.ipv6.abo.wanadoo.fr) joined #highaltitude.
[19:04] es5nhc (~es5nhc@95.149.250.238) left irc: Ping timeout: 240 seconds
[19:13] kc2uez (~SKA0ut@static-74-42-252-20.br1.glvv.ny.frontiernet.net) left irc: Ping timeout: 240 seconds
[19:15] kc2uez (~SKA0ut@static-74-42-252-20.br1.glvv.ny.frontiernet.net) joined #highaltitude.
[19:18] sumie-dh (~sumie-dh@78.108.102.220) joined #highaltitude.
[19:28] HarveyPwca (~HarveyPwc@ip-64-134-173-72.public.wayport.net) left irc: Ping timeout: 240 seconds
[19:30] HarveyPwca (~HarveyPwc@ip-64-134-173-72.public.wayport.net) joined #highaltitude.
[19:37] Smaned (~IceChat78@129.123.28.131) joined #highaltitude.
[19:38] <SpacenearUS> New vehicle on the map: 03PeakR - 12https://tracker.habhub.org/#!qm=All&q=PeakR
[19:38] <SpacenearUS> New vehicle on the map: 03PeakL - 12https://tracker.habhub.org/#!qm=All&q=PeakL
[19:45] tibs01 (~steve@tibs01.steve-gibbs.co.uk) left irc:
[19:46] <SpacenearUS> New position from 03HIRFW-6 after 0318 hours silence - 12https://tracker.habhub.org/#!qm=All&q=HIRFW-6
[19:52] HarveyPwca (~HarveyPwc@ip-64-134-173-72.public.wayport.net) left irc: Quit: The Pwca has left the building
[19:55] d33p3y35 (~d33p3y35@91-145-163-242.internetia.net.pl) left irc: Ping timeout: 240 seconds
[19:59] d33p3y35 (~d33p3y35@91-145-163-242.internetia.net.pl) joined #highaltitude.
[20:09] nigelvh (~nigel@50-46-212-13.evrt.wa.frontiernet.net) left irc: Remote host closed the connection
[20:10] LazyLeopard (~irc-clien@chocky.lazyleopard.org.uk) left irc: Quit: Now QRT
[20:23] Mike-SA6BSS|2 (~Mike-SA6B@h-155-4-221-109.NA.cust.bahnhof.se) left irc: Read error: Connection reset by peer
[20:24] tibs01 (~steve@tibs01.steve-gibbs.co.uk) joined #highaltitude.
[20:25] Mike-SA6BSS (~Mike-SA6B@h-155-4-221-109.NA.cust.bahnhof.se) joined #highaltitude.
[20:34] nigelvh (~nigel@50-46-212-13.evrt.wa.frontiernet.net) joined #highaltitude.
[20:40] es5nhc (~es5nhc@95.149.250.238) joined #highaltitude.
[20:52] nigelvh (~nigel@50-46-212-13.evrt.wa.frontiernet.net) left irc: Remote host closed the connection
[20:55] rjsnyder (~rjsnyder@p54A44CE0.dip0.t-ipconnect.de) left irc: Remote host closed the connection
[21:02] nigelvh (~nigel@50-46-212-13.evrt.wa.frontiernet.net) joined #highaltitude.
[21:06] Hiena (~boreger@81.93.195.181.datatrans.hu) left irc: Quit: Konversation terminated!
[21:20] es5nhc (~es5nhc@95.149.250.238) left irc: Ping timeout: 248 seconds
[21:26] es5nhc (~es5nhc@95.149.250.238) joined #highaltitude.
[21:37] nigelvh (~nigel@50-46-212-13.evrt.wa.frontiernet.net) left irc: Remote host closed the connection
[21:40] Vostok (vostok@kapsi.fi) left irc: Ping timeout: 276 seconds
[21:41] Vostok (vostok@kapsi.fi) joined #highaltitude.
[22:01] nigelvh (~nigel@50-46-212-13.evrt.wa.frontiernet.net) joined #highaltitude.
[22:15] Smaned_ (~IceChat78@129.123.136.207) joined #highaltitude.
[22:18] Smaned (~IceChat78@129.123.28.131) left irc: Ping timeout: 256 seconds
[22:22] Smaned_ (~IceChat78@129.123.136.207) left irc: Ping timeout: 256 seconds
[22:23] es5nhc (~es5nhc@95.149.250.238) left irc: Ping timeout: 248 seconds
[22:55] bertrik (~bertrik@rockbox/developer/bertrik) left irc: Quit: "This incident will be reported"
[22:55] rjsnyder (~rjsnyder@p54A44CE0.dip0.t-ipconnect.de) joined #highaltitude.
[23:00] rjsnyder (~rjsnyder@p54A44CE0.dip0.t-ipconnect.de) left irc: Ping timeout: 256 seconds
[23:06] uwe_ (~uwe_@ipservice-092-211-039-238.092.211.pools.vodafone-ip.de) left irc: Ping timeout: 256 seconds
[23:17] <SpacenearUS> New vehicle on the map: 03M2353385 - 12https://tracker.habhub.org/#!qm=All&q=M2353385
[23:17] <SpacenearUS> New vehicle on the map: 03N1650484 - 12https://tracker.habhub.org/#!qm=All&q=N1650484
[23:23] <SpacenearUS> New vehicle on the map: 03M4613459 - 12https://tracker.habhub.org/#!qm=All&q=M4613459
[23:27] Laurenceb_ (~laurence@host86-145-122-125.range86-145.btcentralplus.com) joined #highaltitude.
[23:33] Kodar (~Kodar@93-142-30-123.adsl.net.t-com.hr) left irc:
[23:43] <SpacenearUS> New position from 03RSISP after 0310 hours silence - 12https://tracker.habhub.org/#!qm=All&q=RSISP
[23:49] <SpacenearUS> New vehicle on the map: 03LU1ESY-3 - 12https://tracker.habhub.org/#!qm=All&q=LU1ESY-3
[23:58] jarod (~jarod@85.93.177.177) left irc: Quit: later
[00:00] --- Fri Jan 19 2018