Joop Stakenborg wrote:
Op woensdag 04-02-2009 om 21:41 uur [tijdzone -0500], schreef John B.
Egger:
Perhaps this isn't the place for this question but all I could find in
sourceforge/hamlib was a developers' forum and I'm a long way from
being a developer.
Hi John,
judging from the output it is not a xlog problem, I see at least 2
errors. The hamlib-devel mailing list is a good starting point for
fixing this.
xlog tries to retrieve mode, power level (if you have the field
enabled), frequency, ptt and your s-meter value. This is done by polling
the rig every x millisecond if you have polling enabled. You might want
to make this time a little longer to see if this helps.
You should make yourself familiar with the rigctl binary. It is in the
ultimate tool for debugging hamlib. It is available in the hamlib-utils
package. People on the hamlib-devel can tell you if the orion II is
fully supported.
Regards,
Joop PG4I
Joop,
Thanks for your advice. Sorry for the delay in responding, but it's
taken me a while to solve the issue. In the hamlib "help" forum, Martin
(AA6E) suggested the latest CVS build of hamlib. When I downloaded and
compiled it, the hamlib problem with Xlog 1.9 was solved. The country
maps are terrific.
Of course now you have 2.0 out, so I'm still a step behind...
_______________________________________________
Xlog-discussion mailing list
Xlog-discussion@nongnu.org
http://lists.nongnu.org/mailman/listinfo/xlog-discussion
