I am wondering if my message problems are due to packets from multiple igates colliding over RF, and so the digipeater can’t decode them.
I now only seem to get the digipeater to respond if I send directly from my igate using the TNC…it doesn’t work from DroidStar (the latter presumably leads to all igates who have heard M0MZB-15 in the last 30 minutes Tx-ing the packet and overlapping)
I guess it also depends on how those iGates are setup and whether they are setup to TX messages and what filter they have in place.
Just thinking about this, if you are not using the external voltage monitor, you could use this to monitor the solar panel voltage. This could be then setup to put the the igate into sleep mode when the solar panel voltage drops off at night. Effectively creating a sleep at night mode.
Is there a risk this would switch it off during the day if it’s misty? Or do the panels convert some power even in low light?
The hills here above the Dee Valley have been in mist since the weekend. My 40w solar panel on MW0PDV-14 is still producing enough power during the day to power a 4G router, the igate and charge very slightly. This did surprise me.
The problem is it’s using more at night than the charge it’s getting during the day in these misty conditions.
The device knows its latitude, if it has a RTC then it can know the time…a rough lookup table should be able to give sunset and sunrise times. So this ought to be possible in software.
So far, GW4BML-10 is going strong, running the 4G router and Igate from a very remote hill top in mid-wales, using a 12v 110AH car battery with a 235w solar panel charging the battery throughout the day.
I’m hoping this year it’ll continue working with no power loss over the winter months, fingers crossed!
Can you not track it? 
Seriously though, was it powered off when you lost it? Or is there no igate coverage to give you more tha a vague idea where it is?
It was powered off as there are no local igates low down. Once I get up high then I usually turn it on.
It was clipped on the top of my backpack but the trees were low and probably brushed it off.
Good work @M0MZB 
I’m currently camped ontop of g/ld-025. The HF bands seem to be in very odd shape though
Has anyone managed to send a spot using LoRa APRS with Android, Serial Bluetooth terminal, BLE and Heltec wireless tracker? I can connect to the tracker from the terminal app. When I sent a message I could see that my iGate had received the message but it was complaining that it was the wrong GPS format. There seemed to be an additional character at the front of the message. I’ve updated to the latest tracker software and now I don’t seem to be able to send anything.
I’ve just put the latest software on. This includes my fix for the dodgy button.
When I try BLE I can see the message is getting to my iGate but it still gives the wrong GPS format error. There is an extra character in front of my call which is obviously confusing it. I’ve tried changing all the line ending characters but it does not work. I don’t know whether this is being inserted by the Bluetooth terminal app or by the tracker software.
@G3CWI Did you get this to work?
hi, when sending BLE over terminal:
WELL, I got the HeltecWireless Tracker boot loop blues too
currently checking how to solve this as even adding caps and all did not fix the issue
Same here, a 100u cap did nothing to stop it
We were not imagining it!
false news: it was my and my fat fingers testing new code and was printing more lines than it can be printed! 
