[00:02] New vehicle on the map: 03VK5QI-9_chase - 12https://tracker.habhub.org/#!qm=All&q=VK5QI-9_chase [00:17] New vehicle on the map: 03VK5NE_chase - 12https://tracker.habhub.org/#!qm=All&q=VK5NE_chase [00:52] New position from 03WB0URW-12 after 0318 hours silence - 12https://tracker.habhub.org/#!qm=All&q=WB0URW-12 [00:56] New position from 03KB6CAG-14 after 034 days silence - 12https://tracker.habhub.org/#!qm=All&q=KB6CAG-14 [00:59] New vehicle on the map: 03VK5ST_chase - 12https://tracker.habhub.org/#!qm=All&q=VK5ST_chase [01:13] SpeedEvil (~quassel@tor/regular/SpeedEvil) joined #highaltitude. [01:13] BitEvil (~quassel@tor/regular/SpeedEvil) left irc: Read error: Connection reset by peer [01:41] happysat (~katpoep@82-169-224-141.biz.kpn.net) left irc: Remote host closed the connection [01:50] happysat (~katpoep@82-169-224-141.biz.kpn.net) 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:06] Laurenceb (~laurence@48.177.208.46.dyn.plus.net) left irc: Ping timeout: 268 seconds [04:08] Axone (~Axone@lfbn-idf1-1-170-248.w82-124.abo.wanadoo.fr) left irc: Quit: ZNC 1.6.6+deb1ubuntu0.2 - http://znc.in [04:09] Axone (~Axone@lfbn-idf1-1-170-248.w82-124.abo.wanadoo.fr) joined #highaltitude. [06:25] YO3ICT (~YO3ICT@86.121.1.149) joined #highaltitude. [06:34] YO3ICT (YO3ICT@86.121.1.149) left #highaltitude. [06:54] FireFighter (~firefight@2601:44:4380:605c:7147:8d54:ca83:38c) joined #highaltitude. [07:04] Kodar (~Kodar@93-142-44-39.adsl.net.t-com.hr) joined #highaltitude. [07:37] SA6BSS-Mike (~SA6BSS-Mi@85.24.253.14) joined #highaltitude. [07:38] SA6BSS-Mike2 (~SA6BSS-Mi@94.254.35.251) joined #highaltitude. [07:40] SA6BSS-Mike1 (~SA6BSS-Mi@94.254.35.251) left irc: Ping timeout: 246 seconds [07:42] SA6BSS-Mike (~SA6BSS-Mi@85.24.253.14) left irc: Ping timeout: 246 seconds [07:50] YO9GJX (~YO9GJX@109.100.112.132) left irc: Remote host closed the connection [08:06] SA6BSS-Mike (~SA6BSS-Mi@94.254.35.251) joined #highaltitude. [08:07] SA6BSS-Mike2 (~SA6BSS-Mi@94.254.35.251) left irc: Ping timeout: 246 seconds [08:13] SA6BSS-Mike (~SA6BSS-Mi@94.254.35.251) left irc: Ping timeout: 246 seconds [08:13] SA6BSS-Mike (~SA6BSS-Mi@94.254.35.251) joined #highaltitude. [08:14] SA6BSS-Mike1 (~SA6BSS-Mi@94.254.35.251) joined #highaltitude. [08:17] SA6BSS-Mike (~SA6BSS-Mi@94.254.35.251) left irc: Ping timeout: 246 seconds [08:50] LazyLeopard (~irc-clien@chocky.lazyleopard.org.uk) joined #highaltitude. [09:00] Lahti (~Lahti@dz2hbpyk9hk0n83c0mf-4.rev.dnainternet.fi) joined #highaltitude. [10:02] Chrischan (~chrischan@ip5f5aff74.dynamic.kabel-deutschland.de) joined #highaltitude. [10:03] YO9GJX (~YO9GJX@109.100.112.132) joined #highaltitude. [10:41] itsonlyluis_ (~luis@cpc156981-wake10-2-0-cust556.17-1.cable.virginm.net) left irc: Ping timeout: 256 seconds [10:46] New position from 03PA3FNT-LORA after 033 days silence - 12https://tracker.habhub.org/#!qm=All&q=PA3FNT-LORA [10:48] itsonlyluis_ (~luis@cpc156981-wake10-2-0-cust556.17-1.cable.virginm.net) joined #highaltitude. [10:52] PE1PSI-2 (~PE1PSI-3@2001:1c05:270b:9f00:44bc:2400:9369:5d44) joined #highaltitude. [11:02] New vehicle on the map: 03CC2XYZ - 12https://tracker.habhub.org/#!qm=All&q=CC2XYZ [11:30] GM .. I have something strange with habhub.. I see myload last received 5h39 min ago, but can be 14:56:35 as mentioned on the map. When I select show only last 1 hour, it is still shown on the map. My payload is still uploading and I see it on the logtail [2020-12-29 11:28:30,128] INFO habitat.parser MainThread: Parsing [ascii] '$$PC4L-4FSK,502,11:28:25,51.49017,3.82359,0,0,6,19,3.51*8A75 [11:30] but can be = but that can´t be [11:30] probably a fun issue with dates [11:31] i suspect theres some data from your payload which is in the 'future' [11:32] {"position_id":"69739042","mission_id":"0","vehicle":"PC4L-4FSK","server_time":"2020-12-29 05:49:15.009564","gps_time":"2020-12-29 13:56:35","gps_lat":"51.49016","gps_lon":"3.82364","gps_alt":"0","gps_heading":"","gps_speed":"0","picture":"","temp_inside":"","data":{"battery":"3.8","satellites":6,"temperature_internal":22},"callsign":"PC4L","sequence":"350"}, [11:32] somehow it got a GPS time of 13:56Z and uploaded it.. [11:33] New position from 03N4XWC-1 after 0310 hours silence - 12https://tracker.habhub.org/#!qm=All&q=N4XWC-1 [11:33] the tracker might have ended up with teh wrong time somehow [11:33] this is using deep sleep mode? [11:33] yep [11:34] latest git pull? [11:34] yesterday [11:34] i know i added some more checks on the fix quality [11:34] hmm [11:34] maybe not enough :/ [11:34] :) [11:34] still, surprised it ended up with that incorrect time [11:35] but yeah, on sequence number 350, it woke up, and had the wrong time :/ [11:36] and since then it´s not updating anymore? [11:37] this is because the datanew.php thing provides positions in gps time order, not arrival tiem at the server [11:37] to deal a bit with out-of-order packets arriving [11:38] and afaik there's no way to fix this... just need to wait for that later time to pass [11:39] ah okay.. will see after 3 days :) [11:39] nah, just a few hours [11:39] as of the tiem of that position, (13:56Z) it should come good [11:39] Do I have to stop uploading first? [11:40] shouldnt [11:40] RR [11:40] but yeah, it makes me wonder if the payload did actually send that time, and if so, how the hell did it get it [11:40] the payload shouldn't got into transmit mode unless the GPS fix is valid in a few different ways [11:41] New position from 03RSIST after 0310 hours silence - 12https://tracker.habhub.org/#!qm=All&q=RSIST [11:41] Hmmm I stopped horus-gui to see if the problem was there, otherwist I could have checked for that specific time [11:41] https://github.com/darksidelemm/RS41HUP/blob/master/ublox.c#L169 [11:42] might need to tweak the paramters i used here [11:42] the tDop parameter in particular might be way too big [11:44] is tdop affecting the time?! [11:44] yes it is :) [11:45] still, a tDop of 10 shouldn't be hours out [11:45] Time Dilution of Precision I learn every day [11:45] i have seen the GPS come out of deep sleep starting from 00:00 [11:45] but... not with a competely incorrect time [11:47] so yeah, i dunno :/ [11:47] maybe better off using powersave mode instead of deep sleep [11:47] power consumption when in low power tracking mode isn't *too* bad [11:49] Will try that later.. deep sleep is amazing, for now I MUST see how long it will sent on one li-ion [11:49] hmm, tDop only affects the timepulse output [11:49] not time/date [11:51] soooooo *shrug* [11:52] it´s almost 14:56 :) [11:52] let´s wait and see [11:53] had to translate *shrug* in dutch ¨schoudersophalend¨ then I know what you mean :) [11:53] haha [11:54] did you get auto_rx going again? [11:57] no.. still puzzeling [11:58] I must be something with flask [11:58] worst case start from scratch image :/ [11:58] hopefully i can upgrade to the latest socketio soon so this isnt an issue [11:59] I´m waiting for my brother to compare some files and versions [12:00] python-engineio==4.0.0 [12:00] python-socketio==5.0.3 [12:01] Flask==1.1.2 [12:01] Flask-SocketIO==2.1 [12:02] ah crap [12:02] maybe i need to pin python-socketio too [12:03] python-socketio comes from the system apckages, i wonder if that got updarted [12:04] hmm wait no [12:05] Name: python-socketio [12:05] Version: 4.6.1 [12:06] not sure how your flask-socketio version is 2.1 [12:06] thats very old [12:08] let me see if I can update that :) [12:08] but 'm also not sure how python-socketio is so new [12:09] we might have to pin more than just flask-socketio [12:09] can you try: sudo pip3 install python-socketio==4.6.1 python-engineio==3.14.2 flask-socketio==4.3.2 [12:12] Requirement already satisfied: python-socketio==4.6.1 in /usr/local/lib/python3.8/dist-packages (4.6.1) [12:12] Requirement already satisfied: python-engineio==3.14.2 in /usr/local/lib/python3.8/dist-packages (3.14.2) [12:12] Requirement already satisfied: flask-socketio==4.3.2 in /usr/local/lib/python3.8/dist-packages (4.3.2) [12:12] Requirement already satisfied: Flask>=0.9 in /usr/local/lib/python3.8/dist-packages (from flask-socketio==4.3.2) (1.1.2) [12:12] Requirement already satisfied: six>=1.9.0 in /usr/lib/python3/dist-packages (from python-engineio==3.14.2) (1.14.0) [12:12] Requirement already satisfied: Jinja2>=2.10.1 in /usr/local/lib/python3.8/dist-packages (from Flask>=0.9->flask-socketio==4.3.2) (2.11.2) [12:12] Requirement already satisfied: itsdangerous>=0.24 in /usr/local/lib/python3.8/dist-packages (from Flask>=0.9->flask-socketio==4.3.2) (1.1.0) [12:12] hmm [12:12] Requirement already satisfied: click>=5.1 in /usr/lib/python3/dist-packages (from Flask>=0.9->flask-socketio==4.3.2) (7.0) [12:12] Requirement already satisfied: Werkzeug>=0.15 in /usr/local/lib/python3.8/dist-packages (from Flask>=0.9->flask-socketio==4.3.2) (1.0.1) [12:12] so... the versions already seem right [12:12] Requirement already satisfied: MarkupSafe>=0.23 in /usr/lib/python3/dist-packages (from Jinja2>=2.10.1->Flask>=0.9->flask-socketio==4.3.2) (1.1.0) [12:13] he is very satisfied already :) [12:13] so as for why its not working :/ [12:13] we can use the shrug again [12:13] hmm [12:13] i woner if you have two copies of python around [12:13] i see /usr/local/lib/python3.8 and /usr/lib/python3 [12:14] oh wait i think /usr/lib/python3 is wher ethe system packages go [12:14] is this on a rpi, and is it being used for anything else? [12:15] no ubuntu pc.. also using openwebrx / habwspr/ ttnhabbridge wsjtx and more goodies [12:16] so theres possibly some conflicting requirements here.. [12:17] New position from 03LU1ESY-11 after 0314 days silence - 12https://tracker.habhub.org/#!qm=All&q=LU1ESY-11 [12:17] i have pyton 2.7 3 3.6 3.8 and 3.9 in that map :) [12:17] i mean, this is what python venvs are intended to deal with [12:20] let me try some purge commands [12:20] :/ [12:22] the only thing working later is auto_rx :) [12:24] i think i need to write some instructions on how to run auto_rx using a virtualenv [12:24] to avoid these issues [12:26] Removing python3 (3.8.2-0ubuntu2) ... Removing python-all-dev (2.7.17-2ubuntu4) ...Removing python3.6 (3.6.9-1~18.04ubuntu1.1) ... Removing python3.8-dev (3.8.5-1~20.04) ... [12:26] so now let´s see [12:38] no desktop, no network link, python3 command not found.. I say.. where´s my linux boot stick :) [12:57] New position from 03DL1XH-4FSK after 032 days silence - 12https://tracker.habhub.org/#!qm=All&q=DL1XH-4FSK [13:09] SpirosMakris (02549215@ppp-2-84-146-21.home.otenet.gr) joined #highaltitude. [13:10] hi, I'm looking for some help to set up a Flextrak, is this an appropriate place to ask questions about it? [13:11] daveake: ^ [13:20] I take it that's a yes :) [13:29] well, i don thave the answers, but daveake would [13:29] depends if he is around tho [13:36] I'll give it some time and send him an email if he doesn't show up. I wasn't sure if spamming his email adress with technical issues is ok. oh well. [13:41] michael_haberler (c1e42fa7@ns.stiwoll.mah.priv.at) joined #highaltitude. [13:47] New position from 03KN4IUD-15 after 0318 hours silence - 12https://tracker.habhub.org/#!qm=All&q=KN4IUD-15 [13:50] New vehicle on the map: 03V200-L - 12https://tracker.habhub.org/#!qm=All&q=V200-L [13:50] New vehicle on the map: 03V200-R - 12https://tracker.habhub.org/#!qm=All&q=V200-R [14:00] SpirosMakris: the best is to stay connected to the channel [14:02] YO3ICT (~YO3ICT@86.121.1.149) joined #highaltitude. [14:04] Will do, thank. I'm waiting for my tracker to find a gps connection for now. Should I be getting any kind of telemetry packets from it while it has no valid gps connection? [14:07] @darkside >> build from scrap, only auto_rx installed.. working fine!! [14:44] PC4L: : [14:44] ) [15:03] SpirosMakris: Yes it starts sending immediately [15:03] itsonlyluis_ (~luis@cpc156981-wake10-2-0-cust556.17-1.cable.virginm.net) left irc: Ping timeout: 272 seconds [15:05] itsonlyluis_ (~luis@cpc156981-wake10-2-0-cust556.17-1.cable.virginm.net) joined #highaltitude. [15:12] itsonlyluis_ (~luis@cpc156981-wake10-2-0-cust556.17-1.cable.virginm.net) left irc: Ping timeout: 265 seconds [15:17] itsonlyluis_ (~luis@cpc156981-wake10-2-0-cust556.17-1.cable.virginm.net) joined #highaltitude. [15:24] thecivvi_ (~thecivvie@86-42-227-211-dynamic.agg7.cdn.mvw-sla.eircom.net) joined #highaltitude. [15:26] thecivvie (~thecivvie@86-42-227-204-dynamic.agg7.cdn.mvw-sla.eircom.net) left irc: Ping timeout: 246 seconds [15:43] New position from 03IDA-4FSK after 03a day silence - 12https://tracker.habhub.org/#!qm=All&q=IDA-4FSK [15:46] New position from 03IDA-RTTY after 03a day silence - 12https://tracker.habhub.org/#!qm=All&q=IDA-RTTY [15:56] blb4393 (~chatzilla@x59cc8701.dyn.telefonica.de) joined #highaltitude. [16:07] Kodar_ (~Kodar@93-142-12-204.adsl.net.t-com.hr) joined #highaltitude. [16:11] Kodar (~Kodar@93-142-44-39.adsl.net.t-com.hr) left irc: Ping timeout: 260 seconds [16:14] daveake ok so I think I have two problems here. I am using the OTG dongle with your windows programme and the default setup of the flextrak. I power up the flextrak using a power bank and leave it outside where it can see the sky. There are buildings around and it doesn't ever find a connection (the flashing led stays red). [16:14] However I do think it should find some connection after a while. I will try this on the roof as well later/tomorrow just o be sure. [16:16] If you never get a GPS lock, then assuming a clear view of most of the sky and nothing near to it interfering, then speak to Anthony@uputronics to get it swapped. [16:16] the other problem is that when I connect the dongle I can't see any telemetry pakets coming in from the traker, it only gives RSSI values. Should I be getting anything before I get a gps lock? [16:17] I have a second unit as well, it it worth taking it out of the box and trying it? [16:17] Yes. You probably need to tune up or down a few kHz to receive [16:18] is there any feedback from the dongle that I did indeed change the settings etc? although i suspect it is fine because I can see the RSSI change depending on the mode I set it to [16:18] The radio modules aren't exactly on whatever frequency you choose, and can bet it by several kHz. If the 2 modules are out in opposite directions then that can be enough to stop packets getting through. [16:18] All assuming you have same mode set at reach side of course [16:19] I'm going to add a search function at some point. [16:19] I left the tracker versions to default and the .ini said mode 1, so I assume they are in the correct mode. [16:19] Ok [16:19] If you're using the pi then there config is on there. [16:20] If standalone then use my Windows configuration program [16:20] I am using it, and left everything to their default for now [16:26] about the frequency, I'm going to try a few different settings in hopes it might work. So I start from 434.225Mhz (default) and change that by 3-5kHz until I see something? How much should I wait for packets to come in? I have both units in the same toom a few meters apart and both have an antenna fitted (flextrak just has this pigtail thing for [16:26] now) [16:39] New position from 03PS-80 after 0313 hours silence - 12https://tracker.habhub.org/#!qm=All&q=PS-80 [16:43] YO3ICT (YO3ICT@86.121.1.149) left #highaltitude. [16:47] Mode 1 packets are about every 2 seconds, so not long [16:47] I''d switch in 2kHz steps and you shouldn't need to go further than about 6kHz [16:47] Do it in both directions [17:22] hm ok let me try this then [17:42] SpirosMakris (02549215@ppp-2-84-146-21.home.otenet.gr) left irc: Remote host closed the connection [18:01] SpirosMakris (02549215@ppp-2-84-146-21.home.otenet.gr) joined #highaltitude. [18:10] I tried sweeping the frequencies around 434.225Mhz where my tracker is set and couldn't pick up anything. I went with 1khz steps and waited a few seconds between changes. I opened up the .ini file and verified that both are in mode 1 [18:11] snaked (~snaked@pdpc/supporter/active/snaked) left irc: Remote host closed the connection [18:12] snaked (~snaked@pdpc/supporter/active/snaked) joined #highaltitude. [18:12] Laurenceb (~laurence@65.177.208.46.dyn.plus.net) joined #highaltitude. [18:20] hm ok I unboxed the second unit, connected the pi to the board and just powered it up with a power bank (I turned the other one off). I'm still not getting anything, so I guess the problem lies at the reciever rather than the trackers? [18:22] To connect to the receiver dongle, I plugged it to the computer, run the lora serial gateway programme and selected the appropriate port. I can see RSSI numbers and have set the frequency to 434.225, and mode set to 1. then i press "set". The white box is not showing anything and all other stats like sentences etc are blank. [18:23] the situation is similar when i use it from my phone (the phone app freezes for me but the tablet one works more or less ok, despite the small screen) [18:25] PH1M (~PH1M@2a02-a452-d93d-1-b848-b4f9-7527-d03d.fixed6.kpn.net) left irc: Remote host closed the connection [18:25] PH1M (~PH1M@84-86-57-116.fixed.kpn.net) joined #highaltitude. [18:33] SA6BSS-Mike (~SA6BSS-Mi@155.4.14.10) joined #highaltitude. [18:34] blb4393 (~chatzilla@x59cc8701.dyn.telefonica.de) left irc: Quit: ChatZilla 0.9.93 [Waterfox 56.3/MOZ_BUILDID] [18:34] Does this dongle use the open source lora serial firmware I found on github? when I open up an arduino serial monitor and try to send commands as they are listed in github (ie, F434.225) I don't get any response back, is that correct? Should I program the dongle using the latest version of lora serial? I was planning to make my own receiver with a [18:34] teensy but I'm missing an SMA connector, so it has to wait. [18:36] SA6BSS-Mike1 (~SA6BSS-Mi@94.254.35.251) left irc: Ping timeout: 246 seconds [18:37] PE1PSI-2 (~PE1PSI-3@2001:1c05:270b:9f00:44bc:2400:9369:5d44) left irc: Ping timeout: 268 seconds [18:38] drsnik__ (~drsnik@gate3.ima.cz) left irc: Quit: Leaving [18:45] LIERO (~no@unaffiliated/liero) left irc: Quit: ZNC 1.8.2 - https://znc.in [18:45] LIERO (~no@vmi473477.contaboserver.net) joined #highaltitude. [18:48] Laurenceb (~laurence@65.177.208.46.dyn.plus.net) left irc: Ping timeout: 256 seconds [18:49] Laurenceb (~laurence@65.177.208.46.dyn.plus.net) joined #highaltitude. [18:57] drsnik (~drsnik@gate3.ima.cz) joined #highaltitude. [19:01] ge [19:04] PA3CPF (~androirc@84-81-60-246.fixed.kpn.net) joined #highaltitude. [19:06] hm, I used putty and managed to send commands and get confirmations from it no problem, so the dongle should be just fine. I verified it gets the commands normally from the windows application as well, so that's not a problem either. I tried manually picking the correct settings from the drop down menus according to what the firmware says but that [19:06] didn't work either. [19:12] sri SpirosMakris i can´t help, i havent played much with LORA [19:15] me neither, tbh, thankfully I have some experience with embedded systems so I'm not at a complete loss (yet). [19:18] OZ1SKY_Brian: thanks for joining our journey, appreciated :-) [19:20] hi Bernd, looks like they are going to stay around me :-) [19:20] drsnik (~drsnik@gate3.ima.cz) left irc: Quit: Leaving [19:21] Hi Brain, that´s why you are so important on that trip :-) [19:21] ill let it run as long as in range, no problem. [19:22] typo, Brian... it is a late x-mas gift [19:22] lol well lets hope when it lands its near by, then ill accept :-) [19:23] :-) [19:23] drsnik (~drsnik@gate3.ima.cz) joined #highaltitude. [19:23] drsnik (~drsnik@gate3.ima.cz) left irc: Remote host closed the connection [19:30] drsnik (~drsnik@gate3.ima.cz) joined #highaltitude. [19:31] drsnik (~drsnik@gate3.ima.cz) left irc: Remote host closed the connection [19:39] Bernd_DL1XH yours is tx every 5min ich? [19:39] ish [19:41] i see some spikes now and then on the freq, is that one of the payloads making those? [19:41] about 4:30 in avarage. This is the new deep sleep mode. Should save power. But is not heating inside the sonde anymore [19:42] the sounds are beeps, for those who need to tune the QRG [19:42] ah ok i see [19:44] it is fun to watch the WF and listen to both [19:44] yeah its very nice they are on the same qrg and dont seems to be an issue, as they dont tx at the same time [19:45] so makes tracking very easy and the excelent GUI Darkside made, is just wonderfull [19:46] it is! thumbs up! [19:46] so its 2 RS41 ? [19:46] yep [19:46] RRR [19:47] did you remove the pressure to save power ? [19:47] sensor i mean [19:47] my sonde has the same problem as the Vaisala...sometimes it just sends 0000 as coordinates :-)) [19:47] all removed [19:48] ok good [19:48] but the power saving comes from the latest FW made by darkside [19:48] yes a saw it was talked about here [19:49] yours should last alot longer as your rtty is also off [19:50] but my enemy here is the repeaters, here in DK we have output on 434.5 to 435 [19:50] too my luck there are no locals on 434.650 [19:51] or 434.675 [19:52] not seen any on 434.6625 [20:02] good for us :-) [20:21] drsnik (~drsnik@gate3.ima.cz) joined #highaltitude. [20:28] Suterusu (~eyer@Morrigan.Armed.Me.Uk) left irc: Ping timeout: 240 seconds [20:42] I made it work, finally! turns out it needed a firmware upgrade, now everything is in order. [20:45] Suterusu (~eyer@host-78-149-94-120.as13285.net) joined #highaltitude. [21:01] great good work... [21:20] PA3CPF (~androirc@84-81-60-246.fixed.kpn.net) left irc: Ping timeout: 240 seconds [21:28] pa3cpf (~androirc@84-81-60-246.fixed.kpn.net) joined #highaltitude. [21:35] Bernd_DL1XH: yes, just be careful abotu deep sleep mode, PC4L reported it sending an incorrect time [21:36] with the latest firmware it *should* never send zeros when it comes out of deep sleep. but... [21:36] SA6BSS-Mike1 (~SA6BSS-Mi@94.254.35.251) joined #highaltitude. [21:39] Darkside: no problems so far, just a few times sending 0000 as lon and lat - in live signal . But stable now - just very cold :-) it is not latest FW [21:39] SA6BSS-Mike (~SA6BSS-Mi@155.4.14.10) left irc: Ping timeout: 246 seconds [21:55] thecivvi_ (~thecivvie@86-42-227-211-dynamic.agg7.cdn.mvw-sla.eircom.net) left irc: [22:03] LIERO (~no@vmi473477.contaboserver.net) left irc: Changing host [22:03] LIERO (~no@unaffiliated/liero) joined #highaltitude. [22:21] Lahti (~Lahti@dz2hbpyk9hk0n83c0mf-4.rev.dnainternet.fi) left irc: Quit: Lähdössä [22:38] Laurenceb (~laurence@65.177.208.46.dyn.plus.net) left irc: Ping timeout: 240 seconds [22:43] SpirosMakris (02549215@ppp-2-84-146-21.home.otenet.gr) left irc: Remote host closed the connection [22:52] Laurenceb (~laurence@65.177.208.46.dyn.plus.net) joined #highaltitude. [23:00] New vehicle on the map: 03VK5NE_chase - 12https://tracker.habhub.org/#!qm=All&q=VK5NE_chase [23:07] New position from 034FSKTEST after 034 days silence - 12https://tracker.habhub.org/#!qm=All&q=4FSKTEST [23:17] New position from 03N4XWC-1 after 0310 hours silence - 12https://tracker.habhub.org/#!qm=All&q=N4XWC-1 [23:21] FireFighter (~firefight@2601:44:4380:605c:7147:8d54:ca83:38c) left irc: Remote host closed the connection [23:26] Bernd_DL1XH: im guessing what you have listed as 'gps error' is actually speed? [23:27] i think you have one of the fields mislabeled :-) [23:27] in the config.h? [23:27] in your payload doc [23:27] ah, need to check. [23:28] looks to be floating, what balloon? [23:29] I think it was OK before using the latest FW. Have not been changing anything since the beginning of my flights. But let cross check [23:29] its not a firmware issue [23:29] its just that the field is mis-labeleld on the payload document [23:29] i see a few other people have done the same [23:30] your are right ...let me check [23:30] its ground speed in kph [23:30] the balloon is a 90cm qualatex with 10g of lift [23:31] 10g? [23:32] RS41 is heavier than that :P [23:33] the whole thing has a lift of 10g including the RS41 [23:33] I have measured the whole setup [23:34] ah pk [23:34] what weight did you get the RS41 down to? [23:40] Bernd_DL1XH: i only made that speed field work recently [23:41] in the same batch of updates that added the deep sleep stuff [23:42] LazyLeopard (~irc-clien@chocky.lazyleopard.org.uk) left irc: Quit: Textual IRC Client: www.textualapp.com [23:44] New position from 03RSIST after 0310 hours silence - 12https://tracker.habhub.org/#!qm=All&q=RSIST [23:45] re weight.. it is 62g ...I gave up on super weight saving as batteries got frozen w/o good enclosure [23:50] yeah [23:50] also eventually you hit the limits of that 26 MHz TCXO and the transmitter goes for a walk down the band [23:53] yeah, but today we are fine staying at -39°C... just within the specs :-) [23:53] ehhh dont trust that temp reading :P [23:56] the last ones have died at a batt voltage around 1.7, i guess thats the point were it stops [23:57] New vehicle on the map: 03EASY-SON - 12https://tracker.habhub.org/#!qm=All&q=EASY-SON [23:59] Kodar_ (~Kodar@93-142-12-204.adsl.net.t-com.hr) left irc: Read error: Connection reset by peer [00:00] --- Wed Dec 30 2020