Menu ▾ ▴

PRM80xx can not connect to my PRM8020 and PRM8070

Help
RaspII
2021-01-10
2021-04-15
1 2 3 4 > >> (Page 1 of 4)

  • RaspII

    RaspII - 2021-01-10

    Hello,
    maybe sombody can help.
    I try to use this lib for my Philips PRM80xx devices.
    I see that the data is send via 4800 bps to the radio, but no answers are coming back.
    I'm able to comunicate to the radios via FPP software (PRM80HW, PRM80SW). Would be fine if somebody can help.
    Best Regards
    Claus (DC0CM)

     

    • Michael Black

      Michael Black - 2021-01-11

      Can you run rigctl and do some tests?
      We've only got the PRM8060 in hamlib and doesn't look like it's ever been tested.
      So if you have a manual with CAT commands it would help.
      Assuming you are running hamlib 4.0
      rigctl -m 28001 -s 4800 -vvvvv -Z
      To read freq f
      To write freqF 145000000
      And send me debug info.
      Mike W9MDB

      On Sunday, January 10, 2021, 05:33:19 PM CST, RaspII <raspii@users.sourceforge.net> wrote:

      Hello,
      maybe sombody can help.
      I try to use this lib for my Philips PRM80xx devices.
      I see that the data is send via 4800 bps to the radio, but no answers are coming back.
      I'm able to comunicate to the radios via FPP software (PRM80HW, PRM80SW). Would be fine if somebody can help.
      Best Regards
      Claus (DC0CM)

      PRM80xx can not connect to my PRM8020 and PRM8070

      Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/

      To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

       
      alternate

      • Michael Black

        Michael Black - 2021-01-11

        I also see in the PRM80 documentation that the serial port is TTL level.So I assume you have a level convertor configured with it?
        Mike W9MDB 

        On Sunday, January 10, 2021, 05:42:16 PM CST, Black Michael <mdblack98@yahoo.com> wrote:

        Can you run rigctl and do some tests?
        We've only got the PRM8060 in hamlib and doesn't look like it's ever been tested.
        So if you have a manual with CAT commands it would help.
        Assuming you are running hamlib 4.0
        rigctl -m 28001 -s 4800 -vvvvv -Z
        To read freq f
        To write freqF 145000000
        And send me debug info.
        Mike W9MDB

        On Sunday, January 10, 2021, 05:33:19 PM CST, RaspII <raspii@users.sourceforge.net> wrote:

        Hello,
        maybe sombody can help.
        I try to use this lib for my Philips PRM80xx devices.
        I see that the data is send via 4800 bps to the radio, but no answers are coming back.
        I'm able to comunicate to the radios via FPP software (PRM80HW, PRM80SW). Would be fine if somebody can help.
        Best Regards
        Claus (DC0CM)

        PRM80xx can not connect to my PRM8020 and PRM8070

        Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/

        To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

         
        alternate

    • Bill Somerville

      Bill Somerville - 2021-01-13

      Hi Claus,

      I believe the reason the FPP software only runs on MS-DOS is because it needs to take direct control of the hardware of the serial port. That is needed because exact but non-standard timing of the signalling is required. On systems that can use Hamlib it will not be possible to directly control the serial port hardware because it is only accessed via a system device driver running in kernel mode. It may be that the modem option board in the PRM-80 series rigs is needed. If you are programming via the mic socket or via the rear DB-25 but do not have a modem option installed; then it may be impossible to access the rig from a modern PC operating system. I am not certain on ant of this, just reading some documents found on line.

      73
      Bill
      G4WJS.

       

      • RaspII

        RaspII - 2021-01-13

        Hi Bill,
        I already was able to send commands via Hyperterminal and get an answer
        from the radio.
        For me that means that it is possible to communicate via Windows
        standard drivers/Dlls.

        If I measure baud rate etc. I can see that 4800 Baud are going via TX
        and RX lines.
        e.g., if you take a look to my scans:
        https://sourceforge.net/p/hamlib/discussion/25919/thread/93afa09f52/#36fc

        If I send "1B 00 04" (Hex) via Terminal I also receive "06 06 11" as the
        DOS software is doing.
        Up to know I do not know what command that is, but I can reproduce that
        a standard windows Terminal Software gets the same results (using
        Windows driver) as the DOS prm80sw software (directly writing to the
        serial port).

        Do you know whether the HAMLIB software needs a special prm80xx Firmware
        programmed to the radio?

        73
        Claus, DC0CM

         

        • Michael Black

          Michael Black - 2021-01-13

          Do you have a manual for that radio shows shows any commands?
          I have the commands for other prm rigs and none of them have a "1B" command.  They are all ASCII letters.
          If you just send an "H" (0x48) does the rig answer with anything?
          And any idea what "06 06 11" means?
          Mike

          On Wednesday, January 13, 2021, 02:06:50 PM CST, RaspII <raspii@users.sourceforge.net> wrote:

          Hi Bill,
          I already was able to send commands via Hyperterminal and get an answer
          from the radio.
          For me that means that it is possible to communicate via Windows
          standard drivers/Dlls.

          If I measure baud rate etc. I can see that 4800 Baud are going via TX
          and RX lines.
          e.g., if you take a look to my scans:
          https://sourceforge.net/p/hamlib/discussion/25919/thread/93afa09f52/#36fc

          If I send "1B 00 04" (Hex) via Terminal I also receive "06 06 11" as the
          DOS software is doing.
          Up to know I do not know what command that is, but I can reproduce that
          a standard windows Terminal Software gets the same results (using
          Windows driver) as the DOS prm80sw software (directly writing to the
          serial port).

          Do you know whether the HAMLIB software needs a special prm80xx Firmware
          programmed to the radio?

          73
          Claus, DC0CM

          PRM80xx can not connect to my PRM8020 and PRM8070

          Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/

          To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

           
          alternate

          • RaspII

            RaspII - 2021-01-13

            Hello Mike,

            No, I don't have a manual.
            And I don't get any response to an "H".

            And I assume only, that the 06 06 00.... is the request for EEPROM read
            (but I'm not sure).

            But why to send "H" ?
            I heard about sending a "H" the first time while reading the
            modification instructions:
            https://sourceforge.net/projects/prm80/files/prm80%20firmware/4.0/
            (chapter 8.)

            But for this modification I need a special Firmware. Is this Firmware
            also needed for the HAMLIB software for prm8060?

            That would explain why my radio is not responding, because I use the
            origninal Firmware version of the prm8070 (no EPROM is available at my
            radio).

            Thank you all for supporting me
            73, Claus

             

            • Michael Black

              Michael Black - 2021-01-13

              Can you show for example the first 5 channel frequencies and the relevant EPROM readings for the channels?
              It does sound like that rig does not support either Version 3 or Version 4 PRM commands.
              If you can program frequencies in the rig can you monitor that serial traffic?
              And what is answer you get with just the "1B" by itself?  Probably the current channel I would think.
              If we can figure out the channel meanings might be able to do something.
              Mike W9MDB

              On Wednesday, January 13, 2021, 02:43:54 PM CST, RaspII <raspii@users.sourceforge.net> wrote:

              Hello Mike,

              No, I don't have a manual.
              And I don't get any response to an "H".

              And I assume only, that the 06 06 00.... is the request for EEPROM read
              (but I'm not sure).

              But why to send "H" ?
              I heard about sending a "H" the first time while reading the
              modification instructions:
              https://sourceforge.net/projects/prm80/files/prm80%20firmware/4.0/
              (chapter 8.)

              But for this modification I need a special Firmware. Is this Firmware
              also needed for the HAMLIB software for prm8060?

              That would explain why my radio is not responding, because I use the
              origninal Firmware version of the prm8070 (no EPROM is available at my
              radio).

              Thank you all for supporting me

              73, Claus
              PRM80xx can not connect to my PRM8020 and PRM8070

              Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/

              To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

               
              alternate

              • RaspII

                RaspII - 2021-01-14

                I will try to figure this out, this evening.
                73, Claus

                 

  • RaspII

    RaspII - 2021-01-11

    Hi,
    yesterday I did the tests with hamlib-w64-3.3, now I switched to hamlib-w64-4.0.
    (The parameter -m was changed from -m2801 to -m28001, is this correct?).
    The result is the same, I see the command arriving with the correct baud rate but the radio is not responding.
    Yes, I use a 5V TTL logic to connect to the radio (MAX232). And this connection is running well if I use the very old DOS configuration software PRM80HW/PRM80SW.

    My assumption is, that I can use the standard Firmware of the radio and don't have to use the firmware from:
    https://svn.code.sf.net/p/prm80/code/firmware/trunk

    Here the debug information (I didn't try to write the frequency, only read):

    C:\Program Files (x86)\hamlib-w64-4.0\bin>rigctl -m28001 -rCOM1 -s4800 -vvvvv -Z
2021-01-11:08:24:33.084757: rigctl Hamlib 4.0
Last commit was Fri Dec 25 02:30:30 2020 +0000 SHA=519f82
2021-01-11:08:24:33.084757: Report bugs to <hamlib-developer@lists.sourceforge.net>

2021-01-11:08:24:33.084757: rig_init called
2021-01-11:08:24:33.085759: initrigs4_prm80: _init called
2021-01-11:08:24:33.085759: rig_register called
2021-01-11:08:24:33.085759: rig_register: rig_register (28001)
2021-01-11:08:24:33.085759: rig_open called
2021-01-11:08:24:33.085759: port_open called
2021-01-11:08:24:33.086752: serial_open called
2021-01-11:08:24:33.120327: serial_setup called
2021-01-11:08:24:33.121324: serial_setup: tcgetattr
2021-01-11:08:24:33.121324: serial_setup: cfsetispeed=4800,0x000c
2021-01-11:08:24:33.121324: serial_setup: cfsetospeed=4800,0x000c
2021-01-11:08:24:33.121324: serial_setup: data_bits=7
2021-01-11:08:24:33.121324: serial_setup: parity=4
2021-01-11:08:24:33.122328: serial_setup: tcsetattr TCSANOW
2021-01-11:08:24:33.123324: serial_flush called
2021-01-11:08:24:33.123324: tcflush
2021-01-11:08:24:33.175510: rig_get_vfo called
2021-01-11:08:24:33.175510: rig_get_vfo: no get_vfo
2021-01-11:08:24:33.176530: vfo_fixup: vfo=VFOA
2021-01-11:08:24:33.176530: vfo_fixup: final vfo=VFOA
2021-01-11:08:24:33.177521: rig_open: No set_vfo function rig so default vfo = VFOA
Opened rig model 28001, 'PRM8060'
2021-01-11:08:24:33.179178: Backend version: 20101027.0, Status: Alpha
2021-01-11:08:24:33.179622: rigctl_parse: called, interactive=1

Rig command: f
2021-01-11:08:24:56.194782: rigctl_parse: cmd=f(66)
2021-01-11:08:24:56.194782: rigctl_parse: cmd==0x66
2021-01-11:08:24:56.195778: rigctl_parse: vfo_opt=0
2021-01-11:08:24:56.195778: rigctl_parse: debug1
2021-01-11:08:24:56.195778: rigctl_parse: debug5
2021-01-11:08:24:56.195778: rigctl_parse: debug10
2021-01-11:08:24:56.195778: rigctl_parse: vfo_opt=0
2021-01-11:08:24:56.195778: rig_get_freq called vfo=currVFO
2021-01-11:08:24:56.196778: vfo_fixup: vfo=currVFO
2021-01-11:08:24:56.196778: vfo_fixup: Leaving currVFO alone
2021-01-11:08:24:56.196778: get_cache_freq: vfo=currVFO, freq=0
2021-01-11:08:24:56.197780: elapsed_ms: start = 0,0
2021-01-11:08:24:56.198778: rig_get_freq: cache check age=1000000ms
2021-01-11:08:24:56.198778: rig_get_freq: cache miss age=1000000ms, cached_vfo=None, asked_vfo=currVFO
2021-01-11:08:24:56.199778: vfo_fixup: vfo=VFOA
2021-01-11:08:24:56.199778: vfo_fixup: final vfo=VFOA
2021-01-11:08:24:56.199778: rig_get_freq: no set_vfo so vfo=VFOA
2021-01-11:08:24:56.200779: rig_flush: called for serial device
2021-01-11:08:24:56.201780: serial_flush called
2021-01-11:08:24:56.201780: tcflush
2021-01-11:08:24:56.202780: write_block called
2021-01-11:08:24:56.202780: write_block(): TX 1 bytes
2021-01-11:08:24:56.202780: 0000    45                                                  E
2021-01-11:08:24:56.203779: read_string called, rxmax=64
2021-01-11:08:24:59.333971: read_string(): Timed out 3.130192 seconds after 0 chars
2021-01-11:08:24:59.333971: elapsed_ms: start = 0,0
2021-01-11:08:24:59.334965: elapsed_ms: after gettime, start = 1610353499,334965800
2021-01-11:08:24:59.334965: rig_get_freq: cache reset age=999000ms, vfo=VFOA, freq=0
2021-01-11:08:24:59.335965: elapsed_ms: start = 0,0
2021-01-11:08:24:59.335965: elapsed_ms: after gettime, start = 1610353499,335965400
2021-01-11:08:24:59.336962: rigctl_parse: vfo_opt=0
get_freq: error = Protocol error
2021-01-11:08:24:59.337967: rigctl_parse: retcode=-8
2021-01-11:08:24:59.338960: rigctl_parse: called, interactive=1

Rig command: 2021-01-11:08:24:59.339961: rigctl_parse: cmd==0x0a

    hope this will help

     

    Last edit: RaspII 2021-01-11

    • Michael Black

      Michael Black - 2021-01-12

      Can you please test the following:
      rigctl -m28001 -rCOM1 -s4800 -vvvvv -Z\get_info
      Need to know if you are version 3 or 4.
      Hopefully that command worksAlso do this and see what is says
      w Ew H

      Mike

      On Monday, January 11, 2021, 02:30:14 AM CST, RaspII <raspii@users.sourceforge.net> wrote:

      Hi,
      yesterday I did the tests with hamlib-w64-3.3, now I switched to hamlib-w64-4.0.
      (The parameter -m was changed from -m2801 to -m28001, is this correct?).
      The result is the same, I see the command arriving with the correct baud rate but the radio is not responding.
      Yes, I use a 5V TTL logic to connect to the radio (MAX232). And this connection is running well if I use the very old DOS configuration software PRM80HW/PRM80SW.

      Here the debug information (I didn't try to write the frequency, only read):
      C:\Program Files (x86)\hamlib-w64-4.0\bin>rigctl -m28001 -rCOM1 -s4800 -vvvvv -Z
      2021-01-11:08:24:33.084757: rigctl Hamlib 4.0
      Last commit was Fri Dec 25 02:30:30 2020 +0000 SHA=519f82
      2021-01-11:08:24:33.084757: Report bugs to hamlib-developer@lists.sourceforge.net

      2021-01-11:08:24:33.084757: rig_init called
      2021-01-11:08:24:33.085759: initrigs4_prm80: _init called
      2021-01-11:08:24:33.085759: rig_register called
      2021-01-11:08:24:33.085759: rig_register: rig_register (28001)
      2021-01-11:08:24:33.085759: rig_open called
      2021-01-11:08:24:33.085759: port_open called
      2021-01-11:08:24:33.086752: serial_open called
      2021-01-11:08:24:33.120327: serial_setup called
      2021-01-11:08:24:33.121324: serial_setup: tcgetattr
      2021-01-11:08:24:33.121324: serial_setup: cfsetispeed=4800,0x000c
      2021-01-11:08:24:33.121324: serial_setup: cfsetospeed=4800,0x000c
      2021-01-11:08:24:33.121324: serial_setup: data_bits=7
      2021-01-11:08:24:33.121324: serial_setup: parity=4
      2021-01-11:08:24:33.122328: serial_setup: tcsetattr TCSANOW
      2021-01-11:08:24:33.123324: serial_flush called
      2021-01-11:08:24:33.123324: tcflush
      2021-01-11:08:24:33.175510: rig_get_vfo called
      2021-01-11:08:24:33.175510: rig_get_vfo: no get_vfo
      2021-01-11:08:24:33.176530: vfo_fixup: vfo=VFOA
      2021-01-11:08:24:33.176530: vfo_fixup: final vfo=VFOA
      2021-01-11:08:24:33.177521: rig_open: No set_vfo function rig so default vfo = VFOA
      Opened rig model 28001, 'PRM8060'
      2021-01-11:08:24:33.179178: Backend version: 20101027.0, Status: Alpha
      2021-01-11:08:24:33.179622: rigctl_parse: called, interactive=1

      Rig command: f
      2021-01-11:08:24:56.194782: rigctl_parse: cmd=f(66)
      2021-01-11:08:24:56.194782: rigctl_parse: cmd==0x66
      2021-01-11:08:24:56.195778: rigctl_parse: vfo_opt=0
      2021-01-11:08:24:56.195778: rigctl_parse: debug1
      2021-01-11:08:24:56.195778: rigctl_parse: debug5
      2021-01-11:08:24:56.195778: rigctl_parse: debug10
      2021-01-11:08:24:56.195778: rigctl_parse: vfo_opt=0
      2021-01-11:08:24:56.195778: rig_get_freq called vfo=currVFO
      2021-01-11:08:24:56.196778: vfo_fixup: vfo=currVFO
      2021-01-11:08:24:56.196778: vfo_fixup: Leaving currVFO alone
      2021-01-11:08:24:56.196778: get_cache_freq: vfo=currVFO, freq=0
      2021-01-11:08:24:56.197780: elapsed_ms: start = 0,0
      2021-01-11:08:24:56.198778: rig_get_freq: cache check age=1000000ms
      2021-01-11:08:24:56.198778: rig_get_freq: cache miss age=1000000ms, cached_vfo=None, asked_vfo=currVFO
      2021-01-11:08:24:56.199778: vfo_fixup: vfo=VFOA
      2021-01-11:08:24:56.199778: vfo_fixup: final vfo=VFOA
      2021-01-11:08:24:56.199778: rig_get_freq: no set_vfo so vfo=VFOA
      2021-01-11:08:24:56.200779: rig_flush: called for serial device
      2021-01-11:08:24:56.201780: serial_flush called
      2021-01-11:08:24:56.201780: tcflush
      2021-01-11:08:24:56.202780: write_block called
      2021-01-11:08:24:56.202780: write_block(): TX 1 bytes
      2021-01-11:08:24:56.202780: 0000 45 E
      2021-01-11:08:24:56.203779: read_string called, rxmax=64
      2021-01-11:08:24:59.333971: read_string(): Timed out 3.130192 seconds after 0 chars
      2021-01-11:08:24:59.333971: elapsed_ms: start = 0,0
      2021-01-11:08:24:59.334965: elapsed_ms: after gettime, start = 1610353499,334965800
      2021-01-11:08:24:59.334965: rig_get_freq: cache reset age=999000ms, vfo=VFOA, freq=0
      2021-01-11:08:24:59.335965: elapsed_ms: start = 0,0
      2021-01-11:08:24:59.335965: elapsed_ms: after gettime, start = 1610353499,335965400
      2021-01-11:08:24:59.336962: rigctl_parse: vfo_opt=0
      get_freq: error = Protocol error
      2021-01-11:08:24:59.337967: rigctl_parse: retcode=-8
      2021-01-11:08:24:59.338960: rigctl_parse: called, interactive=1

      Rig command: 2021-01-11:08:24:59.339961: rigctl_parse: cmd==0x0a

      hope this will help

      PRM80xx can not connect to my PRM8020 and PRM8070

      Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/

      To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

       
      alternate

      • RaspII

        RaspII - 2021-01-12

        I had to add a blank between "-Z" and "\ get_info", else the command "rigctl -m28001 -rCOM1 -s4800 -vvvvv -Z\ get_info" ends up with an error message, only.
        Even with this blank the programm stops working but shows some information before
        My result:

        C:\Program Files (x86)\hamlib-w64-4.0\bin>rigctl -m28001 -rCOM1 -s4800 -vvvvv -Z \get_info
2021-01-12:18:59:26.642239: rigctl Hamlib 4.0
Last commit was Fri Dec 25 02:30:30 2020 +0000 SHA=519f82
2021-01-12:18:59:26.643243: Report bugs to <hamlib-developer@lists.sourceforge.net>

2021-01-12:18:59:26.643243: rig_init called
2021-01-12:18:59:26.643243: initrigs4_prm80: _init called
2021-01-12:18:59:26.644242: rig_register called
2021-01-12:18:59:26.644242: rig_register: rig_register (28001)
2021-01-12:18:59:26.644242: rig_open called
2021-01-12:18:59:26.645239: port_open called
2021-01-12:18:59:26.645239: serial_open called
2021-01-12:18:59:26.680249: serial_setup called
2021-01-12:18:59:26.680249: serial_setup: tcgetattr
2021-01-12:18:59:26.680249: serial_setup: cfsetispeed=4800,0x000c
2021-01-12:18:59:26.680249: serial_setup: cfsetospeed=4800,0x000c
2021-01-12:18:59:26.681236: serial_setup: data_bits=7
2021-01-12:18:59:26.681236: serial_setup: parity=4
2021-01-12:18:59:26.681236: serial_setup: tcsetattr TCSANOW
2021-01-12:18:59:26.682250: serial_flush called
2021-01-12:18:59:26.682250: tcflush
2021-01-12:18:59:26.734242: rig_get_vfo called
2021-01-12:18:59:26.735243: rig_get_vfo: no get_vfo
2021-01-12:18:59:26.735243: vfo_fixup: vfo=VFOA
2021-01-12:18:59:26.736245: vfo_fixup: final vfo=VFOA
2021-01-12:18:59:26.736245: rig_open: No set_vfo function rig so default vfo = VFOA
Opened rig model 28001, 'PRM8060'
2021-01-12:18:59:26.738245: Backend version: 20101027.0, Status: Alpha
2021-01-12:18:59:26.739247: rigctl_parse: called, interactive=0
Command ' ' not found!
2021-01-12:18:59:26.741245: rigctl_parse: called, interactive=0
2021-01-12:18:59:26.742241: rig_close called
2021-01-12:18:59:26.743246: port_close called
2021-01-12:18:59:26.744246: ser_close called
2021-01-12:18:59:26.745244: ser_close: restoring options
2021-01-12:18:59:26.860740: rig_cleanup called

        the command "w Ew H" shows:

        Rig command: w Ew H
2021-01-12:19:04:37.006352: rigctl_parse: cmd=w(77)
2021-01-12:19:04:37.007351: rigctl_parse: cmd==0x77
2021-01-12:19:04:37.008352: rigctl_parse: vfo_opt=0
2021-01-12:19:04:37.009351: rigctl_parse: debug1
2021-01-12:19:04:37.010354: rigctl_parse: debug2
2021-01-12:19:04:37.010354: rigctl_parse: debug2a
2021-01-12:19:04:37.011353: rigctl_parse: debug5
2021-01-12:19:04:37.011353: rigctl_parse: debug10
2021-01-12:19:04:37.012353: rigctl_parse: vfo_opt=0
2021-01-12:19:04:37.012353: rigctl_send_cmd: called
2021-01-12:19:04:37.013350: rigctl_send_cmd: backend_num=28
2021-01-12:19:04:37.013350: rigctl_send_cmd: arg1=Ew H
2021-01-12:19:04:37.014353: rigctl_send_cmd: bufcmd=Ew H
2021-01-12:19:04:37.014353: rigctl_send_cmd: text protocol, send_cmd_term=0x0a 0x0d 0x0d
2021-01-12:19:04:37.015353: rig_flush: called for serial device
2021-01-12:19:04:37.015353: serial_flush called
2021-01-12:19:04:37.016356: tcflush
, cmd_len=519:04:37.017357: rigctl_send_cmd: rigport=1, bufcmd=Ew H
2021-01-12:19:04:37.017357: write_block called
2021-01-12:19:04:37.018353: write_block(): TX 5 bytes
2021-01-12:19:04:37.018353: 0000    45 77 20 48 0d                                      Ew H.
2021-01-12:19:04:37.019358: rigctl_send_cmd: debug Cmd
Reply: 2021-01-12:19:04:37.020375: read_string called, rxmax=513
2021-01-12:19:04:40.147610: read_string(): Timed out 3.126210 seconds after 0 chars
2021-01-12:19:04:40.147610: rigctl_send_cmd: read_string error Communication timed out
2021-01-12:19:04:40.148609: rigctl_parse: vfo_opt=0
2021-01-12:19:04:40.148609: rigctl_parse: retcode=0
2021-01-12:19:04:40.149611: rigctl_parse: called, interactive=1

        Do you know wheter I need a secial Firmware?

         

        • Michael Black

          Michael Black - 2021-01-12

          Run this...rigctl -m28001 -rCOM1 -s4800 -vvvvv -ZThen you'll get the "Rig command:" promptThen\get_info
          Thenw E
          Then w H
          Mike

          On Tuesday, January 12, 2021, 01:09:32 PM CST, RaspII <raspii@users.sourceforge.net> wrote:

          I had to add a blank between "-Z" and "\ get_info", else the command "rigctl -m28001 -rCOM1 -s4800 -vvvvv -Z\ get_info" ends up with an error message, only.
          Even with this blank the programm stops working but shows some information before
          My result:
          C:\Program Files (x86)\hamlib-w64-4.0\bin>rigctl -m28001 -rCOM1 -s4800 -vvvvv -Z \get_info
          2021-01-12:18:59:26.642239: rigctl Hamlib 4.0
          Last commit was Fri Dec 25 02:30:30 2020 +0000 SHA=519f82
          2021-01-12:18:59:26.643243: Report bugs to hamlib-developer@lists.sourceforge.net

          2021-01-12:18:59:26.643243: rig_init called
          2021-01-12:18:59:26.643243: initrigs4_prm80: _init called
          2021-01-12:18:59:26.644242: rig_register called
          2021-01-12:18:59:26.644242: rig_register: rig_register (28001)
          2021-01-12:18:59:26.644242: rig_open called
          2021-01-12:18:59:26.645239: port_open called
          2021-01-12:18:59:26.645239: serial_open called
          2021-01-12:18:59:26.680249: serial_setup called
          2021-01-12:18:59:26.680249: serial_setup: tcgetattr
          2021-01-12:18:59:26.680249: serial_setup: cfsetispeed=4800,0x000c
          2021-01-12:18:59:26.680249: serial_setup: cfsetospeed=4800,0x000c
          2021-01-12:18:59:26.681236: serial_setup: data_bits=7
          2021-01-12:18:59:26.681236: serial_setup: parity=4
          2021-01-12:18:59:26.681236: serial_setup: tcsetattr TCSANOW
          2021-01-12:18:59:26.682250: serial_flush called
          2021-01-12:18:59:26.682250: tcflush
          2021-01-12:18:59:26.734242: rig_get_vfo called
          2021-01-12:18:59:26.735243: rig_get_vfo: no get_vfo
          2021-01-12:18:59:26.735243: vfo_fixup: vfo=VFOA
          2021-01-12:18:59:26.736245: vfo_fixup: final vfo=VFOA
          2021-01-12:18:59:26.736245: rig_open: No set_vfo function rig so default vfo = VFOA
          Opened rig model 28001, 'PRM8060'
          2021-01-12:18:59:26.738245: Backend version: 20101027.0, Status: Alpha
          2021-01-12:18:59:26.739247: rigctl_parse: called, interactive=0
          Command ' ' not found!
          2021-01-12:18:59:26.741245: rigctl_parse: called, interactive=0
          2021-01-12:18:59:26.742241: rig_close called
          2021-01-12:18:59:26.743246: port_close called
          2021-01-12:18:59:26.744246: ser_close called
          2021-01-12:18:59:26.745244: ser_close: restoring options
          2021-01-12:18:59:26.860740: rig_cleanup called

          the command "w Ew H" shows:
          Rig command: w Ew H
          2021-01-12:19:04:37.006352: rigctl_parse: cmd=w(77)
          2021-01-12:19:04:37.007351: rigctl_parse: cmd==0x77
          2021-01-12:19:04:37.008352: rigctl_parse: vfo_opt=0
          2021-01-12:19:04:37.009351: rigctl_parse: debug1
          2021-01-12:19:04:37.010354: rigctl_parse: debug2
          2021-01-12:19:04:37.010354: rigctl_parse: debug2a
          2021-01-12:19:04:37.011353: rigctl_parse: debug5
          2021-01-12:19:04:37.011353: rigctl_parse: debug10
          2021-01-12:19:04:37.012353: rigctl_parse: vfo_opt=0
          2021-01-12:19:04:37.012353: rigctl_send_cmd: called
          2021-01-12:19:04:37.013350: rigctl_send_cmd: backend_num=28
          2021-01-12:19:04:37.013350: rigctl_send_cmd: arg1=Ew H
          2021-01-12:19:04:37.014353: rigctl_send_cmd: bufcmd=Ew H
          2021-01-12:19:04:37.014353: rigctl_send_cmd: text protocol, send_cmd_term=0x0a 0x0d 0x0d
          2021-01-12:19:04:37.015353: rig_flush: called for serial device
          2021-01-12:19:04:37.015353: serial_flush called
          2021-01-12:19:04:37.016356: tcflush
          , cmd_len=519:04:37.017357: rigctl_send_cmd: rigport=1, bufcmd=Ew H
          2021-01-12:19:04:37.017357: write_block called
          2021-01-12:19:04:37.018353: write_block(): TX 5 bytes
          2021-01-12:19:04:37.018353: 0000 45 77 20 48 0d Ew H.
          2021-01-12:19:04:37.019358: rigctl_send_cmd: debug Cmd
          Reply: 2021-01-12:19:04:37.020375: read_string called, rxmax=513
          2021-01-12:19:04:40.147610: read_string(): Timed out 3.126210 seconds after 0 chars
          2021-01-12:19:04:40.147610: rigctl_send_cmd: read_string error Communication timed out
          2021-01-12:19:04:40.148609: rigctl_parse: vfo_opt=0
          2021-01-12:19:04:40.148609: rigctl_parse: retcode=0
          2021-01-12:19:04:40.149611: rigctl_parse: called, interactive=1

          Do you know wheter I need a secial Firmware?

          PRM80xx can not connect to my PRM8020 and PRM8070

          Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/

          To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

           
          alternate

          • RaspII

            RaspII - 2021-01-12

            ok, result of "\get_info" is:

            Rig command: \get_info
2021-01-12:19:40:19.359242: rigctl_parse: cmd=\(5c)
2021-01-12:19:40:19.360236: rigctl_parse: cmd=get_info
2021-01-12:19:40:19.361237: rigctl_parse: vfo_opt=0
2021-01-12:19:40:19.361237: rigctl_parse: debug1
2021-01-12:19:40:19.362236: rigctl_parse: debug5
2021-01-12:19:40:19.363236: rigctl_parse: debug10
2021-01-12:19:40:19.364232: rigctl_parse: vfo_opt=0
2021-01-12:19:40:19.364858: rig_get_info called
2021-01-12:19:40:19.364858: rig_flush: called for serial device
2021-01-12:19:40:19.365872: serial_flush called
2021-01-12:19:40:19.365872: tcflush
2021-01-12:19:40:19.366870: write_block called
2021-01-12:19:40:19.367870: write_block(): TX 1 bytes
2021-01-12:19:40:19.367870: 0000    56                                                  V
2021-01-12:19:40:19.367870: read_string called, rxmax=64
             

            • Michael Black

              Michael Black - 2021-01-12

              There's nothing after that?
              Should at least be a timeout....

              On Tuesday, January 12, 2021, 01:44:13 PM CST, RaspII <raspii@users.sourceforge.net> wrote:

              ok, result of "\get_info" is:
              Rig command: \get_info
              2021-01-12:19:40:19.359242: rigctl_parse: cmd=(5c)
              2021-01-12:19:40:19.360236: rigctl_parse: cmd=get_info
              2021-01-12:19:40:19.361237: rigctl_parse: vfo_opt=0
              2021-01-12:19:40:19.361237: rigctl_parse: debug1
              2021-01-12:19:40:19.362236: rigctl_parse: debug5
              2021-01-12:19:40:19.363236: rigctl_parse: debug10
              2021-01-12:19:40:19.364232: rigctl_parse: vfo_opt=0
              2021-01-12:19:40:19.364858: rig_get_info called
              2021-01-12:19:40:19.364858: rig_flush: called for serial device
              2021-01-12:19:40:19.365872: serial_flush called
              2021-01-12:19:40:19.365872: tcflush
              2021-01-12:19:40:19.366870: write_block called
              2021-01-12:19:40:19.367870: write_block(): TX 1 bytes
              2021-01-12:19:40:19.367870: 0000 56 V
              2021-01-12:19:40:19.367870: read_string called, rxmax=64

              PRM80xx can not connect to my PRM8020 and PRM8070

              Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/

              To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

               
              alternate

              • RaspII

                RaspII - 2021-01-13

                Ok, you are right. I didn't wait long enough for the results. Sorry for that.
                Nevertheless, do you have an answer to my question whether I need a special firmware for my radio to communicate with Hamlib?
                Additional, is there a chance that you answer without quotation of the last messages (I'm always struggeling to find the most current comment :-)

                Here is the whole response, now:

                Rig command: \get_info
2021-01-13:10:23:01.994740: rigctl_parse: cmd=\(5c)
2021-01-13:10:23:01.995747: rigctl_parse: cmd=get_info
2021-01-13:10:23:01.996743: rigctl_parse: vfo_opt=0
2021-01-13:10:23:01.996743: rigctl_parse: debug1
2021-01-13:10:23:01.997745: rigctl_parse: debug5
2021-01-13:10:23:01.998742: rigctl_parse: debug10
2021-01-13:10:23:01.998742: rigctl_parse: vfo_opt=0
2021-01-13:10:23:01.999739: rig_get_info called
2021-01-13:10:23:01.999739: rig_flush: called for serial device
2021-01-13:10:23:02.000742: serial_flush called
2021-01-13:10:23:02.000742: tcflush
2021-01-13:10:23:02.001739: write_block called
2021-01-13:10:23:02.001995: write_block(): TX 1 bytes
2021-01-13:10:23:02.001995: 0000    56                                                  V
2021-01-13:10:23:05.139448: read_string(): Timed out 3.136438 seconds after 0 chars
2021-01-13:10:23:02.003010: read_string called, rxmax=64
Info:
2021-01-13:10:23:05.145552: rigctl_parse: vfo_opt=0
2021-01-13:10:23:05.146578: rigctl_parse: retcode=0
2021-01-13:10:23:05.147585: rigctl_parse: called, interactive=1

Rig command:
                 

                • Michael Black

                  Michael Black - 2021-01-13

                  So the rig is not talking at all.
                  How is your MAX232 powered?
                  You may need to add "--set-conf=rts_state=1" or "--set-conf=dtr_state=1".
                  The rig should respond to the "V" command to tell us the firmware version.  That command is in both V3.0 and V4.0 firmware
                  Once you have the "Rig command:" prompt you should also be able to get the list of available commands with this command:
                  Rig command: w H
                  What firmware version do you have?

                  Mike

                   
                  alternate

                  • RaspII

                    RaspII - 2021-01-13

                    Hello Mike,

                    do not know wheter I can answer directly via Mail.

                    Your question which FW I use seem to be related to my unanswered
                    question whether I can use the original Firmware or not.
                    If you talk about V3.0 or V4.0 I assume you are talking about this
                    Firmware, correct?
                    https://sourceforge.net/projects/prm80/files/prm80%20firmware

                    My prm8070 does not have a EPROM at all, that means I can not run
                    modified Firmware.

                    My 5V RS232 Interface runs well, because I have shorted the HW Handshake
                    signals in Hardware and tested this with the very old DOS Software (it
                    runs if signals are shorted, and runs not if not).
                    prm80hw.exe and prm80sw.exe.

                    Best Regards and thanks again.

                    Claus

                     

                    • Michael Black

                      Michael Black - 2021-01-13

                      Does the prm software do anything other than a memory dump?
                      Mike

                      On Wednesday, January 13, 2021, 07:48:26 AM CST, RaspII <raspii@users.sourceforge.net> wrote:

                      Hello Mike,

                      do not know wheter I can answer directly via Mail.

                      Your question which FW I use seem to be related to my unanswered
                      question whether I can use the original Firmware or not.
                      If you talk about V3.0 or V4.0 I assume you are talking about this
                      Firmware, correct?
                      https://sourceforge.net/projects/prm80/files/prm80%20firmware

                      My prm8070 does not have a EPROM at all, that means I can not run
                      modified Firmware.

                      My 5V RS232 Interface runs well, because I have shorted the HW Handshake
                      signals in Hardware and tested this with the very old DOS Software (it
                      runs if signals are shorted, and runs not if not).
                      prm80hw.exe and prm80sw.exe.

                      Best Regards and thanks again.

                      Claus

                      PRM80xx can not connect to my PRM8020 and PRM8070

                      Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/

                      To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

                       
                      alternate

                      • RaspII

                        RaspII - 2021-01-13

                        Yes, I can program the frequencies, set the power levels for each
                        channel, modify CTCSS and so on.
                        But afterwards I have to program this configuration to the EEPROM.
                        My idea was that I can set the frequency via PC online (directly while
                        using the radio), so that there is no need any more to preprogram the
                        memories.

                        Claus

                        Am 13.01.2021 um 17:05 schrieb Michael Black:

                        Does the prm software do anything other than a memory dump?
                        Mike

                         On Wednesday, January 13, 2021, 07:48:26 AM CST, RaspII <raspii@users.sourceforge.net> wrote:

                        Hello Mike,

                        do not know wheter I can answer directly via Mail.

                        Your question which FW I use seem to be related to my unanswered
                        question whether I can use the original Firmware or not.
                        If you talk about V3.0 or V4.0 I assume you are talking about this
                        Firmware, correct?
                        https://sourceforge.net/projects/prm80/files/prm80%20firmware

                        My prm8070 does not have a EPROM at all, that means I can not run
                        modified Firmware.

                        My 5V RS232 Interface runs well, because I have shorted the HW Handshake
                        signals in Hardware and tested this with the very old DOS Software (it
                        runs if signals are shorted, and runs not if not).
                        prm80hw.exe and prm80sw.exe.

                        Best Regards and thanks again.

                        Claus

                        PRM80xx can not connect to my PRM8020 and PRM8070

                        Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/

                        To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

                        PRM80xx can not connect to my PRM8020 and PRM8070

                        Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/

                        To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

                         

                        • Michael Black

                          Michael Black - 2021-01-13

                          Can you trace the serial i/o then when doing that?
                          Can you read the freq too?
                          Mike

                          On Wednesday, January 13, 2021, 12:59:07 PM CST, RaspII <raspii@users.sourceforge.net> wrote:

                          Yes, I can program the frequencies, set the power levels for each
                          channel, modify CTCSS and so on.
                          But afterwards I have to program this configuration to the EEPROM.
                          My idea was that I can set the frequency via PC online (directly while
                          using the radio), so that there is no need any more to preprogram the
                          memories.

                          Claus

                          Am 13.01.2021 um 17:05 schrieb Michael Black:

                          Does the prm software do anything other than a memory dump?
                          Mike
                          On Wednesday, January 13, 2021, 07:48:26 AM CST, RaspII raspii@users.sourceforge.net wrote:

                          Hello Mike,

                          do not know wheter I can answer directly via Mail.

                          Your question which FW I use seem to be related to my unanswered
                          question whether I can use the original Firmware or not.
                          If you talk about V3.0 or V4.0 I assume you are talking about this
                          Firmware, correct?
                          https://sourceforge.net/projects/prm80/files/prm80%20firmware

                          My prm8070 does not have a EPROM at all, that means I can not run
                          modified Firmware.

                          My 5V RS232 Interface runs well, because I have shorted the HW Handshake
                          signals in Hardware and tested this with the very old DOS Software (it
                          runs if signals are shorted, and runs not if not).
                          prm80hw.exe and prm80sw.exe.

                          Best Regards and thanks again.

                          Claus

                          PRM80xx can not connect to my PRM8020 and PRM8070

                          Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/

                          To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

                          PRM80xx can not connect to my PRM8020 and PRM8070

                          Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/

                          To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

                          PRM80xx can not connect to my PRM8020 and PRM8070

                          Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/

                          To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

                           
                          alternate

                          • RaspII

                            RaspII - 2021-01-13

                            I already did that some day's ago, see here:

                            https://sourceforge.net/p/hamlib/discussion/25919/thread/93afa09f52/#36fc

                            Claus

                             

                            • Michael Black

                              Michael Black - 2021-01-13

                              What application are you trying to do?

                              On Wednesday, January 13, 2021, 01:12:28 PM CST, RaspII <raspii@users.sourceforge.net> wrote:

                              I already did that some day's ago, see here:

                              https://sourceforge.net/p/hamlib/discussion/25919/thread/93afa09f52/#36fc

                              Claus

                              PRM80xx can not connect to my PRM8020 and PRM8070

                              Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/

                              To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

                               
                              alternate

                              • RaspII

                                RaspII - 2021-01-13

                                My trace was done while reading the EEPROM.

                                My idea was that I can modify the frequency of the radio directly from
                                PC while operating.

                                So I don't have to program the memories before scanning the frequencies.

                                My understanding is, that I can modify the frequencies with HAMLIB.

                                Claus

                                 

                                • Michael Black

                                  Michael Black - 2021-01-13

                                  Well we have to figure out how to set freq on the radio.
                                  So if you can trace a set freq and read freq operation that would be a start.
                                  Mike

                                  On Wednesday, January 13, 2021, 01:38:54 PM CST, RaspII <raspii@users.sourceforge.net> wrote:

                                  My trace was done while reading the EEPROM.

                                  My idea was that I can modify the frequency of the radio directly from
                                  PC while operating.

                                  So I don't have to program the memories before scanning the frequencies.

                                  My understanding is, that I can modify the frequencies with HAMLIB.

                                  Claus

                                  PRM80xx can not connect to my PRM8020 and PRM8070

                                  Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/

                                  To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

                                   
                                  alternate
1 2 3 4 > >> (Page 1 of 4)

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.