How to Manually Transfer Client Mesh and Config Files (DRAFT)¶
This guide covers how to manually transfer a client's existing calibration files (.mesh and .json) from an external USB thumb drive to the local system folders. This process is used when a customer has sent back modified files that need to be dropped into place.
To facilitate this process, you will use a command-line interface. Before beginning the file transfer, you must apply the following specific operational licenses to the target unit:
- License #1000 – Debug X Term
- License #1001 – Digitalis Staff Root Access
⚠️ Important License Expiration Rule: Set both licenses to expire exactly one day after you expect to complete this manual transfer.
What is Bash?¶
bash is the name of the program that runs the command-line interface (the terminal text window). It acts as the translator that takes the commands you type and passes them to the system's core to be executed.
Steps¶
Step 1: Download the Client’s Files¶
- Using your workstation (not the customer’s unit), navigate to: https://digitarium.com/refresh/logs/?C=M;O=D
- Locate the client’s most recent update and download the .zip file.
- Unzip the file locally and open it.
Locate the config.json file¶
Your file path should look similar to this:
/home/user/Downloads/7001014–2026-05-27T06_06_16/usr/share/warp/digitalis
- Action: Copy the config.json file to an empty external USB drive.
Locate the Mesh Files¶
Your file path should look similar to this:
/home/user/Downloads/7001014–2026-05-27T06_06_16/usr/share/warp/digitalis/mesh
- Action: Save the warp files to a blank external USB Drive.
Step 2: Open a Command Terminal¶
When your CU has started successfully and is projecting either on monitors or projectors, connect a USB keyboard and press Alt + X. This should bring up a command terminal on your display.
Note: If the configuration you are updating has a preview monitor, the terminal window may populate there even if you do not have the preview monitor plugged in.
💡 Troubleshooting: If Alt + X does not populate a terminal window, double-check that the license is enabled for your device in the license manager and update the unit.
Step 3: Locate the USB Drive¶
Find the exact mount path of the client files loaded onto the external drive using the following command:
Bash
lsblk
What to Expect: A list of storage devices will display on the screen. Look at the right-hand column labeled MOUNTPOINT. You are looking for a line that ends in /media/your_external_drive. If you don't see it, the USB drive isn't plugged in or recognized yet.
Step 4: Verify Client Files on the USB¶
Confirm that the client's mesh folder, .mesh files, and config.json exist on the drive before copying anything.
Bash
ls -l /media/your_external_drive/mesh
What to Expect: The terminal will display a list of files inside that USB folder. You should see config.json, warp1.mesh, and warp2.mesh. If the terminal says “No such file or directory”, double-check your spelling or use the Tab key to auto-complete the path.
Step 5: Copy Files to Local System¶
- Copy the Configuration File
This command copies only the configuration file into the main digitalis folder.
Bash
cp /media/your_external_drive/mesh/config.json /usr/share/warp/digitalis/
What to Expect: Absolute silence. The terminal will drop to a new, blank command line with no success message. If no error text appears, the configuration file transferred successfully.
- Copy the Mesh Files
This command utilizes a wildcard (*.mesh) to copy only the mesh files straight into the nested mesh subdirectory.
Bash
cp /media/your_external_drive/mesh/*.mesh /usr/share/warp/digitalis/mesh/
What to Expect: Absolute silence. Like the previous command, a successful copy will output nothing on the screen and present a fresh command line.
Step 6: Final Placement Check¶
Because the copy commands are silent, run these quick checks to confirm that everything is in its correct home and the job is complete.
- Check 1: Verify Main Directory
Bash
ls -l /usr/share/warp/digitalis/
What to Expect: You will see a list showing that config.json is sitting in this main folder along with the mesh/ folder wrapper. Because we targeted the copy paths directly, loose .mesh files will not appear out here.
- Check 2: Verify Mesh Subfolder
Bash
ls -l /usr/share/warp/digitalis/mesh
What to Expect: You should see warp1.mesh and warp2.mesh listed safely inside this subfolder.
Success: If both checks match this layout, the system is configured correctly!