Hi
my driver seems similar but not the same - do you use a 32bit version?
<plist version="1.0">
<dict>
<key>CFBundleDevelopmentRegion</key>
<string>English</string>
<key>CFBundleExecutable</key>
<string>SiLabsUSBDriver64</string>
<key>CFBundleIdentifier</key>
<string>com.silabs.driver.CP210xVCPDriver64</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundleName</key>
<string>SiLabsUSBDriver64</string>
<key>CFBundlePackageType</key>
<string>KEXT</string>
<key>CFBundleSignature</key>
<string>????</string>
<key>CFBundleVersion</key>
<string>3.0.0d1</string>
<key>IOKitPersonalities</key>
Mac OS X version 10.11.6 (15G1217)
Icom IC7300 with latest firmware.
BTW, contrary to what I thought (and wrote) in a previous mail, the Audio
Devices are not listed alphabetically in my WSJT-X config dialog.
„Built-In Line Input“ is first, then „Built-In Digital Input“, and then the
other devices are listed, with „USB Audio CODEC“, and then the devices I
created in Audio-MIDI-Setup.
Same pattern for the Outputs.
Nonetheless, since I created this new Audio Device in the Audio-MIDI-Setup
application named with „AAAA“ at the beginning (and pointing to the USB Audio
CODEC device),
the problem did not occur any more.
Siggi
> Am 14.02.2017 um 20:29 schrieb Keith Laaks <wkla...@gmail.com>:
>
> Hi John,
>
> It must be my “SiLabsUSBDriver”.
>
> I just noticed that ‘sudo dmesg’ shows the following message whenever this
> issue occurs - always around the 4 or 5th time that WSJTX is switching from
> TX to RX:
>
> "005421.557360 IOUSBHostHIDDevice: IOUSBHostHIDDevice::interruptRetry:
> resetting device due to IO failures”
>
> I have uninstalled the SiLabs USB driver v 4.10.14. Then installed an earlier
> one from an older dmg I found on another machine: v4.10.13.
> That one does exactly the same.
>
> I don’t have any other issues with any other USB devices on the MacBook - so
> can only be the driver or radio itself.
>
> I will go back to SiLabs to see if they can provide advice here. Will also
> try log this with Yeasu.
>
> I would be interested to hear the exact setup that others also using the
> SiLabs driver (not sure if this is only limited to Yeasu) are using
> successfully:
> a) Exact version of MacOS (10.12.3 Beta (16D30a))
> b) Version of SiLabs driver (I have tried both 4.10.14 and 4.10.13.)
> c) Radio Firmware version: (On my FT-991, Main Firmware Version = 02-16)
>
> One can find the version of SiLabs driver by done a “more
> /Library/Extensions/SiLabsUSBDriver.kext/Contents/Info.plist” in a terminal:
> —
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
> "http://www.apple.com/DTDs/PropertyList-1.0.dtd";>
> <plist version="1.0">
> <dict>
> <key>BuildMachineOSBuild</key>
> <string>14A283o</string>
> <key>CFBundleDevelopmentRegion</key>
> <string>English</string>
> <key>CFBundleExecutable</key>
> <string>SiLabsUSBDriver</string>
> <key>CFBundleIdentifier</key>
> <string>com.silabs.driver.CP210xVCPDriver</string>
> <key>CFBundleInfoDictionaryVersion</key>
> <string>6.0</string>
> <key>CFBundleName</key>
> <string>SiLabsUSBDriver</string>
> <key>CFBundlePackageType</key>
> <string>KEXT</string>
> <key>CFBundleSignature</key>
> <string>????</string>
> <key>CFBundleVersion</key>
> <string>4.10.13</string>. <================== THE
> VERSION YOU ARE RUNNING =====
> <key>DTCompiler</key>
> <string>com.apple.compilers.llvm.clang.1_0</string>
> <key>DTPlatformBuild</key>
> <string>6A1052d</string>
> <key>DTPlatformVersion</key>
> <string>GM</string>
> <key>DTSDKBuild</key>
> <string>13F26</string>
> <key>DTSDKName</key>
> <string>macosx10.9</string>
> <key>DTXcode</key>
> <string>0610</string>
> <key>DTXcodeBuild</key>
> <string>6A1052d</string>
> <key>IOKitPersonalities</key>
> —
>
>
>
> Best Regards
>
> Keith
> Zs6tw
>
>
>>
>> ------------------------------
>>
>>
>> Message: 3
>> Date: Mon, 13 Feb 2017 20:32:34 +0000
>> From: John Nelson <j...@rmnjmn.co.uk>
>> Subject: Re: [wsjt-devel] Bug Report (WSJT-X v1.7.0 r7405 on Mac OS X)
>> (Keith Laaks)
>> To: WSJT software development <wsjt-devel@lists.sourceforge.net>
>> Message-ID: <ae663efb-ac0b-46b0-a587-daa14c39a...@rmnjmn.co.uk>
>> Content-Type: text/plain; charset=utf-8
>>
>> Hi Keith,
>>
>> I managed to get the waterfall to freeze but only by disconnecting the USB
>> cable (Audio) from the SignaLink box which wasn?t turned on anyway. WSJT-X
>> configuration still reported USB Audio Codec as did Sytem Preferences >
>> Sound. The USB cable was free - unterminated.
>>
>> WIth the USB cable terminated in the SignaLink box (not switched on) but no
>> audio from the rig (audio cable to the rig disconnected) the waterfall
>> continues to drop. So the waterfall does not depend on audio input.
>>
>> What seems to freeze the display are unexpected problems on USB such as a
>> disconnection when live.
>>
>> Can there be some problem with the USB on your Mac?
>>
>> ? John G4KLA
>>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Greetings
Siegfried Hanisch
mailto:siegfried.hani...@hanisch.com
http://www.hanisch.com
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
