Bill Somerville | 20 Oct 18:44 2014

Request pull: fix error in Elecraft K3 backend

The following changes since commit 7d01e0fc4d17076b3cd56854ee7773b069874f78:

   RIG_OK is zero and need not be negated and this will not change 
(2014-10-18 20:31:47 +0100)

are available in the git repository at:

   git://git.code.sf.net/u/bsomervi/hamlib k3-get-split-mode-error

for you to fetch changes up to 12e88dc33d992de8a144e56b42bd80a06bb58054:

   Fix response length expected error in K3 back end (2014-10-20 
13:43:34 +0100)

----------------------------------------------------------------
Bill Somerville (1):
       Fix response length expected error in K3 back end

  kenwood/k3.c | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

73
Bill
G4WJS.

------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
(Continue reading)

Bill Somerville | 18 Oct 00:32 2014

Pull-request: Add retry mechanism for "newcat" Yaesu backends

The following changes since commit 89ebe6bc846d18668864598aed1b139f2b24da96:

   Add support for DMK Engineering URI (2014-10-12 09:05:25 -0500)

are available in the git repository at:

   git://git.code.sf.net/u/bsomervi/hamlib yaesu-retries

for you to fetch changes up to dfa2d69b451bc0f12a4e9d8febf6d2d21c20d229:

   Disable auto information mode on open (2014-10-17 23:08:10 +0100)

----------------------------------------------------------------
Bill Somerville (3):
       Add retry mechanism for Yaesu "newcat" backend
       Implement retries for Yaesu "newcat" rigs
       Disable auto information mode on open

  yaesu/ft2000.c |    2 +-
  yaesu/ft450.c  |    2 +-
  yaesu/ft5000.c |    2 +-
  yaesu/ft9000.c |    2 +-
  yaesu/ft950.c  |    4 +-
  yaesu/newcat.c | 1142 
++++++++++++++++----------------------------------------
  6 files changed, 324 insertions(+), 830 deletions(-)

73
Bill
G4WJS.
(Continue reading)

Bill Somerville | 16 Oct 22:35 2014

Pull request: fix defects in IC-7410 back end.

The following changes since commit c38dfb97aa47f2279ba7718a8942b64271c06cae:

   Quell compiler warning--missing parens (2014-10-12 09:17:31 -0500)

are available in the git repository at:

   git://git.code.sf.net/u/bsomervi/hamlib ic-7410-vfos

for you to fetch changes up to ad8b1983af58e498687b38cde4b2b916a666ce3d:

   Added IC-7410 data modes (2014-10-16 21:33:19 +0100)

----------------------------------------------------------------
Bill Somerville (2):
       Icom IC-7410 has VFO A/B not MAIN/SUB
       Added IC-7410 data modes

  icom/ic7410.c | 19 ++++++++-----------
  1 file changed, 8 insertions(+), 11 deletions(-)

73
Bill
G4WJS.

------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
(Continue reading)

Andreas Kupries | 14 Oct 19:00 2014
Picon

21th Tcl Conference - Registration & Hotel Reminder

21'th Annual Tcl/Tk Conference (Tcl'2014)
http://www.tcl.tk/community/tcl2014/

This is a reminder that Registration for the Conference is open and
can be done at

	http://www.tcl.tk/community/tcl2014/reg.html

Note that the holding period for hotel rooms has passed. To register
for a room, call 1-503-796-3851, speak to Mary Kirchner and mention
the Tcl Conference to receive the reduced rate.

See you in Portland,

Andreas Kupries
Tcl 2014 Program Chair
ActiveState Software Inc.
Vancouver, BC, Canada

------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
Harrison Kyle | 14 Oct 16:59 2014
Picon

IC-735 and the "m" option

Hello all,

I've been working on fixing up a program written in perl that uses rigctld as the back-end. The program is called yfktest for those who are interested. I'm prefacing this message with what I have done so that I can be complete in my description of a problem I might have com across in hamlib.

I have an IC-735 (it's marked as beta in hamlib) that uses a CI/V to USB cable for rig control. My initial issue was that when I would tune the radio quickly, yfktest would lock up. So I did a bit of searching, and found that yfktest asked for mode and frequency whenever it asked for an update. In order to debug, I ran rigctl with 5 'v's of debugging to find that instead of returning the mode, it returned "get_mode: error = Command rejected by the rig". I'll add in the links to 2 pastebins, one for when I type 'm' without tuning, and one when I type 'm' while tuning.

Without tuning: http://pastebin.com/7iCnqWV5

With tuning: http://pastebin.com/rZX4AWU1

I found a website that was based in Germany that had a great explanation of CI/V data bytes. It seems that the rig is trying to send too much data all at once and is either confused itself, or is confusing hamlib.


If I'm unclear in anything, or if I picked the wrong list, please let me know.
Harrison -- VE2HKW

Use Linux!: linuxmint.org
Known as ve2hkw on irc.freenode.net irc.spotchat.org, irc.dream-phase.net and almost anywhere else!
><>
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
Hamlib-developer mailing list
Hamlib-developer <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hamlib-developer
Bill Somerville | 14 Oct 15:24 2014

Patch to fix Ten-Tec Orion set/get split VFO defects.

The following changes since commit 89ebe6bc846d18668864598aed1b139f2b24da96:

   Add support for DMK Engineering URI (2014-10-12 09:05:25 -0500)

are available in the git repository at:

   git://git.code.sf.net/u/bsomervi/hamlib fix-tt-orion-get-split

for you to fetch changes up to 5ede844bafbb2eb00db78ae094b18e629bd18d6a:

   Fix Ten-Tec Orion get/set split functions (2014-10-14 14:19:40 +0100)

----------------------------------------------------------------
Bill Somerville (1):
       Fix Ten-Tec Orion get/set split functions

  tentec/orion.c | 10 +++++-----
  1 file changed, 5 insertions(+), 5 deletions(-)

73
Bill
G4WJS.

------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
Bill Somerville | 14 Oct 14:05 2014

Small patch to fix rig_open configuration checking.

The following changes since commit 89ebe6bc846d18668864598aed1b139f2b24da96:

   Add support for DMK Engineering URI (2014-10-12 09:05:25 -0500)

are available in the git repository at:

   git://git.code.sf.net/u/bsomervi/hamlib serial-contro-line-error-fix

for you to fetch changes up to cd44a8d9267db3ca8725d7e28eda84373718d4f7:

   Only check for serial control line conflicts if PTT shares CAT port 
(2014-10-14 12:51:23 +0100)

----------------------------------------------------------------
Bill Somerville (1):
       Only check for serial control line conflicts if PTT shares CAT port

  src/rig.c | 103 
++++++++++++++++++++++++++++++++++----------------------------
  1 file changed, 57 insertions(+), 46 deletions(-)

73
Bill
G4WJS.

------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
Veijo Arponen | 12 Oct 11:25 2014
Picon

Support for DMK Engineering URI is missing

Hello,

I have a problem with the CM119A GPIO. The PTT line of the DMK Engineering URI was not activated by the hamlib  when using fldigi or rigctl.

I fiddled with the source code and managed to edit the code in cm108.c to get the PTT-line activate on my URI-box.

A successful rigctl command is
rigctl -p /dev/hidraw0 -C ptt_pathname=/dev/hidraw0,ptt_type=CM108,ptt_bitnum=2


Attached is the modified source code file and a patch in 'git diff' format. The version of origin is 1.2.15.3.

73 de Veijo OH3NFC
diff --git a/hamlib-1.2.15.3/src/cm108.c b/hamlib-1.2.15.3/src/cm108.c
index cd8b923..b9f1d17 100644
--- a/hamlib-1.2.15.3/src/cm108.c
+++ b/hamlib-1.2.15.3/src/cm108.c
 <at>  <at>  -102,9 +102,10  <at>  <at>  int cm108_open(hamlib_port_t *port)
 	if (!ioctl(fd, HIDIOCGRAWINFO, &hiddevinfo)
 	&&
 	  (
-	    (hiddevinfo.vendor == 0x0d8c	// CM108/109/119
-		&& hiddevinfo.product >= 0x0008
-		&& hiddevinfo.product <= 0x000f
+	    (hiddevinfo.vendor == 0x0d8c &&	// CM108/109/119/119A
+                (hiddevinfo.product >= 0x0008 &&
+                hiddevinfo.product <= 0x000f ||
+                hiddevinfo.product == 0x013a)
 	    )
 	    ||
 	    (hiddevinfo.vendor == 0x0c76 &&	// SSS1621/23
Attachment (cm108.c): text/x-csrc, 8 KiB
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
Hamlib-developer mailing list
Hamlib-developer <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hamlib-developer
Bill Somerville | 9 Oct 18:54 2014

Hamlib 3 usage in WSJT-X.

Hi All,

this is a heads up and a request.

First some background:

WSJT-X (http://physics.princeton.edu/pulsar/K1JT/wsjtx.html) uses hamlib 
and other mechanisms for communications with rigs. It became apparent 
that a few of the hamlib back ends were not working quite right and a 
few others needed writing. The master branch had a good number of these 
issues resolved so we, the WSJT-X team, decided to use the master branch 
as our hamlib. Also I have been doing various fixes and enhancements to 
hamlib in my own git fork and pushing the patches upstream to Nate once 
they are tested.

Currently I have a few outstanding patches to push upstream so we are 
building hamlib from my fork where I maintain an integration testing 
branch where I merge all outstanding changes based on the official 
master. We statically link hamlib to avoid clashes, particularly on 
Linux, with the official hamlib release which is used by other 
applications including some of the other WSJT modes. We also package the 
rigctld server since it has the back end code embedded, also statically 
linked for the same reason and some of our users do use the server in 
their station setups. We install that as rigctld-wsjtx to avoid clashes.

We are fast approaching our first official release of WSJT-X v1.4 with 
this arrangement of hamlib, we have the first release candidate Beta in 
the field right now.

We intend to push all hamlib changes we make upstream and will only use 
those that are accepted, modulo a small time delay while we test them. 
We do this because we have every intention of switching to the next 
official release of hamlib when it is available on the various platforms 
we support (currently Windows, Mac, and Linux on Intel and ARM so far). 
At that time we will almost certainly revert to dynamic linking.

So the request:

We are shipping what I guess is a derivative work as it stands (maybe 
the wrong term), we are open source (apart from one binary which we are 
stripping out of the Linux packages and making an optional user install) 
and GPL v3 licensed.

So are the hamlib team happy with this and if so, what attribution and 
licensing statements do we need to add to our product with respect to 
hamlib?

73
Bill
G4WJS.

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
Nate Bargmann | 9 Oct 17:43 2014
Picon

Re: Yaesu FT dx 3000

* On 2014 06 Oct 06:12 -0500, Bill Somerville wrote:
> Hi All,
> 
> does anyone have WIP on a back end for this rig?

Not me.  Go for it!

73, Nate

--

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
D. R. Evans | 7 Oct 23:22 2014
Face
Picon

meaning of "target VFO" in rig_set_split_vfo?

The API documentation says:

----

int rig_set_split_vfo 	( 	RIG *  	rig,
		vfo_t  	vfo,
		split_t  	split,
		vfo_t  	tx_vfo
	) 		

set the split mode

Parameters:
    rig	The rig handle
    vfo	The target VFO
    split	The split mode to set to
    tx_vfo	The transmit VFO

----

The plain language of this would seem to be that if I have:
  VFO A on 14010 (current VFO)
  VFO B on 14020
with split NOT enabled, and if I then exceute:

rig_set_split_vfo(rigp, RIG_VFO_B, RIG_SPLIT_ON, RIG_VFO_B)

that would say:
  1. split VFO B from the current VFO (because VFO B is the target), and
  2. make VFO B the transmit VFO.

But that's not what happens at all on my K3. What actually happens is:
  1. The frequencies of VFO A and VFO B get swapped (!! weird; I didn't tell
any frequencies to change)
  2. the transmit VFO becomes VFO B.

I don't understand the first step of this behaviour at all. The lack of
understanding possibly comes from the ambiguity of the phrase "target VFO" in
the API description. What *exactly* do those words mean here?

Sorry if this question is answered somewhere in the documentation. I couldn't
find it.

  Doc  N7DR

--

-- 
Web:  http://www.sff.net/people/N7DR

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Hamlib-developer mailing list
Hamlib-developer <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hamlib-developer

Gmane