highaltitude.log.20200703

[00:36] Hoogvlieger (~Hoogvlieg@2001:1c03:3e10:3c00:28b1:9d91:4ace:b5b6) joined #highaltitude.
[00:40] <SpacenearUS> New vehicle on the map: 03N4XWC-1 - 12https://tracker.habhub.org/#!qm=All&q=N4XWC-1
[00:51] snakedGT (~snaked@pdpc/supporter/active/snaked) joined #highaltitude.
[00:51] snaked (~snaked@pdpc/supporter/active/snaked) left irc: Read error: Connection reset by peer
[01:15] daveake (uid144009@gateway/web/irccloud.com/x-zxmynxeqcmgkeokc) left irc: Quit: Connection closed for inactivity
[01:41] Nick change: snakedGT -> snaked
[02:10] Laurenceb (~laurence@110.207.208.46.dyn.plus.net) joined #highaltitude.
[02:32] Laurenceb (~laurence@110.207.208.46.dyn.plus.net) left irc: Ping timeout: 246 seconds
[02:32] Laurenceb (~laurence@110.207.208.46.dyn.plus.net) joined #highaltitude.
[02:51] snakedGT (~snaked@pdpc/supporter/active/snaked) joined #highaltitude.
[02:52] Laurenceb (~laurence@110.207.208.46.dyn.plus.net) left irc: Ping timeout: 260 seconds
[02:53] snaked (~snaked@pdpc/supporter/active/snaked) left irc: Ping timeout: 256 seconds
[02:53] DL7AD (~sven@2001:16b8:5c5a:f100:1ced:8e4:ba10:ae5e) left irc: Ping timeout: 260 seconds
[02:55] Laurenceb (~laurence@110.207.208.46.dyn.plus.net) joined #highaltitude.
[03:09] DL7AD (~sven@2001:16b8:5cde:da00:cd61:62b3:f7e1:7c8d) joined #highaltitude.
[03:19] Axone (~Axone@lfbn-idf1-1-1835-51.w90-91.abo.wanadoo.fr) left irc: Quit: ZNC 1.6.6+deb1ubuntu0.2 - http://znc.in
[03:21] Axone (~Axone@lfbn-idf1-1-1835-51.w90-91.abo.wanadoo.fr) joined #highaltitude.
[03:51] snakedGT (~snaked@pdpc/supporter/active/snaked) left irc: Remote host closed the connection
[03:52] snaked (~snaked@pdpc/supporter/active/snaked) 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.
[03:58] snaked (~snaked@pdpc/supporter/active/snaked) left irc: Remote host closed the connection
[03:58] snaked (~snaked@pdpc/supporter/active/snaked) joined #highaltitude.
[04:00] Laurenceb (~laurence@110.207.208.46.dyn.plus.net) left irc: Ping timeout: 264 seconds
[04:02] snaked (~snaked@pdpc/supporter/active/snaked) left irc: Remote host closed the connection
[04:06] snaked (~snaked@pdpc/supporter/active/snaked) joined #highaltitude.
[04:17] snaked (~snaked@pdpc/supporter/active/snaked) left irc: Remote host closed the connection
[04:17] snaked (~snaked@pdpc/supporter/active/snaked) joined #highaltitude.
[05:09] YO3ICT (~YO3ICT@188.25.199.68) joined #highaltitude.
[06:13] snh (~snh@unaffiliated/snh) left irc: Read error: Connection reset by peer
[06:13] snh (~snh@unaffiliated/snh) joined #highaltitude.
[06:56] <SpacenearUS> New position from 03DELTA-5R after 0315 hours silence - 12https://tracker.habhub.org/#!qm=All&q=DELTA-5R
[07:04] Lahti (~Lahti@dyvypnfhvzmcz7w-yw0tt-4.rev.dnainternet.fi) joined #highaltitude.
[07:04] LazyLeopard (~irc-clien@chocky.lazyleopard.org.uk) joined #highaltitude.
[07:51] daveake (uid144009@gateway/web/irccloud.com/x-vmqslgpzpnxmwgiw) joined #highaltitude.
[08:09] <SpacenearUS> New vehicle on the map: 03Fdx017_chase - 12https://tracker.habhub.org/#!qm=All&q=Fdx017_chase
[08:14] Axone (~Axone@lfbn-idf1-1-1835-51.w90-91.abo.wanadoo.fr) left irc: Ping timeout: 246 seconds
[08:16] michal_f (~mfratczak@17-153-196-109.itvmedia.pl) joined #highaltitude.
[08:20] Axone (~Axone@lfbn-idf1-1-1835-51.w90-91.abo.wanadoo.fr) joined #highaltitude.
[09:29] Nick change: edmoore_ -> edmoore
[10:11] <SpacenearUS> New vehicle on the map: 03FRS2013_chase - 12https://tracker.habhub.org/#!qm=All&q=FRS2013_chase
[10:15] yo3ihg (050c76fd@5-12-118-253.residential.rdsnet.ro) joined #highaltitude.
[10:15] <YO3ICT> Salut yo3ihg
[10:16] <yo3ihg> hi guys
[10:16] <yo3ihg> i am trying to test the PITS software for RPI
[10:16] <yo3ihg> do you have any idea if it is working without the GPS connected?
[10:16] <yo3ihg> i just want to see if the lora module is transmitting
[10:17] <yo3ihg> but i get a single telemetry packet at PITS startup
[10:20] <SpacenearUS> New position from 03NLS1 after 032 days silence - 12https://tracker.habhub.org/#!qm=All&q=NLS1
[10:20] <bertrik> I saw xttn on the map yesterday, it looked like it eventually did not land in the sea
[10:20] Sirius-BE (~BeB@139.178.15.70) left irc: Ping timeout: 240 seconds
[10:20] <bertrik> Was it recovered?
[10:21] <YO3ICT> yo3ihg : daveake here should know
[10:21] <SpacenearUS> New position from 03BMB5 after 0320 hours silence - 12https://tracker.habhub.org/#!qm=All&q=BMB5
[10:27] <SA6BSS-Mike> bertrik: XABEN-165 successfully recovered this evening - very easy recovery. The payload landed just a mile inland, really tense watching on the tracker as it didn't look like it was going to make it back to land. If the balloon had burst a couple of minutes earlier it would have landed in the sea.
[10:27] <SA6BSS-Mike> https://groups.google.com/g/ukhas/c/SxUo0VpO1XQ
[10:27] Nick change: yo3ihg -> YO3IHG
[10:29] <SpacenearUS> New vehicle on the map: 03habboy_chase - 12https://tracker.habhub.org/#!qm=All&q=habboy_chase
[10:30] <bertrik> SA6BSS-Mike: nice!
[10:32] <pc4l_hab> @YO3IHG try uploading the example script from radiolib named ¨rtty transmit¨ . By default it will send on 434.000
[10:32] <YO3IHG> i don't have any RTTY module, only LoRa
[10:33] <pc4l_hab> hihi it uses the lora module :)
[10:33] <pc4l_hab> rfm 95/96/98 1278
[10:34] <pc4l_hab> RadioLib RTTY Transmit Example
[10:34] <pc4l_hab> This example sends RTTY message using SX1278's
[10:34] <pc4l_hab> FSK modem.
[10:34] <pc4l_hab> Other modules that can be used for RTTY:
[10:34] <pc4l_hab> - SX127x/RFM9x
[10:34] <pc4l_hab> - RF69
[10:34] <pc4l_hab> - SX1231
[10:34] <pc4l_hab> - CC1101
[10:34] <pc4l_hab> - SX126x
[10:34] <pc4l_hab> - nRF24
[10:35] <daveake> YO3IHG: Yes it will work without GPS. Only 1 LoRa packet means an issue with the DIO0 pin 0 not connected or misconfigured.
[10:40] <YO3IHG> pc4l_hab, can you please provide more details? where can i get this?
[10:40] <YO3IHG> daveake, with the pins configured i get no transmission at all
[10:40] <YO3IHG> LORA_Frequency_1=437.600
[10:40] <daveake> Yes, you have the module wrongly configured or not connected properly
[10:41] <daveake> For the _1 settings you need CE1 on the Pi to NSS, DIO0/5 connected as per settings/source, and MOSI/MISO connected
[10:42] <daveake> DIO0 tells the software that a packet has gone, so if 1 s goes then it's a DIO0 issue; if no packets then one of the other pins
[10:50] <YO3IHG> with this pins settings, the LoRa Gateway worked before for the YO3ICT-PITS balloon, so the pins should be correct
[10:51] <YO3IHG> but in the original config file the pins are not defined at all
[10:51] <pc4l_hab> https://github.com/jgromes/RadioLib ... also available in Arduino tools/manage libraries ( I use dutch version but should be something like that) then search for RadioLib
[10:51] tryphe (~tryphe@unaffiliated/tryphe) left irc: Ping timeout: 260 seconds
[10:53] <daveake> There are default pins in the code. You can override them with e.g. DIO5_1=xx to match whatever you have connected
[10:54] <daveake> Sorry LORA_DIO5=xx
[10:54] <daveake> FFS stupid keyboard
[10:54] <daveake> LORA_DIO5_1=xx
[10:55] <YO3IHG> in my config file i was no t able to find, i had only
[10:55] <YO3IHG> LORA_Frequency_1=437.600
[10:56] <SpacenearUS> New vehicle on the map: 03KD9LWH-11 - 12https://tracker.habhub.org/#!qm=All&q=KD9LWH-11
[10:57] <daveake> Yes, you need to add it, because you're not using PITS, so you need to define your own hardware
[10:59] LazyLeopard (~irc-clien@chocky.lazyleopard.org.uk) left irc: Quit: Textual IRC Client: www.textualapp.com
[11:00] <YO3IHG> good
[11:00] <YO3IHG> with the pins defined, i don't even get the single packet at stratup
[11:00] <YO3IHG> startup*
[11:01] <daveake> DIO5
[11:01] <daveake> You can set that one to zero to avoid using the pin
[11:02] chris_99 (uid26561@gateway/web/irccloud.com/x-yjzvmmhbbcgndevz) joined #highaltitude.
[11:02] <YO3IHG> now i get the same, only the first packet
[11:03] <daveake> Which is DIO0
[11:04] <daveake> Take a look at which pin you've physically connected, then do "gpio readall" to see which wiringpi pin that actually is
[11:04] <YO3IHG> 23
[11:07] <YO3IHG> like i said, the gateway is working with this pin configuration
[11:12] nickoe (~quassel@5b96fc67.rev.stofanet.dk) left irc: Ping timeout: 240 seconds
[11:12] <daveake> You can check that you've set things correctly by watching the screen when it starts, when it will tell you what DIO0/5 are set to. Beyond that, perhaps you have 2 copies running which will cause issues.
[11:13] <YO3IHG> pi@YO3IHG-RPI4:~/pits/tracker $ sudo ./startup
[11:13] YO3IHG (050c76fd@5-12-118-253.residential.rdsnet.ro) left irc: Excess Flood
[11:14] <pc4l_hab> wrong screen :)
[11:14] YO3IHG (050c76fd@5-12-118-253.residential.rdsnet.ro) joined #highaltitude.
[11:19] <daveake> :)
[11:20] <daveake> Kill startup first, then check (ps -ef | grep tracker) that the tracker isn't running. You can then restart the tracker with sudo ./tracker
[11:22] <YO3IHG> pi@YO3IHG-RPI4:~ $ ps -ef | grep tracker
[11:22] <YO3IHG> what is this? sorry i am a beginner in linux
[11:23] <daveake> It's what said; it checks of tracker is running
[11:23] <daveake> Or just reboot
[11:24] <daveake> If you have the right settings and you reboot it will work
[11:24] <YO3IHG> the rpi was rebooted, at stratup i got a single telemetry empty packet
[11:25] <daveake> DIO0
[11:25] <YO3IHG> GPIO 23
[11:26] <daveake> DIO0 tells the software that the packet has been sent. So the software is not seeing that signal. So DIO0 is wrong in some way.
[11:27] <daveake> and GPIO 23 is not the same as WiringPi 23
[11:30] <YO3IHG> really?
[11:30] <daveake> really
[11:31] <YO3ICT> There is a lot of confusion around as which designation it is used by what...Some softwares use GPIO, other BCM, others WiringPi
[11:31] <daveake> Like I said earlier .... run gpio readall, it will show a picture of the I/O pins, and you can locate the pin you are using, and read off the wiring pi pin
[11:32] <daveake> PITS and my gateway both use wiringpi
[11:32] <YO3IHG> pi@YO3IHG-RPI4:~ $ gpio readall
[11:32] <YO3IHG> i used the same pins configured for the gateway
[11:33] <daveake> They both wiring pi and neither will work if you specify the wrong pins
[11:35] Hoogvlieger (~Hoogvlieg@2001:1c03:3e10:3c00:28b1:9d91:4ace:b5b6) left irc: Quit: Leaving
[11:41] LazyLeopard (~irc-clien@chocky.lazyleopard.org.uk) joined #highaltitude.
[11:55] <SpacenearUS> New vehicle on the map: 03SITS-2 - 12https://tracker.habhub.org/#!qm=All&q=SITS-2
[12:02] <SpacenearUS> New vehicle on the map: 03REL_chase - 12https://tracker.habhub.org/#!qm=All&q=REL_chase
[12:05] <SpacenearUS> New vehicle on the map: 03CHEESE - 12https://tracker.habhub.org/#!qm=All&q=CHEESE
[12:33] cgfbee (~bot@oc1.itim-cj.ro) joined #highaltitude.
[12:43] YO3IHG (050c76fd@5-12-118-253.residential.rdsnet.ro) left irc: Ping timeout: 245 seconds
[12:47] <SpacenearUS> New position from 03PS-76 after 033 days silence - 12https://tracker.habhub.org/#!qm=All&q=PS-76
[12:50] <SpacenearUS> New vehicle on the map: 03KB1KVR - 12https://tracker.habhub.org/#!qm=All&q=KB1KVR
[13:07] OZ1SKY_Brian (~Brian@5.186.79.28.dhcp.fibianet.dk) joined #highaltitude.
[13:09] <OZ1SKY_Brian> hi
[13:13] <SpacenearUS> New vehicle on the map: 03KE5GD-11 - 12https://tracker.habhub.org/#!qm=All&q=KE5GD-11
[13:40] <SpacenearUS> New position from 03K9APX-3 after 0311 hours silence - 12https://tracker.habhub.org/#!qm=All&q=K9APX-3
[14:23] YO3IHG (050c76fd@5-12-118-253.residential.rdsnet.ro) joined #highaltitude.
[14:55] <SpacenearUS> New position from 03TRILO after 033 days silence - 12https://tracker.habhub.org/#!qm=All&q=TRILO
[14:57] hyde00001 (~hyde00001@cpc69050-oxfd25-2-0-cust745.4-3.cable.virginm.net) joined #highaltitude.
[15:06] hyde00001 (~hyde00001@cpc69050-oxfd25-2-0-cust745.4-3.cable.virginm.net) left irc:
[15:21] <PE2BZ> Let me try a LoRa question.... With around 40 receivers (guestimated) in the UK / Ireland and about the same in the Netherlands, 2 in Germany, One in Denmark and 3 in Romania, does it make sense to add calling mode to the assumed floaters with LoRa ? How many receivers would have their setup ¨waiting¨ on the 433.650 calling mode frequency ? I now know one so far....
[15:21] <SIbot> In real units: 2 in = 5.08 cm
[15:24] mattbrej1a (~mfb2g09@srv02335.soton.ac.uk) joined #highaltitude.
[15:25] mattbrejza (~mfb2g09@srv02335.soton.ac.uk) left irc: Ping timeout: 240 seconds
[15:25] fredy (~fredy@193.234.224.97) left irc: Ping timeout: 240 seconds
[15:28] fredy__ (~fredy@193.234.224.97) joined #highaltitude.
[15:28] <OZ1SKY_Brian> i dont even know what calling mode is :-)
[15:31] <OZ1SKY_Brian> https://www.daveakerman.com/?p=1816
[15:31] <OZ1SKY_Brian> now i do :-)
[15:31] <OZ1SKY_Brian> sounds like a good idea
[15:33] <OZ1SKY_Brian> oh well would not work here, only got 1 radio on 70cm
[15:34] fredy__ (fredy@193.234.224.97) left #highaltitude ("bye to all o/").
[15:35] fredy (~fredy@193.234.224.97) joined #highaltitude.
[15:36] <OZ1SKY_Brian> unless the lora gateway could be programmed to listen on the calling freq, if it hears a calling it retunes to the payload freq. Then if it does not hear anything for ? min, it returns to the calling freq. or does it allready to that?
[15:36] <OZ1SKY_Brian> to=do
[15:38] <Geoff-G8DHE> Thats what I understood the calling mode working was! It has worked here in the past, but then I think the calling channel was changed
[15:39] <Geoff-G8DHE> I have updated the frequency, but not heard anything in the last few years, to me it seems the ideal solution.
[15:39] <OZ1SKY_Brian> ok it looks like it does
[15:49] DK6OV (~DK6OV@2a02:560:4259:9700:dc8:df8b:8808:a389) joined #highaltitude.
[15:49] DK6OV_ (~DK6OV@2a02:560:4259:9700:dc8:df8b:8808:a389) joined #highaltitude.
[15:50] DK6OV_ (DK6OV@2a02:560:4259:9700:dc8:df8b:8808:a389) left #highaltitude.
[15:50] <DK6OV> Hi
[15:51] <DK6OV> I only connect the LoRa-receiver to the antenna when there is a flight.
[15:53] <DK6OV> Than I can tune in the right frequency from the publication.
[15:57] <OZ1SKY_Brian> i left mine running and a few days later that payload came back
[15:57] <pc4l_hab> BREAK BREAK
[15:57] <OZ1SKY_Brian> unexpected
[15:57] <OZ1SKY_Brian> pc4l_hab go ahead :-)
[15:58] <pc4l_hab> https://ibb.co/VgnWDTB
[15:58] <pc4l_hab> TU brian
[15:58] <pc4l_hab> can Dave or someone else tell me what is the CS=0 in this screenshot?!
[15:58] <SIbot> In real units: 0 in = 0.00 cm
[15:59] <pc4l_hab> TU BOT
[16:00] <eor> gotta love this bot
[16:00] qyx (~qyx@gw2.krtko.org) left irc: Ping timeout: 272 seconds
[16:00] <eor> someone could use a lesson in writing regular expressions
[16:00] <pc4l_hab> just behind de lora1 DIO0 and DIO5
[16:00] <YO3ICT> @PE2BZ Could you also take a look on YO3IHG's pisky?
[16:01] <pc4l_hab> YO3IHG> i think i quit, my head hurts :)))
[16:01] <pc4l_hab> he needs a break ;)
[16:01] DK6OV (~DK6OV@2a02:560:4259:9700:dc8:df8b:8808:a389) left irc: Quit: Leaving
[16:02] DK6OV (~DK6OV@2a02:560:4259:9700:dc8:df8b:8808:a389) joined #highaltitude.
[16:02] <SpacenearUS> New position from 03BB10 after 0319 hours silence - 12https://tracker.habhub.org/#!qm=All&q=BB10
[16:06] <craag> eor: I think it was the first set of regexes I ever wrote ;) I do need to look at it again, but meanwhile enjoy the entertainment.
[16:06] qyx (~qyx@gw2.krtko.org) joined #highaltitude.
[16:08] <eor> does it even understand 5'11"
[16:08] <SIbot> In real units: 11 in = 27.94 cm
[16:08] <eor> not quite
[16:09] <craag> it was mainly built to deal with pilots talking in ft
[16:09] <craag> hab at 30000'
[16:09] <SA6BSS-Mike> hab at 30000feet
[16:09] <SIbot> In real units: 30000 ft = 9144 m
[16:09] <craag> lol that worked well
[16:10] <craag> pull reqs welcome https://github.com/philcrump/SIbot
[16:10] <eor> I think it's a shame, the way the aviation world is stuck with retard units
[16:10] <eor> although some regions do use meters
[16:11] DK6OV (~DK6OV@2a02:560:4259:9700:dc8:df8b:8808:a389) left irc: Quit: Leaving
[16:11] DK6OV (~DK6OV@2a02:560:4259:9700:dc8:df8b:8808:a389) joined #highaltitude.
[16:11] DK6OV (~DK6OV@2a02:560:4259:9700:dc8:df8b:8808:a389) left irc: Client Quit
[16:12] DK6OV (~DK6OV@2a02:560:4259:9700:dc8:df8b:8808:a389) joined #highaltitude.
[16:13] <michal_f> 1/5
[16:13] <michal_f> well, yesterday sibot instructed me about inches when I said 1/5
[16:14] <craag> 1/5 in something
[16:14] <SIbot> In real units: 5 in = 12.70 cm
[16:14] <craag> You've distracted me now, I'm looking at it.
[16:16] <michal_f> :)
[16:17] DK6OV (~DK6OV@2a02:560:4259:9700:dc8:df8b:8808:a389) left irc: Quit: Leaving
[16:22] <SpacenearUS> New vehicle on the map: 03LOGIC - 12https://tracker.habhub.org/#!qm=All&q=LOGIC
[16:23] <eor> that code in github is probably not up to date since there's nothing about inches in there
[16:25] <craag> Yep spotted that sorry!
[16:28] SIbot (~nodebot@philcrump.co.uk) left irc: Remote host closed the connection
[16:29] SIbot (~nodebot@philcrump.co.uk) joined #highaltitude.
[16:29] <craag> 1/5 ft
[16:29] <craag> 5 ft
[16:29] <SIbot> In real units: 5 feet = 1.52 m
[16:29] <eor> I don't think there's any easy way around it. Just leave 'in' out of the expression.
[16:30] <eor> you're just gonna get more false positives than useful hits
[16:30] <eor> 1.5 ft
[16:30] <SIbot> In real units: 5 feet = 1.52 m
[16:30] <craag> I don't claim to be particularly good at regex but I've had a go. It now uses lookahead and lookbehind which should reduce a lot of the errors
[16:30] <eor> your regex doesn't understand . as a decimal separator
[16:31] <eor> 9fet
[16:31] <SIbot> In real units: 9 feet = 2.74 m
[16:31] <eor> funny
[16:32] <eor> -1°F
[16:32] gb73d (gb73d@79-76-139-36.dynamic.dsl.as9105.com) joined #highaltitude.
[16:32] <eor> seems you've disabled the fahrenheit part
[16:32] <eor> it doesn't understand negative numbers
[16:33] <eor> 9a9 ft
[16:33] <SIbot> In real units: 9 feet = 2.74 m
[16:33] <eor> 9a9 lb
[16:33] <SIbot> In real units: 9 lbs = 4.1 kg
[16:35] <eor> 9999999999999999999999999999999999999999999999999999999999999lb
[16:35] <SIbot> In real units: 999999999999 lbs = 453591999999.5 kg
[16:36] <eor> 0.,9lb
[16:36] <SIbot> In real units: ,9 lbs = 4.1 kg
[16:37] <eor> 0. lb
[16:38] <eor> .9 lb
[16:38] <SIbot> In real units: .9 lbs = 408 g
[16:39] <eor> 00000000000.0 lb
[16:39] <SIbot> In real units: 00000000000 lbs = 0 g
[16:48] YO3IHG (050c76fd@5-12-118-253.residential.rdsnet.ro) left irc: Remote host closed the connection
[16:49] SIbot (~nodebot@philcrump.co.uk) left irc: Remote host closed the connection
[16:52] YO3IHG (050c76fd@5-12-118-253.residential.rdsnet.ro) joined #highaltitude.
[16:55] <PE2BZ> YO3IHG, what´s up ? Did your head stop spinning ?
[16:55] <PE2BZ> Eduard asked me to take a look at you ;-)
[16:56] <YO3IHG> not yet, hi
[16:56] <YO3IHG> i am installing everything again
[16:56] <YO3IHG> am switch from RPI4 to 0
[16:56] <YO3IHG> i think RPI4 is the problem
[16:57] <YO3IHG> "gpio readall" does not give me anything on RPI4
[16:57] <PE2BZ> Not completely impossible, but usually nothing which can not be fixed with different settings.
[16:58] <PE2BZ> No output at all ?
[16:58] <YO3IHG> no
[16:59] <YO3IHG> just some unknown something......
[16:59] <PE2BZ> But the Pi4 is currently not accessible I assume ?
[16:59] <YO3IHG> but not like the RPI0
[16:59] <YO3IHG> no, both cards are erased and currently writing again
[16:59] <YO3IHG> i willl put the GTW on RPI4 and the PITS on RPI0
[17:00] <PE2BZ> I have a Pi4 running satnogs, so not setup for gpio. What did I need to install for the wiringpi... I guess the answer is in this question....
[17:01] <PE2BZ> Know your hardware.... Pi 3B+ on the top of the output ;-)
[17:02] <PE2BZ> Let me try another one.
[17:02] <YO3IHG> RPI0 is back online, so i will install PITS quickly
[17:03] <PE2BZ> Not quickly....
[17:03] <PE2BZ> Is it a Pi zero W ?
[17:03] <YO3ICT> PE2BZ If it is a Zero W, might be the BT causing issues?
[17:04] <YO3IHG> i will disable it
[17:04] <YO3IHG> zero W yes
[17:04] <PE2BZ> YO3ICT, indeed that was what I ment
[17:05] <YO3IHG> i disabled BT on the RPI4 and it didn't worked
[17:05] <PE2BZ> Found my Pi4
[17:05] <PE2BZ> pi@raspberrypi:~ $ gpio readall
[17:05] <PE2BZ> Oops - unable to determine board type... model: 17
[17:06] <YO3IHG> exactly what i got before
[17:08] <PE2BZ> From the pi stack exchange page:
[17:08] <PE2BZ> Now that wiringpi is deprecated (and requires a download from the author's site to work on the Pi4) the future of the gpio readall command is unknown.
[17:08] <PE2BZ> The good news, I am assembling an add on board ( YO3ICT knows which) for this Pi4 so I might run into the same problems. Let´s find out...
[17:10] SIbot (~nodebot@philcrump.co.uk) joined #highaltitude.
[17:14] <YO3ICT> PE2BZ Same board at YO3IHG
[17:15] <YO3ICT> https://imgur.com/a/GOREl7z Testing the upcoming floater tracker
[17:15] <PE2BZ> YO3ICT, only one 1278 left over here ;-)
[17:15] <YO3ICT> Same here :/
[17:25] <PE2BZ> YO3ICT, what a very large GPS wire ;-)
[17:27] <YO3ICT> PE2BZ I wanted it bigger :(
[17:28] <PE2BZ> Attach it to the closest satellite ;-)
[17:28] <SA6BSS-Mike> lol
[17:28] <SpacenearUS> New vehicle on the map: 03Yc14roh_chase - 12https://tracker.habhub.org/#!qm=All&q=Yc14roh_chase
[17:29] <SA6BSS-Mike> reminds me, I saw someting on hangouts...
[17:31] <YO3ICT> PE2BZ Be careful. https://imgur.com/a/4EAqjGb
[17:32] <SA6BSS-Mike> whats that?
[17:32] <SA6BSS-Mike> your 3d printer going crazy? :)
[17:32] <YO3ICT> a big blob of 3d printing filament gone wrong
[17:33] <PE2BZ> Awwwww.....
[17:33] <PE2BZ> Mine was silver ;-)
[17:33] <PE2BZ> All dripped off to the bed now :-)
[17:34] <YO3ICT> SA6BSS Not mine. Mine's shipping in september.
[17:34] <YO3ICT> No more printing payloads on other's printers
[17:34] <SA6BSS-Mike> :) cool
[17:35] <PE2BZ> Not mine either ;-) Mine only crashed in the printed object after pausing the print, adjust the PINDA sensor and unpause. #neverdothatagain
[17:36] <PE2BZ> https://photos.app.goo.gl/82KBdD2VwtaQBQzF6
[17:36] <PE2BZ> Printing happily ever after :-)
[17:36] <YO3ICT> PE2BZ You can stop the print directly from the slicer to unload and load filament. So printing in multiple colors without the MMU
[17:38] <PE2BZ> YO3ICT, I need to study a bit :-) I tried to use the slicer just to edit an object to be 5 mm high instead of 2 mm. That did not work, came out as 2 mm. I did try the same in Design Spark, but somehow I made an ¨Y mistake¨ where the printer stopped because I was going to print 3 mm below the bed.
[17:39] <YO3IHG> now i installed the gateway on the rpi4 and surprise, it's not working like on the rpi0
[17:39] <YO3ICT> AFAIK, the slicer can only scale objects
[17:39] <PE2BZ> YO3IHG, so, also the gateway does not work ?
[17:40] <PE2BZ> YO3ICT, are the GPIO´s fixed on the board?
[17:41] <PE2BZ> I am almost ready for testing myself.
[17:46] <daveake> What board is this ?
[17:47] <PE2BZ> YO3ICT pi zero add on board.
[17:47] <PE2BZ> Which he used on his Pi Zero camera flights
[17:54] <daveake> So it used to work and doesn't work now?
[17:55] <PE2BZ> No, it works on a Pi Zero but not on a Pi4 where the GPIO readall also gives an error message ( unknown board ID)
[17:55] <daveake> Ah right
[17:55] <PE2BZ> I am close to testing the same board on a Pi4 myself. Forgot to wire CE1 choice....
[17:55] <daveake> Someone needs to fix wiringpi then
[17:56] <daveake> Definitely worth checking for an update
[17:56] <PE2BZ> You´re not volunteering are you ?
[17:56] <daveake> hahahahaha
[17:56] <daveake> no
[17:56] <PE2BZ> There appears to be a seprate download on the authors page
[17:56] <PE2BZ> https://raspberrypi.stackexchange.com/questions/102421/is-the-gpio-readall-command-compatible-with-rpi-4
[17:57] <daveake> The author decided to retire from maintaining it
[17:57] <YO3IHG> i moved the gateway to rpi4 and not it is not working anymore
[17:58] <YO3IHG> i moved the PITS to rpi0 and trying to configure it
[17:58] <YO3IHG> sa wiringpi is not working anymore on rpi4?
[17:58] <PE2BZ> Let me try to find the Pi4 version for wiringpi
[17:58] <daveake> The Pi4 is complete overkill for either
[17:58] <daveake> Drag a Pi 1 out of the cupboard
[17:59] <PE2BZ> No no no ;-) not for me, it will combine with an rtl-sdr as remote setup in a nice quiet area in the northern part of Holland :-)
[17:59] <PE2BZ> Pi1... with the blue audio connector ?
[17:59] <daveake> :)
[17:59] <daveake> heh I have several
[18:00] <daveake> Plenty fast enough
[18:00] <daveake> Anyway sounds like installing the latest wiringpi should sort it
[18:01] <PE2BZ> http://wiringpi.com/wiringpi-updated-to-2-52-for-the-raspberry-pi-4b/
[18:01] <PE2BZ> This makes working gpio readall for me
[18:02] <PE2BZ> I tried first with freshly wiringpi but that does not work (yet)
[18:04] <SpacenearUS> New vehicle on the map: 03KD9IEA-11 - 12https://tracker.habhub.org/#!qm=All&q=KD9IEA-11
[18:05] <PE2BZ> sudo halt
[18:06] <PE2BZ> Mmmm
[18:09] <YO3IHG> unfortunately i do not have any older rpi but a single zero
[18:09] <YO3IHG> the rest is rpi4
[18:10] <SpacenearUS> New vehicle on the map: 03ARY3 - 12https://tracker.habhub.org/#!qm=All&q=ARY3
[18:10] <PE2BZ> YO3IHG, http://wiringpi.com/wiringpi-updated-to-2-52-for-the-raspberry-pi-4b/
[18:11] <PE2BZ> can you install that and test gpio readall again after that ?
[18:14] <YO3IHG> ok, the gpio readall is working now on 4
[18:14] <YO3IHG> let me reboot and start the gtw
[18:15] <pc4l_hab> ICT board is using CE0??
[18:16] <YO3ICT> is a solder bridge
[18:16] <pc4l_hab> RR
[18:16] <YO3ICT> on the bottom, but I reversed ce0 and ce1 on the silkscreen
[18:16] <YO3ICT> its backwards :D
[18:18] <pc4l_hab> that´s a slow PI4 :)
[18:19] <PE2BZ> With the new wiringpi, the CE1 selected in reverse on the hardware, and CE0 set in the software I get an RSSI of -97 on 16 cm wire
[18:19] <YO3IHG> guys, this http://wiringpi.com/wiringpi-updated-to-2-52-for-the-raspberry-pi-4b/ seems to be working on rpi4
[18:19] <YO3IHG> many thanks!
[18:24] <SpacenearUS> New position from 03BZ-1a after 036 days silence - 12https://tracker.habhub.org/#!qm=All&q=BZ-1a
[18:26] <YO3IHG> working now, both PITS and GATEWAY
[18:26] <YO3IHG> thank you all for help!
[18:28] <daveake> Woo
[18:30] <daveake> PE2BZ: So wiringpi swaps CEO/1 on the Pi4 ?
[18:30] <PE2BZ> No, YO3ICT did that on his board. Jumper bridge moved to the bottom but not mirrorring the text.
[18:30] <YO3ICT> no, thats my fault
[18:30] <daveake> Oh ok
[18:31] <daveake> Good :)
[18:31] <YO3ICT> was fixed in the latest revision, that flew with the Taoglas antenna
[18:31] <PE2BZ> WiringPi needs 2.52 to work and that´s not yet in the distribution
[18:31] <daveake> Ok
[18:31] <YO3ICT> pcbs made somewhere netherlands/germany by aisler, incredible quality
[18:33] <YO3ICT> have a good one, all of you, 73
[18:33] YO3ICT (YO3ICT@188.25.199.68) left #highaltitude.
[18:36] <PE2BZ> YO3IHG, does your gateway Pi4 receive more as one packet ?
[18:38] <PE2BZ> Mine receives one packet from my tracker, turns the RSSI to -164 after that
[18:40] <daveake> So the SPI fails. As a test, see if setting the SPI pin manually fixes it. CS_1=<pin>
[18:41] <daveake> Maybe I should recode to avoid wiringpi
[18:44] <PE2BZ> Wher <pin> also means the wiringpi pin ?
[18:45] <chris_99> isn't wiring pi deprecated?
[18:46] <daveake> Yes wiringpi pin
[18:47] <daveake> Yeah the wiringpi guy decided to stop developing or supporting it
[18:47] <daveake> I believe he got fed up with dealing with derp
[18:48] <PE2BZ> daveake, If I type the first two characters of your nick but still in the LoRa screen my frequency is 101 kHz off ;-)
[18:48] <PE2BZ> but no change, one string, rssi to -164 so let´s see if YO3IHG has the same problem.
[18:49] <pc4l_hab> he has, he mentioned earlier
[18:50] <PE2BZ> daveake, after every retune the RSSI goes to normal values again and it receivs one packet again.
[18:50] <pc4l_hab> 12:16 <yo3ihg> i just want to see if the lora module is transmitting
[18:50] <pc4l_hab> <yo3ihg> but i get a single telemetry packet at PITS startup
[18:51] <PE2BZ> That´s the tracker TX part. Wirinpi on the pi4 needs a special built version
[18:52] <PE2BZ> With that version my Pi4 gateway works, receiving only one packet till I tune up or down so there is a problem with either the Pi4 / wiring pi combination or my hardware.
[18:52] Action: PE2BZ did not disable bluetooth on the Pi4.
[18:54] <daveake> Doesn't matter
[18:54] <chris_99> daveake: is PITS your project btw?
[18:57] <PE2BZ> daveake, you´re right. Doesn´t change anything
[19:13] <PE2BZ> Moved a PITS board (868 / 434 ) from Upu to the same Pi4, changed the DIO settings but the same error happens. Reverted from 2.52 wiringpi to 2.50 and with that I get an Segementation Fault as soon as one packet is received.
[19:14] <PE2BZ> Going to stop for the night. pc4l_hab has it running on a Pi4 so we will check tomorrow together for differences.
[19:14] <PE2BZ> Thanks so far, enjoy the evening. Night .Morning,
[19:18] <daveake> I'll probably set one up and recode for something other that wiringpi
[19:26] gb73d (gb73d@79-76-139-36.dynamic.dsl.as9105.com) left irc:
[19:26] <SpacenearUS> New position from 03W5KUB-18 after 0318 hours silence - 12https://tracker.habhub.org/#!qm=All&q=W5KUB-18
[19:38] YO3IHG (050c76fd@5-12-118-253.residential.rdsnet.ro) left irc: Ping timeout: 245 seconds
[19:49] <michal_f> didn't read all discussion re wiringPI, but
[19:49] <michal_f> I used pigpio on my last rPI tracker
[19:57] michal_f (~mfratczak@17-153-196-109.itvmedia.pl) left irc: Ping timeout: 264 seconds
[20:04] chris_99 (uid26561@gateway/web/irccloud.com/x-yjzvmmhbbcgndevz) left irc:
[20:10] <daveake> Same. Just need to go and edit PITS and the gateway
[20:11] <daveake> wiringpi seems to be becoming abandonware/brokenware
[20:12] michal_f (~mfratczak@17-153-196-109.itvmedia.pl) joined #highaltitude.
[20:28] michal_f (~mfratczak@17-153-196-109.itvmedia.pl) left irc: Ping timeout: 240 seconds
[20:54] snaked (~snaked@pdpc/supporter/active/snaked) left irc: Read error: Connection reset by peer
[20:54] snaked (~snaked@pdpc/supporter/active/snaked) joined #highaltitude.
[21:32] inode (~inode@unaffiliated/inode) joined #highaltitude.
[22:11] Lahti (~Lahti@dyvypnfhvzmcz7w-yw0tt-4.rev.dnainternet.fi) left irc: Quit: Lähdössä
[22:29] inode (~inode@unaffiliated/inode) left irc: Quit: 
[22:46] LazyLeopard (~irc-clien@chocky.lazyleopard.org.uk) left irc: Quit: Textual IRC Client: www.textualapp.com
[23:50] <SpacenearUS> New position from 03N4XWC-1 after 03a day silence - 12https://tracker.habhub.org/#!qm=All&q=N4XWC-1
[00:00] --- Sat Jul 4 2020