1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

HyperCon NEWBIE HERE, please help

Discussion in 'Software Support' started by Wim, 12 July 2017.

  1. Wim

    Wim Member

    Messages:
    129
    Hardware:
    RPi1/Zero, RPi2
    sudo netstat --listen:


    Active Internet connections (only servers)
    Proto Recv-Q Send-Q Local Address Foreign Address State
    tcp 0 0 *:19444 *:* LISTEN
    tcp 0 0 *:19445 *:* LISTEN
    tcp 0 0 *:ssh *:* LISTEN
    tcp6 0 0 [::]:ssh [::]:* LISTEN
    udp 0 0 *:57309 *:*
    udp 0 0 *:mdns *:*
    udp 0 0 *:bootpc *:*
    udp 0 0 raspberrypiZERO.fri:ntp *:*
    udp 0 0 localhost:ntp *:*
    udp 0 0 *:ntp *:*
    udp6 0 0 [::]:mdns [::]:*
    udp6 0 0 [::]:59451 [::]:*
    udp6 0 0 fe80::9dac:12b6:508:ntp [::]:*
    udp6 0 0 localhost:ntp [::]:*
    udp6 0 0 [::]:ntp [::]:*
    raw6 0 0 [::]:ipv6-icmp [::]:* 7
    Active UNIX domain sockets (only servers)
    Proto RefCnt Flags Type State I-Node Path
    unix 2 [ ACC ] SEQPACKET LISTENING 4865 /run/udev/control
    unix 2 [ ACC ] STREAM LISTENING 4869 /run/systemd/journal/stdout
    unix 2 [ ACC ] STREAM LISTENING 11113 @/tmp/dbus-BVk8rH8Ohb
    unix 2 [ ACC ] STREAM LISTENING 10280 @/tmp/.X11-unix/X0
    unix 2 [ ACC ] STREAM LISTENING 10281 /tmp/.X11-unix/X0
    unix 2 [ ACC ] STREAM LISTENING 12217 @/dbus-vfs-daemon/socket-IXnNJMJs
    unix 2 [ ACC ] STREAM LISTENING 11703 /tmp/.pcmanfm-socket--0-pi
    unix 2 [ ACC ] STREAM LISTENING 12105 /tmp/.menu-cached-:0-pi
    unix 2 [ ACC ] STREAM LISTENING 12211 @/dbus-vfs-daemon/socket-yPoIlt7Z
    unix 2 [ ACC ] STREAM LISTENING 11098 /tmp/ssh-p9cbFt6qC2Ha/agent.691
    unix 2 [ ACC ] STREAM LISTENING 11601 /tmp/ssh-s6XWqiBlshwA/agent.872
    unix 2 [ ACC ] STREAM LISTENING 8878 /var/run/avahi-daemon/socket
    unix 2 [ ACC ] STREAM LISTENING 8881 /var/run/dbus/system_bus_socket
    unix 2 [ ACC ] STREAM LISTENING 9142 /var/run/dhcpcd.sock
    unix 2 [ ACC ] STREAM LISTENING 10941 /run/user/1000/systemd/private
    unix 2 [ ACC ] STREAM LISTENING 9151 /var/run/dhcpcd.unpriv.sock
    unix 2 [ ACC ] STREAM LISTENING 4842 /run/systemd/private
     
  2. Wim

    Wim Member

    Messages:
    129
    Hardware:
    RPi1/Zero, RPi2
  3. Wim

    Wim Member

    Messages:
    129
    Hardware:
    RPi1/Zero, RPi2
    Wait (sorry).

    I changed the ip-adress of Kodi from the shield to the desktop (probably a wrong setting in the shield, from pi2?) and now I get all white leds for a few seconds, than probably kodi's leds, than all white again, etc. No more "KODICHECK ERROR: Kodi Connection error (7)".
    And when I use the android app, I get an effect for a few seconds and than all white leds for a few seconds and then the effect again for a few seconds, etc!

    Meaning a change is being set correct, but after 1 second all leds turn white and I can't see the setting anymore. So the question is not why the change stops, but why the leds turn all white after a second.


    JSONSERVER ERROR remaining:

    Hyperion Ambilight Deamon (1316)
    Version : V1.03.3 (brindosch-2fbbcff/2f01dfa-1495880388
    Build Time: Jun 3 2017 02:06:37
    INFO: Selected configuration file: /etc/hyperion/hyperion.config.json
    HYPERION INFO: ColorTransform 'default' => [0; 179]
    HYPERION INFO: ColorCorrection 'default' => [0; 179]
    HYPERION INFO: ColorAdjustment 'default' => [0; 179]
    LEDDEVICE INFO: configuration:
    {
    "colorOrder" : "grb",
    "name" : "MyHyperionConfig",
    "type" : "ws2812spi"
    }

    INFO: Creating linear smoothing
    HYPERION (CS) INFO: Created linear-smoothing(interval_ms=50;settlingTime_ms=200;updateDelay=0
    EFFECTENGINE INFO: 27 effects loaded from directory /usr/share/hyperion/effects
    EFFECTENGINE INFO: Initializing Python interpreter
    INFO: Hyperion started and initialised
    INFO: Boot sequence 'Knight rider' EFFECTENGINE INFO: run effect Knight rider on channel 0
    BLACKBORDER INFO: threshold set to 0.01 (3)
    BLACKBORDER INFO: mode:default
    started
    INFO: Kodi checker created and started
    terminate called after throwing an instance of 'std::runtime_error'
    what(): JSONSERVER ERROR: could not bind to port
     
  4. Wim

    Wim Member

    Messages:
    129
    Hardware:
    RPi1/Zero, RPi2
    Okay, checked Kodi-addon on the Shield. It was disabled, that's why the Kodicheck error. Sorry about that.

    Now the white-leds-issue and the jsonserver error.
     
  5. penfold42

    penfold42 Moderator Developer

    Messages:
    750
    Hardware:
    RPi1/Zero, RPi2, RPi3, 32/64bit, +Arduino, +nodeMCU/ESP8266
    The log looks ok.

    How confident are you in the wiring ?

    What level shifter are you using ?

    The SPI loopback test worked ok ?

    Try stopping Hyperion and directly manipulating the gpio from a command prompt to set it high and low and then check the voltage you get at the 1st led.
     
  6. Wim

    Wim Member

    Messages:
    129
    Hardware:
    RPi1/Zero, RPi2
    With the pi2, everything works ok. When I put the sd from the pi0 in the pi2, same. The sd from the pi2 in the pi0 won't boot. So must be hardware related. With the pi2, everything works okay, so at most the soldered headers on the pi0 are not okay, but I don't think so. I thought that the gpio pins on the pi2 and pi0 are the same, true?
    SN74HCT125N

    Will try it again to be sure.

    I'm going to do that now.

    Wim
     
  7. Wim

    Wim Member

    Messages:
    129
    Hardware:
    RPi1/Zero, RPi2
    Penfold,

    Have you seen these posts on mine:
    https://hyperion-project.org/threads/newbie-here-please-help.917/page-7#post-7245
    https://hyperion-project.org/threads/newbie-here-please-help.917/page-7#post-7246
    https://hyperion-project.org/threads/newbie-here-please-help.917/page-7#post-7250

    Wim
    I'm going to run the tests now and report back.
     
  8. Wim

    Wim Member

    Messages:
    129
    Hardware:
    RPi1/Zero, RPi2
    spi mode: 0
    bits per word: 8
    max speed: 500000 Hz (500 KHz)

    FF FF FF FF FF FF
    40 00 00 00 00 95
    FF FF FF FF FF FF
    FF FF FF FF FF FF
    FF FF FF FF FF FF
    DE AD BE EF BA AD
    F0 0D
     
  9. Wim

    Wim Member

    Messages:
    129
    Hardware:
    RPi1/Zero, RPi2
    sudo service hyperion stop
    gpio -1 mode 19 out

    gpio -1 write 19 1
    DI (data in) -0.02
    BI (backup in, I'm using ws2813) -5.16

    gpio -1 write 19 0
    DI (data in) -0.02
    BI (backup in, I'm using ws2813) 0.00


    Reboot (so hyperion active again)
    Before making a change (color or effect):
    DI (data in) -0.07 (white leds)
    BI (backup in, I'm using ws2813) 0.00

    Making a change, for 0.5s:
    DI (data in) -0.01 (effect or color)
    BI (backup in, I'm using ws2813) 0.00

    After 0.5s:
    DI (data in) -0.07 (white leds again)
    BI (backup in, I'm using ws2813) 0.00

    I didn't mix up the results from DI and BI!
    BI and DI are correctly tied together.

    It did work correct with the pi2.

    When the leds have turned white after 0.5s and I wait long enough I can see the color I set before, again for 0.5 and than all white again, while DI drops to -0.01 and when the leds turn white again up to -0.07 again.

    I don't know what you make of it, but I think I have a faulty pi0. And it seems that all tests are useless. Perhaps the same as this:
    Loopback test okay: https://github.com/PiSupply/PaPiRus/issues/81#issuecomment-286412767
    Third pi0 working: https://github.com/PiSupply/PaPiRus/issues/81#issuecomment-286723151


    After 10 mins, not only the leds I addressed with hyperion are white (for testing purposing I reduced the number to 5):
    led 6 pink
    7 white
    8 green
    9 -13 black
    14, 15 white
    16 yellow
    17-19 black
    20, 21 white
    22 yellow
    23-25 black
    26,27 white
    28 yellow (although less pronounced yellow, more whitish).

    There seems to be a pattern here. And maybe it's green, yellow green, white yellow?

    Changing the color or effect on the first 5 leds, makes no change to the other leds.

    Wim
     
  10. penfold42

    penfold42 Moderator Developer

    Messages:
    750
    Hardware:
    RPi1/Zero, RPi2, RPi3, 32/64bit, +Arduino, +nodeMCU/ESP8266
    Isn't spi MOSI on gpio 10 ?
     
  11. Wim

    Wim Member

    Messages:
    129
    Hardware:
    RPi1/Zero, RPi2
    Yes, gpio 10, physical pin 19.

    Fragment from http://wiringpi.com/the-gpio-utility/:
    "Examples

    gpio mode 0 out
    gpio write 0 1
    The above uses the wiringPi pin numbers to set pin 0 as an output and then sets the pin to a logic 1.

    gpio -g mode 17 out
    gpio -g write 17 1
    This uses the BCM_GPIO pin numbering scheme and performs the same operation as above.

    gpio -1 mode 11 out
    gpio -1 write 11 1
    This uses the physical P1 pin numbering scheme and performs the same operation as above."

    I'm using the last kind, physical pin number
     
  12. penfold42

    penfold42 Moderator Developer

    Messages:
    750
    Hardware:
    RPi1/Zero, RPi2, RPi3, 32/64bit, +Arduino, +nodeMCU/ESP8266
    I wonder if the core_clock is taking effect.
    Can you run
    vcgrncmd measure_clock core

    Ideally do it in a fast loop and then start Hyperion and watch for changes in the clock speed.


    On you gpio cmdline tests - was it 5v or -5v ? I'm assuming you just typed it that way
     
  13. Wim

    Wim Member

    Messages:
    129
    Hardware:
    RPi1/Zero, RPi2
    Penfold, sorry for the late response, the email got stuck in spambox.

    sudo service hyperion stop
    watch -n 0.1 "vcgencmd measure_clock core"

    I see alternating 250000000 and 400000000


    sudo service hyperion start
    watch -n 0.1 "vcgencmd measure_clock core"

    Same results, but also the leds are flashing white.

    Wim
    Thanks for helping me!
     
  14. Wim

    Wim Member

    Messages:
    129
    Hardware:
    RPi1/Zero, RPi2
    I already had core_freq=400 at the bottom of the file, I now added it on top and rebooted. Same results.

    Not on every flash, but on most of them, clock core changed from 250000000 to 400000000. Sometimes it stays at one or the other. And on a few occasions I see a different number, something with a lot of 999.
     
  15. Wim

    Wim Member

    Messages:
    129
    Hardware:
    RPi1/Zero, RPi2
    I think the leds flash at every command I type???

    When I type sudo nano /boot/config.txt the leds also flash.

    Wait, they don't flash when typing:
    gpio -1 write 21 0

    But again flashing when:
    sudo gpio -1 write 21 0

    Is this normal???
     
  16. penfold42

    penfold42 Moderator Developer

    Messages:
    750
    Hardware:
    RPi1/Zero, RPi2, RPi3, 32/64bit, +Arduino, +nodeMCU/ESP8266
    The core clock speed changes are your problem.

    Try force_tiurbo=1
     
  17. Wim

    Wim Member

    Messages:
    129
    Hardware:
    RPi1/Zero, RPi2
    Ladies and gentlemen, we've got him!
    Penfold, you did it. I can't believe it!!!!!!!!!

    What caused the issue? Is this normal behaviour? Why is force_turbo needed?
     
  18. penfold42

    penfold42 Moderator Developer

    Messages:
    750
    Hardware:
    RPi1/Zero, RPi2, RPi3, 32/64bit, +Arduino, +nodeMCU/ESP8266
    This is another way to force the core_clock frequency.

    Someone suggested that this isn't the "best" way, but it worked for me in the past when setting the core freq didnt
     
  19. Wim

    Wim Member

    Messages:
    129
    Hardware:
    RPi1/Zero, RPi2
    Works for me too :)

    Thanks for the help again.

    Wim