--You received this message because you are subscribed to the Google Groups "UKHAS" group.To unsubscribe from this group and stop receiving emails from it, send an email to ukhas+unsub...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/bc4ac3d5-df13-aa47-431d-0a378778942c%40randomaerospace.com.
To unsubscribe from this group and stop receiving emails from it, send an email to ukhas+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/859681446.837150.1593537947563%40mail.yahoo.com.
--
You received this message because you are subscribed to the Google Groups "UKHAS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ukhas+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/bc4ac3d5-df13-aa47-431d-0a378778942c%40randomaerospace.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/CAJn3SCovSESyXUGw8-ii%3DSDRj%3D4SO%2Be0uZ8S_HvWw3DtaByK4w%40mail.gmail.com.
Yes I forgot to mention that - it's an original RPi model B (I
knew I would find a use for it one day) that sits on my network
bridging TTN and habitat 24x7 for this application. After some
timeout tweeking its been running flawlessly for a couple of
months.
see:
https://revspace.nl/TTNHABBridge
for details.
Thanks to Bertrik Sikken who wrote it and Medad for pointing me in the right direction.
Steve
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/CAN3_bBrHgpUR%2Btrcte9PDPKhVr%3DEn3qcpSkwpEKAkryPMTo53Q%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/1a6d4b8b-6a5e-105e-7fbb-e01483477ed5%40randomaerospace.com.
Perhaps, but surprisingly little LoRa that I have seen round here - LoRa is quite easy to distinguish from all the other 867/868 activity - I would have thought they would have been reasonably evident especially with a yagi and or rural location.
I was expecting the new positions to pop up reasonably quickly on the TTNmap ? - and thus folk would know when a new packet had been received. Data seems to make its way from the receiving node to the TTN console almost instantly - but I'm not sure how long it would take to get to the TTNmap - spacenear lags behind by anything up to 15 seconds.
Steve
If this is a LoRaWAN flight, on the standard LoRaWAN\TTN frequencies, how would you be able to monitor it with an SDR for frequency shifts, there would likley be a lot of other activity on the same frequencies ?
--
You received this message because you are subscribed to the Google Groups "UKHAS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ukhas+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/6415e07f-9b98-4a33-b461-00a7e767aeb3o%40googlegroups.com.
Thanks Ben - frankly I'm not 100% sure what I'm doing on TTN - but mostly it seems to make sense.
yes it shows I have a ttnmapper integration on that application - is there something I need to do to enable "track"? or perhaps its not showing a track because the transmitter hasn't moved its position yet?
Steve
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/CACbGgOuaDMaqspUK7tDADcWcdaxs0KRU_CRchzKJtP0NruCrgg%40mail.gmail.com.
If I do chase the flight I can now travel any distance for an outdoor
activity.
Very wise. In any event an East coast sea landing is much more probable.
Steve
On Tuesday, June 30, 2020 at 11:47:42 PM UTC+1, G8KHW wrote:If I do chase the flight I can now travel any distance for an outdoor
activity.
Stay out of Wales.
Stay out of Wales.
Plenty of coverage @13:21.What Spreading Factor is in use ?
--
You received this message because you are subscribed to the Google Groups "UKHAS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ukhas+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/825e740d-b8ad-456a-bd9c-3fdc4341b20fo%40googlegroups.com.
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.
Steve
To unsubscribe from this group and stop receiving emails from it, send an email to ukhas+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/859681446.837150.1593537947563%40mail.yahoo.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/8245a00f-c930-684d-eeed-a0e62d917949%40randomaerospace.com.
Hi John
We built this arduino pro mini https://www.thethingsnetwork.org/labs/story/lorawan-gsp-tracker
The only thing we changed for a good altitude is
coords[8] = altitudeGPS >> 16;
coords[9] = altitudeGPS >> 8;
coords[10] = altitudeGPS >> 0;
There are more lorawan projects on github, almost doing the same as the above
GL
Marcel (PC4L)
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/CAJn3SCpL7fTcucX19oseiC%3Dg%2B%3DrdGKJej%3DCWS7cr_CELH-%2BUMA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/73C6D703-A2B3-4324-AC38-720DFB2BED54%40hxcore.ol.
To unsubscribe from this group and stop receiving emails from it, send an email to uk...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/859681446.837150.1593537947563%40mail.yahoo.com.
Virus-free. www.avg.com
--
You received this message because you are subscribed to the Google Groups "UKHAS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to uk...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/8245a00f-c930-684d-eeed-a0e62d917949%40randomaerospace.com.
--
You received this message because you are subscribed to the Google Groups "UKHAS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to uk...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/CAJn3SCpL7fTcucX19oseiC%3Dg%2B%3DrdGKJej%3DCWS7cr_CELH-%2BUMA%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "UKHAS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to uk...@googlegroups.com.
I guessed this might come up: so I had spent some time checking
into the UK duty cycle and LoRaWAN limits and mulling it over.
The flight was designed to keep within the regulatory duty cycle
limits - but it bust the LoRaWAN airtime limits. Here is the
rational:
Regulatory limits: LoRaWAN channel frequencies 868.1 868.3 and 868.5MHz fall into one EU band and the channel frequencies 867.1 867.3 867.5 867.7 and 867.9MHz into a different EU band - both have a duty cycle limit of 1%. I made sure that I didn't break the duty cycle limits in either band - but that gave me overall 2% airtime to play with.
The packet rate used was adaptive and at its lowest in the middle of the flight and highest above 36Km - the duty cycle limits are defined as per hour without defining where the hours start and end - that also gives some flexibility.
The packet rates were chosen to keep within the regulatory duty
cycle limits throughout the flight.
LoRaWAN: The SF12 packets were chosen for range, as a
small part of the reason for the flight was to try for the LoRaWAN
distance record, also for recovery on the ground I wanted to give
myself the best chance if it landed in a radio dead zone. The
packets are pretty much minimal GPS - and the TTN data page
estimated the airtime at 1.1 seconds, so I know that over the
course of the flight it will have broken the 30 seconds per day
LoRaWAN airtime limit.
In my defense I would say that other people attempting the
distance record have also ignored that limit and I don't see why I
should be at a disadvantage if I want to attempt it (as long as
I'm not breaking the regulation).
Other thoughts on the experience: I agree that in normal operation for balloon tracking a lower SF and hence shorter packets would be more than adequate. Maybe to get the most out of the system adaptive SF would be the way to go.
I sill have reservations about using LoRaWAN for latex up-down
balloon tracking. In the air for tracking you can't argue - the
coverage is massive - I don't think a packet was lost over the
entire flight above 500m. However on the ground at launch and
recovery locations there are a couple of things that are a pain:
a) the channel hopping b) the need for internet coverage.
The channel hopping either means you have to have an expensive full LoRaWAN gateway - or several single channel packet forwarders set to different frequencies - either way more cost than needed.
Because LoRaWAN packets are encrypted you can't decode them on a gateway - this means that the gateway needs internet coverage in order to get the packet to TTN for it to be unencrypted and hence find the GPS location of the transmitter (and get it back to you). In some rural locations this will be a challenge. At the launch site yesterday coverage was iffy and I had to loft my hotspot in order to determine the GPS had locked before launch. Likewise I was lucky the landing location had mobile internet coverage.
I think some form of mixed system would be best - with plain LoRa on the ground and LoRaWAN in the air. That way a cheap single channel receiver could be used on the ground - switching to (or adding) LoRaWAN transmissions once in the air.
Steve
--
You received this message because you are subscribed to the Google Groups "UKHAS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ukhas+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/2568dbe3-66c9-437c-a06b-13ccfbda65d1o%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/7d014bca-d429-0e68-1598-33f82c3403b7%40randomaerospace.com.
FWIW I asked on Twitter a while back about LoRaWAN "fair use" DC limits with a view to choosing a good scheme for HAB, and got a PM saying that they are routinely ignored.
To unsubscribe from this group and stop receiving emails from it, send an email to uk...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/2568dbe3-66c9-437c-a06b-13ccfbda65d1o%40googlegroups.com.
The 1.1 seconds airtime came from the TTN console data page - see
the bottom of this (shows a decoded packet):
https://www.flickr.com/photos/16828840@N07/50090178401/in/dateposted-public/
If that's wrong not my fault. In any event I doubt that the duty
cycle limits were broken as I had allowed some headroom.
The choice of frequency and applying duty cycle is down to the device itself - I had set up the duty cycles on each channel to ensure no more than 1% in each of the two EU bands and hence 2% overall. Hence the upper 3 frequencies (EU LoRaWAN channels 0 to 2) had a slightly higher probability of being chosen for transmission. The choice of channel across the two bands is still random within that limitation.
Like I say my intention was to stay within the regulatory limits
but not necessarily the LoRaWAN fair use.
Steve
To unsubscribe from this group and stop receiving emails from it, send an email to ukhas+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/711354df-0aca-4a18-9b96-44085c65dd04o%40googlegroups.com.
Assuming Stuart's 1.483s figure is correct is correct:
At 1.483s per message the cycle time can be as quick as 71 seconds (allowing for the 1% + 1% duty cycle)
The cycle time up to 36Km was 96 seconds and 32 seconds above that. The balloon spent 13 minutes above 36Km. I define the cycle time hour boundary to be half way through that period above 36Km.
That's 6.5 minutes on a 32 second cycle and 53.5 minutes on a 96
second cycle - giving about 45 or 46 messages in that hour = 78 -
80 second cycle time on average. Therefore I didn't break the
duty cycle limits.
I guess nobody expects the Spanish Inquisition.
Steve
--
You received this message because you are subscribed to the Google Groups "UKHAS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ukhas+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/c088b026-6227-4784-9d23-962096ae1220o%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/a5dd9d11-4d36-07c6-16c3-a277f3c2a691%40randomaerospace.com.
I enjoyed it - particularly as I got it back - which was a bit of a bonus.
I haven't done the post flight analysis of the data yet - there
were certainly some reports over 750Km but the longest distance
is maybe being obscured by incorrect positions on a couple of
gateways (one showing as being 9000Km away in Shenzhen China).
https://ttnmapper.org/track/?experiment=xaben&startdate=2020-07-02
If anyone knows a way to extract the data ordered by distance
(or a way of purging specific nodes from the data) I'd appreciate
the pointer.
Steve
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/CAJn3SCrLmDx9nD7aAuva_J7ok4mcDFC_giApe-%2B%2B241Fdmq%2B_Q%40mail.gmail.com.
If its 1.65 seconds the duty cycle is almost exactly on the on the 2% limit.
Steve
--
You received this message because you are subscribed to the Google Groups "UKHAS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ukhas+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/f22d1f48-36cb-45c9-ab1e-83a0943bce2eo%40googlegroups.com.
Ben
--
You received this message because you are subscribed to the Google Groups "UKHAS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ukhas+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/41a4bdc7-4ca2-c857-f6fb-8fc8b5ef547b%40randomaerospace.com.
A video of the launch of this flight showing use of detaching cardboard de-reeler:-
Steve
--
You received this message because you are subscribed to the Google Groups "UKHAS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ukhas+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ukhas/CACbGgOtZPRONEkR5nrEXPQqeh0V6wcX1sR%2Bj2SrpD0WmgXo2TA%40mail.gmail.com.