[00:04] New position from 03SQ6NEI-12 after 037 hours silence - 12https://tracker.habhub.org/#!qm=All&q=SQ6NEI-12 [00:20] kristianpaul (~paul@user/kristianpaul) left irc: Ping timeout: 265 seconds [00:24] kristianpaul (~paul@user/kristianpaul) joined #highaltitude. [01:00] happysat (~katpoep@82-169-224-141.biz.kpn.net) left irc: Remote host closed the connection [01:36] snakedGT (~snaked@user/snaked) joined #highaltitude. [01:39] snaked (~snaked@user/snaked) left irc: Ping timeout: 260 seconds [01:50] Suterusu (~EyeR@Morrigan.Armed.Me.Uk) joined #highaltitude. [01:55] happysat (~katpoep@82-169-224-141.biz.kpn.net) joined #highaltitude. [02:12] aOf__ (~DarkoAOF@95-178-159-120.dsl.optinet.hr) joined #highaltitude. [02:15] aOf_ (~DarkoAOF@95-178-158-131.dsl.optinet.hr) left irc: Ping timeout: 260 seconds [03:22] snaked (~snaked@user/snaked) joined #highaltitude. [03:22] snakedGT (~snaked@user/snaked) left irc: Ping timeout: 252 seconds [03:39] Suterusu (~EyeR@Morrigan.Armed.Me.Uk) left irc: Ping timeout: 252 seconds [04:04] Suterusu (~EyeR@Morrigan.Armed.Me.Uk) joined #highaltitude. [04:09] YO9GJX (~YO9GJX@109.100.112.132) left irc: Remote host closed the connection [04:59] _9A7AOF (~DarkoAOF@95-178-159-120.dsl.optinet.hr) joined #highaltitude. [05:03] Lahti (~Lahti@87-95-114-71.bb.dnainternet.fi) joined #highaltitude. [05:05] no 434.662 and 432.665 signal, but SQ6NEI very good [05:35] BZ-rtty might need a 30-60 min more before the sun is high enough for the solar cells to start the board [05:46] Suterusu (~EyeR@Morrigan.Armed.Me.Uk) left irc: Ping timeout: 265 seconds [06:01] ok, BZ comming online :) [06:01] good signal on web sdr [06:03] Green ! [06:03] New position from 03BZ-RTTY-5 after 0315 hours silence - 12https://tracker.habhub.org/#!qm=All&q=BZ-RTTY-5 [06:03] one line needs to be commented out from radiolib and it shoudl decode just fine with horus-gui [06:05] yeah, I saw the comment yesterday, easy fix :) [06:08] VK5QI: can you describe that change? (OH3BHX here) [06:09] after each byte radiolib puts the radio into standby [06:09] though it may be my RTL-SDR has USB issues and I can't fix it remotely [06:09] https://github.com/jgromes/RadioLib/issues/306#issuecomment-915177878 [06:10] you can see the gaps in signal between each byte [06:10] this is *not* how a modem, RTTY or otherwise, shoudl behave [06:10] so out-of-the-box horusdemodlib won't decode that? [06:10] correct [06:11] because horusdemodlib expects the transmitter to behave like a modem [06:12] hm, I haven't installed RadioLib manually [06:12] only horusdemodlib [06:12] es5nhc__ (~es5nhc@static-213-100-139-88.cust.tele2.ee) joined #highaltitude. [06:12] not sure what the relation is there [06:13] RadioLib is whats being used on the payload [06:13] its resulting in a FSK signal with very bad timings, and as such the FSK modem used within horusdemodlib will not lock onto the symbol timing [06:14] so, you have to compile the payload fw with a modified radiolib source? [06:14] ahh ok so it's an issue in TX, not RX [06:14] well, ideally radiolib will be fixed [06:14] rr [06:14] because it is really bad behaviour [06:14] its not how any rtty modem works. in an absolute worst case there should at least be an idle tone between bytes, not silence [06:15] yeah sounds bad indeed [06:15] 4FSK from Estonia can be heard very well here -- if my RTL-SDR just wanted to work properly, not sure what happened with it... probably crappy extension cable [06:16] oh yeah, there will be 4FSK modulation support added to radiolib too [06:17] what hardware are these balloons using? both the same? I mean there's another balloon transmitting 4FSK over Estonia right now... the RTTY one is in Finland [06:18] the RTTY payload is using custom hardware, using a SX127x radio modem (hence the LoRa) [06:18] ah right, yes, I've heard of that [06:19] hmm i might have to set mask estimation to be off by default if 4FSK goes into RadioLib, as the tone spacing will be different to whats used in teh RS41s [06:21] mask estimation gives better weak signal performance though [06:23] I wonder what SQ6NEI-4FSK is using... there's APRS there too [06:23] maybe multiple transmitters [06:23] nah thats a RS41 still [06:23] APRS is probably on 70cm [06:24] yes it is... I can receive 4FSK here too -- I was just wondering if it's a re-used RS41 or something else [06:24] dammit i keep on clicking payloads on the habhub map expecting the list on the left to scroll like it does on sondehub :P [06:24] I do that too! :D [06:24] yep in the comment, APRS on 432.5 MHz [06:27] thay are all rs41 sondes for all I know [06:28] might find something here http://sp7pki.iq24.pl/default.asp?grupa=230409 [06:28] its the only platform ive provided code to generate 4fsk on [06:30] The Lora-5 program is not working, I will continue to follow 4FSK https://ibb.co/hcYjkG0 [06:31] that's definitely not configured right to decode the flight [06:31] select the flight from the drop-down list where it says flight [06:31] choose the appropriate payload, then click auto-configure [06:35] Lahti: for lora you have to have a stand alone rx made for just lora, but from the same puload alos rtty is transmitted, that should be fine with the dl-fldigi I linked to yesterday, did that work to install? [06:44] nice, I see there landed a wx sonde 7km from here, probably hanging in a tree but will go have a look when it stops raining [06:44] I dont understand, Horus is really good, I focus on that [06:45] do you see the BZ payload at 434.662 tx every 90 sec [06:45] Lahti: thanks :P [06:46] horus v16 stil the latest? [06:46] theres 0.2.1 now [06:46] oh :) [06:48] finally adds support for the v2 horus mode (which nobody is flying yet) [06:48] i need to get some transmitter code out there so someone can do a launch with it in europe and force everyone to upgrade! [06:48] ok, I see the V1/V2 [06:49] yeah [06:50] I've got V2 added to my RS41ng firmware, but haven't completed testing yet... decoding wasn't working right away, so must be some bugs in my code :) [06:50] oh cool [06:50] if you can add continuous mode to your firmware, i'll just switch to using your code :P [06:50] (also the power save bip bip stuff) [06:51] let's see if I have the time... I've been more interested in the multi-mode capabilities. But more features is always good :D [06:51] for launches here we alwasy run continuous mode [06:51] or run 4FSK only with gaps in between, with the regular 'pips' to let people know they are on frequency [06:52] is your goal just to get updates as often as possible? or is there a special meaning in what you call "continuous mode"? [06:53] continuous mode is where its continually modulating 4FSK. when there is no bytes to send, it just increments the symbol [06:53] there is still a 'gap' of about 1 second between data packets, in that time its just doing that symbol increment [06:53] that way the modem remains locked on to the modulation, for best performance [06:54] ok, but doesn't the RS41 transmitter need breaks to work properly for long durations? [06:54] sure, for the multi-day flights you want the gaps to save power [06:54] but for a regular up/down flight there's no need [06:54] even transmitting continuously, 2xAAs will power a RS41 for 24 hours [06:55] and for a regular up/down flight i want fast updates [06:55] ok, so transmitting for a couple of hours continuously is OK for RS41... I remember reading something going wrong with the internal state of the transmitter with long TX [06:56] oh right - so yes you need to briefly switch the transmitter into standby then back out again [06:56] yeah, that's what I meant [06:56] this can be done quickly enough that the modem doesnt lose lock [06:56] kk [06:57] I'll have to see what your code does in the continuous mode at some point [06:57] first I'll be focusing on getting V2 working and possibly 4FSK on HF (Si5351) [06:57] if there's no bytes of data to be sent, it just takes the currently sent symbol and increments it, then modulos it with 4 [06:58] ok [06:58] so you just send symbol 0 1 2 3 0 1 2 3 0 1 2 3 [06:58] just like in the preamble actually [06:58] aa right [06:58] that's fairly simple to do [07:01] kristianpaul (~paul@user/kristianpaul) left irc: Read error: Connection reset by peer [07:02] https://github.com/darksidelemm/RS41HUP/blob/master/main.c#L266 [07:03] but yes, you need to just briefly take the radio out of transmit mode into standby, then back into standby. best time to do this is at the end of a packet [07:05] kristianpaul (~paul@user/kristianpaul) joined #highaltitude. [07:06] ok thanks, will have a look at implementing that... I'd also like to add variable transmit intervals based on altitude, just to save batteries [07:06] I'm also not using GPS/CPU power saving modes yet [07:07] ahh [07:07] GPS power save mode is well worth it [07:07] its not hard to do [07:08] https://github.com/darksidelemm/RS41HUP/blob/master/ublox.c#L73 [07:08] FFS, my RasPi4 lost USB RTL-SDR now completely [07:08] preivously it was working 100% fine [07:08] bleh [07:09] i wouldnt go any lower than the 1 second cyclic mode. thats about the best the ublox 6 series can do reliably [07:09] are you using the power-save mode between transmissions? [07:09] or how does it work? [07:09] power-save mode is just a mode the gps can sit in all the time [07:09] aha right [07:09] though its recommended to only put it into that mode once it has lock [07:09] cool ok [07:09] so on startup, run in regular high performance mode, once you have lock you can send that command to enter power-save mode. [07:09] and if it loses fix, maybe disable it? [07:09] yeah you can try that [07:09] I mean until it gets a fix [07:09] kk [07:10] LazyLeopard (~irc-clien@chocky.lazyleopard.org.uk) joined #highaltitude. [07:10] is the CPU power saving worth it? [07:10] not sure [07:10] havent tried it myself [07:10] ok :) [07:11] oh ok in my code i enter powersave mode once i have a fix, but i dont ever exit it [07:11] hasnt seemd to be an issue [07:11] run the cpu on a lower speed? [07:11] https://github.com/darksidelemm/RS41HUP/blob/master/main.c#L484 [07:11] right [07:11] aha i only enter powersave mode when i have >6 sats [07:11] insted of 8 run it a 1 [07:11] in powersave mode it doesnt re-aquire new sats as often. [07:11] anyway, thanks for the details -> will have to go offline now -> [07:12] also i indicate the state of the gps tracker powersace mode in the numSV field https://github.com/darksidelemm/RS41HUP/blob/master/main.c#L524 [07:12] ok, cya [07:30] New position from 03NOB9 after 0316 hours silence - 12https://tracker.habhub.org/#!qm=All&q=NOB9 [07:35] New position from 03KD2FOU-11 after 0316 hours silence - 12https://tracker.habhub.org/#!qm=All&q=KD2FOU-11 [07:50] Netshroud (~Netshroud@user/netshroud) left irc: Quit: Ping timeout (120 seconds) [08:17] LazyLeopard (~irc-clien@chocky.lazyleopard.org.uk) left irc: Quit: Textual IRC Client: www.textualapp.com [08:36] Suterusu (~EyeR@Morrigan.Armed.Me.Uk) joined #highaltitude. [09:24] richardeoin (~richard@ec2-35-176-87-167.eu-west-2.compute.amazonaws.com) left irc: Ping timeout: 240 seconds [09:51] Trieste_ (T@user/pilgrim) joined #highaltitude. [09:51] Trieste (T@user/pilgrim) left irc: Ping timeout: 240 seconds [10:14] richardeoin (~richard@ec2-35-176-87-167.eu-west-2.compute.amazonaws.com) joined #highaltitude. [10:16] Chrischan11 (~Chrischan@ip5f5be027.dynamic.kabel-deutschland.de) left irc: Ping timeout: 265 seconds [10:26] New vehicle on the map: 03F5APQ_chase - 12https://tracker.habhub.org/#!qm=All&q=F5APQ_chase [10:30] New vehicle on the map: 03SP8ESA-4FSK - 12https://tracker.habhub.org/#!qm=All&q=SP8ESA-4FSK [10:42] Lahti (~Lahti@87-95-114-71.bb.dnainternet.fi) left irc: Quit: Ping timeout (120 seconds) [10:51] New vehicle on the map: 03SQ9FOX-11 - 12https://tracker.habhub.org/#!qm=All&q=SQ9FOX-11 [10:55] New vehicle on the map: 03SP5LA - 12https://tracker.habhub.org/#!qm=All&q=SP5LA [11:01] Lahti (~Lahti@87-95-114-71.bb.dnainternet.fi) joined #highaltitude. [11:11] New position from 03LU1ESY-28 after 036 hours silence - 12https://tracker.habhub.org/#!qm=All&q=LU1ESY-28 [11:22] New position from 03N4XWC-1 after 039 hours silence - 12https://tracker.habhub.org/#!qm=All&q=N4XWC-1 [11:25] VK5QI, if possible, can you take a look at this wav file ? https://www.dropbox.com/s/7nn2x4q07dybh95/bz-rtty-6.wav?dl=0 ? Thatīs with the sandby() disabled [11:25] 200 baud 7n2 600 shift [11:27] yeah still not decoding [11:27] might still be timing issues due to the non-interrupt-driven modulation [11:28] New vehicle on the map: 03SP8ESA_chase - 12https://tracker.habhub.org/#!qm=All&q=SP8ESA_chase [11:34] unsure about this one tbh [11:36] then again fldigi doesnt seem to be decoding it either [11:37] the drift is pretty bad [11:38] oh wait, dl-fldigi seems to decode it [11:38] yet regular fldigi doesnt [11:38] my suspicion is the fldigi rtty decoder has changed between dl-fldigi and now, ans is perhaps less tolerant of timing issues [11:42] My new problem is that I canīt ICSP the processor again with the lora module (RFM98) attached to mosi miso :-( [11:42] ahh [11:43] a test you could run would be to transmit a very long sequence of 0x55 characters [11:43] oh wait, and use 7N1 [11:43] urgh hand on [11:43] hmm [11:44] 8N1, sending 0x55 should result in essentially a continuous 0101010101 sequence [11:44] i think [11:50] ok, i can generate 7N2 RTTY from fldigi and it decodes ok in horus-gui [11:50] at 200 baud [11:53] VK5QI: would it be easy to add 50 baud 4FSK to horusdemodlib / horus-gui? Just for testing 4FSK on HF (using slow Si5351) [11:53] its already an option in horus-gui [11:53] oh is it? [11:54] for horusdemodlib, you need to use the --rate=50 option on horus_demod [11:54] ok :D that was easy [11:54] yeah i've always had 50/100/300 options for horus binary [11:54] ok I previously saw 100/300 [11:54] below 50 baud the demod performans falls off a cliff unfortunately [11:55] ok [11:55] have to go do a different type of demodulator to work at those low baud rates it seems [11:55] yeah, well having short packet durations is more important for me [11:55] so 50 baud should be good... if Si5351 is too slow, the it is too slow [11:55] *then [11:55] i dont expect it will work that well over HF tbh [11:56] especially at si5351 powers [11:56] it really wasnt designed for that kind of radio channel [11:56] power is around 10-20 mW I guess [11:56] yeah, well, it's an experiment :) [11:56] yeah i doubt it'll go that well on hf tbh [11:56] you need to the super super slow modes to work well on HF at those powers [11:57] i need powers in the order of tens of watts to have the 50 baud mode work over long HF paths [11:59] yes, that's to be expected [11:59] its in part a problem of noise level [11:59] So the 0.2.1 version of Horus GUI binaries (Win/Mac) has the 50 bauds / Horus V2 support? [11:59] (don't have a Windows computer here right now) [12:00] i thought 50 baud has been in there for ages [12:00] ok :) it's weird that I didn't see it before... [12:00] v2 is only in 0.2.1, and use of the v2 mode is going to require additions to the custom field list file [12:00] yes [12:00] i can confirm 0.1.16 had 50 baud support [12:02] ok, good [12:02] i'd suggest just using teh v1 mode for that experiment to start ith [12:02] I'll probably be running V1 as primary and V2 as an alternative tracking method... so no continuous mode yet [12:02] yes [12:03] until there is a bit more uptake of v0.2.1 [12:03] no dates on the flight yet, as I'm waiting for TX permit on 80m [12:03] 80m? :/ [12:03] thats like the worst band to do this stuff on tbh. way too much atmospheric noise [12:03] yep, it will be a local experiment... not aiming for 20m [12:03] 20/30m is a sweet spot [12:03] well right. I know. [12:03] yeah but if its local, you're using teh wrong kind of antenna on the balloon for NVIs [12:04] NVS* [12:04] NVIS* (sigh) [12:04] so basically its going to be line of sight, in which case you're fighting against local noise [12:04] i did a flight on 40m years back, had similar issues [12:04] also flying such a long antenna freaks me out nowdays [12:04] 2 flights after i did the 40m flight we landed over powerlines [12:05] powerlines over a field of very dry, very long grass [12:05] it's a possibility of course, but not very likely at least here in Finland... [12:07] New position from 03NOB8 after 03a day silence - 12https://tracker.habhub.org/#!qm=All&q=NOB8 [12:08] Prutz (~Prutz@86-86-193-122.fixed.kpn.net) joined #highaltitude. [12:08] we could do another flight on 20m band later, but for that it'd be great to have RX stations ready on HF a bit further away [12:08] Prutz (~Prutz@86-86-193-122.fixed.kpn.net) left irc: Client Quit [12:08] Prutz (~Prutz@86-86-193-122.fixed.kpn.net) joined #highaltitude. [12:09] (meaning outside Finland) [12:09] which requires quite a lot of coordination [12:09] or finding decent kiwisdrs you can use [12:10] good point [12:10] but again, based on my experience testing this mode over long distance paths (with a decent station), you will need more than 20mw [12:11] Turjakas: what kind of data are you going to be sending in the custom field area? [12:11] i want to make sure i have suitable datatype conversion functions available [12:12] Prutz (~Prutz@86-86-193-122.fixed.kpn.net) left irc: Client Quit [12:12] I'm not sure yet if I even need it. Currently, I only have support for BMP280 sensor, which would provide ext temp (signed 8-bit), humidity (unsigned 8-bit) and pressure (unsigned 16-bit). [12:14] though I could use signed 16-bit for temp to get 0.1 C granularity... pressure would be in mbar [12:16] ok, so i'm going to add some converters for divide-by-10 and divide-by-100 [12:17] which will just take an integer (signed or unsigned, whatever size) value and divideby 10 or 100, and provide that in the output string [12:17] cool, great [12:19] which means i'd better get a new horus-gui version out with it.. [12:20] im hoping the basic data types plus those converters will cover most use-cases [12:20] Prutz41 (Prutz@gateway/vpn/protonvpn/prutz) joined #highaltitude. [12:20] g__ (Prutz@gateway/vpn/protonvpn/prutz) joined #highaltitude. [12:20] Prutz41 (Prutz@gateway/vpn/protonvpn/prutz) left irc: Client Quit [12:20] hi [12:21] Nick change: g__ -> Prutzz [12:22] Turjakas: hopefully this is descriptive enough: https://github.com/projecthorus/horusdemodlib/wiki/5-Customising-a-Horus-Binary-v2-Packet#interpreting-the-custom-data-section [12:22] that looks good, I already had a look at it [12:23] i just added in the two extra converters [12:23] if you think of any other converters that might be required, let me know.. [12:23] Hi folks. Got a small question. I got a Rasp RTLSDR working with a 1/4 antenna and it works like a charm. [12:24] Turjakas: ill get this update out tomorrow [12:24] But now playing around with a TTGO with both RDWZ and MySondyGo firmware. But seems I don't receive anything. [12:24] Antenna is a yagi and connected with a Baofend the signal comes in loud and and clear [12:25] But connecting it to a TTGO nothing... [12:25] Prutzz: i can only really speak for the rdz-ttgo-sonde firmware, once is et up a frequency i'm able to receive RS41s fine [12:25] havent tried with other sonde types [12:25] ideal would be if you have a sonde put it outside and see if you can rx that [12:25] how sensitive is it? [12:26] Prutzz, let me ask the obvious: The ttgo has an SMA connector, not reversed SMA [12:26] some lora boards have an antenne switch [12:26] Do you use the right antenna adapter ? [12:26] to switch between rx and tx [12:26] my have standard sma, and its quite sencetive, at least on par with the good rtl:s [12:26] yes, Im using a SMA connector [12:27] I use this fw for rs41 rx and upoad to sondehub https://github.com/dl9rdz/rdz_ttgo_sonde [12:27] Like I said, when im connecting the antenna to the Baofeng radio it comes in loud and clear [12:27] no lna inline then I guess [12:28] Does your ttgo have both SMA and mini IPX connector on board ? [12:28] no just antenna [12:28] err... yes i think so [12:28] hold on will have a look, its upstairs atm [12:28] picture of the board, there is quite a few boards out there [12:28] Can you have a close look, sometimes itīs a missing solder bridge [12:29] most fw hae a rsi so the noise floor should increase whn you connect the antenna [12:31] https://external-content.duckduckgo.com/iu/?u=https%3A%2F%2Fcdn.myshoptet.com%2Fusr%2Fwww.laskarduino.cz%2Fuser%2Fshop%2Fbig%2F3827-1_lilygo-ttgo-lora32-t3_v1-6-433mhz-0-96--sma-wifi-modul.jpg%3F5e9804b9&f=1&nofb=1 [12:31] got this one but then ofcourse the 400mhz [12:31] same as im using [12:32] Now take a close look if the antenna from the lora module is bridged to the SMA or the tiny IPX connector. [12:33] I can try to measure continuity from the SMA pin to the LoRa chip. Seems the one on the corner is Antenna output [12:33] Thatīs right [12:34] One next to that is gnd. [12:35] yes it has connection.. [12:36] is it a 434 MHz TTGO (not a 868 MHz)? [12:37] New vehicle on the map: 03SQ6NLN-4FSK - 12https://tracker.habhub.org/#!qm=All&q=SQ6NLN-4FSK [12:37] oh sorry for asking, I see you told that already [12:37] When I use spectrum and use my baofeng on the frequency It shows the right frequency. (yes it is the 434mhz). [12:38] no worries :) [12:39] Don't know what it could be.. Since the yagi antenna work very well compared omni on the baofeng. And the rasp-SDR also is an omni. [12:39] most fw hae a rsi/signal meter in the dispaly, does the noise floor increase when you connect the antenna? [12:40] excuse me what do you mean with fw? [12:40] there is lots of fw for those boards and can be configured in a nr of ways, does your board show rsi or sn in the dispaly? [12:41] will flash the firmware back to RDZ... hold on :) [12:42] New vehicle on the map: 03SQ6NLN-12 - 12https://tracker.habhub.org/#!qm=All&q=SQ6NLN-12 [12:42] i prefer the rdz firmware :-) [12:43] yes, tried a few but this supports sondehub upload :) [12:44] rdz that is [12:44] yes [12:44] and its open source [12:44] yeah me too. Just tried MySondy to check if that might work. As with the Rasp-SDr I tried RadioSondy first... but didn't work well. Then tried autoRX and it works flawless [12:45] heh [12:45] nice to know :-) (I'm the author of aut_rx) [12:45] auto_rx* [12:45] oh really? Great job man! :D [12:47] cheers! (though a lot of the really hard bits were done by someone else - i just combined it all together :-) ) [12:48] still impressive :D [12:48] can't do it my self ;) [12:50] Ok, firmware is loaded and connected and disconnected the antenna while looking on the spectrum.. floor noise doesn't seem to change [12:54] When transmitting with the baofeng with no antenna (yes I know it's bad) and no antenna on the TTGO you can see a spike on the spectrum [12:54] New vehicle on the map: 03SP6ZWR-4FSK - 12https://tracker.habhub.org/#!qm=All&q=SP6ZWR-4FSK [12:54] so it does receive something. [12:55] Peak is also the correct frequency [13:00] could it be the sma center pin is to short? [13:00] omg... you are my hero [13:00] you have any sma adapters you can run it through [13:00] ok :) [13:01] Both SMA connectors are female.. but one is reversed ofcourse [13:01] New vehicle on the map: 03SP6ZWR-12 - 12https://tracker.habhub.org/#!qm=All&q=SP6ZWR-12 [13:01] xD [13:02] Ok I feel a bit stupid... [13:02] Thanks for the hint haha [13:03] biggest fail in history of connectors are the rp-sma :) you are not the first and you will not be the last!!! :) [13:03] im glas you (probably) goina get it going [13:03] *glad [13:06] Well... sometimes you think too difficult... [13:06] Instead of starting with the easiest things. [13:07] Turjakas: ok, ended up getting it out tonight [13:07] you should be able to update the horusdemodlib library and horus-gui [13:07] Now I'm even more impressed with a Yagi since it worked very well even it also didn't connect propparly [13:07] with the baofeng [13:07] true! [13:09] okeydoke, horus-gui v0.2.3 is up [13:15] Tnx! [13:15] OK1MDX (~OK1MDX@ip-37-188-181-68.eurotel.cz) joined #highaltitude. [13:16] yeah now I see a noise floor in the Spectrum! Many thanks for the help! [13:17] OK1MDX (~OK1MDX@ip-37-188-181-68.eurotel.cz) left irc: Client Quit [13:40] New vehicle on the map: 03K1amo_chase - 12https://tracker.habhub.org/#!qm=All&q=K1amo_chase [13:43] Do you guys use the app as well? [13:43] i don't [13:43] what app? [13:44] https://github.com/dl9rdz/rdzwx-go [13:44] Or do you use the TTGO only to receive and send to hub? [13:45] cool, didnt know it existed, but the sondehub and the web ui is good enough for my need but I will probably test the ap [13:45] p [13:45] yes, only to tx to sondehub [13:45] ah I see :) [13:46] i run auto_rx and chasemapper [13:46] and view that on a tabler [13:46] tablet* [13:46] if there is a local landing I connect the yagi and rx with the rtl and RS41 Tracker [13:46] not so good for 'portable' (e.g. out of car) mind you [13:46] havent heard *anything* from the rs41tracker guy [13:46] have emailed him 3 times now [13:46] ahh, that couls be nice ading ofc [13:47] yeah, I have mostly brough at laptop and a rtl in the car chasing them [13:47] I see :) [13:48] any precomipled .app somewhere? [13:48] Tonight would like to go hunt for my first balloon. Didn't have thought about a setup yet [13:48] Sadly not... Tried to compile it my self this morning but with no luck. [13:52] New vehicle on the map: 03K1AMO - 12https://tracker.habhub.org/#!qm=All&q=K1AMO [13:54] New position from 03KB1KVR after 03a day silence - 12https://tracker.habhub.org/#!qm=All&q=KB1KVR [13:54] here I found one https://github.com/dl9rdz/rdzwx-go/releases/tag/v1.0.5 [13:54] lets test it... [13:55] https://github.com/dl9rdz/rdzwx-go/releases/tag/v1.0.6 [13:56] cool [14:02] no clue how to connect [14:03] TTGO is an acces point and got my phone connected to the AP. [14:05] pull the power to router and ttgo, then power ttgo [14:06] then the ttgo goes into ap mode and you can connect to the go from phone [14:07] the phone found the ttgo through the router so thats cool :) [14:08] errr... :P why mine isn't [14:08] I'm connected straight to the GO [14:09] did you do something with the config? [14:09] nothing, whn I pressed the sympol looking like ttgo on the right side I went straight to the go web ui [14:10] I see the ip adress of the go at the top [14:10] mine is 192.168.1.237 [14:10] thats the IP address from the router to the GO [14:10] yes [14:10] local is 192.168.4.1 [14:11] if you are straight connected [14:11] indeed [14:11] yes [14:11] no, not [14:11] straight now im trough the router [14:11] yes [14:11] its in the attic so not that easy acsess to it [14:11] :P [14:20] Chrischan11 (~Chrischan@ip5f5be027.dynamic.kabel-deutschland.de) joined #highaltitude. [14:22] weird.. can you connect through rdzsonde.local ? [14:23] yes [14:24] my phone can't... only the IP [14:24] maybe thats why I have a problem with the app [14:24] ah, on the phone... [14:25] no, not on the phone and chrome [14:25] weird [14:39] Chrischan11 (~Chrischan@ip5f5be027.dynamic.kabel-deutschland.de) left irc: Ping timeout: 265 seconds [14:53] New vehicle on the map: 03SP6ZWR_chase - 12https://tracker.habhub.org/#!qm=All&q=SP6ZWR_chase [14:56] oh got it working! Had an older Master firmware. Now tried one of the dev types. [14:56] yes! [14:56] nice! [14:57] you know of the http://rdzsonde.local/update.html [14:58] it must be connected to the router [14:59] Lahti (~Lahti@87-95-114-71.bb.dnainternet.fi) left irc: Quit: Connection closed [15:01] ah great didn't know that one [15:03] 👍 [15:05] VK5QI: awesome, thanks. I'm able to get back to testing V2 next week. [15:07] New position from 03SP6QKM-4FSK after 037 hours silence - 12https://tracker.habhub.org/#!qm=All&q=SP6QKM-4FSK [15:10] New position from 03OK1OMG after 03a day silence - 12https://tracker.habhub.org/#!qm=All&q=OK1OMG [15:13] Turjakas: dont forget you'll need a payload id (or multiple) at some point [15:40] Chrischan11 (~Chrischan@ip5f5be027.dynamic.kabel-deutschland.de) joined #highaltitude. [16:02] New position from 03OK1OMG-12 after 03a day silence - 12https://tracker.habhub.org/#!qm=All&q=OK1OMG-12 [16:05] Chrischan11 (~Chrischan@ip5f5be027.dynamic.kabel-deutschland.de) left irc: Ping timeout: 252 seconds [16:07] New vehicle on the map: 03SQ6BOR_chase - 12https://tracker.habhub.org/#!qm=All&q=SQ6BOR_chase [16:38] New position from 03icspace26-hab-eu-863-870 after 0320 hours silence - 12https://tracker.habhub.org/#!qm=All&q=icspace26-hab-eu-863-870 [17:26] New vehicle on the map: 03KG7HIZ-11 - 12https://tracker.habhub.org/#!qm=All&q=KG7HIZ-11 [17:40] LazyLeopard (~irc-clien@chocky.lazyleopard.org.uk) joined #highaltitude. [17:49] New vehicle on the map: 03PE2BZ - 12https://tracker.habhub.org/#!qm=All&q=PE2BZ [17:51] Prutzz (Prutz@gateway/vpn/protonvpn/prutz) left irc: Ping timeout: 265 seconds [18:11] Prutz (Prutz@gateway/vpn/protonvpn/prutz) joined #highaltitude. [18:11] YO9GJX (~YO9GJX@109.100.112.132) joined #highaltitude. [18:27] _9A7AOF (~DarkoAOF@95-178-159-120.dsl.optinet.hr) left irc: Quit: Leaving [18:47] New position from 03K5ENG-74 after 036 days silence - 12https://tracker.habhub.org/#!qm=All&q=K5ENG-74 [18:56] snakedGT (~snaked@user/snaked) joined #highaltitude. [18:58] snaked (~snaked@user/snaked) left irc: Ping timeout: 260 seconds [19:05] New vehicle on the map: 03LU1ESY-27 - 12https://tracker.habhub.org/#!qm=All&q=LU1ESY-27 [19:19] OK1MDX (~OK1MDX@ip-37-188-244-89.eurotel.cz) joined #highaltitude. [19:19] 180f33dbd1291f211eaf69d129d172dc [19:22] New position from 03LU1ESY-28 after 036 hours silence - 12https://tracker.habhub.org/#!qm=All&q=LU1ESY-28 [19:23] snakedGT (~snaked@user/snaked) left irc: Ping timeout: 265 seconds [19:24] New position from 03N0MPM-13 after 0314 hours silence - 12https://tracker.habhub.org/#!qm=All&q=N0MPM-13 [19:32] New vehicle on the map: 03OK1OMG-1 - 12https://tracker.habhub.org/#!qm=All&q=OK1OMG-1 [19:35] Chrischan11 (~Chrischan@ip5f5be027.dynamic.kabel-deutschland.de) joined #highaltitude. [19:40] Chrischan12 (~Chrischan@ip5f5be027.dynamic.kabel-deutschland.de) joined #highaltitude. [19:43] Chrischan11 (~Chrischan@ip5f5be027.dynamic.kabel-deutschland.de) left irc: Ping timeout: 260 seconds [19:44] Chrischan12 (~Chrischan@ip5f5be027.dynamic.kabel-deutschland.de) left irc: Ping timeout: 265 seconds [19:46] New position from 03W8VPV-1 after 0315 hours silence - 12https://tracker.habhub.org/#!qm=All&q=W8VPV-1 [19:50] snakedGT (~snaked@user/snaked) joined #highaltitude. [20:00] snakedGT (~snaked@user/snaked) left irc: Ping timeout: 260 seconds [20:06] es5nhc__ (~es5nhc@static-213-100-139-88.cust.tele2.ee) left irc: Ping timeout: 260 seconds [20:07] snakedGT (~snaked@user/snaked) joined #highaltitude. [20:43] New vehicle on the map: 03OK1OMG-13 - 12https://tracker.habhub.org/#!qm=All&q=OK1OMG-13 [21:36] New position from 03SP6QKM-4FSK after 036 hours silence - 12https://tracker.habhub.org/#!qm=All&q=SP6QKM-4FSK [23:09] LazyLeopard (~irc-clien@chocky.lazyleopard.org.uk) left irc: Quit: Textual IRC Client: www.textualapp.com [23:17] New position from 03N4XWC-1 after 039 hours silence - 12https://tracker.habhub.org/#!qm=All&q=N4XWC-1 [00:00] --- Sun Sep 12 2021