Home of the Squeezebox™ & Transporter® network music players.
Page 12 of 12 FirstFirst ... 2101112
Results 111 to 113 of 113
  1. #111
    Junior Member
    Join Date
    Feb 2016
    Posts
    6
    Thanks, trying this !
    I was getting ready to buy a new Radio but it seems the new one might get the issue...

    I copied the zip using WinSCP
    Also I redirected the output to /var/log to get some logging without having to run nc on the pi.
    /etc/wlanpoke/wlanpoke.sh -x > /var/log/wlanpoke.log &

    Will report back !

    Edit : Ah sorry it seems there are plenty of logs already :-)
    Last edited by gomi; Yesterday at 11:51.

  2. #112
    Junior Member
    Join Date
    Aug 2020
    Posts
    10

    Today's Update & Watching the Radio

    Quote Originally Posted by gomi View Post
    Thanks, trying this !
    I was getting ready to buy a new Radio but it seems the new one might get the issue...
    I copied the zip using WinSCP
    Also I redirected the output to /var/log to get some logging without having to run nc on the pi.
    /etc/wlanpoke/wlanpoke.sh -x > /var/log/wlanpoke.log &
    Will report back !
    Edit : Ah sorry it seems there are plenty of logs already :-)
    I don't think a new radio would be immune to the wireless connectivity issue. I'm using squeezelite and jive on two pi zeros, and they have been reliable. I was integrating Bluetooth, line level audio input streaming, and re-enabling the image viewer screen savers when I was interrupted by this project.

    Could you post your instructions for using WinSCP to upload the software so I can put it into the manual?

    I don't know how much storage is reasonable for log files to occupy on the radio. Then, they have to be uploaded for viewing. It was quicker and easier to stream the logs to a more capable machine. This is, hopefully, temporary use software. Also, it is important to run the software at boot up, which means you don't see the output except using 'tail -f', and until storage is exhausted.

    By the way, 'nc' and 'tail' are so much fun to watch. You can fiddle with the log level to get more or less console output, which is intended for debugging the wlanpoke script, not the radio. Without 'nc' you will miss the circular buffer prior events display, as it is not echoed to the console. (Perhaps it should be.) Would it be helpful to have a cookbook Windows solution for remote logging and display? You can run a reasonable Ubuntu in Windows 10, and have terminal messages scrolling up in a desktop window as an amusement. Of course, for modifying and debugging wlanpoke, you need to launch from the terminal shell, and a high log level.

    I have attached a recent t21a_2020-09-19_16-54_tail_did.zip log file from here as captured by nc -l -k -p 1121 >> t21a.log & and displayed by tail -f t21a.log &. Looking at the log file, during this brief time span, there were several disconnections. The signal levels were excellent. The bit rates of a couple declined to 5.5 Mb/s and 1 Mb/s at the time of ping failure. I remember these values falling earlier than in the last 2 seconds, but that is not shown here. AFAICT, things seem to be going well until suddenly, they aren't.

    Not wanting to make a habit of daily releases [sic], but the log file was produced by today's 0.5.1 update, wlanpoke.0.5.1.zip. It addresses several bugs and includes additional enhancements for troubleshooting. The 6 radios have been running for 4 days now on various versions of the software without other intervention.
    Last edited by POMdev; Yesterday at 16:33.

  3. #113
    Junior Member
    Join Date
    Feb 2016
    Posts
    6
    OK dunno if it's corrected in 0.5.1 but got an issue in 0.5.0
    Seems the scripts restarted at 22:55

    Code:
    wlanpoke 0.5.0 9/18/2020
    Running as 720
    2020-09-19T22:55:14+0200 Stopping and restarting wlan...
    ..unloading all
    Setting eth1 macaddr: 00:04:20:2C:36:4F
    Load Board Data from /lib/atheros/calData_ar6102_15dBm.bin
    Updating MAC address
    BMI Write Memory (address: 0x502400, filename: /lib/atheros/athwlan.bin)
    BMI Write Memory (address: 0x52d8bc, filename: /lib/atheros/data.patch.hw2_0.bin)
    BMI Write Memory (address: 0x500418, value: 0x52d8bc)
    BMI Bit-Wise (OR) modify Register (address: 0x500410, orig:0x0, new: 0x1,  mask:0x1)
    BMI Done
    Restarting dhcp
    udhcpc (v1.18.2) started
    Sending discover...
    Performing a DHCP renew
    Sending discover...
    Sending select for 192.168.1.54...
    Lease of 192.168.1.54 obtained, lease time 86400
    adding dns 192.168.1.1
    2020-09-19T22:55:29+0200 Waiting for successful ping...
    And it seems it worked beacause the Radio is responding.
    But I have a huge wlanerr.log of 3 MB, with a new line every 2/3 secs

    Code:
    2020-09-20T12:44:22+0200 Marlin failed reset 2020-09-19T22:55:14+0200 up 2020-09-19T22:55:29+0200 eth1 AR6000 802.11g ESSID:"SynGom" Mode:Managed Frequency:2.462 GHz Access Point: 00:11:32:72:5F:59 Bit Rate=54 Mb/s Tx-Power=15 dBm Sensitivity=0/3 Retry:on Encryption key:off Link Quality:25/94 Signal level:-70 dBm Noise level:-96 dBm Rx invalid nwid:0 Rx invalid crypt:15 Rx invalid frag:0 Tx excessive retries:29 Invalid misc:0 Missed beacon:0 PING 192.168.1.1 (192.168.1.1): 56 data bytes 64 bytes from 192.168.1.1: seq=0 ttl=64 time=2.943 ms --- 192.168.1.1 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max = 2.943/2.943/2.943 ms
    2020-09-20T12:44:25+0200 Marlin failed reset 2020-09-19T22:55:14+0200 up 2020-09-19T22:55:29+0200 eth1 AR6000 802.11g ESSID:"SynGom" Mode:Managed Frequency:2.462 GHz Access Point: 00:11:32:72:5F:59 Bit Rate=54 Mb/s Tx-Power=15 dBm Sensitivity=0/3 Retry:on Encryption key:off Link Quality:25/94 Signal level:-70 dBm Noise level:-96 dBm Rx invalid nwid:0 Rx invalid crypt:15 Rx invalid frag:0 Tx excessive retries:29 Invalid misc:0 Missed beacon:0 PING 192.168.1.1 (192.168.1.1): 56 data bytes 64 bytes from 192.168.1.1: seq=0 ttl=64 time=8.293 ms --- 192.168.1.1 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max = 8.293/8.293/8.293 ms
    2020-09-20T12:44:28+0200 Marlin failed reset 2020-09-19T22:55:14+0200 up 2020-09-19T22:55:29+0200 eth1 AR6000 802.11g ESSID:"SynGom" Mode:Managed Frequency:2.462 GHz Access Point: 00:11:32:72:5F:59 Bit Rate=54 Mb/s Tx-Power=15 dBm Sensitivity=0/3 Retry:on Encryption key:off Link Quality:26/94 Signal level:-69 dBm Noise level:-96 dBm Rx invalid nwid:0 Rx invalid crypt:15 Rx invalid frag:0 Tx excessive retries:29 Invalid misc:0 Missed beacon:0 PING 192.168.1.1 (192.168.1.1): 56 data bytes 64 bytes from 192.168.1.1: seq=0 ttl=64 time=35.303 ms --- 192.168.1.1 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max = 35.303/35.303/35.303 ms
    2020-09-20T12:44:30+0200 Marlin failed reset 2020-09-19T22:55:14+0200 up 2020-09-19T22:55:29+0200 eth1 AR6000 802.11g ESSID:"SynGom" Mode:Managed Frequency:2.462 GHz Access Point: 00:11:32:72:5F:59 Bit Rate=54 Mb/s Tx-Power=15 dBm Sensitivity=0/3 Retry:on Encryption key:off Link Quality:26/94 Signal level:-69 dBm Noise level:-96 dBm Rx invalid nwid:0 Rx invalid crypt:15 Rx invalid frag:0 Tx excessive retries:29 Invalid misc:0 Missed beacon:0 PING 192.168.1.1 (192.168.1.1): 56 data bytes 64 bytes from 192.168.1.1: seq=0 ttl=64 time=5.020 ms --- 192.168.1.1 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max = 5.020/5.020/5.020 ms
    2020-09-20T12:44:33+0200 Marlin failed reset 2020-09-19T22:55:14+0200 up 2020-09-19T22:55:29+0200 eth1 AR6000 802.11g ESSID:"SynGom" Mode:Managed Frequency:2.462 GHz Access Point: 00:11:32:72:5F:59 Bit Rate=54 Mb/s Tx-Power=15 dBm Sensitivity=0/3 Retry:on Encryption key:off Link Quality:26/94 Signal level:-69 dBm Noise level:-96 dBm Rx invalid nwid:0 Rx invalid crypt:15 Rx invalid frag:0 Tx excessive retries:29 Invalid misc:0 Missed beacon:0 PING 192.168.1.1 (192.168.1.1): 56 data bytes 64 bytes from 192.168.1.1: seq=0 ttl=64 time=6.277 ms --- 192.168.1.1 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max = 6.277/6.277/6.277 ms
    2020-09-20T12:44:36+0200 Marlin failed reset 2020-09-19T22:55:14+0200 up 2020-09-19T22:55:29+0200 eth1 AR6000 802.11g ESSID:"SynGom" Mode:Managed Frequency:2.462 GHz Access Point: 00:11:32:72:5F:59 Bit Rate=54 Mb/s Tx-Power=15 dBm Sensitivity=0/3 Retry:on Encryption key:off Link Quality:26/94 Signal level:-69 dBm Noise level:-96 dBm Rx invalid nwid:0 Rx invalid crypt:15 Rx invalid frag:0 Tx excessive retries:29 Invalid misc:0 Missed beacon:0 PING 192.168.1.1 (192.168.1.1): 56 data bytes 64 bytes from 192.168.1.1: seq=0 ttl=64 time=2.955 ms --- 192.168.1.1 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max = 2.955/2.955/2.955 ms
    Any clue ?

    Concerning WinSCP
    1 . Install
    2 : Launch, in login choose protocol SCP, use to correct ip address user root pass 1234
    3 : Answer yes to the 2 questions the questions
    4 : Enjoy

    Hope it helps,
    Name:  winscp.png
Views: 5
Size:  7.9 KBName:  winscp2.png
Views: 10
Size:  30.6 KB

Posting Permissions

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