Keeping lost connection to BeagleBone Black (BBB) wireless

Runtime
Anonymous
2018-05-08
15 hours ago
  • Anonymous - 2018-05-08

    Originally created by: myemail for codesys

    Hi,
    I installed free codesys 3.5 sp12 patch3+ (64bit)
    and beaglebone black wireless (running with bone-debian 9.3 lxqt)
    then update BBB from codesys. Installed the package v3.5.12.30.
    But always can not detect the target with IP Address.( Tried with USB and Wifi)

    Anyway I can get the status as below:

    root@beaglebone:~# service codesyscontrol status
    ● codesyscontrol.service - LSB: Prepares and starts codesyscontrol
    Loaded: loaded (/etc/init.d/codesyscontrol; generated; vendor preset: enabled)
    Active: active (exited) since Sat 2018-05-05 23:31:16 UTC; 7min ago
    Docs: man:systemd-sysv-generator(8)
    Process: 7753 ExecStop=/etc/init.d/codesyscontrol stop (code=exited, status=0/SUCCESS)
    Process: 7794 ExecStart=/etc/init.d/codesyscontrol start (code=exited, status=0/SUCCESS)

    May 05 23:31:14 beaglebone systemd[1]: Starting LSB: Prepares and starts codesyscontrol...
    May 05 23:31:14 beaglebone codesyscontrol[7794]: Backup licenses
    May 05 23:31:14 beaglebone codesyscontrol[7794]: tar: Removing leading `/' from member names
    May 05 23:31:15 beaglebone codesyscontrol[7794]: chmod: cannot access '/sys/bus/i2c/devices/0-0050/at24-0/nvmem': No such file or directory
    May 05 23:31:15 beaglebone codesyscontrol[7794]: pid 7813's current affinity mask: 1
    May 05 23:31:15 beaglebone codesyscontrol[7794]: pid 7813's new affinity mask: 1
    May 05 23:31:16 beaglebone codesyscontrol[7794]: codesyscontrol started
    May 05 23:31:16 beaglebone systemd[1]: Started LSB: Prepares and starts codesyscontrol.

    After "Stop" then "Start" the runtime in "beaglebone black" tab. The status changed:

    ● codesyscontrol.service - LSB: Prepares and starts codesyscontrol
    Loaded: loaded (/etc/init.d/codesyscontrol; generated; vendor preset: enabled)
    Active: active (running) since Sat 2018-05-05 23:56:47 UTC; 3s ago
    Docs: man:systemd-sysv-generator(8)
    Process: 20520 ExecStop=/etc/init.d/codesyscontrol stop (code=exited, status=0/SUCCESS)
    Process: 20563 ExecStart=/etc/init.d/codesyscontrol start (code=exited, status=0/SUCCESS)
    Tasks: 13 (limit: 4915)
    CGroup: /system.slice/codesyscontrol.service
    ├─20581 /opt/codesys/bin/codesyscontrol.bin /etc/CODESYSControl.cfg
    └─20596 /opt/codesys/bin/codesyscontrol.bin /etc/CODESYSControl.cfg

    May 05 23:56:45 beaglebone systemd[1]: Starting LSB: Prepares and starts codesyscontrol...
    May 05 23:56:45 beaglebone codesyscontrol[20563]: Backup licenses
    May 05 23:56:45 beaglebone codesyscontrol[20563]: tar: Removing leading `/' from member names
    May 05 23:56:45 beaglebone codesyscontrol[20563]: chmod: cannot access '/sys/bus/i2c/devices/0-0050/at24-0/nvmem': No such file or directory
    May 05 23:56:45 beaglebone codesyscontrol[20563]: pid 20581's current affinity mask: 1
    May 05 23:56:45 beaglebone codesyscontrol[20563]: pid 20581's new affinity mask: 1
    May 05 23:56:47 beaglebone codesyscontrol[20563]: codesyscontrol started
    May 05 23:56:47 beaglebone systemd[1]: Started LSB: Prepares and starts codesyscontrol.

    While in this mode, I can "scan network" and find the BBB, and login BUT only a few minutes( if not seconds) The codesyscontrol service changed back to active(exited). And the dialog "No connection to the device. Please rescan your network" pop out. The scan network will not work except I do the routine "stop" then "start" again. But it only last for few minutes.

    Above situation tested with both USB and WiFi connection. I will try this on the second BBB later to exclude the hardware problem.

    Thanks!

    Chen

     
  • eschwellinger

    eschwellinger - 2018-05-16

    Hi,

    yes at the moment this not supported!
    Could you please write a 'feature request' to the CODESYS Store helpdek - 'my question'?

    BR
    Edwin

     

Log in to post a comment.