Common Problems

Common Problems

Here are some issues that people run into when trying to use America’s Kansas City Wide digital network:

I can’t get checked in to a net. The host never hears me.

Kansas City Wide has grown far beyond what Yaesu envisioned when they designed the networking protocol. On top of Wires-X we have multiple bridges to other protocols such as YSF, DStar, DMR. Here’s the key point: all of these nodes/rooms/bridges run asynchronously, with no knowledge of what other network facilities might be doing at any specific point in time. All of these connections funnel down to a single point, and only the first to arrive gets heard in the room. 

When you have 300-500+ nodes trying to check into a popular net, there are going to be a LOT of people who get blocked by the one person who arrived at the room first during any particular exchange. There is no indication that a ‘double’ has occurred, and anyone who arrives a millisecond late has their transmission discarded.

I have personally been unable to check into an hour-long net because someone always beat me to the punch.

I have no advice other than to be persistent.

Please try throwing your call out there during quiet times between nets. It’s very likely that someone will hear you and respond.

I’m not being heard in KCWide.

Most often this is caused because you have an invalid callsign programmed into your Yaesu radio. The callsign box in the radio menu MUST start with your callsign, with no spaces, dashes, asterisks, etc. It’s fine if you want to add your name, rig, etc. to the end. Here’s what we see a lot:

  1. FT-991A (the default that 991s arrive with)
  2. ADJ (No idea where this comes from. Possibly from units repaired at Yaesu)
  3. YAESU
  4. NOCALLSIGN (These get immediately blocked from the room)
  5. W 0 A B C (Spaces between characters)
  6. KF9 ABC (Space in the middle)
  7. ND-KX4ABC (Anything in front of the callsign)

If this is NOT your issue, drop an email to feedback@kansascitywide.com with your callsign, your 5-character radio ID, and the EXACT UTC time you tried to connect. We’ll do our best to find out what the problem is.

I can’t connect my node to KCWide, but I can connect to other rooms.

This happens way more often that you’d think. Your Wires-X program has a node REJECT list. It can be found under VIEW -> Node-info(N), and looks like this:

Just click on AMERICA-KC-WIDE then hit the Delete button.

This happens when you are trying to add a node to your bookmark list in the Wires-X program. If you right-click on a node, you will get a pull-down menu:

If your mouse slips a little too far down, you click the Node Reject button, and the room gets added to your reject list without any notification from the Wires-X program. This can happen to any room you might be looking at. Just follow the instructions above to remove the entry from your reject list.

If this is NOT your issue, drop an email to feedback@kansascitywide.com with your callsign, your 5-character radio ID and/or node ID, and the EXACT UTC time you tried to connect. We’ll do our best to find out what the problem is.

CreateCaptureBuffer failed: Error code 80004005

Caused when Windows Security is preventing access to the audio input/microphone.

Click on START -> SETTINGS -> PRIVACY -> MICROPHONE

Find ‘Allow access to the microphone on this device’, and turn it on

Scroll down and find ‘Allow desktop apps to access your microphone’ and turn it on