Menu

Kenwood TS850 controled bij HAMLIB

Help
pa3dsc
2005-04-03
2013-01-15
  • pa3dsc

    pa3dsc - 2005-04-03

    I connect my TS850 to the /dev/ttyS0
    Sometimes gMFSK starts correct but mostly there are some errors at startup:

    In the qMFSK window:
    "Hamlib init: rig_get_freq failed: Invalid parameter"

    In the terminal window:
    pa3dsc@largo:/usr/bin$ gmfsk
    kenwood_get_freq: unsupported VFO 536870912

    hamlib is enabled (hamlib 1.2.1, gMFSK 0.6,  slackware-10.1)

    With the minicom program I can communicate with the TS850 no problem.

    Back to hamlib
    I don't change anything and there are different outputs at the same command.

    Bad:
    pa3dsc@largo:~$ rigctl -r /dev/ttyS0 -m 209 f
    kenwood_transaction: Unexpected reply 'FA00014070360'
    kenwood_transaction: Unexpected reply '4070360'
    kenwood_transaction: Command is not correctly terminated '70360  '
    kenwood_transaction: Command is not correctly terminated 'IF0001'
    kenwood_get_freq: unsupported VFO 536870912
    get_freq: error = Invalid parameter

    Good:
    pa3dsc@largo:~$ rigctl -r /dev/ttyS0 -m 209 f
    14070360

    I like to have my gMFSK correct working with hamlib.
    Maybe is an stable result from rigctl the sollution.

    I'm not a programmer. Still I like to use gMFSK. (hamlib)

    Look a like problem is mentioned in:
    http://sourceforge.net/mailarchive/message.php?msg_id=8203860
    But I don't find the sollution.

    Can anybody help me?

    73 martin pa3dsc

     
    • Martin Ewing, AA6E

      I suggest that there may be a delay when opening the connection to the rig.  Possibly it takes a while for your serial port to stabilize.  If you run rigctl interatively, i.e., wait a little while before giving the "f" command, do you always get the right answer?

      Also, try running with the -vvvvv option (rigctl -m ... -r ... -vvvvv to get verbose debugging information and report it here.

      I am running gMFSK with no particular problems with the Orion.

      73, Martin AA6E

       

Log in to post a comment.