> For the complete documentation index, see [llms.txt](https://mugic-motion.gitbook.io/mugic-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mugic-motion.gitbook.io/mugic-r-documentation/about-mugic-r/technical-details-on-configuring-your-mugic-r.md).

# Technical Details on Configuring your MUGIC®

### Technical Details on Configuring your MUGIC®

The state of your device is stored in RAM while the device is running, and can be written to EEPROM (a more permanent storage that will keep its contents even if the device is powered off).  Upon powering on, the state is loaded into RAM from EEPROM.

All commands below modify the state, and these modifications will persist when the configuration is reloaded from EEPROM upon restart or after pressing the Reset button. They are automatically saved into EEPROM.  The hardware reset command (by pressing Power and Reset buttons simultaneously) will erase the state of the EEPROM and overwrite with the default / factory settings.

The state of your device consists of the following main parameters with the following values:

| name                                                    | This is the name of your device.                                                            | MUGICXXXXXX                                                     |
| ------------------------------------------------------- | ------------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
| <p>ap\_ssid</p><p>ap\_pwd</p><p>ap\_port</p><p><br></p> | SSID (network name) and PWD (password) for the wireless network in AP mode.                 | <p>MUGIC® </p><p>ConnectXXXXXX</p><p>mugicXXXXXX</p><p>4000</p> |
| <p>wifi\_ssid</p><p>wifi\_pwd</p>                       | SSID (network name) and PWD (password) of the wireless network joined while in Client mode. | <p>MUGIC® </p><p>NetworkXXXXXX</p><p>mugicXXXXXX</p>            |
| <p>wifi\_ip\[0-7]</p><p>wifi\_port</p>                  | Up to 8 wifi IP addresses to send data to, in client mode.                                  | <p>192.168.4.2 …</p><p>4000</p>                                 |
| loop\_delay                                             | <p><br></p>                                                                                 | 25ms (40Hz)                                                     |

{% hint style="info" %}
The most efficient way to publish data we have come about is over OSC messages, via WIFI, and turning off any non-essential measurements (which would then be published as 0) as indicated by the flags section in the next section.  Using this we can achieve a consistent 15ms loop-delay, and with occasional fluctuations even 10ms (but some measurements might occasionally be spaced apart by more than 10ms).
{% endhint %}

{% hint style="info" %}
It is possible to publish the data in raw (ascii) or Json mode, and we are currently researching the possibility of publishing MIDI format as well. Those can be selected as "Output Data Format" in the Configuration Web page.
{% endhint %}
