I noticed recently that my EON fan is no longer responding to the control scripts. I had the custom scripts from @NHHiker installed but I’ve created a fresh OS (64-bit Bullseye) on a new Micro SD card and getting the same results. I even created a fresh OS, installed the default Argon scripts, and set the fan to always on but no change.
The fan spins on boot so it’s getting power and the argononed service is running. This is the output from the Argon Configuration utility when I choose System Information and then Fan Speed…
--------------------------
TEMPERATURE INFORMATION:
CPU: 45.2°C
SDA: 40.0°C
SDB: 38.0°C
HDD MIN: 38.0°C
HDD MAX: 40.0°C
FAN CONFIGURATION INFORMATION:
Fan Temp-Speed cut-offs
1.0=100
HDD Temp-Speed cut-offs
1.0=100
FAN SPEED INFORMATION:
Fan Speed 100
--------------------------
It appears it thinks it’s running at 100% but it’s definitely not running - at all. Anyone seeing similar behavior or have any suggestions of what else to check?
There was a code change that modified the configuration for Debian installs, not Raspberry PI OS installs… I’m thinking it may be doing the wrong thing.
Actually that does help. It looks like GPIO.wait_for_edge is causing an runtime error. If this is the case, then any GPIO may be failing, this would prevent the setting the fan speed.
I’ll examine the code setup around the GPIO. I’m not getting home until 9pm this evening, so it may be a day or so.
OK, thanks again. I’m happy to provide any logs needed and perform any testing. I looked at the argoneon.log and mine started throwing errors on 08/12/24.
Since the default Argon scripts don’t seem to trigger the fan either, do you think this may be related to an OS update?
Only to be sure, do you have already made the case powerless (unplug the power supply) ? I know situations there the MCU of Argon ONE cases are stucked (disconnected from I2C bus) and then it’s needed to make it one time powerless to RESET. Perhaps the MCU in the EON case has the same behaviour.
Also it seems, during your troubleshooting attempt that you have installed the wrong script. You have installed the daemon for argononed not argoneond.
The script that runs the fans is argononed.py… for some reason Argon didn’t change the name, when they ported… Unfortunately I didn’t change the name either ;-(
But, unplugging and letting it sit for a moment might help depending on the design.
I upgraded everything on my PI, and still no issues. I rebooted and disabled SPI and I2C in raspi-config… no issues. I re-enabled SPI and I2C and … no issues.
Looks like I have to boot the latest to see what happens.
my log (with debugging):
Oct 05 24 21:31:36 561 [INFO] argononed service version 2023.02.10 starting.
Oct 05 24 21:31:36 561 [DEBUG] writing to fan port, speed 0
Oct 05 24 21:31:36 561 [DEBUG] Temperature (34.563) >= 30.0 suggesting fanspeed of 100
Oct 05 24 21:31:36 561 [DEBUG] Returning fanspeed of 100
Oct 05 24 21:31:36 561 [DEBUG] Returning fanspeed of 0
Oct 05 24 21:31:37 561 [DEBUG] writing to fan port, speed 100
Oct 05 24 21:35:21 561 [DEBUG] Temperature (32.615) >= 30.0 suggesting fanspeed of 100
Oct 05 24 21:35:21 561 [DEBUG] Returning fanspeed of 100
Oct 05 24 21:35:21 561 [DEBUG] Returning fanspeed of 0
Oct 05 24 21:36:21 561 [DEBUG] Temperature (32.615) >= 30.0 suggesting fanspeed of 100
Oct 05 24 21:36:21 561 [DEBUG] Returning fanspeed of 100
Oct 05 24 21:36:22 561 [DEBUG] Returning fanspeed of 0
Oct 05 24 21:37:22 561 [DEBUG] Temperature (32.128) >= 30.0 suggesting fanspeed of 100
Oct 05 24 21:37:22 561 [DEBUG] Returning fanspeed of 100
Oct 05 24 21:37:22 561 [DEBUG] Returning fanspeed of 0
Oct 05 24 21:38:22 561 [DEBUG] Temperature (32.128) >= 30.0 suggesting fanspeed of 100
Oct 05 24 21:38:22 561 [DEBUG] Returning fanspeed of 100
Oct 05 24 21:38:22 561 [DEBUG] Returning fanspeed of 0
Oct 05 24 21:39:22 561 [DEBUG] Temperature (32.615) >= 30.0 suggesting fanspeed of 100
Oct 05 24 21:39:22 561 [DEBUG] Returning fanspeed of 100
Oct 05 24 21:39:22 561 [DEBUG] Returning fanspeed of 0
Oct 05 24 21:40:22 561 [DEBUG] Temperature (32.128) >= 30.0 suggesting fanspeed of 100
Oct 05 24 21:40:22 561 [DEBUG] Returning fanspeed of 100
Oct 05 24 21:40:23 561 [DEBUG] Returning fanspeed of 0
Oct 05 24 21:41:23 561 [DEBUG] Temperature (31.641) >= 30.0 suggesting fanspeed of 100
Oct 05 24 21:41:23 561 [DEBUG] Returning fanspeed of 100
Oct 05 24 21:41:23 561 [DEBUG] Returning fanspeed of 0
I did notice that if I attempt to run:
sudo python /etc/argon/argononed.py FANON
I get similar errors to what you have posted:
Traceback (most recent call last):
File "/etc/argon/argononed.py", line 71, in <module>
GPIO.setup(PIN_SHUTDOWN, GPIO.IN, pull_up_down=GPIO.PUD_DOWN)
File "/usr/lib/python3/dist-packages/RPi/GPIO/__init__.py", line 696, in setup
_check(lgpio.gpio_claim_input(_chip, gpio, {
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/lgpio.py", line 755, in gpio_claim_input
return _u2i(_lgpio._gpio_claim_input(handle&0xffff, lFlags, gpio))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/lgpio.py", line 458, in _u2i
raise error(error_text(v))
lgpio.error: 'GPIO busy'
I wonder if there are two instances of the service running???
FYI: My fan is dead, dead, dead. Smells funny and I cannot turn it with air… I can move it with my finger, but it does not free spin.
Replaced fan, and everything is working. I cannot reproduce your issue…
I swapped my fan, too…just for grins - same thing. It just spins up on power on and then stops after 3-4 seconds.
I also did a continuity test on the cable that connects from the board at the bottom of the case to the combination fan controller/OLED module - all good.
My only thought at this point is that the OLED module/fan controller is bad, but still “good enough” to pass power to the fan on boot. Argon’s store does not sell this part, and I only found complete EONs for sale on eBay.