highaltitude.log.20190911

[00:13] Laurenceb_ (~laurence@140.141.208.46.dyn.plus.net) joined #highaltitude.
[01:01] Laurenceb_ (~laurence@140.141.208.46.dyn.plus.net) left irc: Ping timeout: 268 seconds
[01:31] happysat (~katpoep@s5594c83f.adsl.online.nl) joined #highaltitude.
[01:57] labjg (~labjg@150.203.88.49) joined #highaltitude.
[02:00] dustinm` (~dustinm@static.38.6.217.95.clients.your-server.de) left irc: Quit: Leaving
[02:04] dustinm` (~dustinm@static.38.6.217.95.clients.your-server.de) joined #highaltitude.
[02:13] labjg_ (~labjg@150.203.88.49) joined #highaltitude.
[02:16] dustinm` (~dustinm@static.38.6.217.95.clients.your-server.de) left irc: Ping timeout: 276 seconds
[02:16] labjg (~labjg@150.203.88.49) left irc: Ping timeout: 246 seconds
[02:23] dustinm` (~dustinm@static.38.6.217.95.clients.your-server.de) joined #highaltitude.
[02:50] DL7AD (~sven@2001:16b8:5c49:8300:addc:4beb:8db0:4e5f) left irc: Ping timeout: 264 seconds
[03:04] DL7AD (~sven@2001:16b8:5cdd:3600:f5fe:613:a866:5431) joined #highaltitude.
[03:16] Axone (~Axone@lfbn-1-12352-154.w90-91.abo.wanadoo.fr) left irc: Quit: ZNC 1.6.6+deb1ubuntu0.2 - http://znc.in
[03:18] Axone (~Axone@lfbn-1-12352-154.w90-91.abo.wanadoo.fr) joined #highaltitude.
[03:39] labjg_ (~labjg@150.203.88.49) left irc: Quit: Leaving
[03:40] edmoore (sid147314@gateway/web/irccloud.com/x-dbkbhibrklxbtokd) left irc: Ping timeout: 250 seconds
[03:40] M0XIN (sid101661@gateway/web/irccloud.com/x-tdpncelyujhihkcs) left irc: Ping timeout: 250 seconds
[03:42] eddyb (sid155877@gateway/web/irccloud.com/x-jwchjpqfdcqsqzmb) left irc: Ping timeout: 264 seconds
[03:44] M0XIN (sid101661@gateway/web/irccloud.com/x-dndtxotrcmccuftj) joined #highaltitude.
[03:44] eddyb (sid155877@gateway/web/irccloud.com/x-otgtzelwkmxuzqaf) joined #highaltitude.
[03:45] edmoore (sid147314@gateway/web/irccloud.com/x-geiqwsneqzdmhxkr) joined #highaltitude.
[03:55] tweetBot (~nodebot@philcrump.co.uk) left irc: Remote host closed the connection
[03:55] tweetBot (~nodebot@philcrump.co.uk) joined #highaltitude.
[04:05] YO9GJX (~YO9GJX@109.100.112.75) left irc: Remote host closed the connection
[05:33] <SpacenearUS> New position from 03AK0SK-11 after 0314 hours silence - 12https://tracker.habhub.org/#!qm=All&q=AK0SK-11
[05:58] Kodar (~Kodar@93-139-135-141.adsl.net.t-com.hr) joined #highaltitude.
[06:03] Kodar (~Kodar@93-139-135-141.adsl.net.t-com.hr) left irc: Client Quit
[06:04] Kodar (~Kodar@93-139-135-141.adsl.net.t-com.hr) joined #highaltitude.
[06:13] SA6BSS-Mike (~SA6BSS-Mi@h-155-4-222-217.NA.cust.bahnhof.se) left irc: Read error: Connection reset by peer
[06:16] SA6BSS-Mike (~SA6BSS-Mi@h-155-4-222-217.NA.cust.bahnhof.se) joined #highaltitude.
[06:53] <SpacenearUS> New position from 03SA6BSS-8 after 0315 hours silence - 12https://tracker.habhub.org/#!qm=All&q=SA6BSS-8
[07:14] Nick change: eddyb -> eddyb[legacy]
[07:25] <SpacenearUS> New position from 03SA6BSS/AM after 0315 hours silence - 12https://tracker.habhub.org/#!qm=All&q=SA6BSS%2FAM
[08:48] <daveake> If anyone needs help understanding payload vs flight docs, I'll get our kitten to explain ... https://usercontent.irccloud-cdn.com/file/5F3FRAuu/image.png
[08:53] <SA6BSS-Mike> :)
[09:40] <SpacenearUS> New vehicle on the map: 03OE3FRE_chase - 12https://tracker.habhub.org/#!qm=All&q=OE3FRE_chase
[09:40] <SpacenearUS> New vehicle on the map: 03S52O-9_chase - 12https://tracker.habhub.org/#!qm=All&q=S52O-9_chase
[09:45] <fsphil> habicat
[10:08] <daveake> :)
[10:24] BrainDamage_ (~BrainDama@unaffiliated/braindamage) joined #highaltitude.
[10:26] BrainDamage (~BrainDama@unaffiliated/braindamage) left irc: Ping timeout: 268 seconds
[10:26] Nick change: BrainDamage_ -> BrainDamage
[10:32] Lahti (~Lahti@dyvym10mtq0j5ck20nvzy-4.rev.dnainternet.fi) joined #highaltitude.
[11:17] chris_99 (uid26561@gateway/web/irccloud.com/x-fjijckxtkwjsjpie) joined #highaltitude.
[11:18] PB0AHX-Herman (~PB0AHX@83-84-6-119.cable.dynamic.v4.ziggo.nl) left irc: Ping timeout: 268 seconds
[11:50] <SpacenearUS> New vehicle on the map: 03APJHAB9 - 12https://tracker.habhub.org/#!qm=All&q=APJHAB9
[11:52] KD4BFP (4080de83@64.128.222.131) left irc: Remote host closed the connection
[11:53] KD4BFP (4080de83@64.128.222.131) joined #highaltitude.
[11:59] FireFighter (~firefight@2601:44:4200:ab4f:fcb4:c4b:f1bb:913b) joined #highaltitude.
[12:00] <SpacenearUS> New vehicle on the map: 03LCARS_chase - 12https://tracker.habhub.org/#!qm=All&q=LCARS_chase
[12:03] <KD4BFP> Any of the PITS software folks available to help debug an issue? Ive been having repeated issues with PITS SSDV images stopping mid-flight. But I cant seem to find anything in the logs as to why.
[12:04] <KD4BFP> PITS sends complete images and telemetry up to a 10-15km and then stops. It appears to capture and store a few additional images on-board, but never returns to sending image packets. Telemetry packets continue normally (thank god).
[12:04] <KD4BFP> Has anyone seen this before? Do I need to add something to snapper to create additional logs? Can you think of any process to watch/reset to keep things going?
[12:05] <SA6BSS-Mike> ping Davake
[12:05] <SpacenearUS> New vehicle on the map: 03APJHAB - 12https://tracker.habhub.org/#!qm=All&q=APJHAB
[12:05] <SA6BSS-Mike> Daveake
[12:05] <daveake> 'ello
[12:06] <SA6BSS-Mike> KD4BFP have a Q
[12:06] <daveake> sec
[12:06] <KD4BFP> Hi Dave! Pesky US PITS user havin issues again...
[12:06] <KD4BFP> Any of the PITS software folks available to help debug an issue? Ive been having repeated issues with PITS SSDV images stopping mid-flight. But I cant seem to find anything in the logs as to why.
[12:07] <KD4BFP> PITS sends complete images and telemetry up to a 10-15km and then stops. It appears to capture and store a few additional images on-board, but never returns to sending image packets. Telemetry packets continue normally (thank god).
[12:07] <KD4BFP> Has anyone seen this before? Do I need to add something to snapper to create additional logs? Can you think of any process to watch/reset to keep things going?
[12:08] <daveake> Not seen anything matching that, however there have been some camera issues. You could redirect the output of the camera script to a log file and see what you get
[12:08] <daveake> Which camera ? Which OS ?
[12:10] <KD4BFP> Using a 'generic' Pi camera on a Pi-zero. At first I thought the camera was having issues with low temperature, but on my recent flight over a hurricane I noticed that there were plenty of images stored on the Pi.
[12:10] <KD4BFP> Up to a point.
[12:10] <daveake> Yeah, generic is probably the issue tbh
[12:11] <KD4BFP> Roger that
[12:11] <daveake> There have been 2 OS-related camera issues
[12:12] <KD4BFP> Is there an OS version you suggest? I have a flight Friday and can make a new clean image
[12:12] <daveake> One was ages ago and was a kernel bug that I reported and got fixed. It caused corrupted images mainly but did sometimes stop the camera from working. This really was a long time ago and I'd expect you to see the corrupted images first.
[12:14] <KD4BFP> All of the images seem fine. The PITS works fine for 30+ minutes of fligh and successfully finishes sending an image and then switching to only sending telemetry for the rest of the flight
[12:14] <Darkside> hmm
[12:14] <daveake> Second issue got fixed in the OS before I noticed it, and caused all SD access to lock up. So that even included the tracker if it was locking. Normally the tracker survives - you can pull the SD and it'll keep going - but this one locked it solid.
[12:14] <Darkside> i've seen little lines of coruruption in my own images, usually like 1 pixel high
[12:14] <Darkside> not sure if thats the camera or what
[12:14] <daveake> That sounds like the data path not the command path (i2c)
[12:15] <daveake> The corruption was huge - image split into 4 smaller images, kind of interlaced
[12:15] <KD4BFP> After the flight, I notice that the Pi has continued to record good images at least 20 minutes beyond when the SSDV stops
[12:16] <daveake> Basically the camera was in a different memory mode to what the application expected, because the commands were lost or corrupted
[12:16] <KD4BFP> So the PITS images FULL folder has lots of images
[12:16] <daveake> KD4BFP: Hmm, not sure that makes sense. Were those in the FULL folder or in the RTTY/LORA folders ?
[12:17] <KD4BFP> I figure that somehow the processing from FULL to LORA is getting messed up
[12:17] <daveake> OK so the camera was successfully taking full-sized images but for some reason couldn't take smaller ones ?
[12:17] <daveake> There's no processing like that - it takes separate photos
[12:17] <KD4BFP> Lemme check...
[12:18] <KD4BFP> You're right, there are more photos in LORA
[12:18] <daveake> The LoRa ones just have different height/width parameters; otherwise the same
[12:18] <KD4BFP> So I guess the problem is converting from LORA to SSDV
[12:19] <KD4BFP> I notice that SSDV images pile up in the root of tracker
[12:19] <daveake> Take a look at one and tell me the width/height of the image in pixels
[12:20] <daveake> Shouldn't do ... the images are saved into the images/LoRa0 (or whatever) folder when they are taken
[12:20] <KD4BFP> 640 x 480
[12:20] <daveake> OK
[12:21] <KD4BFP> Looks like images are saving to LORA1 okay
[12:21] <daveake> Then when it chooses the next image for SSDV those images get moved into a dated folder
[12:21] <KD4BFP> yes, I see some in there
[12:21] <daveake> So what folder are these images in ?
[12:22] <daveake> i.e. images taken after ssdv stopped
[12:22] <daveake> Also sort by size and check the largest image file
[12:23] <KD4BFP> there is a bogus timestamped folder with a few setup images. Then the GPS got good time lock. So there is another date stamped folder
[12:23] <daveake> Yes that's fine - it uses the Pi time/date till GPS updates it. The Pi defaults to the last time it was shutdown
[12:30] <KD4BFP> should there be a handful of "ssdv" images piling up in the root of tracker? Maybe I should just reformat the microSD and do a clean install
[12:31] <daveake> What file extension ?
[12:32] <daveake> Things like ssdv_1.bin ?
[12:32] <daveake> (iirc)
[12:32] <KD4BFP> yes
[12:32] <daveake> Normal. Those are just kept in case the ground station asks for an image packet to be re-sent
[12:33] <daveake> It could tidy those more aggresively
[12:33] d33p3y35 (~d33p3y35@83-238-169-175.static.ip.netia.com.pl) left irc: Ping timeout: 246 seconds
[12:33] d33p3y35 (~d33p3y35@83-238-169-175.static.ip.netia.com.pl) joined #highaltitude.
[12:33] <daveake> e.g. If there's no uplink enabled it can delete once sent
[12:33] <KD4BFP> I'll do a clean re-install and run some extended tests..
[12:34] <daveake> Yeah. You can replay a flight to see if that triggers it.
[12:34] <KD4BFP> that's right
[12:35] <KD4BFP> the stored images stop prior to burst, so there is an additional issue with the camera anyway
[12:35] <daveake> But basically if the camera is taking good images (correct width/height ... nothing to cause the ssdv conversion to fail) and partition isn't full, then SSDV should keep going
[12:36] <daveake> Yeah does sound likely.
[12:36] <daveake> Once the camera stops working that's it till reboot
[12:38] <daveake> Raspbian Stretch was the one that had (at least) one dodgy version
[12:38] <KD4BFP> Maybe I can set some sort of watchdog to track images and try to reset the camera
[12:38] <daveake> RPi don't know what they fixed or when, but it affects RPi V2 camera (the current, Sony one)
[12:38] <daveake> http://www.daveakerman.com/?page_id=2631
[12:39] <daveake> Well, if you find out how to reset the camera without rebooting, let me know!
[12:39] <daveake> As for watchdog, maybe raspistill returns an error code - that would be easier to trap
[12:40] <KD4BFP> Nice clean Buster image coming up!
[12:40] <daveake> :)
[12:41] <daveake> If you can repeat it on the ground with the old image then test with the new one, that would be very helpful
[12:41] <KD4BFP> I'll do that
[12:41] <daveake> Remember that PITS only takes full images once airborne (once above the high=xxx value)
[12:41] <KD4BFP> Here's the flight report so far: http://www.ncnearspace.org/missions/nsl-75
[12:41] <daveake> So Set high=0 and run a soak test
[12:43] <daveake> OK potentially you have power issues related to the camera
[12:43] fl__0 (unknown@unaffiliated/fl-0/x-7355575) joined #highaltitude.
[12:43] fl_0 (unknown@unaffiliated/fl-0/x-7355575) left irc: Ping timeout: 264 seconds
[12:45] <fsphil> do you detect undervolt and transmit it in the telemetry daveake?
[12:45] <fsphil> might be useful if you don't
[12:45] <daveake> hmmm good idea
[12:46] <KD4BFP> I ran it on my bench power supply and dialed down the voltage. The lora quit before the camera. Well on the bench at least...
[12:46] <fsphil> https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=147781&start=50#p972790
[12:46] <KD4BFP> (cause I'm sending 100mW in US)
[12:47] <fsphil> overtemp might be useful to have too
[12:48] <KD4BFP> That would be cool !
[12:48] <daveake> GPU temp is included in that setup
[12:49] <daveake> Well, with existing PITS s/w you can add whatever fields you like with a little Python (example included)
[12:50] fl__0 (unknown@unaffiliated/fl-0/x-7355575) left irc: Ping timeout: 245 seconds
[12:50] <daveake> For bench testing do set high=0 so it uses higher resolution on the camera which, I'd expect, pulls more current and/or for longer
[12:51] <KD4BFP> Roger
[12:51] <daveake> Otherwise it takes smaller images on the basis that who wants large images of the launcher staring at the tracker? :)
[12:52] fl_0 (unknown@unaffiliated/fl-0/x-7355575) joined #highaltitude.
[12:52] <KD4BFP> I usually get a bunch of crotch shots.
[12:52] <KD4BFP> But only at public events when everyone is looking at ssdv.habhub
[12:53] <daveake> lol
[12:53] <daveake> Yeah I nearly mentioned that that happens a lot too :D
[12:54] <daveake> Maybe I should choose "best image" based on content not image size .....
[12:54] <KD4BFP> We do a lot of school and Maker Faire type events. We project up on big screens. Always happens
[12:54] <daveake> "Oh look 20% of the image is black sky that's a good one"
[12:54] <KD4BFP> :)
[12:54] <daveake> heh
[12:55] <daveake> I can imagine the comments testing this ....
[12:56] <daveake> "Whay are you standing in front of that camera so it takes images of your crotch?" "Well dear, I'm training the AI not to select images like that"
[12:57] <fsphil> reference image, https://i.imgur.com/ngHWeNr.jpg
[13:00] <daveake> Hmmm tricky :D
[13:06] labjg (~labjg@150.203.88.49) joined #highaltitude.
[13:14] labjg_ (~labjg@150.203.88.49) joined #highaltitude.
[13:18] labjg (~labjg@150.203.88.49) left irc: Ping timeout: 245 seconds
[13:30] <PE2BZ> KD4BFP, 100 mW output power, which TX module you use for that ?
[13:31] <KD4BFP> <silly grin> I am able to do that with the normal Lora 433 or 915 chips, but I try to keep the duty cycle down. But I also have the 1 WATT !! version also.
[13:35] <KD4BFP> Last week I used a standard RFM98W and transmitted every 2.5 seconds. I wouldn't have been surprised if it burnt out, but it ran fine and transmitted for 22 hours on 3 AA batteries
[13:36] <KD4BFP> Where I live, we have a rather high noise floor at 70cm, so I really appreciate being able to go over 10mW
[13:36] <KD4BFP> (Granted the high noise floor is due to a bunch of us slamming the airwaves)
[13:37] <KD4BFP> I also use the TTGO T-Beam units a lot. They work well at 100mW and are pretty reliable for $26USD Lora trackers
[13:38] <KD4BFP> Friday I'm flying a 915MHz T-Beam at 100mW
[13:39] <daveake> I've been meaning to get one of those things to play with
[13:40] <KD4BFP> Your code runs on them readily. Good code :)
[13:41] <daveake> Ah right :)
[13:41] Action: daveake removes 1 item from todo list
[13:43] <daveake> Also it could be made into a receiver to connect to Android over bluetooth
[13:43] <daveake> prolly that code would "just work" (TM) too
[13:43] <daveake> Depends how the bluetooth is connected
[13:44] <KD4BFP> That's why I was asking you for your Android code the other day
[13:45] <KD4BFP> They also make ones with little OLED screens
[13:45] <daveake> Yes, amazing what you get for the money
[13:45] <SA6BSS-Mike> I have one of those, use it to rx ww sondes whn im hunting them dow
[13:45] <daveake> I don't fancy staring at a little OLED to track a balloon tho
[13:45] <SA6BSS-Mike> n
[13:46] <daveake> Yeah I saw that someone wrote code to get the LoRa module to decode sondes
[13:46] <SA6BSS-Mike> its working great :)
[13:46] RocketBoy (054496ae@054496ae.skybroadband.com) joined #highaltitude.
[13:46] <KD4BFP> With the TBeam, you could make a self contained "tracker watch" that would give you distance to target
[13:47] <daveake> Yes. You could add a couple of buttons and have a basic UI to select lora/sonde, frequency etc
[13:47] <daveake> Just need a bigger display ideally
[13:47] RocketBoy (054496ae@054496ae.skybroadband.com) left irc: Remote host closed the connection
[13:47] RocketBoy (054496ae@054496ae.skybroadband.com) joined #highaltitude.
[13:47] <SA6BSS-Mike> the fw im using at the moment acts like a server so I have the phone screen , big enough :)
[13:47] <daveake> With my eyesight I need to remove glasses to read a watch that small :)
[13:48] <daveake> yes I think a phone link makes a lot of sense
[13:48] <SA6BSS-Mike> it listen for my wifi router for 10sec then it switch over to AP mode if its not in range
[13:49] <daveake> neat
[14:05] <PE2BZ> KD4BFP, My max was 17.8 dBm (60 mW) but that ran 4 hours on 432 MHz with 100% duty cycle without problems. That was wenet transmitting in about 250 kHz bandwidth
[14:06] <PE2BZ> Have to measure battery consumption when running 17.8 instead of 10 dBm :-)
[14:06] <SIbot1> In real units: 8 in = 20.32 cm
[14:06] <PE2BZ> How could we survive without SIbot1 ;-)
[14:08] <daveake> sometimes, better :)
[14:12] SA6BSS-Mike|2 (~SA6BSS-Mi@h-155-4-222-217.NA.cust.bahnhof.se) joined #highaltitude.
[14:15] SA6BSS-Mike (~SA6BSS-Mi@h-155-4-222-217.NA.cust.bahnhof.se) left irc: Ping timeout: 264 seconds
[15:04] YO9GJX (~YO9GJX@109.100.112.75) joined #highaltitude.
[15:12] <SpacenearUS> New position from 03W8MV-11 after 0314 hours silence - 12https://tracker.habhub.org/#!qm=All&q=W8MV-11
[17:43] <SpacenearUS> New vehicle on the map: 03KN4VS-1 - 12https://tracker.habhub.org/#!qm=All&q=KN4VS-1
[18:36] dustinm` (~dustinm@static.38.6.217.95.clients.your-server.de) left irc: Ping timeout: 245 seconds
[18:42] dustinm` (~dustinm@static.38.6.217.95.clients.your-server.de) joined #highaltitude.
[18:44] RocketBoy (054496ae@054496ae.skybroadband.com) left irc: Remote host closed the connection
[19:01] Kodar_ (~Kodar@93-142-47-115.adsl.net.t-com.hr) joined #highaltitude.
[19:02] drsnik (~drsnik@gate3.ima.cz) left irc: Quit: Leaving
[19:03] <PE2BZ> SA6BSS-Mike|2, any info on the tracker ? HW, Radio, antenna ?
[19:03] <PE2BZ> take your time, will read tomorrow :-)
[19:05] Kodar (~Kodar@93-139-135-141.adsl.net.t-com.hr) left irc: Ping timeout: 245 seconds
[19:16] drsnik (~drsnik@gate3.ima.cz) joined #highaltitude.
[19:22] <SA6BSS-Mike|2> PE2BZ: ...
[19:22] <SA6BSS-Mike|2> evening
[19:24] <SA6BSS-Mike|2> its a 4,6gram om3bc tracker under a prestreached (0,640psi) clear foil using a si4060 with a so "good" filter probably filtering out moste of it 10mW power so it gets maby 5mW out to the antenna
[19:25] Nick change: SA6BSS-Mike|2 -> SA6BSS-Mike
[19:26] <SA6BSS-Mike> teh anntena is a dipole 49cm up up and 49 cm pointing down
[19:27] <SA6BSS-Mike> got a new fw from om3bc / Joseph that supports the cheap atgm336 gps module, thats whats onboard the tracker
[19:36] <SpacenearUS> New position from 03APJHAB after 037 hours silence - 12https://tracker.habhub.org/#!qm=All&q=APJHAB
[19:40] geheimnis` (~geheimnis@23.226.237.192) left irc: Ping timeout: 245 seconds
[19:41] geheimnis` (~geheimnis@23.226.237.192) joined #highaltitude.
[20:04] chris_99 (uid26561@gateway/web/irccloud.com/x-fjijckxtkwjsjpie) left irc:
[20:29] <SpacenearUS> New vehicle on the map: 03MODBN1 - 12https://tracker.habhub.org/#!qm=All&q=MODBN1
[20:47] mickod (25e4f32b@37.228.243.43) joined #highaltitude.
[20:47] KD4BFP (4080de83@64.128.222.131) left irc: Remote host closed the connection
[20:50] mickod (25e4f32b@37.228.243.43) left irc: Remote host closed the connection
[20:51] Mick54 (25e4f32b@37.228.243.43) joined #highaltitude.
[21:05] SA6BSS-Mike (~SA6BSS-Mi@h-155-4-222-217.NA.cust.bahnhof.se) left irc: Ping timeout: 264 seconds
[21:06] SA6BSS-Mike (~SA6BSS-Mi@h-155-4-222-217.NA.cust.bahnhof.se) joined #highaltitude.
[21:10] Mick54 (25e4f32b@37.228.243.43) left irc: Remote host closed the connection
[21:18] <SpacenearUS> New position from 03ICT3 after 0317 hours silence - 12https://tracker.habhub.org/#!qm=All&q=ICT3
[21:26] <SpacenearUS> New vehicle on the map: 03mickod_chase - 12https://tracker.habhub.org/#!qm=All&q=mickod_chase
[21:33] <SpacenearUS> New position from 03EA1IDZ-11 after 034 days silence - 12https://tracker.habhub.org/#!qm=All&q=EA1IDZ-11
[21:59] Lahti (~Lahti@dyvym10mtq0j5ck20nvzy-4.rev.dnainternet.fi) left irc: Quit: Lähdössä
[22:00] RocketBoy (054496ae@054496ae.skybroadband.com) joined #highaltitude.
[22:02] Laurenceb_ (~laurence@140.141.208.46.dyn.plus.net) joined #highaltitude.
[22:04] michal_f (~mfratczak@83-238-169-175.static.ip.netia.com.pl) joined #highaltitude.
[22:04] RocketBoy (054496ae@054496ae.skybroadband.com) left irc: Remote host closed the connection
[22:07] Kodar_ (~Kodar@93-142-47-115.adsl.net.t-com.hr) left irc: Read error: Connection reset by peer
[22:14] michal_f (~mfratczak@83-238-169-175.static.ip.netia.com.pl) left irc: Ping timeout: 246 seconds
[22:17] <SpacenearUS> New vehicle on the map: 03LU1ESY-3 - 12https://tracker.habhub.org/#!qm=All&q=LU1ESY-3
[22:17] michal_f (~mfratczak@83-238-169-175.static.ip.netia.com.pl) joined #highaltitude.
[22:31] <michal_f> ping Darkside
[22:35] <SpacenearUS> New position from 03LU1ESY-13 after 03a day silence - 12https://tracker.habhub.org/#!qm=All&q=LU1ESY-13
[22:36] <Darkside> michal_f: saw the response, can't test it until later this evening
[22:37] <michal_f> no prob
[22:54] snaked (~snaked@pdpc/supporter/active/snaked) left irc: Remote host closed the connection
[22:54] snaked (~snaked@pdpc/supporter/active/snaked) joined #highaltitude.
[23:02] qyx (~qyx@gw2.krtko.org) left irc: Read error: Connection reset by peer
[23:06] qyx (~qyx@gw2.krtko.org) joined #highaltitude.
[23:11] michal_f (~mfratczak@83-238-169-175.static.ip.netia.com.pl) left irc: Remote host closed the connection
[23:27] <SpacenearUS> New vehicle on the map: 03Lachy_RX_chase - 12https://tracker.habhub.org/#!qm=All&q=Lachy_RX_chase
[23:40] labjg_ (~labjg@150.203.88.49) left irc: Ping timeout: 245 seconds
[00:00] --- Thu Sep 12 2019