+ From what URL can I download documentation for this radio's CAT instruction set?

There is no CAT instruction set info in any of the documentation at:
<>


73,

... Joe, W4TV


On 2025-05-24 4:34 PM, Dave AA6YQ wrote:

+ AA6YQ comments below

We are pleased to introduce the new FTX-1F and FTX-1Optima"


"FTX-1Field is a Portable 6W or 10W* HF/50MHz/VHF/UHF Multimode
Transceiver.?(*10w with 13.8VDC supply.)"



"FTX-1Optima is the FTX-1Field with a 100W on HF/6m & 50W on VHF/UHF
clip-on Linear Amplifier with built in ATU for HF/6M."

+ From what URL can I download documentation for this radio's CAT instruction set?
73,
Dave, AA6YQ

+ AA6YQ comments below

will dxlab support the new ftx-1?

+ I can't find any information about the FTX-1 on Yaesu's web site:



+ My understanding is that FTX-1 is a receiver that covers 30kHz through 174MHz and from 400MHz through 470MHz including SWL, FM
broadcast, and Air-band.

+ Since it has no ability to transmit, the answer to your question is "no", unless its CAT documentation - when available - shows
that it's CAT instruction set is a proper subset of that of a supported Yaesu transceiver.

73,

Dave, AA6YQ

+ AA6YQ comments below

My transceiver is an IC7300. I am on FT8 with WSJT. A CW DX spot comes out, and I double-click in spot collector. Commander changes to the correct frequency, mode, and filter bandwidth. (It seem sometimes I have to stop monitoring on WSJT, and sometimes not, or it will grab me back to the FT8 frequency, but that's not what this is about). When I return to FT8 by re-enabling the monitor in WSJT, I see that the bandwidth is 2.7 kHz. Before that, it was 3+ kHz on the waterfall. I then change the Filters Group setting back to Normal (or Wide), and the bandwith goes back to the 3+ kHz. But now, the Group bandwidth display periodic bounces from normal to narrow, about 1 to 2 times per second. I can change the filter to wide, same bouncing. I can change it to narrow (where it was on CW immediately prior to coming back to FT8), and there is no bounce. There is some kind of polling going on and the state it keeps trying is Narrow. I don't hear any bandwidth changes on the radio while this is going on, and I don't see any change in the WSJT spectrum.

+ So that I can see what's going on, please do the following:

1. on the Configuration window's General tab, check the "Log debugging info" box

2. terminate Commander

3. start Commander

4. replicate the misbehavior you describe above

5. on the Configuration window's General tab, uncheck the "Log debugging info" box

6. attach the errorlog.txt file from your Commander folder to an email message, and send that message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ

+ AA6YQ comments below

When I post to the Cluster (using SpotCollector) the audio alarm readout says "Grid Square FO93" included in the announcement.

First of all:

1. F093 is wrong, and no matter what Call is Spotted, the same Grid Square is announced.
2. Even in Spots announced by other stations, the Grid Square FO93 is announced.

What is the source of this and how can I turn it off?

+ That's the result of a regression. I've sent you a new version of SpotCollector with this defect corrected; please let me know how it goes.

73,

Dave, AA6YQ

will dxlab support the new ftx-1?

thanks


Reggie
k6xr

+ AA6YQ comments below.

You'd have to account for the fact that some parks are in multiple counties, states, and even grids.

+ The downloadable POTA park definition file specifies the following for each POTA reference number:

- Park Name, e.g. "Acadia National Park"

- Active

- DXCC entity code, e.g. 291 (continental US)

- DXCC entity abbreviation and primary administrative subdivision, e.g. US-ME

- latitude & longitude

- grid square

+ Double-clicking on a Spot Database Entry with POTA reference NO-1631 - Reinaya Nature Reserve - specifies NO-IN,NO-MR, meaning that it lies in two Norwegian primary subdivisions, could display a small window asking the user to choose the correct primary subdivision or leave it blank.

+ Multiple grid squares could be handled in the same way.

73,

Dave, AA6YQ

You'd have to account for the fact that some parks are in multiple counties, states, and even grids.

Earl / KD5XB

Sent from Proton Mail Android

开云体育

+ AA6YQ comments below

Been thinking about this a lot today as I have been chasing POTA on 20m FT8. My overall goal is to work ATNO's first and then whoever else is activating second (who may be activating multiples and no way to tell if the additional parks are ATNO's). How I am doing it now is using GridTracker as it takes spots from pota.app and indicates them on the Call Roster. I also use Chrome with POTAPlus to inform me if they are ATNO's. I would much rather just use SpotCollector because everything would be on one application to include the logging interface between WSJT-X and DXKeeper.

This is what I would wish SpotCollector would do - let me know which ones are ATNO's plus displaying the spots from pota.app as well as those from other sources - I use the IZ2LSC cluster that has a pre-filtered SOTA/POTA feed. When I work and log it, it already takes the POTA info and adds it to the user defined field in DXKeeper already, so I don't think that one needs to even mess with DXKeeper. You would download the CSV file from pota.app under My Stats of all of the unique parks you have credited to you. This database would be checked against the incoming spot data to see if it was an ATNO and then indicate it.

+ Having to download a CSV file to update your POTA status each time you work a new POTA park would frankly be a kludge. Were this to become widespread practice, whatever if serving that CSV file might become a bottleneck.

+ For NPOTA, DXKeeper's NPOTA progress report would generate an SQL query that could be invoked from SpotCollector to identify any active stations in unworked U.S. parks. That too was a kludge, but given NPOTA's one-year lifespan, it was a tolerable compromise.

73,

Dave, AA6YQ

+ AA6YQ comments below

I'll argue that when activators submit logs to LotW and don't create and use appropriate locations it may "hurt" grid or County hunters, and if in a different state or country, it may "hurt" WAS or DXCC hunters.

+ After completion of the proposed "step 3" in POTA/SOTA support, double-clicking a Spot Database Entry that specifies a POTA code would query the local POTA database (generated from ) for that park's U.S. State and Gridsquare. This would prevent the location misinformation caused by callbook location information being tied to a callsign.

73,

Dave, AA6YQ