Re: [Xlog-discussion] v1.6 adventures & comments

[Martin Ewing - AA6E]

Alex was spot on about the logic needing to be in the transceiver 
backend.  I had forgotten all about this, but the Orion backend (my 
backend!) seems to be set up correctly.  I coded and tested the 
following snippet that retrieves the current output power in watts:

status = rig_get_level(my_rig, RIG_VFO_CURR, RIG_LEVEL_RFPOWER, &pwr);
        /* pwr (actually, pwr.f) is relative: 0.0 - 1.0 range */
status = rig_power2mW(my_rig, &mwpwr, pwr.f, freq, mode);
        /* mwpwr (int) will be set to the actual demanded output power
          in milliwatts (0 - 100000 for the Orion). Freq and mode
          are current valid rig vfo setting and operating mode. */

I don't know what xlog is doing, but it is not this.  So I think we have 
an actual bug report.

73 Martin AA6E

Alexandru Csete wrote:
> On Wed, 14 Nov 2007 23:07:12 -0500
> Martin Ewing - AA6E <address@hidden> wrote:
>
> > ...
> >
> > 2. Clicking Power button gives a result between 0 and 256.  Hamlib 
> > returns a floating value between 0.0 and 1.0.  For a 100 watt rig
> > like mine, that should be 0 - 100 W of course.  Ideally, there would
> > be a preference setting for max. power that would be used to scale
> > the result.  In any case, 256 can't be right for most of us!
>
> The application can use rig->power2mW API function if it is implemented
> by the backend.
>
> Otherwise, the min/max power is also available via the
> rig_caps->tx_range_list1 / 2 - again, if properly implemented by the
> backend.
>
> Conversion shouldn't be done at application level,
> since for HF/VHF/UHF rigs the max power depends on which band you are
> on. I don't know if there is any convention for whether 1.0
> corresponds to the "global" max power or just the band specific max
> power.
>
> 73
> Alex OZ9AEC
>
>
> _______________________________________________
> Xlog-discussion mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/xlog-discussion