USB Idle timeout limit of 3600 seconds

[dave14305]

Is there a technical reason for the GUI imposed limit of 3600 seconds for the USB idle spindown? The actual sd-idle tool has no upper limit to the best of my knowledge.

I’m my case I want to set it to 4200 because I have a PC that backs up hourly, so I’d prefer the timeout to be slightly greater than an hour to prevent sleep/wake until there is no more backup activity on successive hours.

Not a big deal, and not related to any new firmware version. Just an old curiosity.

 

[ColinTaylor]

I don't think there's a reason. John's firmware lets you enter values up to 43200.

Try setting it manually:

# nvram set usb_idle_timeout=4200
# nvram commit

Although I guess that would mean that you couldn't "Apply" anything on that GUI page anymore (without setting a smaller number).

 

[dave14305]

I don't think there's a reason. John's firmware lets you enter values up to 43200.

Try setting it manually:

# nvram set usb_idle_timeout=4200
# nvram commit

I went that route, but the GUI enforces the 3600 when making other changes on the System page. It’s one of the small differences I miss from the fork!

 

[RMerlin]

This was most likely done by Asus when they added it to the stock firmware, and their limitation was then merged into my code. I can increase that, but note that I cannot allow more than 9999 however, since the nvram max length for that parameter is four characters.

 

[dave14305]

This was most likely done by Asus when they added it to the stock firmware, and their limitation was then merged into my code. I can increase that, but note that I cannot allow more than 9999 however, since the nvram max length for that parameter is four characters.

That would work just fine for me. Thanks.