Cannot change config

abliss00

I uploaded 1.cfg (converted from my tw3 layout). FW v2.13. Paired and connected over bt in the default layout. I press T0F4M and it always blinks 3 green lights and stays in default.

When I plug in and mount the USB storage, I see my 1.cfg and no log:

-rwxr-xr-x 1 root root 1736 2015-12-31 18:00 0.CFG
-rwxr-xr-x 1 root root 0 2015-12-31 18:00 0.LOG
-rwxr-xr-x 1 root root 393 2024-07-30 19:04 1.CFG
-rwxr-xr-x 1 root root 0 2015-12-31 18:00 1.LOG
-rwxr-xr-x 1 root root 0 2015-12-31 18:00 2.CFG
-rwxr-xr-x 1 root root 0 2015-12-31 18:00 2.LOG
-rwxr-xr-x 1 root root 0 2015-12-31 18:00 3.CFG
-rwxr-xr-x 1 root root 0 2015-12-31 18:00 3.LOG

How to debug further?

Edit: copying the default config to 1.cfg works. Something seems to have gone wrong in converting my layout, which I now realize was v4. Ah well. I guess I have to make it again from scratch.

Edit: the web tuner is so agonizingly slow. I see there is a csv export, but how can I import an edited csv? That would be so much faster.

datacyclist

abliss00 I had the same problems. I uploaded configurations from the tuner to the device as 1.cfg or 2.cfg, could then cycle to these configurations, but got stuck there, i.e. couldn't cycle further. Something must have gone wrong in the tuner, because when I recreated the exact same config again, it worked. This happened a few times and I couldn't pinpoint it. My upload to the device works reliably, I can rule that out.

+1 for the CSV file upload, this has already been requested multiple times.

I can also confirm the slow and sometimes sluggish tuner interface. In like 30 percent of the time I get cloudflare errors and timeouts.

Geoff

Rather than starting from scratch, consider copying your old layout (without converting it), editing it to remove anything unusual and then convert that to the latest version.

You can also open a support ticket and attach the non working layout.

Tony

Copy cfg to Twiddler
UNPLUG USB <---- this stage writes to the onboard storage
Use the Twiddler as usual (USB or BT) new configs will be active.

If you do not unplug the USB, it looks like it has written to the storage but it has not. It is in an intermediary location that the Twiddler firmware does not read.

datacyclist

Before step 2, you might want to eject the device per the Windows dialog (if you're on windows) or unmount it explicitly if you're on Linux (and probably Mac, too). Depending on how the mounting happened, changes to the file system might not be written instantly to the device, but rather when you unmount/eject it -- before it gets unplugged.

The CFG file size is negligible, though, so it might get written instantly to the device, but I've seen enough corrupted filesystems due to this misunderstanding.

Tony

datacyclist EJECT if it makes you feel better. We have found that it doesn't make a difference for T4 as the storage topology is different. While T4 presents as storage medium, there is more going on in the background. The real storage is obfuscated and writing occurs when you unplug the USB. The T4 writes files to its storage and reads those files back to present them to the host in a storage like metaphor.

This way, T4 only stores files in knows about and removes files it doesn't know about. Unlike the T3, the T4's storage is very limited and specific.

datacyclist

Tony That's true for the T4 side of operations. However, I was thinking about the OS side. For example, if you unplug a USB drive that was mounted with the async option without waiting for the actual write process to finish first, you may have data loss. Explained, e.g. here: https://www.baeldung.com/linux/sync-vs-async-mount-options Might not be an issue due to the extremely small file sizes for the T4 anyway, but just in case.

abliss00

Thanks all. The problem was that the CFG I downloaded from the tuner was in the old v4 format and the T4 couldn't read it.

Maybe in a future firmware version, the T4 could blink a red LED to indicate that it failed to parse 1.CFG, instead of pretending that it doesn't exist and staying on 0.CFG?

samuelwlinton

I'm not sure that this is related at all, but here goes.

I just updated to firmware version 3.2, and ever since then, I have not been able to upload my custom config files to the Twiddler. I drag them onto the Twiddler disk, and it appears that they are there. But when I disconnect the USB, and reconnect, the original files are still there. This works with any file I try to upload.

I am on Windows 11.