Great presentation, thank you! One of my major interests, even at work, is focused on how do I make things work together. I also like the fact that Node.Red is cross platform and not tying anyone into a specific OS like, just Windows or just Linux.

@Chris VE3NRT that link is the one I had in the original article, but offers 0.3.9 which is not the latest work that has been completed. The code for 0.3.10 in .py formats and not the .exe can be found at https://github.com/wb8tyw/D-Rats/tree/python3_tyw So for those of you with programming knowledge, it would be intriguing to look at the code.

For those interested in the latest version of D-RATS software, this is the latest known version I can find. Just download, unzip and run d-rats.exe For further info on how to configure the software, take a look at their groups.io at https://groups.io/g/d-rats/files?p=updated,,,20,2,0,0

Nicely done. I have tried to use an Arrow dual band antenna, but holding it by hand over your head and trying to point accurately is not easy when you are also trying to concentrate on the radio transmissions. I like the fact this system takes the weight so you can focus better. The angle marking is also a nice addition.

I agree that 1200 bps is SLLOOOWWWWW and if a message has to go via a digipeater can be 2-3x slower than that because every packet has to be repeated and then extra overhead to manage that too with timeouts. The issue becomes how do you build out a network to run AREDN MESH across a wide area like York Region?

I am currently running a Winlink RMS on 144.930MHz in lower Richmond Hill which seems to be working well on 1200bps packet. And yes, I know they can all co-exist on the same frequency! The intent is to use 144.930MHz at the EOC in Newmarket once we can get back into the systems after COVID.

I would be interested, but what cost to get started?

I too am trying the paclink-unix and following your instructions too.

Chris, ARES never gets activated unless required by the York Region Emergency Management Office. We never self-activate! There are two scenarios when we might get activated: 1) Break down in police/fire/ambulance communication systems - however, these days it is highly reliable, but it is a technology and we know technology breaks. 2) To handle extra communications with third-party organizations such as Red Cross or St John Ambulance, again only when primary communications have failed, such as telco capabilities. As York Region EMO have commented in the past, if they have to call ARES into an Emergency, then it must already be VERY bad. With COVID-19, there is potential for a call-out because Rogers, Bell and others may start to fail and if staff are ill, then they may have a lack of resources such as field engineers to keep systems running. On the other hand, ARES would never be pulled into a situation where we may become ill ourselves. It's all a fine balance. IMS-100 is the first course to complete. If you have completed IMS-100 please send your IMS-100 certificate to emcomm@yrarc.org Following this is the IMS-200 course which we are hoping will be put on during April, though COVID-19 might itself stop this moving forward. Watch this space. Mike VA3MCT EC York Region ARES

Many thanks to Bruce (VE3BV) who fixed our IRLP Node. The issue was a bad DTMF decoder chip on the IRLP board. It is now back on the air through VE3YRA (145.350 MHz, -0.6MHz offset, 103.5 PL). regards, Brian VE3IBW

I have ID-800 mobiles and ID-80H handhelds, but all club owned.

VE3WOO is a fusion repeater that is also connected via WIRES-X (i.e. internet enabled) and has the same owner name and address as VE3NUS. VE3WOO shows as Toronto, but that might be a generic naming, rather than a specific grid square/gps location. Node: 51073 Fusion ROOM: 61073 Callsign: VE3WOO/R Location: Toronto, Ontario, Canada VE3WOO-RPT 442.3375MHz+5.000MH Toronto, Ontario, Canada VE3WOO/R 51073 Digital DG-ID:00-00 Mike

As for your comment on "end up hogging the repeater so nobody else can use it or worse breaking the thing". Just use it as you see fit. We are all new users on this system and ALL are in learning mode about what works and what doesn't work. Again, general Ham Radio protocols of use apply, gentlemanly conduct and listen before you transmit! There is very low probability of you breaking anything. As we learn more, we will put some guidelines in place, but not so sure we need anything at this time.

You have identified one problem we have with the current setup. When someone has connected a room where they are discussing the price of tomatoes, that is not relevant to York Region users and they do not leave time between transmissions, it is difficult to break in and change the room. I will look into how this can be changed. I know I can do it directly from the system I have in the basement, but I am not monitoring 24*7. I am trying to enable some other folks in the repeater group to have access to the software in my basement that runs the WIRES-X gateway.

James, There is a timeout based on inactivity. So if you are connected to CQ-CANADA-VE1AO, which although it has lots of attendees, they do not say much, so there is no "voice" traffic, then yes, it will default back after 15 minutes to our local room VE3YRC-ROOM. If another local user wants to use the repeater, they can do so with the usual protocols of ham radio. If there is nothing on that frequency/channel/room, then go ahead, pick up the mic and make your call. If the repeater is still connected to CQ-CANADA-VE1AO, then they will be heard by all in that room. If the repeater has moved back to the default VE3YRC-ROOM, then only local repeater users and anyone else in the VE3YRC-ROOM would hear. You are not "preventing" other users from using the repeater when connected to another room, but their calls may go further than they expect. The easiest thing to do is to use the WIRES-X button on your radio and let it "connect" to the repeater. That way you can see what ROOM the repeater is connected to, the local VE3YRC-ROOM or another from around the world. Also, if there is no voice communication going on on the repeater and it happens to be connected to a room in RUSSIA or TEXAS-NEXUS for example, a local user is able to change it to whatever room they desire, though again, it would be prudent to make a call out to see if anyone is currently using the repeater or wait a short period of time to listen for other users before making such a change. Hope that helps, Mike

@Ron Gibson VE3CGR You should be able to tell from this website https://www.yaesu.com/jp/en/wires-x/id/active_room.php but VE3YRC does not seem to be showing up, so I do not know if they only update hourly or something. From what I see in WIRES-X software, we should be up and running. Mike

WIRES-X has been on and off today as I had pipework for a furnace installed in the basement. I have been looking into a remote viewer to see status, but the Yaesu software breaks when I put this mode into place. Hopefully it will get corrected soon. WIRES-X is back on air now.

OK, so APRS data just gets sent along with all of the other packets of data that are already being sent with voice content, hence no other specific frequency required. Understood, thanks for clarification. Neat!

Brian, I'll watch the video and maybe my question will be answered there, but what is the difference between Analog APRS and Digital APRS, since APRS is all digital anyway? Are they actually transmitted on the same frequency? 144.390MHz? Mike

RJ, I sent some files to your ylab address. Not Chirp, but .xls and .pdf. We are currently determining a best standard for sending this info out.