Nano Digi USB support

[Martin-By]

Hi,
I am not profession in linux coding, but could install the executable files within /usr/local/bin.
Running "minidsp" it returns: "Error: No devices found"

The Device is found by system:
lsusb: Bus 003 Device 002: ID 04d8:003f Microchip Technology, Inc. nanoDIGI v2.6

and mapped as hidraw0:
crw-rw-rw- 1 root root 242, 0 Jun 13 11:09 /dev/hidraw0

within "/etc/udev/rules.d" I created a file "50-minidsp_usb.rules"
SUBSYSTEM=="usb", ATTR{idVendor}=="04d8", ATTR{idProduct}=="003f", MODE="0666"

ubuntu@musicserver1:~$ cat /sys/class/hidraw/hidraw0/device/uevent
DRIVER=hid-generic
HID_ID=0003:000004D8:0000003F
HID_NAME=miniDSP LTD. nanoDIGI v2.6
HID_PHYS=usb-0000:00:1d.1-1/input0
HID_UNIQ=
MODALIAS=hid:b0003g0001v000004D8p0000003F

root@musicserver1:/dev/input# minidsp probe
thread 'main' panicked at 'index out of bounds: the len is 2 but the index is 2', protocol/src/commands.rs:575:53
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

What I am doing wrong with my setup to use minidsp?

My Device: MiniDSP_2x8_nanoDIGI_204
Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64)

[mrene]

Hi! I think you're the first one to try it out with a nano-digi!

At first glance it seems that there is a slight difference in how the device responds with it's hardware id - could you try this: minidsp -vvv probe - it would still crash but I'm hoping it'll print some packets before :)

A successful run would start with:

Sent: [31]
Sent: ReadHardwareId
Recv: [31, 01, 0a, 0a]
Recv: HardwareId { payload: [01, 0a, 0a] }

Alternatively, RUST_LOG="minidsp=trace" minidsp probe would also yield something comparable.

[2021-06-16T21:35:42Z TRACE minidsp::transport::multiplexer] send: ReadHardwareId
[2021-06-16T21:35:42Z TRACE minidsp::transport::hid::stream] read: [05, 31, 01, 0a, 0a, ff, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 04]
[2021-06-16T21:35:42Z TRACE minidsp::transport::multiplexer] recv: HardwareId { payload: [01, 0a, 0a] }

[Martin-By]

So now the result for my NanoDigi device:

root@musicserver1:/etc/environment.d# RUST_LOG="minidsp=trace" minidsp probe
[2021-06-17T08:39:08Z TRACE minidsp::transport::multiplexer] send: ReadHardwareId
[2021-06-17T08:39:08Z TRACE minidsp::transport::hid::stream] read: [04, 31, 02, 09, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, 02]
[2021-06-17T08:39:08Z TRACE minidsp::transport::multiplexer] recv: HardwareId { payload: [02, 09] }

ubuntu@musicserver1:~/.local/share$ sudo minidsp -vvv probe
[sudo] password for ubuntu:
Sent: [31]
Sent: ReadHardwareId
Recv: [31, 02, 09]
Recv: HardwareId { payload: [02, 09] }
thread 'main' panicked at 'index out of bounds: the len is 2 but the index is 2', protocol/src/commands.rs:575:53
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

[mrene]

Thanks, I made a tentative fix, can you try this build and let me know if it works?

[Martin-By]

Hi, today I used an Android App to use the Master Gain to create a Command File:
commands3.txt

I hope there is some useful code available from this.
Best regards, and thank you for this piece of code, I enjoy!
Martin

[mrene]

Ah, this confirms the command being sent by minidsp-rs is already the right one, and the werid device response should not be considered as an error but as a different kind of acknowledgement.

[Martin-By]

The send command for Master Gain by Android APP did not change Level of Master Gain on the minidsp board.

[mrene]

Oh that is unfortunate :(

[Martin-By]

Yeah, I forgot to make clear in my earlier post, sorry for that.