Based on the Raspberry Pi 4B, ClearRPT V2 supports Hi and Lo Polarity for COS and PTT, includes an integrated cooling fan. It is currently available in the web store.
We currently have configuration and cables to support the Alinco and Yaesu Land Mobile radios. Kenwood radios are under investigation.
73 … Gerry.
There are a LOT of configuration options in ClearNode, and as folks discover other settings they want to be able to control, we dutifully add them to the configuration screens. If you chose to have your ClearNode delivered with minimal or no configuration, apart from your call sign, you really only need to configure 2 items to get your node up and running on AllStar – Node Number and Node Password. (“IAX Port (binport)” is important to, but in general you leave it at the default.)
As time goes by you will start tweaking the myriad other options – and why not ? … customize your node to suite your purpose and use case. Until … oh phooey … now NOTHING works !!! … and I’ve only got half an hour before the net starts !!! … and I’m filling in for Net Control !!!
You have a “get out of jail free” card to play – “Revert setup to ex-factory” – on the Node Details screen, tap on the Share menu icon in the top right corner.
When we get ready to ship your node to you, we configure the settings you sent to us – usually AllStar, EchoLink, WiFi and Radio frequency/CTCSS, along with some other settings specific to your account. We then test each of these modes to make sure your node is ready to get to work for you. The very last thing we do before shutting down your new node and packing it ready for shipping – we run a “Cleanup” script that makes sure any extraneous files are removed and then we generate a special file that reflects your node settings at that point in time: “nodeSetup.shipped”. That file will not change again unless Support re-runs the Cleanup script, which we rarely do.
Choosing this option will reset your nodes configuration to that known good configuration – which, in general, will get you out of your conundrum.
73 … Gerry.
(This is the fifth episode in a series of posts to help you discover all the functionality that you might not know exists in your ClearNode, ClearAlpha, ClearZero or ClearRPT. We’re going to publish an episode each Sunday evening – come back and join us each week !)
There are a surprising number of ClearNode customers who own multiple ClearNodes, ClearRPTs, ClearZeros and ClearAlphas. Often times those nodes co-exist on the same home or office network.
In general, nodes “find” each other by looking up the destination node in a reference database that each node downloads every so many minutes. That database links the node’s AllStar # with it’s public Wide Area Network (WAN) IP Address and the IAX Port it is using. When your local node goes to connect to another node it uses that information to start the connection to the destination node.
Now imagine you want to connect 2 nodes together that are on the same home network – they both have the same WAN IP Address – the process above is not going to work. (There are some tricks you can deploy in advanced routers like “pfsense”, but those are beyond the scope of this discussion.) It’s somewhat analogous to wanting to pass a letter to your family member in the same house – you wouldn’t take it to your local Post Office and have them deliver it.
AllStar provides a mechanism in its core configuration file “rpt.conf” to overcome this limitation – there is a stanza “[nodes]” at the end of the file where you can define local “pointers” to your local nodes that AllStar will not be able to resolve via the public node database that is periodically downloaded. Here is an example of such a stanza that is empty – i.e. it only refers to itself.
Pretty scary looking huh ?
The ClearNode mobile app can automate the generation of this information – since it knows the intimate details of your nodes – including what network they are on and what their individual local IP addresses are.
From the “Your Nodes” screen of the ClearNode mobile app, tap the “Share” menu in the top right corner and chose “Configure Private Nodes”.
This process happens pretty quickly, but it will reboot every node that it updates. Below is an example output file for Node 48063 that tells AllStar where it can find the other local nodes. In my case I have 2 locations each with their own WAN IP Addresses, so it only links the ones that local to each location.
And hey presto ! Now I can connect my 2 test nodes to my main neighborhood Simplex node.
Of course, this only works for your ClearNodes – if you have other nodes that are not connected to the ClearNode control system they won’t be included. Another good reason for getting a ClearNode software subscription for your SHARI and DINAH devices !
73 … Gerry.
(This is the fourth episode in a series of posts to help you discover all the functionality that you might not know exists in your ClearNode, ClearAlpha, ClearZero or ClearRPT. We’re going to publish an episode each Sunday evening – come back and join us each week !)
(This is the third episode in a series of posts to help you discover all the functionality that you might not know exists in your ClearNode, ClearAlpha, ClearZero or ClearRPT. We’re going to publish an episode each Sunday evening – come back and join us each week !)
Just a quick recap – Timed Events are control actions that your node can take automatically at specific times of the Month, Week, Day or Hour.
Select “Manage Timed Events” on the bottom of the Node Details screen
You can specify things like “Connect to DoDropIn every Tuesday at 7 pm” (for The Absolute Tech Net)
That’s pretty straight forward, in the time picker you are picking a specific day of the week, hour and minute, and of course the node you want to connect to.
Imagine you generally keep your node connected to a particular hub all day every day – with their permission of course. But the hub controllers have to reboot that hub once in a while, or maybe when you’re not in attendance some miscreant uses your node interfere with the hub, and the hub controllers have to disconnect your node to put a stop to it. Now when you come back to your node you see it disconnected – has been for hours – that’s a tad annoying. There is a solution – again get permission before from the hub controllers before you deploy this.
You can have your node re-connect every so many minutes per hour – the miscreants usually lose interest if they’ve been intercepted and disconnected, you can get back to business once they’ve gone elsewhere.
Create a Connect type Timed Event and select “Hourly” for the Repeat type. Now scroll the Minute Picker down to the bottom – note there are several odd looking entries with a star, a slash and a number.
The number represents how many minutes between each connect attempt, starting at the top of the hour. So “*/20” means the connection will be attempted at 0, 20 and 40 minutes past the top of the hour. I’m sure you can figure out the other alternates for yourself. Handy way to refresh that connection if get’s dropped. In this case the longest you’ll be disconnected will be 20 minutes. If it’s already connected, the connect attempt will be ignored.
There may be an action you want performed shortly after the node boots up – every time it boots up. There is a special case for the “Repeat” type. Create a new Timed Event and scroll the “Repeat” all the way to the bottom.
Note that the “Event time” picker has been locked out and now says “After reboot”. You can pick any Event Type for this kind of “After reboot” entry, although some probably won’t be appropriate – Custom Shell Commands are going to be particularly useful for some of you Linux savvy folks.
These “After reboot” events don’t fire immediately after reboot – they are delayed by 30 seconds – that’s so you can be sure the node has completed it’s startup process, so you’re command isn’t calling some service that hasn’t started up yet.
FYI … in ClearNode Timed Events are implemented as “cron jobs” – you can list them at the Linux CLI using the command “crontab -l”. We constructed this “separation of concerns” so that in the future, if we implement ClearNode on a platform other than Linux that doesn’t support “crontab”, we’d have the option to create something that has a familiar look and feel.
And one last time … if you implement automated connections to big hubs – be careful not to cross connect and ALWAYS seek permission before you do so.
73 … Gerry.
(This is the second episode in a series of posts to help you discover all the functionality that you might not know exists in your ClearNode, ClearAlpha, ClearZero or ClearRPT. We’re going to publish an episode each Sunday evening – come back and join us each week !)
Continuing on our mission to discover where the action is at, this week we are going to look at the Fleet Last Heard screen. Once again tap on the share menu icon top left of the Your Nodes screen.
Tap on “Fleet Last Heard” in the App Menu – initially you’ll get an empty list – this is a live view and nothing will be listed until a node in the fleet lifts off their HT’s PTT button.
Patience will reward you here – wait a while and the screen will start filling up with entries – the latest will be on the top.
Some things to note here. Only nodes that are connected to other nodes are listed here – if a node is disconnected but receiving on the node transceiver – it will not be listed. Also, “kerchunks” are ignored the transmission has be greater than zero seconds.
The 1st line of each entry tells you the call sign and node number that is receiving on its RF side and thus pushing audio onto the destination, i.e. nodes it’s linked to.
The 2nd line of each entry gives you the timestamp of the end of the transmission and the destination nodes the audio was sent to. If you tagged those destination nodes in your ADD CONNECTION screen, the tag will be displayed in favor of the standard AllStar Number. If the destination is a call sign – it’s likely to be an instance of DVSwitch mobile, Zoiper mobile or RepeaterPhone mobile.
73 … Gerry.
Our supply of Pi 4Bs has landed !
It’s going to be a busy few weeks – we’re expecting to get the first units out around Monday June 5th.
Given that the supply of Pi4s is healthy, but not unlimited, it seems fair to let people reserve their slot in the production cycle.
Version 2 of ClearRPT is nearing completion – still some testing to do and we need to finalize the case design. We’ll open Pre-Orders for ClearRPT in the coming weeks.
Onwards and upwards !
73 … Gerry.
(This is the first episode in a series of posts to help you discover all the functionality that you might not know exists in your ClearNode, ClearAlpha, ClearZero or ClearRPT. We’re going to publish an episode each Sunday evening – come back and join us each week !)
AllStar, EchoLink and the Digital Modes can be a bit overwhelming for the uninitiated … or should I say a little UNDERwhelming ! You’ve gone to all the trouble to understand how all this works, you’ve got it all configured … and now what … where do you go ?
Discovering where the “action is at” can be discouraging to the point some folks give up and go play with a different toy. That’s a shame because there is a whole lot of action out there – it’s a question of where and when !
We’ve deployed a couple tools in the ClearNode system to help you along the path of discovery. In this episode we are going to look at the live connection and disconnection activity monitor.
On the “Your Nodes” screen tap on the “Share” icon in the top left corner to bring up the App Menu
Tap on the “Fleet connection activity” option to bring up a screen that looks across the ClearNode fleet to see who’s connecting where.
You can see right away that there’s definitely some action on the Sierra Foothills system – lots of connects within the last 3 hrs. You can refine your search to a shorter or longer query period – 1 hr, 3 hrs, 24 hrs or 1 week – are you looking for what’s going on right now, or what goes on more generally ?
Let’s say you’re curious about the Sierra Foothills system – go ahead and tap on the Target Name – you will be offered the option to connect to that system right away. Your node “49855” will be connected to “51018” which is the actual node number for the Sierra Foothills system.
In this example the Target systems have real names “Sierra Foothills”, “The Talk Box”, etc. When you first start using your node these will be generic AllStar node numbers. As you get more familiar with your ClearNode you will start tagging those node numbers with names you can more easily recognize – we will cover that process in a later episode. Once you’ve tagged a node number that’s what will be presented here in favor of the generic node number.
Go ahead and give it a try !
73 … Gerry.
What’s new in this release ?
73 … Gerry.
ClearAlpha is a new product based on the Raspberry Pi 3A+
There are a lot of similarities with the ClearZero product which is no longer available. Compact form, very low power consumption – ClearAlpha is a great travel companion. No ethernet port nor available USB ports – so managing WiFi connections carefully is important.
Exact same software stack as the ClearNode – you can work AllStar, EchoLink, DMR, P25, YSF, FCS & NXDN.
A lower price ($295) makes this node a little more affordable.
73 … Gerry.