Radio, railways, stuff...

M0RVB

Current Meshtastic setup

After a lot of fiddling about writing code to look at mesh traffic I am on other projects (like, sorting the house out!)... so here is my current state of play... I have an 868MHz node in the loft directly connected to a collinear which is hanging off the rafters. This is powered by USB from one of the Pi systems in the shack. It is set to work over wifi, not BLE as it's just too far away. Its position coordinates are fixed. But I do not need to access it directly, see below. The useful thing here is I have installed the Python CLI on that Pi and can access the node's data stream directly. There is one 868MHz node in the shack with the supplied stubby little antenna. There is no way this can see any other nodes in the local area (I've tried) but can access the node in the loft. So this one has hops set to 4 as it uses one just to get upstairs. This node is set to read position data from the iPhone and can thus go mobile. Well, ok, it could go mobile anyway but at least this way it says where it is etc. But it will probably never go mobile. With this powered over USB from the Mac Mini I can also access the data stream via the CLI. One issue with this setup is that the shack node reports all nodes seen as having an excellent signal strength as it only sees data from the loft node. In reality only a couple of local nodes have anything approaching a 'good' signal strength. Both 868MHz nodes are Lily T3S3 units with no GPS. And there is a 433MHz node, this time a T-Beam with GPS on board, directly connected to a 2m/70cm collinear which is hanging from the window blinds in the shack with some bungee cord. This is of course temporary. I have yet to see any other nodes on 433MHz and I suspect I will quietly give up with that. 868MHz-wise there is a lot of local activity. Currently the loft node sees 180 other nodes, although not all will be active. They do tend to stick and clearing the node database then starts afresh, slowly building up a list as data is seen. And the use? So far, mainly people asking if they can be heard. There are some private channels, no idea what as they are encrypted, pus there are at least two very well sited nodes acting as routers for the area and beyond. One of those is extremely well made.

Continue reading...
M0RVB

More meshtastic

This Meshtastic business seems often very hit and miss. Locally there is an expectation that it will always work and if you can hit one node one day you should always be able to. Or at least that's what I glean from comments. Of course, just a few mW at 868MHz is not destined for long distance comms, and yet I can get 24 miles provided the path is line of sight. Not bad. But I can't manage 1.3km to my nearest neighbour who can get out all over the place. There is a hill to consider there, plus many houses, so not surprising really. Oh yes, and there is the small matter of the antenna still being in the loft so it has to punch through wood and concrete, often wet at that, before it gets to air. For now, at least locally traffic is mostly messages asking if one can be heard. There is a series side of course. Nodes can be placed in advantageous positions, run off battery and solar recharged, and left as area repeaters (or routers in Meshtastic parlance) forming a mesh with other similarly advantageously placed nodes. We have this locally to some extent. It is very easy then to get into a position where you a reach those nodes, just don't expect it to work from your basement. Used correctly - and that probably means used as originally proposed - it is certainly neat, potentially ubiquitous, even anonymous. I already have a use for it at 'work' where I need data comms across 3km with no line of sight and with little or no money available... For now, we're all playing and having fun or getting frustrated. The worry is people will give up and lack of coordination will make that worse. Of course, it's early days, the software is still being developed, the boards are hard to come by but that will change as stock moves. It's quite interesting to be in this now, relatively early on and as it develops further.

Continue reading...
M0RVB

Pi reduction

I've been rationalising hardware, in particular as the PoE HAT on the Pi running the GB7RVB packet mailbox was noticeably noisy and needs replacing. I had originally moved the packet mailbox off of my AMPRnet router Pi as I needed to install a VPN and the networking was becoming a bit too complex for my liking. In the end I had no use for the VPN, so GB7RVB has gone back, removing one Pi. Linbpq went across just fine - there is an apt for it (https://wiki.oarc.uk/packet:linbpq-apt-installation) so installation is easy. Just install and copy the config across and the files under /opt/oarc/bpq (there are neater ways but this sledgehammer method works). With the node running I could access via the web interface as expected, but then the axudp route disappeared. Then I realised that our broadband router had a NAT rule for the UDP port needed for axudp and that was still pushing it to the now switched off Pi. And I'm sure I've forgotten this same thing before! So now I have a note as a reminder, assuming I bother to check the note... Now having removed one Pi with a noisy fan the NTP server Pi is also whining. Grumble.

Continue reading...