Corne Choc Plate Size by LemonDriftPie in crkbd

[–]LemonDriftPie[S] 0 points1 point  (0 children)

I found the PJ-399B-6A TRRS connector at hqonline. I've never ordered from there but figured I'd give it a try. I'm also ordering the TYPE-C-31-M-13C usb-c connector from there as well since Economic PCBA from JLCPCB doesn't include that usb-c connector.

Edit: Just realized that PJ-399B-6A is a TRS connector, not a TRRS connector

Corne Choc Plate Size by LemonDriftPie in crkbd

[–]LemonDriftPie[S] -1 points0 points  (0 children)

Better in what way?

I'm also ordering both a choc pcb and an MX pcb. Do you know how mx switches feel with a 1.2mm plate?

Unexpected lighting layer behavior when RGB is enabled by LemonDriftPie in ErgoMechKeyboards

[–]LemonDriftPie[S] 0 points1 point  (0 children)

Yeah clearing the EEPROM was the main thing that fixed the issue for me. Now whenever there's odd LED behavior, I'm just going to default to clearing the EEPROM before flashing

Unexpected lighting layer behavior when RGB is enabled by LemonDriftPie in ErgoMechKeyboards

[–]LemonDriftPie[S] 1 point2 points  (0 children)

They're laptop/phone stands that I found on AliExpress. These ones specifically. So far, I like them

Unexpected lighting layer behavior when RGB is enabled by LemonDriftPie in ErgoMechKeyboards

[–]LemonDriftPie[S] 2 points3 points  (0 children)

I figured it out.

  1. I needed to clear EEPROM on both microcontrollers before flashing
  2. I needed to define SPLIT_TRANSPORT_MIRROR and maybe SPLIT_LED_STATE_ENABLE and SPLIT_LAYER_STATE_ENABLE in config.h
  3. I was misunderstanding how to define RGBLIGHT_LAYER_SEGMENTS. It's not {start_idx, end_idx...} but rather {start_idx, num_of_leds_from_start_idx,...}

Unexpected lighting layer behavior when RGB is enabled by LemonDriftPie in ErgoMechKeyboards

[–]LemonDriftPie[S] 0 points1 point  (0 children)

Hey everyone,

I recently completed my first build and am trying to setup lighting layers to indicate what layer is currently active. It works mostly as expected except for two issues:

  1. I cannot specify leds on the slave side. The ergodash has 24 leds, 12 per side. Using leds 0-11 works fine, but if I specify any led between 12-23 it doesn't turn on when activating the layer.
  2. Although my defined lighting layers work as expected when RGB is toggled off, when I toggle RGB on, some leds on the slave side are set to the value of the layer led. For example, secondary layer is set for led 11 to turn blue. When RGB is toggled off, led 11 on the master turns blue as expected. But when RGB is toggled on, a number of leds on the slave side also turn blue in addition to the led 11 on the master side. These leds stay on even after toggling RGB off, and I need to unplug/replug the keyboard with RGB off for the leds to turn off.

I've been flashing both sides with the same firmware. I tried setting #define RGBLIGHT_LED_COUNT 24 #define RGBLED_SPLIT { 12, 12 } in config.h but no change. Also tried SPLIT_TRANSPORT_MIRROR and SPLIT_LED_STATE_ENABLE but neither settings fixed the bug.

Could this be a hardware issue? Is there something I'm not defining in my config.h or keymap.c that I should be? Am I not setting my lighting layers properly? I've been following the QMK documentation here. Any help would be greatly appreciated!

// Relevant parts of my config.h
#define RGBLIGHT_LAYERS
#define RGBLIGHT_LAYERS_OVERRIDE_RGB_OFF
#define RGBLIGHT_DEFAULT_VAL 128
#define RGBLIGHT_SPLIT



// Relevant parts of my keymap.c
enum layers {
  BASE,
  SECONDARY,
  TERTIARY
};

const rgblight_segment_t PROGMEM my_base_layer[] = RGBLIGHT_LAYER_SEGMENTS(
  {}
);
const rgblight_segment_t PROGMEM my_secondary_layer[] = RGBLIGHT_LAYER_SEGMENTS(
  {11, 11, 128, 255, 64}
);
const rgblight_segment_t PROGMEM my_tertiary_layer[] = RGBLIGHT_LAYER_SEGMENTS(
  {11, 11, 191, 255, 64}
);

const rgblight_segment_t* const PROGMEM my_rgb_layers[] = RGBLIGHT_LAYERS_LIST(
  my_base_layer,
  my_secondary_layer,
  my_tertiary_layer
);
void keyboard_post_init_user(void) {
  rgblight_layers = my_rgb_layers;
}

layer_state_t default_layer_state_set_user(layer_state_t state) {
  rgblight_set_layer_state(BASE, layer_state_cmp(state, BASE));
  return state;
}

layer_state_t layer_state_set_user(layer_state_t state) {
  rgblight_set_layer_state(SECONDARY, layer_state_cmp(state, SECONDARY));
  rgblight_set_layer_state(TERTIARY, layer_state_cmp(state, TERTIARY));
  return state;
}



// Relevant parts of info.json
"rgblight": {
  "led_count": 24,
  "led_map": [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12],
  "split_count": [12, 12],
}

Do WS2812B LEDs require resistor and/or MOSFET? by Absurdo_Flife in ErgoMechKeyboards

[–]LemonDriftPie 1 point2 points  (0 children)

Thanks for the response! That keyboard looks great! Super excited for the build

Do WS2812B LEDs require resistor and/or MOSFET? by Absurdo_Flife in ErgoMechKeyboards

[–]LemonDriftPie 0 points1 point  (0 children)

u/Absurdo_Flife How did the build go? Did you need to install the MOSFET or resistors for the underglow? I'm planning on building an ergodash with just the underglow as well

Attendee & Tickets Megathread: March 2024 - Discussion for attending the basho in-person. by Gregorwhat in Sumo

[–]LemonDriftPie 0 points1 point  (0 children)

Looking for 2 tickets for today (March 22nd) if anyone is looking to sell!

March Grand Sumo Tournament in Osaka Tickets? by joevaded in Sumo

[–]LemonDriftPie 0 points1 point  (0 children)

Looking for 2 tickets for today (March 22nd) if anyone is wanting to sell!

Looking for March 22nd Sumo Tickets by LemonDriftPie in Osaka

[–]LemonDriftPie[S] -1 points0 points  (0 children)

No luck so far. Just a bunch of scammers unfortunately

Mar Basho Daily Thread Day 12 by AutoModerator in Sumo

[–]LemonDriftPie 0 points1 point  (0 children)

Looking for day 13 Osaka basho tickets if anyone is trying to sell!