MeshCom mobile...
A new toy arrived today, a Lilygo T-Deck Plus - basically a T-Deck with GPS and a case. I flashed this with the latest relevant verison of MeshCom and configured it, and it all works nicely. Not sure yet how long the battery will last but having it all integrated like this means I can wander round the local area and gauge how far it can be received by my hub in the loft. This is all on 70cm, specifically 439.9125MHz.
And here it is:

You should also read:
MeshCom woes
(MeshCom woes indeed but not MeshCom's fault!) As mentioned before I have been fiddling with a RAK setup and MeshCom. I had MeshCom running on both the RAK and a T-Beam device, the former connected by Ethernet adapter and running as Internet gateway, the latter by wifi and connecting to the gateway via RF. My aim was to run the RAK node in the loft connected to the 70cm collinear that is already up there and power it from one of the shack Netgear Ethernet switches. However, it has been running on the shack desk powered over USB because of the issue with the PoE board. Also, it was freezing at random intervals and so I have been using 'cu' to log the console debugging information to file to see if there was any error messages. The board would run like that form one or two days then freeze with no obvious cause - no errors, except twice it froze after a few APRS callsign error messages. Given this and given the plan to run it off a Netgear switch I planned to monitor it and use SNMP to toggle the PoE on the relevant port if it froze. That way it could be run in the loft with no need to access it to reboot it. However, this evening I unplugged the USB in order to check my monitoring scripts. The scripts worked fine and sent me an alert via DAPNET, but once plugged back in the RAK would only run for five seconds or so. Re-flashing the firmware looked to have sorted that but it froze again after 30 minutes. It seems rather fragile. I must add that the same firmware version running on the T-Beam has run perfectly well for over a week. I think I’ve spent enough time on this now. I have reassigned the T-Beam to be the gateway and will experiment with making the RAK into a mobile device. Pity the Ethernet interface and PoE board would be of no use then but as always this is all experimental. The T-Beam connects via wifi of course and I need to see if it reconnects as every so often I need to power cycle the access points. But it has anounced itself to the mesh and is aslo running the web server and my monitoring script is keeping watch. Now I just need to relocate it into the loft with a suitably long USB lead or put a Raspberry Pi up there and power it that way. At least this should be stable enough to see if I can drum up some local interest.
Continue reading...MeshCom
(updated / edited 16/Feb/2025) Having played with Meshtastic a little while ago I came across an amateur radio specific mesh, MeshCom (https://icssw.org/en/meshcom/). Aimed at 70cm operations and with callsigns required I thought this was a better way forward than Meshtastic which, in our area at least is (or was at the time anyway) entirely used for people asking if they can be heard. MeshCom will work on a variety of hardware similar to Meshtastic. I opted for a RAK setup because it has an Ethernet module and I personally prefer this over wifi connectivity. It also gives the possibility of powering the device using PoE which in turn makes it easy to remotely power cycle it. So, the RAK hardware duly arrived via Aliexpress and is easy to assemble, literally plug and play. I got the RAK 4631 RF module, 19007 base board, 13800 Ethernet interface and 19018 PoE module. Firmware is loaded by simply downloading the file from the MeshCom website, althogh it can be quite hard to find. Once that is done, the RAK module is set to appear as a USB disk by quickly clicking the reset button twice. The firmware is dragged across and the RAK resets and loads the firmware up. Nice and easy. It can be configured via the console (e.g.PuTTY, or 'screen' on the Mac) and also via an iPhone app via Bluetooth (BLE). I set it all up with my callsign etc and got a welcome message from a German amateur almost immediately. Nodes can be found via https://meshcom.oevsv.at However, there is an issue with PoE. It doesn't work, although it important to note that this is not a fault of MeshCom. Looking at my Netgear switch it looks like the RAK is trying to negotiate but continually fails. A search on the web found that there is an issue whereby the RAK PoE module is simply not sinking sufficient power and one option is to wire a resistor across its output - I have yet to try this, because there is a further issue... The main issue is that the RAK would freeze at random, sometimes in as little as 5 seconds from boot. This has improved a lot since I installed Meshtastic to ensure the RAK device was ok - it was, that was stable for hours - and reinstalled the firmware after again erasing it all. It managed an hour this way, then froze, but after a reboot it has been running for many hours. I would report this but as yet after 8 months of being a member of the relevant groups.io group I am moderated as a new member and so cannot send messages. Anyway, I also installed the software on a T-Beam and after finding the latest firware (4.34o), which was a struggle in itself, I can send messages from it to the mesh via the RAK device as gateway. There is currently very little MeshCom activity in the UK - 4 nodes I think -…
Continue reading...Meshcom 4.0
(edited 27/7/24 15:34) I recently came across Meshcom (https://icssw.org/en/meshcom/) which broadly speaking is an amateur radio off grid messaging network like Meshtastic. I had a 433MHz Heltec V3 with Meshtastic installed but as there is no 433MHz activity nearby it has just been sat in the abandoned project pile aka the corner of the desk. So, I thought, here is an interesting use even if there are no nodes nearby… yeah, that’s always a bad start. Anyway, as yet the instructions are not as polished as those for Meshtastic and I struggled to get anywhere, routinely managing to lock Windows up completely when using the esptool. When I finally got the thing to look like it had connected the downloader instantly gave an error and packed up. It was then I noticed there is a web flasher (url) so I tried that. Off to a bad start, the flasher reported that the serial port (the device is directly USB connected) was not ready, and no amount of whinging and gnashing of teeth fixed it. Unplugging and re-plugging the Heltec in made no difference. Three times, same thing. I connected it to the Mac and checked that the esptool.py there could see the board in case I had killed it. It found it and gave the correct output. Back to Windows and the web flasher, and on the fourth failure I pressed the reset button on the Heltec and then the installation succeeded. 5th time lucky. [Subsequently I flashed a TBeam device first time and with no issues, so the Heltec may be a bit odd] Some configuration is needed which can be done by commands typed in via the web flasher which also has a console function. After setting the location and wifi access the node appeared on the home LAN and also announced itself to the world via the dashboard at https://srv08.oevsv.at/meshcom/# and after a while it sent all the location information etc via the Internet. The Heltect only has its tiny spring antenna right now as the 433MHz collinear has and rx LoRa APRS gateway connected. As this is really just yet another experiment it may get repurposed again anyway, but it is an interesting project. Time to read. 27/7/24 I repurposed the TBeam unit that was my LoRa APRS rx gate and was basically doing nothing. Meshcom uses the same spot frequency of 439.9125MHz so it needed to go. This has GPS built in and appears to be communicating - it has its location and altitude etc. plus time The node will go back in the oft on a collinear but once there I have no way to communicate with it because for some reason the onboard web server will not work and the Meshcom iPhone app is beta and on Testdrive which I do not want to install on my phone. I may need to run a USB lead down to one of the Pi systems assuming I have serial comms enabled on it. [15:34 rebooting…
Continue reading...