rigserve-devel Mailing List for Rigserve
Status: Alpha
Brought to you by:
aa6e
Menu
▾
▴
rigserve-devel — Comments, questions, and discussion about the rigserve project
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(5) |
Jun
|
Jul
(11) |
Aug
(17) |
Sep
(5) |
Oct
|
Nov
(1) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(3) |
Feb
|
Mar
(8) |
Apr
(3) |
May
(3) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
| 2009 |
Jan
(9) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
|
From: <aa...@us...> - 2011-10-25 01:46:06
|
Revision: 52
http://rigserve.svn.sourceforge.net/rigserve/?rev=52&view=rev
Author: aa6e
Date: 2011-10-25 01:46:00 +0000 (Tue, 25 Oct 2011)
Log Message:
-----------
add to release info
Modified Paths:
--------------
trunk/readme.txt
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <aa...@us...> - 2011-10-25 01:41:19
|
Revision: 51
http://rigserve.svn.sourceforge.net/rigserve/?rev=51&view=rev
Author: aa6e
Date: 2011-10-25 01:41:13 +0000 (Tue, 25 Oct 2011)
Log Message:
-----------
Add Yaesu FT-8xx, set vers 0.35, clean up
Modified Paths:
--------------
trunk/backend.py
trunk/changelog.txt
trunk/dummy.py
trunk/globals.py
trunk/ic_765.py
trunk/ic_codes.py
trunk/ic_r8500.py
trunk/icom.py
trunk/readme-be.txt
trunk/readme-developer.txt
trunk/readme.txt
trunk/rigclient.py
trunk/rigserve.py
trunk/tentec.py
trunk/tt_omni6.py
trunk/tt_orion.py
trunk/user_guide.html
trunk/user_guide.odt
Added Paths:
-----------
trunk/yaesu_ft8xx.py
trunk/yaesu_ft8xx_symbols.py
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <aa...@us...> - 2008-06-13 01:38:23
|
Revision: 50
http://rigserve.svn.sourceforge.net/rigserve/?rev=50&view=rev
Author: aa6e
Date: 2008-06-12 18:38:20 -0700 (Thu, 12 Jun 2008)
Log Message:
-----------
Rationalize vfo_select (Icom) with Ten-Tec style VFO selection.
Modified Paths:
--------------
trunk/backend.py
trunk/ic_765.py
trunk/ic_codes.py
trunk/ic_r75.py
trunk/ic_r8500.py
trunk/icom.py
trunk/tentec.py
trunk/tt_omni6.py
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <aa...@us...> - 2008-05-01 00:03:21
|
Revision: 49
http://rigserve.svn.sourceforge.net/rigserve/?rev=49&view=rev
Author: aa6e
Date: 2008-04-30 17:03:08 -0700 (Wed, 30 Apr 2008)
Log Message:
-----------
Tagging release 0.31 of Rigserve project
Added Paths:
-----------
tags/release-0.31/
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <aa...@us...> - 2008-05-01 00:01:52
|
Revision: 48
http://rigserve.svn.sourceforge.net/rigserve/?rev=48&view=rev
Author: aa6e
Date: 2008-04-30 17:01:49 -0700 (Wed, 30 Apr 2008)
Log Message:
-----------
version update
Modified Paths:
--------------
trunk/tentec.py
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <aa...@us...> - 2008-05-01 00:01:27
|
Revision: 47
http://rigserve.svn.sourceforge.net/rigserve/?rev=47&view=rev
Author: aa6e
Date: 2008-04-30 17:01:13 -0700 (Wed, 30 Apr 2008)
Log Message:
-----------
Improve serial I/O logic
Modified Paths:
--------------
trunk/tentec.py
trunk/tt_orion.py
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <aa...@us...> - 2008-04-29 20:41:28
|
Revision: 46
http://rigserve.svn.sourceforge.net/rigserve/?rev=46&view=rev
Author: aa6e
Date: 2008-04-29 13:41:23 -0700 (Tue, 29 Apr 2008)
Log Message:
-----------
Add IC-765, Icom capabilities, prepare release 0.31
Modified Paths:
--------------
trunk/backend.py
trunk/changelog.txt
trunk/dummy.py
trunk/globals.py
trunk/ic_codes.py
trunk/ic_r75.py
trunk/ic_r8500.py
trunk/icom.py
trunk/readme-be.txt
trunk/readme.txt
trunk/rigclient.py
trunk/rigserve.py
trunk/tentec.py
trunk/tt_omni6.py
trunk/tt_orion.py
Added Paths:
-----------
trunk/ic_765.py
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: Martin E. A. <aa...@ew...> - 2008-04-12 14:49:28
|
Hello, Rigserve list! You may be interested to know that Rigserve's web site has largely moved to a Sourceforge Wiki. You can still get there through http://rigserve.sourceforge.net or directly at http://rigserve.wiki.sourceforge.net/ . What's the big deal? Well, it's a Wiki, which means *you* can edit and extend the material. For now, it's open to the world, but it's best if you identify yourself when contributing. You can subscribe to the Wiki's RSS feed to see when anything changes. Leave questions or comments of general interest on the FAQ page. Or use this list. Cheers / 73 Martin -- Martin Ewing, AA6E aa...@ew... +1-203-315-5160 |
|
From: <aa...@us...> - 2008-04-06 21:42:38
|
Revision: 45
http://rigserve.svn.sourceforge.net/rigserve/?rev=45&view=rev
Author: aa6e
Date: 2008-04-06 14:42:35 -0700 (Sun, 06 Apr 2008)
Log Message:
-----------
add Omni 6
Modified Paths:
--------------
trunk/user_guide.html
trunk/user_guide.odt
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <aa...@us...> - 2008-03-29 04:32:10
|
Revision: 44
http://rigserve.svn.sourceforge.net/rigserve/?rev=44&view=rev
Author: aa6e
Date: 2008-03-28 21:32:02 -0700 (Fri, 28 Mar 2008)
Log Message:
-----------
Add support for Ten-Tec Omni6, Omni6 Plus
Modified Paths:
--------------
trunk/backend.py
trunk/globals.py
trunk/ic_codes.py
trunk/ic_r75.py
trunk/icom.py
Added Paths:
-----------
trunk/tt_omni6.py
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <aa...@us...> - 2008-03-19 14:53:43
|
Revision: 43
http://rigserve.svn.sourceforge.net/rigserve/?rev=43&view=rev
Author: aa6e
Date: 2008-03-19 07:53:40 -0700 (Wed, 19 Mar 2008)
Log Message:
-----------
screwed up the release no again...
Removed Paths:
-------------
tags/release-0.22/
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <aa...@us...> - 2008-03-19 14:52:45
|
Revision: 42
http://rigserve.svn.sourceforge.net/rigserve/?rev=42&view=rev
Author: aa6e
Date: 2008-03-19 07:52:40 -0700 (Wed, 19 Mar 2008)
Log Message:
-----------
Tagging release 0.30 of Rigserve project
Added Paths:
-----------
tags/release-0.30/
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <aa...@us...> - 2008-03-19 14:52:10
|
Revision: 41
http://rigserve.svn.sourceforge.net/rigserve/?rev=41&view=rev
Author: aa6e
Date: 2008-03-19 07:52:08 -0700 (Wed, 19 Mar 2008)
Log Message:
-----------
Tagging release 0.22 of Rigserve project
Added Paths:
-----------
tags/release-0.22/
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <aa...@us...> - 2008-03-19 14:51:43
|
Revision: 40
http://rigserve.svn.sourceforge.net/rigserve/?rev=40&view=rev
Author: aa6e
Date: 2008-03-19 07:51:39 -0700 (Wed, 19 Mar 2008)
Log Message:
-----------
Used wrong release number -- again!
Removed Paths:
-------------
tags/release-0.23/
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <aa...@us...> - 2008-03-19 14:15:35
|
Revision: 39
http://rigserve.svn.sourceforge.net/rigserve/?rev=39&view=rev
Author: aa6e
Date: 2008-03-19 07:15:33 -0700 (Wed, 19 Mar 2008)
Log Message:
-----------
fixing error
Removed Paths:
-------------
tags/release-0.23/trunk/
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <aa...@us...> - 2008-03-19 14:14:44
|
Revision: 38
http://rigserve.svn.sourceforge.net/rigserve/?rev=38&view=rev
Author: aa6e
Date: 2008-03-19 07:14:42 -0700 (Wed, 19 Mar 2008)
Log Message:
-----------
Correcting misnamed release
Added Paths:
-----------
tags/release-0.23/
Removed Paths:
-------------
tags/release-0.22/
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <aa...@us...> - 2008-03-19 14:05:13
|
Revision: 37
http://rigserve.svn.sourceforge.net/rigserve/?rev=37&view=rev
Author: aa6e
Date: 2008-03-19 07:05:06 -0700 (Wed, 19 Mar 2008)
Log Message:
-----------
Tagging release 0.22 of Rigserve project
Added Paths:
-----------
tags/release-0.22/trunk/
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: Adam C. <car...@ca...> - 2008-01-21 04:04:57
|
Hi Hugh, Hugh Blemings wrote: > Hi Adam, All, >> I've recently purchased a Yaesu FT-897D, and CT-62 control cable for it. >> Now all I need to do is get some software for it :) >> >> I stumbled upon rigctl, which led me to rigserve. >> > Cool, welcome to the list and, judging by the F call, the hobby :) > :) I was scheduled to upgrade to the advanced license in February but a trip to ZL is going to push that back a few months - but thanks for the welcome. >> I see that there isn't a Yaesu BE development in SVN yet, and I don't >> feel comfortable donating my brand new radio :) But I have got a little >> bit of Python experience, and have worked with (mainly IP) protocol >> analysis before so I wouldn't mind having a bash at writing a backed for it. >> >> Is anyone else working on a Yaesu backend that I might be able to work with? >> > /me looks a bit sheepish. > > I had some basic code going with my FT817 which is very similar to the '897 but didn't get it finished up to the point of being suitable for public consumption :) > > Will dig around and see where it got to and advise. > That'd be awesome thanks! Looking at the examples and (really not enough) 1.5 pages of reference in the manufacturer's manual, you may have reached the limit as to how much can be controlled. 73 and Regards, Adam VK2FNRD |
|
From: Hugh B. <hu...@bl...> - 2008-01-21 02:34:53
|
Hi Adam, All, > I've recently purchased a Yaesu FT-897D, and CT-62 control cable for it. > Now all I need to do is get some software for it :) > > I stumbled upon rigctl, which led me to rigserve. Cool, welcome to the list and, judging by the F call, the hobby :) > I see that there isn't a Yaesu BE development in SVN yet, and I don't > feel comfortable donating my brand new radio :) But I have got a little > bit of Python experience, and have worked with (mainly IP) protocol > analysis before so I wouldn't mind having a bash at writing a backed for it. > > Is anyone else working on a Yaesu backend that I might be able to work with? /me looks a bit sheepish. I had some basic code going with my FT817 which is very similar to the '897 but didn't get it finished up to the point of being suitable for public consumption :) Will dig around and see where it got to and advise. vy 73 Hugh VK2YYZ/AD5RV |
|
From: Adam C. <car...@ca...> - 2008-01-21 02:07:29
|
Hello list, I've recently purchased a Yaesu FT-897D, and CT-62 control cable for it. Now all I need to do is get some software for it :) I stumbled upon rigctl, which led me to rigserve. I see that there isn't a Yaesu BE development in SVN yet, and I don't feel comfortable donating my brand new radio :) But I have got a little bit of Python experience, and have worked with (mainly IP) protocol analysis before so I wouldn't mind having a bash at writing a backed for it. Is anyone else working on a Yaesu backend that I might be able to work with? If not, I'll happily have a go at porting an existing (maybe icom I also have: o Icom 718 - HF transceiver o Yaesu VX-7R - handheld transceiver (6M, 2M, 70cm) o Uniden Bearcat 396 - handheld digital scanner (receive from high HF bands up to 23cm I think). Thanks in advance, 73 VK2FNRD... Adam |
|
From: Martin E. A. <aa...@ew...> - 2007-12-30 14:31:05
|
[I have changed the mailman options so that non-member posts will be held for moderation and then (hopefully) posted to the list. - Martin AA6E] Subject: Re: [Rigserve-devel] TS-2000 etc From: Jared Harvey <ma...@ja...> Date: Sun, 30 Dec 2007 09:16:39 -0500 To: Developers and testers of Rigserve <rig...@li...> CC: rig...@ja... Hello Martin, MEA> Please note (and all other subscribers, too) MEA> that you must use the same return address MEA> when sending to this list as the one you MEA> registered under. You registered under MEA> 'rig...@ja...' but sent mail MEA> apparently from 'ma...@ja...'. Mail MEA> from unknown sources is automatically MEA> discarded - with a copy to me. Hmmm what a bugger, I looked at the message I sent, and it had rig...@ja... for the >From field. I'm using google apps to manage my e-mail at jaredharvey.com, I guess Google must toss the ma...@ja... in the header some where. Hmmm not sure what I can do about that. I CCed myself on this one so I can look at the header. MEA> I would be delighted to have a TS-2000 MEA> backend definition for Rigserve. Possibly one MEA> of us could look at the problem. The main MEA> issue is that I do not have one of these MEA> units to test on, and things go a *lot* MEA> faster if you have one available! I have one available, but at my site. It's my only HF rig and I'm not currently willing to ship it. I can grant you SSH permissions to the machine it will be connected to. I could probably setup a web cam so you can see the radio display if required. At the moment I have the materials to make the PC interface , but I haven't soldered it up yet. I've been waiting until I had a software solution in hand, incase it influences my interface design. I currently plan on doing transformer isolation for the audio signals, 232 RTS for PTT, and 232 Tx Rx for radio control data. I can setup the 232 part quite quickly and you noted you don't support streaming at this time. So audio is probably less important. Simply connecting a 232 cable to it shouldn't be that big of a deal. I've found many streaming options, but haven't found a solution that allows PTT via 232 RTS line. I'd prefer not using VOX. What I'm really looking for is something like the http://www.w4mq.com/ setup, but I'd prefer Linux based. If my constraints are ones you can work with, let me know and I'll start setting it up. Items I'll have to do include, moving the radio and PC next to each other, ethernet at this point will probably be wireless, then allowing SSH through the firewall machine to my local net. Best regards. .. ..-. / -.-- --- ..- / .-. . .- -.. / - .... .. ... .-.. . - ... / .... .- ...- . / .- / -... . . .-. Jared Harvey Operator KB1GTT e-mail rig...@ja... Web page http://jaredharvey.com |
|
From: Martin E. A. <aa...@ew...> - 2007-12-30 02:10:13
|
Jared - Thanks for your interest in Rigserve. Please note (and all other subscribers, too) that you must use the same return address when sending to this list as the one you registered under. You registered under 'rig...@ja...' but sent mail apparently from 'ma...@ja...'. Mail from unknown sources is automatically discarded - with a copy to me. I would be delighted to have a TS-2000 backend definition for Rigserve. Possibly one of us could look at the problem. The main issue is that I do not have one of these units to test on, and things go a *lot* faster if you have one available! Hamlib will probably support your rig, but as you may know, it is not really designed as an IP server. There is an RPC server interface available, however. Neither Hamlib or Rigserve attempts to support audio or other signal modes over Internet at this point. I believe there are other Linux technologies that can do that, although I have not explored them myself. (Streaming audio, certainly, but that normally has buffering delays. VOIP solutions may behave better.) 73 & Happy New Year Martin AA6E ------------ Subject: inquiry From: ma...@ja... Date: Sat, 29 Dec 2007 19:30:00 -0500 To: rig...@li... Hello rigserve-devel, I just happened across rigserver and it looks like exactly what I'm looking for. What I'm looking for is a TCP/IP interface that can work on both local networks as well as Internet networks. Including PTT Tx audio and Rx audio. I haven't found a complete solution quite yet, and it looks like this one is the best so far. Unfortunately, rigserver doesn't appear to support my radio a Kenwood TS2000. How ever Kenwood has been kind enough to offer the control commands in the freely available user manual. Found here http://kenweb1.kenwoodusa.com/KenwoodPortal/KenwoodComm/Resources/AMA_InstructionManuals/TS-2000%20Rve2.pdf So it probably isn't much of an issue to get the TS2000 supported, I'm willing to experiment if required. Either that or I'll have to keep searching for a solution. So what I'm looking for is feed back about using my TS2000 as a test platform, or perhaps suggestions of other TCP/IP control solutions. I've tried Echolink and failed because it doesn't support local networking, and other options don't seem to offer Linux support, a preference I'd like to keep. Would adding the TS2000 be a big task, or does anyone one here have a suggested remote rig control option for Linux? Best regards. .. ..-. / -.-- --- ..- / .-. . .- -.. / - .... .. ... .-.. . - ... / .... .- ...- . / .- / -... . . .-. Jared Harvey Operator KB1GTT e-mail rig...@ja... Web page http://jaredharvey.com |
|
From: <aa...@us...> - 2007-12-01 02:40:01
|
Revision: 36
http://rigserve.svn.sourceforge.net/rigserve/?rev=36&view=rev
Author: aa6e
Date: 2007-11-30 18:40:00 -0800 (Fri, 30 Nov 2007)
Log Message:
-----------
More error checking
Selectable binary or alpha VFO set/read methods
Update v1 S-meter calibration
Modified Paths:
--------------
trunk/tentec.py
trunk/tt_orion.py
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <aa...@us...> - 2007-12-01 02:38:01
|
Revision: 35
http://rigserve.svn.sourceforge.net/rigserve/?rev=35&view=rev
Author: aa6e
Date: 2007-11-30 18:37:53 -0800 (Fri, 30 Nov 2007)
Log Message:
-----------
Move backend dictionary to globals, other minor changes.
Modified Paths:
--------------
trunk/globals.py
trunk/rigserve.py
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <aa...@us...> - 2007-11-26 18:01:00
|
Revision: 34
http://rigserve.svn.sourceforge.net/rigserve/?rev=34&view=rev
Author: aa6e
Date: 2007-11-26 10:00:56 -0800 (Mon, 26 Nov 2007)
Log Message:
-----------
Add dummy backend
Modified Paths:
--------------
trunk/rigserve.py
trunk/tt_orion.py
Added Paths:
-----------
trunk/dummy.py
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
16 messages has been excluded from this view by a project administrator.
