New LED control is.....uh.........
Posted: Tue Oct 04, 2016 10:05 pm
.....one of the dumbest changes ever to Mikrotik ROS....
In revisiting using the LEDs on a radio card....411AH, 912, 435 boards....to indicate RSSI and link status, I was completely blown away when I tried to use a script I was using with ROS < 6.18, that I had to completely rewrite it to deal with the "new" way LEDs are turned on and off.
Who made this decision? The janitor?
The LEDs aren't just turned off and on anymore, and the process is now slower-than-molasses.....since now, using the recommended method, the script needs to "search" the configuration for an entry in the LED section that has a matching LED defined, modify that setting (LED), and then it saves it too NV MEM ALL THE TIME!!!!!!! on each change. (?) ....nice way to chew up NAND memory and wear it out prematurely.
And if the script is running when the box powers down, it leaves (as saved) the LEDs in they are and when rebooted, they are restored.
This wouldn't be too bad if there was a far better built in RSSI functionality (/system led/)...but there isn't. According to what I've been able to find, the built in RSSI can only indicate between a link (at around -90) and -61dBm.
In revisiting using the LEDs on a radio card....411AH, 912, 435 boards....to indicate RSSI and link status, I was completely blown away when I tried to use a script I was using with ROS < 6.18, that I had to completely rewrite it to deal with the "new" way LEDs are turned on and off.
Who made this decision? The janitor?
The LEDs aren't just turned off and on anymore, and the process is now slower-than-molasses.....since now, using the recommended method, the script needs to "search" the configuration for an entry in the LED section that has a matching LED defined, modify that setting (LED), and then it saves it too NV MEM ALL THE TIME!!!!!!! on each change. (?) ....nice way to chew up NAND memory and wear it out prematurely.
And if the script is running when the box powers down, it leaves (as saved) the LEDs in they are and when rebooted, they are restored.
This wouldn't be too bad if there was a far better built in RSSI functionality (/system led/)...but there isn't. According to what I've been able to find, the built in RSSI can only indicate between a link (at around -90) and -61dBm.