I’ve been trying to update the firmware on my HelTec LoRa32 iGate using the web-based flasher, and everything seems to work right up to the point the installation is completed.
However, nothing I’ve tried gets the device to boot again afterwards. The screen remains blank, and there’s no sign of either a network connection attempt or the special first-time configuration WiFi either.
Edit: It REALLY helps if you upload the correct version of the code!
Despite what it says on the box, this device is a HelTec V3, not a HelTec LoRa32…
I must’ve known when I got it, because it all worked fine first time round, but I couldn’t remember off-hand wen it came to updating the firmware, so I looked for the box. It’s that little red one…
Edit: Just measured it as 28 turns (outside diameter 4.42mm) of 0.8mm wire, plus up to about a centimetre or so to the centre pin (but some of that’s inside the connector)…
Some interesting stats coming from https://lora-aprs.live/ - some fabulous distances last Friday - including my own low down iGate receiving John @G3WGV 's digipeater at 229km. This wasn’t recorded by APRS-IS though:
This table is available here (direct link): LoRa APRS Top Tens. The stats show that my iGate is hearing quite a lot more than it actually manages to gate to APRS-IS.
Looks like Friday was a particularly good day for UHF, @GW4BML 's iGate gating some brilliant distances including over to @M1GEO in the fens:
I’ve finally managed to get my iGate mounted properly in the attic, with an external antenna (it is Station info for G7WKX-10 – aprs.fi – live APRS map ). This should provide good reception coverage for Liverpool, Runcorn and North Wales…
Looking forward to seeing what it receives now - hopefully something other than my own tracker in our front room
My iGate mostly receives beacon transmissions from other iGates. It heard M0XZS-2 (44.5km away near Malvern) 96 times yesterday, and G3CWI-13 (171.8kms away) once. It only received two mobile stations, M0HCU-7 (17 times) and G4OYX-4 (3 times). Some days are busier…
Thanks Rick, mine hasn’t received anything other than my own tracker and that was just local. I was at a high point yesterday evening, but my iGate didn’t receive my tracker. I might need to look at altering the antenna location - will see how it goes over the weekend as I imagine there will be a few more people around.
Is your antenna directly connected to the iGate?
The signals are weak so if you have a long run of coax hardly anything gets to the iGate. I was hardly receiving anything with a 6 m run of LMR240, but connecting the antenna directly to the SMA on the board has improved things a lot.
Hi Pete, I have 1m of LMR240 from antenna to iGate. I will have a look on Sunday and see if I can connect it directly.
SOTA tomorrow takes priority
73, Simon
Yesterday was one of those. Best direct distance reported was just over 315 km from M0MZB-15, but M0MZB-15 also relayed positions from GW3ATZ-11, M0MZB-8, M0MZB-10, MB7UCW-10 and MB7UWS-2. Those last two (at least) are other iGates beaconing.
Sounds like an antenna check is in order. Maybe also a check for strong nearby transmissions that might be swamping the LoRa data.
Thanks Ross @G6GVI I will take a look at my antenna set up tomorrow.
Thanks Rick @M0LEP I will take a look soon. Nothing on 439.9125 here on my SDR, so I’m happy the frequency itself is clear locally, but worth a check. I suspect it’s the antenna/coax.
I’ve turned off M1BUU-10 today. I had intended to run the iGate to cover G/NP-004, G/NP-005 and G/NP-010. My iGate did receive from those summits, but they seem to be better served by other iGates.
Now that winter is on it’s way my solar based power system is diminished. I don’t think that my iGate will be missed!
