Re: [Hamlib-developer] Error trying to set hamlib PTT in soundmodem

[Tony C. <ton...@gm...>]

On 4 May 2013 10:29, Remi Chateauneu <rem...@gm...> wrote:

> Hi Tony,
>
> Just to be sure, can you pleqse use the command-line option "-c" to ensure
> that the right file is taken ?
>
> It should be /etc/ax25/soundmodem.conf
>
> http://dev.man-online.org/man8/soundmodem/
>
> *soundmodem* accepts the following options:
> -v levelSet the verbosity level. 0 only displays fatal errors.-c
> confignameUse the named configuration. If absent the first is taken.
>
Could you also ensure that this file is readable by typing the following
> command ?
>
> ls -l /etc/ax25/soundmodem.conf
>
> Thanks
>
>
>
OK, so some weird stuff is happening here ...

By default, soundmodem looks for /etc/ax25/soundmodem.conf (or it has
been!) but when I specifically call it with the -c option, I get ...

    tonyc@Compaq:~$ soundmodem -c /etc/ax25/soundmodem.conf
    sm[5501]: Configuartion not found

Note this was run as an unprivileged user, I have confirmed I get the same
result running it as root!

I then check to see if the file is there (and readable) ...

    tonyc@Compaq:~$ ls -l /etc/ax25/soundmodem.conf
    -rw-r--r-- 1 root root 657 May  4 11:56 /etc/ax25/soundmodem.conf

It is!

I then attempted to run soundmodem as root (because I reminded myself I get
symlink errors to do with my USB CAT cable when running as an unprivileged
user!)

    root@Compaq:~# soundmodem
    rig:rig_init called
    rig: loading backend yaesu
    yaesu: initrigs2_yaesu called
    ...

(Hamlib init lines removed for simplicity)

    ...
    ft817: ft817_init called
    sm[5572]: Hamlib: rig_set_conf: 0=(null) : Invalid parameter
    sm[5572]: cannot start PTT output

So from what I can tell, something has changed from 0.16 to 0.18 (I haven't
tried 0.17!) that has messed with the Hamlib PTT in such a way that a NULL
value is being passed to Hamlib by the soundmodem software.

Interestingly, I have lost the GPIO options within soundmodemconfig so I
don't know if there is a link between the two?  Maybe soundmodem is no
longer detecting GPIO, which was there when I ran 0.16 which in turn is
causing it to mess up?

Cheers,
Tony


>
> On Sat, May 4, 2013 at 10:44 AM, Tony Corbett <ton...@gm...> wrote:
>
>> On Saturday, May 4, 2013, Remi Chateauneu wrote:
>>
>>> Hi Tony,
>>>
>>> Let's summarize. When running soundmodem as root, it works. As a normal
>>> user, you get the error message:
>>>
>>> I always start soundmodem as a privileged user (root) and never as a
>> normal user (in my case my own account) I get the error from the Hamlib PTT
>> when starting as root, I have never tried as an unprivileged user. Perhaps
>> I should, but as noted previously, I believe there was a reason for
>> starting as root. Think I need to try if only to remind myself!
>>
>>
>>> sm[9304]: cannot start PTT output
>>>
>>>  sm[9304]: Hamlib: rig_set_conf: 0=(null) : Invalid parameter
>>>
>>>  First question please, can you run the command dmesg or tail the content of your syslog
>>> file when starting soundmodem ? It might show interesting messages maybe.
>>>
>>> I will do this when I get home,  right now I'm out and about!
>>
>> Now let's see the code. The error comes from the soundmodem file ptt.c :
>>>
>>> my_rig_error = rig_set_conf(state->u.rig_ptr,
>>>      rig_token_lookup(state->u.rig_ptr, ptr_key), ptr_val);
>>> if (my_rig_error != RIG_OK) {
>>>      logprintf(MLOG_ERROR,
>>>           "Hamlib: rig_set_conf: %s=%s : %s\n",
>>>            ptr_key ? ptr_key : NULL,
>>>            ptr_val ? ptr_val : NULL,
>>>            rigerror(my_rig_error));
>>>
>>>  First problem: ptr_key is NULL, but this case is not taken into account.
>>>
>>> This is because the string params[3] is NULL:
>>> int pttinit(struct pttio *state, const char *params[])
>>>
>>> Are we sure that soundmodem accesses the same config file when running
>>> as root and as a normal user ? Could you please send your command line and
>>> this config file ?
>>>
>>
>> The soundmodem file is stored under the /etc hierarchy and requires a
>> privileged account to edit it by default (perhaps this was my reason for
>> starting as root, as I had to edit as root?) If I edit as unprivileged
>> user using the GUI, I can read it but cannot save (expected due to
>> permissions set on the file!)
>>
>> As far as I can tell, soundmodem is using the same config file as both
>> privileged and unprivileged user.
>>
>> The command line I am using is a simple "soundmodem &" to get it running
>> in the background.
>>
>> After this I can normally exit as root then run "xastir &" as an
>> unprivileged user.
>>
>> Indeed, there should be a fix printing these args in case it does not
>>> work.
>>>
>>> Thanks
>>>
>>> Remi
>>>
>>>
>>> On Fri, May 3, 2013 at 8:53 PM, Tony Corbett <ton...@gm...> wrote:
>>>
>>>> remi.chateauneu <at> gmail.com <remi.chateauneu <at> gmail.com> writes:
>>>>
>>>> >
>>>> > Le 25.03.2013 20:09, Tony Corbett a écrit :
>>>> > > Hi Remi,
>>>> > >
>>>> > > Thanks for the reply, and by all means forward it to the Hamlib
>>>> reflector.
>>>> > >
>>>> > > (1) I am able to use rigctl without error.
>>>> > >
>>>> > > (2) I used root for soundmodem, but ran Grig with my own account.
>>>> > >
>>>> > > (3) I'm sure there was a reason I used root to start soundmodem, but
>>>> > > can't recall why? I probably ran into some permissions problems
>>>> > > somewhere and have "always done it this way since!"
>>>> >
>>>> > Maybe access right to the serial interfaces ?
>>>> > Or necessary rights so that soundmodem can create its network
>>>> interfaces ?
>>>> >
>>>> > >
>>>> > > (4) It is indeed an FT-817, and the serial_speed was just me trying
>>>> to
>>>> > > see if the (null) was coming from the rig configuration params box;
>>>> it
>>>> > > wasn't!
>>>> > >
>>>> > > There has been some developments since I sent my initial email to
>>>> you!
>>>> > >
>>>> > > I now have it ALL working, however I had to use a pre-compiled
>>>> binary
>>>> > > from Ubuntu Software Centre! Unfortunately it is version 0.16 not
>>>> 0.18
>>>> > > as is the latest version on Thomas' site.
>>>> > >
>>>>
>>>> Ok, so I got this going by installing the precompiled version in the
>>>> Ubuntu
>>>> Software Centre (0.16)
>>>>
>>>> Today, I upgraded to Ubuntu 13.04 which in turn has upgraded soundmodem
>>>> to
>>>> 0.18, and the exact same problem has re-appeared!
>>>>
>>>> I am now at a loss as to how to solve this without uninstalling 0.18 and
>>>> trying to compile a previous version again!
>>>>
>>>> Any help would be appreciated!
>>>>
>>>> 73,
>>>> Tony
>>>> G0WFV
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Get 100% visibility into Java/.NET code with AppDynamics Lite
>>>> It's a free troubleshooting tool designed for production
>>>> Get down to code-level detail for bottlenecks, with <2% overhead.
>>>> Download for free and get started troubleshooting in minutes.
>>>> http://p.sf.net/sfu/appdyn_d2d_ap2
>>>> _______________________________________________
>>>> Hamlib-developer mailing list
>>>> Ham...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/hamlib-developer
>>>>
>>>
>>>
>>
>> --
>> A J CORBETT
>> ton...@gm...
>>
>>
>>
>


-- 
A J CORBETT
ton...@gm...