Thanks for pointing this out. The datasheet is wrong here. It’s actually connected via a mosfet to P1.04/LED2 in the RAK4630, same that drives the onboard blue LED.
Interesting Xose! Pardon my ignorance but I don’t follow the consequences of the mosfet and the behavior of the P1.04/LED2 functionality. The mPCIe electromechanical specifications document describes the LED_WWAN# pin behavior as “Open drain, active low signals.” and “shall be capable of sinking to ground a minimum of 9.0 mA at up to a maximum VOL of 400 mV”.
Is the RAK4630 LED2 pin active low? Does it sink current to ground?
I haven’t so far seen any activity on the WWAN light on my laptop. Maybe it’s that the arduino bootloader and / or meshcore firmware doesn’t interact with the pin? But I find that unlikely since nerds love blinking LEDs… what do you think?
In Ubuntu, looking at sysfs, I don’t see anything promising exposed under /sys/class/leds . Do you know if the linux driver supports something like an leds trigger configuration in cfg80211 subsystem — The Linux Kernel documentation ? All I can find is the tty interface which doesn’t seem to have any LED setting.
Have flashed a bluetooth-enabled meshcore image to the RAK4631, and can confirm that the laptop WWAN LED now blinks as the bluetooth is waiting for connection.
So I guess to get the LED to be lit when the module is powered, or blink on LoRA transmit, would require a software change on the meshcore image?
Thanks for the pointer. I guess I can close this feature request as the hardware is capable.