Argon One Replacement Daemon

[henkiew]

OK great. I have really no idea for the value. I already tried to change the branch with git to give it a try, but only the master branch seems to be available, but I can wait for the next stable release. No need to hurry. My selfhosted environment is pretty stable.

[DarkElvenAngel]

Small Update:

I've added a docker build script for building the self install packages for libreelec and lakka, This is mostly for anyone uses a Pi with a 64 bit OS installed and wants to build for a 32bit system.

The docker stuff is very basic and I'm sure it can be improved I've only just learned docker so I'm open input on how to make things better.

To be clear the nature of how the daemon works I don't think it could run properly in a docker container this is strictly to preform the build steps.

[DarkElvenAngel]

An update as to what is going on.

Version 0.4.x is still stuck in development we've had a far share of issues crop up with how the build system works and compatible with different OS and kernels. The 0.4.x branch answers these problems and keeps gaining features as a result so until I can lock down the source I can't do a proper release.

Something I didn't expect has come up. A user has leveraged the docker build system I recently added to preform a native build on LibreElec. LibreElec on it's own has no build tools, it can however add docker as a Kodi plug-in. I don't know how common this will be but I took it as a challenge to try it myself not knowing what steps they took. I've created a script that can pull the files from the repo and from there you can leverage docker to do the build.

I'm going to post this a merge request where I will hopefully get some input on how this should be working.

Has anyone here used docker on LibreElec, would you want a script you could run to preform the LibreElec build on LibreElec itself? The current method has a few steps I'm not sure if streamlining things is a good idea or not.

Interested in what my users think.

The merge may take a few days from when I post to go up I have some tweaks to make.

ADD: Build support for LibreElec

[dtcooper]

Wondering if anyone has had any luck soldering a 940nm IR LED/blaster to the board. If so, is setting it up easy, or something the daemon would need to support?

[DarkElvenAngel]

Wondering if anyone has had any luck soldering a 940nm IR LED/bladder to the board. If so, is setting it up easy, or something the daemon would need to support?

I have no support for IR Transmit or Receive there is no need as there are existing tools that can do a much better job.

If you have a V2 case I do have support for setting the the remote power button it's not fully implemented and is scheduled for the 0.4.x release.

For my V1 case I did buy an IR receiver I haven't bothered to install it as I have a V2 that has one pre installed. I don't have a use case for transmission using IR, I believe you can just make sure the polarity is correct and solder it in if you want to use it and then lircd or the kernel driver is what you want to use software side.

Hopefully that helps.

[dtcooper]

Wondering if anyone has had any luck soldering a 940nm IR LED/bladder to the board. If so, is setting it up easy, or something the daemon would need to support?

I have no support for IR Transmit or Receive there is no need as there are existing tools that can do a much better job.

If you have a V2 case I do have support for setting the the remote power button it's not fully implemented and is scheduled for the 0.4.x release.

For my V1 case I did buy an IR receiver I haven't bothered to install it as I have a V2 that has one pre installed. I don't have a use case for transmission using IR, I believe you can just make sure the polarity is correct and solder it in if you want to use it and then lircd or the kernel driver is what you want to use software side.

Hopefully that helps.

It does, thank you kindly. Any idea what GPIO pin it's connected to?

[DarkElvenAngel]

So the IR Receiver is on GPIO 23

once installed in the case you add this line to the config.txt (assuming you are on an OS that supports overlays)

Code: Select all

dtoverlay=gpio-ir,gpio_pin=23

As for a transmitter I don't know if there is one or what pin it would use I'm sure the information is online somewhere. The other option is to try using a continuity tester and figure it out, I'd look myself both my cases are in use.

[dtcooper]

As for a transmitter I don't know if there is one or what pin it would use I'm sure the information is online somewhere. The other option is to try using a continuity tester and figure it out, I'd look myself both my cases are in use.

Thanks for getting back to me. Customer support says it's wired up to 22. Not sure if it has the right resistor or whatever (not an electrical guy). I'll check it out, solder it up, and report back for posterity I guess!

[DarkElvenAngel]

Thanks for getting back to me. Customer support says it's wired up to 22. Not sure if it has the right resistor or whatever (not an electrical guy). I'll check it out, solder it up, and report back for posterity I guess!

Thank you I'll add this to my notes I'll document it in the project too so any info you share is great

[tinker2much]

Thank you very much for both the daemon and the panel applet. Great stuff!I use them on my Pi4-8GB, in the ArgoneOne V2 case.

Here's one thing I'm puzzled by - I don't know to get to the small "Fan Setting" dialog box you picture under "Screen Shots" at the bottom of the applet's gitlab page. This would be to set the three temperature and fan speed schedules, or the hysteresis.

I do know how to get the box that has Auto/Off/Manual/Fan up/Fan down/About - by left clicking on the applet in the panel. I do know how to get to the "Argon One Fan Monitor" settings box, that you describe under the "How to Use" heading - but DON'T picture - by right clicking on the applet in the panel and then choosing ""Argon One Settings".

What am I missing or doing wrong?

[DarkElvenAngel]

Thank you very much for both the daemon and the panel applet. Great stuff!I use them on my Pi4-8GB, in the ArgoneOne V2 case.

Here's one thing I'm puzzled by - I don't know to get to the small "Fan Setting" dialog box you picture under "Screen Shots" at the bottom of the applet's gitlab page. This would be to set the three temperature and fan speed schedules, or the hysteresis.

I do know how to get the box that has Auto/Off/Manual/Fan up/Fan down/About - by left clicking on the applet in the panel. I do know how to get to the "Argon One Fan Monitor" settings box, that you describe under the "How to Use" heading - but DON'T picture - by right clicking on the applet in the panel and then choosing ""Argon One Settings".

What am I missing or doing wrong?

What version of the applet are you running? i have 0.5 running on my pi now I tend to be a version ahead for testing purposes.

and what version of Pi OS are you on?

[tinker2much]

The applet reports version 0.0.5.

I'm on Raspberry Pi OS, Bullseye 64-bit, all up to date.

Code: Select all

pi@pi8:~ $ uname -a
Linux pi8 5.15.84-v8+ #1613 SMP PREEMPT Thu Jan 5 12:03:08 GMT 2023 aarch64 GNU/Linux

Code: Select all

pi@pi8:~ $ argonone-cli --decode
INFO:  Running under normal user some features may not work.
>> DECODEING MEMORY <<
Fan Status OFF Speed 0%
System Temperature 41°
Hysteresis set to 3°
Fan Speeds set to 10% 55% 100%
Fan Temps set to 55° 60° 65°
Fan Mode [ AUTO ] 
Fan Speed Override 0% 
Target Temperature 0° 
Daemon Status : Waiting for request
Maximum Temperature : 42°
Minimum Temperature : 35°
Daemon Warnings : 0
Daemon Errors : 0
Daemon Critical Errors : 0

[tinker2much]

And here are all the non-blank, non-commented lines in /boot/config.txt:

Code: Select all

pi@pi8:/boot $ livelines config.txt 
arm_freq=1900
dtparam=i2c_arm=off
dtoverlay=gpio-shutdown,gpio_pin=3
dtparam=audio=on
camera_auto_detect=1
display_auto_detect=1
dtoverlay=vc4-kms-v3d
max_framebuffers=2
arm_64bit=1
disable_overscan=1
[cm4]
otg_mode=1
[all]
[pi4]
dtoverlay=argonone
arm_boost=1
hdmi_enable_4kp60=1
[all]

[tinker2much]

Trying git pull on the applet got me nothing newer.

Trying git pull on the daemon only got me this:

Code: Select all

Updating aa75305..7629b06
Fast-forward
 OS/nixos/default.nix | 14 +++++++++++++-

In both projects, I'm on the master branch.

[tinker2much]

And, in case it matters, I never installed any software from the manufacturer, only yours.

[DarkElvenAngel]

Sorry I was busy earlier and not at home I had to vnc in to see what I have.

So I now see what your looking for. Left click the applet and click Schedule That will bring up the fan settings window. Keep in mind this doesn't persist over a reboot.

If you don't see the Schedule option however I will update the repo

Sorry there is something wrong on my end I can't upload the fix.

these lines need to be added to main.c at line 510 you can see // SEPERATOR - About window is the land mark

Code: Select all

  GtkWidget *item_schedule = gtk_menu_item_new_with_label ("Schedule");
  gtk_menu_shell_append(GTK_MENU_SHELL(pTest->popup_menu), item_schedule);
  g_signal_connect(item_schedule, "activate", G_CALLBACK(test_mnu_schedules), pTest);
// SEPERATOR - About window

[tinker2much]

When I left click the applet, there is no "Schedule" option"

[DarkElvenAngel]

There is a fix in my last post there is missing code

[tinker2much]

Thanks, that did it. I can now see the schedule option and change the temperature thresholds and fan speeds.

[tinker2much]

I looked at the decoded values, where there's one "critical error" noted at the bottom:

Code: Select all

pi@pi8:~ $ argonone-cli --decode
INFO:  Running under normal user some features may not work.
>> DECODEING MEMORY <<
Fan Status OFF Speed 0%
System Temperature 47°
Hysteresis set to 2°
Fan Speeds set to 5% 55% 100%
Fan Temps set to 50° 55° 60°
Fan Mode [ AUTO ] 
Fan Speed Override 0% 
Target Temperature 0° 
Daemon Status : Waiting for request
Maximum Temperature : 56°
Minimum Temperature : 41°
Daemon Warnings : 0
Daemon Errors : 0
Daemon Critical Errors : 1

I checked the log:

Code: Select all

pi@pi8:/var/log $ sudo tail -n20 argononed.log 
Sat Jan 28 16:14:48 2023 [INFO] Fan Temps set to 50 60 65
Sat Jan 28 16:14:48 2023 [INFO] Fan Mode [ AUTO ] 
Sat Jan 28 16:14:48 2023 [INFO] Fan Speed Override   0 
Sat Jan 28 16:14:48 2023 [INFO] Target Temperature 30 
Sat Jan 28 16:15:54 2023 [INFO] Request reload of config from shared memory
Sat Jan 28 16:15:54 2023 [INFO] Hysteresis set to 2
Sat Jan 28 16:15:54 2023 [INFO] Fan Speeds set to 5% 55% 100%
Sat Jan 28 16:15:54 2023 [INFO] Fan Temps set to 50 55 60
Sat Jan 28 16:15:54 2023 [INFO] Fan Mode [ AUTO ] 
Sat Jan 28 16:15:54 2023 [INFO] Fan Speed Override   0 
Sat Jan 28 16:15:54 2023 [INFO] Target Temperature 30 
Sat Jan 28 16:19:33 2023 [INFO] Set fan to 5%
Sat Jan 28 16:21:52 2023 [CRITICAL] Unable to get GPIO Line Event : Device or resource busy
Sat Jan 28 16:23:59 2023 [INFO] Set fan to 55%
Sat Jan 28 16:29:29 2023 [INFO] Set fan to 5%
Sat Jan 28 16:29:33 2023 [INFO] Set fan to 0%
Sat Jan 28 16:31:13 2023 [INFO] Set fan to 5%
Sat Jan 28 16:31:47 2023 [INFO] Set fan to 55%
Sat Jan 28 16:41:13 2023 [INFO] Set fan to 5%
Sat Jan 28 16:41:23 2023 [INFO] Set fan to 0%

Should I be concerned?

[DarkElvenAngel]

I looked at the decoded values, where there's one "critical error" noted at the bottom:

Code: Select all

pi@pi8:~ $ argonone-cli --decode
INFO:  Running under normal user some features may not work.
>> DECODEING MEMORY <<
Fan Status OFF Speed 0%
System Temperature 47°
Hysteresis set to 2°
Fan Speeds set to 5% 55% 100%
Fan Temps set to 50° 55° 60°
Fan Mode [ AUTO ] 
Fan Speed Override 0% 
Target Temperature 0° 
Daemon Status : Waiting for request
Maximum Temperature : 56°
Minimum Temperature : 41°
Daemon Warnings : 0
Daemon Errors : 0
Daemon Critical Errors : 1

I checked the log:

Code: Select all

pi@pi8:/var/log $ sudo tail -n20 argononed.log 
Sat Jan 28 16:14:48 2023 [INFO] Fan Temps set to 50 60 65
Sat Jan 28 16:14:48 2023 [INFO] Fan Mode [ AUTO ] 
Sat Jan 28 16:14:48 2023 [INFO] Fan Speed Override   0 
Sat Jan 28 16:14:48 2023 [INFO] Target Temperature 30 
Sat Jan 28 16:15:54 2023 [INFO] Request reload of config from shared memory
Sat Jan 28 16:15:54 2023 [INFO] Hysteresis set to 2
Sat Jan 28 16:15:54 2023 [INFO] Fan Speeds set to 5% 55% 100%
Sat Jan 28 16:15:54 2023 [INFO] Fan Temps set to 50 55 60
Sat Jan 28 16:15:54 2023 [INFO] Fan Mode [ AUTO ] 
Sat Jan 28 16:15:54 2023 [INFO] Fan Speed Override   0 
Sat Jan 28 16:15:54 2023 [INFO] Target Temperature 30 
Sat Jan 28 16:19:33 2023 [INFO] Set fan to 5%
Sat Jan 28 16:21:52 2023 [CRITICAL] Unable to get GPIO Line Event : Device or resource busy
Sat Jan 28 16:23:59 2023 [INFO] Set fan to 55%
Sat Jan 28 16:29:29 2023 [INFO] Set fan to 5%
Sat Jan 28 16:29:33 2023 [INFO] Set fan to 0%
Sat Jan 28 16:31:13 2023 [INFO] Set fan to 5%
Sat Jan 28 16:31:47 2023 [INFO] Set fan to 55%
Sat Jan 28 16:41:13 2023 [INFO] Set fan to 5%
Sat Jan 28 16:41:23 2023 [INFO] Set fan to 0%

Should I be concerned?

The GPIO Line Event error is dealing with the power button. This type of busy error has cropped up for other users. In the current version this error is ignored.

BLOCK ERROR "Device or resource busy" It seems to be a false alarm

If you want to be sure you can update the daemon to the current version 0.3.4 or the next release version 0.4.0 is in the 0.4.x branch it's very stable there are some features introduced in 0.4.x that are not active and that's why it hasn't moved to the master branch yet.

I run 0.4.0 on my Pi and so do many other users it remains compatible with the applet as well though the may change in newer versions.

You don't need to upgrade though so long as everything is working.

[tinker2much]

I'll try 0.3.x. Thanks.

another question - can you tell - via sound or vibration - that the fan is actually spinning faster or slower? I'm somewhat hearing impaired, and even with hearing aids, I can't hear any difference between the sound of the fan at 10 or 55 or 100%. With my fingers on the case, I can't feel any difference in the vibrations, either. NOTE: I can hear and feel the difference between off and on, it's just the different fan speeds that I can't distinguish.

Is there some value that I can read somewhere giving the actual rpms of the fan?

[tinker2much]

I'll try 0.3.x. Thanks.

It looks like 0.3.x is the same as master, so I already had that version installed?

Code: Select all

7629b06 (HEAD -> 0.3.x, origin/master, origin/HEAD, master) Merge branch 'feature-nixos-patch' into 'master'