modmypi / pimodules Goto Github PK

I'd like it to behave like a normal power button (i.e. it should shutdown the computer when pressed whether on line power or battery). It would be great if there was an option so that I could make the daemon behave like that.

Thanks. :)

Hi there!

This "issue" might be a little OT but because of the broken forum registration on the pimodules forum I try to get help here.

Is there any documentation, timing sheet, etc. for the fssd protocol on GPIO22/27? I found no information, neither in the manual, nor in the forum.

The python script you provide makes no sense to me, but I assume it's working as no one complains about.

Background for my question is, that I plan using my own daemon, which uses the pigpio library/daemon and a concurrent use with the RPi.GPIO library is not an option for me.

Thanks in advance!

Hi everybody!

With the UPS PIco HV3.0A you are only able to set a battery runtime of at least 60 seconds (writing 0x00 to the 0x01 address on 0x6b according to your documentation) resulting in a battery runtime of 60 + 0 * 60 seconds, thus limiting the user to a minimum battery runtime of 60 seconds.

Anyway, for some applications it's useful to have an even shorter (= below one minute) battery runtime before the ups sends the shutdown signal. An option for an immediate shutdown could be useful as well.

Hello I've four Raspberry PI 2 with UPS Pico HV3.0B module installed.
The batteries are all LiPo 450 mAh.

The power supply is a standard Raspberry PI wall supply marked Stontronics 5.1V 2.5A
The UPS Pico module is used only as UPS, non other peripheral are connected or used.

The four systems works normally for hours or even days but suddenly I found them off.
When I found them off the UPS and FAN led are continuously lit, fan is spinning and Raspberry is off with red light on.

If I recycle the power the units starts regularly, watchdog working and battery charging.

I've found that:

• Raspberry does not shut down regularly (Not Clean) when the event happens
• One battery was at 3.0 V
• Another Battery was a 0V !!!

I Enabled the log on the picoffsd scripts but there are no evidence that the shut down is script generated.
Added some more log lines on the python script but non evidence of something wrong inside the scripts.

If I test the UPS functionality they works regularly, so if I remove the power supply after some time the raspberry shut down cleanly.

Regards
Mattiolo

UPS PIco HV3.0B with Raspberry PI 3 Model B

Sometimes when powering on, Raspberry remains off.

Here is my scenario:

0. Power on
1. Battery gets loaded.
2. Power off
3. Raspberry has enough power to shutdown clean
4. Power on

[Steps 2 to 4 are repeated until battery is depleted]

5. Power on

Now here sometimes it doesn't boot anymore.
On UPS PIco: UPS and BAT are lightened
On Raspberry: Red led is lightened.

I wait for 20-45 seconds, and then:

UPS PIco: ( 3 LEDS near GPIO OR OR CHG )are all lightened for a second , then UPS and BAT are lightened
Raspberry PI: Red light is always on, while ACT blinks in set of 7 blinks

If I Power off, wait 5 seconds, an power on again,, it works.

Any ideas?
If SD Card was the issue I would have seen a boot error at least once I guess...

Hello,
I am searching for a way to configure how the pico UPS decides whether it should trigger a safe shutdown. Mine is a bit too jumpy, right now - shutting down when nothing is wrong, really (I have logs of the supply voltage). Is there a way to make this more inert?

I ordered a PCB with relay installed already. I can hear the switch go back and forth when sending the commands, but there seems to be no contact going through. I noticed that two of the relay pins are not soldered on. Are all pins required to be soldered, in order for the relay to work?

Commands used are:

sudo i2cset -y 1 0x6b 0x0c 0x01 (and 0x00)
Has anyone else had this problem?

Just bought a PICO UPS HAT and I need too use it for OSMC, is there a complete tutorial on how to do it?not Familiar with programming, or if there is an image ready available with UPS Software for OSMC that will be appreciated.

Hi guys, I just want to ask you if the UPS PIcoHV3.0A works properly and fits well with all the Raspberry NanoPi models. Thank you in advance!

Albert

In my project I've to connect more PSU. Rapberry has some fuse with limit power too 1,1A. I need more.
But if I connect PSU through GPIO pins. UPS pico blink UPS led and sudo i2cget -y 1 0x690x00 return 0x02.
I need to have info when power is from BAT or PSU but PSU must bi connected to GPIO or some how but not through raspberry mico usb?

Is there something I can do for the Still Alive (STA) Functionality to remain enabled after UPS PIco restart ?
How can I check?

From the documentation here: http://pimodules.com/products/ups-pico-hv3-0a-b-b/common-updates
https://drive.google.com/open?id=1-qsnRpp6tYCa9hC7_SYldHXyOm-1pYLi (pag. 173)

After execution of the STA Restart the sta_timer is set again to 0xff (disabled).

I am new to UPS PIco world. I just received 2 boards from PiModules (UPS PIco HV3.0B+ HAT Stack 450 PoE). Took a while to get them up and running. I've been making up circuits since my teenage years and am not an amature at soldering components. The 'Magic Switch' was a bit confusing as the manual has few errors and is missing some information. Strange rebooting, not staying shut down and boot loops made it all very frustrating.

There was no mention that you can can't use a heat sink if you install the fan as there is not enough room.

The manual really needs checking and updating. E.g. from page 83:

When System is Cable Power user has a possibility to restore the factory defaults. To do that the following steps need to be followed:
• Press and hold the UR button
• Continue to hold the UR button, and press and hold the C button.
• Release the UR button, but keep holding the F button
• Release the F button

What? This does not make sense. Keep holding the F button, or should that be C button.

Running the pico_status_hv3.0.py I get the following errors:

UPS PIco Firmware.....: ec
UPS PIco Bootloader...: 53
UPS PIco PCB Version..: 43
UPS PIco BAT Version..: ERROR
UPS PIco BAT Runtime..: 2 MIN
UPS PIco r232 State...: OFF

Powering Mode.........: RPi POWERED
BAT Percentage........:
Traceback (most recent call last):
File "pico_status_hv3.0.py", line 194, in
print " ","BAT Percentage........:",bat_percentage(),"%"
File "pico_status_hv3.0.py", line 95, in bat_percentage
return datapercentage
UnboundLocalError: local variable 'datapercentage' referenced before assignment

So I had look at the code and tried to work out what is going wrong. Turns out I have a battery type 0x43:

sudo i2cget -y 1 0x6b 0x07
0x43

I tried resetting the board to the factory defaults using the buttons as per the manual but still get the same battery code.

Is this a bug? Have the battery codes changed in version ec?
According to the manual this is an invalid battery type.
Should I try and change the code to 0x53?

And when will the official forums be fixed, and the new firmware (0xed) released which has been in beta for almost a year! Using GitHub as forum is not ideal.

So far I would give the whole UPS PIco experience a 5 out of 10 rating. But it's hard to find one that works with the official Pi PoE HAT.

I just want some advice on the battery version code.

Hi,

I installed a brand new pico hat on a brand new raspbien. I did all the installation steps, installed the "on/off" button and the buzzer.
First time I plugged the power with the hat, the raspberry started and the pico worked perfectly (I removed the cable and the raspberry continues to work).
Then I shutdown the raspberry (doesn't matter if I do it pushing apico button or in command line).
I tried all buttons the raspberry never started again. I have to unplug the power cable only then a button started the raspberry.

All I want is: If the power cable goes off=> shutdown the rasbperry (no wait)
If the power cable goes on=> start the rapberry.

I don't want to have to use buttons for start/stop, any chance to setup this behaviour? Or at least to be able to start the raspberry with the power cable on?

Thanks in advance.

Same problem with python2 / python2.7

(root|~/PiModules/pico_status) python pico_status_hv3.0.py

***********************************
      UPS PIco HV3.0A Status
***********************************

  UPS PIco Firmware.....: ec
  UPS PIco Bootloader...: 53
  UPS PIco PCB Version..: 43
  UPS PIco BAT Version..: ERROR
  UPS PIco BAT Runtime..: 2 MIN
  UPS PIco r232 State...: OFF

  Powering Mode.........: RPi POWERED
  BAT Percentage........:
Traceback (most recent call last):
  File "pico_status_hv3.0.py", line 194, in <module>
    print " ","BAT Percentage........:",bat_percentage(),"%"
  File "pico_status_hv3.0.py", line 95, in bat_percentage
    return datapercentage
UnboundLocalError: local variable 'datapercentage' referenced before assignment

With python3 / 3.5

(root|~/PiModules/pico_status) python3 pico_status_hv3.0.py
  File "pico_status_hv3.0.py", line 181
    print " "
            ^
SyntaxError: Missing parentheses in call to 'print'

I just received my PIco and started looking through the install / setup documentation and can't seem to find anything on these extra parts that came with my kit.

Two pin header w/ jumper - where does this go and is it needed?

Relay - Loads of questions about this one, I'll just leave it at that

On / Off (I'm assuming) switch - Where does it go and is it needed?

Single long pin - Where does it go and is it needed?

Foam sticker - Where does it go and is it needed?

Thanks

When UPS Pico is shut down (and the rPi itself is running) the charge current is nice and high at ~500 mA (measured with clamp meter, on 10 Ah pack).

When the UPS Pico is enabled and pulsetrain is running it drops to below 100mA

Is that supposed to happen ? The voltage on rPi ports is almost exactly 5V (and on 3A charger)

Hello,
What issues may cause that Pico UPS does not use external power when it is present? When I start the device by plugging battery in and then applying external power, it boots up and starts RPi. After couple of seconds on my lab bench power supply (set to 5V, 5A) I can see, that no power is used. At the same time LED blinks slower and I2C responses about battery power mode. Battery is not being charged. After about 60 seconds system is being turned off by Pico UPS.

P. S. I assure you that my power supply good and it cannot be an issue here.

Is there a way to "start" UPS Pico, if say rPi stopped generating pulse train for few minutes ?

I'm trying to write replacement for picofssd (the daemon is not working in the 64 bit Debian because libs do not support it) and so far it works well until I stop it and start again (because I am testing).

I am assuming UPS Pico goes into suspend mode and I'm getting some pulses:

event:  RISING EDGE offset: 27 timestamp: [1573132477.587398017]
event: FALLING EDGE offset: 27 timestamp: [1573132477.587476401]
event:  RISING EDGE offset: 27 timestamp: [1573132477.587520255]
event: FALLING EDGE offset: 27 timestamp: [1573132477.587586660]
event:  RISING EDGE offset: 27 timestamp: [1573132477.587650201]
event: FALLING EDGE offset: 27 timestamp: [1573132477.587718951]
event:  RISING EDGE offset: 27 timestamp: [1573132477.587780929]
event: FALLING EDGE offset: 27 timestamp: [1573132477.587846710]

event:  RISING EDGE offset: 27 timestamp: [1573132498.751365780]
event: FALLING EDGE offset: 27 timestamp: [1573132498.751465362]
event:  RISING EDGE offset: 27 timestamp: [1573132498.751496612]
event: FALLING EDGE offset: 27 timestamp: [1573132498.751554997]
event:  RISING EDGE offset: 27 timestamp: [1573132498.751618069]
event: FALLING EDGE offset: 27 timestamp: [1573132498.751708954]
event:  RISING EDGE offset: 27 timestamp: [1573132498.751748849]
event: FALLING EDGE offset: 27 timestamp: [1573132498.751828744]

event:  RISING EDGE offset: 27 timestamp: [1573132519.915647220]
event: FALLING EDGE offset: 27 timestamp: [1573132519.915752271]
event: FALLING EDGE offset: 27 timestamp: [1573132519.915810760]
event: FALLING EDGE offset: 27 timestamp: [1573132519.915854614]

it generates 4 short pulses every 20 seconds, what should be rPi answer to those ?

Also should probably use HTTPS...

Hello,

I have soldered the TO-90 Temperature sensor, the two POGO pins, the fan.
I'm running on a custom raspbian on which I applied the installation procedure:(https://github.com/modmypi/PiModules/wiki/UPS-PIco-Installation).

The fan is running fine, but the battery is not okay. UPS function is not working at all. The PI shutdown as soon as the usb cable is unplug.

And when I run the pico_status_hv3.0.py I got this strang value for the battery:

***********************************
      UPS PIco HV3.0A Status       
***********************************
 
  UPS PIco Firmware.....: e0
  UPS PIco Bootloader...: 53
  UPS PIco PCB Version..: 43
  UPS PIco BAT Version..: LiPO (ASCII: S)
  UPS PIco BAT Runtime..: 2 MIN
  UPS PIco r232 State...: OFF
 
  Powering Mode.........: RPi POWERED
  BAT Percentage........: -426.666666667 %
  BAT Voltage...........: 0.2 V
  RPi Voltage...........: 5.0 V
  NTC1 Temperature......: 42 C
  TO-92 Temperature.....: 41 C
  Extended Voltage......: 0.0 V
  A/D2 Voltage..........: 0.0 V
 
  PIco FAN Mode.........: ERROR
  PIco FAN State........: OFF
  PIco FAN Speed........: 320.0 RPM
 
***********************************
         Powered by PiCo           
***********************************

So I tried to use the image you give: https://github.com/modmypi/PiModules/wiki/UPS-PIco-Installation
And with this image, the UPS behave correctly.

What could I have done wrong in my custom raspbian image?

thank you

I can read my serial GPS fine, without the Pico HAT connected. However, as soon as it is installed, access to the GPS on ttyAMA0 results in nadda.

The documentation suggests that the serial port is only enabled during boot and f/w upgrade.

I have tried "sudo i2cset -y 1 0x6b 0x02 0x00" to disable the serial port on the Pico, without any joy.

Hi, installed all software - Pico HV3.oB+. All seems to work, Pico will shutdown after 60 seconds and pressing FSSD will shutdown however pressing FSSD will not power up again. Have to remove battery and external power to restart. Have installed POGO into Pin 3 for Pi3B.

Any help appreciated.

Hi,
I am using a Raspberry Pi 3 and the UPS PIco HV3.0B Stack 450. I have installed everything according to your instructions, but when I run pico_status_hv3.0.py from here, it gives me this:

Traceback (most recent call last):
  File "pico_status_hv3.0.py", line 186, in <module>
    print " ","UPS PIco Firmware.....:",fw_version()
  File "pico_status_hv3.0.py", line 29, in fw_version
    data = i2c.read_byte_data(0x69, 0x26)
IOError: [Errno 121] Remote I/O error

The UPS does work - the lights come on correctly, fssd works, and when I take the main power out, the battery kicks in.
I am using Python 2.7, and have enabled I2C, so I'm not quite sure what the problem is...

Any help would be appreciated :)

Are there any firmware updates for HV3.0B? I know there's updates for A.

Hi,

I am trying to set a schedule to turn the RPi on at 6AM for 12 hours every 24 hours. I am following the examples from the documentation, but it is not working for me:

sudo i2cset -y 1 0x6b 0x16 0x00 && i2cset -y 1 0x6b 0x17 0x00 && i2cset -y 1 0x6b 0x19 0x01 && i2cset -y 1 0x6c 0x00 0x01 && i2cset -y 1 0x6c 0x05 0x19 && i2cset -y 1 0x6c 0x04 0x05 && i2cset -y 1 0x6c 0x03 0x02 && i2cset -y 1 0x6c 0x02 0x06 && i2cset -y 1 0x6c 0x01 0x00 && i2cset -y 1 0x6d 0x00 0720 w && i2cset -y 1 0x6d 0x02 0x00 && i2cset -y 1 0x6d 0x03 0x01 && i2cset -y 1 0x6d 0x04 0x24 && i2cset -y 1 0x6e 0x00 01 && i2cset -y 1 0x6b 0x17 0x1

No matter what I do, I always get the following for the Actions:

0x00
0x00
0x01
0x01
0x19
0x05
0x02
0x06
0x00
0x0001
0x00
0x00
0x00
0x7f
0x01

Any ideas where the issue is?

Regards,
Peter

Can't find any description of the fail safe shutdown procedure. What I want to do is to to run backup service before system shutdown. So when there is power failure or I press F button I want to run this backup. The backup takes some time and it seems that it is interrupted in the middle and the Pi shuts down. Is there any timeout after which the pico ups will shut down the power to the PI regardless of the PI state?

I'm writing this issue because my message on pimodules forum has not been published yet.
I have a UPS-PIco HV3.0A Plus and I'm not satisfied with this product at all.

First, given that this board costs almost twice as much as the raspberry PI3, I don't like to see smd resistors soldered like in the pictures below.

Also, the documentation is scattered in many different pieces... Where can I find the official product manual (with things like product features, first setup, etc?)

Pictures of the board:

I know that the UPS PIco HV3.0 has implemented 2 independent, Time Schedulers. There are:

• the Basic Time Scheduler (BS)
• the Event Triggered RTC Based System Actions Scheduler (ETR SAS)

They both seem to have been implement around 15/07/2017 between firmware 0x39 and 0x40.
The above information have been take from what the last version of the user guide printed on 05/09/2018. Most important, the product pages on the Pi Modules shop seems to confirm their presence.

It seems that both the BS and the ETR SAS can't be used right now, nor they could have been used since the beginning, if I'm not wrong. I really want/need these features. Don't know if other customers agree. I just write an issue on the subject in order to receive updates.

I just received UPS PIco HV3.0 A Stack 450
I connected to my Pi and started OK after following installation instructions

I se Blue led blinking slowly and Yellow Led for Battery
After few minutes system will suddenly shutdown (Blue becomes steady)
Is it because battery is not charged?
Any interface I can see battery status?
Any user manual for the buttons and the other leds?

Hi.
Is there any documentation about INF LED?
I looking through latest manual and find nothing about this.

For me, INF LED blinks at a certain time and I do not know if it is an error or a correct behavior. (video)

I use Raspberry Pi 3+ with official 2.5A PSU.

***********************************
      UPS PIco HV3.0A Status       
***********************************
 
  UPS PIco Firmware.....: e2
  UPS PIco Bootloader...: 53
  UPS PIco PCB Version..: 42
  UPS PIco BAT Version..: LiPO (ASCII: S)
  UPS PIco BAT Runtime..: 2 MIN
  UPS PIco r232 State...: OFF
 
  Powering Mode.........: RPi POWERED
  BAT Percentage........: 80.0 %
  BAT Voltage...........: 4.0 V
  RPi Voltage...........: 4.9 V
  NTC1 Temperature......: 41 C
  TO-92 Temperature.....: 07 C
  Extended Voltage......: 9.0 V
  A/D2 Voltage..........: 0.0 V
 
  PIco FAN Mode.........: ERROR
  PIco FAN State........: OFF
  PIco FAN Speed........: 320.0 RPM
 
***********************************
         Powered by PiCo           
***********************************

I have got a UPS PIco HV3.0 A Stack 450 with default 450mAh LiPO Battery.
Status script shows 120% of battery percentage. Any clue why it is not 100%? Report below:

  UPS PIco HV3.0A Status       

UPS PIco Firmware.....: 31
UPS PIco Bootloader...: 53
UPS PIco PCB Version..: 41
UPS PIco BAT Version..: LiPO (ASCII: S)
UPS PIco BAT Runtime..: 1 MIN
UPS PIco r232 State...: OFF

Powering Mode.........: RPi POWERED
BAT Percentage........: 120.0 %
BAT Voltage...........: 4.3 V
RPi Voltage...........: 4.9 V
NTC1 Temperature......: 38 C
TO-92 Temperature.....: 12 C
Extended Voltage......: 0.0 V
A/D2 Voltage..........: 0.0 V

PIco FAN Mode.........: ERROR
PIco FAN State........: OFF
PIco FAN Speed........: 320.0 RPM

     Powered by PiCo           

UPS Pico HV3.0B+ with 450mAh LiPO. on a RPi 3B
While I'm utilizing the system, with power cable and battery connected, the battery drains and the system starts beeping.

I have assembled the hardware and installed the software according to the instructions (minus RTC).

Thanks

I am building a fairly complicated system with the pi3 and find that the two gpio you used are already in use by other boards. I would like to have the Pico UPS designed into the system as the usage may be far up in the mountains where it is difficult to recover from a bad shutdown, right now I can't do this.

I have several questions below

Question 1,

Short term -
what changes can I make to the board and software to get the signals onto different GPIO pins? I am very comfortable with cutting traces, and doing very fine pitch soldering if appropriate. I have access to great tools so I can do most any reasonable mods. I would like to use pins 11 and 37 currently as those are the only 2x20 header pins still open.

Looking at the software, it appears I only need to edit the following to fix the sw
https://github.com/modmypi/PiModules/blob/master/code/python/upspico/picofssd/scripts/picofssd#L25-L26

but I need to know where to cut/jump to bring in these pins in the board where they won't interfere with my other boards..

long term -
Unless there is a strong reason against it, you are already consuming the I2C bus, so why not use an expander like the MCP23017 or a register in the I2C device that could be polled?

perhaps you could also include some options in the board like solderable jumpers or 0-ohm resistors to select between a few of the gpio pins if you can't fit a gpio expander on the board? For selfish reasons, I would like to have 11 and 37 be the alternates :-)

Question 2,
It appears you are using I2C addresses 0x6b and 0x69 - Please confirm if these are the only addresses in use?

Question 3,
For the I2C bus usage, I am using the modern device tree to load up several devices (mostly MCP23017 gpio expanders, but also some others) on the I2C bus.

Can you please update the instructions with a device tree overlay so that I can merge it with my existing overlay rather than having to load the /etc/modules method. I haven't tried yet until I get my hardware delivered, but trying to ensure no conflicts where the two methods stomp on each other.

Hello everyone,

I see that the file /etc/pimodules/picofssd/picofssd.xml is readable for all users.
There is the password of the mail account just encoded in base64 inside.

All users can therefore read the base64 string and decode it to obtain the password.
For an Internet application, it is a security problem.
The installation script should make a 'chmod 600' of this file.

++

Hello,
i bought the ups Pico HV3.0B+ yesterday. I follow the installations steps and de RP2B+ shutdown 2 minutes later than i powered on.

Attach this image:

The software don't detect my Pico version correctly and in powering mode always said "Bat powered" and its powered by usb...

Can anybody help me?

I would like to try to add an RTC module because I get error msg about invalid argument when I use hwclock to set the PIco RTC. Ioctl can't read a file and RTC never gets updated.

I expect to try to fix this problem by using an external RTC module. Do I have to disable the UPS PIco RTC to avoir conflict? And if so...Any suggestion how to do it?

i have followed the setup on a fresh installation of jessie but when i get to installing the monitoring part it just gives me the message below. any help please ?

pi@raspberrypi:~ $ cd PiModules/code/python/package
pi@raspberrypi:/PiModules/code/python/package $ sudo python setup.py install
running install
running build
running build_py
running install_lib
running install_egg_info
Removing /usr/local/lib/python2.7/dist-packages/pimodules-0.1dev.egg-info
Writing /usr/local/lib/python2.7/dist-packages/pimodules-0.1dev.egg-info
pi@raspberrypi:/PiModules/code/python/package $ cd PiModules/code/python/upspico/picofssd
bash: cd: PiModules/code/python/upspico/picofssd: No such file or directory
pi@raspberrypi:/PiModules/code/python/package $ sudo python setup.py install
running install
running build
running build_py
running install_lib
running install_egg_info
Removing /usr/local/lib/python2.7/dist-packages/pimodules-0.1dev.egg-info
Writing /usr/local/lib/python2.7/dist-packages/pimodules-0.1dev.egg-info
pi@raspberrypi:/PiModules/code/python/package $ sudo update-rc.d picofssd defaults
update-rc.d: error: initscript does not exist: /etc/init.d/picofssd
pi@raspberrypi:~/PiModules/code/python/package $

Hello,
I am attempting to reset the battery run time using
sudo i2cset -y 1 0x6B 0x01 0xff
but it is returning "Error: Write failed"
I get a similar read failed error with i2cget
My apologies if this is an easy fix, I am new to linux and rpi.
Thank you for the help!

I thought I would test this unit again by pulling the power cable (to simulate power failure) and I was somewhat surprised that the whole unit died.

Upon re-powering the unit, I notice that the BAT LED is on constantly.

Running the pico_status.py script, gives me a Battery voltage of 0v. I have of course checked that the battery connector is firmly plugged in.

The PI is currently powered from the standard Pi mains-to-5v plugin adaptor.

What else can I try ?

Hello.
I have a bunch of Rpi and PIco UPS to protect them, and some have undervoltage issue upon boot:

• Rpi3b + PIco UPS for mediacenter. So far, never had any issue
• RPi3b+ + PIco + 2.13in epaper screen for PiHole: when booted up, soon I get an "undervoltage log" and the rpi shutdowns after 40 seconds. To have a stable boot I need to:
  • plug the power. The Rpi starts
  • when I get the undervoltage error, unplug the 5V cable.
  • wait for a few seconds, plug again, boom, the status script says "Rpi powered", and could stay like this for weeks
• Rpi3b+ + PIco + USB keys (zwave sticks, rfxcom) for domoticz. Same issue, undervoltage log and auto-shutdown after 40 sec. The previous tricks does not work, I have to plug a self-powered USB hub, without anything connected to it. Having the 5V a bit leveled up by the USB kind of help PIco.

For all Rpi I use, for each, a 5V 3A power charger. I do think the issue is somehow related to power, but 5V 3amps is what you recommend, and I don't think there is 5V 4amps charger anywhere. Any idea how to solve my boot issue?

Thanks

Something like the one for the old version, with a list of LEDs and their interpretations when blinking?

Trying to update the firmware

enter the following:

sudo python 9600_picofuHV3.0.py 0xE3_UPS_PIco_HV3.0_main.hex

return is

python: can't open file 9600_picofuHV3.0.py [Er no2] No such file or directory

Please see: https://learn.adafruit.com/adding-a-real-time-clock-to-raspberry-pi/set-rtc-time for instructions.
Found here: https://www.youtube.com/watch?v=yCWGeNUxF88&lc=z12pexl4ml3vwr0fk22bxdyjrzfdfh2fp

I started using this and found what I think isn't normal behavior:

The piezo beeps continuosly every 6 or 7 seconds, doing a different tone each time. I believe I discovered this is because the UPS Pico is constantly switching from USB power to battery. When I run:

sudo i2cget -y 1 0x69 0x00 b

I get 0x02 most of the time even though it's powered via USB, and eventually I get 0x01 but I immediately get back to 0x02

Then if I disconnect the USB power, the raspberry shuts down.

Am I doing something wrong, or is the UPS Pico defective?

I uploaded a video to demonstrate this:
https://www.youtube.com/watch?v=yCWGeNUxF88

Issue: When the main power to Pi is lost then the Pico takes over and shuts down the Pi at the set time. But then it takes about 60 seconds for the module to shut itself off. If power comes back during this, the Pi wont restart.

I'm reading that this is a known issue but I can't find a solution anywhere. Please help.
I'm using the the 0XEC firmware version.

Hi, I just have read the new manual version .

3.0 15/06/2018 all Updated to Version HV3.0B/C with new
functionalities and B+ assembly Instructions

I still don't understand which register I have to set to which value to enable magic-switch :

• power off of pi when slide is in off position (with battery and don't care about of Cable power)
• power on of pi when slide is in on position (with battery and don't care about of Cable power)

There is some new information on page 84, but it's not really clear for me.

Hello everyone,

I hope, I am at the right place for my topic.

I have a UPS Pico Stack Plus 3 and a LiPO Battery 4000 mAh connected. Before I installed the latest Firmware update (0xE3) firmware update, i disabled the shutdown delay to indefinite by setting the following i2c command:

sudo i2cset -y 1 0x6B 0x01 0xFF

PThiw worked fine so far.
After the firmware update, the Raspi shots down immediately after diconnecting, even when i set the shutdown time to indefinete.

Does anybody else observe such a behaviour?

Thynk you
Gerald

Hi I've just finished soldering all components to the PIco Plus HV3.0B board and was left with

• 1 jumper pins
• on/off switch

for which I could not find anything in the documentation, except that the on/off switch seems to be soldered on one of the corners according to the picture.
On the PCB the only socket for the pins I could find noted with WD (Watchdog?)

Did I solder the components correctly and what is its purpose?

thanks

I bought the 8000mAh battery hoping to get long hours out of it, but it discharges too quickly. I only get about 90 minutes out of it before FSSD (3.6V -> 3.0V).,

The pico board is set to the correct profile and we charge it with 5V 3A charger. No tasks or gui is running. Just logging.

Board:
UPS Pico HV3.0A Stack Plus

Battery:
LiFePO4 3.2V
Capacity: 8000 mAh

I have the UPS PIco HV3.0A Stack Plus with the included 450 mAh battery. In the manual it says that: The External Supply Powering Input is equipped with Over Current protection, Over Voltage as also with Zero Voltage Drop Inverse Polarity Protection protecting Raspberry Pi System from improper usage, but also offers, due to zero voltage drop, usage of all available energy from the Solar Panel in case of use.

But in the documentation it doesn't say anything about how to do it. In my case I can have another 5V input for the PICO but I don't know how to make the connection.