+ AA6YQ comments below

That’s not the same on a 7300. You don’t need an external circuit. I just set my 7300 up on MMTTY last week. Just needed the USB port and the EXTFSK64 DLL. Plus the right settings in the rig.

+ MMTTY can do that because it's a single application that is performing both transceiver control and RTTY FSK generation.

+ Unlike the IC-7100, IC-7610, IC-7851, IC-9100 - which create two virtual COM ports -- the IC-7300 creates only one virtual COM port. If Commander is using this virtual COM port for transceiver control, WinWarbler cannot use it for RTTY FSK generation, thereby requiring an external FSK circuit like those described in the "FSK Connection" section of

<>

73,

Dave, AA6YQ

+ AA6YQ comments below

That is only the case if you use an eternal CI-V interface
for CAT *or* use a third arty "port splitter" to split the
RTS/DTR (PTT/FSK) and TxD/RxD lines (CI-V) to separate port
numbers.

Windows will not allow two programs (e.g., WinWarbler/ExtFSK
and Commander) to access the same serial port at the same
time.

Note: If you use FSK on the 7300, you can not use CW as the
7300 allows only two of the three (PTT, CW, FSK) signals.

+ When using in IC-7300, WinWarbler and Commander can be configured to generate CW from text, with CW timing controlled by the transceiver; quality-wise, this is far superior to having WinWarbler wiggle DTR or RTS on the 7300's virtual COM port to generate CW, as the latter relies on Windows for timing; for example, moving your mouse can produce perceptible changes to CW timing. See item #5 in

<>

73,

Dave, AA6YQ

+ AA6YQ comments below

against Gremlins in radio shack, I've found this on the internet:



It would be interesting to know what do you think about this gadget.

+ My understanding is that this device was developed to provide a private CI-V bus for the PW-1 amplifier, the need for which is described by Larry K8UT here:

<>

+ DXLab users with a PW-1 have no need of this device, as Commander's Secondary CAT port can be configured to provide the required private CI-V bus.

<>

73,

Dave, AA6YQ

+ AA6YQ comments below

Now that I have WSJT-X directly directly connected to SpotCollector and it is working.

I want my Band Activity Calls (while monitoring 6 meter MSK144 with WSJT-X) to automatically be uploaded to N6WS. ...or is that already happening?

+ As described in

<>

+ SpotCollector can accept incoming spots from up to 4 DX Clusters, a local packet cluster, the DX Summit web cluster, and one or more local instances of WSJT-X. The incoming spots are used to maintain a Database with one entry for each active DX station operating in a particular mode near a particular frequency. The information in this database can be viewed in multiple ways: in a table that you can filter and sort, on DXView's world map (with independent filtering), on Commander's Bandspread, in a display optimized to reveal propagation patterns, on a Spectrum-Waterfall window (when controlling a recent Icom transceiver, or on a Flex Signature Panadapter.

+ SpotCollector does not provide a way to automatically route the information it collects to a DX Cluster. You can of course generate outgoing spots, either directly, via DXKeeper, or via Winwarbler.

I see those spots appear from me if I manually force them from a logged qso (Right Click on Log Entry > Spot ...etc)

+Correct.

I just saw a decode from of N8CJK EN84 working K0TPP. I have not seen a new spot created in SpotCollector.
Same for N5SYV calling CQ

I am now working N5WYV. I finished / logged the QSO in WSJT-X and it populated DXKeeper, and auto-uploaded to LoTW.

I see nothing on SpotCollector for either my monitored decodes, nor my actual contacts.

Am I missing a setting, and if so, where and what?

( I have read the sections on how to set things up for X and SpotCollector, but I see no reference to Auto-Uploading calls decoded in X)

Strangely enough, all my FT8 monitoring on HF fills my SpotCollector screen. Obviously, I'm missing something. Maybe a sub-mode setting?

+ I have tested SpotCollector with WSJT-X decoding FT4 and FT8 stations, but not MSK-144. So that I can see what's going on, please do the following:

0. download the new version of SpotCollector that I will send you via email; this version has additional diagnostics for monitoring incoming WSJT-X messages

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

2. place WSJT-X in FT8 mode, and wait until several callsigns operating in FT8 and decoded by WSJT-X have appeared in SpotCollector's Main window

3. place WSJT-X in MSK144 mode, and wait until WSJT-X has decoded several MSK144 stations.

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

5. attach the errorlog.txt file from your SpotCollector folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ

against Gremlins in radio shack, I've found this on the internet:



It would be interesting to know what do you think about this gadget.

73 de
Salvatore (I4FYV)

That is only the case if you use an eternal CI-V interface
for CAT *or* use a third arty "port splitter" to split the
RTS/DTR (PTT/FSK) and TxD/RxD lines (CI-V) to separate port
numbers.

Windows will not allow two programs (e.g., WinWarbler/ExtFSK
and Commander) to access the same serial port at the same
time.

Note: If you use FSK on the 7300, you can not use CW as the
7300 allows only two of the three (PTT, CW, FSK) signals.

73,

... Joe, W4TV

That’s not the same on a 7300. You don’t need an external circuit. I just set my 7300 up on MMTTY last week. Just needed the USB port and the EXTFSK64 DLL. Plus the right settings in the rig.

Tom NY4I


Principal Solutions Architect
Better Software Solutions, Inc.
727-437-2771

开云体育

+ AA6YQ comments below

Using IC-7300, DXLab and windows 10.

I am having a problem sending RTTY. When I click on start in Winwarbler I get a solid tone.

+ That means you don't have WinWarbler properly configured for RTTY FSK. Follow the instructions here:

<>

73,

Dave, AA6YQ

Using IC-7300, DXLab and windows 10.

I am having a problem sending RTTY. When I click on start in Winwarbler I get a solid tone.
I also have a stand alone version of MMTTY which works perfectly.?
I am at a loss on how to correct this problem so any fixes I can try will be appreciated.

73,
Art WB4MNK

+ AA6YQ comments below

I only have one radio at a time power up when I am using them.
The issue I have is I am using ARMY MARS software M110A, that controls transmit thru CAT control in the software.
For some reason I an having trouble getting the software to key the data transmit

+ I can't help you with that. Perhaps someone else here can.

73,

Dave, AA6YQ

I only have one radio at a time power up when I am using them.
The issue I have is I am using ARMY MARS software M110A, that controls transmit thru CAT control in the software.
For some reason I an having trouble getting the software to key the data transmit

+ AA6YQ comment below

The 7300 and the 7200 are connected by USB (Silicon Labs CP210x USB to URART bridge- Icom ver 1.30 USB driver) cable.
Both the 7200 and the 7300 have both the "CI-V Transceive" disabled.
The Flex 5000A connects to the computer thru a firewire cable.
The Flex, and the IC-7300 work just great with Commander , I just having issues with the IC-7200.
The main issue I have with the IC-7200 is being able to transmit both voice and data. it seems to be an either or situation

+ With the two Icom transceiver's connected to your PC "point-to-point" with USB cables, "CI-V transceive" disabled in each Icom radio, and a 200 ms interrogation interval, there should be no CI-V bus collisions unless one of the radios is reporting a collision at startup.

+ Click the red "CI-V" indicator to extinguish it; how soon before it re-appears?

+ Power down your 7200, and restart Commander with your 7300 running; does the "CI-V" indicator illuminate?

+ Power down your 7300, and restart Commander with your 7200 running; does the "CI-V" indicator illuminate?

+ I don't understand what "The main issue I have with the IC-7200 is being able to transmit both voice and data. it seems to be an either or situation" means; please elaborate.

73,

Dave, AA6YQ

Also the interval is set to 200 for all three radios

The 7300 and the 7200 are connected by USB (Silicon Labs CP210x USB to URART bridge- Icom ver 1.30 USB driver) cable.
Both the 7200 and the 7300 have both the "CI-V Transceive" disabled.
The Flex 5000A connects to the computer thru a firewire cable.
The Flex, and the IC-7300 work just great with Commander , I just having issues with the IC-7200.
The main issue I have with the IC-7200 is being able to transmit both voice and data. it seems to be an either or situation

Tom W7TJM

+ AA6YQ comments below

Hello, I have two Icoms-a IC-7300 and a IC-7200, plus a Flex 5000A connected to DL LABS Commander ver 14.4.0
I see a red CI-V indicator on the very bottom of the Commander box.
Please advise a way of troubleshooting this issue.

+ As the explanatory popup indicates when you let the mouse cursor hover over that red "CI-V" indicator, the indicator appears when the primary radio reports that is has detected a CI-V bus collision.

+ How are your three radios connected to your PC?

+ In the Radio panel on the Configuration window's General tab, to what is the Interrogation interval set.

+ Is your IC-7200's "CI-V Transceive" menu item enabled or disabled?

+ Is your IC-7300's "CI-V Transceive" menu item enabled or disabled?

+ Commander will tolerate CI-V bus collisions if you enable its "Verify CI-V command acceptance" option on the in the Radio panel on the Configuration window's General tab, but it would be best to first understand why collisions are occurring before deciding to enable this option.

73,

Dave, AA6YQ

Hello, I have two Icoms-a IC-7300 and a IC-7200, plus a Flex 5000A connected to DL LABS Commander ver 14.4.0
I see a red CI-V indicator on the very bottom of the Commander box.
Please advise a way of troubleshooting this issue.

Tom W7TJM

开云体育