BTW the resonant frequency is not the frequency with the best VSWR but the frequency with Xs=0
So is this antenna only suitable for those having the proper RF equipment to measure antenna performance and are willing to tune the antenna themselves (and not a good buy for others)?
Why (and where) is it not waterproof?
A post was merged into an existing topic: The LIBRARY basement part 12
No. The antenna is performing well enough for many applications.
That is because the top is hard-plastic and I expect that the capillary effect will allow water to enter. As the internal connector is an F-type (from what I know is this connector 75 ohms, not 50) the water might leak into the coaxial cable connected to it.
No, there is additional length taken from the rods to tune it.
Using OTAA & TTSCE (TTN V3)
This is one of my Raspberry Pi Pico’s + RFM95 using LoRaWAN to connect to TTN V3.
It runs the LMIC-node example application.
NOT on the WorkBench any time soon …
How are you finding the LT-33222? I have a US-915 version that I need to install the AU915 firmware on before I can use it. I’ve got some ideas for agricultural use.
Apparently too cute to send to a customer …
I started from a moteino based, added tpl5110 for managing deep sleep, added place for rfm95w, added place for bme280 ( with polish nails xD) , added patch antenna, those little baby run for 1 year and half now on 2 AAA lithium cells
I also made the same but this time adding a mofset to switch off the moisture sensor.
All run on ttn v3, with custom optiboot firm
I can share diagram on easyEDA.
This is my Adafruit QT Py (SAMD21) board with HPD13A LoRa module and SSD1306 OLED display running LMIC-node connected to TTN V3.
Support for the Adafruit QT Py has just been added to LMIC-node.
I had a productive day working with the owner of a local WISP to perform a test installation and range testing at a proposed gateway colocated on one of his sites. This didn’t happen in my workshop but was on site at a PoP on a hill. Still I think it counts for here.
As they say no contact with the enemy goes as planned which was true today. The WISP guy had some trouble with getting a connection to the internet via the router used to act as CPE instead of connecting directly to his core. That was solved with noticing a VPN program had crashed and the laptop was trying to connect to a different part of the core and was fixed with a reboot.
It was then my time to shine. While checking if the gateway had booted we discovered that the status is no longer displayed in V2 of the console so I had to hastily read the migration documentation and move my gateway from V2 to V3. This was actually easier than I was expecting and went well with the gateway talking to the V3 console. I’m going to move over my other gateways in the next few weeks but I might leave one on V2 until I know all V2 apps are moved to V3 though.
I had a T-Beam module loaded with TTN-Mapper firmware installed but forgot to charge the 18650 battery. None of the powerbanks I brought with me would power it properly nor would the other guy’s USB charger. We eventually got enough power into the battery to get the T-Beam to boot.
From there it was time to drive around testing range with two different antennas. The best we got was about -110dbm RSSI with -2.5 SNR at about 13KM for the trial gateway. From there we did more driving to add more coverage to TTN mapper for the local area. We happened to get 20KM to a different gateway in a nearby town which also impressed me.
I’m quite pleased with how the day went. I’ve got a new collaborator to work with, we have a great idea how much actual range we have compared to simulated coverage and I have ordered a better gateway based on the SX1302 chipset to go into production at the site. We have plans to rollout LoRaWAN coverage at some of his other sites in the future if the next stage of collaboration works out.
As the current world wide shortage of, well, anything really, spent 30 minutes today tracking down some 220uF Electrolytic capacitors, 5mm pitch that weren’t gold plated, let alone finding a LoRaWAN module and an MCU to suit, I’ve gone back to me roots and updated it a little:
It’s an ATmega4808 28 pin SSOP which is, with a fine tipped soldering iron, feasibly hand-solderable. I’m using a trusty RFM95. The 4808 has 48KB of flash and 6KB of SRAM which is half as much again of flash and three times more than the trusty 328P of Arduino Uno/Nano/Pro Mini fame.
I’ve put the Optiboot boot loader on it, so the Arduino IDE thinks it’s an Arduino and I used the latest MCCI LMIC (v4) that provides v1.0.3 LoRaWAN to test OTAA and the forbidden fruit that is ABP and all is well.
Having turned off some of the junk for Class B but turned up logging to 11 (as I want to explore the MAC commands coming down from v3 a bit more), it took up 26741 bytes of flash (54%) and 1216 bytes SRAM (19%). Plenty of space for sensors and gratuitous text strings. With logging set to 0, it uses 22882 bytes of flash.
So for non-critical applications, I suspect this will be my go-to build for a while until the silicon universe stops ebbing & flowing quite so much.
An alternative to EdgeImpulse for edge AI classification before sending result over LoRaWAN?
Not on any workbench for a rather long time … … is it me or is supply going backwards?
Looks like the latest Microchip MPLAB ICE 4 emulator, programmer, debugger is out and available in stock with latest IDE support available for download if interested (AVR, SAMD users et al)
Think I’ve just found the idea power supply for my next LoRaWAN GPS Tracker development:
Now how can this be adapted/adopted to support remotely deployed RPi based gw’s? Main weakness is vulnerability for SD card corruption, usually during uncontrolled power out, so if this could help fix…?
Pity it’s only Pi 4 onwards…to many 2b/3b+ & 0Ws deployed so far… (less power draw than Pi4’s)…
Only if they are on a network as they have to download ~1Gb as a minimum - although could be via LTE but it has to be an external network to the Pi as it can’t do anything until it’s installed.
It would also need to be able to detect a corrupt SD Card and trigger a refresh - bit hard to do if the OS is borked - but a watchdog could intervene - but it would be a sophisticated watchdog with a network - maybe another Pi?
Perhaps you could create a spec for a remote setup so we can have an alternative to Balena and then the community could come together to create a solution …
Academic at present but stock coming mid March …
How about using CM4 with eMMC on Sourcekit PiTray Mini. No more corrupt SDcards. Combined with balena a winning combination.