Programming and using a Yaesu FT70D with a Hotspot

NOTE: In this video I had issues staying connected to the HRCC link. After making this video, I found the following information which will correct the issues I was having:

"YAESU YSF HRCC LINK USERS:
Update hotspot (Get latest hostfiles)
Restart
Re-Connect to US HRCC LINK

YSF Reflector was migrated today. "

For Pi-Star users, just go into your pistar dashboard and go to the "update" tab. The pistar will update after about 10 minutes and you will no longer have a disconnect issue.

In this video I discuss connecting to a hotspot with the FT70D and a few issues/quirks you'll run into.

John Kruk from Yaesu made a statement regarding Hotspots vs WiresX: The statement is below, but I found the statement while browsing the pistar forums at https://forum.pistar.uk/viewtopic.php?t=1096:

"Time to clear up some confusion that has been popping up on some (Anti) Yaesu System Fusion sites. This is in regards to YSF and FCS reflectors.

The first one and the biggest one is that YSF and FCS reflectors are not owned, maintained, designed, or monitored by Yaesu in any way, shape, or form. Yaesu System Fusion (C4FM) is an open protocol and people have made these types of servers or reflectors for Yaesu System Fusion voice protocol.

Some have crossed these FCS and YSF reflectors over to the WiRES-X network but they are NOT, and I stress NOT, a direct connection to the WiRES-X network. The only thing that can be directly connected to the WiRES-X network is a HRI-200.

These devices have caused some audio issues especially when doing a crossmode set-up (one digital voice mode to C4FM). This can create audio issues or issues in where people are not heard but the callsign appears. This is NOT a WiRES-X issue but usually a crossmode issue with the device.

Remember that these devices that give you access to these reflectors are not true Yaesu System Fusion (C4FM) transmitters as they do NOT have a DP-ID. Therefore, you need to be careful if you choose to block a node or room because of the traffic or issues created by these bridges. EXAMPLE: If you have a crossover from a device using an FCS or YSF reflector to a WiRES-X node the node ID will be shown across the room. Therefore, if you block that node because of issues you take out everything with that node. Be it the users with Yaesu System Fusion radios going into the node directly or the devices carrying the FCS or YSF reflector traffic.

WiRES-X nodes or rooms use actual numbers as the address to the room. Therefore, when you attempt to save a room into a WiRES-X memory on a radio they will save. If you attempt to save an FCS or YSF reflector it WILL NOT work. EXAMPLE: Yaesu nodes start with a 1xxxx or a 3xxxx number and rooms start with a 2xxxx or a 4xxxx number. So if you want to store say room 21001 into a WiRES-X memeory slot you can enter 21001 or the room name. YSF reflectors do not have a number associated with them and FCS numbers do not work. Even with FCS the server 00x and reflector xx equal a five digital number the number would always stat with a 0 (like 00xxx). The radio knows that 0 is not a valid number and will not save it. It might until the radio powers off but then it will be gone.

This is just to clear up questions about FCS and YSF that users have had recently. This is not a post about saying which one is better than the other. WiRES-X operation is very different then FCS and YSF operation. Thank you for reading this and I hope that this answers peoples questions"

Видео Programming and using a Yaesu FT70D with a Hotspot канала HAM RADIO DUDE