Jump to content

rongon

  • Posts

    24
  • Joined

  • Last visited

  • Country

    United States

Retained

  • Member Title
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I have been waiting patiently for a response from ALLO support, but it's now been over two weeks and not a peep. Is anyone answering basic questions?
  2. I sent dmesg log. I can't get the Boss DAC to initialize any more. It is no longer working, even from a single power supply. I tried powering it from 5V 3A power supply connecting to Boss DAC USB-C port, jumper J25 shorted. Boss DAC not working. I tried powering it from 5V 2.5A power supply connecting to RPi USB Micro-B port, J25 shorted. Boss DAC still not working. Always get the MPD error Failed to open "alsa default", etc. Should I wipe the uSDcard and reinstall Moode OS?
  3. And now I cannot get the Boss DAC to work, even with J25 shorted (jumper installed) and no matter which power supply I use, or if I connect the power supply to the RPi USB port or to the Boss DAC USB port. Only one green LED lights on the Boss DAC and it does not play music. I have set the i2s device to Allo Boss DAC, rebooted, restarted MPD service, multiple times. Ah, but now I got it to work by powering the setup through the RPi USB Micro-B port instead of the DAC USB-C port. I don't understand. It seems the Boss DAC will only work when it wants to. There is no one configuration that always works.
  4. It appears that now the only way to get the Boss 1.2 DAC to work on my RPi, I have to power it from a single supply plugged into the USB-C port on the Boss DAC pcb. This way, both green LEDs on the Boss DAC light up and the DAC plays sound. It is detected by aplay as well. When I connect the power supply to the RPi USB Micro-B port, only the single green LED lights up on the Boss DAC, and it does not play sound. It is now not detected by aplay. I tried two different power supplies and both produce the exact same results. What does this mean?
  5. I'm using two Raspberry Pi 5V 3A power supplies. RPi is connected to Ethernet to my network router. 1) I removed J25 jumper from Boss 1.2 DAC pcb. 2) I connected the supply with USB-C connector to the Boss 1.2 DAC USB-C port. 3) I waited for 10 seconds. Noticed that only one LED is lit on the DAC board. 4) I connect the supply with the USB Micro-B connector to the RPi USB Micro-B port. 5) RPi booted. I waited until only the red LED was lit. Only the one green LED is lit on the Boss DAC board. 6) I loaded Moode from http://moode 7) Click 'Play' in Moode. Result is MPD Error: Failed to open "ALSA default" [alsa], Failed to open ALSA device "hw.0,0" : No such file or directory 8) From puTTY, I ran aplay -l Result is pi@moode:~ $ aplay -l aplay: device list:270: no soundcards found... 9) Shutdown Moode. Removed all power from RPi and Boss DAC boards. 10) Replaced jumper onto J25. 11) Connected power to RPi USB Micro-B port only. 12) Rebooted, but still Boss DAC will not play. MPD Error displays in Moode. Only one LED lit on Boss DAC. 13) I set i2s audio device to None, then clicked SET. 14) Set i2s device to Allo Boss DAC, then clicked SET. 15) Rebooted RPi and Moode. 16) Finally, both green LEDs are lit on Boss DAC. Moode is able to play music. 17) Opened puTTY, ran aplay -l . Result is pi@moode:~ $ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: BossDAC [BossDAC], device 0: Boss DAC HiFi [Master] pcm512x-hifi-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 __________________________________________ I hope that provides useful information.
  6. I am applying single power fed through RPi micro B USB. That is working well. I earlier tried single power fed through Boss 1.2 USB-C connector, and that works too. I will run command aplay -l when I get home this evening and post results. Do I run this with single power, or attempt it with 2 separate power supplies to RPi and Boss 1.2? Also, confirming order of power up for devices is: 1) Apply power to Boss 1.2 USB-C connector 2) Apply power to RPi. Is that correct? I may have been applying power to the RPi first, then the Boss 1.2. Hopefully that is the solution to the problem. I will reply here.
  7. I have an Allo Boss DAC 1.2 installed on a Raspberry Pi 3B+ running Moode 4.3. 1) If I have J25 installed and power the DAC and Pi from a single 5V power supply, music plays, all works. On the Boss DAC, both the power LED and LED1 light up (green). 2) If I remove J25 and use two 5V DC power supplies, one to the Boss DAC USB-C and the other to the RPi3B+ USB Micro-B, it seems the DAC does not work. Only the power LED lights up, but LED1 remains dark no matter what. When I try to play a music file, I get this error: MPD errorFailed to open "ALSA default" [alsa]Failed to open ALSA device "hw0,0" Nosuch file or directory It appears the DAC is not working with J25 removed. What could be causing this? Output from cat /var/log/moode.log : pi@moode:~ $ sudo cat /var/log/moode.log20181211 212124 worker: - Start20181211 212124 worker: Successfully daemonized20181211 212124 worker: Integrity check ok20181211 212125 worker: Session loaded20181211 212125 worker: Debug logging (off)20181211 212125 worker: - Platform20181211 212126 worker: Host (moode)20181211 212126 worker: Hdwr (Pi-3B+ 1GB v1.3)20181211 212126 worker: Arch (armv7l)20181211 212126 worker: Rasp (9.4)20181211 212126 worker: Kver (4.14.76-v7+)20181211 212126 worker: Ktyp (Standard)20181211 212126 worker: Gov (performance)20181211 212126 worker: Rel (Moode 4.3 2018-09-27)20181211 212126 worker: Upd (2018-10-19)20181211 212126 worker: MPD (0.20.20)20181211 212126 worker: USB boot enabled20181211 212126 worker: File system expanded20181211 212126 worker: HDMI port off20181211 212127 worker: File check ok20181211 212127 worker: - Network20181211 212127 worker: eth0 exists20181211 212127 worker: eth0 (192.168.0.105)20181211 212127 worker: wlan0 exists20181211 212127 worker: wifi country (US)20181211 212127 worker: wlan0 SSID is blank20181211 212127 worker: eth0 addr exists, AP mode not started20181211 212127 worker: wlan0 address not assigned20181211 212127 worker: - Audio20181211 212127 worker: ALSA outputs unmuted20181211 212127 worker: ALSA card number (0)20181211 212127 worker: Audio out (I2S audio device)20181211 212127 worker: Audio dev (Allo Boss DAC)20181211 212127 worker: ALSA mixer name (Digital)20181211 212127 worker: MPD volume control (disabled)20181211 212127 worker: Hdwr volume controller exists20181211 212127 worker: Chip options (Burr Brown PCM5122)20181211 212127 worker: - Services20181211 212127 worker: Reset renderer active20181211 212129 worker: MPD started20181211 212129 worker: MPD scheduler policy (time-share)20181211 212129 worker: Configure MPD outputs20181211 212129 worker: MPD output 1 ALSA default (on)20181211 212129 worker: MPD output 2 ALSA crossfeed (off)20181211 212129 worker: MPD output 3 ALSA parametric eq (off)20181211 212129 worker: MPD output 4 ALSA graphic eq (off)20181211 212129 worker: MPD output 5 ALSA bluetooth (off)20181211 212129 worker: MPD crossfade (off)20181211 212129 worker: - Music sources20181211 212129 worker: USB sources (none attached)20181211 212129 worker: NAS sources (none configured)20181211 212129 worker: - Miscellaneous20181211 212129 worker: Volume level (0) restored20181211 212129 worker: Maintenance interval (21600)20181211 212129 worker: Screen saver activation (Never)20181211 212129 worker: Watchdog started20181211 212129 worker: Ready20181211 212138 worker: Job i2sdevice20181211 212208 worker: Job mpdcfgpi@moode:~ $ Please help. I would like to be able to use the Boss DAC 1.2 with separate power supplies for DAC and Pi, since that is supposed to perform so much better.
  8. Did you ever find out the answer to your question?
  9. I never heard from anyone at Allo. - I did use two separate power supplies, one for the RPi3, one for the Boss DAC. That did not fix the problem. - This is on a RPi3 (not B+) running MoOde 3.84. - Again, the problem is that as soon as music plays through the DAC, the wireless access point disappears from the list in my phone, so the headless player is no longer controllable from the phone. - The problem is the same whether I use my Android 5.1 phone or my old Android 4.4.1 tablet. - Everything works fine with the RPi3 connected to PC through Ethernet, controlled from the PC. - Therefore, I believe the DAC is causing the RPi3's onboard wifi adapter to fail as soon as the DAC starts to operate. I have purchased an RPi3 B+ with 5GHz onboard wifi adapter. I hope to have that assembled soon. If the Boss 1.2 DAC works on the RPi3B+, then that would suggest the problem is interference in the 2.4GHz caused by the DAC is disabling the RPi3's onboard 2.4GHz wifi adapter. Right? I find it hard to believe that I'm the only customer here who has run into this problem. Anybody?
  10. It's now 16 June. I left my last update 9 June. To recap: - In Raspberry Pi 3 with 5V 3A power supply connecting to USB Micro-B port - MoOde Audio 3.84 in AP mode (headless, using built in 2.4GHz WiFi on RPi3) - 256GB USB memory stick for music storage - 8GB microSD card for OS - Allo Boss 1.2 (board rev1.4) with jumper open, 5V 2.5A psu - MoOde boots successfully, Boss DAC loads. - One tune plays, but then MoOde AP disappears from list of available access points in phone - From then on, MoOde cannot respond to input. Is hung. Even with separate power supplies for RPi3 and Boss DAC. Is there anything that can be done? Is there a defect in the Boss 1.2 DAC I purchased? --
  11. I tested with two separate power adapters, one for the RPi, the other for the Boss. Jumper open. DC adapters rated 5V DC, 2.5A and 3A. This worked fine for a couple of hours, but then the WiFi dropped. MoOde SSH had disappeared from the Android phone. I rebooted the RPi and the phone. Moode SSH was again seen by the phone. I could connect and start playback, but no sound played from the Boss. Then the Moode SSH disappeared from the phone and the WiFi connection dropped again. This is very frustrating because the DAC sounded absolutely fabulous while it was working, but it is not working reliably in my RPi 3 (last year's version).
  12. Is the problem due to RF interference, caused by the Boss DAC 1.2 clocks radiating RF that interferes with the RPi3 onboard WiFi? If so, is there some way to fix this? My setup is very standard, just a RaspberryPi 3 (about a year old) with Allo Boss DAC 1.2 powered by a single 5V DC SMPS. (Jumper is shorted on the Boss DAC 1.2.) Help?
  13. A clue, maybe... As soon as I hit Play, the MoOde AP disappears from the list of SSH 'devices' in my Android tablet's wireless network settings. I think that means the Allo Boss 1.2 DAC is knocking out the RPi3's built in WiFi adapter. That's why the MoOde UI becomes unresponsive; it's not receiving anything from the Android because MoOde is running headless with the Pi's WiFi knocked out. I swapped in a 3A rated 5V DC power supply but that didn't change anything. The Pi's WiFi adapter disappears as soon as music starts playing from the DAC.
  14. I'm running a Raspberry Pi 3 (about a year old) with MoOde 3.84. It's been working great with an older Boss DAC (it says "v1.2" on the pcb). I just received my new Boss DAC 1.2 (it says "v1.4" on the pcb). My understanding is that the Boss DAC 1.2 uses the same driver as the older version Boss DAC in MoOde. I installed the new Boss DAC 1.2 onto my Pi3's header and booted it up. MoOde did not complain of any problem, and music plays when I touch the play button. However, when I go back to pause playback, MoOde is hung, does not respond to input. I have to shut power off to stop playback. I took the new Boss DAC 1.2 off the Pi3, and put the older Boss DAC back on the Pi3. Rebooted MoOde. Press play, it plays. Press pause, playback stops. Just as it should be. I put the new Boss DAC 1.2 back on the Pi, same problem. So the Pi works fine with the older Boss DAC, but not with the newer Boss DAC 1.2. Do I need to use a different driver for the new Boss DAC 1.2 in MoOde 3.8.4? Does the newer Boss DAC 1.2 require more power from the power supply? The one I'm using is the one that came with the RPi3 Canakit, which I'm pretty sure is rated for 2.5A. Is 2.5A not enough?
×
×
  • Create New...