Jump to content

piknew

Members
  • Posts

    113
  • Joined

  • Last visited

Posts posted by piknew

  1. If something happens (physical damage, difference in chemistry) to one of the cells to change its internal resistance to different than the other, the TP4056 chip can end up overcharging one of the cells in the pair (since its reading information from the combination of the cells), and its not unknown for a lithium cell to react rather violently when this happens.

     

    One TP4056 per cell if you want to play it safe. At the very least charge at no more than 1C of a single cell of the pair.

     

    1. I have written "in parallel". So, it is 1S2P (or 2P1S) configuration.

    2. DW01 protection exists (one of function is overcharge protection).

    3. Currently (again: in parallel) it is charging to 1A / 4500 mAh (2 x Sony US18650V3 2250mAh), so it is under 0.25C. Even, if because of some reason 1 cell wil stop consuming any current (infinite resistance), then the other will be charged below 0.5C.

  2. If about "UPS" I was planning to make my own with control lines (reporting for "on battery", "on ac" status) and simple "c" daemon (similar to upsd) for powering off the device after defined period of time. Additionally for delay circuit for powering on after power was restored and some defined time elapsed (it total it would be quite complicated circuit).

     

    Then I made my "UPS power bank" with tp4056 charger, 2 18650 cells (in parraler), step up with MT3608 module and switching circuit as mentioned here (with slight optimization): http://ficara.altervista.org/?p=2736

     

    Then after tests it appered that my "UPS" can handle up to 7-8 hrs of keeping server up & running (of course not under heavy load), with average consumption of 0.4 A. IN such a case I resigned from controlling module and leave simple function.

     

    Module is working under full charge (4.2v). I am aware that in normal condition it will decrease lifetime of cells, but it is no problem to replace it (eg. after 3 years) :).

  3. Just as warning - It seems that Orange Pi devices have quite "easy to burn" hdmi port. This post is quite clear about it: http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=1556

     

    And case happened to me - I did it simply by plugging in and out hdmi cable. At some moment "no signal" is coming from HDMI (or maybe I should say "nothing is coming" ;) ). It is on my Orange Pi PC. Now I wait for composite TV/Audio cable (in post I am referring there is information that TV out is still working).

    Or my device will be changed to "server" only...

     

     

  4. BTW: In case you moved your installation within the last 5 weeks to eMMC then you're lucky since I adopted our firstrun behaviour (leavy some space unpartitioned on SD card) for nand-sata-install too. This has been done for exactly this reason: ease the cloning of an installation.

     

    I guess it is ok? See results:

    admin@PKSERVER:~$ sudo fdisk /dev/mmcblk0
    
    Welcome to fdisk (util-linux 2.25.2).
    Changes will remain in memory only, until you decide to write them.
    Be careful before using the write command.
    
    
    Command (m for help): p
    Disk /dev/mmcblk0: 14.6 GiB, 15634268160 bytes, 30535680 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x576a94d9
    
    Device         Boot Start      End  Sectors  Size Id Type
    /dev/mmcblk0p1       2048 30230303 30228256 14.4G 83 Linux
    
    
    Command (m for help): q
    
    admin@PKSERVER:~$ cat /proc/partitions
    major minor  #blocks  name
    
     179        0   15267840 mmcblk0
     179        1   15114128 mmcblk0p1
     179       32       4096 mmcblk0boot1
     179       16       4096 mmcblk0boot0
       8       16  121085952 sdb
       8       17  121084928 sdb1
    admin@PKSERVER:~$
    
    
  5. From OPi Plus 2E you do

    ssh root@plus2 "dd if=/dev/mmcblk1 bs=1M | gzip -c" | gunzip -c | dd of=/dev/mmcblk1
    

    Then shut the board down, remove SD card, power on and enjoy the migrated installation. The nand-sata-install approach might also work but this means two times cloning a live installation which is known to NOT work in case you have databases running or stuff like that (simply use 'lsof' to get an idea how many open files your installation currently has. All of them are prone to change/mismatch when cloning a live installation as we do it with the nand-sata-install script)

     

    Thank you. Your way is much simpler. For running databases etc. actually I wanted to "stop services etc." (it is not 100% efficient, then lsof would be good to determine if any of important live-data is still under some processing/activity). But cloning offline system is much much better and efficient (just as stated size of target eMMC must be at least the same by number of blocks).

     

    Just to clarify your post (I guess there is a little bit of mistake - one SD card should contain OPi Plus 2 and second one - OPi Plus 2e - appropriate for target platform). And the described way is OK no matter which system I would run on both devices (It may be even not Armbian ;)). It would be important that both are run from SD card (for example /dev/mmcblk0) and eMMC is available as some other device (for example as /dev/mmcblk1).

     

    Thanks once again.

     

    BTW. I have only one SD Card. But I will use 3rd device in my network, QNAP Nas. So 1st I will run OPi Plus 2 from SD and from NAS:

     

    [~/OPiPlus2] # ssh root@plus2 "dd if=/dev/mmcblk1 bs=1M | gzip -c" >eMMC.gz

     

    (I can execute it from OPi Plus 2, but the command of course will be different).

     

    Then modify link so OPi Plus 2e would be able to start from SD Card. Start OPi Plus 2E and execute command to transfer image to mmcblk1 (I can execute command from either NAS or OPi Plus 2E).

  6. Hi, currently my small server is running under Armbian 5.16 on Orange Pi Plus 2 board. It is using eMMC as root fs. I am expecting to get Orange Pi Plus 2E to be delivered shortly. The question is if following procedure will be OK to migrate server between boards:

     

    before: stop services etc.

     

    1. insert SD card (16GB) when system is running. eMMC is visible as /dev/mmcblk0, SD card will appear as /dev/mmcblk1.

    2. use nand-sata-install to copy system to SD Card.

    3. mount /dev/mmcblk1 under some mount point, for example /mnt

    4. verify, if /mnt/etc/fstab is valid:

     

    /dev/mmcblk0p1 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1

     

    5. modify link:

     

    cd /mnt/boot && rm script.bin && ln -s bin/orangepiplus2e.bin script.bin

     

    (* currently it is link to bin/orangepiplus.bin).

     

    6. umount /mnt

     

    remove SD Card and insert to new 2E device. It should boot without problems??? If yes - use nand-sata-install to copy system to eMMC (procedure very similar to above).

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines