← Back to team overview

ubuntu-hams-devel team mailing list archive

[Bug 483925] Re: rigctl/hamlib does not work with Icom PCR1000

 

Hello genepool-

I have constructed a "pre-release" update package of hamlib (for Ubuntu Karmic or Lucid) which includes the latest fixes for the Icom PCR100, PCR1000, and PCR1500 radios, as mentioned by Stephane.  Would it be possible for you to install this version of hamlib on your system and verify that it fixes the problem on your PCR1000?:
  https://launchpad.net/~ubuntu-hams/+archive/ppa

Thanks for reporting this problem, and for your help in testing the fix.

** Changed in: hamlib (Ubuntu)
       Status: Triaged => Incomplete

-- 
rigctl/hamlib does not work with Icom PCR1000
https://bugs.launchpad.net/bugs/483925
You received this bug notification because you are a member of Ubuntu
ham developers, which is the registrant for hamlib.

Status in Ham Radio Control Libraries: Unknown
Status in “hamlib” package in Ubuntu: Incomplete

Bug description:
Ubuntu 9.10 Karmic rigctl, Hamlib version 1.2.9 outputs the following error on startup with Icom pcr1000

 $ rigctl -m 401 -r /dev/ttyS1 -s 9600 -vvvvvv
    rigctl, Hamlib version 1.2.9
    Report bugs to <hamlib-developer@xxxxxxxxxxxxxxxxxxxxx>
    rig:rig_init called 
    rig: loading backend pcr
    pcr: init called
    rig_register (402)
    rig_register (401)
    rig:rig_open called 
    pcr_transaction: cmd = H101
    pcr_send: cmd = H101, len = 4
    TX 6 bytes
    0000     48 31 30 31 0d 0a  H101..
    pcr_read_block
    RX 1 bytes
    0000     0a .
    RX 1 bytes
    0000     47 G
    RX 3 bytes
    0000     30 30 30   000
    pcr_read_block: RX 4 bytes
    pcr_transaction: got G000
    pcr_parse_answer: len = 4
    pcr_transaction: cmd = H101
    pcr_send: cmd = H101, len = 4
    TX 6 bytes
    0000     48 31 30 31 0d 0a  H101..
    pcr_read_block
    RX 4 bytes
    0000     0a 47 30 30    .G00
    pcr_transaction: got 
    G00
    pcr_parse_answer: len = 4
    rig_open: error = Protocol error 

I tried hamlib-1.2.10 and got the same error.  I have not tried the unstable snapshot yet.