[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xlog-discussion] v1.6 adventures & comments
From: |
Joop Stakenborg |
Subject: |
Re: [Xlog-discussion] v1.6 adventures & comments |
Date: |
Sat, 24 Nov 2007 20:09:05 +0100 |
Op donderdag 15-11-2007 om 21:47 uur [tijdzone -0500], schreef 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. */
>
Yes, xlog was using both functions, but because of a wrong RFPOWER level
function for the ts870, I multiplied it by 2.56...
It is fixed in CVS now. There will be an updated xlog soon.
> 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
Thanks,
Joop PG4I