lost serial gateway after un plug power Rpi



  • hi guys
    after un plug raspberry pi and plug in power again , my serial gateway (mysensors) is lost , so i must disconnect USB cable (serial gateway) and connect again every time. . . !!!
    where problem !?

    0_1474810074123_ksksk.jpg



  • anybody test this issue !? and have same problem !



  • I have this exact problem. I have 2 gateways, a moteino USB for RFM69 radios and a nano for an NRF24 radios.
    Domoticz running on a raspberry pi.
    If I reboot the pi, or power down and restart, the moteino connects back up automatically.
    For the nano, I have to unplug and reconnect it after the pi has booted up, or it won't be detected.


  • Admin

    I have never experienced this. I'm using a nano with nrf24.

    Could be a hardware issue with your arduino.



  • i think that this problem is related to startup . when plug in power (rasspberry pi ) , the serial gateway is faster to startup than rasspberry. so when raspberry pi is startup dont detect serial gateway !!! are there any ways for this ? for example a delay for turn on gateway or startup until first raspberry pi started!


  • Hero Member

    The possible cause is that the Raspberry-Pi has no consistency in assigning USB port numbers. This occurs mainly when you have more than 1 USB port in use. Read for a solution..
    Btw I never experienced it running 3 PI's with each a serial gateway.



  • @AWI
    i test this but dont work.
    0_1474891685019_Untitledksks.jpg


  • Hero Member

    @Reza What does not work?



  • @AWI

    after turn off Rpi ,lost serial gateway yet


  • Hero Member

    @Reza Do you reboot or just unplug the PI? You can also try to enable the "Data Timeout" in Domoticz, that way it searches actively when not found in first instance



  • @AWI

    first i reboot and lost serial. i test once unplug. in both serial gateway is lost... data timeout must disable !!!!


  • Hero Member

    @Reza said:

    data timeout must disable !

    Whatever 😕

    If you are using a good quality Nano with default sketch I am out of options.




  • Hero Member



  • @AWI
    🙂
    I'm tired for this problem 😕
    thank you



  • i think if Rpi gateway complete and test... this is can resolved this problem ! is that correct? so i must wait...


  • Admin

    @Reza

    I assume that you have tried to look at lsusb, dmesg, and /dev population, when the device is not turning up in Domoticz?

    Does any of those indicate something bad / interesting?



  • @tbowmo
    I can not understand what you mean !!!
    but after all my try , after reset (Rpi) or turn off .... my serial gateway is lost and i must unplug usb cable and plug in again.


  • Admin

    after you have powered on your raspberry, you log in

    then at the command prompt you type:

    lsusb

    -> provide the output

    unplug / plug the usb device

    once more in your terminal
    lsusb
    -> provide output

    the same for dmesg. In a terminal type "dmesg" hit return, and provide the output, both before you unplug a device that is not working, and after you have done it, and it is working.



  • @tbowmo 0_1474903726513_12.jpg

    "the same for dmesg. In a terminal type "dmesg" hit return, and provide the output, both before you unplug a device that is not working, and after you have done it, and it is working."

    for this , what am i do ?



  • @tbowmo

    after power off (rpi)

    
    pi@raspberrypi:~$ dmesg
    [    0.000000] Booting Linux on physical CPU 0x0
    [    0.000000] Initializing cgroup subsys cpuset
    [    0.000000] Initializing cgroup subsys cpu
    [    0.000000] Initializing cgroup subsys cpuacct
    [    0.000000] Linux version 4.1.18-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3                               (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #846 SMP Thu Feb 25 14:22:53 GM                              T 2016
    [    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
    [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instructio                              n cache
    [    0.000000] Machine model: Raspberry Pi 3 Model B Rev 1.2
    [    0.000000] cma: Reserved 8 MiB at 0x3a400000
    [    0.000000] Memory policy: Data cache writealloc
    [    0.000000] On node 0 totalpages: 241664
    [    0.000000] free_area_init_node: node 0, pgdat 80876f80, node_mem_map b9bb400                              0
    [    0.000000]   Normal zone: 2124 pages used for memmap
    [    0.000000]   Normal zone: 0 pages reserved
    [    0.000000]   Normal zone: 241664 pages, LIFO batch:31
    [    0.000000] [bcm2709_smp_init_cpus] enter (9420->f3003010)
    [    0.000000] [bcm2709_smp_init_cpus] ncores=4
    [    0.000000] PERCPU: Embedded 12 pages/cpu @bafb0000 s20416 r8192 d20544 u4915                              2
    [    0.000000] pcpu-alloc: s20416 r8192 d20544 u49152 alloc=12*4096
    [    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
    [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pag                              es: 239540
    [    0.000000] Kernel command line: 8250.nr_uarts=1 dma.dmachans=0x7f35 bcm2708_                              fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa02082 bcm2709.serial=                              0xd2e92fc7 smsc95xx.macaddr=B8:27:EB:E9:2F:C7 bcm2708_fb.fbswap=1 bcm2709.uart_c                              lock=48000000 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000  dwc_otg.lpm                              _enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsc                              k.repair=yes rootwait
    [    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
    [    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
    [    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
    [    0.000000] Memory: 939416K/966656K available (6024K kernel code, 534K rwdata                              , 1660K rodata, 448K init, 757K bss, 19048K reserved, 8192K cma-reserved)
    [    0.000000] Virtual kernel memory layout:
        vector  : 0xffff0000 - 0xffff1000   (   4 kB)
        fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
        vmalloc : 0xbb800000 - 0xff000000   (1080 MB)
        lowmem  : 0x80000000 - 0xbb000000   ( 944 MB)
        modules : 0x7f000000 - 0x80000000   (  16 MB)
          .text : 0x80008000 - 0x807895a0   (7686 kB)
          .init : 0x8078a000 - 0x807fa000   ( 448 kB)
          .data : 0x807fa000 - 0x8087fac0   ( 535 kB)
           .bss : 0x80882000 - 0x8093f79c   ( 758 kB)
    [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
    [    0.000000] Hierarchical RCU implementation.
    [    0.000000]  Additional per-CPU info printed with stalls.
    [    0.000000] NR_IRQS:608
    [    0.000000] Architected cp15 timer(s) running at 19.20MHz (phys).
    [    0.000000] clocksource arch_sys_counter: mask: 0xffffffffffffff max_cycles:                               0x46d987e47, max_idle_ns: 440795202767 ns
    [    0.000008] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 43980                              46511078ns
    [    0.000026] Switching to timer-based delay loop, resolution 52ns
    [    0.000243] Console: colour dummy device 80x30
    [    0.001283] console [tty1] enabled
    [    0.001335] Calibrating delay loop (skipped), value calculated using timer fr                              equency.. 38.40 BogoMIPS (lpj=192000)
    [    0.001402] pid_max: default: 32768 minimum: 301
    [    0.001719] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
    [    0.001763] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
    [    0.002757] Initializing cgroup subsys blkio
    [    0.002806] Initializing cgroup subsys memory
    [    0.002855] Initializing cgroup subsys devices
    [    0.002897] Initializing cgroup subsys freezer
    [    0.002946] Initializing cgroup subsys net_cls
    [    0.003016] CPU: Testing write buffer coherency: ok
    [    0.003103] ftrace: allocating 20309 entries in 60 pages
    [    0.048770] CPU0: update cpu_capacity 1024
    [    0.048834] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
    [    0.048867] [bcm2709_smp_prepare_cpus] enter
    [    0.049017] Setting up static identity map for 0x8240 - 0x8274
    [    0.050796] [bcm2709_boot_secondary] cpu:1 started (0) 17
    [    0.051117] [bcm2709_secondary_init] enter cpu:1
    [    0.051161] CPU1: update cpu_capacity 1024
    [    0.051167] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
    [    0.051541] [bcm2709_boot_secondary] cpu:2 started (0) 17
    [    0.051797] [bcm2709_secondary_init] enter cpu:2
    [    0.051818] CPU2: update cpu_capacity 1024
    [    0.051824] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
    [    0.052179] [bcm2709_boot_secondary] cpu:3 started (0) 17
    [    0.052363] [bcm2709_secondary_init] enter cpu:3
    [    0.052384] CPU3: update cpu_capacity 1024
    [    0.052390] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
    [    0.052452] Brought up 4 CPUs
    [    0.052550] SMP: Total of 4 processors activated (153.60 BogoMIPS).
    [    0.052579] CPU: All CPU(s) started in HYP mode.
    [    0.052605] CPU: Virtualization extensions available.
    [    0.053299] devtmpfs: initialized
    [    0.071496] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3                               rev 4
    [    0.071761] clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max                              _idle_ns: 19112604462750000 ns
    [    0.072612] pinctrl core: initialized pinctrl subsystem
    [    0.073157] NET: Registered protocol family 16
    [    0.078246] DMA: preallocated 4096 KiB pool for atomic coherent allocations
    [    0.079185] bcm2709.uart_clock = 48000000
    [    0.083230] bcm2709: Mini UART enabled
    [    0.083298] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint                               registers.
    [    0.083345] hw-breakpoint: maximum watchpoint size is 8 bytes.
    [    0.083515] Serial: AMBA PL011 UART driver
    [    0.083660] 3f201000.uart: ttyAMA0 at MMIO 0x3f201000 (irq = 83, base_baud =                               0) is a PL011 rev2
    [    0.084082] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
    [    0.149475] bcm2708-dmaengine 3f007000.dma: DMA legacy API manager at f300700                              0, dmachans=0xf35
    [    0.149545] bcm2708-dmaengine 3f007000.dma: Initialized 7 DMA channels (+ 1 l                              egacy)
    [    0.150132] bcm2708-dmaengine 3f007000.dma: Load BCM2835 DMA engine driver
    [    0.150169] bcm2708-dmaengine 3f007000.dma: dma_debug:0
    [    0.150736] SCSI subsystem initialized
    [    0.150942] usbcore: registered new interface driver usbfs
    [    0.151048] usbcore: registered new interface driver hub
    [    0.151165] usbcore: registered new device driver usb
    [    0.151700] raspberrypi-firmware soc:firmware: Attached to firmware from 2016                              -02-25 14:25
    [    0.178766] Switched to clocksource arch_sys_counter
    [    0.220329] FS-Cache: Loaded
    [    0.220609] CacheFiles: Loaded
    [    0.229845] NET: Registered protocol family 2
    [    0.230805] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
    [    0.230946] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
    [    0.231157] TCP: Hash tables configured (established 8192 bind 8192)
    [    0.231269] UDP hash table entries: 512 (order: 2, 16384 bytes)
    [    0.231338] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
    [    0.231662] NET: Registered protocol family 1
    [    0.231982] RPC: Registered named UNIX socket transport module.
    [    0.232014] RPC: Registered udp transport module.
    [    0.232042] RPC: Registered tcp transport module.
    [    0.232070] RPC: Registered tcp NFSv4.1 backchannel transport module.
    [    0.232996] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counter                              s available
    [    0.234075] futex hash table entries: 1024 (order: 4, 65536 bytes)
    [    0.247434] VFS: Disk quotas dquot_6.6.0
    [    0.247761] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    [    0.249874] FS-Cache: Netfs 'nfs' registered for caching
    [    0.250795] NFS: Registering the id_resolver key type
    [    0.250867] Key type id_resolver registered
    [    0.250896] Key type id_legacy registered
    [    0.252948] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 2                              52)
    [    0.253120] io scheduler noop registered
    [    0.253159] io scheduler deadline registered (default)
    [    0.253460] io scheduler cfq registered
    [    0.255711] BCM2708FB: allocated DMA memory fa800000
    [    0.255757] BCM2708FB: allocated DMA channel 0 @ f3007000
    [    0.260734] Console: switching to colour frame buffer device 82x26
    [    0.265080] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
    [    0.270218] 3f215040.uart: ttyS0 at MMIO 0x3f215040 (irq = 29, base_baud = 50                              000000) is a 16550
    [    0.273978] vc-cma: Videocore CMA driver
    [    0.275426] vc-cma: vc_cma_base      = 0x00000000
    [    0.276825] vc-cma: vc_cma_size      = 0x00000000 (0 MiB)
    [    0.278175] vc-cma: vc_cma_initial   = 0x00000000 (0 MiB)
    [    0.279717] vc-mem: phys_addr:0x00000000 mem_base=0x3dc00000 mem_size:0x3f000                              000(1008 MiB)
    [    0.293674] brd: module loaded
    [    0.301959] loop: module loaded
    [    0.304024] vchiq: vchiq_init_state: slot_zero = 0xba880000, is_master = 0
    [    0.306821] Loading iSCSI transport class v2.0-870.
    [    0.308864] usbcore: registered new interface driver smsc95xx
    [    0.310204] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
    [    0.511798] Core Release: 2.80a
    [    0.513109] Setting default values for core params
    [    0.514466] Finished setting default values for core params
    [    0.716148] Using Buffer DMA mode
    [    0.717508] Periodic Transfer Interrupt Enhancement - disabled
    [    0.718907] Multiprocessor Interrupt Enhancement - disabled
    [    0.720281] OTG VER PARAM: 0, OTG VER FLAG: 0
    [    0.721617] Dedicated Tx FIFOs mode
    [    0.723166] WARN::dwc_otg_hcd_init:1047: FIQ DMA bounce buffers: virt = 0xba8                              14000 dma = 0xfa814000 len=9024
    [    0.725878] FIQ FSM acceleration enabled for :
    Non-periodic Split Transactions
    Periodic Split Transactions
    High-Speed Isochronous Endpoints
    [    0.731405] dwc_otg: Microframe scheduler enabled
    [    0.731452] WARN::hcd_init_fiq:412: FIQ on core 1 at 0x8040ecc0
    [    0.732841] WARN::hcd_init_fiq:413: FIQ ASM at 0x8040f030 length 36
    [    0.734244] WARN::hcd_init_fiq:438: MPHI regs_base at 0xbb89c000
    [    0.735630] dwc_otg 3f980000.usb: DWC OTG Controller
    [    0.736993] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number                               1
    [    0.738381] dwc_otg 3f980000.usb: irq 32, io mem 0x00000000
    [    0.739780] Init: Port Power? op_state=1
    [    0.741091] Init: Power Port (0)
    [    0.742548] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
    [    0.743903] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=                              1
    [    0.745248] usb usb1: Product: DWC OTG Controller
    [    0.746564] usb usb1: Manufacturer: Linux 4.1.18-v7+ dwc_otg_hcd
    [    0.747890] usb usb1: SerialNumber: 3f980000.usb
    [    0.749849] hub 1-0:1.0: USB hub found
    [    0.751175] hub 1-0:1.0: 1 port detected
    [    0.752770] dwc_otg: FIQ enabled
    [    0.752779] dwc_otg: NAK holdoff enabled
    [    0.752787] dwc_otg: FIQ split-transaction FSM enabled
    [    0.752817] Module dwc_common_port init
    [    0.753084] usbcore: registered new interface driver usb-storage
    [    0.754495] mousedev: PS/2 mouse device common for all mice
    [    0.756379] bcm2835-cpufreq: min=600000 max=1200000
    [    0.757894] sdhci: Secure Digital Host Controller Interface driver
    [    0.759214] sdhci: Copyright(c) Pierre Ossman
    [    0.760790] sdhost: log_buf @ ba813000 (fa813000)
    [    0.838802] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
    [    0.862571] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
    [    0.863912] mmc-bcm2835 3f300000.mmc: DMA channels allocated
    [    0.898871] sdhci-pltfm: SDHCI platform and OF driver helper
    [    0.899905] mmc0: host does not support reading read-only switch, assuming wr                              ite-enable
    [    0.902796] mmc0: new high speed SDHC card at address 0001
    [    0.903125] ledtrig-cpu: registered to indicate activity on CPUs
    [    0.903251] hidraw: raw HID events driver (C) Jiri Kosina
    [    0.903437] usbcore: registered new interface driver usbhid
    [    0.903439] usbhid: USB HID core driver
    [    0.903843] Initializing XFRM netlink socket
    [    0.903867] NET: Registered protocol family 17
    [    0.903975] Key type dns_resolver registered
    [    0.904375] Registering SWP/SWPB emulation handler
    [    0.905035] registered taskstats version 1
    [    0.905217] vc-sm: Videocore shared memory driver
    [    0.905226] [vc_sm_connected_init]: start
    [    0.905858] [vc_sm_connected_init]: end - returning 0
    [    0.920575] Waiting for root device /dev/mmcblk0p2...
    [    0.921960] mmcblk0: mmc0:0001 ASTC 7.49 GiB
    [    0.925258]  mmcblk0: p1 p2
    [    0.944235] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
    [    0.947068] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
    [    0.949872] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
    [    0.953839] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
    [    0.968856] Indeed it is in host mode hprt0 = 00021501
    [    1.045676] mmc1: new high speed SDIO card at address 0001
    [    1.049593] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. O                              pts: (null)
    [    1.051801] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
    [    1.071212] devtmpfs: mounted
    [    1.073080] Freeing unused kernel memory: 448K (8078a000 - 807fa000)
    [    1.148811] usb 1-1: new high-speed USB device number 2 using dwc_otg
    [    1.150223] Indeed it is in host mode hprt0 = 00001101
    [    1.349115] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
    [    1.350489] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    [    1.352527] hub 1-1:1.0: USB hub found
    [    1.353956] hub 1-1:1.0: 5 ports detected
    [    1.588465] random: systemd urandom read with 67 bits of entropy available
    [    1.594185] systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SEL                              INUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
    [    1.597377] systemd[1]: Detected architecture 'arm'.
    [    1.628809] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
    [    1.729087] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
    [    1.730789] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber                              =0
    [    1.735270] smsc95xx v1.0.4
    [    1.745950] NET: Registered protocol family 10
    [    1.748688] systemd[1]: Inserted module 'ipv6'
    [    1.755788] systemd[1]: Set hostname to <raspberrypi>.
    [    1.792046] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-                              1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:e9:2f:c7
    [    1.888865] usb 1-1.5: new full-speed USB device number 4 using dwc_otg
    [    1.968813] usb 1-1.5: device descriptor read/64, error -32
    [    2.158838] usb 1-1.5: device descriptor read/64, error -32
    [    2.348821] usb 1-1.5: new full-speed USB device number 5 using dwc_otg
    [    2.428821] usb 1-1.5: device descriptor read/64, error -32
    [    2.460547] systemd[1]: Cannot add dependency job for unit display-manager.se                              rvice, ignoring: Unit display-manager.service failed to load: No such file or di                              rectory.
    [    2.467973] systemd[1]: Starting Forward Password Requests to Wall Directory                               Watch.
    [    2.471355] systemd[1]: Started Forward Password Requests to Wall Directory W                              atch.
    [    2.474592] systemd[1]: Starting Remote File Systems (Pre).
    [    2.478343] systemd[1]: Reached target Remote File Systems (Pre).
    [    2.480117] systemd[1]: Starting Encrypted Volumes.
    [    2.483719] systemd[1]: Reached target Encrypted Volumes.
    [    2.485531] systemd[1]: Starting Arbitrary Executable File Formats File Syste                              m Automount Point.
    [    2.491276] systemd[1]: Set up automount Arbitrary Executable File Formats Fi                              le System Automount Point.
    [    2.494817] systemd[1]: Starting Swap.
    [    2.498623] systemd[1]: Reached target Swap.
    [    2.500437] systemd[1]: Expecting device dev-mmcblk0p1.device...
    [    2.504101] systemd[1]: Starting Root Slice.
    [    2.507679] systemd[1]: Created slice Root Slice.
    [    2.509328] systemd[1]: Starting User and Session Slice.
    [    2.512813] systemd[1]: Created slice User and Session Slice.
    [    2.514394] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
    [    2.517880] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
    [    2.519535] systemd[1]: Starting Delayed Shutdown Socket.
    [    2.523022] systemd[1]: Listening on Delayed Shutdown Socket.
    [    2.524617] systemd[1]: Starting Journal Socket (/dev/log).
    [    2.527987] systemd[1]: Listening on Journal Socket (/dev/log).
    [    2.529550] systemd[1]: Starting udev Control Socket.
    [    2.532835] systemd[1]: Listening on udev Control Socket.
    [    2.534388] systemd[1]: Starting udev Kernel Socket.
    [    2.537650] systemd[1]: Listening on udev Kernel Socket.
    [    2.539289] systemd[1]: Starting Journal Socket.
    [    2.542761] systemd[1]: Listening on Journal Socket.
    [    2.544384] systemd[1]: Starting System Slice.
    [    2.547719] systemd[1]: Created slice System Slice.
    [    2.549299] systemd[1]: Starting File System Check on Root Device...
    [    2.554613] systemd[1]: Starting system-systemd\x2dfsck.slice.
    [    2.558396] systemd[1]: Created slice system-systemd\x2dfsck.slice.
    [    2.560159] systemd[1]: Starting system-getty.slice.
    [    2.563701] systemd[1]: Created slice system-getty.slice.
    [    2.565277] systemd[1]: Starting Increase datagram queue length...
    [    2.571112] systemd[1]: Starting Restore / save the current clock...
    [    2.586219] systemd[1]: Starting udev Coldplug all Devices...
    [    2.618179] systemd[1]: Started Set Up Additional Binary Formats.
    [    2.618832] usb 1-1.5: device descriptor read/64, error -32
    [    2.688814] systemd[1]: Starting Load Kernel Modules...
    [    2.698660] systemd[1]: Mounting POSIX Message Queue File System...
    [    2.704893] systemd[1]: Mounting Debug File System...
    [    2.711134] systemd[1]: Mounted Huge Pages File System.
    [    2.713598] systemd[1]: Starting Create list of required static device nodes                               for the current kernel...
    [    2.723719] systemd[1]: Starting Slices.
    [    2.727641] systemd[1]: Reached target Slices.
    [    2.769467] systemd[1]: Mounted POSIX Message Queue File System.
    [    2.774363] systemd[1]: Mounted Debug File System.
    [    2.780105] systemd[1]: Started Increase datagram queue length.
    [    2.818840] usb 1-1.5: new full-speed USB device number 6 using dwc_otg
    [    2.822486] systemd[1]: Started Create list of required static device nodes f                              or the current kernel.
    [    2.831991] systemd[1]: Started udev Coldplug all Devices.
    [    2.909077] systemd[1]: Started Restore / save the current clock.
    [    2.918673] systemd[1]: Time has been changed
    [    2.925513] i2c /dev entries driver
    [    2.949725] systemd[1]: Starting Create Static Device Nodes in /dev...
    [    2.953159] Driver for 1-wire Dallas network protocol.
    [    2.955976] systemd[1]: Starting Syslog Socket.
    [    2.960058] systemd[1]: Listening on Syslog Socket.
    [    2.961827] systemd[1]: Starting Journal Service...
    [    2.969730] systemd[1]: Started Journal Service.
    [    3.233621] systemd-udevd[109]: starting version 215
    [    3.238870] usb 1-1.5: device not accepting address 6, error -32
    [    3.318844] usb 1-1.5: new full-speed USB device number 7 using dwc_otg
    [    3.738841] usb 1-1.5: device not accepting address 7, error -32
    [    3.739083] usb 1-1-port5: unable to enumerate USB device
    [    4.429582] bcm2835-rng 3f104000.rng: hwrng registered
    [    4.431363] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f2                              00000
    [    4.553870] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
    [    4.584409] cfg80211: Calling CRDA to update world regulatory domain
    [    4.680641] brcmfmac: brcmf_sdio_drivestrengthinit: No SDIO Drive strength in                              it done for chip 43430 rev 1 pmurev 24
    [    4.681212] usbcore: registered new interface driver brcmfmac
    [    4.852417] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Dec 15 2                              015 18:10:45 version 7.45.41.23 (r606571) FWID 01-cc4eda9c
    [    4.920017] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
    [    5.051038] systemd-journald[101]: Received request to flush runtime journal                               from PID 1
    [    5.094725] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
    [    5.094743] cfg80211: World regulatory domain updated:
    [    5.094748] cfg80211:  DFS Master region: unset
    [    5.094752] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gai                              n, max_eirp), (dfs_cac_time)
    [    5.094760] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 m                              Bm), (N/A)
    [    5.094766] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 m                              Bm), (N/A)
    [    5.094772] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 m                              Bm), (N/A)
    [    5.094780] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AU                              TO), (N/A, 2000 mBm), (N/A)
    [    5.094787] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AU                              TO), (N/A, 2000 mBm), (0 s)
    [    5.094793] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000                               mBm), (0 s)
    [    5.094799] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 m                              Bm), (N/A)
    [    5.094805] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0                               mBm), (N/A)
    [    5.343368] brcmfmac: brcmf_add_if: ERROR: netdev:wlan0 already exists
    [    5.343385] brcmfmac: brcmf_add_if: ignore IF event
    [    5.459585] uart-pl011 3f201000.uart: no DMA platform data
    [    5.931305] Adding 102396k swap on /var/swap.  Priority:-1 extents:8 across:3                              20576k SSFS
    [    6.127331] random: nonblocking pool is initialized
    [    6.509970] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
    [    6.510112] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    [    7.952466] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [    7.954680] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E                              1
    [    9.974404] Bluetooth: Core ver 2.20
    [    9.974454] NET: Registered protocol family 31
    [    9.974459] Bluetooth: HCI device and connection manager initialized
    [    9.974474] Bluetooth: HCI socket layer initialized
    [    9.974485] Bluetooth: L2CAP socket layer initialized
    [    9.974502] Bluetooth: SCO socket layer initialized
    [   10.003554] Bluetooth: HCI UART driver ver 2.3
    [   10.003567] Bluetooth: HCI UART protocol H4 registered
    [   10.003571] Bluetooth: HCI UART protocol Three-wire (H5) registered
    [   10.003576] Bluetooth: HCI UART protocol BCM registered
    [   10.207606] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [   10.207619] Bluetooth: BNEP filters: protocol multicast
    [   10.207632] Bluetooth: BNEP socket layer initialized
    

  • Admin

    @Reza

    Is this a china model arduino? It could be a cheap counterfeit FTDI chip..



  • now !!! with unplug / plug gateway dont work !



  • @tbowmo
    no this is arduino nano with a FT232 chip


  • Admin

    is it a genuine arduino nano? I thought they where all using atmega32u4 for usb interface nowadays



  • @tbowmo said:

    is it a genuine arduino nano? I thought they where all using atmega32u4 for usb interface nowadays

    i dont know this is a genuine or no but i know this is a nano with chip FT232 . not CH340
    now ! after unplug / plug , gateway dont back !



  • @tbowmo 0_1474905097662_123.jpg

    i have this error


  • MySensors Evangelist

    Hi.

    I had the same issue with (original) FTDI chipset ARDUINO.
    I use FTDI chipset because that enables me to FIX the USB to stick at for example USB20 and not to a different port. Comes in handy after a reboot. Domoticz will continue to work.

    However ... I had the same issue you described.
    I replaced ARDUINO with new one for testing with CH340.
    Gateway was recognized again.
    The failing FTDI Arduino that was nog recognized works perfectly well with my Windows 10 PC however not with Raspi.

    Keep in mind the CH340 has no serial number. I was unable to fix at a certain USB position.

    From your logs I can confirm I had the same issue.
    try: dmesg | grep "ÃœSB"

    It will not show you a USB1 or USBx device.

    I bought a new FTDI arduino and said bye bye to the problem. All is working again.



  • @sincze
    sorry for weak in english , so you have use which one ? FT232 or CH340 ???
    now you have not same problem ???


  • MySensors Evangelist

    No problem.

    I had problems with original FTDI arduino.
    For testing i changed to 340 arduino that worked.

    Than ordered new FTDI arduino.. And it worked again.
    Do you have a spare ARDUINO that you can flash with your gateway software??

    If your gateway is not assigned a /dev/ttyUSBx address It will not work.



  • @sincze
    sorry again , i am beginner 🙂
    first i do this Instructions (https://www.domoticz.com/wiki/PersistentUSBDevices) and dont work , after this , @tbowmo told me :
    lsusb

    -> provide the output

    unplug / plug the usb device

    once more in your terminal
    lsusb
    -> provide output
    also i do :
    dmesg

    -> provide the output

    unplug / plug the usb device

    so now after unplug/plug , my gateway dont detect and dont work



  • 0_1474907053201_kdkdkdkdk.jpg

    i change usb port for my gateway and this working now , but after reset my problem again,,,,



  • @sincze
    i use a spare ARDUINO but there is my problem yet...
    0_1474908555516_0.jpg



  • @tbowmo
    now i run this
    lsusb

    -> provide the output

    unplug / plug the usb device

    once more in your terminal
    lsusb
    -> provide output

    the same for dmesg. In a terminal type "dmesg" hit return, and provide the output, both before you unplug a device that is not working, and after you have done it, and it is working.

    but after unplug power . there is my problem yet

    0_1474909146153_00.jpg


  • MySensors Evangelist

    @Reza just to be sure: unplug power you mean:

    Unplug the power cord from raspberry right?
    Not unplug and replug FTDI device?



  • @sincze said:

    just to be sure: unplug power you mean:

    Unplug the power cord from raspberry right?
    Not unplug and replug FTDI device?

    my serial gateway is always plug and connect. i mean unplug power of raspberry.
    Suppose i use solar panel and battery for home and in cloudy day . power's home is off... so raspberry will be turn off...(or other reason for power off...)


  • Admin

    @Reza

    from the initial logs, after powerup, there is no FT232 listed in your lsusb listing, then you unplug and plug it again, and THEN the FT232 is present..

    This IS not a bug in mysensors, as it's an HW chip (FT232) that your linux doesn't see before it's unplugged / plugged, it smells of a hardware issue with your nano. Now @sincze mentioned to you that he have had the same issues, and he cured it by exchanging the arduino, maybe it's worth a shot?

    @awi also linked to a document, that describes how to make USB devices persistent in the naming (this can happen once in a while, that a USB device enumerates as a different device number.. That is, /dev/ttyUSB1 instead of /dev/ttyUSB0).

    @Reza said:
    0_1474903726513_12.jpg



  • @tbowmo
    thank you my friend . so this is related to my arduino totally . very very thank you
    so i think , when complete gateway with a Rpi , this problem will be solved !!!



  • @tbowmo
    i test some arduino but all have this problem .
    i have a question . is there a code in linux(Rpi) that after turn off/ on or reset Rpi (after some minutes) , usb port Be reset once !?
    is there a ready code for this ?


  • Admin

    @Reza

    Not that I know of..



  • @tbowmo
    I'm looking for a solution for this issue 🙂
    thank you



  • I have the same problem, i posted a question at the Domoticz Forum :
    Not reconnecting serial portt

    Greetz Peer



  • Somehow I think it's more related to the linux kernel than it's a mysensors or Domticz related issue
    I would start to check which linux kernel you are using with uname -a and then start to search from this
    Maybe it could also be USB power related? Try to use a better USB power supply to your RPI
    https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=53832



  • Why not connect the gateway to one of the onboard serial ports through the GPIO header? I have an Orange Pi which has a GPIO header that is pin compatible with the Raspberry Pi and I ran my gateway from there with no problems. I used pins 6, 8 and 10 which for me was /dev/ttyS3:
    alt text
    The trick in doing this with Domoticz is to create a synlink. The reason for this is that Domoticz looks for a ttyUSBxxx device, so with the symlink you are basically tricking Domoticz into thinking that the onboard serial port is USB. In my case I created a symlink for ttyS3 to ttyUSB30 like this:

    sudo ln -s /dev/ttyS3 /dev/ttyUSB30
    

    This way you avoid having the problem of USB devices not being detected on boot.



  • Thank's for the answers to this problem.
    They didn't work for me, but i think i solved mine.
    Stop monitoring the serial port for data from a terminal session.
    See my post at Domoticz forum.


Log in to reply
 

Suggested Topics

  • 5
  • 2
  • 5
  • 5
  • 2
  • 1

17
Online

11.2k
Users

11.1k
Topics

112.5k
Posts