>From DXLab website: DXLab on Linux
de Bill N6WS DXLab applications will not run natively on Linux, nor will Wine enable their use on Linux. I got the application to install via WINE.. however when I try to enable/install any of the components it just hangs on the download at 3072 bytes.... so don't get too excited about DXLabs working just because com ports work :( Any luck on your end? On Fri, Jul 3, 2015 at 10:34 AM, joshua besneatte <[email protected]> wrote: > Cool I hope you can get it working. I am installing DXLab now via wine to > see how that works, however I would much rather use native applications if > I could. I just started playing with fldigi. It looks really robust and > seems to have all the features you are looking for ( much more so than > rigctl which I think is more of a testing ground for the hamLib libraries? > ).... > > What functionality are your looking for in rigctl that is not available in > fldigi? > > On Fri, Jul 3, 2015 at 10:18 AM, Lahra Svare <[email protected]> wrote: > >> Yep - I get that now. But when people say: "Try this", that's all I >> knew to try. In some commands, the word RIG actually needs to be there - o >> it made it hard to figure out. I just missed some of the windows software >> for hams - the linux software is just very herky and missing so many >> features I've been using for many years. Thanks and good luck getting your >> tickets!!! >> >> L >> >> >> On 07/03/2015 10:48 AM, joshua besneatte wrote: >> >> Hi Laura, >> >> All the "syntax" below is essentially the same. In Linux everything is >> a file, so when you plug >> your rig in it gets associated a file link, eg /dev/ttyUSB0 >> >> However, depending on the device and system, it might end up in a >> different place. The below >> examples that didn't work, didn't work because the people that gave the >> suggestions expected >> you to know that /dev/rig means "refer to the device file of your rig". >> >> When you first plug in your USB device that connects to your rig, it is >> attached to a file in the /dev >> folder. It is not necessarily the same every time you plug it in. This is >> especially true if you have more than one >> of the same/similar type of device. If you unplug a usb serial device and >> immediately plug it back in >> it will get the next number, eg /dev/ttyUSB1. You can find out where your >> device got attached to the >> file-system by running the command: >> >> dmesg >> >> from the command line after you plug the device in. >> >> If you are referencing the device via a script or want it to have a >> static name you will need to set up a >> udev rule. Something like on this page: >> http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/ >> >> The syntax is not cut and paste though. If you plug in your device and >> then send me the output of: >> >> lsusb >> >> and the last 10 lines or so of >> >> dmesg >> >> I can help you set up a udev rule so that your device will always have >> a symlink at something like /dev/ham-rig >> We will also be able to ensure the device has the correct permissions to >> be able to interact with all of your software. >> >> I hope you find this useful. I am a long time Linux user but am new to >> the whole HAM scene, so I don't know much >> about the software you are using... at least not yet. You are using the >> software I just installed and am about to use. >> Hopefully this can be a good learning experience for both of us. I am >> taking my Tech and maybe the General exam >> tomorrow so I will have a call sign soon and can begin testing. >> >> -Joshua >> >> >>> *CORRECT CO*DE for me: *rigctl -m 104 -r /dev/ttyUSB0 set_freq %d* >>> Some others I tried, based on other users, none of these worked: >>> * rigctl -m 104 -r /dev/*rig >>> * set_freq %d * >>> *rigctl -m 104 -r /dev/tty/USB0 set_freq %d **rigctl -m 104 -r >>> /dev/ttyUSB0 set_freq %d* >>> >>> With each time I found another user giving another syntax - I'd first >>> try that - then try other radio codes, then try different settings - it was >>> so hard to tell if the problem was my syntax or my rig code or something >>> else I had no way of determining. All along, I was just not getting the >>> right info. Now it's working. >>> >>> Finally getting it to work was a short-lived happiness, however, as now >>> I find it conflicts with fldigi and my woes are beginning again. >>> >>> THIS is why I wanted to try to run a program like DXLabs, where all the >>> components work together without conflict. I want to run a dx cluster, >>> digital radio control and the ability to send CW, which was a three week >>> process to figure out in Ubuntu. Finally found out:, to send CW, I >>> have to be in Packet (USB) mode. Why? Maybe my confusion is just from too >>> many years of running windows software to control my radios. But it really >>> seems there aren't many great software solutions for hams in linux. >>> >>> I'm currently running FLDigi, Klog & XDX. I miss all the other pieces of >>> DXLabs (or HRD, from back in the day, now it's bloated and no fun). Where's >>> the contest software? Like N1MM or similar? >>> >>> If any of you have some lists of software you use and enjoy in Linux, >>> please share them. I'm more than willing to learn something new - but I am >>> having trouble finding them. >>> >>> My original question was how to use windows software under wine and >>> still use com ports, as the windows software doesn't see ttyUSB0 as an >>> option. I didn't get that answered - so instead I'm trying to use the >>> limited software available in ubuntu and I'm hopeful there's more out there >>> I have not yet found. >>> >>> Now, back to the frustration of trying to work a deaf special event >>> station on 17 meters. >>> >>> 73 and thanks for all the help. >>> >>> Lahra, KT9X >>> >>> >>> Lahra KT9X [email protected] (or [email protected]) >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~ubuntu-hams >>> Post to : [email protected] >>> Unsubscribe : https://launchpad.net/~ubuntu-hams >>> More help : https://help.launchpad.net/ListHelp >>> >>> >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~ubuntu-hams >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~ubuntu-hams >> More help : https://help.launchpad.net/ListHelp >> >> >> >
_______________________________________________ Mailing list: https://launchpad.net/~ubuntu-hams Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-hams More help : https://help.launchpad.net/ListHelp
