the-via / firmware Goto Github PK

i tried compiling and flashing the via .hex file with qmk. i also downloaded preonic_rev1_via.hex from caniusevia.com firmware downloads page and flashed it. but the keyboard is not detected with either .hex file. what can i do to get my preonic rev1 to be detected by via?

Does anyone know if the apex 5 is supported?? I find no mention of it online.

I recently installed VIA on my YMD75v3 and I found that the Enter key and the |\ key are swapped in VIA

I am using the firmware from
https://www.caniusevia.com/docs/download_firmware
the filename is ymdk_ymd75_rev3_via.hex

the enter key on the phisical keyboard is recognised as the |\ key
and the |\key is recognized as enter
they just need to be swapped for the layout to be correct

Same problem if I enable the ISO enter key (which is the layout that I am using)

pressing the physical enter key lights up the |\ key

same thing here but with the ANSI enter key

Please fix this.

This commit broke underglow toggling in Instant60. Found other reports of the same symptom and tested it on 2 Instant60 PCB:

385d6e7#diff-434e2deeddbf4ebb7f2e2e948c50ae8c4d2c4d5df1d63b85663411467823d2df

This appears to be the last working version:
https://github.com/the-via/firmware/blob/fc223789a3a00157ccb068af61a2c3ea17f90947/cannonkeys_instant60_via.bin

any chance that we could see updated option to select the newer "twinkle" animation in VIA. It's quite nice.

I have modifier keys like the following MT(MOD_LCTL | MOD_LSFT,KC_Y). The issue is that during my normal typing, when I tap this key, it defaults to the holding key first, not the tap. This is the case for every key where I have such a similar modifier. This makes my keyboard almost infeasible to use. How can I resolve this issue? Is there anyplace that I can specify what the default delay time should be? Thanks!

Hi, the bm60ec firmware provided by krepublic doesnt seems to be recognised by VIA, any ideas?

RGB locks up and the keypad is unresponsive, when connected to a computer running Windows, the numpad works just fine.

I downloaded the Skog Lite firmware from https://caniusevia.com/docs/download_firmware. It flashed successfully using QMK Toolbox and the keyboard is working properly, however, it does not show up in the VIA UI.

Just wondering if the team can add support to the preonic? Thanks

Hi Wilba/Olivia,

I hope this is the right place to report this issue.

The VIA firmware .bin file for the Iron165 is currently incorrect on the website. It is not compiled with the VIA_ENABLE=yes makefile flag so we have seen a lot of people running into an issue when flashing their PCB's.

I have committed a fix for this and all that needs to be done is to re-compile the firmware from top of tree and re-upload it.

QMK PR: qmk/qmk_firmware#9298

Thanks for the hard work!

Would love to see support for the Leopold FC980C Hasu controller. The FC660C is already supported and I understand that the boards are very similar.

Looks like HHKB support was merged in with the-via/keyboards#71 and the website now says it supports HHKB and HHKB JP, but there is no firmware download for the HHKB listed.

I just got my PC Godspeed75, I flashed it and it's detected by VIA and I can remap keys, but when using the fn to try to enable underglow, nothing happens nor does anything happen when going to the Lighting tab on the left, I just get a blue window, causing me to restart VIA

Would love to see support for Voice65 firmware.

Please add support for Keychron Q60

Far be it from me to understand the creative decision of using a git repository for binary blobs that both requests that you do not download files from it or send pull requests to it, however the ability to see that information lies below a 1000 line file list:

Does this actually make sense to have all firmware (not to be downloaded) in the root directory of the repository and not a subdirectory where users can easily see that they shouldn't be using this firmware?

Somewhat related, the wording of the about box: DO NOT DOWNLOAD FIRMWARE FROM HERE..... GO TO conflicts with the README.md: Firmware is more easily downloaded from here:, both linking to the same place. So which is it? Should the firmware not be downloaded from this repository, or is this firmware identical too and more easily downloaded from the provided link?

The website says it's supported (https://www.caniusevia.com/docs/supported_keyboards) and the source seems to exist (https://github.com/the-via/keyboards/tree/master/src/drop/alt), but I don't see it listed on the downloads (https://www.caniusevia.com/docs/download_firmware) or in this repo. Is it possibly named something else or is it actually missing?

My keyboard stops working after my laptop goes to sleep. I saw this new commit and thought it was a software issue so I flashed my keyboard but after flashing I have all sorts of other issues:

• I cannot change the settings through Via anymore (Via and my keyboard get frozen when I change the settings)
• If I don't turn the lighting off with the short keys, my keyboard starts randomly triggering switches.

Could you please let me know if it's a software issue or a hardware/PCB issue?

^ Title...
it's my favorite keyboard for years. I would love to customize it with VIA :(

Hello,
I am glad to become a user of this project. I am reading a lot of docs to configure my keyboard Keycron Q10.
I find a very good feature of QMK - [mod-tap] (https://docs.qmk.fm/#/mod_tap)

However, this is a little bit buggy with VIA. I configure space to MT(MOD_LCTL, KC_SPC). This works fine when I type slowly, but if I type quickly, the space is lost and become ctrl + <next_key_I_typed>. this is very annoying and make it hard to use.

I figured out there is one option for [tap_hold] (https://docs.qmk.fm/#/tap_hold) - TAPPING_TERM.
I think this issue can be resolved by adjusting this option. However, I cannot find any place to configure this. I neither didn't find anything useful from VIA's doc.

Please check this and add support to configure it if possible!

Regards,
Lesca

Hi team

I'm using the dz65rgb PCB, and just wondering if there's an easy way to add an extra layer on top of VIA's default, i.e. 5th layer with the layer no. 4? Going through QMK, changing configs and recompile the hex file for VIA seems to be a bit too much. Thanks.

Is there plan to support configuring tap-hold keys?

I was setting up my keyboard and accidentally reassigned FN to f12. The funny thing is that I can’t delete the keyboard settings, nor switch to wired mode to destroy all the settings. I checked from the manual that the settings can be erased, but the keyboard does not respond to pressing space + backspace at the same time; they do nothing.

As the title says, and a few Reddit threads I came across. There is some issue with the firmware on the U80-A PCB, at least the SEQ 2 Hotswap version maybe more I haven't tested my solder ones yet, where intermittently the keyboard becomes completely unresponsive to any computer I connect it to, macOS or Windows. Refreshing it with the firmware directly from the VIA website in QMK Toolbox will temporarily fix the issue.

Please advise.

I am using a Discipline keyboard and have tested the switches:

Is this anything someone has experienced before, or anything someone recommends I can do to continue to troubleshoot? I have tested this on both mac and pc, and the sound media keys are not functioning.

Thank you!

I want to know if there is any screen support in VIA?

When you program a key with MT(MOD_RALT,KC_SPC), it is saved as MT(MOD_LALT | MOD_RALT,KC_SPC). Both with the app and the website.