My case of using Rpi0w is an external homebrew midi implementation of the BeatBuddy drum machine functionality in python.
Rpi0w is configured as usb gadget, pretends to be a usb midi device, and streams midi drum notes to my ModDuoX via MDX’s USB A, and also listens and syncs to MDX’s tempo.
Are you using WIFI on the Pi?
I use Rpi0w’s Wifi in the client mode for configuring my python drum app using flask-based web interface (composing drum songs from the library of midi clips) , but it has nothing to do with MDX web interface. There is only usb midi connection between rpi0w and MOD in my setup and nothing related to network.
Also drum midi is sensitive to timing, timing is sensitive to cpu usage, therefore I disable any midi processing when working with my Rpi0w’s web interface.
Never tried sending midi and providing web interface in the same time.
I was really looking for ways to connect via WIFI like I can with my PC.
If I understand correctly, you want to reach MOD’s web interface. My RPI0w case does not help with that.
If you need to reach MOD’s web ui via wifi you have two known options:
-
Using Mango router connected to Usb B (basically connecting cable you usually use for PC to Mango)
Work! Access over WiFi with GL.iNet GL-MT300Nv2
I’ve tried that, and it works. This way you get a Wifi AP you can connect to, and see MOD’s WebUI by IP. -
Most of the time I use a Wifi dongle connected to USB A of MOD. However, with this method MOD would be a Wifi client only, AccessPoint mode is still not implemented, you would need some existing wifi network to connect to. I connect MDX to my home WIFI network, and reach WebUI that way 90% of the time without additional usb cables.
WiFi - MOD Wiki