I suggest that you install Oracle s Virtual Box and then a real Windows (XP is cheap on the internet) in the virtual machine. That will probably give moreMessage 1 of 6 , Oct 1View SourceI suggest that you install Oracle's Virtual Box and then a "real"
Windows (XP is cheap on the internet) in the virtual machine. That will
probably give more control over how the USB devices / drivers are
recognized by the windows application.
Howdy Dave, I have found in the past, that while some programs have no issues finding the com port when running in Wine, some will just plain refuse. IMessage 1 of 6 , Oct 1View Source
I have found in the past, that while some programs have no issues finding the com port when running in Wine, some will just plain refuse.
I apologize for misunderstanding your original post. I personally try to avoid ever recommending that anyone purposely run a Microsoft operating system. I would instead suggest a search for a Linux alternative. Another suggestion would be to search the Wine forums. Perhaps a posting to a Wine specific group. Wine can be a touchy app and a pain to configure at times. It is also not unheard of to get it working with one app, only to have it break another app.
Best of Luck,
Michael - K5WRN
---In email@example.com, <djaksha@...> wrote:
Hi, everyone for responding.
Let me clarify, somewhat.
In my example of establishing the symbolic link to com9, I have in fact used a different com port number for each app. I should have stated that first.
Yes, the FLdigi is the standard install that you download from the FLdigi site. So in FLdigi, when you assign the port for PTT, you will get a list of possible devices available. In the case of my Navigator interface it will be cu.NavPTT-----00POXO0YB. PTT works as it should.
In the case of the RigBlaster Advantage it would be cu.SLAB_USBtoUART and PTT works as it should. This would indicate to me, that the cabling is correct between the computer,interface and transmitter.
The problem occurs with the WINE executables. With the Navigator interface establishing a symbolic link works just as you would expect, and the transmitter keys normally.
With the RigBlaster Advantage the same procedure produces no PTT action. I can select VOX with the PTT/VOX switch on the Advantage and the transmitter will key ok
---In firstname.lastname@example.org, <michaelwrenn@...> wrote:I noticed that you say that FLDigi is the standard Mac install. I read this to mean that it is not running through Wine but is running natively. With that in mind, your link will have no effect as FLDigi will not be using the Wine dosdevices links.
You did not say what rig you are using. For my RBA (Rig Blaster Advantage) setup, both with an Icom and a Yaesu radio, I have used VOX as the method to key the radio. FLDigi is configured to use the RBA's audio for receive and playback.
If you are attempting to use the com port for keying, you will have to use alternate settings. Also, I had a Dumb Dumb moment this past weekend where I couldn't figure out why RTTY wouldn't key the rig. I had forgotten that the RTTY keying is being sent through the CW/FSK port of the RBA in which case the rig had to be put into CW mode to key up. Something I'll have to look at again at a later date to see if it actually works that way. But, the point is to remember how everything is cabled up and how the software interfaces with the RBA.
Michael - K5WRN
---In email@example.com, <geoff.nw7gm@...> wrote:
One potential problem I see is you're linking both interfaces to 'Com9'. Try linking the RigBlaster to a different 'com' port.
Geoff McAlpin, NW7GM (ex N7PGN)
CN87trOn Sep 30, 2013 12:11 PM, <djaksha@...> wrote:
Hi, everyone. Hope someone has some insight into this problem.I have two interface for digital work on the Mac. The first is a US Interface Navigator. The second, I just bought, is a RigBlaster Advantage. Both are USB interface devices.I use Fldigi and JT65 and WSPR. The FLdigi is the standard compile for the Mac, and the other two programs are WINE executables that I have used for a long time with my US Interface Navigator.When selecting the audio interface for Fldigi, you just need to select the device in the /dev directory. But the other two pieces of software need a COMxx port specified. I normally do this by setting up a symbolic link. For example:ln -s /dev/cu.NavPTT-----00POXO0YB com9
This link is established in the dosdevices directory in the JT65 or WSPR package. This works fine to trigger the PTT on my KX3.The problem I am having is I cannot get the PTT to work with other software besides FLdigi when using the new interface, a RigBlaster
However, the same procedure does not work for the Advantage.
Trying the following:
ln -s /dev/cu.SLAB_USBtoUART com9
installs the com9 reference in the dosdevices directory, but does not result in the PTT being actuated on the Advantage.
Do you have any suggestion on how to proceed to resolve this problem?
The vendor has no idea why this will not work.Any insights would really be appreciated.73,DaveKF7DRU