Posted: 1/1/2010 8:30:38 PM EDT
Any fldigi users here that use rig control successfully? I think I've gotten it to work once and that's it. I usually use HRD but now that I'm running Linux I'm trying to get fldigi going. I haven't had any luck with hamlib or Rigcat. Neither of them work. Here's what my hamlib config looks like. It'd really be sweet if I could get this working.
This is the error it gives me when I start fldigi. For whatever reason I get no errors when I click the Initialize button. 
What works in HRD doesn't work in fldigi. And fwiw this didn't work when I was on Windows either. |
| I have no experience with fldigi whatsoever but since you had it work once, it suggests that your cabling and baud rate etc is good but something else in your comms is on the hairy edge. Have you tried increasing the write delay and post write delay settings? It could be that your computer is blasting the serial data into the radio faster than it can accept it. Maybe try a write delay of 2 ms? |
Oh, dude, I'm sorry, but every time I see a post like this the first thing I do is laugh hysterically. Moving to linux is like joining a cult of self-flagellation. I'm allowed to say this because I still have the scars, having run a production quality MythTV installation for the family for 3 years now. First piece of advice: go back to the dark side. Seriously. OK, Luke, still won't go there? Then my second quasi-useful piece of advice is to check out the com port using a terminal program. Can you get commands into and data back out of the radio successfully? If so then we can start blaming Fldigi and hamlib. Which C-IV interface are you using, BTW? P.S. if you do go back to the dark side you can use Fldigi and HRD together on Windows. Just instantiate HRD's "third party software" virtual serial port. Set Fldigi to Kenwood mode and point it at that port. You'll still have to designate another port for PTT control or rely on something like Signalink VOX for keying in this case, though (that's how I do it). aa |
|
Don't listen to him! He's in Gates' pocket and even gets paid DOUBLE every time he forwards the Microsoft email-tracking chain letters! (I know this because I used my super secret linux programs to hack his internetz)
Big time props for the working MythTV rig though!! Anyway, I have some of fldigi's rig control working with my 857 and will fire it all up later today (hopefully) and see what my settings are. (posted via Google Chrome on Ubuntu 9.10 Karmic) 
|
|
ALKVA, how ya doin'? I was just thinking about you the other day. It's been too long since we talked. I haven't mucked with the delay settings but I'll give that a whirl.
aa, if you re-read the OP it didn't work under Windows either.  I'm using the Icom CI-V / CT17 / CAT Interface from ZLP Electronics.
GT, thanks man. I'll look forward to seeing your settings. |
|
i see from the OP your "device" setting is /dev/ttyUSB0
you don't state whether you're running a usb interface or if you're running straight from a serial port. based on the CAT interface you say you're using i'm thinking you're running from a serial port. i'm running, in windows, from COM1 which in my fldigi setup in linux translates to /dev/ttyS0 hope this helps. if i'm out in left field forget i was even here. 
|
Every time a PC user converts to Linux or Unix, an angel gets her wings 
Conversely, every time a user fires up a Microsoft product God kills a kitten. Please don't give up Jax-think of the kittens... ETA: Posted via Opera on a smart phone running BSD Posted Via AR15.Com Mobile |
|
I'm trying. It's painful though.
Since they don't put serial adapters on computers these days I have no choice but to use an adapter. So running concurrently with the fldigi rig control issue I had another realization this afternoon. All my radio programming software as well as the APRS stuff require me to get the adapter working through the Vista VM I have since there aren't Linux alternatives. Me thinks this will be a longer process than I'd hoped. But I'll do my best for the kittens! |
|
Quoted:
aa, if you re-read the OP it didn't work under Windows either. I'm using the Icom CI-V / CT17 / CAT Interface from ZLP Electronics.Didn't catch that. Thought you had only tried HRD under Windows and Fldigi under Linux. So you are saying that HRD under Windows with that hardware setup is 100% but Fldigi under Windows is a no-go? If so then at least we know the hardware and drivers work under Windows. You might go back to debugging it under Windows so that you can confirm the hardware is working with HRD, then get the settings correct in Fldigi still under Windows, then transition to Linux. That way you eliminate the Linux driver guessing game and save that for last. Hey, at least with my Mythbox all the kittens that die get their angel wings 
|
|
Quoted:
Didn't catch that. Thought you had only tried HRD under Windows and Fldigi under Linux. So you are saying that HRD under Windows with that hardware setup is 100% but Fldigi under Windows is a no-go? If so then at least we know the hardware and drivers work under Windows. That's what I'm sayin'. 
You might go back to debugging it under Windows so that you can confirm the hardware is working with HRD, then get the settings correct in Fldigi still under Windows, then transition to Linux. That way you eliminate the Linux driver guessing game and save that for last. Might try that. I have to bring the Windows drive back online to migrate my mail and gather what I suspect will be a mind-boggling list of software to worry about moving/finding alternatives for. 
ETA: Grrr, I thought I was about to be smarter than the average bear. I figured maybe I could at least get my radio apps to run under WINE but I still can't get them to recognize the adapter. Any way I can make /dev/ttyUSB0 = COMx? |
|
Quoted:
ETA: Grrr, I thought I was about to be smarter than the average bear. I figured maybe I could at least get my radio apps to run under WINE but I still can't get them to recognize the adapter. Any way I can make /dev/ttyUSB0 = COMx? Yeah, don't sweat not having something work in WINE when there are peripherals involved. The only thing I've accomplished peripheral-wise with WINE is DVDShrink. |
|
Quoted:
Any fldigi users here that use rig control successfully? yes, with Ubuntu and my new IC7200. the fact that the interface is not working in Windows either is a clue...
so let's do some basic troubleshooting: what is the output of this: $ dmesg | grep tty ar-jedi |
|
Quoted:
Oh, dude, I'm sorry, but every time I see a post like this the first thing I do is laugh hysterically. Moving to linux is like joining a cult of self-flagellation. I'm allowed to say this because I still have the scars, having run a production quality MythTV installation for the family for 3 years now. ooops, didn't realize this was the Girl Scouts technical forum, my error. ar-jedi 
ps: which Myth distro are you using? Knoppmyth/LinHES? Mythbuntu? |
|
Quoted:
which Myth distro are you using? Knoppmyth/LinHES? Mythbuntu? Straight shot Ubuntu 9.04 and Myth 0.21 right out of the standard repository. 4 tuners: 2 x HDHomeRun (for clear QAM) and 2 x PVR-150 (straight cable and STB output). Firewire to tune the STB. Nvidia out at 1080p into my 42" LCD. Logitech remote running through LIRC. Meanwhile, back to our regularly scheduled Fldigi problem...still think you need to get it running under Windoze first. Try RigCAT instead of HamLib. XML files can be downloaded from here: http://www.w1hkj.com/xmlarchives.html I currently have Fldigi configured for RigCAT and CAT PTT talking to my HRD third party serial port. I can run it and DM780 simultaneously that way and have them both operate my IC7000. That isn't the same as going straight to the radio but it does demonstrate that RigCAT works and the nice thing about the xml files is that they set all the RigCAT param's for you except for COM port and port speed. eta typo |
|
Quoted:
Quoted:
which Myth distro are you using? Knoppmyth/LinHES? Mythbuntu? Straight shot Ubuntu 9.04 and Myth 0.21 right out of the standard repository. 4 tuners: 2 x HDHomeRun (for clear QAM) and 2 x PVR-150 (straight cable and STB output). Firewire to tune the STB. Nvidia out at 1080p into my 42" LCD. Logitech remote running through LIRC. 0.21 is pretty much plug-n-play with the hardware you have. back in the day, ca 2003/4, getting myth snapshots a couple of times a week was necessary, the makes often required a lot of patch gymnastics, v4l was in it's infancy, and my PVR250/PVR350 pair cost a lot and had no end of audio and video related driver issues plus that stupid ROM download, meanwhile LIRC sort of worked some of the time. i was among the first to derive an IR blaster-friendly LIRC solution to channel changing on external set-top boxes... link. so quit bitching about things being difficult!
ar-jedi |
|
Quoted:
so let's do some basic troubleshooting: what is the output of this: $ dmesg | grep tty Well, I'm back on my Windows drive but that's how I got that the serial adapter is running as /dev/ttyUSB0. Quoted:
Meanwhile, back to our regularly scheduled Fldigi problem...still think you need to get it running under Windoze first. Try RigCAT instead of HamLib. XML files can be downloaded from here: http://www.w1hkj.com/xmlarchives.html RigCAT doesn't work either. I'd already downloaded the ic-7000 xml file. Well, Houston, I think we have a bigger problem. HRD isn't working now either. I've tried both of my CAT cables.  I'm beginning to suspect the adapter though I don't know why it would've quit working all of a sudden. I'm trying to find the programming cable for my HT. If that works then it's not the adapter.
ETA: Well crap. I was hoping it was the adapter. Unfortunately I just used it to read my 8800. I wonder if something's up with the radio. I'm going to do a reset and see if it starts working. ETA2: Ok, still doesn't work after doing a CPU reset. So the adapter works with the 8800, not the 7000. When I try HRD or IC7000BKT to connect to the radio the tx and rx lights just blink together (at the same time) and at a steady pace until it fails. I guess maybe I need to call Icom Monday. Looks like something might have happened to the radio. 
|
|
Quoted:
Quoted:
Quoted:
which Myth distro are you using? Knoppmyth/LinHES? Mythbuntu? Straight shot Ubuntu 9.04 and Myth 0.21 right out of the standard repository. 4 tuners: 2 x HDHomeRun (for clear QAM) and 2 x PVR-150 (straight cable and STB output). Firewire to tune the STB. Nvidia out at 1080p into my 42" LCD. Logitech remote running through LIRC. 0.21 is pretty much plug-n-play with the hardware you have. back in the day, ca 2003/4, getting myth snapshots a couple of times a week was necessary, the makes often required a lot of patch gymnastics, v4l was in it's infancy, and my PVR250/PVR350 pair cost a lot and had no end of audio and video related driver issues plus that stupid ROM download, meanwhile LIRC sort of worked some of the time. i was among the first to derive an IR blaster-friendly LIRC solution to channel changing on external set-top boxes... link. so quit bitching about things being difficult!
ar-jedi Sorry about the possibility of it being the Radio, Jax, but at least you've got it narrowed down now. You know, Jedi, it IS easier now.  My first build with 0.20 before it was in the repository took me a week to get it running and about two months to get it stable. Of course I knew nothing about Myth or Linux. The new build took me about 8 hours and a week to get it stable. That includes fixing all the BS things like upgrading the Nvidia drivers, adding codecs, killing off the new stupid pop up warnings in Ubuntu, re-writing the lirc .conf files and a half dozen other things including beating Samba back into submission (the family uploads all digital photos to the server so we can play them on the big screen), etc. So yeah, it's easier now...NOT! I would guess that if I was starting from scratch with no knowledge base to pull from it would still take the original week and two months. However we all have our geek hobbies like Linux and ham radio in addition to the manly art of the black rifle so who am I to complain
|
|
Seems pretty simple, GT. I guess you actually have a serial port on your pc. Which reminds me, I bet I can try it on my old laptop. It's got a serial connection. I'll test that theory now. Thanks for the screenshot.
ETA: It would appear to be my radio. It didn't work on the laptop either with the serial port. That eliminates the USB/Serial adapter.
|
|
This might be obvious but sometimes obvious thing get messed up?
Make sure the radio is set properly, I believe there is a setting for the serial address in a menu on the rig make sure those are set how your software wants. I just looked in the pdf manual, baud rate is menu item number 48 and address is 49. Hope that helps. I remember running grig to my 746Pro and I think I ran fldigi as well, I yanked my computer stuff out of my shack because since I work on a computer I really didn't enjoy it... If you continue to have trouble I might drag it up form the basement and sked you. |
|
Quoted:
This might be obvious but sometimes obvious thing get messed up? Make sure the radio is set properly, I believe there is a setting for the serial address in a menu on the rig make sure those are set how your software wants. I just looked in the pdf manual, baud rate is menu item number 48 and address is 49. Hope that helps. I remember running grig to my 746Pro and I think I ran fldigi as well, I yanked my computer stuff out of my shack because since I work on a computer I really didn't enjoy it... If you continue to have trouble I might drag it up form the basement and sked you. Good point! CI-V address and baud rate! |
| Yeah, I've ensured that the address is 70 and I've changed the baud rate with no change. I've also confirmed that the config files match these settings. I'll double check when I get home, though, since I did the CPU reset. I'm pretty sure 70 is the default now. |