delara news Delaware Amateur Radio Association, Delaware OH   VOL 37 NUMBER 11

Ohio Section News

Scott Yonaly, N8SY Ohio Section Manager A change in the Ohio cabinet There are a couple of changes to the Cabinet that I want to let you all know about.. Scott Hixon, KC8ITN as decided to retire from the post of ASM – Scouting. His job and family responsibilities have changed quite a bit from the past and he felt that this would be in the best interest for the Section. Scott has agreed to continue his post as E.C. in Pickaway County, so he does plan on continuing to be active in the Section still. Anthony Luscre, K8ZT who was our ASM – Education representative has agreed to accept the post as Section Youth Coordinator on our Cabinet. The SYC position actually encompasses both Education and Scouting, so this is really a great move for Anthony as he will be directly involved with both programs under this one roof now. I do want to thank Scott for his many years as our Scouting representative and to congratulate Anthony on his new position as our very first Section Youth Coordinator!! I also want to thank all of you for the great job you all have been doing in getting articles in the Ohio Section Journal. For the last 6 months we have set records for the largest Ohio Section Journals EVER!!!! These past 2 months we have seen OSJ’s that are 41 pages of extremely good and valuable information. There is NO other monthly Section newsletter bigger or better than ours. This is only possible because of YOU and I thank each and every one of you for that. Let’s keep this record going. The folks not only in the Ohio Section, but all around the country are eager to hear from US!!!  Gang- this is how it’s done! I want to share a message with all of you that is a great learning tool for everyone  to share and learn by. Hello Group: Earlier today, Mike KD8ZLB noticed a post on social media stating that the city's phone lines were out of service. Residents were instructed to contact the city departments via email if needed. Mike immediately notified Bryan KC8EGV and John KD8MMY of the situation. As one of the liaisons to Wyoming, John contacted me to discuss potential further actions from HamCo ARES. We decided to reach out to members in the area as best as we could via email to assess the situation and potential need of our services. Although we have a formal MOU with Wyoming, we have not been introduced to the new fire chief, so we did not want to assume he knew what ARES is and what our capabilities are. So, we did not want to call him directly on his cell phone. We took a passive response to not 'get in the way'. NOTE: An introduction is being arranged. Based on the information found, we concluded that the residents in the area and 911 dispatch did not seem to be affected. PSAP is handled by HCCC for Wyoming. I was busy with work tasks, so John took the lead on the response. John proceeded with the following actions: • Emailed members in the Wyoming area for information gathering. • Gathered response availability from a few ARES members in case an immediate response would be needed. A larger response would be organized if rquested by Wyoming. • Logged into WebEOC for any indication of a larger incident in the area. • Obtained outage data from Cincy Bell Telephone. • Emailed a SetRep to Bryan with updates on the above items. John was able to eventually make contact with Wyoming PD. He was given the following: • All department heads had responded to the city building for coordination. • It appeared that the city phone lines were starting to come back online. • As far any anyone knew, cell lines and resident landlines were not affected. • No comms services were needed from ARES. John contacted Bryan with the updates and John give a stand down to everyone contacted earlier. APPROX. TIMELINE 09:55 - Wyoming Posted on Twitter 10:14 - Mike Text to Bryan & John 10:17 - John Call to Bryan to establish a plan 10:58 - John SetRep via Email 11:10 - John Call to Bryan with final SitRep 11:15 - Stand Down Given I want to thank Mike KD8ZLB for being aware and notifying myself and John KD8MMY of the incident in Wyoming today. I also want to thank John KD8MMY for taking the lead to determine if we could be of service to the City of Wyoming. He also kept me informed on the situation and planned what our response would be if needed. If the City of Wyoming would have requested our services, I feel we were prepared to assist as asked. This is why we do this. - Bryan Hoffman, KC8EGV Hamilton County EC The New OpenSPOT-2 It seems that this little critter will do just about everything that a dedicated digital person would want. This is something that we’ve all been waiting for. A unit that is easy to setup and operate, and it doesn’t break the bank. The openSPOT2 has a lot of features for a standalone unit Compatible digital radio protocols and networks* • DMR (BrandMeister, DMRplus, XLX) • D-STAR (DCS, REF/DPlus, XRF/DExtra, XLX) • System Fusion/C4FM (FCS, YSFReflector) • NXDN (NXDNReflector) • P25 (P25Reflector) • POCSAG (DAPNET) Supports cross modem modes (example: talk with your C4FM radio on DMR, and with your DMR radio on System Fusion networks). * NXDNReflector, POCSAG and P25 support will be added in a later firmware upgrade (soon). More supported networks and features will be available with new firmware releases. And now they have finally released the pricing.. It’s only 199,00 € Or approximately. $226.33 US dollars. No, I’m not selling these, nor am I being paid to advertise them. I’m only letting you know of some of this new units features for no other purpose than to let you all know that it is another way of getting on the radio if you live in an antenna restricted area, or you don’t have any repeaters close to you. Want more information?? Here’s a link to their website. We still need help finding some good E.C.’s in a number of counties… Please, help Stan and I out by really considering becoming an E.C.! Now I know that this may be too much for you to handle right now? I have a proposal for you. How’s about becoming a person that can just input events and approve hours into the new ARES Connect system. You do not have to be an E.C. for this, although we’d prefer that they would be willing to step up to that challenge someday. If we could just have some folks willing to do the inputting of events and approve hours for now I’d be eternally grateful. Counties where this is only a RACES program in place. Please.. this is a great opportunity for you as that we will not interfere with any of the programs that you already have in place. In fact, it will help you in getting those valuable volunteer hours recorded as they have never been before!!! How’s about it? Could you spend a little time just working with ARES Connect? Let me know!!! Again, you do not have to be E.C.’s to do this work in ARES Connect. We can give you admin privileges so that you can help with logging events into the system, keeping track of hours or even making sure that certificates get to Jim or I for placement into the statewide database. Here are the counties that we really need help with. Allen, Fulton, Henry, Mercer, Paulding, Putnam, Logan, Adams, Brown, Clermont, Carroll, Athens, Jackson, Meigs, Perry, Vinton, Belmont, Harrison, Monroe. This is a great opportunity for anyone that has a little time and is willing to volunteer. I do want you to start encouraging your ARES membership to also get registered in the ARES Connect system. Here’s a quick link for them. https://arrl.vol\ 

Section training Coordinator

Jim Yoder, W8ERW ARES Training Update I expect anytime now we will see our next NIMS certificate submission which will take us to number 750 and our Section Manager will be awarding another ARES safety vest to that lucky person. Overall, there are nearly 1,000 ARES members who have submitted training documents to the database, well over half of our ARES official membership number. I think that is amazing and the numbers continue to increase almost daily. We have approximately 7,200 total courses logged as well. Fantastic this is indeed. Our Ohio Hams are the greatest. I have recently had several questions come up regarding how we determine the level designations that are represented on the report that I generate regularly. There appears to be some confusion and I’d like to clarify the process this month. I have also made some revisions to the report and I hope the changes will make the information more understandable. However, before I continue, let me announce our 750th ARES member to submit his certificates for NIMS training, W8TRW Allen Mytyk from Toledo, Lucas County. Allen will be receiving a nice ARES safety vest awarded by our Section Manager, Scott Yonally N8SY. Congratulations Allen! ARES participation consists of three levels, 1, 2 and 3. Most Amateurs would enter at level 1 and progress as necessary or desired to level 2 and level 3. Level 1 members have not completed the initial NIMS training, ICS-100, ICS- 200, ICS-700 and ICS-800. Once these core NIMS courses have been completed and the completion certificates are logged into the ARES Training database, you are considered level 2. Level 3 requires the submission of your completion certificates for ICS-300 and ICS- 400. Beyond level 3 are several ICS and ARRL courses that are desired for more advanced participation in ARES activities. The ARRL courses in Emergency Communications, EC-001 and EC-16 are two of those. Both courses are required to attain this designation. ICS-706 and ICS-802 comprise another designation and again both courses are required. Served agencies may require these courses. Additionally, there are some other courses which may be required by our served agencies. These are COMM L, COMM T, COMM N and AUX COMM. ARES members serving in a management role may be required to have these courses in addition to the advanced level courses. Many of our routine ARES activities do not normally require level designations to participate. Providing communications support for a local public service event such as a 10K or bicycle race are examples. NIMS certification at level 2 and at level 3 would be required to actively deploy with ARES to a disaster situation that would utilize the NIMS structure to manage. The more advanced and supplemental training could be required by a served agency as they deem necessary and our member(s) would be acting in a management role with them. ARES encourages all members to complete NIMS training, ICS-100, ICS 200, ICS-700 and ICS-800. These are considered the core courses and would normally be required to serve with your local EMA. Some of the confusion that has surfaced recently is with the supplemental courses, especially, ICS-706 & ICS802 and EC-001 & EC-016. In order to attain these designations, both courses in each are required. All ARES members are encouraged to progress to whatever level they desire by taking the required courses and submitting their certificates to the ARES Training database. These are all exceptional courses designed to give you the skills to operate in an environment where they are necessary for success in responding to and managing to a disaster situation. As always, your questions are welcome. Please feel free to contact me or any of our Ohio Section officials with your concerns. We are here to assist you and help in any way that we can. Now for some funs stuff. We have just completed our SET exercise, Operation Black Swan 2018. From all that I am hearing, we were a great success this year with many county ARES organizations participating. Seneca County was quite active throughout the SET period this year as Jeff Potteiger WB8REI directed our activities. Jeff focused on providing a real-life exercise including unexpected events, changes, failures and many of the happenings that might occur in a real situation. We were able to utilize repeaters and simplex, Hamshack Hotline, the AREDN MESH Network, NTS Traffic, CW and SSB. I may have missed something. All in all it was an interesting and productive exercise drawing a wide variety of our capabilities into the action and offering some very realistic failures of normal routine operation. Thank you, Jeff and the entire Seneca County ARES team, for a great SET exercise this year.

From the Section Traffic Manager

David Maynard, WA3EZN – STM ACCURACY - ACCURACY If you have been a traffic handler for very long I am sure you have been told to copy the radiogram “exactly” as it is being sent. As this hold true for 99 percent of the time it is not true 100 percent of the time. I am sure you have heard if not received or sent a radiogram where there is an obvious mistake in the text or the header. For instance, an October traffic report where the header date is August being sent. I see this mistake at least once a month. But there is more, and I am not immune to making a mistake either. Here is one of my recent mistakes. 450 R KB8XXX 16 XXX OH OCT 8 KD8TTE BT YOUR TEST WELFARE NUMBERS 2090 TEST WELFARE 2091 TEST WELFRE 2092 UNDELIVERBLE DUE TO INCOMPLETE ADDRESS BT KD8TTE <<<< wrong signature??? A similar mistake in the radiogram below from the RRI link shows how easy it is to ruin the meaning of a radiogram by a one-word mistake. ----- Forwarded Message ----- From: "James Wades [TFC-OPS]" <TFC-> To:; Sent: Friday, October 12, 2018 7:59 AM Subject: [TFC-OPS] "Unglued" Hello Everyone: Yesterday, I originated several messages, all of which contained the word "unguarded." A few hours later, I received an e-mail from an addressee requesting clarification of my "cryptic" message. It turns out that "unguarded" became "unglued" somewhere in the process. Of course, we all make mistakes. However, this incident points to something that should be quite obvious. In the case of plain text traffic, it is wise to review the text carefully before acknowledging receipt of the message. If the text does not make sense, one should seek fills or request clarification. For example "eighth region Winlink function unguarded" makes sense, whereas "eighth region Winlink function unglued" likely does not. There is good news. The message was originated at 2230Z and delivered  sometime before 0230Z, so the speed of service for a routine radiogram is excellent. In this respect, good customer service was provided. Unfortunately, the garble did undermine the quality of that service. I suspect this error has a bit to do with the heavy reliance on "bulk traffic," with its predictable texts and "cookie-cutter" formulas. When a unique radiogram is injected into the system, many are unprepared to handle significant variations in content. This case, and others like it, point to the need for more individual, personalized messages to exercise the system. 73, JW (WB8SIW) I agree with Jim that we have become complacent with the handling of bulk traffic from stations like NK9X, N1IQI, KI0JO, DL4FN and others. When we get something different we seem to be in a hurry to pass traffic and close the net. Even with the bulk traffic form these stations we want to go reading speed and can easily override a mistake or a change in the text while we rush. I have notice this with traffic coming from the eighth region and other nets to the OSSBN net. Sometimes the text read does not match the text intended as it is coming through the digital network without errors. I have been sending out some radiograms with the handling instructions HXC. I am concerned with the fact that more than a few of the radiograms are being delivered and no delivery (HXC) report is coming back to me. I want to remind everyone that the handling instructions are there for a purpose. I would hope that all traffic handlers pay attention to the handling instruction and act appropriately. Here is a list of instructions and their meaning: HXA – (Followed by a number Collect landline delivery authorized by addressee within ….. miles (If no number, authorizations in unlimited) HXB – (Followed by a number) Cancel message if not delivered within …. Hours of filing time, service originating station HXC – Report date and time of delivery (TOD) to originating station HXD – Report to originating station the identity of stations from which received, plus date and time. Report identity of station to which relayed, plus date and time, or if delivered report date, time and method of delivery HXE – Delivering station get reply from addressee, originate message back. HXF - (Followed by a number) Hold delivery until ….. date. HXG – Delivery by mail or landline toll call not required. If toll or other expense involved, cancel message and service originating station. The easiest way to report back to the originating station is to use ARL FORTY SEVEN and ARL SIXTY SEVEN and adding the letters ARL before you check number in the header .as ARL FORTY SEVEN : Reference your message number …. to …. delivered on ….. at ….. UTC. Example: (ARL FORTY SEVEN 1234 WA3EZN SEPT 1 0012) ARL SIXTY SEVEN : Your message number …..undelivered because of ….. Please Advise. Example: (ARL SIXTY SEVEN 1234 phone disconnected) In the above example it is a good idea to also include the phone number so the originating station knows you were calling the number that he had in his radiogram. Dyslexia happens you know. A point brought up by WB8SIQ on the OSSBN net is the use of handling instruction HXB. The proper procedure for HXB (followed by number) is cancel delivery if not delivered within so many hours of the filing time in the header and service originating station. If this handling instruction is use you must have a time filed in the header of the radiogram. Otherwise the destination station will not know what to do. Another point well worth mentioning is the use of Q signals on a phone net. Q signals are special ARRL signals for use in amateur CW nets only. They are not meant for use on phone nets or casual amateur conversation. Do not use QN signals on phone nets. Say what you mean in words. Here are I few that I have heard said in error. I am QRU – simply say you have no traffic I QSL your message – simply say Rodger