WIRES-X Error Codes

These are codes which will be displayed by the WiRES-X software on a node PC.

This page will attempt to deal with error codes as displayed on the WiRES-X PC software interface. CAUTION: These entries are user-submitted and are not official in any way. Interpret and use them at your own risk. Submitted entries must be accompanied by the submitter’s callsign, operating system and other pertinent information.

_____________________________________________________________________________

Check the header in each section for location of each error message.

************************************************************************

ERROR MESSAGES IN THE STATUS BAR

Message: Transceiver not connect(ed)

Submitted by K1KC Date: August 19, 2019

Cause: The WiRES-X software is not reading the radio.

Solution: Since there is more than one cause, check these solutions: 1. Make sure the transceiver is in the WiRES-X mode. 2. Make sure the transceiver is an approved node radio. 3. Wait for the transceiver to power up and be recognized by the software. 4. Make sure the transceiver has power supplied and is turned on. 5. If the transceiver is a repeater, make sure the repeater is set to ‘RPTR+HRI Mode’.

———————————————

Message: “ON-AIR LOCK” state.

Submitted by: K1KC Date: December 7, 2019 OS: Windows 10 Home V. 1909

Cause: The ON-AIR LOCK button was pressed during operation.

Solution: Press the LOCK button again to unlock.

                                      ———————————————-

Message: Not found the Audio device for the WiRES-X use.

Submitted by: K1KC  Date: December 21, 2019  OS: Windows 10 Home Version 1909

Effect: No connection with the node radio was possible.

Cause: The PC did not load the audio drivers/devices for audio to pass between radio and computer.

Solution: (I’d like to say: ‘Strongly encourage Yaesu to adopt some other OS than Windows’). However, they have indicated that won’t be happening. Therefore, you must figure out how to do this. Until near the end of 2019, this was usually accomplished by a second re-booting of your Windows PC after an update. Now it has become more difficult.  Good luck.

************************************************************************

ERROR MESSAGES IN THE LOG BOX

Message: *_*_* Call to Rejected No.(node number), In Conf *_*_*

Submitted by K0HCV Date: August 21, 2019

Cause: (Not determined yet)

Solution: One solution offered by Yaesu was to go to the PC software, under FILES, select SET DEFAULT, then OKAY. This returns the WIRES-X software to its initial state and shuts the program down. You will have to reboot.


Message: One AMBE out

Submitted by K0HCV Date: August 14, 2019

Cause: This error is believed to be caused by a non-Yaesu device such as a hotspot on the network, but this has not been confirmed.

Solution: We believe that eliminating the use of non-Yaesu digital devices may cure this issue. This has not been confirmed.

                                         —————————-

Message: Error: Socket Communication Timeout at call (see additional response below)

Submitted (elsewhere) by G4OXY

Effect: No audio, intermittent traffic, timer would start running for reason

Cause: RFI on frequency

Solution: Increase squelch level setting

                                   —————————

Message: Digital transceiver error reset  code = 1120100

Submitted by: K1KC  Date:  October 4, 2019  OS: Windows 10

Effect: No WiRES-X operation

Cause: Power was removed from node radio

Solution: Restore power to node radio

                                   ——————————-

Message: Digital transceiver error reset  code = 1050100

Submitted by: K1KC  Date:  October 4, 2019  OS: Windows 10

Effect: No WiRES-X operation

Cause: Node radio was turned off or power was removed to node radio

Solution:  Restore power to node radio

                                    ———————————–

Message: * – * – * Cancelled call to analog node or Analog & Digital room * – * 

Submitted by: K1KC  Date: October 5, 2019  OS: Windows 10 Pro

Effect: PDN would not connect to room

Cause: PDN was in PDN mode and Room was in Mixed Mode

Solution: Change PDN to HRI mode from PDN mode

                                   ———————————-

Message: Error: Socket Communication Timeout

Submitted by: K1KC  Date:  October 6, 2019  OS: windows 10 Pro

Effect: Communications with previously connected node or room lost

Cause:  The previously connected node or room went offline

Solution:  (Depends on your desires) Manually re-connect to node or room if it comes back online and if you do not have ‘Return To Room’ enabled, or connect to another node or room

                                    ———————————–

Message:  Error: No answer from called PC  * Disconnected *

Submitted by: K1KC  Date:  October 6, 2019  OS:  Windows 10 Pro

Effect: Self-explanatory: the node you called did not answer

Cause:  The node you called was offline at the time

Solution:  Try again when node/room appears in the active list

                                       ———————————-

Message:  return to room (______) last (____) count

Submitted by: K1KC  Date:  October 6, 2019  OS: Windows 10 Pro

Effect: The WiRES-X PC software attempted a ‘return to room’ call

Cause:  Your software is set up to return to a specified room when able

Solution:  The software will attempt (up to 10 times) to contact the specified room. If unsuccessful, no more attempts will be made. You will see the results in the Log Box

                                           ——————————

Message:  Error: No Entry on ILS Server * Disconnected *

Submitted by: K1KC  Date: October 7, 2019  OS: Windows 10 Pro

Effect: No connection was made to the called node or room

Cause: The called node or room was not in the active nodes/rooms lists because it is offline, therefore the listserver cannot direct your request

Solution: Request connection to an online node/room or wait until the desired node/room comes online

                                         ——————————–

Message:  List server response time-out

Submitted by: K1KC  Date:  October 27, 2019  OS:  Windows 10 Pro

Effect:  No connection to the listserver was made

Cause:  The listserver was offline or there was no Internet connection

Solution:  Check your Internet connection or wait for listserver to come back online

                                         ——————————–

Message:  * – * – * Can not accept own call * – * – *

Submitted by:  K1KC  Date:  October 28, 2019  OS:  Windows 7

Effect:  No connection to any node was made

Cause:  The connection attempt was made to your own node, that is, the node tried to call itself

Solution:  Call a node or room other than the one the call is being placed from

                                        ———————————-

Message:  Error: Socket Communication Timeout at call

Submitted by: K1KC  Date:  October 28, 2019  OS: Windows 7

Effect:  Connection to node/room was dropped (if it was ever established)

Cause:  All necessary ports were not open. When the “Node control” port is open, but no others, the software on both ends may show a connection, however, no nodes will populate the Connect ID Window of the calling node with the single open port. The Connect ID Window of the called node/room will display the calling node name until the connection is dropped. No audio or other info is passed. The ‘apparent’ connection will cancel itself in approximately 40 seconds

Solution:  Make sure all ports are open or wait for self-cancellation

                                        ——————————

Message:  Digital Transceiver error reset.  code = 1030100

Submitted by: K1KC  Date: November 08, 2019  OS: Windows 10 Pro

Effect:  WiRES-X operation interrupted  

Cause:  This seems to be another case of an error code indicating loss of power to the node radio

Solution:  Maintain power to the node radio

                                        ——————————-

Message:  Transceiver TX Stop. Disconnect.

Submitted by:  K1KC  Date: November 08, 2019  OS:  Windows 10 Pro

Effect:  WiRES-X PC software lost connection to node radio

Cause: Probably caused by digital cable to node radio getting disconnected. This can also be caused by entered a change request of the USER ID while in WiRES-X.

Solution:  That ought to be self-evident!

                                        ——————————–

Message:  Create Capture Buffer Failure  code = 80004005

Submitted by: K1KC  Date: June 26, 2019  OS: Windows 10

Effect: W10 denied WiRES-X access to the microphone. In other words, local-to-Internet and Internet-to-local audio traffic would not pass.

Cause: Regular Windows Update

Solution: Instruct W10 to allow microphone access to the WiRES-X ‘app’. In some cases, simply rebooting the computer will re-establish the presence of the microphone input.

                                      ———————————–

Message: Digital transceiver error reset  code = 1040100

Submitted by: K1KC  Date: October 3, 2019  OS: Windows 7

Effect: WiRES-X operation was interrupted

Cause: Power was removed from transceiver 

Solution: Do not remove power from transceiver while in WiRES-X operation. When external PS is plugged in, WiRES-X operation will be interrupted even though a battery is installed.

                                     —————————————

Message: Digital transceiver error reset  code = 1050100

Submitted by: K1KC  Date: July 25, 2019  OS: Windows 10 Home 

Effect: Briefly locked WiRES-X and knocked FT-2D into PDN Standby mode from PDN Direct mode 

Cause: Switching between internal and external power supply for FT-2D

Solution: Do not change power supply while in operation or, be prepared to take FT-2D out of PDN Standby mode each time.

                                      ——————————————

Message:  Server Access Error: “A connection with the server could not be established”

Submitted by: K1KC  Date: November 14, 2019  OS: Windows 10 Pro

Effect: No lists were populated and therefore, no connections could be made. In this particular case, only PDN’s were affected.

Cause: The listserver was out of service for an unknown reason.

Solution: In this case, moving to an HRI-based node would solve the problem, but this may not always be the case. Otherwise, you will have to wait until the listserver comes back online.

                                          —————————————

Message: * – * – * Cancelled call in PDN standby * – * – *

Submitted by: K1KC  Date: November 20, 2019  OS: Windows 10-1903

Effect: Lists would not populate and no connections were possible in the PDN mode.

Cause: The node radio was in ‘PDN Standby’ mode.

Solution: Place node radio in ‘PDN active’ mode by correct method for that radio.

                                       —————————————-

Message: Digital transceiver error reset. code = 11A0100

Submitted by: K1KC  Date: November 20, 2019  OS: Windows 10-1903

Effect: WiRES-X lists did not populate

Cause: Connection to the node radio was lost, probably due to radio being powered off.

Solution: Re-power radio or do not interrupt power to node radio.

                                    ———————————————-

Message: ** End sound: Digital transceiver frame response time-out.

Submitted by: K1KC  Date: December 7, 2019  OS: Windows 10 Home V. 1909

Effect: Audio discontinued? 

Cause: Most likely because ON-AIR LOCK was engaged and audio stream was interrupted.

Solution: Disengage ON-AIR LOCK.

                                  ———————————————–

Message:  * * Connect message: Digital transceiver frame response time-out.

Submitted by: K1KC  Date: December 17, 2019  OS: Windows 10 Version 1909

Effect: The node disconnected from the room it was connected to.

Cause: Although the node appeared to be connected to a room, it likely was not. Attempts to transmit would light up the “Internet” button but no activity was shown in the connect ID Window from the node in question.

Solution: Re-boot WiRES-X PC software. Make sure the correct USB audio codecs are listed as audio input and output.

                            —————————————————-

Message: Server Access Error “The server name or address could not be resolved”.

Submitted by: K1KC  Date: December 18, 2019  OS: Windows 10 Version 1909?

Effect: WiRES-X did not connect to the listeserver.

Cause: The most likely cause is that you did not have an active Internet connect at the time WiRES-X booted and attempted to contact the listserver.

Solution: Make sure you have an active Internet connection before booting the WiRES-X PC software. Of course, you can always connect afterwards. 

************************************************************************

ERROR MESSAGES IN THE MIDDLE OF THE PAGE

Message: A small box with this: WiRES-X

????????

Submitted by K1KC Date: September 11, 2019

Cause: Indeterminate (It may have been caused by a keyboard entry it did not recognize)

Solution: The error resolved itself apparently.

————————————————

Message:  A medium-sized box with “Warning” in light grey in the upper left-hand corner with a yellow triangle with an exclamation point in it will appear. It will read as follows:

A connecting transceiver was changed from Repeater type to Simplex type. The WiRES-X software is rebooted in Simplex (Mobile transceiver) mode.

Submitted by: K1KC  Date: October 6, 2019  OS: Windows 10 Pro

Cause:  A repeater node was changed from Repeater + HRI to Repeater.

Solution:  This is simply a warning to let you know the status of the software has changed. If you wish to swap modes, you must turn off the repeater, hold the DISPLAY button down while turning the power back on until the display lights up, at which point you release the DISPLAY button. You will then be prompted to choose REPEATER + HRI or REPEATER. Choose REPEATER + HRI if you want to get out of Simplex (Mobile transceiver) mode.                       *  SEE NOTE BELOW *

                                ———————————————–

Message:  A medium-sized box (as noted above) will appear. It will read:

A connecting transceiver was changed from Simplex type to Repeater type. The WiRES-X software is rebooted in Repeater mode. 

Submitted by: K1KC  Date:  October 6, 2019  OS:  Windows 10 Pro

Cause:  A repeater node was changed from Repeater to Repeater + HRI. 

Solution:  Follow the instructions of the example above except choose REPEATER if you want to get out of Repeater + HRI mode. 

                                  * SEE NOTE BELOW *

NOTE: These actions simply link, or unlink a repeater from an HRI-200. The message warns you which mode has been selected. The linking or unlinking is not physical…it is virtual as the CT-174 (or whatever) cable may still be attached. The repeater cannot be used for WiRES-X operation in the REPEATER mode.

************************************************************************

ERRORS (not messages) IN THE USER MONITORING WINDOW:

    I have noticed a number of errors over the years in the User Monitoring Window, specifically where it says “DOWNLINK”. Some of those errors include: (callsign)SPOT, (callsign)E, (callsign)SB, (callsign)T, (callsign)SN-RPT and other errors which I will try to catalog. I did notice that certain errors occurred identically when a particular station transmitted. This is over WiRES-X of course.

WIRES-X Basics

WIRES (Wide-Coverage Internet Repeater Enhancement System) is an Internet communication system which expands the range of amateur radio communication. For WIRES-X operation, an amateur node station connecting to the Internet is used as an access point connecting your wireless communication to the Internet. Your station can communicate with other amateur stations all over the world using a node within your radios range.

The W7NEO (147.040/145.19/442.125), WB7ILL (443.80), and WF7S (146.80) repeaters are all the local machines within Umatilla & Klickitat counties that are currently linked to the WiresX system. The W7NEO machines (with the exception of 442.125), WB7ILL, and the KE7PUP Node (147.55) are all four parked in the same WiresX room (NE-OREGON). This effectively links them all together to provide a foot print covering roughly a 150 mile area within both NE Oregon and SE Washington. All of these machines allow world-wide contacts to be made through the WiresX system. In addition to this is the KB7PPM repeater located in Salem Oregon which for the moment, covers all of the immediate area of Salem. According to the owner (Paul, KB7PPM) there are plans to relocate the repeater at a later date to a higher location which should provide excellent coverage over the Willamette valley.

 FAQ’s:

“Will I have to buy a new radio?”
If you’re accessing the system via analog FM then no you won’t. But if you’re accessing a repeater that is operating in digital voice only (such as the W7NEO machine) then unfortunately you will need to have a radio that is C4FM capable. On the up side, the digital voice mode provides considerably more features, better voice fidelity, and ease of operation.

 “Can I turn the Wires-X System On/Off when I want to?”
~Yes! If you’re going through an analog repeater pressing your PTT (Push-To-Talk) and pressing  “*”  on your DTMF keypad will disconnect the Repeater from the Wires-X system (for about 20 seconds). Most local repeaters are configured to automatically return to their home room after they have been disconnected from the previous room (such as the W7NEO system). If you’re on a digital system (such as the W7NEO repeater) there is no need to press the PTT, just press and hold down the “*” button on your microphones DTMF pad for a couple of seconds, without depressing the PTT and the system will disconnect from the current room you are in. Again, most systems are configured to return to their “Home Room” by default (W7NEO returns to NE-OREGON).

“Who all can hear me?”
~You decide! When a user connects to a “room”, the room may be full of other users, or only a few. Some might be in the USA, others could be overseas! Keep reading for more on this.

 *The W7NEO repeater by default is parked in the NE-OREGON room (40289) when not in use.

“Is this like IRLP or Echolink?”
~Somewhat. With Wires-X, a node connects to a room, which might already be hosting other nodes. This feature is not available with IRLP or Echolink. Wires-X (a Yaesu system) allows “Rooms” that often host several other nodes, some of which might be repeaters or personal nodes, belonging to a single operator. Keep reading…

“Do I need to upgrade my license to use Wires-X?”
~No! A newly minted Technician class operator can access the system and still make contacts with other states, and countries. A license upgrade is NOT required to use Wires-X.

“What if I need the repeater for an emergency?”
~Easy, first disconnect the system from the WIRES-X system. Either way, your emergency traffic WILL be heard locally, and possible on other systems as well if the systems are still connected. Pressing your PTT, then “*” , will quickly disconnect, or hang-up on the system. NOTE, this can only be done (right now) in-between transmissions.

*Be aware that the W7NEO system is NOT affiliated with ARES or RACES or any other such organization.

Good Operating Practices while using the WIRES-X system

SIMPLY FOLLOW THESE 4 STEPS

1 Listen!

2 Listen!

3 Listen!

4 …..Ok, this step has several steps. Did you happen to notice steps 1-3? Yes! Listen, Listen, Listen! This is the best advice I can offer you. Please KNOW what you are doing BEFORE you do it. The more prepared you are, the more receptive other stations will be to engage in a QSO with you.

Typically most of the repeaters local within Umatilla, and surrounding Counties are connected to their own rooms. Their individual rooms will accept calls from outside stations as well. If you desire a different room, there are two ways to go about it depending if the repeater is digital, or analog voice (The W7NEO repeater system is digital).

For Digital, you’ll have to first connect to the WiresX system by pressing the DX button on your radio. Once connected you can either do a search, or choose from your favorites list for a room to navigate too. This can vary depending upon the individual radio. Once you’re finished with which ever room you’ve been using, you can either navigate to another room in the same manner, or press “*” on your DTMF mic (without keying the radio) and the repeater system will do the rest.

For a WiresX repeater operating in Analog FM mode, simply key your radio and send the DTMF character * into the repeater (Digital Operation is slightly different). Once you DISCONNECT (*) from a room, or whatever room the system is currently in, you will hear the repeater “talk back” to you with 4 rapid dits. This is a MORSE CODE “H” (for hangup) and is the indicator that you have just disconnected from a room. Within about 20 seconds, key into the repeater (with your PTT button) the # sign followed by the room number of your choice, and un-key your radio. Once again, the repeater will “talk back” to you and announce that it is connected to the room you requested. If you do not receive an announcement that you are connected, a series of 5 longs tones will be heard. This indicates that the room is either busy or is not accepting incoming connections. Once you receive the announcement that you are connected, PLEASE wait to transmit, to ensure that there is not already a QSO in progress.

There is a list of available rooms on the internet. From the internet simply look up the list of available rooms currently on the system. Click on this link to view the list of active rooms, and their room numbers. Remember the number of the room you would like to join. If you are accessing the system through one of the local analog repeaters you should know that some rooms do not want analog nodes to connect. Please pay attention to the comment section of the list, and respect those who ask that no analog repeaters (or RF linked repeaters) connect to their room.

The repeater may already be connected to a room and someone might already be in a conversation. So… Listen, Listen, Listen, to make sure the repeater is NOT in a room already, and that a QSO is not in progress. Better yet, after listening for a few moments, announce “is the repeater or Wires X in use”? Once you are confident that you are not interrupting, key the * symbol into the repeater. This is also know as “hang-up” or “Disconnect”, which will disconnect the repeater from any Wires-X room it’s in. The repeater will answer this with 4 rapid dits (Morse code “H” for hang-up), indicating it has disconnected if analog, or the word “Disconnected” on a digital connection.

 Now that you have your desired room, send the DTMF character #, PLUS the desired room number into the repeater using your PTT by pressing # followed by the 5 digit room number you desire. The repeater will either announce to you it has connected, or that the connection has failed, using a series of 5 rapid tones. This is true for digital operation as well, in addition to the search feature.

You have just connected to your very first room! Congratulations! VERY IMPORTANT – When entering a room, a QSO might already be in progress, so follow steps 1, 2 and 3 again. Better yet, follow them a second time. No one wants to be interrupted by someone barging into a room hollering their call sign. Once connected, either (1) Listen for other stations, (2) Respond to a calling station, or (3) Put out your call sign with the state (Washington or Oregon) that you are calling from, and simply ask for a Wires-X contact. You will likely get a response using this method. The room you are in likely has several repeaters in it, so make sure to follow the rules and be mindful that your transmission might be carried by dozens of repeaters systems in the USA and OVERSEAS.

Use your call sign Phonetically! Phonetics help immensely with stations being able to hear your call sign and respond to you!

When you are in a room and establish a contact, it is VERY IMPORTANT that you not “Tailgate” or “Quick-Key”. Once the other station is done transmitting, count to 3 or 4, and then begin your transmission. When you start your own transmission, please key up, wait a second or two, and THEN begin speaking. Remember, you are likely bringing up several (sometimes up to 150+!) connected repeaters, and they like a little time to start transmitting before you start talking. This allows the entire system to complete the previous step before picking up your transmission. Once you are done speaking, leave your mic keyed for about 1 second (dead air), and then UN-key. This encourages the station on the other end to do the same, keeping the system flowing smoothly. Please review these points to present yourself as well prepared station.

 When you are done with the Wires-X system, feel free to stay connected, in case another station wants to begin a QSO themselves. This is called “leaving the link up”, or “keeping it connected”. If you disconnect, (dropping the link), that’s fine as well. Just be sure to use your call sign when you key the repeater to connect (#) or disconnect (*).

  • On the W7NEO system those WiresX nodes not already locked in the NE-OREGON room are set to automatically disconnect and return to their home room (NE-OREGON) after 15 minutes.

ALWAYS IDENTIFY your transmission, when connecting or disconnecting the Wires-X link.

Here is something else to listen for. Once you disconnect from a room using the “*” key , any room, our node will “park” itself back in the Home room after about 15 – 20 seconds. If you do not key a new room into the system, our node will put itself back in our own room automatically. Feel free to test this out yourself. Disconnect from the current room, and then wait and listen. it will go back to its own room about 15 – 20 seconds later. Most all of the local repeaters are ALWAYS in a room, even if it isn’t their own room.

 Here are 2 perfectly acceptable examples…

 “This is K7ABC, accessing WIRES-X”, (assuming that you have already disconnected previously) and then without un-keying, key your desired DTMF characters into your radio. Now UN-KEY.

 The same is true when disconnecting…

 Key * into your radio, and then without un-keying your radio, announce “This is K7ABC, dropping (or) disconnecting WIRES-X“.  Now UN-KEY your own radio. You will hear the repeater return with the disconnect message.

September 2020 Pickle Barrel Review

The official newsletter of the Weston Mountain Digital Radio Association


Introduction

Greetings one and all to the first issue of the Pickle Barrel Review! The hope is to make this a regular monthly publication filled with the latest happenings not only of the W7NEO system, and the NE-OREGON room, but System Fusion and other Ham Radio related goings on as well. That said, we invite others to contribute with articles, or if your club or organization is having an event such as a tailgate, swap meet, VE testing, or whatever you can list it here as well. The only thing we ask is that your contribution be nonpolitical (unless it’s a government action that directly affects Ham Radio), respectful of others (no personal attacks), and relatively family friendly.  So, all that said, feel free to reach in the barrel, grab yourself a pickle, pull up a chair and have sit while we discuss the latest happenings in Ham Radio.


Repeater Updates

This month was a busy one for the W7NEO system. Work continued with the Cabbage Hill repeaters (444.975 & 146.88) trying to reduce, and or eliminate all together the noise interference that was trashing the 146.88 machine. Although we did install an inline A/C noise filter it appears that perhaps we may not have been the only ones falling victim to the noise. Although the filter was effective at reducing the noise, it seems to have simply stopped all on it’s own. Ironically it was after a conversation on the repeater in which a comment was made that we finally had the contact information for the FCC enforcement division and was planning on simply handing the issue over to them. I’m not saying that the originator of the noise was listening, but it is nice to not have to deal with the noise for the past few weeks. Fingers crossed it stays gone!

Another progress report pertains to the Weston Mountain repeaters. After (literally) years of talking the installation and raising of the tower is finally complete! For photos of this monumental undertaking check out the Photo Gallery section of the web site. Unfortunately, due to safety concerns we were unable to go the entire 45 feet and had to instead settle for 35 feet. Considering just how high the antennas “weren’t,” and how well they were still performing regardless, raising both the 147.040 and the 441.700 antennas up another 25 feet, in addition to upgrading both of the feedlines to 7/8” Heliax will most definitely result in some increased coverage for both machines. We might still add the missing 10 ft of tower at a later date depending upon availability of equipment such as a bucket truck, etc. So, either way I’m sure we’ll be doing the Happy Dance once we are able to verify the improved coverage.

Speaking of both Cabbage Hill and Weston Mountain, the analog side of each site will be undergoing a slight change. The 441.700 DR2X will be getting replaced with a Kenwood TKR-850, and for the 146.880 repeater on Cabbage Hill the DR1X will be getting replaced with a Kenwood TKR-750. These are both commercial grade repeaters, and if the reviews are correct both machines should provide excellent service for years to come. Although the DR2X is to be repurposed, one of the two DR1X (refurbished) will most likely be going up for sale. The other has already been spoken for.

Well that’s about it for our system status update for now. I wish I could tell you all that we have a date and will be installing the Chandler Butte repeater soon, but unfortunately this CONVID 19 fiasco that has a choke hold on everything is also delaying our installation of a new repeater on the system. Hopefully next month I’ll have some better news.

  • Lynn Wilson, K7LW

Disaster Preparedness

So last winter was abit on the crazy side with all the flooding, and what not, which makes most of us wonder if there have been any indications as to what we can expect for this winter? One of the things that has a significant effect on weather is the formation of either an El Nino, or an El Nina. Okay so what exactly is an El Nino, or El Nina? Well I’m glad you asked;

The El Niño/Southern Oscillation has a major influence on climate patterns in various parts of the world. This naturally occurring phenomenon involves fluctuating ocean temperatures in the central and eastern equatorial Pacific, coupled with changes in the atmosphere. Scientific progress on the understanding and modelling of this phenomenon has improved prediction skills to within a range of one to nine months in advance, giving society the opportunity to prepare for associated hazards such as heavy rains, floods and drought.

Organizations such as the World Meteorological Organization (WMO) track the potential formation of both the El Nino and El Nina’s in order to try and get a leg up on just what to expect for winter and summer weather patterns. Here is what their saying about this winter:

The El Niño-Southern Oscillation (ENSO) status in the tropical Pacific remains neutral, signifying that neither El Niño nor La Niña is currently occurring. However, since May both surface and sub-surface waters in the region have leaned to below average. The latest forecasts from the WMO Global Producing Centers of Long Range Forecasts indicate that tropical Pacific sea surface temperatures are likely to cool further, potentially reaching La Niña levels during September 2020. Given current conditions and model predictions, the chance of La Niña during September-November 2020 is estimated to be around 60%, with about a 40% chance for ENSO-neutral conditions to continue. Chances for La Niña decrease to 55% for the December-February 2020/2021 period. National Meteorological and Hydrological Services will closely monitor changes in the state of ENSO over the coming months and provide updated outlooks.

In summary:

  • The tropical Pacific has been an ENSO-neutral condition since July 2019. However, since May 2020, sea surface temperatures over the area have leaned slightly towards below-average.
  • Current observations show below-average surface and sub-surface water temperatures in the tropical Pacific, suggesting a likely tendency towards further decreases in sea surface temperature, possibly reaching La Niña thresholds during September 2020.
  • Model predictions and expert assessment indicate that the probability for La Niña development during September-November 2020 is about 60%, while that for ENSO-neutral conditions continuing is 40% and that for El Niño is near-zero. For the December-February 2020/2021 season, the probability for La Niña slightly drops to about 55%, while that for ENSO-neutral remains at 40% and that for El Niño marginally rises to 5%.
  • Sea surface temperatures in the east-central Pacific Ocean are most likely to be in the range of 0.3 to 1.3 degrees Celsius below average during September-November 2020, and 0.1 to 1.2 degrees below average during December-February 2020/2021.

The state of ENSO will continue to be carefully monitored by WMO Members and partners. More detailed interpretations of the implications for regional climate variability will be carried out routinely by the climate forecasting community over the coming months and will be made available through the National Meteorological and Hydrological Services.

So there you have it. As if COVID 19 wasn’t enough right?

As a disclaimer, the closest I’ve ever been to being a meteorologist is having maintained various weather monitoring sensors for the feds, owning my own home weather monitoring station, and watching the evening news for the local weather forecast. Other that that I’m just as confused as everyone else with this stuff.

*Information contained within this article was obtained primarily from The World Meteorological Organization (WMO).

  • Lynn Wilson, K7LW

Emergency Communications

  • The ARES folks (Both Oregon & Washington) are planning on having a SET (Simulated Emergency Test) exercise Saturday October 3rd from 0800 to 1400 +/-.
  • Please be aware that the WMDRA (W7NEO) does not participate in any of the above listed training, this information is made available to our users for informational purposes only.

Local Events

Thanks to COVID 19 most all of the normal yearly events such as Ham Fests, Swap Meets, etc. are pretty much all on hold until further notice. Hopefully once this plague has tired of ravaging the countryside we can get back to normal and go back to holding our cherished nerd conventions once again. But should you have any knowledge of events such as VE testing, or even something virtual locally going on let us know and we’ll get it in the Review for others.

Thanks!


VE Testing

  • Hermiston ARC – September 12, 2020 15:00 – 17:00 – Visit their web page at http://ai7ho.org/ for location, and other details.
  • Tri-Cities ARC – Sept 20, 2020 – Visit their web page at http://www.w7az.org/ for location, and other details.

W7NEO Analog Weston Mountain Repeater 441.700

The analog repeater on Weston Mountain is somewhat of an experimental repeater. The hope is for it to one day be connected via AllStar node.

If you aren’t familiar with AllStar, you can find more here.

LocationWeston Mountain (above Weston, OR)
Frequency441.700MHz
OffsetPositive 5MHz
PL Tone131.8Hz
LinkingNone (yet)
ModeFM Analog
Repeater Make/ModelYaesu DR-2
Elevation2950 ft
AntennaSuper Station Master
Antenna Height12 ft
Control OperatorsLynn Wilson (K7LW) PRIMARY
Eric Ramirez (K7ELJ)
Will Studer (N7WSY)

Coverage Map

W7NEO Analog Cabbage Hill Repeater 146.880

The “Cabbage Hill 88” repeater is our adopted site. It was previously part of another club and that club disbanded. It later went completely off the air due to equipment failure. We put in a new repeater and got it back on the air.

LocationCabbage Hill (I84 20 miles E of Pendleton near the weigh station)
Frequency146.880MHz
OffsetNegative 0.6MHz
PL Tone67Hz
LinkingNone
ModeFM
Repeater Make/ModelYaesu DR-1
Elevation3562 ft
AntennaSuper Station Master
Antenna Height34 ft
Control OperatorsLynn Wilson (K7LW) PRIMARY
Eric Ramirez (K7ELJ)
Will Studer (N7WSY)

Coverage Map

W7NEO-RPT 3 Digital Chandler Butte Repeater 147.320

Chandler as we so affectionately refer to it is our latest repeater project. We have already built of our equipment for the site, but haven’t had a chance to begin the physical work yet due to COVID-19. This site will fill in a few missing spots and increase our Washington coverage.

LocationChandler Butte (I82 between Prosser and Benton City)
Frequency147.320MHz
OffsetPositive 0.6MHz
PL ToneNone
LinkingWires-X to NE-Oregon Room (40289)
ModeC4FM/Yaesu Digital Fusion ONLY
Repeater Make/ModelYaesu DR-2
Elevation2040 ft
AntennaComscope DB224
Antenna HeightTBD
Control OperatorsWill Studer (N7WSY) PRIMARY
Lynn Wilson (K7LW)
Eric Ramirez (K7ELJ)

Coverage Map

W7NEO-RPT2 Digital Roosevelt Repeater 145.190

The Roosevelt repeater was the second repeater to go up. It was a group effort by members and users of the system. It increased the range of the W7NEO C4FM/Yaesu Fusion System significantly. There are plans/hopes of elevating the antenna higher on the 100ft tower it is located on.

LocationHillside above Roosevelt, WA
Frequency145.190MHz
OffsetNegative 0.6MHz
PL ToneNone
LinkingWires-X to NE-Oregon Room (40289)
ModeC4FM/Yaesu Digital Fusion ONLY
Repeater Make/ModelYaesu DR-2
Elevation1737 ft
AntennaCommander Tech 220-2N
Antenna Height40 ft
Control Operators:Eric Ramirez (K7ELJ) PRIMARY
Lynn Wilson (K7LW)
Will Studer (N7WSY)

Coverage Map

W7NEO-RPT1 Digital Weston Mountain Repeater 147.040

The Original Weston Mountain repeater was not only the first of the system, it is what began the group and gave it it’s name.

LocationWeston Mountain (above Weston, OR)
Frequency147.040MHz
OffsetPositive 0.6MHz
PL ToneNone
LinkingWires-X to NE-Oregon Room (40289)
ModeC4FM/Yaesu Digital Fusion ONLY
Repeater Make/ModelYaesu DR-2
Elevation2950 ft
AntennaComscope DB224
Antenna Height12 ft
Control OperatorsLynn Wilson (K7LW) PRIMARY
Eric Ramirez (K7ELJ)
Will Studer (N7WSY)

Coverage Map