Is it possible to use the control scripts on the DXP480T? #6
Comments
|
I think it is possible to control the power LED, but we need to probe each of these addresses. According to what I see from the driver, you can read bytes from registers at # replace <chip addr> below with the addresses you see from i2cdetect, which is (in your case) 0x08, 0x26, ...
i2cget -y 0 <chip addr> 0x5a b
i2cget -y 0 <chip addr> 0x5b b
sleep 5
i2cget -y 0 <chip addr> 0x5d bIf I am correct, the chip for the power LED will return |
|
This is the result of the few commands for my chip address: |
|
Good to see that, it seems It seems the relevant registers at chip
i2cset -y 0 0x26 0x50 0 b
i2cset -y 0 0x26 0x51 0 b
i2cset -y 0 0x26 0xb1 2 b
i2cset -y 0 0x26 0xa0 1 b
I guess you can search these undetermined values and try to figure the meaning of them. Update: Given that |
|
For reading the status, you can try registers starting from |
|
For blinking and breathing, one pattern is:
Finally, for consecutive writes, you may need to add a sleep between them. |
|
With the following code, I was able to stop the LED from flashing. That was very annoying. I assume that the color cannot be changed, it seems to be a white LED. Not an RGB LED. Even though I haven't quite understood what each line of it does. I think |
|
I do not know the exact meaning of them, neither. It was found in the de-compiled code of the kernel module named Basically, I think I guess to turn-off the light, you can use # change only one register
for i in $(seq 0 7); do
i2cset -y 0 0x26 0xb1 $i b
sleep 1
done
# change two registers
for i in $(seq 0 7); do
for j in $(seq 0 7); do
i2cset -y 0 0x26 0xb1 $i b
sleep 0.5
i2cset -y 0 0x26 0xa0 $j b
done
sleep 1
done |
|
I have found out which commands are suitable for what. Fast flashing Slow flashing Breathing slowly No slow Flashing / breathing Colors: White LED on after off If both LEDs are on, the one that was switched on first wins. |
|
Summarized here, every possible LED function that seems to exist. |
|
Oh nice I just knew it was on the HDD Nas systems. What would that look like if you wanted to use it? I've never worked with anything like this before. |
|
My primary concern was that the power LED kept flashing after I replaced the UGOS with a different OS. That's why I wanted to know how to control the LED. I found out with the help of this repo and the developer. Now a script always runs when the system boots, which sets the LED to permanently white. |
|
@blaugrau90 Great to hear that! It seems we now have full control of the power LED on DXP480 Plus. @Erani0 I guess in UGOS the light will also indicate device faults. If you want to use it in such a way, you must write a script (e.g., |
|
I use Proxmox now An i have no idea ro write Linux scripts |
|
TrueNAS Scale, no output from i2cdetect -l ... |
|
do you load the i2c-dev module? please check the output of lsmod.
…On Sat, Jun 15, 2024, 02:52 YugiFanGX ***@***.***> wrote:
TrueNAS Scale, no output from i2cdetect -l ...
—
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABBGJTAFNQOWWRJYJQLNLNDZHM3WPAVCNFSM6AAAAABJA7Y4T6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRYGU4DGMBVGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
That solved the issue. Thank you! |
|
I'm passing the SATA controllers for Proxmox into a TrueNAS VM and I believe the passing of the controllers may be affecting the device IDs? None of the commands in the exhaustive list above work and I get an Here is the output of i2cdetect -l and i2cdetect -y 0 in TrueNAS VM: Here is the output of i2cdetect -l and i2cdetect -y 0 in Proxmox: |
|
@Dataninja126 at the moment you cannot use this tool in a VM -- it should be run in the host (i.e., your proxmox); for the outputs in proxmox, is |
Sorry I must have accidently omitted that line and I have the 6800Pro |
Have you tried the cli tool in proxmox? I think it will work. This issue and the commands above are about 480T -- it is different from other HDD models. |
Well, the script worked in a sense that it stopped the trailing lights, but because the SATA controllers are passed through it's triggering the following: |
I think this is an expected behavior, supporting this case will be complicated, though it is possible. |
Thanks for the quick replies. I'm okay with the lights not flashing. Because I'm not well versed in this space, I was considering passing through i2c-0, but not sure how that would affect my Proxmox system... Edit: nevermind, I'm not going to try, quick google search it supports critical functions of motherboard/periphal communication. |
@blaugrau90 can you please share this script? I have the same machine and tried Proxmox, not sure why it kept flashing until now. I also get random reboot and intermittenly lose Web GUI Proxmox activity. Have you experience that? Thanks. |
|
I have installed Windows Server 2025 on my DXP480T after some hardware upgrades. |
@blaugrau90 I agree with the previous speaker. It would be great if you could make your script available here. Many thanks in advance! |
|
@bangity @miskcoo Maybe you can add what comes next to your repo / wiki. I'll share how I implemented this. First, we need two scripts that control the LED after booting and when shutting down. We then create startup and shutdown services that use these scripts. Here is a detailed description of how this works. To ensure a script runs during boot and another during shutdown on Debian, you can use the init system settings. Depending on the version of Debian, you can use startup-script.sh#!/bin/bash
i2cset -y 0 0x26 0xa0 1 b # red off
i2cset -y 0 0x26 0xa0 2 b # white off
i2cset -y 0 0x26 0x51 0 b # Slow Flash off
i2cset -y 0 0x26 0x50 0 b # Permanently on
i2cset -y 0 0x26 0xb1 2 b # white on
i2cset -y 0 0x26 0x50 1 b # Fast Flash on
sleep 10
i2cset -y 0 0x26 0xa0 1 b # red off
i2cset -y 0 0x26 0xa0 2 b # white off
i2cset -y 0 0x26 0x51 0 b # Slow Flash off
i2cset -y 0 0x26 0xb1 2 b # white on
i2cset -y 0 0x26 0x50 0 b # Permanently on
sleep 1
i2cset -y 0 0x26 0xa0 1 b # red off
i2cset -y 0 0x26 0xa0 2 b # white off
i2cset -y 0 0x26 0x51 0 b # Slow Flash off
i2cset -y 0 0x26 0xb1 2 b # white on
i2cset -y 0 0x26 0x50 0 b # Permanently onshutdown-script.sh#!/bin/bash
i2cset -y 0 0x26 0xa0 1 b # red off
i2cset -y 0 0x26 0xa0 2 b # white off
i2cset -y 0 0x26 0x51 0 b # Slow Flash off
i2cset -y 0 0x26 0x50 0 b # Permanently on
i2cset -y 0 0x26 0xb1 1 b # red on
i2cset -y 0 0x26 0x50 1 b # Fast Flash on
sleep 5
i2cset -y 0 0x26 0xa0 1 b # red off
i2cset -y 0 0x26 0xa0 2 b # white off
i2cset -y 0 0x26 0x51 0 b # Slow Flash off
i2cset -y 0 0x26 0xb1 1 b # red on
i2cset -y 0 0x26 0x50 0 b # Permanently on
sleep 1
i2cset -y 0 0x26 0xa0 1 b # red off
i2cset -y 0 0x26 0xa0 2 b # white off
i2cset -y 0 0x26 0x51 0 b # Slow Flash off
i2cset -y 0 0x26 0xb1 1 b # red on
i2cset -y 0 0x26 0x50 0 b # Permanently onRunning a script at boot
Running a script at shutdown
Summary
By following these steps, your startup script will run at system boot, and your shutdown script will run when the system is shutting down. |
|
Hi and thanks for sharing this :-) |
I have the DXP480T Full SSD NAS. Unfortunately, the scripts do not work here. The SMBUS I801 is present, but the script does not find any LEDs that it can control.
Here is the output of i2cdetect -l and i2cdetect -y 0:
Is there any way to adapt this so that it also works on this NAS? Currently the power LED flashes all the time. There are no other LEDs.
The text was updated successfully, but these errors were encountered: