I can use it to play UMIGURI just fine though. Purchased 2 weeks ago so it should have the latest firmware by default.
[00:00:00.000] (d68) INFO Loading config
[00:00:00.000] (d68) INFO Config file found at "C:\\Users\\user\\AppData\\Roaming\\impress labs\\slidershim\\config\\config.json"
[00:00:00.000] (d68) WARN Some(Config { raw: "{\"deviceMode\":\"tasoller-two\",\"outputMode\":\"kb-32-tasoller\",\"ledMode\":\"umgr-websocket\",\"disableAirStrings\":true,\"divaSerialPort\":\"COM1\",\"divaBrightness\":63,\"brokenithmPort\":1606,\"keyboardSensitivity\":20,\"keyboardDirectInput\":false,\"outputPolling\":\"100\",\"outputWebsocketUrl\":\"localhost:3000\",\"ledFaster\":true,\"ledColorActive\":\"#ff00ff\",\"ledColorInactive\":\"#ffff00\",\"ledColorAirActive\":\"#0086ed\",\"ledColorAirInactive\":\"#000000\",\"ledSensitivity\":20,\"ledWebsocketUrl\":\"localhost:3001\",\"ledUmgrWebsocketPort\":7124,\"ledSerialPort\":\"COM5\"}", device_mode: Hardware { spec: TasollerTwo, disable_air: false }, output_mode: Keyboard { layout: Tasoller, polling: Hundred, sensitivity: 20, direct_input: false }, lights_mode: UmgrWebsocket { faster: true, port: 7124 } })
[00:00:00.001] (d68) INFO Loading manager
[00:00:00.001] (d68) INFO Config saving...
[00:00:00.001] (5c28) INFO Manager thread started
[00:00:00.001] (d68) INFO Config saving to "C:\\Users\\user\\AppData\\Roaming\\impress labs\\slidershim\\config\\config.json"
[00:00:00.002] (d68) INFO Config saved
[00:00:00.002] (5c28) INFO Manager runtime started
[00:00:00.002] (d68) INFO Running tauri
[00:00:00.002] (5c28) INFO Rebuilding context
[00:00:00.002] (5c28) INFO Context creating
[00:00:00.002] (5c28) INFO Device config Hardware { spec: TasollerTwo, disable_air: false}
[00:00:00.002] (5c28) INFO Output config Keyboard { layout: Tasoller, polling: Hundred, sensitivity: 20, direct_input: false }
[00:00:00.002] (5c28) INFO Lights config UmgrWebsocket { faster: true, port: 7124 }
[00:00:00.003] (5c28) INFO Thread worker starting device
[00:00:00.003] (5c28) INFO Async worker starting output
[00:00:00.003] (8fcc) INFO Device finding vid 7375 pid 9011
[00:00:00.003] (5c28) INFO AsyncHaltable worker starting lights
[00:00:00.003] (376c) INFO UMGR LED websocket server listening on 0.0.0.0:7124
[00:00:00.042] (8fcc) ERROR Device not found
[00:00:00.042] (8fcc) ERROR Device setup failed: ShimError
[00:00:00.042] (8fcc) INFO Thread worker received stop device
[00:00:00.441] (9aa4) INFO Start signal received
I can use it to play UMIGURI just fine though. Purchased 2 weeks ago so it should have the latest firmware by default.
```
[00:00:00.000] (d68) INFO Loading config
[00:00:00.000] (d68) INFO Config file found at "C:\\Users\\user\\AppData\\Roaming\\impress labs\\slidershim\\config\\config.json"
[00:00:00.000] (d68) WARN Some(Config { raw: "{\"deviceMode\":\"tasoller-two\",\"outputMode\":\"kb-32-tasoller\",\"ledMode\":\"umgr-websocket\",\"disableAirStrings\":true,\"divaSerialPort\":\"COM1\",\"divaBrightness\":63,\"brokenithmPort\":1606,\"keyboardSensitivity\":20,\"keyboardDirectInput\":false,\"outputPolling\":\"100\",\"outputWebsocketUrl\":\"localhost:3000\",\"ledFaster\":true,\"ledColorActive\":\"#ff00ff\",\"ledColorInactive\":\"#ffff00\",\"ledColorAirActive\":\"#0086ed\",\"ledColorAirInactive\":\"#000000\",\"ledSensitivity\":20,\"ledWebsocketUrl\":\"localhost:3001\",\"ledUmgrWebsocketPort\":7124,\"ledSerialPort\":\"COM5\"}", device_mode: Hardware { spec: TasollerTwo, disable_air: false }, output_mode: Keyboard { layout: Tasoller, polling: Hundred, sensitivity: 20, direct_input: false }, lights_mode: UmgrWebsocket { faster: true, port: 7124 } })
[00:00:00.001] (d68) INFO Loading manager
[00:00:00.001] (d68) INFO Config saving...
[00:00:00.001] (5c28) INFO Manager thread started
[00:00:00.001] (d68) INFO Config saving to "C:\\Users\\user\\AppData\\Roaming\\impress labs\\slidershim\\config\\config.json"
[00:00:00.002] (d68) INFO Config saved
[00:00:00.002] (5c28) INFO Manager runtime started
[00:00:00.002] (d68) INFO Running tauri
[00:00:00.002] (5c28) INFO Rebuilding context
[00:00:00.002] (5c28) INFO Context creating
[00:00:00.002] (5c28) INFO Device config Hardware { spec: TasollerTwo, disable_air: false}
[00:00:00.002] (5c28) INFO Output config Keyboard { layout: Tasoller, polling: Hundred, sensitivity: 20, direct_input: false }
[00:00:00.002] (5c28) INFO Lights config UmgrWebsocket { faster: true, port: 7124 }
[00:00:00.003] (5c28) INFO Thread worker starting device
[00:00:00.003] (5c28) INFO Async worker starting output
[00:00:00.003] (8fcc) INFO Device finding vid 7375 pid 9011
[00:00:00.003] (5c28) INFO AsyncHaltable worker starting lights
[00:00:00.003] (376c) INFO UMGR LED websocket server listening on 0.0.0.0:7124
[00:00:00.042] (8fcc) ERROR Device not found
[00:00:00.042] (8fcc) ERROR Device setup failed: ShimError
[00:00:00.042] (8fcc) INFO Thread worker received stop device
[00:00:00.441] (9aa4) INFO Start signal received
```
I did indeed not install any custom firmware or anything. I assume I need that UART cable for that?
I'm also not too sure what to Google, I've tried variations of "tasoller hid firmware". Would very much appreciate any help.
I did indeed not install any custom firmware or anything. I assume I need that UART cable for that?
I'm also not too sure what to Google, I've tried variations of "tasoller hid firmware". Would very much appreciate any help.
you need the "custom" firmware but check first if you are already on v2 firmware (if not then you need the UART cable for upgrading). double press FN2 and see if your tasoller still send out keys. if not then you are on v2. https://github.com/icex2/tasollertools
you need the "custom" firmware but check first if you are already on v2 firmware (if not then you need the UART cable for upgrading). double press FN2 and see if your tasoller still send out keys. if not then you are on v2. https://github.com/icex2/tasollertools
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I can use it to play UMIGURI just fine though. Purchased 2 weeks ago so it should have the latest firmware by default.
I am 99% sure your tasoller is running keyboard firmware instead of HID firmware. Please search around on how to get the HID firmware installed.
I did indeed not install any custom firmware or anything. I assume I need that UART cable for that?
I'm also not too sure what to Google, I've tried variations of "tasoller hid firmware". Would very much appreciate any help.
you need the "custom" firmware but check first if you are already on v2 firmware (if not then you need the UART cable for upgrading). double press FN2 and see if your tasoller still send out keys. if not then you are on v2. https://github.com/icex2/tasollertools
Issue was indeed with not having the right firmware installed on my board. Works as intended.