Home of the Squeezebox™ & Transporter® network music players.
Page 13 of 26 FirstFirst ... 3111213141523 ... LastLast
Results 121 to 130 of 254
  1. #121
    Hi shunte88,

    just tested the new version, thanks for the nice work.

    With my setup two issues are remaining:

    - Restart of LMS freezes the lmsmonitor
    - If there is more than one long scrolling string, the strings will be jumbled as they move across the screen

    Aki

  2. #122
    Member
    Join Date
    Apr 2019
    Location
    Finland
    Posts
    71
    Hello,

    I can't get this to work. Nothing is shown on the display.

    This is my display: https://www.aliexpress.com/item/3289...archweb201603_

    Some info:

    Code:
    tc@piCorePlayer:/mnt/mmcblk0p2/tce$ ldd lmsmonitor
            libpthread.so.0 => /lib/libpthread.so.0 (0xf7d67000)
            librt.so.1 => /lib/librt.so.1 (0xf7d50000)
            libi2c.so.0 => /usr/local/lib/libi2c.so.0 (0xf7d3e000)
            libssl.so.1.1 => /usr/local/lib/libssl.so.1.1 (0xf7cda000)
            libcrypto.so.1.1 => /usr/local/lib/libcrypto.so.1.1 (0xf7b19000)
            libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xf79cc000)
            libm.so.6 => /lib/libm.so.6 (0xf795f000)
            libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xf7930000)
            libc.so.6 => /lib/libc.so.6 (0xf77ef000)
            /lib/ld-linux-armhf.so.3 (0xf7d90000)
            libz.so.1 => /usr/lib/libz.so.1 (0xf77da000)
            libdl.so.2 => /lib/libdl.so.2 (0xf77c7000)
    Code:
    tc@piCorePlayer:/mnt/mmcblk0p2/tce$ sudo /mnt/mmcblk0p2/tce/lmsmonitor -n "piCor
    ePlayer" -crbkd -iiii
    OLED Mode ...........: IIC
    This is lmsmonitor (0.4.52) - built Sep  3 2020 08:59:46.
    Verbosity ...........: Info
    OLED Driver .........: (6) SH1106 I2C 128x64
    OLED Address ........: 0x3c
    Scrolling Mode ......: (0) Cylon (Default)
    OLED Clock Font .....: Classic LCD Clock Font
    Sending LMS Discovery ...
    LMS (Server) responded:
    Server IP ...........: 192.168.1.xx:x483
    Player Count ........: 9
    Player Name .........: piCorePlayer
    Player ID ...........:
    Player IP ...........:
    Visualization .......: Inactive
    Hostname ............: piCorePlayer
    Interface ...........: wlan0
    Address .............: 192.168.1.xx
    GFX Font Width ......: 6 (px)
    GFX Font Height .....: 8 (px)
    Code:
    tc@piCorePlayer:/mnt/mmcblk0p2/tce$ i2cdetect -y 1
    Error: Could not open file `/dev/i2c-1' or `/dev/i2c/1': No such file or directory
    Any help is appreciated!

    Thanks

    -Jursi
    Last edited by Jursi; 2020-09-07 at 12:10.

  3. #123
    Member
    Join Date
    Apr 2019
    Location
    Finland
    Posts
    71
    Update:

    Now I get this but nothing on the display:

    Code:
    tc@piCorePlayer:~$ sudo /mnt/mmcblk0p2/tce/lmsmonitor -n "LuxorRadio" -crbkd -ii
    ii -V
    OLED Mode ...........: IIC
    This is lmsmonitor (0.4.52) - built Sep  3 2020 08:59:46.
    Verbosity ...........: Maximum
    OLED Driver .........: (6) SH1106 I2C 128x64
    OLED Address ........: 0x3c
    Scrolling Mode ......: (0) Cylon (Default)
    OLED Clock Font .....: Classic LCD Clock Font
    Sending LMS Discovery ...
    LMS (Server) responded:
    Server IP ...........: 192.168.1.xx:xxxx
    Player Count ........: 8
    Player Name .........: LuxorRadio
    Player ID ...........: xx:bf:xx:xx:de:xx
    Player IP ...........: 192.168.1.xx
    Visualization .......: Inactive
    Hostname ............: piCorePlayer
    Interface ...........: wlan0
    Address .............: 192.168.1.xx
    GFX Font Width ......: 6 (px)
    GFX Font Height .....: 8 (px)
    2020-09-07 21:41:11 :: src/lmsmonitor.c-0833 : isRefreshed
    2020-09-07 21:41:11 :: src/lmsmonitor.c-0876 : activeScroller test
    2020-09-07 21:41:11 :: src/lmsmonitor.c-0881 : display clock test
    2020-09-07 21:41:11 :: src/lmsmonitor.c-0833 : isRefreshed
    2020-09-07 21:41:11 :: src/lmsmonitor.c-0847 : isPlaying
    2020-09-07 21:41:12 :: src/lmsmonitor.c-0833 : isRefreshed
    2020-09-07 21:41:12 :: src/lmsmonitor.c-0847 : isPlaying
    2020-09-07 21:41:13 :: src/lmsmonitor.c-0833 : isRefreshed
    2020-09-07 21:41:13 :: src/lmsmonitor.c-0847 : isPlaying
    2020-09-07 21:41:14 :: src/lmsmonitor.c-0833 : isRefreshed
    2020-09-07 21:41:14 :: src/lmsmonitor.c-0847 : isPlaying
    2020-09-07 21:41:15 :: src/lmsmonitor.c-0833 : isRefreshed
    2020-09-07 21:41:15 :: src/lmsmonitor.c-0847 : isPlaying
    2020-09-07 21:41:16 :: src/lmsmonitor.c-0833 : isRefreshed
    2020-09-07 21:41:16 :: src/lmsmonitor.c-0847 : isPlaying
    2020-09-07 21:41:17 :: src/lmsmonitor.c-0833 : isRefreshed
    2020-09-07 21:41:17 :: src/lmsmonitor.c-0847 : isPlaying
    2020-09-07 21:41:18 :: src/lmsmonitor.c-0833 : isRefreshed
    2020-09-07 21:41:18 :: src/lmsmonitor.c-0847 : isPlaying
    test

  4. #124
    Hi Jursi,

    did you follow the setup instruction on https://github.com/shunte88/LMSMonitor?

    my command line options (in gomonitor):

    ...
    CMD="sudo ${BINDIR}/lmsmonitor -n ${PNAME} -c -z -f7 $1 $2 $3 $4 $5 $6 $7 $8 $9"
    ...

    Aki

  5. #125
    Member
    Join Date
    Apr 2019
    Location
    Finland
    Posts
    71
    Quote Originally Posted by Aki7 View Post
    Hi Jursi,

    did you follow the setup instruction on https://github.com/shunte88/LMSMonitor?

    my command line options (in gomonitor):

    ...
    CMD="sudo ${BINDIR}/lmsmonitor -n ${PNAME} -c -z -f7 $1 $2 $3 $4 $5 $6 $7 $8 $9"
    ...

    Aki
    Hello,

    Yes,

    I did these steps:

    From the Squeezlite page of the pCP web frontend type 1 in the "m" ALSA parameter section

    And, in the Various Options add -v

    See the squeezelite page for more details

    We also need to install the i2c tools library so we can review setup and communicate with the OLED screen


    Code:
    tc@piCorePlayer:~$ sudo /mnt/mmcblk0p2/tce/lmsmonitor --name "LuxorRadio" -c -x
    ”0x3c” -rbkd --verbose -V
    OLED Mode ...........: IIC
    This is lmsmonitor (0.4.52) - built Sep  3 2020 08:59:46.
    Verbosity ...........: Maximum
    OLED Driver .........: (6) SH1106 I2C 128x64
    OLED Address ........: 0x3c
    Scrolling Mode ......: (0) Cylon (Default)
    OLED Clock Font .....: Classic LCD Clock Font
    Sending LMS Discovery ...
    LMS (Server) responded:
    Server IP ...........: 192.168.1.xx:xxxx
    Player Count ........: 9
    Player Name .........: LuxorRadio
    Player ID ...........: 1c:bf:xx:xx:xx:xx
    Player IP ...........: 192.168.1.xx
    Provider IP .........: 84.xxx.3.xx
    Reported TZ .........: Europe/Helsinki
    Longitude ...........:   23.1172
    Latitude ............:   60.3900
    Sunrise .............: 09-07-2020 09:44:13
    Sunset ..............: 09-07-2020 23:14:10
    Set Display .........: Night Mode
    rotation ....(in)....: 0
    rotation ....(02)....: 0
    rotation ....(out)...: 0
    Visualization .......: Inactive
    Hostname ............: piCorePlayer
    Interface ...........: wlan0
    Address .............: 192.168.1.xx
    GFX Font Width ......: 6 (px)
    GFX Font Height .....: 8 (px)
    2020-09-08 11:36:10 :: src/lmsmonitor.c-0833 : isRefreshed
    2020-09-08 11:36:10 :: src/lmsmonitor.c-0876 : activeScroller test
    2020-09-08 11:36:10 :: src/lmsmonitor.c-0881 : display clock test
    2020-09-08 11:36:10 :: src/lmsmonitor.c-0961 : clockPage
    2020-09-08 11:36:10 :: src/lmsmonitor.c-0968 : cpu Metrics?
    2020-09-08 11:36:11 :: src/lmsmonitor.c-0833 : isRefreshed
    2020-09-08 11:36:11 :: src/lmsmonitor.c-0847 : isPlaying
    2020-09-08 11:36:11 :: src/lmsmonitor.c-0833 : isRefreshed
    2020-09-08 11:36:11 :: src/lmsmonitor.c-0847 : isPlaying
    2020-09-08 11:36:12 :: src/lmsmonitor.c-0833 : isRefreshed

    But nothing on the display.

    SDA is connected to GPIO2
    SCK (SCL) is connected to GPIO3

    Raspberry pi zero
    Last edited by Jursi; 2020-09-08 at 01:43.
    test

  6. #126

    Iic

    hi @jursi, sorry your having problems

    gomonitor takes care of prepping your environment including loading the IIC infrastructure if it not already active

    you can do the same with:
    Code:
    sudo modprobe i2c-bcm2835
    sudo modprobe i2c-dev
    then check for your device with i2cdetect, e.g. for my setup
    Code:
    tc@koala:/mnt/mmcblk0p2/tce$ i2cdetect -y 1
         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
    00:          03 -- -- -- -- -- -- -- -- -- -- -- -- 
    10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- -- 
    40: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 
    50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    70: -- -- -- -- -- -- -- --
    you may see more than one device if you have a DAC or other IIC device attached to your pi

    your device should show up at 0x3c

    ensure all your connections are good, pins are clean and solder joints are good - check your jumper wires too

    the device looks to be a standard ssd1306 so you should need to specify any OLED parameters
    if it doesn't work out of the box its usually just a matter of trying the various IIC drivers until you get a match, -o 3, 5, or 6 would be the ones to try - 6 is the default

    you can update and install to the latest with the following set of commands, they'll do everything except change the squeeze parameters, that you would still have to do manually
    Code:
    tce-load -i i2c-tools.tcz
    pcp bu
    cd /mnt/mmcblk0p2/tce
    cp gomonitor safe.gomonitor
    wget "https://github.com/shunte88/LMSMonitor/blob/master/bin/lmsmonitorpcp.tgz?raw=true" -O lmsmonitorpcp.tgz && \
    tar -xzvf lmsmonitorpcp.tgz && \
    chmod +xX gomonitor
    pcp bu
    note it backs up gomonitor before update in case you rolled your own

    fingers crossed you resolve, given those daylight hours hopefully you won't have to burn the midnight oil

    note that I'm checking out a self selecting solution which if its fit for purpose will make its way into the solution

    also coming today a fix for the "half-flip" issue
    hoping to get re-connection in play too for dropped player/server scenarios

    I refactored code and improved the memory footprint some.
    To celebrate I added another "egg",and fully refactored the entire implementation for those visualizations so they can be conditionally compiled in a future release
    As of 26-Feb-2021 my digitized collection is (25608 hours 20 minutes) + (15 seconds) or
    2.921 years in duration
    random continuous play would really annoy the neighbors...

    Digitized thus far:

    Total Tracks: 165,586
    Total Albums: 15,155
    Total Artists: 21,734
    Total Genres: 765
    Total Playing Time: 25608:20:15


    With another ~2400 yet to be ripped... a moving target such that it is ...

  7. #127
    Member
    Join Date
    Apr 2019
    Location
    Finland
    Posts
    71
    Quote Originally Posted by shunte88 View Post
    hi @jursi, sorry your having problems

    gomonitor takes care of prepping your environment including loading the IIC infrastructure if it not already active

    you can do the same with:
    Code:
    sudo modprobe i2c-bcm2835
    sudo modprobe i2c-dev
    then check for your device with i2cdetect, e.g. for my setup
    Code:
    tc@koala:/mnt/mmcblk0p2/tce$ i2cdetect -y 1
         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
    00:          03 -- -- -- -- -- -- -- -- -- -- -- -- 
    10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- -- 
    40: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 
    50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    70: -- -- -- -- -- -- -- --
    you may see more than one device if you have a DAC or other IIC device attached to your pi

    your device should show up at 0x3c

    ensure all your connections are good, pins are clean and solder joints are good - check your jumper wires too

    the device looks to be a standard ssd1306 so you should need to specify any OLED parameters
    if it doesn't work out of the box its usually just a matter of trying the various IIC drivers until you get a match, -o 3, 5, or 6 would be the ones to try - 6 is the default

    you can update and install to the latest with the following set of commands, they'll do everything except change the squeeze parameters, that you would still have to do manually
    Code:
    tce-load -i i2c-tools.tcz
    pcp bu
    cd /mnt/mmcblk0p2/tce
    cp gomonitor safe.gomonitor
    wget "https://github.com/shunte88/LMSMonitor/blob/master/bin/lmsmonitorpcp.tgz?raw=true" -O lmsmonitorpcp.tgz && \
    tar -xzvf lmsmonitorpcp.tgz && \
    chmod +xX gomonitor
    pcp bu
    note it backs up gomonitor before update in case you rolled your own

    fingers crossed you resolve, given those daylight hours hopefully you won't have to burn the midnight oil

    note that I'm checking out a self selecting solution which if its fit for purpose will make its way into the solution

    also coming today a fix for the "half-flip" issue
    hoping to get re-connection in play too for dropped player/server scenarios

    I refactored code and improved the memory footprint some.
    To celebrate I added another "egg",and fully refactored the entire implementation for those visualizations so they can be conditionally compiled in a future release
    Thank you for you answer.

    When I try to run LMSmonitor with -o specified, I get:


    Code:
    tc@piCorePlayer:/mnt/mmcblk0p2/tce$ sudo /mnt/mmcblk0p2/tce/lmsmonitor --name "Retropi" --oled 5 -c -rbkd --verbose -V
    
    Cleanup and shutdown
    
    Cleanup and shutdown
    All Done
    Bye Bye.
    If I try to run:

    Code:
    sudo /mnt/mmcblk0p2/tce/gomonitor rn -o 3 -c -V
    Process doesn't start either (checked ps/top)

    Btw, what is the difference between running tce/lmsmonitor and running tce/gomonitor? Which one should I use?


    Thanks!
    Last edited by Jursi; 2020-09-08 at 10:54.
    test

  8. #128
    5 is an invalid driver, it should just abend like that but tell you the available options

    which it did on my build environment
    Code:
    pi@zebra001:~/LMSMonitor $ sudo bin/lmsmonitor --name "caracara" --verbose -c -rbkd -o5
    Supported OLED types:
        1 ...: Adafruit SPI 128x64
        3 ...: Adafruit I2C 128x64
        4 ...: Seeed I2C 128x64
        6* ..: SH1106 I2C 128x64
        7 ...: SH1106 SPI 128x64
    
    * is default
    lmsmonitor: you specified 5, it is an invalid 128x64 OLED type
    it looks like its the space in "--oled 5 "that's the cause of abend
    use -o[driver] or --oled=driver. No spaces for this parameter


    I'll track that down and fix it.

    I don't think it likes the space on the "-o 3" either - use -o3

    Your device is an I2C flavor, SPI and IIC are nothing more than ways of talking to the device, but they are different entities

    from the list you can see that the I2C is applicable for 3, 4, and 6 only

    6 is the default if you don't override

    gomonitor eats all of the output so stick with calling the lmsmonitor binary directly while you troubleshoot

    gomonitor is a "helper" script - it hides some of the complexities, if you really want to take control use lmsmonitor

    on my setup I use gomonitor on startup and while I'm tooling on the solution I'm at the command line using lmsmonitor

    I just pushed an update, fresh binary and gomonitor script

    was your cabling Ok?

    also, have you used the OLED on any other solution and had it working?
    Last edited by shunte88; 2020-09-08 at 12:17.
    As of 26-Feb-2021 my digitized collection is (25608 hours 20 minutes) + (15 seconds) or
    2.921 years in duration
    random continuous play would really annoy the neighbors...

    Digitized thus far:

    Total Tracks: 165,586
    Total Albums: 15,155
    Total Artists: 21,734
    Total Genres: 765
    Total Playing Time: 25608:20:15


    With another ~2400 yet to be ripped... a moving target such that it is ...

  9. #129
    Member
    Join Date
    Apr 2019
    Location
    Finland
    Posts
    71
    Quote Originally Posted by shunte88 View Post
    5 is an invalid driver, it should just abend like that but tell you the available options

    which it did on my build environment
    Code:
    pi@zebra001:~/LMSMonitor $ sudo bin/lmsmonitor --name "caracara" --verbose -c -rbkd -o5
    Supported OLED types:
        1 ...: Adafruit SPI 128x64
        3 ...: Adafruit I2C 128x64
        4 ...: Seeed I2C 128x64
        6* ..: SH1106 I2C 128x64
        7 ...: SH1106 SPI 128x64
    
    * is default
    lmsmonitor: you specified 5, it is an invalid 128x64 OLED type
    it looks like its the space in "--oled 5 "that's the cause of abend
    use -o[driver] or --oled=driver. No spaces for this parameter


    I'll track that down and fix it.

    I don't think it likes the space on the "-o 3" either - use -o3

    Your device is an I2C flavor, SPI and IIC are nothing more than ways of talking to the device, but they are different entities

    from the list you can see that the I2C is applicable for 3, 4, and 6 only

    6 is the default if you don't override

    gomonitor eats all of the output so stick with calling the lmsmonitor binary directly while you troubleshoot

    gomonitor is a "helper" script - it hides some of the complexities, if you really want to take control use lmsmonitor

    on my setup I use gomonitor on startup and while I'm tooling on the solution I'm at the command line using lmsmonitor

    I just pushed an update, fresh binary and gomonitor script

    was your cabling Ok?

    also, have you used the OLED on any other solution and had it working?
    Hello,

    I changed from pi zero to pi 4 and used driver 3 and it is working! There must be something wrong with my pi zero I believe.

    Thank you for your help and sorry for the trouble caused.

    I will try to get the pi zero working also.
    Last edited by Jursi; 2020-09-08 at 13:23.
    test

  10. #130
    Member
    Join Date
    Apr 2019
    Location
    Finland
    Posts
    71
    Quote Originally Posted by Jursi View Post
    Hello,

    I changed from pi zero to pi 4 and used driver 3 and it is working! There must be something wrong with my pi zero I believe.

    Thank you for your help and sorry for the trouble caused.

    I will try to get the pi zero working also.

    I am restoring old radio. The display will be on the top panel. Looks awesome: https://imgur.com/a/0ZHpiYl
    test

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •