[SOLVED] Connecting to Server Issue


#1

Hello everyone,

Firstly, this looks great. I see the mighty @Patrick_Pagano is in here, which immediately made me smile. The internet just isn’t big enough, eh, Patrick? Fortunate for me.

I’m fairly comfortable using command lines, though by no means am I anything but amateur level here. I’m attempting to set up Modep. Thankfully, this documentation was so kindly provided:

https://blokas.io/modep/docs/Running-MODEP/

I’ve attempted to follow the steps outlined here. I’m easily able to connect to the MODEP wi-fi signal. No sweat there. However, when I attempt to visit the http://172.24.1.1 or http://modep.local addresses, neither seem to bring up anything. I’ve given this a shot on my laptop. My iPad gives me the following message:

“Safari could not open the page because the server stopped responding.”

I’m probably missing some glaringly obvious step here. But before I yank too many hairs out of my head, I thought I’d reach out and see if any of you have some insight here. Thanks a whole bunch, I appreciate it.

  • Joe

#2

Hi, first step would be to check the statuses of MODEP services:

sudo systemctl status jack
sudo systemctl status mod-host
sudo systemctl status mod-ui

In case there’s any services that don’t run, you can check its log by running:

sudo journalctl -u jack
sudo journalctl -u mod-host
sudo journalctl -u mod-ui

A short documentation on troubleshooting MODEP: https://blokas.io/modep/docs/Troubleshooting/


#3

Thank you, Giedrius. I really appreciate it.

My hope was to set this up without the Pisound, just to make sure I didn’t run into technical hurdles. I don’t want to burn up anyone’s time here.

Here’s a snippet of the MOD-HOST log:

– Logs begin at Tue 2018-09-11 20:26:50 UTC, end at Tue 2018-09-11 20:34:32 UTC
Sep 11 20:26:55 modep systemd[1]: Started MOD-UI.
Sep 11 20:26:57 modep systemd[1]: Stopping MOD-UI…
Sep 11 20:26:57 modep systemd[1]: Stopped MOD-UI.
Sep 11 20:26:57 modep systemd[1]: Started MOD-UI.
Sep 11 20:26:59 modep python3[556]: lilv_world_load_bundle(): warning: Replacing
Sep 11 20:26:59 modep python3[556]: lilv_world_load_bundle(): note: New version
Sep 11 20:26:59 modep python3[556]: Cannot connect to server socket err = No suc
Sep 11 20:26:59 modep python3[556]: Cannot connect to server request channel
Sep 11 20:26:59 modep python3[556]: jack server is not running or cannot be star
Sep 11 20:26:59 modep python3[556]: JackShmReadWritePtr::~JackShmReadWritePtr -
Sep 11 20:26:59 modep python3[556]: [W 180911 20:26:59 iostream:1126] Connect er
Sep 11 20:26:59 modep python3[556]: [W 180911 20:26:59 iostream:1126] Connect er
Sep 11 20:26:59 modep python3[556]: WARN: Missing file /usr/local/modep/mod-ui/d
Sep 11 20:26:59 modep python3[556]: ERROR: Failed to open HMI serial port, error
Sep 11 20:26:59 modep python3[556]: init() got an unexpected keyword argumen
Sep 11 20:26:59 modep python3[556]: Using HMI => False
Sep 11 20:26:59 modep python3[556]: cc start socket missing
Sep 11 20:26:59 modep python3[556]: Host failed to initialize, is the backend ru
Sep 11 20:26:59 modep python3[556]: jack client deactivated NOT
Sep 11 20:26:59 modep systemd[1]: mod-ui.service: Main process exited, code=exit
Sep 11 20:26:59 modep systemd[1]: Stopped MOD-UI.
Sep 11 20:26:59 modep systemd[1]: mod-ui.service: Unit entered failed state.
lines 1-23

I’m likely just too in over my head on this one. I’d really love to pick up a Pisound, just don’t want to end up running into debugging right off the bat. Do you suppose it could simply be an issue with the sound card I’m using?

Thanks a bunch for your time, really do appreciate it.


#4

Ah, that explains it - the image is configured to run with Pisound right off the bat. For other audio cards, you must reconfigure the jack service correctly. Did you do the steps outlined here:

https://blokas.io/modep/docs/Sound-Card-Setup/

In case you want to use the Raspberry Pi built-in output, for it to work, you have to also increase the buffer sizes (change -p 128 -n 2 to -p 512 -n 3) and use hw:0 in place of hw:pisound, that also increases the latency.


#5

It was the buffer size. Totally works like a charm now. This is brilliant. Thanks so much.