Qmk_firmware: redox wireless, D4 on receiver

Created on 19 Feb 2020  路  8Comments  路  Source: qmk/qmk_firmware

Hello,
I noticed that the redox wireless has a fourth led on the receiver labeled D4.
However, only three of the leds seems to be controllable from the firmware. Is there any reason for this?
Is it possible to control the fourth led ? It will be a real advantage!

help wanted question stale

Most helpful comment

Hi,
actually yes it's perfectly usable. Here I put a few references on how to use it with the old API. It's been some time since I wanted to merge the 4th led code upstream using the new API but never find the time to actually work on it, I'm sorry.

All 8 comments

@mattdibi Could you please advise?

Hi,
actually yes it's perfectly usable. Here I put a few references on how to use it with the old API. It's been some time since I wanted to merge the 4th led code upstream using the new API but never find the time to actually work on it, I'm sorry.

Thanks for the link, I'll take a look at it. What do you mean by the old api? How is this led different from the other three?

What do you mean by the old api?

Now there's a higher level API to control LEDs but is more readable and easier to use.

How is this led different from the other three?

It is not. It's exactly the same and should be used the same way.

But is there code to use D4 right now? Like the existing defs to turn on the blue led, magenta color and such?
I'm not interested on caps lock or that stuff, I just want to turn them on and off based on my own logic

But is there code to use D4 right now? Like the existing defs to turn on the blue led, magenta color and such?

No, there isn't. You need to add the changes I implemented here and add your own logic.

Hope this helps.

This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs.
For maintainers: Please label with bug, in progress, on hold, discussion or to do to prevent the issue from being re-flagged.

This issue has been automatically closed because it has not had activity in the last 30 days. If this issue is still valid, re-open the issue and let us know.

Was this page helpful?
0 / 5 - 0 ratings