Menu

ft817 / ft857D cache invalid

2020-05-31
2020-06-02
  • Jan Bruggeman

    Jan Bruggeman - 2020-05-31

    Until a week ago I could talk to my ft817 and ft857D thru an USB interface III using rigctl. Now it's not working anymore.

    I use 2 setups, and both setups quit working (mobile: raspberry pi 1 -> USB Interface III (1) -> ft857 ; fixed: raspberry pi 2 -> USB Interface III (2) -> ft857) . I also use my laptop (Linux mint ) . The only thing that changed was a regular system update, but even if I start with an older kernel version on my laptop, the same thing happens.

    this is the output of rigctl for the ft817 (same happens with the ft857, indifferent of wether i use the raspberry's or my laptop)

    [jan@Asterix ~]$ rigctl -m 120 -r /dev/ttyUSB0 -vvvv
    rigctl, Hamlib 3.1
    Report bugs to hamlib-developer@...

    rig:rig_init called
    yaesu: initrigs3_yaesu called
    rig_register (121)
    rig_register (127)
    rig_register (110)
    rig_register (105)
    rig_register (106)
    rig_register (107)
    rig_register (109)
    rig_register (120)
    rig_register (101)
    rig_register (122)
    rig_register (123)
    rig_register (111)
    rig_register (115)
    rig_register (113)
    rig_register (114)
    rig_register (128)
    rig_register (131)
    rig_register (116)
    rig_register (103)
    rig_register (124)
    rig_register (104)
    rig_register (125)
    rig_register (129)
    rig_register (132)
    rig_register (130)
    rig_register (117)
    rig_register (119)
    rig_register (118)
    rig_register (126)
    rig_register (133)
    rig_register (134)
    rig_register (135)
    ft817: ft817_init called
    rig:rig_open called
    ft817: ft817_open called
    Opened rig model 120, 'FT-817'
    Backend version: 0.5.1, Status: Beta

    Rig command: 3
    rigctl_parse: input_line: 3
    rig_pathname: "Path name to the device file of the rig"
    Default: /dev/rig, Value: /dev/ttyUSB0
    String.
    write_delay: "Delay in ms between each byte sent out"
    Default: 0, Value: 0
    Range: 0.0..1000.0, step 1.0
    post_write_delay: "Delay in ms between each command sent out"
    Default: 0, Value: 0
    Range: 0.0..1000.0, step 1.0
    timeout: "Timeout in ms"
    Default: 0, Value: 200
    Range: 0.0..10000.0, step 1.0
    retry: "Max number of retry"
    Default: 0, Value: 0
    Range: 0.0..10.0, step 1.0
    itu_region: "ITU region this rig has been manufactured for (freq. band plan)"
    Default: 0, Value: 2
    Range: 1.0..3.0, step 1.0
    vfo_comp: "VFO compensation in ppm"
    Default: 0, Value: 0.000000
    Range: 0.0..1000.0, step 0.0
    poll_interval: "Polling interval in millisecond for transceive emulation"
    Default: 500, Value: 500
    Range: 0.0..1000000.0, step 1.0
    ptt_type: "Push-To-Talk interface type override"
    Default: RIG, Value: RIG
    Combo: RIG, DTR, RTS, Parallel, CM108, None
    ptt_pathname: "Path name to the device file of the Push-To-Talk"
    Default: /dev/rig, Value:
    String.
    ptt_bitnum: "Push-To-Talk GPIO bit number"
    Default: 2, Value: 0
    Range: 0.0..7.0, step 1.0
    dcd_type: "Data Carrier Detect (or squelch) interface type override"
    Default: RIG, Value: RIG
    Combo: RIG, DSR, CTS, CD, Parallel, CM108, None
    dcd_pathname: "Path name to the device file of the Data Carrier Detect (or squelch)"
    Default: /dev/rig, Value:
    String.
    serial_speed: "Serial port baud rate"
    Default: 0, Value: 38400
    Range: 300.0..115200.0, step 1.0
    data_bits: "Serial port data bits"
    Default: 8, Value: 8
    Range: 5.0..8.0, step 1.0
    stop_bits: "Serial port stop bits"
    Default: 1, Value: 2
    Range: 0.0..3.0, step 1.0
    serial_parity: "Serial port parity"
    Default: None, Value: None
    Combo: None, Odd, Even, Mark, Space
    serial_handshake: "Serial port handshake"
    Default: None, Value: None
    Combo: None, XONXOFF, Hardware
    rts_state: "Serial port set state of RTS signal for external powering"
    Default: Unset, Value: Unset
    Combo: Unset, ON, OFF
    dtr_state: "Serial port set state of DTR signal for external powering"
    Default: Unset, Value: Unset
    Combo: Unset, ON, OFF

    Rig command: f
    rigctl_parse: input_line: f
    ft817: cache invalid
    read_block(): Timed out 0.200337 seconds after 0 chars
    get_freq: error = Communication timed out

    Rig command: m
    rigctl_parse: input_line: m
    ft817: cache invalid
    read_block(): Timed out 0.200299 seconds after 0 chars
    get_mode: error = Communication timed out

    Rig command: q
    rig:rig_close called
    ft817: ft817_close called
    rig:rig_cleanup called
    ft817: ft817_cleanup called
    [jan@Asterix ~]$

     
  • Bill Somerville

    Bill Somerville - 2020-05-31

    Hi Jan,

    'cache invalid' is not an error message, it is just reporting that there is no cached data so it must red driectly from the rig, no surprise aboput that in the very first read. The real error is that you are getting "Communication timed out" that usually means that there is no data coming back from the rig when a query command is sent to it. Have you changed the baud rate of the rig's CAT port or maybe it is in ATU control mode rather than CAT mode? The problem lies in the interface between your rig and PC.

    73
    Bill
    G4WJS.

     
  • Jan Bruggeman

    Jan Bruggeman - 2020-06-01

    hamlib has no connection to my tranceiver because something is missing when I plugin the Microham USB Interface III. It is using ftdi for the usb/serial conversion to the rig, and ftdi drivers are loaded when I plugin the interface. However errors appear in /var/log/syslog:

    [jan@Asterix ~]$ sudo lsmod | grep ftdi
    ftdi_sio 53248 0
    usbserial 45056 1 ftdi_sio

    [jan@Asterix ~]$ sudo tail -20 /var/log/syslog
    Jun 1 20:50:38 Asterix kernel: [32069.252750] usbserial: USB Serial support registered for FTDI USB Serial Device
    Jun 1 20:50:38 Asterix kernel: [32069.253267] ftdi_sio 2-3.2:1.0: FTDI USB Serial Device converter detected
    Jun 1 20:50:38 Asterix kernel: [32069.253489] usb 2-3.2: Detected FT232RL
    Jun 1 20:50:38 Asterix kernel: [32069.254664] usb 2-3.2: FTDI USB Serial Device converter now attached to ttyUSB0
    Jun 1 20:50:38 Asterix upowerd[1913]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.2
    Jun 1 20:50:38 Asterix upowerd[1913]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.2/2-3.2:1.0
    Jun 1 20:50:38 Asterix kernel: [32069.451934] usb 2-3.1: new full-speed USB device number 7 using xhci_hcd
    Jun 1 20:50:38 Asterix kernel: [32069.534587] usb 2-3.1: New USB device found, idVendor=074d, idProduct=3503
    Jun 1 20:50:38 Asterix kernel: [32069.534595] usb 2-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    Jun 1 20:50:38 Asterix kernel: [32069.534598] usb 2-3.1: Product: USB Audio Codec
    Jun 1 20:50:38 Asterix kernel: [32069.534601] usb 2-3.1: Manufacturer: microHAM
    Jun 1 20:50:38 Asterix mtp-probe: checking bus 2, device 7: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.1"
    Jun 1 20:50:38 Asterix mtp-probe: bus: 2, device: 7 was not an MTP device
    Jun 1 20:50:38 Asterix kernel: [32069.653156] usbcore: registered new interface driver snd-usb-audio
    Jun 1 20:50:38 Asterix upowerd[1913]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.1
    Jun 1 20:50:38 Asterix upowerd[1913]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.1/2-3.1:1.2
    Jun 1 20:50:38 Asterix upowerd[1913]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.1/2-3.1:1.1
    Jun 1 20:50:38 Asterix systemd-udevd[16051]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 2' failed with exit code 99.
    Jun 1 20:50:38 Asterix upowerd[1913]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.1/2-3.1:1.0
    Jun 1 20:50:40 Asterix ModemManager[967]: <info> Couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.2': not supported by any plugin</info>

    This behaviour only exists since I've upgraded all my computers (linux mint / raspberry)
    there are errors mentioning alsa in the log, however, the soundcard does work as I can decode signals in fldigi. Only rig control (both flrig and rigctl) do not work.

    still looking for idea's ...

     
  • Jan Bruggeman

    Jan Bruggeman - 2020-06-02

    Thanks for reply's but a complete reinstall and use of stronger power supply did the trick. The upgrade had done something nasty to the USB/serial setup.

     

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.