No inputs, no outputs



  • Hi,

    I installed Evok as described (from a clean Raspbian Jessie install on RPI 2). When I check the UniPi Control Panel I don't see any of the inputs and outputs. I also get an empty array when loading http://ip/rest/all. I2C is enabled. I checked the battery, power supply (5V; 2A), I tried separate power supply for my RPi and UniPi (Jumper 1 not connected) and I did the install all over with a clean install of Raspbian Jessie but with no results.

    The board seems to be found when I run i2cdetect -y 1:

         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
    00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
    10: -- -- -- -- -- -- -- -- 18 -- -- -- -- -- -- -- 
    20: 20 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    50: 50 -- -- -- -- -- -- 57 -- -- -- -- -- -- -- -- 
    60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- 6f 
    70: -- -- -- -- -- -- -- -- 
    
    

    I searched for a solution but found nothing. Could it be a hardware failure of the UniPi board of am I missing something?

    With regards,
    Aäron



  • Hi,

    I installed Evok as described (from a clean Raspbian Jessie install on RPI 2). When I check the UniPi Control Panel I don't see any of the inputs and outputs. I also get an empty array when loading http://ip/rest/all. I2C is enabled. I checked the battery, power supply (5V; 2A), I tried separate power supply for my RPi and UniPi (Jumper 1 not connected) and I did the install all over with a clean install of Raspbian Jessie but with no results.

    The board seems to be found when I run i2cdetect -y 1:

         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
    00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
    10: -- -- -- -- -- -- -- -- 18 -- -- -- -- -- -- -- 
    20: 20 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    50: 50 -- -- -- -- -- -- 57 -- -- -- -- -- -- -- -- 
    60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- 6f 
    70: -- -- -- -- -- -- -- -- 
    
    

    I searched for a solution but found nothing. Could it be a hardware failure of the UniPi board of am I missing something?

    With regards,
    Aäron



  • Hi, try to stop the evok service and run it by hand /opt/evok/evok.py and post the output. Also chceck that pigpio daemon is running correctly.



  • Hi,

    I didn't notice Pigpio daemon was not running. But when I start pigpiod service:

    sudo service pigpiod status
    ● pigpiod.service - Daemon required to control GPIO pins via pigpio
       Loaded: loaded (/lib/systemd/system/pigpiod.service; disabled)
       Active: failed (Result: signal) since ma 2016-06-20 20:45:18 UTC; 4s ago
      Process: 903 ExecStop=/bin/systemctl kill -s SIGKILL pigpiod (code=killed, signal=KILL)
      Process: 899 ExecStart=/usr/bin/pigpiod -l (code=exited, status=0/SUCCESS)
     Main PID: 901 (code=exited, status=127)
    
    jun 20 20:45:18 domotica systemd[1]: Started Daemon required to control GPIO pins via pigpio.
    jun 20 20:45:18 domotica systemd[1]: pigpiod.service: main process exited, code=exited, status=127/n/a
    jun 20 20:45:18 domotica pigpiod[899]: 2016-06-20 20:45:18 gpioCfgInterfaces: bad ifFlags (4)
    jun 20 20:45:18 domotica pigpiod[899]: /usr/bin/pigpiod: symbol lookup error: /usr/bin/pigpiod: undefined symbo...rnals
    jun 20 20:45:18 domotica systemd[1]: pigpiod.service: control process exited, code=killed status=9
    jun 20 20:45:18 domotica systemd[1]: Unit pigpiod.service entered failed state.
    Hint: Some lines were ellipsized, use -l to show in full.
    
    

    When I try to run sudo /usr/bin/pigpiod -l:

    2016-06-20 20:46:36 gpioCfgInterfaces: bad ifFlags (4)
    /usr/bin/pigpiod: symbol lookup error: /usr/bin/pigpiod: undefined symbol: gpioCfgSetInternals
    
    

    Evok returns the following error when running manually:

    Listening on port: 80
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    Can't connect to pigpio on localhost(8888)
    
    Did you start the pigpio daemon? E.g. sudo pigpiod
    
    Did you specify the correct Pi host/port in the environment
    variables PIGPIO_ADDR/PIGPIO_PORT?
    E.g. export PIGPIO_ADDR=soft, export PIGPIO_PORT=8888
    
    Did you specify the correct Pi host/port in the
    pigpio.pi() function? E.g. pigpio.pi('soft', 8888))
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    Error in config section I2CBUS_1 - 'NoneType' object has no attribute 'stop'
    Error in config section EPROM_1 - Invalid device circuit number 1
    Error in config section MCP_1 - Invalid device circuit number 1
    Error in config section RELAY_1 - Invalid device circuit number 1
    Error in config section RELAY_2 - Invalid device circuit number 1
    Error in config section RELAY_3 - Invalid device circuit number 1
    Error in config section RELAY_4 - Invalid device circuit number 1
    Error in config section RELAY_5 - Invalid device circuit number 1
    Error in config section RELAY_6 - Invalid device circuit number 1
    Error in config section RELAY_7 - Invalid device circuit number 1
    Error in config section RELAY_8 - Invalid device circuit number 1
    Error in config section AICHIP_1 - Invalid device circuit number 1
    Error in config section AI_1 - Invalid device circuit number 1
    Error in config section AI_2 - Invalid device circuit number 1
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    Can't connect to pigpio on localhost(8888)
    
    Did you start the pigpio daemon? E.g. sudo pigpiod
    
    Did you specify the correct Pi host/port in the environment
    variables PIGPIO_ADDR/PIGPIO_PORT?
    E.g. export PIGPIO_ADDR=soft, export PIGPIO_PORT=8888
    
    Did you specify the correct Pi host/port in the
    pigpio.pi() function? E.g. pigpio.pi('soft', 8888))
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    Error in config section GPIOBUS_1 - 'NoneType' object has no attribute 'stop'
    Error in config section AO_1 - Invalid device circuit number 1
    Error in config section DI_1 - Invalid device circuit number 1
    Error in config section DI_2 - Invalid device circuit number 1
    Error in config section DI_3 - Invalid device circuit number 1
    Error in config section DI_4 - Invalid device circuit number 1
    Error in config section DI_5 - Invalid device circuit number 1
    Error in config section DI_6 - Invalid device circuit number 1
    Error in config section DI_7 - Invalid device circuit number 1
    Error in config section DI_8 - Invalid device circuit number 1
    Error in config section DI_9 - Invalid device circuit number 1
    Error in config section DI_10 - Invalid device circuit number 1
    Error in config section DI_11 - Invalid device circuit number 1
    Error in config section DI_12 - Invalid device circuit number 1
    Entering 1wire loop
    
    

    Thanks for the fast response.

    With regards,
    Aäron



  • Hello, can you please try to update the pigpiod according to their pages: http://abyz.co.uk/rpi/pigpio/pigpiod.html and let me know if it worked? I have not tested the build on github if it is still compatible with the latest Raspbian. It would save a lot of time. Thanks!



  • Thanks! This solved the problem!

    I updated the Pigpio library with the version from GitHub. I asume the Debian package from the Raspbian repo is outdated and causes the problem.
    Thanks a lot!

    With regards,
    Aäron



  • Thanks a lot. The newest release of raspbian caused the pigpiod to fail starting. Github is updated with the newest version of pigpiod and also with support of systemd service manager.