Synology fails to see RFLink as a serial port

[david128]

I've had an RFLink arduino mega connected to my DS216j for several years, using Domoticz
I've recently updated both the DSM on the Synology NAS (DSM 6.2.4-25556 Update 7) and Domoticz (2020.2-10), and the connection to RFLink is now not working
I've run RFLink loader with the rflink device on my pc, and it's working fine (receiving my temp sensors), so it's not the RFLink device
So,
Domoticz reports Error: RFLink: Error opening serial port!

In Domoticz:hardware, the setup for RFLink doesn't show any serial port for selection - so I don't believe it's Domoticz thats the problem - I suspect that a 'correct' serial port isn't being created for the RFLink by the Synology NAS

DSM info center shows the RFLink as HL-340 USB-Serial adapter - QinHeng Electronics

lsusb gives the following....

lsusb
|__usb1 1d6b0310 09 2.00 480MBit/s 0mA 1IF (Linux 3.10.105 xhci-hcd xHCI Host Controller f10f0000.usb3) hub
|__1-1 1a86:7523:0254 ff 1.10 12MBit/s 96mA 1IF ( d8b9d0a2c794b989a795d784d1)
|__usb2 1d6b0310 09 3.00 5000MBit/s 0mA 1IF (Linux 3.10.105 xhci-hcd xHCI Host Controller f10f0000.usb3) hub
|__usb3 1d6b0310 09 2.00 480MBit/s 0mA 1IF (Linux 3.10.105 xhci-hcd xHCI Host Controller f10f8000.usb3) hub
|__3-1 10580106 00 2.00 480MBit/s 2mA 1IF (Western Digital External HDD 574341505733373836343634)
|__usb4 1d6b0310 09 3.00 5000MBit/s 0mA 1IF (Linux 3.10.105 xhci-hcd xHCI Host Controller f10f8000.usb3) hub
|__usb5 1d6b0310 09 2.00 480MBit/s 0mA 1IF (ehci_hcd f1058000.usb) hub
( Note I have a USB WD HDD drive connected as well)

I'm thinking its the synology NAS that not really recognising the RFLink as a serial port, and not creating a tty device for it - despite what the info center says

Question is - what would you expect to see, and is there a known issue with DSM 6.2.4 that doesn't recognise RFLink?
I hope you can offer some suggestion on how to progress this


I've also tried more commands (below) which don't appear to show the RFlink being recognised
the last one, dmesg, looks to me like the USB connection to usb1-1 (RFLink I believe) is disconnected for some reason

ll /sys/class/tty
total 0
drwxr-xr-x 2 root root 0 May 17 19:31 .
drwxr-xr-x 37 root root 0 May 16 22:09 ..
lrwxrwxrwx 1 root root 0 May 17 19:31 console -> ../../devices/virtual/tty/console
lrwxrwxrwx 1 root root 0 May 17 19:31 ptmx -> ../../devices/virtual/tty/ptmx
lrwxrwxrwx 1 root root 0 May 17 19:31 tty -> ../../devices/virtual/tty/tty
lrwxrwxrwx 1 root root 0 May 17 19:31 ttyS0 -> ../../devices/soc.0/internal-regs.1/f1012000.serial/tty/ttyS0
lrwxrwxrwx 1 root root 0 May 17 19:31 ttyS1 -> ../../devices/soc.0/internal-regs.1/f1012100.serial/tty/ttyS1
lrwxrwxrwx 1 root root 0 May 17 19:31 ttyS2 -> ../../devices/platform/serial8250/tty/ttyS2
lrwxrwxrwx 1 root root 0 May 17 19:31 ttyS3 -> ../../devices/platform/serial8250/tty/ttyS3


dmesg | grep tty
[ 0.000000] Kernel command line: console=ttyS0,115200 ip=off initrd=0x3000000 root=/dev/md0 rw syno_hw_version=DS216j hd_power_on_seq=2 ihd_num=2 netif_num=1 syno_hdd_enable=15,16 flash_size=8
[ 3.548199] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 44) is a 16550A
[ 4.357721] console [ttyS0] enabled
[ 4.381893] f1012100.serial: ttyS1 at MMIO 0xf1012100 (irq = 45) is a 16550A
[ 31.655031] synobios open /dev/ttyS1 success
[ 59.592209] synobios open /dev/ttyS1 success
[ 60.529565] synobios open /dev/ttyS1 success


cat /proc/tty/drivers
/dev/tty /dev/tty 5 0 system:/dev/tty
/dev/console /dev/console 5 1 system:console
/dev/ptmx /dev/ptmx 5 2 system
serial /dev/ttyS 4 64-67 serial
pty_slave /dev/pts 136 0-1048575 pty:slave
pty_master /dev/ptm 128 0-1048575 pty:master



dmesg | grep usb
[ 31.046687] usbcore: registered new interface driver usbfs
[ 31.055413] usbcore: registered new interface driver hub
[ 31.063509] usbcore: registered new device driver usb
[ 31.186932] xhci-hcd f10f0000.usb3: USB2 Vbus gpio 58
[ 31.192020] xhci-hcd f10f0000.usb3: power control enabled
[ 31.197482] xhci-hcd f10f0000.usb3: xHCI Host Controller
[ 31.202834] xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 1
[ 31.210658] xhci-hcd f10f0000.usb3: irq 48, io mem 0xf10f0000
[ 31.225290] xhci-hcd f10f0000.usb3: USB3 Vbus gpio 58
[ 31.230374] xhci-hcd f10f0000.usb3: power control enabled
[ 31.235833] xhci-hcd f10f0000.usb3: xHCI Host Controller
[ 31.241187] xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 2
[ 31.260236] xhci-hcd f10f8000.usb3: USB2 Vbus gpio 59
[ 31.265344] xhci-hcd f10f8000.usb3: power control enabled
[ 31.270780] xhci-hcd f10f8000.usb3: xHCI Host Controller
[ 31.276167] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 3
[ 31.286406] xhci-hcd f10f8000.usb3: irq 49, io mem 0xf10f8000
[ 31.317598] xhci-hcd f10f8000.usb3: USB3 Vbus gpio 59
[ 31.322686] xhci-hcd f10f8000.usb3: power control enabled
[ 31.328167] xhci-hcd f10f8000.usb3: xHCI Host Controller
[ 31.333536] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 4
[ 31.454433] orion-ehci f1058000.usb: failed to get Vbus gpio
[ 31.460137] orion-ehci f1058000.usb: USB2 Vbus gpio -1
[ 31.465325] orion-ehci f1058000.usb: power control disabled
[ 31.470923] orion-ehci f1058000.usb: EHCI Host Controller
[ 31.476370] orion-ehci f1058000.usb: new USB bus registered, assigned bus number 5
[ 31.484068] orion-ehci f1058000.usb: irq 50, io mem 0xf1058000
[ 31.503049] orion-ehci f1058000.usb: USB 2.0 started, EHCI 1.00
[ 32.593050] usb 1-1: new full-speed USB device number 2 using xhci-hcd
[ 33.783054] usb 3-1: new high-speed USB device number 2 using xhci-hcd
[ 83.025008] usb-storage 3-1:1.0: USB Mass Storage device detected
[ 83.063244] scsi2 : usb-storage 3-1:1.0
[ 83.067343] usbcore: registered new interface driver usb-storage
[ 83.341386] usbcore: registered new interface driver usblp
[ 83.594082] usbcore: registered new interface driver usbhid
[ 83.599683] usbhid: USB HID core driver
[67254.386858] usb 1-1: USB disconnect, device number 2
[69846.643081] usb 1-1: new full-speed USB device number 3 using xhci-hcd

[david128]

Ok, it appears it's down to the Synology NAS not having the matching serial drivers (and the community Domoticz package doesn't install them), so not an RFLink issue
It appears the original Jahald domoticz build I used did contain the right drivers, but when I updated to the 'community' Domoticz install, this doesn't have the drivers, and so the RFLink stopped working

[m_ny]

Would you be able to help a noob? I have the rflink. I tried to get the USB drivers installed via the web archive, but I might have missed a step. I have a DS215j which is an Armada375.

Thank you.

[david128]

Ok, managed to find my copy of the Jadahl build of Domoticz I was using before my upgrade attempt, so uninstalled the community version, installed this version, and extracted the usb_serial drivers from that.
Then uninstalled this version (the community version won't install over the Jadahl version - complains of port still in use), and re-installed the community version.
Then manually installed the drivers - it's now working!

The install is as follows..

Copy the files to your Synology using winscp or another suitable program. The files must be copied to / lib / modules
Here you will also find the other driver files.
Then type:

Code: Select all

  sudo insmod /lib/modules/usbserial.ko
  sudo insmod /lib/modules/ftdi_sio.ko
  sudo insmod /lib/modules/cp210x.ko
  ... (any other drivers you have/need)

to activate the files.

--- NOTE: you must install usbserial.ko before installing others, otherwise they will fail to install

Would you be able to help a noob? I have the rflink. I tried to get the USB drivers installed via the web archive, but I might have missed a step. I have a DS215j which is an Armada375.

I hope that answers your question