Comments (20)

  1. Fernando Asanza

    Reply

    The manual says using picoolfan4 at an i2c address other than 0x60 requires an specific firmware (for each one, 0x50, 0x40, 0x30…) and all python scripts adapted to it that is, consecuently reading from 0x50… etc, not from 0x60. As I’m using a fixed i2c address sensor (0x60) I would need one of this new firmwares. Is it available somewhere now or will it be soon? Thank you.

    • PiAdmin

      Reply

      Hi,
      This firmware can be re-compiled on demand at any time, please advice what address you need to have in order send you firmware recompiled to your request, Python scripts you should do your self but it is a very easy task. Please advise by email to support@pimodules.com what I2C address you are interesting on. We will re-compile the firmware in 5 minutes and send you. We can also change permanent the temperature threshold, to your needs as default set up.
      Kind Regards
      Ioannis

      • Fernando Asanza

        Reply

        Hi, thank you very much for such a quick response and offer!,
        For my needs, changing the base i2c address to 0x30 would be great. About ttemp, default 50º and fixed maximun possible to 75º in the latest firmware 1.04 it is fine. Of course, I’ll take care of adapting python scripts as well as any shell script using i2cset… No problem at all.
        Anyway I’m going to advise all this to that support email provided.
        Thank you again in advance.
        Kind Regards
        Fernando

  2. Martin Sperl

    Reply

    I wish there was an option for a fallback plan, when – depending on the mode used – the CPU Temperature is not updated or the fan speed is not set in the last 5 minutes.
    So either go back to the internal sensor or use a fixed fan speed.
    That would resolve a possible issue of the system overheating when the monitoring process has died and is not restarted…

    Using this i2c communication as a sort of watchdog that would pull a pin low (which can then get connected to the reset pin on the pi) may also be a helpful addition to the firmware…

    • PiAdmin

      Reply

      Hi,
      Thank you for your email!
      We are currently updating the firmware, it is good time to implement your idea. Could you please explain in more details your idea to be sure that I understand it properly and go to implementation. The controller we are using in the PiCoolFAN4 is very small memory footprint, but there is little bit free space to add some lines of code (or remove other parts and add your idea)
      Can you please describe in more details your idea on our support email support@pimodules.com
      Kind Regards
      PiModules

  3. Loek Dompeling

    Reply

    I also have the Pi4coolfan and I tried to install the latest firware but then I receive a message you must define. Wehn i boot the pi4 with the coolfan I only see a blue light and no green light. When I boot the coolfan without the battery then I see a red and greenlight. What kind of steps do i have to make to work the pi4coolfan propely.
    Thanks

    • PiAdmin

      Reply

      Hi,
      Thank you for your email!
      You, for someone reason have not completed boot loading process. It could be not proper RS232 set up on Raspberry Pi, or any other reason.
      However it is not big problem. Your PiCoolFAN4 when enter to boot loading process stay in this mode until properly firmware will be uploaded. The boot loader state is indicated with the Blue LED. Therefore your PiCoolFAN4 is waiting for the firmware upload. More details are described in the last (35) page in the manual I copy it here also:
      —
      During boot loading process system hang up (or for any reason and not completed uploading)
      The implemented in the PiCoolFAN4 bootloader is very secure. If the bootloaded new firmware not finished successfully, PiCoolFAN4 will not start. Will wait for repeated loading until completed properly. The Green User LED will lit then. If something like that happen, then user need to repeat the bootloader command without recalling (bootloader itself) it, like below. Remember to write the proper and current firmware name instead this typed.

      sudo python PCF4_serial0_9600_FU1.0.py -v -f PiCoolFAN.hex
      —
      Please do not hesitate to ask whatever you need again here
      Kind Regards
      PiModules Team

  4. Loek Dompeling

    Reply

    Thank you for your answer. I updated the firmware and my pi is booting .But I have no blue light only a red and green light on. What Kind of steps do I have to make for that the blue light is on.
    Thanks

    • PiAdmin

      Reply

      Hi,
      The Blue LED lit when temperature is below the threshold. I do not know in which environment you have your system (I mean what case), and what threshold you set. Therefore, you should play little-bit with threshold temperature – slightly increase (i.e. by 1 degree) and observe the system, normally in an open (no case at all) environment, you should have the threshold set to about 46-48 degrees, and in closed case to 48-50 degrees.
      Please check it and keep me informed
      Kind Regards
      Ioannis

      • Loek Dompeling

        Reply

        Thank you. I have the pi not in a case but open. on my desk. I set the tresshold to 40 but the red light is still on. About the firmware when you exeute the hexfile I didn’t receive the prompt back . Is that oke I mean is that normal ?
        Thanks

        • Loek Dompeling

          Reply

          It is working now. I did an update and upgrade for my pi4 and the blue light is now on. I think I set the tresshold to 50.
          Thanks again

  5. Michael

    Reply

    Could you please kindly include a feature to switch serial interface of the HAT on and off via i2cset as I would like to combine the fan with another hat that leverages the serial interface quite heavily. – Thanks!

  6. Jay

    Reply

    Hello, when trying to install the latest firmware on the picoolfan module something went wrong.
    Only the green LED lights up and the fan stops moving.
    Can you tell me the full input commands and the current version of the firmware?
    I am not a professional when it comes to programming.

    Thank you very much for your help.

    Validating firmware: OK
    Checking communication with bootloader: KO
    ERROR: Something wrong happened during verification of communication channel with PIco bootloader via port: /dev/serial0 Please verify that the serial port is availble and not used by some other application.

    Validating firmware: OK
    Checking communication with bootloader: KO
    ERROR: Failed to establish communication with bootloader in PIco. Is the PIco in the bootloader mode? (Red LED lid on PIco)

    • PiAdmin

      Reply

      Hi,
      Please check the last page of the manual where is described such problems and how to solve them. Please also make sure that you have activated serial port on the Raspberry Pi
      Kind Regards
      Ioannis

  7. jay

    Reply

    pi@raspberrypi:~/PiCoolFan $ sudo python PCF4_serial0_9600_FU1.0.py -v -f PiCoolFAN_V1_4.hex
    Validating firmware: OK
    Checking communication with bootloader: KO
    ERROR: Failed to establish communication with bootloader in PIco. Is the PIco in the bootloader mode? (Red LED lid on PIco)

    • PiAdmin

      Reply

      Hi,
      Thank you for your question.
      Please check the last page of the manual when are described such behavior and steps needed to overcome it.
      Kind Regards
      Ioannis

  8. Thomas

    Reply

    Using smbus2 and python3 on Fedora34 while attempting a firmware upgrade, it has been deactivated altogehter:

    pi@raspberrypi:~/PiCoolFan4/original $ i2cdetect -y 1
    0 1 2 3 4 5 6 7 8 9 a b c d e f
    00: — — — — — — — — — — — — —
    10: — — — — — — — — — — — — — — — —
    20: — — — — — — — — — — — — — — — —
    30: — — — — — — — — — — — — — — — —
    40: — — — — — — — — — — — — — — — —
    50: — — — — — — — — — — — — — — — —
    60: — — — — — — — — 68 — — — — — — —
    70: — — — — — — — —

    Any way to reset it and get the device going under Raspberry Pi OS is highly appreciated. Thank zou!

  9. Thomas

    Reply

    A reset can be easily done with the jumper that comes with the package. However, I just had to complete part 2 of the bootloader sequence which is the culprit in most cases:

    #Bootloader Part 1:
    sudo i2cset -y 1 0x60 0x08 0xbb && sleep 1 && sudo python PCF4_serial0_9600_FU1.0.py -v -f
    PiCoolFAN.hex

    #Bootloader Part 2:
    sudo python PCF4_serial0_9600_FU1.0.py -v -f PiCoolFAN.hex

Leave a comment

Your email address will not be published. Required fields are marked *