ICOM IC7300 USB driver

Discussion in 'OS: Mac OS' started by W3ATV, May 13, 2016.

ad: L-HROutlet
ad: l-rl
ad: L-MFJ
ad: Left-3
ad: l-BCInc
ad: Subscribe
ad: Left-2
  1. W3ATV

    W3ATV XML Subscriber QRZ Page

    Is there a Mac USB driver for the 7300? I can not get my rig control working in FLdigi. I have it decoding, but thats it. No transmit, no communication with the rig. In the pull down menus I do not see USB as a way to communicate with the rig for rig control.

  2. W3ATV

    W3ATV XML Subscriber QRZ Page

    I found it- but for anyone who needs it, it is here: http://www.ftdichip.com/Drivers/VCP.htm

    I love having FLdigi work with one cable- no CT-17, no external Signal Link modem, etc. One cable does it all!!!!
  3. K3DCW

    K3DCW QRZ Lifetime Member #212 Volunteer Moderator Platinum Subscriber Life Member QRZ Page

    Interesting that they went away from the SILabs chipset that they've used in previous models.
  4. W3ATV

    W3ATV XML Subscriber QRZ Page

    K6LPM likes this.
  5. K3DCW

    K3DCW QRZ Lifetime Member #212 Volunteer Moderator Platinum Subscriber Life Member QRZ Page

  6. W3ATV

    W3ATV XML Subscriber QRZ Page

    Dave- I am loving this 7300 so far. Had it up and running on digi modes in 30 minutes. Most of that was spent finding the USB driver. You walked me through my Yaesu CAT and serial converter problems a while back for which I am grateful. Getting the Icom going was a cake walk in comparison.

    K3DCW likes this.
  7. AI6VN

    AI6VN Ham Member QRZ Page

    It is my experience that the USB audio levels are controlled by the speaker volume control. As a result, in order to run WSJT-X in WSPR mode I have to turn up the volume on the 7300 and hear all the rx noise from the 7300 speaker isn wspr-rx mode and the tx tones in my pc headphones when in wspr-tx mode. Have I missed something about how to configure the 7300 or wsjt-x? thanks
  8. AE9AM

    AE9AM Ham Member QRZ Page

    That definitely should not be the case. When you're interfacing the 7300 to a PC using the single USB cable for both rig control and audio in/out, the volume levels are controlled by menu settings in the 7300 and are indepentent of the AF gain and the speaker on the radio.

    So for example using WSJT-X for JT65, I can turn up the AF knob on the radio to monitor the band on the internal 7300 speaker, then turn it back down to zero to silence the radio, and none of that has any efffect on the level that WSJT-X sees coming in over USB.

    But when I first set things up, I had similar behavior to what you describe, where the AF Gain seemed to control the level WSJT-X saw. If I had the volume up, then it could decode things just fine, but if I turned it down then it stopped seeing signals. This was quite puzzling until I dropped something on the floor and got a big spike on the waterfall, and realized that WSJT-X was NOT listening over the USB interface at all, but was actually listening to the 7300's speaker through the microphone on my laptop (and still managing to decode messages just fine!) I had failed to select the proper audio interface in WSJT-X.

    The 7300 has seperately configurable normal and digital versions of each mode (USB and USB-D etc.) and for each one you specify whether it uses the Mic/Aux or USB for audio in/out. You can use either for operating digital. The -D version is convenient if you also operate voice modes, but note that the -D version defaults to a 500Hz narrow CW filter I believe, which is the opposite of what you want for most modern digital modes, but of course you can change the filter settings to wide once you're in that mode.

    There are a bunch of YouTube videos for configuring the 7300 for USB-based digital modes. If you watch a couple of those you'll probably figure out what you have wrong.

    One other thing that's confusing is that the the 7300 has a traditional serial CI-V REMOTE port on the back which has its own serial chip limited to 19,200 baud, as well as a separte internal serial adapter connected to the USB interface that can run at up to 115 Kbaud. There's a menu setting (Ports, CI-V, CI-V USB Port) that controls whether these two ports are tied together internally, and if they are then the USB to serial CI-V link is limited to the 19,200 baud maximum speed of the external CI-V port. You normally want this set to "Unlink from [REMOTE]" which will let you set the CI-V USB Baud Rate all the way up to 115,200 which (when set to the same thing on the PC side in your rig control app) will give you much smoother real-time response for rig control back and forth as it's six times faster.
  9. AI6VN

    AI6VN Ham Member QRZ Page

    I cannot get WSJT-X 1.7 to reliably use the USB audio output. I am running WSJT-X 1.7.0 on a MacBook Pro Sierra OSX connected via a USB cable to a ICOM-7300. I have set WSJT-X to use USB audio input and output and the ICOM-7300 to do the same. WSJT-X reliably controls the ICOM- RX/TX functions and alway receives audio, but after several tx cycles WSJT-X starts to output the tx audio through the analog headphone output jack on the Mac. WSJT-X preferences always shows USB audio output, and if I quit WSJT-X and start it, the tx audio resumes, sometimes for hours of tx cycles before WSJT-X stop sending USB audio and starts to send audio to the analog headphone jack.

    UPDATE: I seem to have fixed the problem by follow instructions on another forum to use the Mac's MIDI configuration utility to set the USB audio output to 44.1 khz rather than the default 48 khz.
    AE9AM likes this.
  10. AI6VN

    AI6VN Ham Member QRZ Page

    I spoke too soon ;=(
    The output audio is no longer switching from USB to headphone jack, but after about 90 minutes WSJT-X stopped triggering my ICOM to transmit. I can bring up WSJT's preferences dialog and the "Test CAT " button goes green and the "Test PTT" goes red and the ICOM goes into transmit.

    Now I notice that the WSJT log window ends with a ---- Transmitting WSPR ---- at that 90 minute time and there has been no WSPR rx or tx activity since then. So it appears that WSPR is locked up in receiving the same band over and over again but logging nothing. The waterfall window is static, but the main window shows the current time and the project bar increments from left to right over and over again at the same frequency.

    Is there a WSJT log file which might give clues to the cause of this lockup behavior?

Share This Page