Skip to content

Contact

JP150PCB 1.3PCB 1.4Jan PřibyslavskýThis page does not apply to the product or PCB revision chosen in the header.

MURA LABS is a brand of DASH audio s.r.o. The product pages and the contact form are at muralabs.org.

What to include in a support request

The more of this comes with the first message, the faster the answer:

  1. The identity of the module. *IDN? in one line gives the model, the serial number and the firmware version, for example MURA LABS,JP150,JP150-0001-0021,26.10.1. MuraLink shows the same on Device > Status; the serial number is also on the factory record (SYS:BOARD:RECORD?).
  2. The board. SYS:BOARD:TYPE? (JP150-1.3, JP150-1.4, or UNSUPPORTED,...).
  3. The diagnostics. The answers of SYS:VERSION?, SYS:FW:PACKAGE?, SYS:RESET:CAUSE?, SYS:BOOTLOADER:INFO?, SYS:RTOS?, SYS:NVM:EEPROM:STATE? and, for a DSP problem, DSP:BOOT? and DSP:CORE:STATUS?. MuraLink shows them on Diagnostics > System and Software; a copy of both pages is enough.
  4. MuraLink's log. The file Logs/dsp-amp-YYYYMMDD.log next to the executable, or the text of Diagnostics > Log, from the session in which the problem occurred.
  5. What happened. The symptom, what was connected, what you did last, and whether a power cycle changes it. For a firmware update: the message MuraLink showed.
  6. Photos or a short video help with LED patterns and wiring questions.

Please do not send a module back before support has asked for it. The troubleshooting page covers the symptoms that need no support case.

A mistake on this site

The bug icon at the top of every page, next to its title, opens a problem report with the page's address already filled in; it needs a GitHub account. A wrong entry in the command reference is reported the same way. The site keeps no analytics and no record of its readers.