I have also installed the following hamlib_settings.json file on my Mac per teh recommendation of the WSJT-X support team. I wonder if there are other settings tab need to be set. I am wondering if you or anyone else has been able to get these to work properly with the IC-7610.ĬI-V Address = 98h (Also tried address for 7300, 7600 andĬI-V USB/LAN – Remote Transceive Address = 00h I keep getting the following error message: Hamlib error: Communications bus error while getting current frequency I have been trying to get this combination of programs (WSJT-X, JT-Bridge and MacLoggerDX) to work with my IC-7610, but so far have been unable to get these to work. Click on the snapshot to see the full image. The next thing is getting WSJT-X and JT-Bridge connected and working together. There are snapshots on the next page. Just download JT-Bridge and drag it to the Applications folder.įor JT-Bridge to log your QSO’s into MacLoggerDX, in JT-Bridge you’ll need to click on File and then Open. JT-Bridge is very easy to install as you’ll see in the video below. In WSJT-X I am using the Icom 7300 for the rig and disabling the rig control in MacLoggerDX (See the video below). See my video on YouTube: WSJT-X Installation on iMac For Icom 7300 The next piece of the puzzle is WSJT-X and it requires a little work to install on a Mac. I made a clip on it and WSJT-X which you can see here: Icom 7300 MacLoggerDX Setup.Įverything on this page is using just the one USB cable. Getting MacLoggerDX (MLDX) installed is a breeze. Like I’ve said before, even if you are on a PC, this is something to look at and consider. It’s not unusual to make contacts on 15 Meters into South America too. I can always make contacts on 20 Meters during the day with 5 or 10 watts. I have grown to enjoy the weak signal modes even with bad propagation. MacLoggerDX, WSJT-X and JT-Bridge make a powerful and fun combination. Remember, Mac OS has no real concept of a “Com port” as in Windows, and Windows Com ports (and their configuration within N1MM and microHam Router) work exactly the same in a virtualized environment as in a native one.Two of my favorite modes theses days is JT65 and JT9. After each contest, I export the N1MM log via ADIF, and import it into my MacLoggerDX log to maintain completeness and consistency. (I will send you the developer’s email privately so you can ask.)Įxactly what I do. (And thank you, Chen, for open sourcing the code.) I have used it with a USB-II not sure if it fully supports an MKIII. It's not clear that it supports the MKIII, though likely since I believe it to perform the same as the MKII from a communications perspective.Chen's (W7AY) original MacOS “router” has been updated and modified by others to keep it current, especially in light of new versions of the MacOS. I've heard of W7AY's µH Router ( ), presumably the third party (not made/supported by Microham) application you are referencing. Well, I can *imagine* it, but I wouldn’t want to write or support it!) (I can’t imagine a driver that could multiplex a device across multiple operating systems. Each OS has an appropriate driver for the device. Essentially, ANY USB device must connect either to the native Mac OS or to a virtual machine running another OS (e.g., Windows). On Jan 30, 2020, at 6:54 PM, Andy Holmes, K5PO wrote:Ĭorrect. Interfaces uses uH Router which is a native MAC OS program. MLDX and other Mac OS software written to support microHAM "keyer" Router (with Windows software) at the same time. You can not run MacOS software (e.g., MLDX) and microHAM USB Device Router as long as no other Windows software is connected to it?No. So you can have the MACLoggerDx connected to the virtualized Microham Have you run into challenges with Com port software/hardware management? Perhaps I'll also use N1MM virtualized for contests too. I'll likely use MACLoggerDX for the day-to-day as you do. It's not clear that it supports the MKIII, though likely since I believe it to perform the same as the MKII from a communications perspective. If I understand correctly, it seems to work well in a virtualized environment provided you're not trying to have applications from multiple OS's connect with the software? So you can have the MACLoggerDx connected to the virtualized Microham Router as long as no other Windows software is connected to it? I don't want to buy a Mac workstation for the hamshack to replace my aging custom PC only to run into software roadblocks. Though I'm a longtime Mac OS and Windows user, my Mac is a work device so not appropriate for testing ham radio software.
0 Comments
Leave a Reply. |