Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Trlog\]\s+Rig\s+Control\s+Problem\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Trlog\]\s+Rig\s+Control\s+Problem\s*$/: 8 ]

Total 8 documents matching your query.

1. [Trlog] Rig Control Problem (score: 1): Author: Alan Dove <alan@alandove.com>; Date: Wed, 16 Feb 2022 18:45:03 -0500; Hey, folks: Next problem: I can't get rig control to work. TR finds my Winkeyer without trouble, but apparently my Icom IC-7200 isn't one of the supported models in the standard TR code - putting "IC; /archives//html/TRLog/2022-02/msg00008.html (7,384 bytes)
2. Re: [Trlog] Rig Control Problem (score: 1): Author: Tree <tree@kkn.net>; Date: Wed, 16 Feb 2022 17:55:09 -0800; It's been a long time since I have looked at the Icom computer interface protocol. Back in the day (some 20 years ago) - the commands were pretty consistent between their radios (unlike Yaesu where e; /archives//html/TRLog/2022-02/msg00009.html (8,600 bytes)
3. Re: [Trlog] Rig Control Problem (score: 1): Author: w9cf@arrl.net; Date: Wed, 16 Feb 2022 19:16:00 -0700; If you are using the linux version and the Icom code doesn't work, the easiest solution is to install hamlib and use the rigctld option. I typically use that anyway since you can then have other prog; /archives//html/TRLog/2022-02/msg00010.html (9,096 bytes)
4. Re: [Trlog] Rig Control Problem (score: 1): Author: "alan@alandove.com" <alan@alandove.com>; Date: Wed, 16 Feb 2022 21:34:43 -0500; Hey, folks: I'm using TRLinux, and as I mentioned, neither the native Icom control nor the hamlib solution works. Hamlib does indeed seem like the way to go. It just isn't working. In other news, I'v; /archives//html/TRLog/2022-02/msg00011.html (10,009 bytes)
5. Re: [Trlog] Rig Control Problem (score: 1): Author: James Pahoundis via Trlog <trlog@contesting.com>; Date: Thu, 17 Feb 2022 02:44:48 +0000 (UTC); I have used the Icom rig control in the linux version. I have used it on the 706 and the 7300.for the 706 I just radio one type=IC706. but for the 7300 I had to set: radio one type = 735 radio one re; /archives//html/TRLog/2022-02/msg00012.html (10,444 bytes)
6. Re: [Trlog] Rig Control Problem (score: 1): Author: Tree <tree@kkn.net>; Date: Wed, 16 Feb 2022 18:55:59 -0800; hamlib is something I know nothing about - so can't help. Tree _______________________________________________ Trlog mailing list Trlog@contesting.com http://lists.contesting.com/mailman/listinfo/trl; /archives//html/TRLog/2022-02/msg00013.html (10,582 bytes)
7. Re: [Trlog] Rig Control Problem (score: 1): Author: w9cf@arrl.net; Date: Wed, 16 Feb 2022 22:55:24 -0700; Obviously, you should use whatever program you find works best. I don't have an Icom rig, so the built in Icom code is written from a combination of Tree's original code and the Icom documentation. I; /archives//html/TRLog/2022-02/msg00014.html (9,373 bytes)
8. Re: [Trlog] Rig Control Problem (score: 1): Author: Alan Dove <alan@alandove.com>; Date: Thu, 17 Feb 2022 09:24:08 -0500; Hey, folks: Thanks again for the quick troubleshooting help. I've now run the additional tests suggested, and it looks like hamlib is working but TRlog isn't able to communicate with my rig through i; /archives//html/TRLog/2022-02/msg00015.html (10,211 bytes)

Current List: 1 - 8
Page: [1]