C4FM/WiRES-X Net Log n’ Blog

C4FM/WiRES-X Net Log n’ Blog

     For tonight’s net (2-13-19), we covered the announcements from the Orlando Hamcation by Yaesu and the firmware and software releases of today, February 13, 2019. We now have a lot of work in front of us!      
For information about the new Portable Digital Node software, see our “System Fusion” page in the front page menu.

Scroll to the bottom of the page for the latest net results—–

     Net number twenty-one is now in the books. Tonight’s tutorial was skipped since we had plenty to talk about otherwise.

     The tech/trivia question was ….non-existent! Current average net length: 52 minutes. Average number of nodes connected during the net: about 10. Average number of stations checking into the net: about 8.

     One thing we have learned is that we can disrupt another node, as long as that node is not transmitting at the time of our attempted connection. That is, if you as Node ‘A’ are connected to Node ‘B’, but are not transmitting, Node ‘C’ can come along and ‘capture’ you, or connect you to Node C rather than Node B. When Node C ‘let’s go of you’, you’ll go back to Node B. I imagine that depends on the software settings you have entered. What apparently does NOT happen is that Node C gets connected to Node B by virtue of Node A already being connected to Node B.

     It’s always important to understand the difference between a node and a room though. Nodes are physical and rooms are virtual, more or less. If Node A is transmitting to Node B, or even to Room B, then you as Node C will get a busy indication. Once again, that may be dependent upon some of the software settings. It’s mind-boggling to contemplate all the potential scenarios that could occur. The digital world is nothing but a series of switches and routings and like a steel ball falling through a Pachinko machine, the signal could go anywhere.

     Lately I’ve been fooling with the Group Monitor mode, trying to determine its usefulness (at least from my perspective). So far I have found only limited use for it. I suppose if you are traveling and want to know if others are in the area it might be helpful. The program uses some unknown parameter for indicating who is ‘in range’ and who is not. You can add them to a list if you like and if both of you are running GPS, then you can get an indication of what direction and distance they are…..provided you are using a radio that will display that information. 

I started with an FTM-3200 on a base antenna, then went about my daily business. I did pick up its beacon with an FTM-400. A relative signal strength was displayed. Being that the 3200 has no GPS, I could not get direction and distance info. The 3200 displayed my FTM-400 beacon quite differently. The 400’s callsign scrolls across the screen of the 3200. I also threw an FT-1 and FT-2 into the mix. They are both capable of GPS operation, but without GPS on the 3200, no position info can be displayed….at either end. 

For local use, and by that I mean ‘within the repeater’s coverage area’, I find little use for GM. Why not pick up the microphone and put your callsign out there? The repeater is going to cover a greater area than a mobile of handheld will. I shall continue to experiment and report my findings. 

    It is now possible to go an estimated 60 miles from Atlanta, driving in a northeasterly direction, and be within reach of one of the participating nodes or repeaters. Not that there would not be dropouts here and there, but there are five nodes or repeaters along that route that take part in the net. We hope to continue to add access points wherever we can…not just along that route. In fact, there is a participating node in the Cedartown, Georgia area. 

Our goal remains to provide service to C4FM and WiRES-X device owners so that they may learn more about those devices and enjoy them fully. We expect to learn ourselves as there is always something new to pick up on and since System Fusion is developing all the time.

QUESTION: Why is the number of ‘nodes’ different than the number of ‘stations’ in the chart below? The nodes that show up in the Connect ID Window of the WiRES-X software for Room 40383 is the source of the counted nodes. Any node that comes into the room during the net gets counted here. The number of stations that actually answer the call for check-ins is what gets counted for ‘Stations’ listing. A node may come online but the person connecting a node to our net may not wish to check in. That is fine. They are welcome to listen if they so desire. The number of ‘stations’ could be higher, OR lower than the number of ‘nodes’ in the list because stations can also come in via RF as well as WiRES-X. So you see, there are variables that cause the numbers to differ. 

NET #    DATE       NODES    STATIONS   TIME     NC       TMA    NA   SA


21. Feb. 13, 2019      16                9              44      K1KC     1079   228   174

20. Feb. 06, 2019      19               10             49      K1KC     1035   212   165

19. Jan. 30, 2019       22               19             95      K1KC      986    193   155

18. Jan. 23, 2019       23               16             98      K1KC       891   171   136

17. Jan. 16, 2019       10                 8              51      K1KC      793    148   120

16. Jan. 09, 2019       8                    5              65      K1KC      742   138   112

15. Jan. 02, 2019       6                    6              49      K1KC      677   130   107

14. Dec. 26, 2018       7                    5              30      K1KC      628   124   101

13. Dec. 19, 2018       5                    4               26      K1KC     598   117    96

12   Dec. 12, 2018       9                    5              31      K1KC     572   112    92

11   Dec. 05, 2018      11                    8             52      K1KC     541   103    87

10   Nov. 28, 2018      7                     5              39      K1KC     489   92      79

9     Nov. 21, 2018       6                    6              29      K1KC     450    85      74

8     Nov. 14, 2018      17                  11              60      K1KC     421   79      68

7      Nov. 7, 2018        11                   9              53       K1KC     361   62      57

6      Oct. 31, 2018        8                    6              54       K1KC     308    51     48

5      Oct 24, 2018         7                    6              52       K1KC     254    43     42

4      Oct. 17, 2018        9                    8              55       K1KC     202    36     36

3      Oct. 10, 2018        9                    8              50       K1KC     147    27     28

2       Oct. 3, 2018         9                   11              43       K1KC     97     18     20

1      Sep. 26, 2018        9                    9              54       K1KC      54       9       9